search

Androidacy / WebviewManager-Module

WebView Manager is a magisk module to change your webview and browser to one of your choice.
https://www.androidacy.com
Other
83 stars 9 forks source link

[Question] I'm not sure how I'm supposed to use the module #5

Closed yephny closed 2 years ago

yephny commented 2 years ago

I can replace the webview by modifying system files; though, I like this module's approach better, so I downloaded and flashed it. During the installation, I specified that I want the webview only, but I was given only a single choice, Bromite, although I wanted to use Ungoogled Chromium's webview. Then, I restarted my decice per instructions and that seemed to be it.

How am I going to update the webview this way? Am I supposed to remove the module, restart, install it in Magisk, then restart again?

A better approach I'd say is using commands. I should be able to open up the terminal, type a certain command like webv -u to update the webview installed by the module and webv -c Ungoogled to switch to Ungoogled Chromium Webview.

This issue is not formatted like a feature reqeuest because it is a question. I'm genuinely curious as to why the app isn't designed to work this way.

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

We didn't implement it this way simply because there's no cli tool for it. You can safely just reflash without reinstalling for it to automatically grab the latest update, or update it with tools like F-Droid.

If enough interest is expressed, I suppose we could definitely consider adding such a tool, but currently it's low priority.

yephny commented 2 years ago

Thank you for your answer, this makes everything clear. If it's possible to update the webview with, for example, F-Droid, then I take back my initial comment as I don't think a CLI tool would be necessary: there's simply no need for an external update command. As for switching to a different webview, it should be too much of a rare occurance to require a command for it. Although the current placing-an-apk-in-a-certain-directory method seems old-fashioned, it doesn't call for a cli tool either.

After having my question answered, I suppose my only suggestion would be to include in the readme even the simplest information that may seem trivial such as how to update the webview.