Closed MichaelZ4714 closed 2 years ago
github-actions[bot]
commented
2 years ago Thanks for your contribution! Please keep in mind we will get to this issue when we have a chance. Logs and device information are mandatory if you do not want your issue closed without response.
androidacy-user
commented
2 years ago Do not report bugs with non official magisk. We cannot verify that they didn't introduce some bug preventing our module from working.
You are on your own until you can reproduce on official magisk. If you still can, open a new issue with logs and we'll take a look.
Installation of WebviewManager 10.4.1 with Bromite Webview and no browser is fine on Samsung S9+ (star2lte) with LineageOS 17.1 and microG (from https://lineage.microg.org) and Magisk 24.102 (from TheHitman7 https://github.com/TheHitMan7/Magisk-Files).
But after reboot Android System Webview is still active and Bromite Webview can not be selected. It looks like the overlay is not functional.
On my reserve device Samsung S4 (jfltexx) with same system environment it works fine.
I can not find a problem in the log files, but I observed a strange behaviour on the not working S9+. The file /data/system/overlays.xml is modified after Magisk module post-fs-data.sh creates the entry for org.androidacy.WebviewOverlay state=6. Some magic process changes to state=1. This does not happen on the S4. When I manually change it back to 6 it is again 1 after reboot. I don't know if this makes the overlay not to work.
I attach the log files from the not working S9+ full-2022-03-10-10_50_38.log full-2022-03-10-10_58_40.log overlays.xml.txt
Does anyone have an idea whats going wrong? I would love to have Bromite Webview back on my main device. Until the change of Bromite Webview's package name everything was working perfect (I did use Magisk module Nanodroid-BromiteWebview).
P.S. For analysis I also did a fresh install of only LineageOS, Magisk and WebviewManager, but same Problem.