- cross-posted to:
- privacy@lemmy.ml
- cross-posted to:
- privacy@lemmy.ml
You must log in or # to comment.
And it still doesn’t support anything that isn’t a Pixel phone.
I respect GrapheneOS very much. But the fact that you need a Google phone to install a deGoogled Android ROM is one contradiction I just can’t get past. I hate Google and I’m never going to buy their hardware and give them money for the privilege of escaping the Google corporate surveillance.
I’m aware of the technical reason why GrapheneOS only supports Pixel phones, but that irony is just too rich for me. So I use CalyxOS on a very much non-Google FairPhone4, and while it’s formally slightly less secure than GrapheneOS, at least Google got none of my money and that’s a lot more important than security to me.
It is quite ironic. “I don’t like Google, let me free myself from all of Google. But to do that first let me buy that $500-$1,000 phone made by Google to then get rid of all the Google software on it”.
Their hardware requirements are pretty clear. Samsung is the only one with comparably secure devices, but they use nonstandard tools like Odin and lock down many security features to the stock OS only.
Other companies are supposedly not making anything as secure.
https://grapheneos.org/faq#future-devices
Also, only Google can really ship updates that quickly and fully, as Android is literally their OS. They are also a huge company, so yeah they have way more resources than a random other company you might prefer.
Example Fairphone, which has horrible update schedules
I am aware of the shortcomings of my choice.
But my priority is to not give a cent to Google: what am I supposed to do then?
I argue that GrapheneOS gives Pixel phones more value, thereby supporting Google. That is not great.
Buy a used Pixel phone.
