Do Not Disturb on my Android suddenly stopped behaving the way I set it up. Some calls and notifications still come through even though I’ve blocked them in the DND settings. I’ve checked schedules, exceptions, and app overrides but nothing seems to fix it. Can someone explain what might be causing this and how to fully lock down Do Not Disturb so only my chosen contacts and apps can break through?
Had this happen on my Pixel a while ago. DND went nuts and started letting random stuff through. A few things to check that are not obvious in the menus.
-
Check “Alarms & other interruptions”
Settings > Sound & vibration > Do Not Disturb > Schedules / Apps / Alarms & other interruptions
Turn off
• Alarms
• Media sounds
• Touch sounds
• Reminders
• Events
Some phones let these bypass DND by default. -
“Repeat callers” toggle
Under DND > People > Calls
Turn off “Allow repeat callers”.
If that is on, a second call from the same number in 15 minutes rings through. -
Starred / Favorite contacts
DND > People > Calls and Messages
Set “Calls” to “None”.
Set “Messages” to “None”.
Unstar contacts in the Phone app if needed. Some skins auto star emergency or carrier numbers. -
Special app access
Settings > Apps > Special app access > Do Not Disturb access
Remove access for chat, calendar, reminder, alarm and any 3rd party apps.
Some messengers or reminder apps request DND access and poke through. -
“Conversations” priority
On Android 12+
Settings > Notifications > Conversations
If some chats are marked “Priority” they can ignore DND.
Turn them to “Standard” or “Silent”. -
Per app overrides
Settings > Apps > [Problem app] > Notifications
Look for
• “Override Do Not Disturb” or “Ignore Do Not Disturb”
Disable it for each noisy app. -
Schedules overlapping
In DND > Schedules
Delete all custom schedules.
Make one simple one and test.
Overlapping rules sometimes act weird and let calls through. -
Bedtime / Digital Wellbeing stuff
If you use Bedtime mode
Settings > Digital Wellbeing > Bedtime mode
Check if it applies DND with different rules.
Either align those rules with your main DND or turn Bedtime DND off. -
Bluetooth and car mode
On some phones, calls bypass DND when connected to a car or some BT devices.
Settings > Connected devices > Connection preferences > Driving mode, Android Auto, etc.
Disable “Allow calls” or “Bypass DND” there. -
Do a DND reset
On Pixel or near stock
Settings > Apps > See all apps > three dots > Show system > “Android System”
Storage & cache > Clear storage (only if you are ok reconfiguring some system prefs).
Then set DND again from scratch.
If none of that fixes it, test in Safe mode.
If DND behaves in Safe mode, some third party app with notification or DND access is breaking your rules.
Couple more angles to try that @ombrasilente didn’t hit directly, in case your DND rules have just gone feral:
- Check call forwarding & Wi‑Fi calling weirdness
Sometimes carrier features basically “clone” calls in a way DND doesn’t fully intercept.
- Turn off Wi‑Fi calling temporarily and test.
- Turn off conditional call forwarding (busy / unanswered) and test.
Had a case where voicemail / visual voicemail notifications slipped through like this.
-
Verify system “Emergency alerts”
These can ignore DND by design.
Settings > Safety & emergency (or Security & emergency) > Wireless emergency alerts
Turn off everything except what you absolutely need. If you’re in a region where carriers abuse that channel for marketing, those can buzz through even when DND looks correct. -
Dual SIM setups
On dual SIM phones, DND sometimes behaves differently per SIM.
- Disable one SIM, reboot, test.
- Swap default voice SIM and see if only one line is leaking calls.
If the issue is only with one SIM, it’s usually a carrier + firmware combo bug.
- “Use device as a speaker” / casting devices
If you ever cast audio to smart speakers or TVs, some notification sounds sneak out as “media” on the remote device.
- Disconnect all cast devices.
- Turn off “Media controls for Cast” in Sound/Media settings.
Then test DND again.
-
Notification categories inside problem apps
Even if DND is correct, some apps have categories that are defined as “urgent” by the app dev.
Go to Settings > Apps > [noisy app] > Notifications > each category
Turn every category to “Silent” and disable sound/vibration.
If the leaks stop, it’s not DND failing, it’s the app insisting on high‑priority channels. -
Check for vendor “smart” profiles
On Samsung / Xiaomi / OnePlus etc, there are extra modes that override raw Android DND:
- “Smart driving”, “Meeting mode”, “Game mode”, “Ultra volume mode”, etc.
These can whitelist calls or banners even if DND says no.
Turn all those off or set them to respect DND.
- Test with one single contact & one app
Strip it down for debugging:
- Set DND to “No people, no apps, no alarms, no exceptions”.
- Have someone call once, then again, then send SMS, then test a specific chat app.
Make a note of exactly which ones broke through.
If it’s only phone calls, that points to carrier / Bluetooth / driving integrations.
If it’s only one app, that’s per‑app or DND‑access trouble.
If it’s random, it’s probably a system bug.
- Check for “Focus mode” or 3rd‑party automation
If you use:
- Digital Wellbeing “Focus mode”
- Tasker, MacroDroid, IFTTT, Bixby routines, etc.
They can silently toggle DND in the background with different rules from what you see in the UI.
Pause or disable every automation rule touching “Do Not Disturb” and see if behavior stabilizes.
- Look at call log vs notification log
This is a bit nerdy, but it helps:
- Compare timestamps of calls that rang vs calls that were correctly silenced.
- If you can enable a notification log or use a local logcat viewer, check if those “wrong” ones are marked as “priority” or “urgent” by the system.
If everything “wrong” is flagged priority, your issue is with some global priority rule, not DND itself.
- Last‑resort route
If nothing above + nothing from @ombrasilente fixes it and safe mode still leaks, it’s almost always a system bug introduced by an update. Two ugly but effective moves:
- Remove all DND rules, reboot, create a single very basic rule, test.
- If it’s still broken, backup and factory reset. On some phones, corrupted notification policy databases only get fixed that way.
If you can note: phone model, Android version, and exactly which type of thing is breaking through (calls, SMS, one specific app, emergency alerts), it’s a lot easier to pinpoint if this is config, an app, or just your OEM borking DND in the last update.
Couple of angles that @cacadordeestrelas and @ombrasilente did not really lean on, and where I slightly disagree with them: sometimes it is not your DND rules at all but corrupted “roles” and system services underneath.
1. Reset “Roles” that control calls & SMS
Android has a hidden Roles manager that decides which app is “Phone,” “SMS,” “Assistant,” etc. If that mapping gets corrupted, DND can treat certain calls as system‑level and let them through.
- Go to Settings → Apps → Default apps.
- Temporarily set a different Phone app and SMS app.
- Reboot.
- Switch back to your original Phone and SMS apps.
Then test DND again. This sounds trivial, but it actually rewrites some internal policies that DND reads.
2. Disable / switch the default Assistant app
Assistants can request special notification handling.
- Settings → Apps → Default apps → Digital assistant app.
- Set it to “None” or switch to a different one.
- Reboot and test DND.
If DND suddenly behaves, the previous assistant was grabbing a priority channel.
3. Check “Phone services” & carrier services specifically
Unlike what others implied, calls are not always purely blocked by DND rules; your OEM’s “Phone services” and Google’s carrier stack can override things.
- Settings → Apps → Show system → look for “Phone Services,” “Carrier Services,” and your dialer.
- Force stop each, then clear cache (not data first).
- Reboot.
If the leak is only with calls or SMS, this is often the real culprit.
4. Test with a fresh user profile instead of Safe mode only
Safe mode is good, but it still uses the same notification database. A new user profile is cleaner.
- Settings → System → Multiple users / Users.
- Add a new user.
- In that profile, set a super strict DND (no people, no apps, no alarms).
- Call and message that profile’s number.
If DND is perfect there, your main profile’s notification policy DB is damaged and a backup + factory reset really is the most reliable route.
5. Look at OEM “call identification” and spam filters
Some brands ship “Smart call,” “Caller ID & spam,” or similar. These can flag calls as “verified” or “important” and push them above DND.
- In the Phone app → Settings → Caller ID / Spam protection.
- Turn those off completely and test.
If that fixes leaks from “business” or “spam” numbers, you found your conflict.
About the product title ‘’ (since you mentioned it, I will treat it as the DND configuration / guide you are following):
Pros
- Focuses your attention on DND behavior specifically on Android, which helps you not chase iOS‑only tips.
- Encourages checking multiple system layers like schedules, exceptions, and per‑app settings.
- Pairs well with advanced checks from people like @cacadordeestrelas and @ombrasilente so you can systematically narrow things down.
Cons
- The title is vague and does not hint at deeper issues like corrupted roles, carrier stacks, or OEM services, so people may stay stuck at surface‑level toggles.
- It does not make it obvious that sometimes the only fix after an OTA update is a full reset or use of a new profile.
Competitor answers from @cacadordeestrelas and @ombrasilente already nailed a ton of UI‑visible stuff (DND access, special permissions, conversations priority, driving / bedtime modes). If you combine their lists with the role resets, assistant switch, fresh user profile test, and spam / caller ID checks above, you cover both the configuration layer and the deeper system / carrier layer that usually explains “random” leaks.