About the notification listener permission
@marcbaechinger is already working on this.
Since Apr 17, 2026.
- Dominant language
- Java
- Stars
- 3k
- Forks
- 955
- Avg merge
- 12d 14h
- Merged PRs (30d)
- 2
Description
It's required to get notification listener permission in order to be able to query the active media sessions and interact with them.
That is a major pain for various reasons, such as:
- Users being rightfully scared by granting such a powerful permission
- Play Protect flagging roughly 100% of non-Play-distributed apps with that permission as malware once a certain install threshold is reached, forcing you to appeal
- Having granted notification listener permission forces the app to stay running in background 24/7 (can be observed in Developer options > Running services), which is convenient for some use cases (such as scrobbler app) but also totally wasteful use of RAM for others
Could it be considered to create a new permission, purely for media session access, as seperate, less sensitive permission? I think notification listener permission should keep it's rights for accessing media session, but there should be a second way which is easier to sell to the user.
I'm aware this is not actionable immediately because it will require internal discussion & prioritization and even if that leads to a favourable outcome, a new platform version will still need to be released. I'm offering this purely as async feedback so you know of this pain point. Thanks for considering!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.