GrapheneOS Drops Pixel 11 Support Over Missing Security Feature

The GrapheneOS team has confirmed it will likely skip support for the Google Pixel 11 series, citing the absence of hardware memory tagging (MTE) support in the device's software, firmware, and hardware [1]. This decision marks a significant shift for the privacy-focused operating system, which has historically relied on Pixel devices as its primary hardware platform due to their robust security architecture [2].

The security gap

Memory tagging extensions (MTE) act as a critical defense against memory-safety bugs, which Google previously identified as the source of over 60% of "high severity" security vulnerabilities [1]. While MTE was an opt-in feature on previous devices starting with the Pixel 8, its apparent removal in the Pixel 11 series creates a security profile that does not meet the requirements for GrapheneOS [1]. The development team noted that while the Pixel 11 includes other upgrades—such as a Titan M3 chip and post-quantum secure verified boot—these additions do not compensate for the loss of MTE [1].

The move coincides with broader friction between Google and the custom ROM community. Developers have reported that Google recently replaced its public, automated kernel code distribution system with a manual request process [3]. This change has increased the time required to access necessary kernel files from hours to weeks, complicating the development pipeline for security-focused projects [3].

A shift toward Motorola

GrapheneOS developers are now signaling a pivot toward Motorola hardware for future support [1]. The team is currently working with Motorola to bring the operating system to its 2027 lineup of "slab" phones, which are expected to utilize Qualcomm’s Snapdragon 8 Elite chips [2].

The developers expressed a preference for the performance and component isolation of Snapdragon chips over Google’s proprietary Tensor hardware, which they characterized as a "sidegrade or downgrade" in certain respects [2]. While Motorola’s current offerings, such as the Razr series, are nearing the necessary security standards, the 2027 devices are expected to be the first to fully integrate the required secure element features [2].

What to watch

• Pixel 11a development: The GrapheneOS team remains hopeful that the upcoming Pixel 11a may include MTE if it shares more architectural DNA with the Pixel 10 generation [1].
• Motorola integration: Monitor the 2027 rollout of Motorola’s non-folding devices, which are slated to be the first to receive full GrapheneOS support outside of the Pixel ecosystem [2].
• Google's response: Whether Google provides official confirmation regarding the presence or absence of MTE in the Pixel 11 hardware remains an open question [1].

The exclusion of the Pixel 11 from the GrapheneOS ecosystem highlights a growing divergence between Google’s hardware strategy and the requirements of privacy-focused developers. As the barrier to entry for custom ROMs rises, the long-standing relationship between the Pixel line and the open-source security community faces its most significant challenge to date.