Flashing the stock Pixel ROM back is just as simple as flashing GrapheneOS, the instructions in GOS website are very good for both.
The only two things I can think of that might be issues are banking apps and Google Pay, if you use that. I use Play services in the main profile and honestly there's not much difference to the stock ROM in terms of user experience. Even Android Auto works nowadays.
For the banking apps, you can have a look at https://privsec.dev/posts/android/banking-applications-compatibility-with-grapheneos/. Just note that if your bank is not on the list, it doesn't necessarily mean it wont work.
I made the switch when I got a new phone. So I kept both the old phone with android and the new phone with GrapheneOS. There was a transition period when I would bring both phones with me, just in case. Now my old phone is my "whatsapp" phone which I keep at home and turn on rarely. During the transition period I used my old phone number whenever I needed to provide my phone to use a service, but eventually I transitioned that to a VoIP. But, even then, many services will reject VoIP phone numbers, so I still make use of the old one.
I had to request a special scanner from my bank because the banking apps do not work with GrapheneOS. And I had to make sure that nothing important goes into my gmail anymore because google would request that I used my old phone 2FA in the most inconvenient moments, and also I don't want to access google from my GrapheneOS phone.
I think that there are many annoyances that can and probably will happen if you try to jump right into GrapheneOS after having previously relied in the google/meta ecosystem. If you attempt to switch too quickly you might inadvertently lose access to your bank, and you might become suddenly unable to communicate with family and friends. My government's online identification system requires that I use their app, which runs on google services, so I still have to use my old phone for that. And I have encountered situations in which the only reasonably convenient way to proceed is to download an app. For example, recently I registered for a gym that would then require me to use their google-store app so that I could identify myself when purchasing a physical card.
Does WhatsApp not work at all on Graphene OS or do you just need to enable Google Play services for it to work? (I do understand why you personally may not want to enable the Play services, but I'm just curious about the potential capabilities).
It works fine if you have Google Play Services
I think that it works, but for it to work you need to enable Google Play services. From what I understand, this is done in a sandboxed manner simulating a fake identity, so it is possible to do this while isolating Google from your phone to an extent. But I think that WhatsApp is in itself problematic and one of the direct offenders that I want to avoid, regardless of its reliance on Google Play services, and so I have not gone through this effort myself.
recently I registered for a gym that would then require me to use their google-store app so that I could identify myself
What do they do if you say "oh, I don't have a smart phone"?
I am not sure as I did not test this one. Maybe you can go in person and get a worker to get you access to the kiosk through your account to print the card. It is one of those massive chains with gyms in every corner. I think that by now they rely on their digital infrastructure and many of their workers are not trained to handle uncommon situations. At least I get that from some of my experiences, but I could be wrong, maybe if I would have called them could have helped me with this. It was just easier to get the app into my old phone, print a card, delete the app.
I'd start by installing the apps you're familiar with (even non Foss ones) then moving to Foss app by app. its a lot easier to get used to one thing at once. that being said, graphene and pixel os are both android, so they're really similar. and the web installer makes it near impossible to mess up
You can easily switch back to stock Android if necessary :)
I switched a couple of years ago and the process then was pretty straightforward to the point I can't really recall much about it, I can't imagine its got trickier since then. I'm due a new Pixel sometime this year and I plan on putting Graphene straight on to it.
Process is simple;
- Backup everything you want to keep and move the backup off your device.
- Identify FOSS equivalents for all the apps you currently have (but maybe you already use them)
- Read the installation instructions. Re-read until you understand exactly what every step entails and means. Any step you're at all unsure of, ask. Much better to ask questions before you start than be stuck needing an answer halfway through.
- If it goes bad (which it won't) or you don't like Graphene you can, as I said, revert back to stock Android.
GrapheneOS and Android are both based on AOSP, and calling/texting is such basic functionality for a mobile OS that I doubt that GrapheneOS' implementation is much different from Android's, if at all.
I've been on GrapheneOS for the past year or so, I've never actually enjoyed using my phone as much as I do now. No Samsung apps I can't uninstall, no Google spyware, the only stuff running on my device is stuff I want it to run, the way I want it to run.
Just do it. The web install makes it really hard to fuck up. And you can always reflash android if you want.
I don't see much at all that could go wrong with switching over to grapheneos immediately. I, admittedly, did it as soon as I recieved my device so there was no concern, but it was about as smooth as the process could possible have been. Back up any files you care about and just do it, I reckon
Everything should work perfectly fine.
Just make sure you know which apps are not supported on GOS such as Netflix, Hulu, Cash App, etc because of the Play Integrity API. Don't be afraid to use the Play Store as well. Its treated like any other app on the system so it isn't highly privileged.
Also, one thing that was a problem for me at first was the restore solution (and backup solution). You will have to transfer your files from an external drive whether its the cloud or a local one.
Feel free to join the GrapheneOS Discord/Matrix/Telegram server and ask more questions because they're very knowledgeable people that can support you.
Graphene has nothing to do with your sim or phone number, your sim card is possibly tied to your IMEI but that never changes so it should be just fine. If for some reason it won't work after you flash graphene your phone provider should be able to swap you to a new sim card and port your number over no problem, but even that would surprise me, it should "just work."
Btw Whatsapp and Gpay can run on graphene but it sort of defeats the entire purpose. Some people will create an alternate user profile for all that type of shit and install google play services on it, and put all their spyware apps over there. Just something to think about, it's easy to set up once you have graphene installed.
Well, you can always go back to stock by just downloading and flashing the image from Google. So that should be of some comfort.
You could buy a pixel 3 or even lower with the lowest storage possible to run lineageos to test if it suits your needs
Privacy Guides
In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.
This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.
You can subscribe to this community from any Kbin or Lemmy instance:
Check out our website at privacyguides.org before asking your questions here. We've tried answering the common questions and recommendations there!
Want to get involved? The website is open-source on GitHub, and your help would be appreciated!
This community is the "official" Privacy Guides community on Lemmy, which can be verified here. Other "Privacy Guides" communities on other Lemmy servers are not moderated by this team or associated with the website.
Moderation Rules:
- We prefer posting about open-source software whenever possible.
- This is not the place for self-promotion if you are not listed on privacyguides.org. If you want to be listed, make a suggestion on our forum first.
- No soliciting engagement: Don't ask for upvotes, follows, etc.
- Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
- Be civil, no violence, hate speech. Assume people here are posting in good faith.
- Don't repost topics which have already been covered here.
- News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
- Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
- No help vampires: This is not a tech support subreddit, don't abuse our community's willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
- No misinformation: Extraordinary claims must be matched with evidence.
- Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
- General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.
Additional Resources:
- EFF: Surveillance Self-Defense
- Consumer Reports Security Planner
- Jonah Aragon (YouTube)
- r/Privacy
- Big Ass Data Broker Opt-Out List