I’ve tried several forks of mobile Firefox over the months and they all (Mull, Fennec, Iceraven) suffered from the same issue of running at 60 Hz while the regular app runs at the native 120. This makes it feel very sluggish especially in comparison to every other app and has kept me on the official app.
I’ve wondered if other people had the same issue or if it’s related to my phone (Nothing Phone 1), and if there’s a potential fix.
I don’t know about the others but Mull does this as part of privacy resist fingerprinting. You can change it in about:config, rfp false iirc.
There was some brief mention the default might change. I don’t think that happened though.
privacy.resistFingerprintingwas already false in Fennec/Iceraven and I’ve set it to false in Mull, unfortunately all remain on 60 Hz even after force closing.
Fennec runs at 90hz on my Pixel 5. Mull doesnt go above 60
I’ve noticed they stay at 120 until I open the first tab, then they’re locked at 60 until I close all tabs and reopen the app.
I don’t have the same issue. Fennec from F-Droid runs at 120Hz even with tabs open
The indicator does flicker between 60 and 120 while the page is loading, but it’s not perceptible. However, if what I’m seeing means the FPS goes down to 60 while the app is busy, this may be some kind of performance throttling done to keep resource usage low. If you have lower end specs, this may be the explanation. I’m on a Pixel 6 Pro.
Performance is a good lead since it feels lower than 60fps and my panel can only switch between 60/120 Hz. I wonder what could cause that to happen only on the forks since the regular Firefox is buttery smooth even on complex sites.
I’ve never noticed sluggishness on Mull or Fennec. Are you talking about the app’s refresh rate to the screen? I’m confused.
