[GH-ISSUE #1724] Insistent notification type (Android call-style alert, no Twilio) #1200

New issue

Open

opened 2026-05-07 01:00:46 +02:00 by BreizhHardware · 0 comments

BreizhHardware commented

2026-05-07 01:00:46 +02:00

Owner

Originally created by @DarthJahus on GitHub (May 3, 2026).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1724

💡 Idea

Add a notification type that triggers Android's insistent/call-style alert (continuous vibration, full-screen intent, screen wake, but without requiring Twilio integration).

The current urgent priority delivers a strong one-shot notification. X-Call achieves continuous alerting but requires Twilio (external dependency, not self-hosted-friendly). There is no middle ground for a fully local, offline-capable setup that needs guaranteed attention (like household paging, on-call alerting on a self-hosted instance).

A new priority level or header (e.g. Priority: insistent or X-Insistent: yes) that, on Android:

Uses FLAG_INSISTENT on the notification, causing continuous vibration/ringtone until dismissed
Triggers a full-screen intent (same as an incoming call)
Works entirely client-side (no server-side telephony required)

This also benefits wearable users: connected watches (Garmin, Wear OS) treat incoming calls as a distinct alert type with continuous haptic feedback, whereas standard notifications (even urgent) produce a single pulse.

Related: #1041 (nagging notifications / repeating interval approach); this proposes the OS-native call-style approach instead.

💻 Target components

Android app

Originally created by @DarthJahus on GitHub (May 3, 2026). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1724 :bulb: **Idea** Add a notification type that triggers Android's **insistent/call-style** alert (continuous vibration, full-screen intent, screen wake, but without requiring Twilio integration). The current `urgent` priority delivers a strong one-shot notification. `X-Call` achieves continuous alerting but requires Twilio (external dependency, not self-hosted-friendly). There is no middle ground for a fully local, offline-capable setup that needs guaranteed attention (like household paging, on-call alerting on a self-hosted instance). A new priority level or header (e.g. `Priority: insistent` or `X-Insistent: yes`) that, on Android: - Uses [`FLAG_INSISTENT`](https://developer.android.com/reference/android/app/Notification#FLAG_INSISTENT) on the notification, causing continuous vibration/ringtone until dismissed - Triggers a full-screen intent (same as an incoming call) - Works entirely client-side (no server-side telephony required) This also benefits wearable users: connected watches (Garmin, Wear OS) treat incoming calls as a distinct alert type with continuous haptic feedback, whereas standard notifications (even `urgent`) produce a single pulse. Related: #1041 (nagging notifications / repeating interval approach); this proposes the OS-native call-style approach instead. :computer: **Target components** Android app