Details
-
Bug
-
Resolution: Unresolved
-
P3: Somewhat important
-
None
-
6.9
Description
When using QScreenCapture::start() to initiate a capture-session, our Android implementation will open up a system-dialog where the end-user has to select what content to capture. Commonly this means selecting either the entire display or a specific application.
The problem is that the Qt UI thread is blocked while this dialog is open. For instance, we cannot run Timers in QML that do periodical work.
Linux+Wayland has a similar setup with the content-picking dialog, but on Linux+Wayland this does not block the UI thread.
What do you expect to happen:
I expect the platforms to behave similarly. Ideally this means I will be able to keep the UI thread going while performing content-picking on Android.
This behavior has been observed on the following devices:
- Motorola Razr 40 Ultra, running Android 15
- Samsung Galaxy Tab A8, running Android 14