this post was submitted on 05 Feb 2024
130 points (97.8% liked)

DeGoogle Yourself

8877 readers
36 users here now

A community for those that would like to get away from Google.

Here you may post anything related to DeGoogling, why we should do it or good software alternatives!

Rules

  1. Be respectful even in disagreement

  2. No advertising unless it is very relevent and justified. Do not do this excessively.

  3. No low value posts / memes. We or you need to learn, or discuss something.

Related communities

[email protected] [email protected] [email protected] [email protected] [email protected] [email protected]

founded 4 years ago
MODERATORS
 

About a week ago, I finally made the decision to flash GrapheneOS on my Pixel 6. I've been thinking about moving to GrapheneOS for months but was afraid to do so because of missing functionalities or app incompatibility that would result in my Pixel 6 becoming unusable. Even though I could just re-flash stock Android should I encounter those issues, I didn't want to bother.

However, last week, I decided to set aside my fears and made the move to GrapheneOS. Whatever fears or concerns I had about missing functionalities or app incompatibilities were completely unfounded. Flashing of GrapheneOS was really easy, thanks to the instructions they provided on their website. The sandboxed Google Play environment still allowed me to download the key apps I needed, whether it be the mobile game that I'm currently playing or a smart home app (e.g. Ring) or a banking app (e.g. Chase). They all worked as expected, though my banking apps required me to turn on Exploit Protection Compatibility Mode, something that was explained to me in one of the Graphene Discussion Boards. Android Auto was another app that I needed for driving, and thanks to the latest update that was made by the GrapheneOS makers, I had no issues in setting up Android Auto to work with my car. That was a huge relief for me!

That being said, there is one thing that is not working, but it's not that important of a feature for me, and that is NFC. Prior to making the move, I did not use NFC that much for payments, although my car app did have a Remote Key function that relied on NFC. As far as I can tell, it looks like NFC is not usable in GrapheneOS. There's probably a good security and/or privacy reason for this, but I do wish something could be implemented for it, as it can be quite convenient. Again, it's not that important of a feature for me to have right now...more of a "nice to have" feature...but I wonder if the GrapheneOS developers are looking into this.

Anyways, it's only been a week since I made the move. I'm sure more use cases will come up the more I use GrapheneOS, and instead of fear, I find myself excited at testing out more apps and functionalities on the OS. Traveling is one scenario I have not yet tried, but that's because I'm not leaving town to go anywhere. That's one set of scenarios that I look forward to trying out.

If anyone has any other advices or information they have about their experience with GrapheneOS, I would welcome it. And for those who are still undecided about moving to GrapheneOS, I hope this post relieves some of your anxieties or worries about making the transition.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 1 points 9 months ago* (last edited 9 months ago) (1 children)

I'm no expert but webview is used anytime remote content is loaded I believe. Certainly you can open links in FF but webview is always there , and not so obvious things always load that way. Webview is baked inte the OS itself. No matter how much you degoogle. Bromite had another webview based on chrome but that's all the alternative that exist as far as I know.

Chromium is still Foss. Google might have a stink and definitely tries to influence on the Foss part. But when it comes to vanadium I have no question about that everything is under a magnifying glass.

As I wrote elsewhere , all projects have their place and I do use FF, just not on android. I would be really happy if FF on mobile would be able to compete but I don't see that happening until we have full Linux phones (that actually does everything android does)

https://www.androidauthority.com/what-is-android-system-webview-3267814/

[โ€“] [email protected] 0 points 9 months ago* (last edited 9 months ago)

I appreciate your response. However, upon reading that article, it seems the truth is somewhere between our two understandings. WebView is no longer baked into the OS:

Around the same time, Google also decoupled WebView from the rest of the operating system and packaged it as a system app instead. This allows the component to be updated independently of major Android updates or security patches.

What I said about an app displaying content using Firefox is also true in some cases. You can see in this screenshot of the article that Firefox is being used in the manner I described (and the selected text describes):

I have often noticed that "powered by Firefox" text, so I guess that's where my assumption came from.

I don't doubt at all that certain apps, specifically Google built ones, still require/use the google WebView, but that's not every app. Boost for Lemmy for example, in my screenshot, uses the custom tab feature which can use Firefox. I am tempted to disable the Google WebView app just to see what happens... I am guessing Google-built apps like Gmail will crash. I wish "custom tabs" were adapted in a manner that Firefox could always be used, but I doubt Google would make that a thing.

At least they do have the custom tab feature, something apple would never do, maybe not even if the friggin EU forced them to. They seem to be weaseling out of some other EU regs, anyhow.

But back to GrapheneOS. Given that Google apps are sandboxed and almost discouraged in that OS, I'm still not sure I understand the specific guidance against Firefox.

Edit: yeah disabling the WebView app causes Gmail to crash horribly and even K9 mail, made by Mozilla, responds the same way. :'(