Hi everyone,
I am looking for technical insight into a persistent issue with Firefox on my Poco F8 Ultra running HyperOS 3.0.7.0 (Android 16).
The Issue:
There is a consi… (meer info)
Hi everyone,
I am looking for technical insight into a persistent issue with Firefox on my Poco F8 Ultra running HyperOS 3.0.7.0 (Android 16).
The Issue:
There is a consistent 10-second delay when opening external links (Intents) from other apps (WhatsApp, Discover, etc.), but there is a very strange catch:
Firefox in background: 10-second delay before the page starts loading.
Firefox force-closed: The link opens instantly.
It appears that the Warm Start is significantly slower than a Cold Start. It feels like the Gecko engine enters a "Deep Sleep" state in HyperOS 3.0 that the Android Intent cannot wake up immediately, causing a timeout. Chrome works perfectly in all scenarios.
Tested on: Firefox Stable, Beta, and Nightly (all exhibit the same behavior).
What I have already tried:
Battery Settings: Set to "No Restrictions", Autostart enabled, and app "locked" in the Task Manager/Security App.
Add-ons: Tested with a completely clean profile (no uBlock, no extensions).
System Settings: Cleared Dual Apps cache, toggled HyperOS Optimizations.
Network: Toggled Private DNS (Android) and DNS-over-HTTPS (Firefox).
Firefox Internals: Tested network.http.speculative-parallel-limit set to 0 and Safe Browsing disabled.
This seems to be a conflict between HyperOS 3.0's new process scheduling and how Gecko handles incoming Intents. When the process is already alive but suspended, the handshake takes 10 seconds. When the process is dead, the OS just spawns a new one which bypasses the "resume" lag.
Is this a known issue with the Snapdragon 8 Elite's scheduling or a GeckoView bug on the latest HyperOS versions?
I have attached a screenshot to show what is just standing there for 10 seconds when I click a URL from anywhere.
