# [Enable Memory Tagging Extension on Google Pixel 8](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/mte_on_pixel8/)

## In this learning path

- [Introduction](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/mte_on_pixel8/)
- [Enabling MTE on Pixel 8](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/mte_on_pixel8/how-to-1/)
- [Understanding MTE](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/mte_on_pixel8/how-to-2/)
- [Testing MTE](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/mte_on_pixel8/how-to-3/)
- [Creating the Bug Report](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/mte_on_pixel8/how-to-4/)
- [The Bug Report](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/mte_on_pixel8/how-to-5/)
- [Next Steps](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/mte_on_pixel8/_next-steps/)

## About this Learning Path

| Skill level:      | Introductory          |
|-------------------|-----------------------|
| Reading time:     | 10 min                |
| Last updated:     | 18 Aug 2026           |

| Author:                   | Roberto Lopez Mendez, Arm                                                                |
|---------------------------|------------------------------------------------------------------------------------------|
| Arm IP:                   | [Cortex-A](https://support.arm.com/?tab=compute-ip&Product%20Type=Application%20Processors) |
| 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](https://developer.android.com/tools/adb) to install Android SDK Platform Tools. The adb tool is included in this package.

### Summary
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
<details>
<summary>What result should I expect when I press a button in the test app?</summary>
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.
</details>

<details>
<summary>How do I capture a bug report after the crash?</summary>
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.
</details>

<details>
<summary>Where in the bug report do I find detailed MTE diagnostics?</summary>
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.
</details>

<details>
<summary>My bug report filename includes “Husky.” Is that expected?</summary>
Yes. Husky is the code name for Google Pixel 8 Pro and can appear in the generated bug report filename.
</details>

<details>
<summary>What should I check if the test app doesn’t crash?</summary>
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.
</details>