We've been testing performance of MTE on the Pixel 11 using ...

Final

npub1hxx76n82ags8jrduk0p3gqrfyqyaxnrlnynu9p5rt2vmwjq6ts3q4sg75y

hex

00000218e1442cf3165a9a172d80a9afca9b0a8392aad7b36a038b484601dda0

nevent

nevent1qqsqqqqzrrs5gt8nzedf59edsz56lj5mp2pe92khkd4q8z6ggcqamgqprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgstnr0dfn4w5grepk7t8sc5qp5jqzwnf3lejf7zs6p44xdhfqd9cgsw3a9kv

Kind-1 (TextNote)

2026-09-02T04:41:12Z

We've been testing performance of MTE on the Pixel 11 using the Android 17 QPR2 Beta 4 release adding back firmware support for it. MTE in asymmetric mode only has around 5% overhead in the standard benchmarks and other tests we've done. That's more than good enough but we've done limited tests.

Android 17 QPR2 Beta 4 on the Pixel 11 force disables MTE for the OS from the firmware. Using it requires ignoring the arm64.nomte parameter being passed to the kernel. It still isn't clear why they're making the feature unavailable. SVE was also force disabled in Android 17 but not in QPR2 Beta 4.

Our initial testing indicates performance isn't substantially worse. The overhead may be higher but there was an incremental CPU performance with the Pixel 11 which should more than make up for it. However, MTE is unavailable with stable firmware and we're bypassing firmware disabling it for QPR2.

Multiple Google engineers we've contacted have said they aren't able to give us any information about this so we're left doing reverse engineering and relying on leaks. The leaks do not seem reliable and do not match what we see. Our concern is that MTE may actually be broken due to CPU errata.

nostr:nevent1qqsqqqqtcwkmalemepulxhurep8ptunmsvyzwyurggpy39prghwwhzcpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtczyzucmm2vat4zq7gdhjeux9qqdysqn56v07vj0s5xsddfnd6grfwzyqcyqqqqqqgdgz630

原始 JSON

{
  "kind": 1,
  "id": "00000218e1442cf3165a9a172d80a9afca9b0a8392aad7b36a038b484601dda0",
  "pubkey": "b98ded4ceaea20790dbcb3c31400692009d34c7f9927c286835a99b7481a5c22",
  "created_at": 1788324072,
  "tags": [
    [
      "p",
      "b98ded4ceaea20790dbcb3c31400692009d34c7f9927c286835a99b7481a5c22",
      "wss://relay.primal.net/"
    ],
    [
      "q",
      "00000bc3adbeff3bc879f35f83c84e15f27b8308271383420248942345dceb8b",
      "wss://relay.primal.net/",
      "b98ded4ceaea20790dbcb3c31400692009d34c7f9927c286835a99b7481a5c22"
    ],
    [
      "nonce",
      "1001L=",
      "20"
    ]
  ],
  "content": "We've been testing performance of MTE on the Pixel 11 using the Android 17 QPR2 Beta 4 release adding back firmware support for it. MTE in asymmetric mode only has around 5% overhead in the standard benchmarks and other tests we've done. That's more than good enough but we've done limited tests.\n\nAndroid 17 QPR2 Beta 4 on the Pixel 11 force disables MTE for the OS from the firmware. Using it requires ignoring the arm64.nomte parameter being passed to the kernel. It still isn't clear why they're making the feature unavailable. SVE was also force disabled in Android 17 but not in QPR2 Beta 4.\n\nOur initial testing indicates performance isn't substantially worse. The overhead may be higher but there was an incremental CPU performance with the Pixel 11 which should more than make up for it. However, MTE is unavailable with stable firmware and we're bypassing firmware disabling it for QPR2.\n\nMultiple Google engineers we've contacted have said they aren't able to give us any information about this so we're left doing reverse engineering and relying on leaks. The leaks do not seem reliable and do not match what we see. Our concern is that MTE may actually be broken due to CPU errata.\n\nnostr:nevent1qqsqqqqtcwkmalemepulxhurep8ptunmsvyzwyurggpy39prghwwhzcpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtczyzucmm2vat4zq7gdhjeux9qqdysqn56v07vj0s5xsddfnd6grfwzyqcyqqqqqqgdgz630",
  "sig": "865a139b1ad0f45457863f343e86fc7bd96a20db399f538f512ac38939915916121416e60783791ba319ef5d4950f0980c1a028c4031f51525c0a52a424769da"
}