Conversation
This Tweet was deleted by the Tweet author. Learn more
Suggest reading grapheneos.org/faq#device-sup and twitter.com/GrapheneOS/sta among other information that's available.
Quote Tweet
We're hopeful the recent attention will help us with finding hardware partners with aligned goals.
It's a requirement for the devices to be at least as secure as a Pixel. That includes a modern mobile SoC and a comparable secure element to the Titan M implementing the same APIs.
Show this thread
1
This Tweet was deleted by the Tweet author. Learn more
Replacing the OS can't make insecure hardware and firmware secure, especially when that phone doesn't provide proper support for having an alternate OS installed securely. Most devices have lackluster support for alternate OSes.
1
This Tweet was deleted by the Tweet author. Learn more
The purpose of GrapheneOS isn't to offer something mediocre for people to install on their existing phones. I strongly recommend giving grapheneos.org/faq#device-sup a read through. Broad device support is counter to the goal of the project rather than something we would want to do.
If OEMs release more secure devices with better support for alternate OSes we can consider supporting those. However, our long term goal is to primarily target hardware built for running GrapheneOS in partnership with the project so that the hardware/firmware can be hardened too.
2
This Tweet was deleted by the Tweet author. Learn more
Show replies