@dalias @luana Our hardware requirements include supporting using verified boot and other features with non-GrapheneOS operating systems too:

https://grapheneos.org/faq#future-devices

> Verified boot key fingerprint for yellow boot state displayed with a secure hash (non-truncated SHA-256 or better)

That applies even if the device has official GrapheneOS support with green verified boot state. Green verified boot state isn't mandatory of course but we'd like to have it. It could differentiate with a better UI.

@greenpete That's about mobile device management software, not anything in GrapheneOS or relevant to it. It isn't relevant to the hardware, kernel, drivers or firmware. It's just an MDM app. Their MDM app could potentially supported being installed and used on GrapheneOS for companies which want to use it. Many companies want something like that to deploy fleets of GrapheneOS devices. We want to have our own open source one and maybe they're interested in that too.

@superblox There are essentially no European manufacturers. Their phones are white labelled Chinese ODM devices where they have little input into it. That stops them from meeting our requirements in practice unless the ODM happens to meet all of them on their own since the OEMs selling those devices don't get much input into the low-level development. They're stuck using the platforms which are available with surface level changes such as choosing a display and the enclosure design.

@gothiccard 2027

@Brokar @tuxicoman It's going to be the same GrapheneOS supporting additional devices with official support and collaboration from the OEM. They're going to benefit through selling many more devices and we get more high quality devices meeting our security requirements which we can properly support. It should also be a lot easier for us to support than Pixels because they're going to be helping us a lot. Most of the work still needs to be done, but it's a serious partnership already.

@43256bc0859462cf14fa7de594a48babdf189b91abe27f88d824abf69b2343c9 Their past and current generation (2026) devices won't be supported. It will be the next generation launching in 2027. You can look at the current Motorola Signature, Motorola razr fold and Motorola razr ultra for a basic idea of what the initially supported devices will resemble. Those 3 devices are close to meeting our requirements but weren't quite there yet and more time is needed. Perhaps if we started 6 months earlier.

@luana It will fully support using other operating systems including users making their own builds of GrapheneOS. It's part of our hardware requirements. We'll likely be able to make hardened builds of firmware and drivers which can be released in an official way for easy builds without needing to extract anything from the GrapheneOS or Motorola OS factory images.

@halfredgreenapple That's unrelated.

@blindcoder It will be 2027 so you might still want to buy an older Pixel to use GrapheneOS in the meantime.

@skywalker2k17 @alexia They're close but don't have hardware memory tagging usable in production and we aren't willing to lose it. It will be the next generation of those devices supporting GrapheneOS.