Android Alarm Not Going Off? The 7 Real Causes, Ranked

If you woke up late this morning to a phone that never made a sound, you want two things: to know why, and to make sure it never happens again. We build an alarm app for a living, and "the alarm didn't go off" is the single bug class we've spent the most engineering time on — so this guide is ranked by what actually causes it in the real world, not by what's easiest to write about. Work down the list; most people find their culprit in the first three.

1. A battery manager killed your alarm app overnight (most likely)

Android phones aggressively shut down background apps to save power. Stock Android's Doze mode is relatively polite about it, but manufacturer skins — Xiaomi's MIUI/HyperOS, some Samsung and OnePlus power modes — go much further and simply kill apps that haven't been used for a few hours. If the alarm app's process is dead and the system refuses to restart it, there is nothing left to ring.

Fix:

1. Open Settings → Apps → [your alarm app] → Battery and set it to Unrestricted (wording varies: "Don't optimize", "No restrictions").
2. On Xiaomi/Redmi/POCO, additionally enable Autostart for the app and lock it in the recents view — we cover the exact taps in our MIUI alarm guide.
3. On Samsung, remove the app from Sleeping apps and Deep sleeping apps — full steps in the Samsung alarm guide.

The deep dive on why this happens (Doze, standby buckets, OEM killers) is in battery optimization killing alarms.

2. The alarm volume stream was at zero

Android keeps four separate volume sliders: media, ring, notifications, and alarm. The volume rocker on most phones changes media volume by default — so you can have music at full blast and the alarm stream muted without ever knowing. The alarm "went off" last night; it just went off silently.

Fix: open Settings → Sound & vibration and drag the Alarm volume slider (it's its own slider) to at least 70%. Then set a test alarm one minute out and confirm you hear it. If it's audible but weak, see why your Android alarm is too quiet.

3. Do Not Disturb swallowed it

DND has a dedicated exception for alarms — but only if two things are true: your DND configuration actually allows alarms, and the app plays its sound on the proper alarm audio stream. If either fails (a strict custom DND schedule, or an app that plays wake-up audio as ordinary media), DND mutes your morning.

Fix: go to Settings → Sound → Do Not Disturb → Alarms & other interruptions (naming varies) and make sure Alarms is allowed. Also check Bedtime mode / Modes schedules that switch DND on overnight. Full walkthrough: Do Not Disturb blocking alarms.

4. Android 14+ blocked the ring screen ("fired but silent")

Since Android 14, the full-screen alarm experience is gated behind special permissions — the "Alarms & reminders" special access and the full-screen-intent permission. Without them, an alarm can degrade into a quiet notification sitting in your shade instead of a ringing screen. In our own engineering we've chased exactly this "rings but no screen" bug class; it's real and it's common after OS updates.

Fix: open Settings → Apps → Special app access → Alarms & reminders and enable it for your alarm app. If your alarm only misbehaves when the phone is locked, read alarm doesn't ring when phone is locked — it's the dedicated guide for this failure.

5. The app uses the wrong alarm API

This one you can't fix in settings — it's on the app developer. Android offers several ways to schedule future work, and only one of them is truly reliable for alarms: the setAlarmClock() API. It fires even in Doze deep sleep and shows the little alarm icon in your status bar. Apps that schedule wake-ups with ordinary jobs or inexact alarms get batched and deferred — sometimes by hours.

Fix / check: after setting an alarm, look at your status bar. No alarm-clock icon usually means the app isn't registering a proper alarm with the system. If a third-party app repeatedly fires late or not at all on a phone where the built-in Clock works, switch apps — that's a design flaw, not a settings problem.

6. A plain scheduling mistake

Unglamorous, but it fills support inboxes: alarm set for PM instead of AM, a one-time alarm that already fired yesterday, repeat days not including today (weekday-only alarms on a Saturday shift), or the alarm created in a second user profile or cloned app that wasn't running.

Fix: open the alarm and read it slowly — time, AM/PM, repeat days, and whether it's actually toggled on. It takes twenty seconds and rules out an embarrassing share of cases.

7. The app was force-stopped or updated overnight

Force-stopping an app from Settings cancels all of its scheduled alarms until you next open it. Some phones' "clean up" buttons do the same thing under a friendlier name. Separately, a Play Store auto-update in the small hours can briefly kill the app; well-built alarm apps re-register alarms immediately after an update, but not all do.

Fix: never force-stop your alarm app, avoid overnight "boost"/"clean" utilities, and open the alarm app once after any update so it can reschedule.

The 60-second test before you sleep

1. Set a test alarm 10–15 minutes out.
2. Lock the phone. Don't touch it — an open app or lit screen invalidates the test.
3. It should ring on time, at full alarm volume, with the screen lighting up over the lock screen and the alarm icon visible in the status bar beforehand.

If that passes but mornings still fail, the killer is time-dependent — battery managers usually strike after hours of idle, which points you back to cause #1.

FAQ

Why did my alarm not go off even though it was set?

The most common cause is that your phone's battery manager killed the alarm app overnight, so nothing was left running to fire it. Other frequent causes: the alarm volume stream (separate from media volume) was at zero, Do Not Disturb was configured without the alarms exception, or on Android 14+ the app lacked the special permission to show a full-screen alarm — so it fired as a silent notification you slept through.

Does force-stopping an app cancel its alarms?

Yes. When you force-stop an app from Settings, Android cancels all of that app's scheduled alarms and the app cannot reschedule them until you open it again. Some aggressive phone brands treat swiping an app away in recents almost like a force-stop, which produces the same missed-alarm result. Never force-stop your alarm app before bed.

Will my alarm go off if my phone is powered off?

On almost all modern Android phones, no — a powered-down phone runs no software, so no app alarm can fire. A few brands offer a scheduled power-on feature that boots the phone before the alarm time, but it is the exception. If your battery is low at night, charge the phone rather than relying on an alarm surviving a shutdown.

How do I test whether my alarm will actually work tomorrow?

Set a test alarm 10–15 minutes out, then lock the phone and leave it completely untouched — don't keep the screen on and don't keep the alarm app open, because that defeats the point of the test. If it rings on time with the screen lighting up, your setup survives Doze. For a stricter test, repeat it after the phone has sat idle for a few hours, which is when battery killers strike.