Closed leehyunkeun closed 10 months ago
No, your only option is to wipe app data.
Please don't make random changes to Mull, it defeats the purpose of it.
There are a small handful of workarounds you should stick to: https://divestos.org/pages/broken#mull
Are you serious?
Surely, there must be a way to access about:config
via adb
.
Where exactly are these settings stored? Isn't there something like a prefs.js
or some XML file that one can modify to reset individual settings? AFAIK, this is no problem whatsoever on desktop versions.
I don't know where settings are stored, I don't keep a rooted device.
This is not a usecase I support, you'll have to figure it out on your own.
How did you build this fork and configure all the about:config
settings without such knowledge? Also, the device in question is not rooted.
Where the files are compiled in is completely different than where they are stored on device in userdata partition.
And if you don't have root, then it is guaranteed you can't possible fix it.
Users can't edit private app data, which is where these settings are saved.
I have modified an
about:config
setting and now tabs are no longer loading, including any of theabout
pages, meaning that the browser is effectively bricked.Is there any way to read out
about:config
settings e.g. viaadb
(similar to the list of important changed configurations as displayed on theabout:support
page) and reset selected ones without having to reset/reinstall the entire app?The last options modified right before the brick belong to the
browser.cache
group, so I am fairly certain which settings need to be reset in order to unbrick the browser.