Adxm My point is that if Pixel 11 support is technically feasible, a warning could be a reasonable way to let users accept the security trade offs rather than excluding the device entirely. I just think that if support is feasible, it could be worth considering given the number of users who may eventually move to Pixel 11.
I'd really like to know what reasons might there be for a user who wants to install GrapheneOS - and is therefore presumably prioritizing privacy and security - to get a Pixel 11 if MTE isn't supported?
The Pixel 11 seems to be such an unimpressive upgrade from the Pixel 10 that it doesn't seem worthy giving up a such an important security feature:
Hardware memory tagging is going to provide a massive increase to protection against remote exploitation for GrapheneOS users. It's the biggest security feature we'll be shipping since we started in 2014. We want to have it enabled by default in async (fast) mode for the base OS.
source: https://x.com/GrapheneOS/status/1716945639198880037
MTE has been supported since the Pixel 8. Depending on which model you buy, the device will be supported by GrapheneOS until 2030 or 2033. That’s still a long time, during which many things may happen (such as Google implementing MTE again in future devices and/or Motorola releasing several devices that run GrapheneOS).
For now, it probably makes sense to wait before buying a Pixel 11 so you can get an official response from Google on whether MTE is supported or not and GrapheneOS has decided how to proceed with the situation.
It also may have economic advantages too: If you look at price depreciation of Google devices , you may save some money if you wait a bit.
And older devices, such as the Pixel 10, are seeing an even more significant price drop: Where I live you're able to get Pixel 10s for around 60% of its launch price which, in my opinion, makes it a much more attractive overall deal than any Pixel 11 pre-order promotion.