Opt-in to Arm Memory Tagging Extensions (MTE)

[thgoebel]

Checklist

• I made sure that there are no existing issues - open or closed - which I could contribute my information to.
• I have read the FAQ and my problem isn't listed.
• I'm aware that this is a request for NewPipe itself and that requests for adding a new service need to be made at NewPipeExtractor.
• I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.

Feature description

Please opt-in to Arm Memory Tagging Extensions (MTE).

Set android:memtagMode="async" in the AndroidManifest.

I have been running NewPipe on GrapheneOS with MTE force-enabled for a few months now, without any issues.

Why do you want this feature?

NewPipe indirectly parses media, and media parsing are notoriously complex and vulnerable.
(Even though parsing is delegated to the Android framework, that code still runs in the app's process.)

MTE would be an easy security improvement. At least for the people who have Google Pixels.

Additional information

• https://source.android.com/docs/security/test/memory-safety/arm-mte#enable-mte-apps
• https://thore.io/posts/2025/09/introduction-to-arm-memory-tagging-extensions/ (my blog 😇 )

[litetex]

I think this would be a good and relatively easy to do improvement, however it should be done by someone who has a Pixel phone (I do not) and can test it :)

@thgoebel
You can also feel free to send a PR if you want :)

[camle2145]

I could give this a shot? It would be my first contribution

I have a Pixel so can test it