Conversation
Vanadium is the WebView provider on GrapheneOS. Read grapheneos.org/usage#web-brow. There's a warning when disabling system apps like Vanadium, but users have been disabling it anyway, and then blaming GrapheneOS or third party apps for the breakage they caused despite the warning.
1
2
2
Since the warning and documentation have proven inadequate, the toggle in the user interface for disabling Vanadium has been disabled as is the case for the core system apps. It can still be disabled by more technical users, but hopefully they understand what they're breaking.
1
1
1
I don't understand why people want to disable it. It's a core part of the operating system and is a major part of what GrapheneOS is working on developing. If you don't want to use it as your browser, that's fine, but you're still using it for the WebView in other apps anyway.
Including the unified app providing both the WebView and browser avoids including two separate releases of Vanadium. It makes the updates substantially leaner and reduces memory usage when both are being used, since they map the same shared libraries / resources from the apk.
1
1
3
On the stock OS, the WebView is provided by Chrome. If users disable Chrome, it triggers updating and using the standalone WebView provider built from the same Chromium source tree. This requires the OS to bundle both of them as system apps to work around users disabling Chrome.
2
1
2
Show replies