this post was submitted on 05 Feb 2024
127 points (98.5% liked)

DeGoogle Yourself

8807 readers
35 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

!privacyguides@lemmy.one !privacy@lemmy.ml !privatelife@lemmy.ml !linuxphones@lemmy.ml !fossdroid@social.fossware.space !fdroid@lemmy.ml

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
[–] jadedwench@lemmy.world 2 points 9 months ago (2 children)

You had me almost convinced to try this on mine up until the NFC. I use contactless payments on mine at 90% of the places I shop, so that is a deal breaker for me.

[–] JustUseMint@lemmy.world 10 points 9 months ago (1 children)

NFC works fine on GOS, however, Google does not consider it a approved os so itb failure attestation, any form of NFC payment will not work because of this. It's not because of GOS or hardware, it's literally Google being cunts.

Just to be clear NFC works fine, you can use Yubikeys all day, and certain other NFC style tokens like a train ticket or what have you do work as well.

[–] joeldebruijn@lemmy.ml 2 points 9 months ago (1 children)

"Any form of NFC payment will not work" means not only Google Pay, but banking apps with their own NFC implementation neither?

[–] PoorPocketsMcNewHold@lemmy.ml 9 points 9 months ago (1 children)

Depending if they rely on the G Play Integrity API or SafetyNet Attestation API https://grapheneos.org/articles/attestation-compatibility-guide There's a secure way to attest it, but if i understand it, it require the app devs to explicitly add support of grapheneOS via hardware attestation API

[–] JustUseMint@lemmy.world 3 points 9 months ago

Yes this 💯 and as well all know the chances of a dev explicitly adding GOS support are slim to none

[–] smeg@feddit.uk 2 points 9 months ago (1 children)

Can you not just get one of those wallet-cases and put your contactless card in the same place as your phone?

[–] jadedwench@lemmy.world 2 points 9 months ago (1 children)

I already have a really nice wallet and phone case. Things are hard enough as it is to fit into my pockets. I personally have no problems with my Pixel 6 and I really don't want to create them without a really good reason.

Having the digital wallet has saved me multiple times in the past with fraudulent payments and lost/damaged cards. When you are waiting for your new card in the mail, the digital payment system that is linked with your bank/CC is still able to be used in the meantime. That means I can go get groceries and gas. I have had it take over a week to get a new card. If I am traveling/out of town, then it is even a bigger mess.

I understand that Google is evil, but there are some things that I am ok with them tracking, such as my location with Google Maps Timeline. As long as I can mostly block out the advertising on my phone with AdGuard, that will just have to be enough at this time.

[–] smeg@feddit.uk 0 points 9 months ago

Those sound like some very specific edge cases. Of course it's fine for you to do whatever you want, it's all a trade-off of what you lose vs what you gain. "Threat model" and all that.