We've received the Pixel 10 we ordered and have confirmed it supports unlocking, flashing another verified boot key and locking again.

Our Pixel 10 support will likely only be possible to complete after we finish porting to Android 16 QPR1 which is being released in September.

A second Pixel 10 we ordered has arrived at a package forwarding service in the US to be shipped to a country without Pixels available.

We'll order a Pixel 10 Pro (XL) and Pixel 10 Pro Fold for our main device testing farm today too since we'll supporting all 4 variants of them.

Previously, we likely would have been able to implement support for the Pixel 10, Pixel 10 Pro and Pixel 10 Pro XL in the next 48 hours. However, we likely need to wait for Android 16 QPR1 and our port to it since we don't expect a Pixel 10 device branch will be pushed to AOSP.
We've received confirmation that Android is switching to having quarterly releases across devices. There will be 3 quarterly and 1 yearly release of Android and the Android Open Source Project. Monthly releases are Pixel exclusive and will have far fewer changes than before.
Previously, only Pixels shipped the quarterly releases in practice. Other OEMs will now be pushed to ship those, but not the monthly releases which are now officially Pixel exclusive. Please note monthly Android Security Bulletins are a different thing from the monthly releases.
Android Security Bulletins are backports of a subset of patches deemed High/Critical severity to older Android releases. That currently means the initial yearly releases of Android 13, 14, 15 and 16 without the monthly/quarterly updates for those. This will need to change now.
The changes are acceptable for us and we can deal with it. We're currently working with a major OEM towards future generations of their devices meeting our requirements and providing official GrapheneOS support. GrapheneOS on both Pixels and these future non-Pixels will be fine.
Pixels are still the most secure Android devices and the only ones combining a high level of security with proper support for an alternate OS. However, it's clear they don't value alternate OS support and won't remain the best devices for GrapheneOS once we have official ones.
We could continue supporting future Pixels such as the Pixel 11 and Pixel 12 after we have another option available but we won't depend on them continuing to provide alternate OS support. It's good that the Pixel 10 still provides it since our alternative is a year or two away.
@GrapheneOS wait, you're working on official devices?? 👀
@xyhhx We're working on GrapheneOS support for future generations of a subset of the device models provided by a major Android OEM. Their current devices don't provide the updates and security features we need, but they're capable of doing it. We're working with them towards providing this so we can support their devices. They may end up officially selling devices with GrapheneOS as an option but that's not the bare minimum and it can be successful even without initially having that.
@GrapheneOS if grapheneos really goes down the route of supporting alternative hardware manufacturer any chance a smaller (6.1 inches or less) phone can be picked for support as well?
@nanasahib If there's a variant of those able to meet our requirements. The initial devices will need to be flagships for better updates and security features and those tend to be larger so that's what you should expect.
@GrapheneOS @nanasahib What is the targeted MSRP for this one?
@GrapheneOS @xyhhx Is major Android OEM Samsung? I can't think of any other company.
@astroboy @GrapheneOS @xyhhx on one side they close the bootloader, on the other side they are working with a little ROM supplier, it make no sense
@DanielDNK @GrapheneOS @xyhhx Yeah, good point. But I just don't know any other "major Android OEM" that would fit the purpose. I don't believe they would work with a chinese OEM, right?
@astroboy @GrapheneOS @xyhhx it's eliminate Motorola, Lenovo, Xiaomi, Oppo, Vivo, Huawei, Oneplus, Realme, ZTE, Lenovo
I agree, not sure we can trust a CCP phone as a secure phone. But Taiwanese phone...
@astroboy @DanielDNK @xyhhx Nearly all phones are either made in China or use a bunch of important components from there. iPhones and Pixels are made in China. It's unavoidable in practice and people would complain about a phone made in the US too.
@GrapheneOS @DanielDNK @xyhhx Hmmm, does that mean you're teaming up with a Chinese OEM?

@GrapheneOS @astroboy @xyhhx it could be made in China but with a western design and a western control over the production to avoid the introduction of CCP backdoors like they use to with the national brand sold to China citizens (and for Western citizen too? Just regarding what US did to spy the world tell us a lot about what a state can do do to introduce backdoors in the hardware and the software).

So not sure I can trust a Chinese brand when we talk about hardening a phone

@astroboy @xyhhx There are a bunch of major Android OEMs making Snapdragon devices. Snapdragon 8 Elite Gen 5 is expected to meet our requirements. It should have working MTE support but it's not clear how much work it will be to set it up and get it working smoothly for production usage. MTE has found a LOT of bugs for the drivers and other device support components on Pixels both through Google's own internal testing and our much broader usage of it deployed in production since Oct 2023.

