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.
The GrapheneOS folks are working with Motorola to have Graphene pre-installed on one of their phones. It would be the first time it is officially usable on anything but a Pixel. It won’t solve the problem described in the OP though. It’s still Android.
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 really hope the Motorola thing actually pans out. Based on the general state of things I’m done with both Apple and Google.
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.
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 is the Motorola thinf being referred to here?
The GrapheneOS folks are working with Motorola to have Graphene pre-installed on one of their phones. It would be the first time it is officially usable on anything but a Pixel. It won’t solve the problem described in the OP though. It’s still Android.
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.
It affects Graphene because people using it still get their apps from Google Play, Aurora Store (also the Play Store), and F-Droid, etc.
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?