Hi everyone, this is my first post here, so bear with me. I was a passive lurker until now but these days I am searching for a new phone, my old one just broke and will run out of security updates soon anyway (I am using GrapheneOS at the moment).

I am satisfied with GrapheneOS but don't like the vendor-lock-in. In general I am a big opponent of mass surveillance and mass collection of user data, naturally I am not a big fan of Google ;).

I looked at alternatives and thought about the Fairphone with /e/OS or CalyxOS which looked nice initially but then I found this thread on the GrapheneOS forum: discuss.grapheneos.org/d/24134-devices-lacking-standard-privacysecurity-patches-and-protections-arent-private which if everything is true the GrapheneOS developer (or whoever is behind the GrapheneOS name there in the forum) is writing there doesn't shine a good light on Fairphone or /e/OS. I truly believe that getting security updates quickly is quite important, especially in the AI era we are living in. If you get security updates after the security issue got public I guess one can expect that this is a problem (depending on the severity of the issue).

I then also found a link to this comparison: (I seem to not be allowed to post the link here, it is eylenburg's "Comparison of Android-based Operating Systems") which to me also says: there is nothing coming close to GrapheneOS.

So my question here: Do you think there are any real alternatives to buying a Google Pixel and using GrapheneOS at the moment if I want a privacy focued OS? I am not so much worried about being targetted by some three-letter agency or what not but am more worried about classical every-day mass-surveillance and data collection.

you are viewing a single comment's thread
view the rest of the comments
[–] 17 points 10 hours ago* (last edited 10 hours ago)

There's not. Procure a Pixel and use GrapheneOS. Even if your primary concern was just mass surveillance this is still the best you can do. /e/OS compromises:

To remove or disable any feature or code that is sending data to Google servers, or at least to anonymize those accesses

All Google apps are removed and replaced by equivalent Open Source applications. The one exception is the Maps Application but this is about to change as Murena now develops Murena Maps (beta).

Other projects likewise make compromises with Google.

Google is a mass-surveillance company that runs on the logic of surveillance-capitalism. Small compromises still give Google a plethora of data from which derivatives can be inferred. There should be no compromises.

An alternative is a GNU/Linux phone like the Pinephone. Mobian (Debian for mobiles) supports other platforms too. This is my preferred approach as it's not derived from AOSP which is ultimately controlled by Google. It's also more experimental with all the implications that entails: less secure, less reliable blah blah blah.

Concerns about supporting Google via procuring a Pixel device:

Your concerns are nonsensical. Google profits from the logic of surveillance-capitalism. Their hardware division is about ensuring people use their software. They’ll sell hardware at a loss to retain and expand their user-base.

Google has been investing for years in building its own hardware that runs on Android’s operating system. That includes Chromebook laptops and Pixel phones. It also builds products like the Nest and Fitbits. Google’s goal is less about building a successful hardware business and more about ensuring that Android, and by extension Google Search, has a broader reach and competes for market share with Apple. But it’s an expensive gambit, and Bernstein estimates that Google loses money on the division.

Google does not manufacture hardware. Don’t get hung up on the branding. Pixels are made by the same company that makes iPhones and a plethora of other computers with a myriad of different brandings.

If a Pixel is sold at a loss buying a Pixel new and installing GrapheneOS on it damages Google financially. I really want to impress upon readers the important distinctions here.

  • source