It's an OS component and is part of Vanadium. Don't touch it, you'll break Vanadium and a lot of apps. We aren't going to give support telling people to break the OS.
remove chrome's apk (trichrome library)
[deleted]
- Edited
It installs with the chrome application
https://github.com/GrapheneOS/os-issue-tracker/issues/1130
- Edited
[deleted] You mean you installed Google Chrome from Play Store and wish to get rid of the Trichromelibrary that gets installed as part of that?
If you have installed Google Chrome, then there is no way other than using adb, to my knowledge to uninstall
com.google.android.trichromelibrary
You should be really careful.
You could easily uninstall the other trichrome library @flawedworld mentioned above and break very basic functionality.
The one you should NOT do anything with is
org.grapheneos.vanadium.trichromelibrary
[deleted]
ayaen I don't want to touch vanadium. Only chrome
- Edited
At the moment it seems that the only way to remove the Chrome's trichrome library (or any user-installed library) is by using adb
(which I'm not particularly fond of).
[deleted]
And what is very strange is that when I uninstalled chrome, I reinstalled it and the play store asked me to reinstall trichrome library ... in short to be sure to do well and as I have no computer I reset my phone
I think it would be a good idea to warn people before they install Google Chrome.
That they should have access to working adb in case they decide to uninstall it as
a 'clean' uninstall would require using it to remove com.google.android.trichromelibrary.
ayaen Agreed, that's exactly why I opened this issue. Maybe it could be addressed in the future.
[deleted]
Wonderfall No need, vanadium is fido2 compatible
- Edited
[deleted] This still needs to be addressed for other apps that might require this. Also, some people want to use Chrome for its synchronization features.
Vanadium being compatible with FIDO2 is great news, but the issue is still somewhat relevant.
[deleted]
Wonderfall OK. Thanks
- Edited
@[deleted] Make sure it's uninstalled by running adb shell pm list libraries
. I had to run the uninstall command a few times to get it removed despite adb returning "Success" several times.
Also, make sure to turn off developers option once you're done. adb should only be used when necessary (from a trusted device) and turned off otherwise.
[deleted]
Wonderfall If one does not feel comfortable tampering with adb, then leaving Chrome installed until there's a way to get rid of the library is probably the safest way to go about this, am I right? Usually I delete unused apps but I guess the library can't be updated without having Chrome installed?
[deleted] I'd say it's better to keep code updated than not updated. Fortunately unlike stock OS, Chrome does not serve the WebView. But still, you want to avoid extra attack surface (ideally).
[deleted]
Wonderfall OK thank you
- Edited
A few things came to my attention (thanks to muhomorr) regarding this topic.
First, unused static libraries can't do anything on their own. They're pretty much harmless.
Second, static libraries can be marked as "unused" by the OS and there are some internal triggers that can decide whether those libraries can be pruned. In other words: no need for adb (unless you want to remove the library immediately), the OS will eventually take care of that (it seems that in Android 12, this likely happens when the device is short on free storage).
Android 13 will make pruning of unused libraries consistent at each system boot and package install/removal.