GrapheneOS, the security-hardened Android build that has run on Google’s Pixel phones for years, says it has hit a wall on the Pixel 11. In a thread posted to its official Mastodon account on 29 August, the project said it had a partial port running after a week of work but could not finish it, because the new Tensor chip appears to have dropped ARM’s hardware memory tagging support “in software, firmware and near certainly hardware.” The project’s blunt conclusion for anyone shopping right now: buy a Pixel 10 instead.
What memory tagging does, and why the Pixel 11 losing it matters
Memory Tagging Extension (MTE) is an ARM hardware feature that tags chunks of memory and traps code that reads or writes outside what it was allocated. It exists to catch memory-safety bugs — the category Google itself said in 2022 accounted for more than 60% of high-severity vulnerabilities it tracked, a figure Android Authority cites in its own coverage of this story.
The Pixel 8 shipped with MTE in October 2023, and every Pixel since has carried it. On stock Pixel software it has stayed largely dormant — an option buried in developer settings, switched on for a handful of processes when you enable Advanced Protection Mode. GrapheneOS uses it far more aggressively: across the kernel and effectively every base OS process, plus a per-app toggle users can flip on for anything they install. Take the hardware away and that entire layer goes with it. As GrapheneOS puts it, losing MTE guts security once the phone has been unlocked.
The project’s own buying advice
GrapheneOS is not hedging on the recommendation:
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. Pixel 11’s Titan M3 should improve BFU security for users without a strong passphrase, but losing MTE craters AFU security.
— the GrapheneOS project’s official Mastodon account, 29 August 2026
It is worth being precise about the scope here. This is advice for people who intend to run GrapheneOS, not a blanket verdict on the Pixel 11 as a phone. The project openly credits the Pixel 11 with real security gains — post-quantum verified boot using ML-DSA, a switch from Samsung’s Shannon IMS stack to AOSP’s, and a Titan M3 that should make a stolen, powered-off phone harder to extract data from. Its position is simply that none of that compensates for the missing feature it built its own defences around.
If you have already bought one
The project pointed buyers at Google’s own returns policy, which allows most Google Store purchases to be sent back within 15 days of delivery — a window that is still open for anyone who ordered near launch. For used-market shoppers on a budget, GrapheneOS suggests a second-hand Pixel 8a, which launched with a seven-year support commitment and still has most of it left.
There is a US-specific catch worth knowing before you swap devices: GrapheneOS notes that Verizon-branded Pixels cannot be used to install another operating system at all, because Verizon does not permit bootloader unlocking. It says T-Mobile does eventually allow it. Being carrier-unlocked for network purposes is not the same thing, and buying the wrong variant is an expensive mistake to discover after the fact.
What is confirmed and what is not
The missing MTE support is GrapheneOS’s own finding from its own port attempt, not something Google has stated. Android Authority says it has asked Google to confirm whether the Pixel 11 supports MTE and will update its article if the company responds; no answer from Google appears in the reporting so far. The project’s added line that “it appears Google cut an important security feature to save money” is explicitly its own inference — it estimates MTE’s tags need roughly 3.125% of extra cache space, and reasons that trimming that saves a small amount of die area per chip. As of 30 August, no official Google statement on the reasoning has surfaced, and the motive is not something anyone outside the company can confirm.
As for what GrapheneOS does next, it says it may skip the Pixel 11 generation entirely and put its effort into the Motorola hardware it has already committed to supporting — a plan we covered when the project set out its Motorola roadmap. It is also hoping the Pixel 11a follows the Pixel 10a’s pattern of reusing the previous generation’s chip, which would quietly hand MTE back.
Sources: GrapheneOS on Mastodon, Android Authority
