[GH-ISSUE #1407] Android application - subsequent notification doesn't vibrate or produce sound #988

Open
opened 2026-05-07 00:29:23 +02:00 by BreizhHardware · 2 comments

Originally created by @freezoo2 on GitHub (Jul 31, 2025).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1407

🐞 Describe the bug
When I receive a notification on Android application, it vibrates and emits sound. If I receive a subsequent notification, it will not generate any sound or vibration. The only way for new message to vibrate or generate sound is to clear the ntfy notifications in Android and then next message will generate sound and vibration. I use a single topic and send messages with highest priority.

💻 Components impacted
Android app

🔮 Additional context
I run Android 16. I disabled the notification cooldown feature in Android 16. This seems to be an application behavior as other application can generate sound and vibration for new notification even if old notification are still present.

This is annoying as I don't clear notification when I need to take action on something. Because 1 notification wasn't cleared, then I don't know when there new message in same topic.

Originally created by @freezoo2 on GitHub (Jul 31, 2025). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1407 :lady_beetle: **Describe the bug** When I receive a notification on Android application, it vibrates and emits sound. If I receive a subsequent notification, it will not generate any sound or vibration. The only way for new message to vibrate or generate sound is to clear the ntfy notifications in Android and then next message will generate sound and vibration. I use a single topic and send messages with highest priority. :computer: **Components impacted** Android app :crystal_ball: **Additional context** I run Android 16. I disabled the notification cooldown feature in Android 16. This seems to be an application behavior as other application can generate sound and vibration for new notification even if old notification are still present. This is annoying as I don't clear notification when I need to take action on something. Because 1 notification wasn't cleared, then I don't know when there new message in same topic.
Author
Owner

@wunter8 commented on GitHub (Aug 1, 2025):

This is an Android 16 OS bug: https://issuetracker.google.com/issues/427367143

Some apps work okay because they set a group ID for each notification. ntfy isn't doing that right now, but I wouldn't expect an Android update soon, unfortunately

<!-- gh-comment-id:3141937109 --> @wunter8 commented on GitHub (Aug 1, 2025): This is an Android 16 OS bug: https://issuetracker.google.com/issues/427367143 Some apps work okay because they set a group ID for each notification. ntfy isn't doing that right now, but I wouldn't expect an Android update soon, unfortunately
Author
Owner

@TimYorke commented on GitHub (Sep 10, 2025):

This is an Android 16 OS bug: https://issuetracker.google.com/issues/427367143

Marked there as fixed as of Aug 4: https://issuetracker.google.com/issues/427367143#comment19

<!-- gh-comment-id:3275096358 --> @TimYorke commented on GitHub (Sep 10, 2025): > This is an Android 16 OS bug: https://issuetracker.google.com/issues/427367143 Marked there as fixed as of Aug 4: https://issuetracker.google.com/issues/427367143#comment19
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
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#988
No description provided.