Skip Navigation
Privacy @lemmy.ml
Darth_Vader__ @lemmy.world

Anyone here use GrapheneOS??

I am a long term GrapheneOS user and would like to talk about it. r/privacy on the redditland blocks custom OS discussions which I think is very bad for user privacy, and I hope this post will be useful to anyone who are in the hunt for better privacy.

Nowadays smartphones are a much bigger threats to our privacy and Desktop systems, and unfortunately manufacturers has designed them to be locked down devices with no user freedom. You can't just "install Linux" on most smartphones and it is horrible. And most preloaded systems spy on us like crazy. That was why I specifically bought a pixel and loaded GOS onto it.

According to https://grapheneos.org/features , they start from base AOSP's latest version, imptoves upon it's security and significantly hardens it. There's hardened_malloc to.prevent against exploitation, disabling lots of debugging features, disabling USB-c data, hardening the Linux kernel and system apps etc. They even block accessing the hardware identifiers of the phone so that apps cannot detect whqt phone you're using. That means with Tor and zero permissions given, apps are anonymous.

Compatibility with apps are best in Custom ROMs but there are still that can't work, especially if they enforce device integrity. Very few apps usually enforce that tho. Also their community isn't the friendliest but you can get help. Just don't try and engage too much or have too many debates.

Anyone else here use GrapheneOS, or any other privacy ROMs? What is your experience? Do you disagree on any point? Let's have a discussion!

