There’s no GrapheneOS for Pixel 11 phones, and the project says it isn’t a matter of needing more time. GrapheneOS confirmed on Mastodon that it could not finish a build for Google’s newest phones, because the Tensor G6 chip drops Memory Tagging Extension, the hardware security feature the project treats as a baseline requirement rather than a nice-to-have.
Why there’s no GrapheneOS for Pixel 11
MTE is an ARM chip feature, not a software patch. It tags every memory allocation and every pointer that touches it with a matching value, then checks the tags on each access. A mismatch usually means a use-after-free or buffer overflow bug is being exploited, and the chip kills the process on the spot instead of letting corrupted memory run. That catches a class of bugs that software-only mitigations can only guess at after the fact. GrapheneOS builds its entire threat model around having that hardware backstop, which is why losing it on one generation of Pixel isn’t a feature the team can quietly work around: without MTE, the phone doesn’t meet the bar GrapheneOS sets for itself.
Without MTE, GrapheneOS would have to ship the Pixel 11 with only the software-side mitigations every other Android build already runs. That’s not a compromise the project is willing to make quietly: it would mean shipping a phone under the GrapheneOS name without the memory-safety guarantee the name is supposed to signal. Refusing to ship is GrapheneOS holding the line on what it promises, rather than watering down the promise to cover a new device.
That’s a shift from how the relationship has worked until now. GrapheneOS builds on Pixel hardware because Pixel silicon has supported the security primitives the project needs, and the Pixel line has benefited from having a serious third-party ROM built for it. For now, GrapheneOS is telling people who want it to buy an older Pixel instead, and is looking at an unreleased Motorola flagship as an alternative platform going forward.
What the leaked documents add
The detail that turns this from a missing spec into a decision is the one Notebookcheck reported: leaked internal documents and bootloader analysis indicate Google had MTE support planned for the Tensor G6 and removed it before launch. That rules out the simplest explanation, that MTE support just wasn’t finished in time. If the leaked material holds up, Google built the feature and then took it back out.
We’ve been tracking the Pixel 11 line’s list of quiet trade-offs since launch, including the Pixel 11 Pro’s dimmer camera flash compared with last year’s phone. Losing MTE fits the same pattern: a regression that never shows up in a spec sheet comparison, and one that most buyers will never notice unless they were relying on GrapheneOS in the first place.
What to watch next
- Whether GrapheneOS confirms support for the Motorola flagship it’s now evaluating, and on what timeline.
- Whether Google responds to the leaked-documents report or explains why MTE was removed from the Tensor G6.
- Whether MTE returns on a future Tensor chip, which would reopen the door for GrapheneOS on Pixel hardware.
