GrapheneOSAug 27, 2025

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.

Show threadGrapheneOSAug 27, 2025

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.

Show threadGrapheneOSAug 27, 2025
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.
Show threadGrapheneOSAug 27, 2025
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.
Show threadGrapheneOSAug 27, 2025
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.
Show threadGrapheneOSAug 27, 2025
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.
Show threadGrapheneOSAug 27, 2025
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.
Show threadconfettiarenasabotage
@GrapheneOS
People do you want to bet/guess which will be the OEM, for the fun? 😆
I think I can only put 4 options -_-
If you think it is another, say which one.
It seems I can't answer to my own polls, but I think it is Motorola or maybe Nothing.
HMD (Nokia)
25%
Nothing
12.5%
Motorola
37.5%
Samsung
25%
Poll ended at .
Aug 28, 2025 at 6:24amWeb
Show threadLukasAug 28, 2025
@Canning1452 @GrapheneOS Imho Nothing are too proud of their OS to work with GrapheneOS, they don't want users to flee the Nothing Experience. Also, Samsung is locking down everything (no more OEM unlocking on some of their recent phones), they don't look open to this kind of things.
Fairphone would be a better guess imo. Even if they already have /e/os, it proves they are open to alternative OS.
Otherwise Nokia, Sony and Motorola could do this too. They are not popular nor trendy in any way.
Show threadconfettiarenasabotageAug 28, 2025
@lukas_moinet @GrapheneOS
Good points for Nothing.
I agree for Samsung yes. They could change their approach to alternative OS though 🤷
GrapheneOS said multiple times Fairphone is very far from meeting their requirements, don't have a good update policy and don't seem interested in getting better.
I think that it is most likely Motorola (((or Nokia))).
Show threadLukasAug 28, 2025
@Canning1452 @GrapheneOS
I'm not sure for Samsung, it is not the Korean vibe I think, but we can still hope for the best.
It seems like you're right about Fairphone, they must have a lot of work to do before it happens.
We've seen "special" things commimg out of Motorola's labs, maybe it is them 🤔
Show threadGrapheneOSAug 28, 2025
@lukas_moinet @Canning1452 Fairphone isn't capable of meeting our requirements and handles security poorly. They barely do engineering themselves, it's done for them by their ODM. Their partnership with Murena is also a major issue. Recommend reading https://discuss.grapheneos.org/d/24134-devices-lacking-standard-privacysecurity-patches-and-protections-arent-private.
Devices lacking standard privacy/security patches and protections aren't private - GrapheneOS Discussion Forum

GrapheneOS discussion forum

GrapheneOS Discussion Forum
Show threadLukasAug 28, 2025
@GrapheneOS @Canning1452
I read most of this but it was a bit overwhelming because english is not my first language 😅
Thus I thought you could kinda "fix" how they do things, I must be wrong then