News for hackers. Stuff that matters.
Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by grapheneos on Monday October 05, 2026 @08:52PM (#49972805)
The information in our linked post is accurate, doesn't have a poor signal-to-noise ratio and isn't emotional. It provides background information on the topic to explain the purpose of the feature and how it's used across iOS, the Pixel OS and GrapheneOS. We didn't roll back our statement. We provided more information as it became available including that it appears MTE may ship for the Pixel 11 in the future. There's no confirmation that it will ship and it may never be available for production use. Your post is misrepresenting what we said, how we said it and the situation for MTE with the Pixel 11.

Pixel 11 still doesn't have support for MTE and therefore doesn't meet our official security requirements. Pixel 11 isn't only missing support for it in the OS but rather also the firmware. An Android 17 QPR2 Beta 4 release was published for the Pixel 11 after we made our initial post which added partial support for MTE to the firmware. The Beta firmware still lacks support for everything needed by MTE OS integration including lacking a way for the OS to enable MTE itself. Instead, it has to be enabled via a fastboot mode command and can be disabled via another fastboot command even when the device is locked. It's only half-baked MTE integration for testing without OS support for it. It isn't known if the hardware MTE support works correctly. We've performed tests of the basic MTE functionality and performance but that isn't enough to rule out serious CPU errata.

Android 17 QPR1 is the latest major release of Android for Pixels and was published on September 15th for the Pixel 6 through Pixel 10a. It was cancelled for the Pixel 11 and still hasn't been published for those. The latest generation of Pixels is now behind on a major Android update and important security patches. Pixel 11 received an update to the 2026-09-01 security patch level in early September but then didn't receive the rest of the September 2026 security patches. Pixel 11 doesn't have the updated firmware, kernel, kernel drivers, userspace drivers and many HAL components for September 2026. That means serious publicly vulnerabilities haven't been patched. That's another blocker for it meeting our requirements. We need the update situation to be sorted out too.

Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by T1ny on Monday October 05, 2026 @09:45PM (#49973168)
I appreciate your engagement in every post I've seen on HN. I have installed GOS several times, and currently have a Pixel 11, so I am definitely invested in the outcome of this. I was tempted to go back P10, but haven't yet. Looking forward to the device next year.

Does most of the GOS team use GOS as a daily driver?

Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by grapheneos on Tuesday October 06, 2026 @01:12AM (#49974457)
Yes, nearly all the people working on it are using it as a daily driver.
Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by rickdeckard on Tuesday October 06, 2026 @03:30AM (#49975347)
First, I really appreciate what you guys are doing and it's angering me as well how Google stays silent on AOSP further and further. So please consider the following as well-intended observation:

At the core the post has accurate information, but the statements keep mixing discovered facts with emotional exaggerations, which creates the noise-element.

And this later forces you to roll back on parts of the statement. Not on the facts but on those speculations, which weakens the overall force of your statements.

For example, the journey of this post is:

  1. No MTE-support found: "It appears Google cut an important security feature to save money"
  2. MTE-support found: "It still has at least bare minimum support for MTE at a hardware level. We think they removed most of the hardware acceleration from the CPU cache to save money. They ruined the performance so it ended up being fully disabled in firmware.
  [..] We expect performance must be quite bad for Google to have decided to entirely strip out support for it"
  3. No observed reduction in performance: "Our own testing doesn't show a substantial reduction in performance so far."
The reason for this uncertainty is clear, Google is not communicating openly.

But jumping from facts straight to exaggerations and indirect accusations is not helping your cause, it's diluting the whole message.

--

> "Android 17 QPR1 is the latest major release of Android for Pixels"

You probably know that already, but the latest release seems to be QPR2 Beta 6 of one week ago, and includes the Pixel 11 series as supported devices [0].

[0] https://developer.android.com/about/versions/17/qpr2/get

Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by gib444 on Wednesday October 07, 2026 @09:51AM (#49992911)
There is no point trying to engage on this level; they don't engage in proper conversation. This comment will get flagged for pointing this out.
Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by DaSHacka on Thursday October 08, 2026 @05:31AM (#50003692)
Heh, well this is fittingly ironic.

Guess some things never change.

Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by rickdeckard on Thursday October 08, 2026 @06:08AM (#50003942)
Just noticed my comment indeed got flagged.

Don't know why, it was really meant in good faith, but okay...