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 Any reason you cannot try to support 10 series based on current build?

@DugganJared The current stock OS is based on code closer to Android 16 QPR1 than Android 16. We could try to support it with Android 16 but there will likely be massive issues with it due to the firmware and driver code being for a newer revision. We need Android 16 QPR1 to do it properly.

@GrapheneOS Do you support a flip phone?

@idare Pixel 9 Fold Pro and Pixel Fold are supported. There isn't a vertically folding phone supported yet since there isn't one meeting our hardware requirements yet. Pixels are currently the only devices providing the necessary security features and updates with alternate OS support.

@GrapheneOS Thank you devs! My gut tells me the OEM is @punkt as they are currently using a non-official GOS and the tweets keep saying new OEM will have “official” GOS support 🤔

@letitrest @punkt We said that it's a major OEM, not a small company. Punkt has no devices running GrapheneOS. They have a fork of Android 13 with some LineageOS and GrapheneOS changes. GrapheneOS is solely based on Android 16. Using portions of our code doesn't make something a GrapheneOS device.

@GrapheneOS How is GrapheneOS on foldables and will it eventually work with the 10 fold?

@Ian_Costa18 Folding devices are fully supported and it works as well as the stock OS. There's one known quirk of the boot animation only appearing on the inner screen but that's all and it's simply not a high priority for us to change it. Will likely be fixed with a fancier boot animation.

@GrapheneOS You need to collaborate with the manufacturer in China and make your own hardware. How long you will remain dependent on google

@Prateek42354333 Read the thread. https://x.com/GrapheneOS/statu...

@GrapheneOS Collaborate with @Fairphone 💚

@patryk_karter Their devices are far from meeting our security requirements and it's very clearly not a priority for them. They already have a partnership with a company selling supposedly private devices not providing basic privacy and security. Not compatible with us. https://discuss.grapheneos.org...

@GrapheneOS With Google soon requiring developer identity verification to sideload apps on certified Android, will side loading on GrapheneOS devices be affected; especially when in sandboxed Play Services?

@CrypticTac It doesn't impact GrapheneOS or sandboxed Google Play.

@GrapheneOS Do you have any plans to release it for other phones besides Pixel?

@gxfernandess There are no other phones available meeting the security and update requirements while supporting using another OS. See https://x.com/GrapheneOS/statu... though.

@GrapheneOS Will there be smartphones that actually come with @GrapheneOS

@NTurtle34396 That's a goal but it's not a requirement for it to be a success.