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.
Replies (13)
That's good news for once.
Why did you stop. From a guy that is wanting to start.
You all are amazing! Thank you!
I love GrapheneOS! Can u add lightning as a donate option pls?
GrapheneOS Foundation plans to add one eventually but need to do it a particular way including making sure we can follow accounting/auditing rules for the foundation.
I have a lightning address on my page, I then offramp sats to the foundation with my own fiat equivalents and spend the sats most of the time.
You the best 👑
Great summary, thank you for the insights.
I really appreciate your work and efforts, you guys are amazing 🔥🤝
Simple bolt 12 address would make it more private for the donators very easily?
Thank you for the amazing work.
I'm glad to hear there are plans for something other than Pixels.
Does Google's hostility mean less of a future for AOSP-based OS's, even if there are devices for them? Will we need to be investing in Linux phones not based on Android?
#V4V
Final
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.
View quoted note →
