Home › Guides › Android Alarm Permissions Guide

Android Alarm Permissions: The Complete Setup Guide

By the AVA Team · Updated July 17, 2026

A silent Android alarm is almost always a permissions problem, and there are exactly five layers to check: (1) notifications allowed, (2) "Alarms & reminders" granted, (3) full-screen notifications allowed (Android 14+, fixes "rings but screen stays black"), (4) battery optimization off — plus Autostart on Xiaomi — and (5) the separate alarm volume stream turned up with alarms excepted from DND. Work top to bottom, then run a two-minute test alarm with the screen locked.

We build an alarm app for a living, and the hardest lesson of that job is this: on modern Android, an alarm that rings reliably is not the default — it's the reward for getting five separate settings right. Miss one and you get the classic ghost failures: the alarm that never fires, the alarm that "rings" as a silent notification, the alarm that dies with the app overnight. This guide is the checklist we walk our own users through, written to work for any alarm app, not just ours.

Layer 1: Notifications (Android 13+)

Since Android 13, apps must ask permission just to post notifications — and an alarm is, at the system level, a very loud notification. If you tapped "Don't allow" during first launch (easy to do on reflex), many alarm apps lose their voice entirely.

Check: Settings → Apps → your alarm app → Notifications → allowed, and make sure the alarm-related notification channel isn't individually muted.

Layer 2: Alarms & reminders (exact alarms)

Android schedules most app work loosely, batching it to save battery. Alarms obviously can't be "roughly 7 a.m.", so exact scheduling is gated behind a special permission labeled "Alarms & reminders." A well-built app requests it and then uses Android's setAlarmClock() API — the strongest scheduling guarantee the OS offers. It fires even in Doze (deep power saving) and puts a small alarm icon in your status bar.

Check: Settings → Apps → your alarm app → Alarms & reminders → Allow. Verify: after setting an alarm, look for the status-bar alarm icon. That icon is your nightly proof the alarm is truly scheduled — no icon, no alarm.

Layer 3: Full-screen intent — the "rings but no screen" bug

This is the sneakiest one. Starting with Android 14, the full-screen ring experience — the big dismiss screen that takes over your lock screen — is gated behind its own special permission for apps installed from the Play Store. Without it, the alarm may fire on time and yet only post a small notification, in the worst cases effectively silent. From the bed, that's indistinguishable from no alarm at all.

Check: good alarm apps prompt you for this during setup (AVA does, proactively). If you skipped it: Settings → Apps → your alarm app → look for "Full-screen notifications" / "Display over other apps" and allow it. Verify: set a test alarm two minutes out, lock the phone, and confirm the full ring screen appears over the lock screen — not just a chime in the notification shade.

Layer 4: Battery managers — where alarms go to die

Stock Android's battery optimization is fairly polite. Manufacturer skins are not. MIUI (Xiaomi, Redmi, POCO) is the most notorious: its battery manager kills background apps overnight by design, and third-party alarm apps are prime targets. Some Samsung and OnePlus power modes do the same under names like "deep sleeping apps."

The fix, in order of impact:

Exempt the app from battery optimization. Settings → Apps → your alarm app → Battery → Unrestricted (or "Don't optimize"). The cost is negligible — an alarm app idles almost all day.
Xiaomi/MIUI extras: enable Autostart for the app (Security app → Permissions → Autostart) and set battery saver for the app to "No restrictions."
Lock the app in recents: open the recent-apps view, long-press or pull down on the alarm app's card, and tap the lock/pin icon so "clear all" can't kill it.
Samsung: make sure the app isn't in "Sleeping" or "Deep sleeping" apps (Settings → Battery → Background usage limits), and add it to "Never sleeping apps."
Avoid extreme battery-saver modes overnight — several of them suspend everything but calls.

Layer 5: Volume and Do Not Disturb

Two sound facts most people never learn until they oversleep:

Alarm volume is its own stream. Android keeps separate sliders for media, ring, and alarm. Turning media or ring volume up (or down) does nothing to alarms. Settings → Sound → drag the Alarm slider specifically. This is the number-one cause of "too quiet" alarms — more on getting sound right in our loud alarm sounds guide and escalating volume setup.
DND has an alarm exception — if everything cooperates. Alarms ring through Do Not Disturb only when the app plays through the proper alarm audio stream and your DND config allows alarms (the default). If you or a "sleep mode" routine customized DND, confirm alarms are still listed as an exception under Settings → Sound → Do Not Disturb.

The 2-minute test that proves the whole stack

After any change — and after every major Android update, which can quietly reset these — run one end-to-end test: set an alarm two minutes out, enable DND, lock the phone, put it down. You should get full alarm volume and the full-screen ring over the lock screen. If you do, all five layers are healthy. If you don't, the layer that failed is now obvious. If alarms pass this test and you still sleep through them, the phone isn't your problem — start with why you sleep through your alarm or, if it never rang because the battery hit zero, the dead-phone playbook. And when choosing an app to trust with all this, our roundup of the best free alarm apps for Android notes which ones handle these permissions gracefully.

An alarm built for modern Android

AVA uses setAlarmClock(), asks for the full-screen permission proactively, and rings over the lock screen with a new AI-voice wake-up tied to your goals. Free to start — set up in two minutes.

Get AVA on Google Play — Free

FAQ

Why does my alarm ring but the screen stays black?

That's the full-screen intent permission. Starting with Android 14, the big over-the-lock-screen ring experience is gated behind a special permission — without it, the alarm may only post a small notification, sometimes silently. In your alarm app's settings look for a prompt about full-screen notifications, or check Settings → Apps → your alarm app and allow full-screen notifications. Grant it, then test with a two-minute alarm while the phone is locked.

Why did my alarms stop working after an Android update?

Major Android updates regularly tighten background-app rules and occasionally reset special permissions. After any big update, re-check four things: the "Alarms & reminders" permission is still granted, notifications are still allowed, the app is still exempt from battery optimization, and on Xiaomi that Autostart survived the update. A two-minute test alarm with the screen locked confirms everything in one shot.

Should I disable battery optimization for my alarm app?

Yes. Battery optimization exists to kill background apps, and on aggressive skins like MIUI it will happily kill your alarm app overnight. Exempting one alarm app costs a negligible amount of battery — the app spends almost all its time idle — and removes the single most common cause of silently missed alarms on Xiaomi, and on some Samsung and OnePlus power modes. On Xiaomi, also enable Autostart and lock the app in the recents screen.

Does Do Not Disturb silence alarms on Android?

Not if two conditions hold: the app plays through the dedicated alarm audio stream, and your DND configuration allows alarms — which is the default. Alarms have a dedicated exception in Android's DND system precisely so you can silence the world at night and still wake up. If alarms are silent under DND, check Settings → Sound → Do Not Disturb and confirm alarms are listed as an exception, then verify the alarm volume slider — a separate stream from media and ring — is up.