I use Mull as daily browser but I felt it was much slower than Firefox and Fennec because it is very much hardened. I want to make Fennec better than stock Firefox but not as hardened as Mull but couldn’t find any wiki or guide for mobile version about:config. I was wondering if there is any guide for about:config which keeps track of mobile config changes too?
Complete unfounded speculation on my part:
I honestly wouldn’t be surprised if any observed performance differences were some weird placebo.
I know of no change that Mull makes that actually has any noticeable impact on performance.
And I’ve found Mull actually much smoother than Chromium-based browsers on my old Galaxy Nexus in testing.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
I use Mull as daily browser but I felt it was much slower than Firefox and Fennec because it is very much hardened. I want to make Fennec better than stock Firefox but not as hardened as Mull but couldn’t find any wiki or guide for mobile version about:config. I was wondering if there is any guide for about:config which keeps track of mobile config changes too?
Yes, same shit as on desc FF , remove all GOOLAG shit and enable webrender / webGPU
I have a similar question, I noticed that when updating FF-F resets the settings, someone knows where he stores his settings and is it possible to create your own preset that will not be reset
@ism1337
The bottom of my comparison table has recommended settings: Browsers - DivestOS Mobile
Actual performance of Mull should be pretty close to regular Firefox for Android however.
Should not happen, what OS are you on?
To lazy to retest it, i will try some online bench at this week
100% at LOS17-18-19 at diff phones (Asus / Sony / Lenovo)
@ism1337
did you install any addons?
Ublock or Adguard / Bitwarden
Hey, so… the Mull browser, from DivestOS (defunct) was - from my understanding - the same as Fennec essentially and, with added arkenfox user.js Advanced Preferences, about:config settings.
The problem with it, one which (absolutely!) persists to this day - now continued via GitHub IronFox project, the successor to Mull - is how they did >NOT< implement all required settings; GitHub - ironfox-oss/IronFox: Private, secure, user first web browser for Android. This is a read-only mirror of https://gitlab.com/ironfox-oss/IronFox. · GitHub
(Understandably so, perhaps, as some >WILL< hamper browser functions.)
One such about:config setting is: dom.serviceWorkers.enabled
… Now, we can read about some (fairly recent) attempts at Firefox “process isolation”, Improved Process Isolation in Firefox 100 - Mozilla Hacks - the Web developer blog & this issue has been the >MAIN< difference between the Firefox browser and the rest… such as Google Chrome, Chromium (and Edge); and, we’re (only, ever!) using Ungoogled Chromium, ofc., btw.
Historically, process isolation has been THE caveat when it comes to (Mozilla) Firefox. << This is, arguably, right, THE most important issue with Mozilla’s browser, so I’m saying that I didn’t necro this locked thread here!
=)
Ok, so… in order to >COMPLETELY< avoid any issues, Firefox being vulnerable to a series-and-a-plethora of attacks which (absolutely!) cannot be mitigated - due to the nature of its engine - and, so, we are simply >ELIMINATING< that entire vector with disabling dom.serviceWorkers.enabled
Alright… cool… as far as the original question, reference to about:config - we are looking at it, exactly through the GitHub arkenfox user.js project @GitHub - arkenfox/user.js: Firefox privacy, security and anti-tracking: a comprehensive user.js template for configuration and hardening · GitHub
*Else, all of the seetings are only individually references (when searched), by Mozilla..
P.S. No technical references, links, added… as this would /could take me like a week to explain, sorz! xF
P.P.S. I may try and add some (hopefully, blah! :))
Furthermore, looking at IronFox - previously the DivestOS Mull browser - we have got more things missing; which should’ve been set… if we’re going to say how it is hardened. The (working) list; not documented anywhere else:
- dom.event.clipboardevents.enabled
- dom.event.contextmenu.enabled << restores original right-click-tap menu to actually be able to control page elements, instead of having it masked by some
crazyB$ (hehe) - network.manage-offline-status << err, not 100% sure if present or, not! ;$
P.S. Could there be in GitHub - yokoffing/Betterfox: Firefox user.js for optimal privacy and security. Your favorite browser, but better. · GitHub hm