Is Do Not Disturb Blocking Your Alarm? Here's How the Exception Really Works
Do Not Disturb has a deal with your alarm clock: notifications shut up, alarms still ring. That deal is honored by the operating system — but it has fine print, and the fine print is where mornings die. If your alarm didn't ring and DND was on, don't just turn DND off forever (it's genuinely good for sleep). Understand which clause broke, fix that one setting, and keep both your quiet nights and your loud mornings. We build an alarm app; below is the exact model we use when debugging DND reports, ranked by how often each cause turns out to be the culprit.
How the alarm exception actually works
Two conditions must both hold for an alarm to ring under DND:
- Your DND configuration allows alarms. Android exposes exceptions ("interruptions") for alarms, media, calls, and so on. Alarms are allowed by default — but the toggle exists and people flip it, often while chasing total silence for a nap.
- The app plays sound on the alarm audio stream. Android routes audio through separate streams — media, ring, notification, alarm. DND's alarm exception applies to the alarm stream, not to whatever noise an app makes. An app that plays its wake-up audio as ordinary media is, from DND's point of view, a podcast at 7 a.m. — muted.
Every DND alarm failure is a violation of one of those two conditions. Now the fixes.
Fix 1: Re-enable the Alarms exception (30 seconds)
- Open Settings → Sound & vibration → Do Not Disturb (Samsung: Settings → Notifications → Do not disturb).
- Find the exceptions section — wording varies: "Alarms & other interruptions", "Allowed during Do not disturb", "Hide notifications vs. mute sounds".
- Make sure Alarms is allowed. While you're here, decide deliberately about Media — some wake-up apps that play music need it (see Fix 3).
Fix 2: Audit the schedules that switch DND on for you
Plenty of people "never use DND" and have it on eight hours a night anyway — via Bedtime mode (Digital Wellbeing), a Sleep mode, or a Samsung Modes & Routines schedule. The trap: a schedule can apply its own DND profile, stricter than the one you just checked manually.
- Open Digital Wellbeing → Bedtime mode and, on Samsung, Settings → Modes and Routines.
- For each overnight schedule, open its sound/DND settings and verify alarms are allowed inside the schedule's own config.
- Check the schedule's end time, too — a mode that ends at 7:30 with a 7:00 alarm has failure modes a mode ending at 6:00 doesn't.
If your alarm only fails on certain days, a schedule is almost certainly involved — the same intermittent signature as Samsung's sleeping apps, but with a calendar instead of an app list. Night-shift workers juggling reversed schedules deal with this constantly; our night shift sleep guide covers building a daytime-sleep setup that doesn't eat alarms.
Fix 3: The app is on the wrong audio stream
The diagnostic is beautifully simple: set a test alarm in your third-party app and one in the built-in Clock, turn DND on, and see which rings. If stock rings and the third-party app stays silent, that app plays its audio as media — and no amount of settings-flipping on your side fully fixes an app that talks to the wrong stream.
Your options, honestly ranked:
- Best: use an alarm app that plays on the alarm stream, as an alarm should. (This is table stakes for anything calling itself an alarm clock — AVA does it, stock clocks do it, the good third parties do it.)
- Workaround: allow Media through your DND exceptions. It works, but it also un-mutes every other media sound overnight — messages previews with sound, videos autoplaying, the lot.
- Fragile: exclude the hours around your alarm from the DND schedule. Works until your wake time changes.
Fix 4: Rule out the neighbors of DND
Three problems get misdiagnosed as "DND blocked my alarm":
- Alarm volume at zero. The alarm stream slider is separate from everything else; DND gets blamed for what a muted slider did. Check alarm volume too quiet.
- The app was dead by morning. Battery managers kill alarm apps overnight; the silence has nothing to do with DND. See battery optimization killing alarms.
- The alarm fired but silently notified. On Android 14+, a missing full-screen permission turns a ring into a mute notification — details in alarm doesn't ring when phone locked.
The right nightly setup
DND on a schedule is worth keeping — fewer 2 a.m. wake-ups from group chats measurably improves sleep. The stable configuration: DND scheduled for your sleep window, Alarms allowed, an alarm app that uses the alarm stream, alarm volume at 80%+, and one test run with DND deliberately on. Do the test once and you'll never wonder again — set an alarm two minutes out, enable DND, lock the phone. It should ring like DND doesn't exist. For its part, a properly built alarm rings through DND by design, not by luck.
An alarm that honors the deal
AVA plays on Android's alarm stream, rings through Do Not Disturb, and launches its ring screen over the lock screen — the reliability engineering is the product. What you wake to is an AI voice speech about your goals, not a beep. 7 free AI wake-ups a month, then $9.99/mo or $65.99/yr.
Get AVA on Google Play — FreeFAQ
Will my alarm go off if Do Not Disturb is on?
Usually yes. Android's DND has a dedicated alarm exception, enabled by default, and alarms that play on the system's alarm audio stream ring straight through DND. Your alarm fails only when that chain breaks: the alarms exception was switched off in a custom DND setup, or the alarm app plays its sound as ordinary media, which DND mutes. Thirty seconds in Settings confirms which case you're in.
How do I allow alarms through Do Not Disturb?
Open Settings → Sound and vibration → Do Not Disturb. Look for the exceptions or interruptions section — on recent Android it's phrased like "Alarms and other interruptions"; on Samsung it's under "Allowed during Do not disturb". Make sure Alarms is toggled on. Repeat the check inside any Bedtime mode or scheduled Mode you use, because schedules can carry their own stricter exception sets.
Why did DND silence my third-party alarm app but not the built-in clock?
The DND alarm exception applies to sound played on the alarm audio stream, not to any noise an app happens to make. Built-in clock apps always use the alarm stream. A third-party app that plays its wake-up audio as media — common with music-based or streaming wake-up apps — gets muted like any other media under DND. If the stock alarm rings through DND and your app doesn't, the app is on the wrong stream; the only real fix is an app that does it correctly.
Does Bedtime mode block alarms?
Bedtime mode itself is mostly a scheduler: it turns on DND and screen changes overnight. Alarms should still ring — provided the DND configuration it applies keeps the alarms exception enabled. The risk is that Bedtime mode applies a stricter DND profile than the one you checked manually, or that it's set to end after your alarm time with unusual combinations. Open the Bedtime mode settings and verify its DND allows alarms.