Pixel 11 and GrapheneOS: why the project says buy a Pixel 10 instead
GrapheneOS has a partial Pixel 11 port but won't ship it: memory tagging (MTE) is switched off. What that means if you're buying a Pixel for GrapheneOS now.
For six years the rule was simple: a new Pixel comes out, and a few weeks later it runs GrapheneOS. The Pixel 11 broke that rule. As of October 14, 2026, the Pixel 11 series is not on GrapheneOS’s list of supported devices, and the project has told people not to buy one if GrapheneOS is the plan. Here is what happened, what the project has said since, and what to buy instead.
What GrapheneOS said about the Pixel 11
On August 29, a week into porting work, GrapheneOS posted that it had a partial port of the Pixel 11 series but could not finish it, because ARM hardware memory tagging (MTE) was missing in software, firmware and “near certainly hardware.” The same thread was blunt about buying advice:
“We strongly recommend against buying Pixel 11 devices. Pixel 8, 9 and 10 have much better overall security for GrapheneOS. Pixel 10 is cheaper with similar hardware and MTE.” (GrapheneOS, Aug 29)
The project wasn’t one-sided about it. It noted real improvements in the new phones, including the Titan M3 security chip, which it said should improve security before first unlock for people without a strong passphrase. Its verdict was that losing MTE “craters” security after first unlock, which is the state most phones are in most of the day.
Why memory tagging matters this much
Memory tagging is a hardware feature in recent ARM chips that catches whole classes of memory-corruption bugs, the kind most real-world phone exploits rely on. GrapheneOS turns it on across the operating system and for apps through its hardened memory allocator, and it treats MTE as a core requirement for any phone it supports. The Pixel 8 was the first phone where that was possible, and it’s a big part of why GrapheneOS recommends 8th-generation Pixels or newer.
A Pixel 11 without working MTE would, in the project’s view, be a step backwards from the Pixel 10 it replaces, even with a newer chip and a newer security element.
The partial walk-back: MTE is in the hardware after all
On September 1, GrapheneOS posted “good news about the Pixel 11”: the hardware still has at least bare-minimum support for memory tagging. The project’s reading is that Google removed most of the hardware acceleration for it, performance suffered, and the feature ended up fully disabled in firmware (GrapheneOS, Sep 1). Android 17 QPR2 Beta 4 then added firmware support back, which makes the hardware usable again in principle.
By September 29 the position was this: Android 17 QPR2 is expected in December 2026 and “will hopefully provide what we need to support the Pixel 11 series.” Until then, the project says its priority is finishing support for its upcoming Motorola flagship, and it can “circle back and finish Pixel 11 support if they ship working MTE” (GrapheneOS, Sep 29).
So the honest status is not supported, maybe later. Nobody outside Google knows whether the December firmware will deliver tagging that works well enough, and GrapheneOS has said it needs to know a port will work before it commits to official support.
Get the next guide in your inbox
One email a week: new degoogling guides, OS and device-support news that matters, and one privacy fix you can do in five minutes. No tracking pixels.
What this means if you’re buying a phone for GrapheneOS
- Don’t buy a Pixel 11 for GrapheneOS today. You’d be buying a phone the project may never support. If it does arrive, you can switch then; the Pixel 11 won’t get cheaper by waiting for nothing.
- The Pixel 10 is the current flagship pick. It has MTE, it’s on the official list, and Google promises updates until August 2032. See our Pixel 10 GrapheneOS update runway story for the full support-end table.
- The Pixel 9a is still the value pick. Official support, updates to April 2032, and a midrange price. Our Pixel 9a specs and install page walks through the 20-minute browser install.
- Already on a Pixel 6? Google’s guaranteed support for the Pixel 6 and 6 Pro ends this month (October 2026). A Pixel 10 or 9a is the upgrade with the longest runway.
- Already own a Pixel 11? Keep it on the stock OS for now, follow our no-flashing degoogle guide, and watch for GrapheneOS’s December update.
Existing Pixels aren’t affected
The Pixel 11 situation set off speculation that GrapheneOS was leaving Pixels behind. The project shut that down on October 11: “Nothing is changing about GrapheneOS support for Pixels. Those will be supported until after end-of-life as has always been made clear from the beginning.” Every model from the Pixel 6 through the Pixel 10a is on the current release, 2026100600, per the GrapheneOS releases page.
The Pixel 11 story is part of a wider shift. GrapheneOS has said Pixels “have become increasingly difficult to support,” and it is now working with Motorola on its first non-Pixel phone, which we cover in a separate story.
The short version
- Pixel 11: not supported by GrapheneOS as of October 14, 2026. Possible after Android 17 QPR2 in December, with no promise.
- Why: memory tagging (MTE), a core GrapheneOS requirement, is disabled on the Pixel 11 in firmware.
- Buy instead: Pixel 10 (updates to 2032) or Pixel 9a (updates to April 2032).
- Pixel 6–10a owners: nothing changes; support continues as documented.
German tech site heise has an independent write-up of the Pixel 11 porting problems if you want a second source. We’ll update this story when GrapheneOS changes the Pixel 11’s status.
Check Pixel 10 prices on Amazon
affiliate link — same price for you, small commission for us