@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.

@956b3e034b1b81a0483f5f69a9071e7eb5c1f434246028a52acd0809482e0d0d We plan to support the Pixel 10a (we ordered one) and future Pixels.

@dado No, Google supporting GrapheneOS for the Play Integrity API would be an entirely separate thing.

@a53bdb We knew you weren't saying that but that's the answer we have for people who are.

@Guillotine_Jones You'll need a new device since their current devices and upcoming 2026 devices don't meet our requirements. It will be 2027.

@182052d256f486269994e4ff65c5d2601109f874fdfb373d113e72fbe48c3d7a 2027 if you're waiting for this.

@lumi @alexia GrapheneOS and the Android Open Source Project are Linux distributions. We strongly disagree with the premise that glibc, systemd and GNOME are preferable to the much more private and secure AOSP software stack. Moving to the desktop software stack would be a huge regression for nearly everything we care about and focus on improving. It's already possible to run desktop Linux apps in GrapheneOS including GUI apps via the hardware virtualization support and there's a desktop mode.

@lumi GrapheneOS is based on the Android Open Source Project which doesn't have Google apps and doesn't use their regular services. It only uses Google as a provider for very basic standard services which we replaced in GrapheneOS.

The purpose of GrapheneOS isn't specifically avoiding Google apps and services but rather providing a high level of privacy and security in general. Using Pixels is not in any way counter to our goals. We want official OEM support, lower level hardening, etc. though.

@a53bdb We'll continue to have Pixels as an option.

@BoloMKXXVIII The analytics feature is for their mobile device management system and their own operating system, not GrapheneOS. GrapheneOS is a separate thing from their operating system. They're both adding official support for GrapheneOS and using a small subset of GrapheneOS features to improve their own operating system. They could add support to GrapheneOS to their MDM but that wouldn't involve us adding any invasive integration for it in GrapheneOS. We wouldn't do something like that.

@katzenberger It will start with flagship devices but their flagships tend to be priced cheaper than flagship Pixels. More devices will be supported over time. It should be expected it will start with only flagships though. Look at the Motorola Signature (2026) and Motorola Razr Fold (2026) for an idea of the kind of future devices it would start out supporting.