One can either go through the steps to find out (or search around to see if that’s the case) or just use the standard Chromium webview ( ) and not worry about the framework procedure.Ĭhromium webview is available for regular updates via F-Droid, using Bromite repo, so that’s cool. To use that one has to hope that custom ROMs today have added support for it. Usually not due to signature issues.įast forward to current time. Only Google’s webview and Chrome products.Īfter going through the steps we’d cross our fingers and hope the ROM would boot. Whereas all custom ROMs use/supoort, stock ROMs did not. In the case of the Nanodroid Bromite webview installer I’ll check to see if the updater script needs modification first.īack in the day, before the package name change, we would try to get Bromite webview working on OEM stock ROMs. Maybe today I’ll take a look at either method. Currently neither of my /e/ devices have TWRP. I vaguely remember, on /e/OS Pie having to manually remove it. The installer package wouldn’t (didn’t) know how to remove/replace it. e/ for instance places its webview at /system/app/BrowserWebView/, which is a non-standard location. Whether or not the package handles current system root location and whether it can find and replace the existing webview. This will essentially be vanilla Chromium webview (). On the other hand, if the last Nanodroid Bromite Webview package can be flashed successfully then it can also be regularly updated via F-Droid (with Bromite repo added). I do so on other ROMs but have not on /e/. If rooted then it is probably doable via a Magisk module.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |