Replying to @⁨beep@piefed.world⁩

These are welcome changes but I hope they will address the elephant in the room sooner or later. They can’t go on depending on Pixels and hardware memory tagging. They need a roadmap for opening up the project to more phone models and they need it yesterday.

They’ve drummed up some publicity with the journalist debacle so it’s a good time to use that. But people who hear about Graphene will want to have some phone choices. “Get an old Pixel” is about to age like milk.

Replying to @⁨SatansDaughter@quokk.au⁩

Which is better than nothing but I can’t help but see it as walking into another exclusive partnership. Also, none of those phones are out yet so I’ll believe it when I see it.

Even if it pans out and there will be one Motorola phone supporting GrapheneOS out of the box in 2027, there’s the issue of how much it will cost (I think it’s supposed to be a “flagship”), what markets it will be available in, what the unlock process and conditions will be like etc.

Last but not least I doubt Lenovo’s commitment to “seven years of proper updates”, which I will also believe when I see. Their track record for Android updates is notoriously poor. They claim 3-5 major Android updates for most of their models but the best I’ve actually seen them do is one update (13 to 14) – and that’s for phones released 2-3 years ago. If that’s the pace they wanna go we’ll be lucky to get two updates in those 7 years.

Replying to an earlier post

Blame the manufacturers for not including hardware security on cheaper phones. It would be nice to have sandboxes Play Services on a less secure phone for example, but it’s simply not GrapheneOS if you gut a lot of features that make people trust in it. Same principal as Privacy Guides. They’re not going to recommend something that’s doesn’t meet their requirements. You will not see them recommend Windows no matter how many people cement “but how do I use Windows privately?” You can’t. That’s why it isn’t recommended.

Replying to an earlier post

Blame people unwilling to pay for security for cheaper phones not having hardware security features.

Blame the other manufacturers for not letting GrapheneOS unlock and relock the bootloader on their good phones with hardware security.

Blame Graphene for not making a lesser version “CharcoalOS” (or something) for other phones, so now I have to use the even less secure, beginner-friendly /e/OS on my Sony phone.