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 threadGrapheneOS

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.

Aug 27, 2025 at 8:01pmWeb
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 threadGrapheneOSAug 27, 2025
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.
Show threadGrapheneOSAug 27, 2025
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.
Show threadPablo Majster Aug 27, 2025
@GrapheneOS Does this mean this will be the end of GrapheneOS support for Pixels?
Show threadGrapheneOSAug 27, 2025
@ppaluchowski64 Only if future Pixels stop meeting our requirements. We still plan to support them if they continue providing what we need including proper alternate OS support.
Show threadTomásAug 27, 2025

@GrapheneOS

"...alternative is a year or two away." sounds like you going into hardware industry or something more like switching Pixels for another devices?

I actually own a Pixel 8 with your SO and I love it. I don't want to mess swapping tbh but if that would be the case... I would do it another time when time arrives

TIA

Show threadGrapheneOSAug 27, 2025
@th0maswaschosen We'll still be supporting the already supported devices until their end-of-life which is 7 years from launch for the Pixel 8.
Show threadEmber Yuuki OrtizSep 12, 2025
@GrapheneOS @th0maswaschosen so uh how close is the pixel 6 to EOL?
Show threadTomásSep 12, 2025

@emberyo @GrapheneOS

There's a very good device table on Graphene's website with all the dates where they'll stop updating them, check it out

Show threadEmber Yuuki OrtizSep 12, 2025
@th0maswaschosen @GrapheneOS oh cool I didn't know could you link it here?
Show threadTomásSep 12, 2025

@emberyo

Sure!

https://grapheneos.org/faq#device-lifetime

There you go, if you need further information you can ask in the community section that corresponds to your question here:

https://grapheneos.org/contact#community

GrapheneOS Frequently Asked Questions

Answers to frequently asked questions about GrapheneOS.

GrapheneOS
Show threadEmber Yuuki OrtizSep 12, 2025
@th0maswaschosen thanks
Show threadGrapheneOSSep 12, 2025
@emberyo @th0maswaschosen It's in the https://grapheneos.org/faq#device-support section.
GrapheneOS Frequently Asked Questions

Answers to frequently asked questions about GrapheneOS.

GrapheneOS
Show threadChristianAug 27, 2025
@GrapheneOS Any idea when you’ll be sharing more details about the Graphene phone? I’d definitely prefer to support your project and get that device over a Pixel 10. However I'm planning to switch to GrapheneOS sooner or later.
Show threadGrapheneOSAug 27, 2025
@7l6dHJh7xq They'll be a future generation of existing mainstream phones with enhanced security and updates to meet our requirements in order to have official GrapheneOS support. It will likely be a year or two so it would be an alternative to the Pixel 11 or Pixel 12 rather than the Pixel 10. We aren't really sure how long it will take at this point.
Show threadDemi Marie ObenourAug 27, 2025
@GrapheneOS @7l6dHJh7xq Is there an estimate for when you will be able to talk about this?
Show threadmüdeAug 28, 2025
@alwayscurious They're already talking about it - at least the parts they can make public up until now. I am also looking forward to learning more!
Show threadDemi Marie ObenourAug 28, 2025
@vinzenz I meant “talk about more details”, but the answer is probably “can’t disclose that”.
Show threadKlarnameAug 27, 2025
@7l6dHJh7xq @GrapheneOS better sooner than later. I did with 9 Pro and its fantastic
Show threadxyhhx 🔻Aug 27, 2025
@GrapheneOS wait, you're working on official devices?? 👀
Show thread• ŁączeAug 27, 2025
@xyhhx Yes 🎉
Show threadGrapheneOSAug 28, 2025
@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.
Show threadxyhhx 🔻Aug 28, 2025
@GrapheneOS that's very exciting news
Show threadnanasahibAug 28, 2025
@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?
Show threadGrapheneOSAug 28, 2025
@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.
Show threadDanielAug 30, 2025
@GrapheneOS @nanasahib What is the targeted MSRP for this one?
Show threadastroboyAug 29, 2025
@GrapheneOS @xyhhx Is major Android OEM Samsung? I can't think of any other company.
Show threadDanielAug 30, 2025
@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
Show threadastroboyAug 30, 2025
@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?
Show threadDanielAug 30, 2025
@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...
Show threadGrapheneOSAug 30, 2025
@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.
Show threadastroboyAug 30, 2025
@GrapheneOS @DanielDNK @xyhhx Hmmm, does that mean you're teaming up with a Chinese OEM?
Show threadDanielAug 30, 2025

