Enable Memory Tagging Extension on Google Pixel 8
Introduction
Enabling MTE on Pixel 8
Understanding MTE
Testing MTE
Creating the Bug Report
The Bug Report
Next Steps

  Log an issue

  Fork and edit

  Discuss on Discord

About this Learning Path

Skill level:  Introductory
Reading time:  10 min
Last updated:  18 Aug 2026
Skill level:
  Introductory
Reading time:
  10 min
Last updated:
  18 Aug 2026
Author:Roberto Lopez Mendez, Arm
Arm IP:Cortex-A
Tags: Performance and Architecture Android MTE adb Google Pixel 8
Author:
  • Roberto Lopez Mendez, Arm
Arm IP:
Cortex-A
Tags:
Performance and Architecture Android MTE adb Google Pixel 8

Who is this for?

This is an introductory topic for developers interested in learning how to enable Arm's Memory Tagging Extension (MTE) on Google's Pixel 8 smartphone and also how to access a memory bug report.

What will you learn?

Upon completion of this Learning Path, you will be able to:

  • Enable MTE on your Google Pixel 8 smartphone
  • Understand how MTE works and learn how to make an application crash when it encounters a memory bug
  • Access the memory bug report
  • Interpret the memory bug report

Prerequisites

Before starting, you will need the following:

  • A Google Pixel 8 smartphone
  • A USB cable to connect your Google Pixel 8 to your desktop machine
  • Android Debug Bridge (adb) installed on your device. Follow the steps in https://developer.android.com/tools/adb to install Android SDK Platform Tools. The adb tool is included in this package.

Summary

AI-assisted

This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
You’ll enable Arm MTE on a Google Pixel 8 and exercise it with a test app. First, you’ll turn on MTE in Developer options, install MTE_test.apk, and capture a bug report after a deliberate memory violation. Then, you’ll inspect the bug report and tombstone to understand the fault and MTE’s lock-and-key model.

Frequently asked questions

AI-assisted

These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
What result should I expect when I press a button in the test app?
With MTE enabled, the app triggers a memory violation and crashes. This lets you capture a bug report that includes MTE-specific details about the fault.
How do I capture a bug report after the crash?
Open Developer options and select Bug report, then tap Report to start generation. Wait for the progress indicator to complete, then use the resulting zip file for analysis.
Where in the bug report do I find detailed MTE diagnostics?
The zip contains a primary bugreport text file, and more detailed information is written to a tombstone file. Look under FS/data/tombstones in the unzipped folder.
My bug report filename includes “Husky.” Is that expected?
Yes. Husky is the code name for Google Pixel 8 Pro and can appear in the generated bug report filename.
What should I check if the test app doesn’t crash?
Verify that MTE is enabled in Developer options before running the app’s tests. Also confirm that MTE_test.apk installed correctly and that you’re invoking one of the buttons designed to trigger a memory bug.
Next