[GH-ISSUE #6] Android app: per-subscription / per-priority notification sound #5

New issue

Closed

opened 2026-05-07 00:18:14 +02:00 by BreizhHardware · 16 comments

BreizhHardware commented 2026-05-07 00:18:14 +02:00

Owner

Copy link

Originally created by @binwiederhier on GitHub (Nov 19, 2021).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/6

Originally created by @binwiederhier on GitHub (Nov 19, 2021). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/6

BreizhHardware 2026-05-07 00:18:14 +02:00

• closed this issue
• added the
  android-app
  in-progress 🏃
  enhancement
  labels

BreizhHardware commented 2026-05-07 00:18:16 +02:00

Author

Owner

Copy link

@Mikaela commented on GitHub (Jun 1, 2022):

This would also be nice on iOS as I tend to default to silent so most applications won't bother me unnecessarily

<!-- gh-comment-id:1143152993 --> @Mikaela commented on GitHub (Jun 1, 2022): This would also be nice on iOS as I tend to default to silent so most applications won't bother me unnecessarily

BreizhHardware commented 2026-05-07 00:18:16 +02:00

Author

Owner

Copy link

@inconis commented on GitHub (Jun 29, 2022):

On Android devices will be helpful the option to override system settings regarding noise.
In this way is possible to create an SOS channel to receive alarms in every condition.
A big thank to the developers of this project that I found so useful.

<!-- gh-comment-id:1170255642 --> @inconis commented on GitHub (Jun 29, 2022): On Android devices will be helpful the option to override system settings regarding noise. In this way is possible to create an SOS channel to receive alarms in every condition. A big thank to the developers of this project that I found so useful.

BreizhHardware commented 2026-05-07 00:18:17 +02:00

Author

Owner

Copy link

@binwiederhier commented on GitHub (Jun 29, 2022):

On Android devices will be helpful the option to override system settings regarding noise. In this way is possible to create an SOS channel to receive alarms in every condition. A big thank to the developers of this project that I found so useful.

You can do the overriding in the main settings. Go to Settings -> Channel settings". There you can override DND for the different priorities.

<!-- gh-comment-id:1170270713 --> @binwiederhier commented on GitHub (Jun 29, 2022): > On Android devices will be helpful the option to override system settings regarding noise. In this way is possible to create an SOS channel to receive alarms in every condition. A big thank to the developers of this project that I found so useful. You can do the overriding in the main settings. Go to Settings -> Channel settings". There you can override DND for the different priorities.

BreizhHardware commented 2026-05-07 00:18:17 +02:00

Author

Owner

Copy link

@inconis commented on GitHub (Jun 30, 2022):

Hi, thanks for your answer. Probably I explained in a bad way what I meant. With the app, "WirePusher" is possible to redirect the stream to "alarm stream" in this way if I put my phone in silent mode I can still receive the sound of the notification.
This function can be really useful for example to receive some "urgent" notifications.

<!-- gh-comment-id:1170881756 --> @inconis commented on GitHub (Jun 30, 2022): Hi, thanks for your answer. Probably I explained in a bad way what I meant. With the app, "WirePusher" is possible to redirect the stream to "alarm stream" in this way if I put my phone in silent mode I can still receive the sound of the notification. This function can be really useful for example to receive some "urgent" notifications.

BreizhHardware commented 2026-05-07 00:18:17 +02:00

Author

Owner

Copy link

@binwiederhier commented on GitHub (Nov 19, 2022):

See also #404

<!-- gh-comment-id:1320965461 --> @binwiederhier commented on GitHub (Nov 19, 2022): See also #404

BreizhHardware commented 2026-05-07 00:18:18 +02:00

Author

Owner

Copy link

@doits commented on GitHub (Nov 30, 2022):

Maybe this could be implemented by creating custom notification channels when enabled for a subscription, like toggling a setting "Custom notification channels for this subscription".

Currently there are 5 default notification channels (min to max). If the setting was toggled for a specific subscription, it could add 5 more notification channels for the specific channel. Then you could set the notification sound etc. within the android app settings, even override DND, like it is now possible for the 5 default notification channels.

Another way (or in addition) maybe you could create custom notification channels globally in the ntfy app settings and then assign a subscription to that notification channel. E.g. in settings you create a channel called "X" and ntfy would create 5 notification channels for "X", one for each priority (min to max). This way you could put multiple subscriptions into the same custom notification channel (not sure if this is needed).

<!-- gh-comment-id:1332280747 --> @doits commented on GitHub (Nov 30, 2022): Maybe this could be implemented by creating custom notification channels when enabled for a subscription, like toggling a setting "Custom notification channels for this subscription". Currently there are 5 default notification channels (min to max). If the setting was toggled for a specific subscription, it could add 5 more notification channels for the specific channel. Then you could set the notification sound etc. within the android app settings, even override DND, like it is now possible for the 5 default notification channels. Another way (or in addition) maybe you could create custom notification channels globally in the ntfy app settings and then assign a subscription to that notification channel. E.g. in settings you create a channel called "X" and ntfy would create 5 notification channels for "X", one for each priority (min to max). This way you could put multiple subscriptions into the same custom notification channel (not sure if this is needed).

BreizhHardware commented 2026-05-07 00:18:18 +02:00

Author

Owner

Copy link

@binwiederhier commented on GitHub (Dec 4, 2022):

@doits This is an incredibly smart idea. And I love that you even provided an implementation for it. I would even go so far as to just create a notification channel for every subscription by default. I'm gonna have a look at the code today if I can.

<!-- gh-comment-id:1336412031 --> @binwiederhier commented on GitHub (Dec 4, 2022): @doits This is an incredibly smart idea. And I love that you even provided an implementation for it. I would even go so far as to just create a notification channel for every subscription by default. I'm gonna have a look at the code today if I can.

BreizhHardware commented 2026-05-07 00:18:18 +02:00

Author

Owner

Copy link

@binwiederhier commented on GitHub (Dec 4, 2022):

Okay, upon thinking about it, having a custom channel for each subscription by default is not going to work, because then the priority-channels would be irrelevant. It's kind of a tricky one. I think if we were to make this a thing, it'd have to be opt-in like you suggested:

With these channels:

- Subscription service
- Min priority
- Low priority
- Default priority
- High priority
- Max priority
- ntfy.sh/mytopic (if opted in)
- ntfy.sh/othertopic (if opted in)

I think adding multiple "per-priority channels" for each topic (like you implemented) is overkill.

<!-- gh-comment-id:1336413344 --> @binwiederhier commented on GitHub (Dec 4, 2022): Okay, upon thinking about it, having a custom channel for each subscription by default is not going to work, because then the priority-channels would be irrelevant. It's kind of a tricky one. I think _if_ we were to make this a thing, it'd have to be opt-in like you suggested: With these channels: ``` - Subscription service - Min priority - Low priority - Default priority - High priority - Max priority - ntfy.sh/mytopic (if opted in) - ntfy.sh/othertopic (if opted in) ``` I think adding multiple "per-priority channels" for each topic (like you implemented) is overkill.

BreizhHardware commented 2026-05-07 00:18:19 +02:00

Author

Owner

Copy link

@binwiederhier commented on GitHub (Dec 4, 2022):

Alright ... So I should have thought about the whole thing and maybe even tried it before commenting. I do think that maybe your approach is actually the correct one. Otherwise you'd essentially take away the ability to have low/high-priority messages when this is enabled.

So what you implemented is this:

Background service
- Subscription service

Priority channels
- Min priority
- Low priority
- Default priority
- High priority
- Max priority

ntfy.sh/mytopic
- Min priority
- Low priority
- Default priority
- High priority
- Max priority

While this seems like the only approach that achieves "infinite flexibility", it also seems like absolute configuration overkill. Say I have 5 subscriptions, that means I now have 25 channels if I enable the feature on a subscription. Doing a simple thing, like changing the notification sound, now becomes an awful chore.

<!-- gh-comment-id:1336416133 --> @binwiederhier commented on GitHub (Dec 4, 2022): Alright ... So I should have thought about the whole thing and maybe even tried it before commenting. I do think that maybe your approach is actually the correct one. Otherwise you'd essentially take away the ability to have low/high-priority messages when this is enabled. So what you implemented is this: ``` Background service - Subscription service Priority channels - Min priority - Low priority - Default priority - High priority - Max priority ntfy.sh/mytopic - Min priority - Low priority - Default priority - High priority - Max priority ``` While this seems like the only approach that achieves "infinite flexibility", it also seems like absolute configuration overkill. Say I have 5 subscriptions, that means I now have 25 channels if I enable the feature on a subscription. Doing a simple thing, like changing the notification sound, now becomes an awful chore.

BreizhHardware commented 2026-05-07 00:18:19 +02:00

Author

Owner

Copy link

@doits commented on GitHub (Dec 4, 2022):

Thanks for your review and your feedback. Your last comment is correct about I implemented it.

I also thought about only adding one channel per subscription (ignoring priority), but I felt this was an important feature of ntfy which should always be present.

While writing a response I thought about different variations and finally asked myself the question: What use case is solved by this? I think most of users want to change the notification sound for a subscription, not having to change the sound of 5 priorities (like you said). Changing the notification for each priority also has it's use case, but probably to fewer users.

So maybe this way is cleaner:

You have the setting ...

Custom notifications for this subscription

... and when you enable it, it creates one extra notification channel:

ntfy.sh/mytopic
- All priorities

So by default, all priorities of this subscription go into this one channel.

In addition, it reveals 5 more settings (maybe they must be expanded first to be visible, or they are on a second "subscription notification page" etc.):

Custom notifications for a specific priority:
- Min priority
- Low priority
- Default priority
- High priority
- Max priority

All are OFF by default. Each toggle creates an extra notification channel just for this subscription and priority, so for example:

Custom notifications for a specific priority:
- Min priority:      OFF
- Low priority:      OFF
- Default priority:  OFF
- High priority:     ON
- Max priority:      ON

... results in ...

ntfy.sh/mytopic
- High priority
- Max priority
- Other priorities

So you can add specific notification channels per priority. If not, they go into the "Other priorities" channel of the subscription.

Finally, if you create a channel for each priority:

Custom notifications for a specific priority:
- Min priority:      ON
- Low priority:      ON
- Default priority:  ON
- High priority:     ON
- Max priority:      ON

... it would result in channels like the current implementation ...

ntfy.sh/mytopic
- Min priority
- Low priority
- Default priority
- High priority
- Max priority

(no need for the "Other priorities" notification channel).

What do you think? Still too complicated?

<!-- gh-comment-id:1336428384 --> @doits commented on GitHub (Dec 4, 2022): Thanks for your review and your feedback. Your last comment is correct about I implemented it. I also thought about only adding one channel per subscription (ignoring priority), but I felt this was an important feature of ntfy which should always be present. While writing a response I thought about different variations and finally asked myself the question: What use case is solved by this? I think most of users want to change the notification sound for a subscription, not having to change the sound of 5 priorities (like you said). Changing the notification for each priority also has it's use case, but probably to fewer users. So maybe this way is cleaner: You have the setting ... ``` Custom notifications for this subscription ``` ... and when you enable it, it creates one extra notification channel: ``` ntfy.sh/mytopic - All priorities ``` So by default, all priorities of this subscription go into this one channel. In addition, it reveals 5 more settings (maybe they must be expanded first to be visible, or they are on a second "subscription notification page" etc.): ``` Custom notifications for a specific priority: - Min priority - Low priority - Default priority - High priority - Max priority ``` All are `OFF` by default. Each toggle creates an extra notification channel just for this subscription and priority, so for example: ``` Custom notifications for a specific priority: - Min priority: OFF - Low priority: OFF - Default priority: OFF - High priority: ON - Max priority: ON ``` ... results in ... ``` ntfy.sh/mytopic - High priority - Max priority - Other priorities ``` So you can add specific notification channels per priority. If not, they go into the "Other priorities" channel of the subscription. Finally, if you create a channel for each priority: ``` Custom notifications for a specific priority: - Min priority: ON - Low priority: ON - Default priority: ON - High priority: ON - Max priority: ON ``` ... it would result in channels like the current implementation ... ``` ntfy.sh/mytopic - Min priority - Low priority - Default priority - High priority - Max priority ``` (no need for the "Other priorities" notification channel). What do you think? Still too complicated?

BreizhHardware commented 2026-05-07 00:18:19 +02:00

Author

Owner

Copy link

@doits commented on GitHub (Dec 4, 2022):

A simplification could be to have the user only choose between three states:

Custom notifications for this subscription:
- A: Off (No custom notifications, default)
- B: On (All notifications have the same custom notification channel, priority not configurable --> one channel)
- C: Per priority (One notification channel for each priority --> 5 channels)

So in essence you could only choose to have all 5 priority channels (C) or one for all priorities (B), which would make the settings dialog simpler (only one list setting) and sacrifice only a little bit flexibility.

<!-- gh-comment-id:1336431612 --> @doits commented on GitHub (Dec 4, 2022): A simplification could be to have the user only choose between three states: ``` Custom notifications for this subscription: - A: Off (No custom notifications, default) - B: On (All notifications have the same custom notification channel, priority not configurable --> one channel) - C: Per priority (One notification channel for each priority --> 5 channels) ``` So in essence you could only choose to have all 5 priority channels (`C`) or one for all priorities (`B`), which would make the settings dialog simpler (only one list setting) and sacrifice only a little bit flexibility.

BreizhHardware commented 2026-05-07 00:18:20 +02:00

Author

Owner

Copy link

@binwiederhier commented on GitHub (Dec 4, 2022):

Your suggestion in the last comment sounds fantastic and tackles all the issues I was worried about. However, option B is so incredibly counter-intiutive ("why does my min priority message still ring?", "why does my max priority message not vibrate like a maniac?") that it doesn't seem like it should exist.

So after all this discussion, I feel like what you have seems to be the right approach. Let's go with that! I still have not reviewed the code, but I will probably tonight.

<!-- gh-comment-id:1336493093 --> @binwiederhier commented on GitHub (Dec 4, 2022): Your suggestion in the last comment sounds fantastic and tackles all the issues I was worried about. However, option B is so incredibly counter-intiutive ("why does my min priority message still ring?", "why does my max priority message not vibrate like a maniac?") that it doesn't seem like it should exist. So after all this discussion, **I feel like what you have seems to be the right approach. Let's go with that!** I still have not reviewed the code, but I will probably tonight.

BreizhHardware commented 2026-05-07 00:18:20 +02:00

Author

Owner

Copy link

@binwiederhier commented on GitHub (Dec 6, 2022):

FYI I still haven't reviewed it, and I'm too tired to do it tonight. I got held up by all that "Google rejecting the app" business (see #531 ...).

<!-- gh-comment-id:1338617284 --> @binwiederhier commented on GitHub (Dec 6, 2022): FYI I still haven't reviewed it, and I'm too tired to do it tonight. I got held up by all that "Google rejecting the app" business (see #531 ...).

BreizhHardware commented 2026-05-07 00:18:20 +02:00

Author

Owner

Copy link

@doits commented on GitHub (Dec 6, 2022):

No problem, take the time you need. There's no push from my side.

<!-- gh-comment-id:1339398072 --> @doits commented on GitHub (Dec 6, 2022): No problem, take the time you need. There's no push from my side.

BreizhHardware commented 2026-05-07 00:18:20 +02:00

Author

Owner

Copy link

@binwiederhier commented on GitHub (Dec 10, 2022):

I merged https://github.com/binwiederhier/ntfy-android/pull/49 and it'll be in the next release. Thank you @doits for all your work.

<!-- gh-comment-id:1344985509 --> @binwiederhier commented on GitHub (Dec 10, 2022): I merged https://github.com/binwiederhier/ntfy-android/pull/49 and it'll be in the next release. Thank you @doits for all your work.

BreizhHardware commented 2026-05-07 00:18:21 +02:00

Author

Owner

Copy link

@doits commented on GitHub (Dec 10, 2022):

Glad it got merged and thanks for your review and your finishing up! Unfortunately I couldn't review your changes (couldn't find the time), but I'm sure it works out like it should :-)

<!-- gh-comment-id:1345234173 --> @doits commented on GitHub (Dec 10, 2022): Glad it got merged and thanks for your review and your finishing up! Unfortunately I couldn't review your changes (couldn't find the time), but I'm sure it works out like it should :-)

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

dependabot/npm_and_yarn/web/fast-uri-3.1.2

email-verification

attachment-no-http2

attachment-fixes

attachment-s3

config-generator

postgres-replica

dockers-v2

postgres-support

postgres-webpush+user+message

postgres-webpush+user

postgres-webpush

1364-copy-action

crashfix

user-header

scalar-api-docs

cancel-scheduled

update-available

windows-server

303-update-notifications

postgres

admin-ui

require-login

http-clipboard

message-cache-lock

debian-stripe

predefined-users

busy-timeout

template-dir

ipv6

client-ip-header

apns-fix

feat_optional_require_login

security-updates

pg-message-cache

templating-disallow

templating-3

templating-2

message-size-limit+delay-limit

remove-rate-topics

html-emails

cf-priority

acl-underscores

auth-user-header

markdown

img-attach

web-improvements

utf8-headers

matrix-507-reject

http-response-writer

new-homepage-design

e2e

canary

windows

electron

update-messages

webhook-templating

v2.22.0

v2.21.0

v2.20.1

v2.20.0

v2.19.2

v2.19.1

v2.19.0

v2.18.0

v2.17.0

v2.16.0

v2.15.0

v2.14.0

v2.13.0

v2.12.0

v2.11.0

v2.10.0

v2.9.0

v2.8.0

v2.7.0

v2.6.2

v2.6.1

v2.6.0

v2.5.0

v2.4.0

v2.3.1

v2.3.0

v2.2.0

v2.1.2

v2.1.1

v2.1.0

v2.0.1

v2.0.0

v1.31.0

v1.30.1

v1.29.1

v1.29.0

v1.28.0

v1.27.2

v1.27.1

v1.26.0

v1.25.2

v1.25.1

v1.25.0

v1.24.0

v1.23.0

v1.22.0

v1.21.2

v1.21.1

v1.21.0

v1.20.0

v1.19.0

v1.18.1

v1.18.0

v1.17.1

v1.17.0

v1.16.0

v1.15.0

v1.14.1

v1.14.0

v1.13.0

v1.12.1

v1.12.0

v1.11.1

v1.11.2

v1.11.0

v1.10.0

v1.9.0

v1.8.0

v1.7.0

v1.6.1

v1.6.0

v1.5.3

v1.5.2

v1.5.1

v1.5.0

v1.4.8

v1.4.7

v1.4.6

v1.4.5

v1.4.4

v1.4.3

v1.4.2

v1.4.1

v1.4.0

v1.3.2

v1.3.3

v1.3.1

v1.3.0

v1.2.5

v1.2.4

v1.2.3

v1.2.2

v1.2.1

v1.2.0

v1.1.3

v1.1.2

v1.1.1

v1.1.0

v1.0.0

v0.0.5

v0.0.4

v0.0.3

v0.0.2

v0.0.1

Labels

Clear labels   

ai-generated

  

android-app

  

android-app

  

android-app

  

🪲 bug

  

build

  

build

  

dependencies

  

docs

  

enhancement

  

enhancement

  

🔥 HOT

  

in-progress 🏃

  

ios

  

prio:low

  

prio:low

  

pull-request

Mirrored from GitHub Pull Request

  

question

  

🔒 security

  

server

  

server

  

unified-push

  

web-app

  

website

No labels

ai-generated

android-app

android-app

android-app

🪲 bug

build

build

dependencies

docs

enhancement

enhancement

🔥 HOT

in-progress 🏃

ios

prio:low

prio:low

pull-request

question

🔒 security

server

server

unified-push

web-app

website

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ntfy#5

No description provided.