yes, if you enable resist fingerprinting on any Firefox build it will cap refresh rate to 60hz. Mull is not doing anything special, it’s just changing about:config options by default.
you can disable resist fingerprinting in mull and regain standard refresh rate (although you lose fingerprinting protection) just as you can enable resistFingerprinting in Firefox beta or nightly and see refresh rate cap at 60.
I wholly agree with you there, I’m just saying it’s the same behavior on all browsers built on Firefox. true for desktop as well
it’s worth noting that this is the intended behaviour for privacy.resistFingerprinting. this is not exclusive to Mull.
aosp and android aren’t necessarily one in the same.
just change it yourself
okay buddy
I’m not trolling you’re just demonstrably incorrect.
you’ve posted this same comment at least 5 times and you’ve been wrong every time.
everything always has a security flaw. this is horrible logic
you could have used winget or chocolatey as well.
less crashes, higher average fps, behaves with alt+tab better, etc. everything works ✨better✨
you’re wrong and look stupid.
I love when people post well known and obvious information. if you hadn’t realized metadata is present then idk what to tell you.
you’re explanation makes sense and yet, gaming still works better on kde. it’s a known reality.
I would extend this Nobara recommendation from “for gaming” to “for anyone with Nvidia graphics”
they’ve done it for you by accident
never in my years of using Linux have I ever thought that it was rendered clearer. let’s be honest with ourselves, no need to lie.
you need to use Firefox beta, nightly, mull, or Fennec F-Droid to access about:config and from there you can search for and enable resistFingerprinting. it’s not an option in the settings.