158 comments

  • Yep. Been using it for about 2 years now. So far no issues except amazon prime but they gave me adds sufficiently annoying that i finally got around to setting up jellyfin. Been able to solve pretty much all my issues with dr gpt.

    Every time i see someone posting about a new mobile phone exploit i get immense joy scrolling down through comments and finding someone posting the fact that graphene patched it 3 years ago and recommended a patch to google who have yet to implement it into base android.

  • Using it since many years on many Pixels and loving it.

    Main pros: zero bloat, efficient, highly secure and highly private (about as private and secure as it can get on any smartphone), and it's an Android without any of Android's typical weaknesses (privacy issues, bloat, etc.). You get to utilize the advantages of Google (its security) and completely avoid the disadvantages (its many privacy issues). You get to use all the advantages of an Android mobile OS while completely avoiding all of its disadvantages. It's like getting your cake and eating it too. You're much better off in terms of security and privacy than almost(?) all other smartphone users. According to leaked documents, Cellebrite for example can't crack GrapheneOS on Pixels at all. They can crack almost any other smartphone if they have physical access to it. Most smartphones are really easy for them to crack. iPhones may pose some trouble depending on model/OS. And Graphene on Pixel is the literal brick wall. And even on top of that it has tons of great security features, like auto-reboot after X hours of inactivity, charge-only-mode for USB-C when locked, distress/duress PIN entry to immediately wipe the phone, many things like that. On the privacy side it's looking great as well: Some folks have analyzed Graphene's network traffic and there's zero privacy issues from the OS or its built-in apps. And the few connections it does make (for updates and so on) are all documented and work exactly like they documented them, and they only transmit the exact least amount of necessary data without anything beyond that (guess what - that's super rare). And on top of that there's even more great privacy features, some of which are invisible but well thought-out, for example any SUPL request goes through a Graphene proxy server first (configurable) which strips all personally-identifiable data from the request and then redirects it to your provider's SUPL server (which is most likely Google's SUPL server in the end). I'm seriously impressed by the quality of the GrapheneOS project. Maybe you don't realize how good and rare such things are nowadays. Also the documentation is very good and actually answers most of your questions and doesn't contain any marketing blurb. The social media feeds and forums are a great source of info as well. On top of all that it's even easy to install GrapheneOS.

    Main cons: it's only available on Google Pixel phones, so if you truly despise Google and don't want to buy or use anything from them, it's not the right device/OS for you (or maybe buy it used?). However, the reason GrapheneOS is on Pixel is purely a technical one: Pixels do offer very high hardware based security already (probably the most, although iPhones have good hardware-based security as well. As is known, Apple tends to be produce good quality hardware, not quite so good software) as well as a very high degree of "platform neutrality", i.e. it's supported by Google to flash a different OS on it or use more advanced tools like adb without any sort of tinkering or unnecessary danger involved. Also you don't have to register to unlock your phone or anything, you only need to be online once to enable the OEM unlocking feature (I think this is because Google needs your IMEI to check whether the phone is carrier-locked (cannot ever be OEM unlocked) or can be unlocked, and they will immediately receive some device data including the IMEI as soon as you go online with the preinstalled Android OS once [of course they will receive some more device data than just the IMEI]), so it's best to not insert your SIM yet (and not do anything with the preinstalled OS) before you've installed GrapheneOS on your new Pixel. Do the OEM unlocking step on WiFi only, best on a public WiFi so Google has much less of a chance to identify you based on your IP or related data. Then install Graphene, then insert your SIM and start using your new phone. Other cons exist but they're rare or pretty much irrelevant in daily use. If you have to hear them, read an older post by me about some potential downsides: https://discuss.tchncs.de/post/19867254/12069767

  • Last 4 or so phones have all been GrapheneOS (I'm not buying new phones all the time to be clear; I use phones till they break; I'm just a long-time user) and yeah I've really had no problems to speak of. I currently have a separate profile with Play services for certain apps, and also just to isolate non-privacy-respecting apps that I have to have installed for whatever reason.

    Almost all the apps I use are FOSS apps who are aware that a significant amount of their userbase will be using various AOSP forks so I've not run into any app compatibility issues. Even back when I used banking apps, I'd used 4 different banks' apps on GrapheneOS and all of them worked completely fine. Now I don't have a banking app because I won't install proprietary software unless I actually have to for some reason, and I can bank on the web just fine.

  • I have the pleasure of using GrapheneOS. I can't imagine using anything else. It was also the first (widely used) custom Android distribution to adopt Android 15. As far as I can tell, almost no others support Android 15 yet.

  • I've been on GrapheneOS for 4 years or so. I've tried CalyxOS every now and then, but always end up coming back to GrapheneOS. I find it simple, private, secure and free of BS. CalyxOS does come with some stuff preinstalled, which doesn't really appeal to me, and I trust the sandboxes Google Play model much more that MicroG.

    About the devs, I really haven't had any issues that I have not been able to resolve myself, so my interaction with the is non-existing. I have read some posts with interactions with them, and they do seem to be hostile towards anything that is not 100% aligned with their train of thought, which I find stupid, to say the least. But regardless of how rude they may be, I feel GOS literally has no competition in the Android landscape in terms of privacy and security.

  • My recommendation is GOS if you care about out of box experience and using gapps, DivestOS if you care about degoogling and removal of proprietary code. Both are hardened.

  • A simple search will tell you a ton of people here use GrapheneOS and other custom ROMs. Are you karma farming?

  • I would but my Pixel 6's USB connection is entirely useless. It hasn't successfully connected to a cable in over a year.

    I was considering it for my next one, though, whenever that is. Don't really feel the need for an upgrade atm.

  • I am waiting for the LineageOS port for my SM-A536B.

  • I've been using it for a few months. Very happy with it. Minimalistic initial setup, gives you the feeling of control as well as privacy, bank apps work splendidly... an effortless transition, I say as somebody who previously used iPhone but wasn't tied into the ecosystem.

  • I had daily drove it for years, but recently started testing the water with iOS. Still have GOS on my secondary devices though.

  • Been using it for about five years now. I absolutely love it. But I will say some of these comments make it sound like it's a little easier than it is. I'd say about 80% of your knowledge from Android will transfer over and just work. But the last 20% is a bit of a learning curve, and will take at least a few weeks to get the hang of.

    What I recommended to some of my friends that switched is to get the phone and mess around with it for a few weeks before you switch your sim. Then you'll get the hang of things like alternative app stores and sandboxed play services, and you'll figure out what you can and can't do.

    I will say the vast majority of things do work easily because of protection compatibility mode and sandboxed play services. But there will be some things that are just more hassle then they're worth. I find keeping a second device, like a tablet, without a custom ROM makes that stuff easier.

    And there are some things that seem impossible to get working properly, at least for me. For example, casting to a TV is basically impossible from what I can tell. Also, tap to pay, even for things like tickets doesn't work (although if you have play services, you can use Google wallet for things with barcodes).

    Overall, it's totally worth trying out. Just don't set your expectations too high. You're not getting a completely "just works" experience.

    As for other custom ROMs, I've tried CalyxOS and LineageOS for MicroG. I didn't find either of them quite as good, but that was many years ago. Maybe they've gotten better.

  • Yea I did the same thing as you about 2 years ago. Gonna maintain and use this phone for as long as I possibly can before either betting another one or find a equally good or better solution that doesn't give money to google(and hopefully one with a replaceable battery)

  • I've been wanting to try it for a while now, but I'm too cheap to buy a phone that can run it.

  • Tried it, tons of apps don't work and battery life was ass.

    • Were you using sandboxed Play Services? Having multiple apps doing their own notification listeners can definitely impact battery, but I've not had an issue.

158 comments