Android's built-in rule layers
Before installing another utility, review the source app's own notification settings, Android's notification channels, and Do Not Disturb or Modes filters. A well-designed app may already separate urgent alerts into their own category. Android may also allow chosen apps, people, conversations, alarms or repeat callers.
DND Override rule types
| Rule | Matches |
|---|---|
| Selected app only | Eligible newly posted notifications from that package |
| Keyword only | Visible notification title/message from any app containing the text |
| App + keyword | Both package and text condition |
| Multiple keywords | Any listed keyword, or all of them |
| Regex | One case-sensitive pattern in title/message text |
Rules can be enabled or disabled without deleting them. Each rule can use the default notification sound, an available system notification sound, or a custom audio file selected through Android's document picker.
What happens after a match
The notification-listener service ignores DND Override's own package and Android group-summary notifications. It extracts the current visible text, finds the first enabled matching rule and checks that DND is active and alarm volume is not muted. It then queues the selected sound using alarm audio attributes. Identical repeated posts for the same notification key and content are deduplicated; a genuinely updated notification can alert again.
What does not happen
- The app does not turn DND on or off.
- It does not change another app's notification channel.
- It does not acknowledge incidents or contact a monitoring provider.
- Dismissing a source notification does not stop sound that is already playing.
- It cannot guarantee that Android or the source app will deliver a notification.
Continue with a specific scenario: server monitoring, security cameras, or smart-home notifications.