Skip to content
KerballOne edited this page Jul 6, 2026 · 1 revision

Alerts

A lightweight sound/vibration/flashlight/screen-wake chime, distinct from a full notification, that fires when Notification Screening allows a message from a screened app. It exists because the original app's notification is already visible on screen, so allowing it again shouldn't produce a duplicate full notification, just a short signal to draw attention. This is especially useful if you've muted that app's own notification channel to silence blocked messages, which would otherwise also silence the allowed ones.

Configuration levels

  • Per-app default (Actions → Alerts): one row per app currently selected for Notification Screening, each with independent toggle icons (vibration / flashlight / wake screen) and a ringtone button.
  • Per-rule override: on a Number/Text Rule set to Allow and applying to notification Title/Body, an Alert row appears in the rule editor with the same controls. Leaving it at default uses the app-level config; setting anything explicitly overrides the app default for that specific rule. A small reset icon reverts back to "use app default."

Ringtone

The ringtone picker is restricted to notification-type sounds (not full call ringtones), and playback is automatically stopped after a few seconds, since this is meant to be a brief alert, not a continuous ring.

Why not just use Notifications?

Notifications (the Actions section's "Notifications" setting) are a full system notification with the message content, needed for Calls and SMS/MMS since disabling the native app's own notifications means this is the only way you'd see the content. Notification Screening doesn't need this: the original app's notification is already visible, so a second full notification would just be a duplicate. Alerts fill that gap with something intentionally lighter.

Clone this wiki locally