@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

Show threadGrapheneOSSep 22
@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.
Show threadMichaelAug 31, 2025

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

Show threadGrapheneOSAug 31, 2025
@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
Show threadGrapheneOSAug 31, 2025
@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.
Show threadMichaelAug 31, 2025

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

Show threadDanielSep 1, 2025
@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
Show threadGrapheneOSSep 1, 2025
@DanielDNK @mikeymop Nothing devices don't currently meet our requirements but we would be willing to work with them.
Show threadDanielSep 1, 2025
@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...
Show threadGrapheneOSSep 1, 2025
@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.
Show threadDanielSep 1, 2025
@GrapheneOS @mikeymop
What ?
You mean Murena ?
I never heard about Fairphone talking about GrapheneOS in this terms
Show threadGrapheneOSSep 1, 2025
@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.
Show threadBenSep 11, 2025
@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.
Show threadBenSep 11, 2025
@GrapheneOS I'm especially curious about the ChatGPT thing you mentioned and any other specifics about how Murena is privacy washing and what not.
Show threadGrapheneOSSep 11, 2025
@perksofbeingben See 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 threadDimitris ZervasAug 28, 2025
@GrapheneOS an almost related question: if the perfect device arrives with all the requirements that you want, is there any chance that contactless payments could be supported, or is that a purely software issue from googles side?
Show threadNiko4uAug 28, 2025
@dzervas
Contactless payment already works with some none google apps.
@GrapheneOS
Show threadGrapheneOSAug 28, 2025
@dzervas Curve Pay, PayPal and many European banking apps provide tap-to-pay support usable on GrapheneOS. Curve Pay is for the UK and European Economic Area. PayPal tap-to-pay is currently very region limited. Both Curve Pay and PayPal tap-to-pay will likely expand to the US and elsewhere.
Show threadGareth KitchenAug 28, 2025
@GrapheneOS
I hope Curve Pay can sort their web site out before that sort of expansion!

@dzervas
Show threadLamb_Borg_GenieAug 28, 2025
@GrapheneOS "since our alternative is a year or two away" Hell yeah, keep going brothers, stay strong. Love and highly appreciate the work you are doing and which benefits it provides to the community.
Show threadDanielAug 30, 2025
@GrapheneOS you will need to make your own phone really fast, Google is evil now and the US gov don't help (it is quite the opposite)
Show threadClutchK1ckSep 1, 2025

@GrapheneOS I'm still a bit confused about what extra work is required without Google publishing the device tree? Am I correct in the assumption that the driver binaries are still available, it's just a case of creating a device tree, the same/similar way it wasn't available for all devices starting Android 16?

Long time grapheneOS user by the way. All this is great news and I love where the project is going, I'll be setting up a monthly donation now.

Show threadGrapheneOSSep 1, 2025
@ClutchK1ck As part of migrating to Android 16 in June, we removed most of the AOSP device trees and ported the small remaining portion to Android 16. We're currently finishing this by removing nearly the entirety of the remaining device trees. We've replaced all of this with our own automation generating what we need from the combination of AOSP and the stock OS factory images. We already had this tooling prior to Android 16 but needed to greatly expand it and ship work we had in-progress.
Show threadadison verliceAug 27, 2025
@GrapheneOS can you use opentitan for a secure element?