Opt-in to Arm Memory Tagging Extensions (MTE) · TeamNewPipe/NewPipe#12644

2025-09-18T13:45:05.000Z

### Checklist - [x] I made sure that there are *no existing issues* - [open](https://github.com/TeamNewPipe/NewPipe/issues) or [closed](https://github.com/TeamNewPipe/NewPipe/issues?q=is%3Aissue+is%3Aclosed) - which I could contribute my information to. - [x] I have read the [FAQ](https://newpipe.net/FAQ/) and my problem isn't listed. - [x] 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](https://github.com/TeamNewPipe/NewPipeExtractor/issues). - [x] I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise. - [x] This issue contains only one feature request. - [x] I have read and understood the [contribution guidelines](https://github.com/TeamNewPipe/NewPipe/blob/dev/.github/CONTRIBUTING.md). ### 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 😇 )

(2 comments) (3 reactions) (0 assignees)Java (38,153 stars) (3,577 forks)batch import

feature requestgood first issue

説明

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

コントリビューターガイド

技術スタック: javaandroid
領域: mobilesecurity
Issue 種別: feature
難度: 1
推定時間: under 1 hour
活動状況: fresh
明確さ: clear
前提条件: Android development basicsfamiliarity with AndroidManifest.xml
初心者向け度: 90
調査方針: The issue requests adding android:memtagMode="async" to the <application> tag in AndroidManifest.xml. Review the current manifest at app/src/main/AndroidManifest.xml. The change is straightforward: add the attribute. No other modifications needed. The issue includes links to Android documentation and a blog post explaining MTE. The author confirms it works on GrapheneOS. No additional dependencies or code changes.