Troubleshooting

NoDial Editorial ／ 2026-10-06

If a call went through when you expected it to be blocked, or blocking seems to have quietly stopped working, work through this list before assuming something's broken.

1. A call still went through

Protection isn't on. If the Home screen shows "Enable call blocking (grant permission)," or a red "⚠ Permission revoked" banner, finish the permission step — see section 2 below, or Getting started for the first-time version of the same screen.
The number is on "Set specific hours," and you're outside the window. That's by design — see Choosing how to block a number.
The number is on "Limit calls," and you haven't used up the limit yet. Calls up to the limit always go through; only calls past it are blocked.
The number is set to "Confirm before calling." This mode never silently blocks — it opens a confirm screen every time. If you completed the slide and redialed within 60 seconds, that call is expected to connect. See Confirm before calling.
"Block all outgoing calls" is on, and the number is in its allowed list. While Block All is enforcing, only its own allowed numbers get through — your per-number rules are paused, not consulted, until you turn Block All off. See Block all outgoing calls.
It was treated as a domestic call, not international. International blocking compares countries, not calling-code digits — a handful of territories that share a larger country's calling code (Puerto Rico with the US, for instance) count as domestic. See International call blocking.
You called through an internet-calling app, not your phone's regular dialer. NoDial acts on calls placed through Android's own calling system, not voice calls made inside a messaging or internet-calling app.
You called a different number. Open the number in NoDial and compare it digit by digit with the one you dialed — one wrong digit makes it a different number, and a contact may have more than one number saved. Writing it with or without the country code doesn't matter; NoDial treats both as the same number.

2. "Call blocking is disabled"

If you see this notification, or a red "⚠ Permission revoked" banner on Home, Android has taken away NoDial's call-handling permission — this can happen after a system update, or if something else on the phone changed the default call-handling app. NoDial doesn't always know exactly what caused it, only that it's no longer held.

The fix is always the same: tap "Re-enable" on the banner (or open NoDial and follow the same permission screen from first-time setup, described in Getting started). If you miss the in-app notice, NoDial also sends a follow-up notice about a day later if the permission is still missing.

3. Blocking stops quietly in the background

Some phones aggressively close background apps to save battery, and NoDial's monitoring runs in the background between calls. If blocking seems to have stopped without any notification or banner explaining why, check your phone's battery settings for an option to stop it from being optimized or closed in the background — the exact wording and location vary by phone maker, so look for something like "battery optimization," "background activity," or "auto-start management" in your phone's own settings app, outside of NoDial itself.

4. Before you uninstall

Uninstalling removes your numbers, their rules, and your memos from the phone permanently — the same loss described in Changing phones, since both are tied to the same on-device data. Your Premium subscription isn't canceled by uninstalling; it keeps billing through Google Play until you cancel it separately, and it comes back automatically if you reinstall NoDial while signed into the same Google account.

5. Emergency numbers

Emergency numbers can never be registered in NoDial in any mode, so there's no scenario where one ends up blocked by mistake — this is checked before anything else, every time.

NoDial — block outgoing calls to the numbers you chooseAlways, on a schedule, with a call limit, or confirm first. Emergency calls never blocked.