@GrapheneOS I'm really hoping for a situation where Graphene works with Fairphone to make a viable 1st party Graphene phone.

That would meet both the privacy and repairability / longevity needs I feel many are looking for.

I understand Fairphone currently is very far from meeting the requirements, but one can hope that expressing this at least gets them on the radar.

@mikeymop Fairphone's devices have atrocious security and are very far from meeting our hardware requirements. They very clearly do not prioritize security and also have negligible engineering resources with nearly everything done by their ODM. You should read https://discuss.grapheneos.org/d/24134-devices-lacking-standard-privacysecurity-patches-and-protections-arent-private. They're definitely not a reasonable choice for GrapheneOS support. The marketing claims for their devices for long term support and updates aren't at all accurate. They already have an incompatible partnership too.
Devices lacking standard privacy/security patches and protections aren't private - GrapheneOS Discussion Forum

GrapheneOS discussion forum

GrapheneOS Discussion Forum
@mikeymop Murena are blatant scammers pushing an extraordinarily insecure/non-private OS and services as something they're not. They're heavily invested into spreading misinformation about GrapheneOS and attacking our project/team. We won't work with a company that's partnered with Murena, who are in fact enemies of privacy and security to the point they secretly send user data to OpenAI and act as if that's a private service better than Apple doing it locally. Their products are truly scams.

@GrapheneOS I knew about Fairphone's security shortcomings thanks to y'all but wasn't sure as to whether it was the result of neglect or the result of just not knowing any better.

While I was already wary of Murena, I didn't know they were so hostile towards Graphene. I am sorry Graphene's team has had to combat toxicity from them.

Unfortunate, as the idea of the FP hardware is attractive. Regardless of who makes it, I do look forward to a 1st party device, and I wish your team success on it.

@GrapheneOS @mikeymop so a Nothing phone with gos is definitely excluded for the same reason
It let us mainly Chinese brand or Volla for the future of GOS after the Pixel
@DanielDNK @mikeymop Nothing devices don't currently meet our requirements but we would be willing to work with them.
@GrapheneOS @mikeymop FYI they did partnership with Murena to be able to sell brand new CMF phone with /e/OS on it but buy it cheaper than the retail price and keep the Nothing warranty. They are a special reseller with a specific partnership like Fairphone is to let them access to brand new phones for less than the MSRP...
@DanielDNK @mikeymop Selling them devices at a bulk rate isn't really a partnership. That's nothing like Fairphone spreading misinformation for them and participating in their attacks on GrapheneOS.
@GrapheneOS @mikeymop
What ?
You mean Murena ?
I never heard about Fairphone talking about GrapheneOS in this terms
@DanielDNK @mikeymop Fairphone has explicitly supported them in doing it. We made a post debunking misinformation from Murena and Fairphone responded to it with a corporate speak response lacking substance. Murena responded with a bunch of misdirection and misinformation. Fairphone helped mislead people into believing that through their response supporting Murena. Fairphone did that after the CEO of Murena had personally targeted our founder and encouraged harassment, which our post addressed.
@GrapheneOS I heard about this and read some of the posts, but didn't realize it had escalated so much or that Fairphone had gotten involved! 😳 Would you mind sharing links or other resources so I can do more research on this? I'd really like to be as informed as possible because I've been rooting for Fairphone, but now I'm skeptical. I'd also like to see more of the stuff from Murena because I only heard about the initial post from them.
@GrapheneOS I'm especially curious about the ChatGPT thing you mentioned and any other specifics about how Murena is privacy washing and what not.
Devices lacking standard privacy/security patches and protections aren't private - GrapheneOS Discussion Forum

GrapheneOS discussion forum

GrapheneOS Discussion Forum

@perksofbeingben Not ChatGPT but rather OpenAI's speech-to-text service instead of doing it locally. In fact, OpenAI themselves has perfectly good models for running locally on the device.

See https://discuss.grapheneos.org/d/24134-devices-lacking-standard-privacysecurity-patches-and-protections-arent-private where we provided a link about this and other things.

Devices lacking standard privacy/security patches and protections aren't private - GrapheneOS Discussion Forum

GrapheneOS discussion forum

GrapheneOS Discussion Forum
Devices lacking standard privacy/security patches and protections aren't private - GrapheneOS Discussion Forum

GrapheneOS discussion forum

GrapheneOS Discussion Forum