Wasn’t the issue here that they would have liked to partner with GrapheneOS, but GrapheneOS didn’t want to, because of some security requirements that they had?
Wasn’t the issue here that they would have liked to partner with GrapheneOS, but GrapheneOS didn’t want to, because of some security requirements that they had?
DreamlandLividity@lemmy.world 10 hours ago
GrapheneOS had security requirements and they offered to help Fairphone implement them, but Fairphone refused. Apparently they are not interested in their user security and privacy. So I won’t be touching Fairphones with a 10ft stick. Motorola was interested and should be launching a phone with GrapheneOS preinstalled at the end of 2026 or 2027.
BigJohnnyHines@lemmy.ca 9 hours ago
Is there a source available for that?
Qwaffle_waffle@sh.itjust.works 9 hours ago
motorolanews.com/motorola-three-new-b2b-solutions…
BigJohnnyHines@lemmy.ca 9 hours ago
Sorry, I meant for the Fairphone refusing their help part. I haven’t read that and find it interesting. Thanks anyway! I’m optimistic about Moto.
ArmchairAce1944@discuss.online 9 hours ago
I got a Google pixel 10 just so I can have GrapheneOS as soon as possible. I am glad that Google’s plans to lock down Android are blowing up in their faces.
hamsterkill@lemmy.sdf.org 9 hours ago
Graphene has beef with every device maker that doesn’t include a secure element throttle (which is every device maker except Google and Apple, and presumably Moto as of the first partnership device).
DreamlandLividity@lemmy.world 9 hours ago
I mean, if you want to call it a beef, go ahead. But it’s not like it is an unreasonable request, since it is necessary to make sure short pins are at least a bit secure.