▲ | pferde 6 days ago | |||||||||||||||||||||||||||||||||||||||||||
There is no single biggest thing. GrapheneOS has a rather strict demands for a device they're willing to support, see https://grapheneos.org/faq#future-devices | ||||||||||||||||||||||||||||||||||||||||||||
▲ | close04 5 days ago | parent [-] | |||||||||||||||||||||||||||||||||||||||||||
GrapheneOS doesn't support Pixels with locked bootloader. It's where the game stops for all locked phones, a common practice now. You can already see how this is the single biggest thing. The second big thing is that the "non-exhaustive list of requirements" is basically "whatever new Pixels do". Your conclusion that Pixel phones are "the only ones with secure enough hardware" is overstretching what's happening here. The developers took the Pixel as a template because it's a well selling line, with good security, and generally with unlocked bootloader, and modelled the requirements based on it. It's a reasonable approach to the development of a niche security oriented OS because: "In order to support a device, the appropriate resources also need to be available and dedicated towards it". It has the downside that it makes it sound like no other phone has comparable security features. Are the fully supported Pixel 6/6a more secure than any other non-Pixel phone sold on the market today? | ||||||||||||||||||||||||||||||||||||||||||||
|