Details
-
Bug
-
Resolution: Fixed
-
P2: Important
-
6.5.5
-
-
9001262b5 (dev), 09f4d2b79 (dev)
-
2024wk12FOQtforAndroid, 2024wk14FOQtforAndroid, 2024wk16FOQtforAndroid, 2024wk18FOQtforAndroid, 2024wk20s2FOQtforAndroid, 2024wk22s2FOQtforAndroid, 2024wk26s2FOQtforAndroid, 2024wk28s2FOQtforAndroid, 2024wk30s2FOQtforAndroid, 2024wk32s2FOQtforAndroid, 2024wk36s2FOQtforAndroid
Description
No example so far unfortunately since I cannot test this myself, but an application that does nothing for intents, the application frozen for some time after a wake up if there have been intents sent to it while the screen was off.
For example, run an application that accepts intents and wait until the screen is off. Then send 100+ intents to it through adb, and wake up the device and try to interact with it.
Attachments
Issue Links
- relates to
-
QTBUG-118840 [Crash] Vulkan examples crash on Android when unlocking the screen
- Closed
-
QTBUG-118985 The screen becomes blank after unlocking the screen in the app with Vulkan content rendered under a Qt Quick scene
- Closed
-
QTBUG-113255 QML view doesn't update properly when device is rotated with permission dialog.
- Closed
-
QTBUG-114656 Document and explain how a Qt Android app handles the Android activity lifecycle
- Closed