#1225·gyroflow

Android 17 / Xiaomi HyperOS 4: Unable to import any video on Xiaomi 18 Fold

Author: ericderwu-hashCreated Sep 14, 2026Updated Sep 14, 2026
Labelsbug

Is there an existing issue for this?

  • I have searched the existing issues

Have you tried the latest dev build?

  • I have tried the latest dev build from here

Do you have latest GPU drivers installed?

  • I have the latest GPU drivers installed, I'm absolutely sure.

Have you checked the documentation?

  • I have read the FAQ and Troubleshooting and didn't find my issue there.

Gyroflow version

1.6.3 (gh2699); also reproduced on latest Android development build

What operating system are you using?

Android 17 (API 37), Xiaomi HyperOS 4.0.11.0.XPNCNXM

What GPU are you using?

Mali-G2-Ultra-NX MC16 (XRing O3)

What happened?

Xiaomi 18 Fold running Android 17 / HyperOS 4.0.11.0.XPNCNXM cannot import any video into Gyroflow. This occurs with both Gyroflow 1.6.3 (gh2699) and the latest Android development build. Steps to reproduce: Open Gyroflow. Select Add/Open video. Select an MP4 using the Android file picker. The picker returns to Gyroflow, but the video is not loaded. The same problem occurs when sharing a video directly from Xiaomi Gallery to Gyroflow. I also copied a test MP4 to a normal folder under Download and selected it using the system file picker. The result is the same. Android bugreport findings: Android 17 / API 37 HyperOS 4.0.11.0.XPNCNXM Gyroflow 1.6.3 (gh2699) Qt 6.7.3 The system granted Gyroflow URI access to the selected media, so this does not appear to be a simple storage/media permission issue. During one Gallery → Gyroflow reproduction, Android recorded APP_SCOUT_HANG. Thread traces show the Android main thread waiting around QtNative.startApplication → QtThread.run → Semaphore.acquire, while the Qt thread reaches QtClipboardManager → QtNative.runAction and waits on the same lock. Earlier native crashes were also recorded on Gyroflow's RenderThread with: FORTIFY: pthread_mutex_lock called on a destroyed mutex followed by Fatal signal 6 (SIGABRT). A separate document-tree result showed a NullPointerException around deliverResultsIfNeeded. This may be a separate path, so I am not assuming it is the direct cause of MP4 import failure. The issue is reproducible on both the stable and latest development builds. I have a full Android bugreport available if the developers need additional traces. I can provide a redacted log or reproduce the issue with specific logging instructions.

Gyroflow_developer_issue_report.md

Relevant log output

bash
APP_SCOUT_HANG

Android main thread:
QtNative.startApplication
QtThread.run
Semaphore.acquire

Qt thread:
QtClipboardManager
QtNative.runAction

Earlier native crashes:
FORTIFY: pthread_mutex_lock called on a destroyed mutex
Fatal signal 6 (SIGABRT)
Thread: RenderThread

A separate document-tree result also recorded:
java.lang.NullPointerException
android.os.Bundle.getString(...) on a null object reference
around deliverResultsIfNeeded