mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 08:26:00 +02:00
[GH-ISSUE #404] Feature request: Change notification sound in mobile apps #309
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ntfy#309
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @BeFs on GitHub (Sep 19, 2022).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/404
Requesting feature to change notification sound in iOS and Android-apps. Would also be super nice to have different sounds based on priority.
Would it be possible to implement a feature where the notification sound repeats x-times (or until its read)?
@binwiederhier commented on GitHub (Oct 1, 2022):
@BeFs You can already define a per-priority sound through Android notification channels. If you long-press on the ntfy icon and then select "App info" -> "Manage notifications", you can define behavior per priority.
I don't think this is technically possible, though I suppose alert apps like OpsGenie can do that too. 🤔
@JuDa-FR commented on GitHub (Oct 10, 2022):
It would also be cool to implement specific notifications on the presence of keywords or regular expressions.
@binwiederhier commented on GitHub (Oct 10, 2022):
Very related #6
@leokennis commented on GitHub (Nov 9, 2022):
On iOS the only alert currently offered is the basic “pinggg” sound.
Many apps offer a range of alert sounds, if not their own at least the iOS built in ones.
Perhaps Ntfy can do the same.
@binwiederhier commented on GitHub (Nov 19, 2022):
I think I'm closing this in favor of the duplicate ticket #6.