News for hackers. Stuff that matters.
Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by rickdeckard on Monday October 05, 2026 @09:33AM (#49964683)
Quite a bad signal-to-noise ratio in this link.

It's an emotional discussion about Google not supporting MTE on Pixel 11 (old news of August, GrapheneOS had to roll back that statement in September [0]).

Now the question is whether MTE will be enabled by Google as part of a future OS-upgrade, to which there is no definite answer AFAIK

[0] https://news.ycombinator.com/item?id=49536384

Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by Luker88 on Monday October 05, 2026 @10:24AM (#49965321)
> Now the question is whether MTE will be enabled by Google as part of a future OS-upgrade, to which there is no definite answer AFAIK

Still means that currently the phone has no support for MTE.

I have bought too many things on vague promises that did not happen.

It's not there now -> it's not supported. EOL.

Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by JacobKfromIRC on Monday October 05, 2026 @12:34PM (#49967069)
Why are we dependent on Google to enable MTE on the OS-side? If it's a hardware feature, why couldn't GrapheneOS enable it in GrapheneOS even if Google's OS wouldn't enable it?
Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by HybridStatAnim8 on Monday October 05, 2026 @07:20PM (#49972102)
Because google may have disabled it due to issues/errata. Google willing to enable it is a good sign it is fine, and at worst, affects stock OS as well. Google isnt answering GrapheneOS when they ask why it was disabled, so GrapheneOS cannot know if the implementation is acceptable or not.
Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by grapheneos on Tuesday October 06, 2026 @01:36AM (#49974608)
GrapheneOS used MTE long before Google made a very limited form of it available as an opt-in feature via Android Advanced Protection Mode. Pixel 11 shipped without support for MTE available to the OS and still doesn't have that with the production firmware. It's only available with the Android 17 QPR2 firmware. It needs to have hardware and firmware support for it for GrapheneOS to use it. We also need to know it's fully functional.
Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by croes on Monday October 05, 2026 @10:27AM (#49965351)
> 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. It may still be usable.

MTE but slow

Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by rickdeckard on Monday October 05, 2026 @11:27AM (#49966128)
"We think", followed by a quite fueled accusation.

It has no MTE right now, okay. Is there any evidence on the rest?

Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by warkdarrior on Monday October 05, 2026 @07:32PM (#49972189)
Dude, we know Google is out to get us, all of us. Start from there and everything else follows.
Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by grapheneos on Monday October 05, 2026 @09:08PM (#49972916)
The information we provided in our post about MTE is accurate. Pixel 11 does not support MTE in either firmware or software. It's not known to what extent it's supported in hardware beyond that it appears to work fine with the partial MTE support in the Beta firmware. The Beta firmware wasn't yet available when we made our post and still lacks the full set of functionality. It's enough for testing it which we've done. It would be possible for GrapheneOS to use it if it ships in December 2026 as part of Android 17 QPR2 but it isn't known that it will happen. We would need to work around the incomplete support for it which is clearly only meant for testing.

Google has gone through years of cost cutting via mass layoffs, buyouts and driving away many employees through ending remote work. It's not due to any shortage of money but rather maximizing profit at the expense of overall quality and security. Android has been heavily impacted by the cost cutting, especially the security team. There's a very visible impact through less frequent security updates, missed updates for Pixels including Android 17 QPR1 not shipping for the Pixel 11. If the reason for MTE not being available at launch is that they lacked resources to get a small amount of work done on the firmware and software to provide it, then that would heavily reinforce our point.

There has been news reporting with leaks showing they planned to cut MTE support to reduce the die size and save money but we don't think that's relevant yet. The cores aren't yet the planned custom cores and hopefully they'll have reversed the decision by then after seeing Apple's launch of MTE integration. Their leaked plans to remove it at a hardware level predate Apple's integration being publicly announced.

Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by grapheneos on Monday October 05, 2026 @08:52PM (#49972807)
Pixel 11 still has no support for MTE. Our original post is accurate and the information is still relevant. A release of Android 17 QPR2 Beta 4 for the Pixel 11 shipped after we made our post. It did not invalidate our post and what we said remains accurate. It added partial firmware support for MTE which shows there's hardware support for it. That was a possibility covered by our original post.

Pixel 11 still doesn't have software or firmware support for MTE. It only has a Beta release of the firmware with incomplete firmware support for it. It isn't clear if it has fully working hardware support. Our hope is that it does and that we can support it in December 2026. We could likely get the incomplete firmware support working for what we need but it wouldn't be ideal and we would have no guarantee it would not be removed in a future update. We don't yet know that there's nothing known to be wrong with the hardware support which could be why MTE is unavailable.

Since then, the Pixel 11 has also missed the update to Android 17 QPR1 and doesn't have the 2026-09-05 patch level due to not receiving the September 2026 updates to the firmware, kernel, kernel drivers, userspace drivers and many HAL components for September 2026. That's a serious problem itself. The update situation needs to be sorted out in addition to full support for MTE being added to the firmware.

Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by gib444 on Monday October 05, 2026 @09:51AM (#49964923)
I wonder what the comms would have been without the Motorola partnership
Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by someonebaggy on Monday October 05, 2026 @10:37AM (#49965477)
They would have either sucked it up and supported the 11, or shut down the GrapheneOS project completely.
Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by HybridStatAnim8 on Monday October 05, 2026 @07:21PM (#49972109)
Neither of these options would have been chosen. GrapheneOS could have continued supporting existing pixels and investigated options paying ODMs directly for devices that met the requirements. They were considering this option before Motorola reached out.
Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by izacus on Monday October 05, 2026 @10:21AM (#49965281)
The comms have been like that for years now.
Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by varispeed on Monday October 05, 2026 @09:37AM (#49964725)
MTE support in itself says nothing as vendors usually obscure implementation details and also MTE is a perfect place to implant undocumented backdoors for security services to use.
Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by brookst on Monday October 05, 2026 @09:41AM (#49964789)
Any evidence of those backsoors?

This reads like “your front door lock is the perfect place for security services to have a master key.” True, but not strong as an argument against having a lock.

Re:Pixel 11 doesn't yet meet the GrapheneOS security standar... by gruez on Monday October 05, 2026 @09:48AM (#49964880)
>This reads like “your front door lock is the perfect place for security services to have a master key

Even that analogy fails because MTE is in addition to existing countermeasures against memory corruption attacks. In the worst case, compromising MTE just means you don't have MTE, not that you get arbitrary code execution.

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...