Pixel 11 encountered an obstacle to GrapheneOS support: the developers stated that they could not complete the porting due to insufficient support for ARM Memory Tagging Extension (MTE) in software and firmware. After a week of work, the team obtained a partial adaptation of the system and proposed the exclusion of the series. However, he did not announce a final decision.
The problem concerns a protection that GrapheneOS considers central to its architecture. In the official communication, the project explains to use MTE in the kernel and base system processeswith temporary deactivations limited to some device-specific processes. According to the developers, this coverage significantly increases resistance to almost all remote exploits and numerous local attacks.
The practical consequence concerns those who buy a smartphone specifically to install GrapheneOS. The team has purchasing the Pixel 11 is not recommended and listed the Pixel 8, 9, and 10 as preferable options for the overall security offered with their system. The judgment therefore concerns a precise use of the device, in which the availability of MTE weighs more than the improvements introduced in other components.
The technical reference starts from Pixel 8, arrived in October 2023 with hardware support for MTE. GrapheneOS recalls integrating the technology into its hardened_malloc allocator and extending its use to the system in the same month. According to the project, Android and the standard Pixel software have not adopted it as active protection by default across the entire system: the advanced protection mode of Android 16 enables it for some processes.
Because other protections don’t solve the problem
The difference also involves the user-installed apps. GrapheneOS automatically enables MTE for a broader set of applications and allows you to force its use through a setting, leaving the option to disable it for individual incompatible apps. The team contrasts this choice with the approach of Android Advanced Protection and Apple Memory Integrity Enforcement, which require explicit developer opt-in for installed applications.
Pixel 11 however introduces progress that the project itself recognizes. The communication mentions the startup verified with ML-DSA, resistant to quantum attacksand replacing Samsung Shannon IMS with AOSP IMS. Added to these is Titan M3, from which the developers expect greater resistance to data extraction before the first unlock, the condition referred to as Before First Unlock (BFU).
They are advantages that protect different aspects. In evaluating GrapheneOS, the improvement expected from Titan M3especially for those who do not use a strong passphrase, does not compensate for the loss of the defenses offered by MTE after the first unlock, in the After First Unlock (AFU) state. Therefore, what counts is the coverage that the system actually manages to use, not the number of new security functions declared.
The project also considers focusing work on future devices developed through the collaboration with Motorola. The goal includes better management of firmware and driver updates, for which GrapheneOS still depends on the manufacturer, and faster transition to new kernel branches. In the message, the team leaves the choice open on the Pixel 11: partial porting does not equate to a guarantee of support.
