zlacker

This list always bugged me. If Pixel - for example - starts to introduce security patches slower, they will change this list... or even ignore it. If something more secure comes into the picture, they will change this list, and they will ditch supporting Pixel. If they don't, then it will be quite obvious, that they formed this list only to meet only Pixel's feature list. Also Google can obviously satisfy this list more easily, than any other company, so basically they created a moot for them.

>>ruszki+(OP)
We haven't removed any requirements from our list. Many things Pixels provide are omitted from the list in order to enable another device to meet our requirements. There are other devices meeting the security feature requirements, but they don't allow us to support them. We're actively working with a major Android OEM towards a subset of their devices meeting these requirements and providing official GrapheneOS support. Providing the requirements on our list is not easier for Google and any OEM should be able to make a Snapdragon device meeting these requirements in 2026. It's already possible to meet all the listed requirements via multiple non-Snapdragon SoC platforms, but we'd prefer the upcoming Snapdragon generation with MTE support. The list has been deliberately kept limited to what is provided elsewhere than Pixels so that other devices can meet the requirements, which is in the process of happening.