this post was submitted on 05 Jun 2026
446 points (97.9% liked)
Privacy
5917 readers
219 users here now
Welcome! This is a community for all those who are interested in protecting their privacy.
Rules
PS: Don't be a smartass and try to game the system, we'll know if you're breaking the rules when we see it!
- Be civil and no prejudice
- Don't promote big-tech software
- No apathy and defeatism for privacy (i.e. "They already have my data, why bother?")
- No reposting of news that was already posted
- No crypto, blockchain, NFTs
- No Xitter links (if absolutely necessary, use xcancel)
Related communities:
Some of these are only vaguely related, but great communities.
- !opensource@programming.dev
- !selfhosting@slrpnk.net / !selfhosted@lemmy.world
- !piracy@lemmy.dbzer0.com
- !drm@lemmy.dbzer0.com
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I really hope the Motorola thing actually pans out. Based on the general state of things I’m done with both Apple and Google.
Same here. And its not like we are overwhelmed with alternatives, too.
Things have taken quite the turn from the nexus era to now, dropping nexus for pixel felt so blatant too.
What about Motorola? 😯
They are going to start loading GrapheneOS on phones from the start
Fantastic! Thanks for explaining 🙏
I got a reply clarifying that theyre partnering with graphene. I figured I'd reply so you didn't miss it in the thread
Yeah same, I have no idea what's happening with Motorola...
They are partnering with GrapheneOS
I don't trust Motorola to make a phone that doesn't have numerous hardware backdoors. Motorola does a ton of work for both the US and Israel. If it sounds too good to be true than it probably is. I think the US/Israel gave Motorola a bit of cash to make backdoored hardware that's made specifically for a privacy hardened software.
Google is more likely to do that than Motorola, a Chinese company
What is the Motorola thinf being referred to here?
Afaik GrapheneOS won't be affected, neither will e/OS. The real problem with them still being based as AOSP is, that google might stop the AOSP project. That would mean the forks would need to do that continous based development themselves.
I searched for statements from GOS and e/OS and what I found tells a different story
https://discuss.grapheneos.org/d/26337-android-developer-verification-are-we-screwed-no-doesnt-apply-to-gos/25 https://xcancel.com/GrapheneOS/search?f=tweets&q=certified&since=&until=&near=
https://community.e.foundation/t/e-os-statement-about-google-developer-verification/79892
Do you have different information?