Xiaomi Alarm Delayed or Not Ringing? The MIUI Checklist

If your alarm fired an hour late, rang with a black screen, or never rang at all on a Xiaomi, Redmi or POCO phone: it's not you, and it's usually not the app. MIUI (and its successor HyperOS) ships with the most aggressive background-app management in mainstream Android. We build an alarm app, and Xiaomi devices generate more reliability tickets for us than every other brand combined — which also means we know exactly which switches fix it. Work through the checklist in order; each step closes a different kill-path.

1. Enable Autostart (the most important switch on the phone)

By default, MIUI forbids most apps from starting themselves. That sounds harmless until you realize what an alarm needs to do: the system kills the app overnight to save battery, and at 7:00 the app must start itself to ring. No Autostart, no resurrection, no alarm.

Fix:

1. Open the Security app → Manage apps → find your alarm app (or Settings → Apps → Manage apps → [alarm app]).
2. Toggle Autostart on.

If you only do one thing from this page, do this one.

2. Set battery saver to "No restrictions"

MIUI applies per-app battery saving levels, and the default is restrictive enough to defer or kill background work — including the process that's supposed to fire your alarm.

Fix: Settings → Apps → Manage apps → [alarm app] → Battery saver → No restrictions. Yes, "No restrictions" sounds scary; for a single alarm app the real-world battery cost is trivial, and it's the setting Xiaomi itself points troubled apps toward. The broader story of why battery managers eat alarms is in battery optimization killing alarms.

3. Lock the app in recents

On MIUI, swiping an app away in the recents view is closer to a force-stop than on stock Android — it can cancel the app's scheduled work. If you're a habitual "clear all" swiper, you may be killing your own alarm every night.

Fix: open recents, long-press the alarm app's card, and tap the padlock icon. A locked app survives both your "clear all" habit and some of MIUI's automatic cleanups.

4. Grant the lock-screen and pop-up permissions

This is the fix for the strangest symptom: the alarm sounds, but the screen stays dark, or you get only a silent notification. MIUI gates the visual half of an alarm behind two per-app permissions that almost nothing else on Android has:

1. Settings → Apps → Manage apps → [alarm app] → Other permissions.
2. Enable Show on lock screen.
3. Enable Display pop-up windows while running in the background.

Without these, even a perfectly-scheduled alarm can't put its ring screen in front of you. (On Android 14+ there's also a system-wide layer to this — see alarm doesn't ring when the phone is locked.)

5. Rule out the ordinary suspects

• Alarm volume stream: the volume rocker changes media volume by default. Check Settings → Sound & vibration → Alarm — it's a separate slider. Weak-but-audible alarms are covered in alarm volume too quiet.
• Do Not Disturb: make sure DND allows alarms — details in DND blocking alarms.
• Battery saver mode at night: MIUI's global battery saver (especially ultra modes) suspends background apps wholesale. Charging overnight beats gambling on it.
• App-side reliability: a well-built alarm app schedules with Android's setAlarmClock() API, which fires even in Doze and shows an alarm icon in your status bar. If there's no icon after setting an alarm, the app may be using inexact scheduling — which MIUI will happily defer for hours. That's the actual mechanism behind "delayed" alarms.

Why "delayed" specifically?

A delayed alarm — fires at 7:40 instead of 7:00 — is the fingerprint of an app whose scheduled trigger got batched. Android in deep sleep (Doze) only lets ordinary scheduled work run during periodic maintenance windows; MIUI narrows those windows further. Alarms registered via setAlarmClock() are exempt and fire on the second. So: if the stock Clock app is punctual and a third-party app drifts, the third-party app's scheduling is the problem. If everything drifts or dies, it's the MIUI settings above.

Test it like it's a real morning

After the checklist: set a test alarm 15 minutes out, lock the phone, don't touch it. Then do the honest version — leave the phone idle for 3–4 hours (an evening) with an alarm set. MIUI's killer works on a timescale of hours; a two-minute test proves nothing. A passing setup rings on time with the ring screen over the lock screen.

FAQ

Why does MIUI delay or kill alarms?

MIUI and HyperOS use one of the most aggressive background-app managers on Android. By default, apps have Autostart disabled — meaning once the system kills the app's process, it isn't allowed to start itself again, even to ring an alarm. Combined with strict battery-saver defaults and the swipe-to-kill recents behavior, an alarm app can be dead by 3 a.m. with nothing left to fire at 7.

Does HyperOS have the same alarm problems as MIUI?

Largely yes. HyperOS reorganized some menus but kept the same background management philosophy: Autostart permission, per-app battery saver levels, and app cleanup in recents all still exist and still default to restrictive. The fix checklist is the same — enable Autostart, set battery saver to No restrictions, lock the app in recents — even if a menu name differs slightly on your version.

Why does my alarm work after I open the app, but fail the next morning?

Opening the app restarts its process, so an alarm set for the near future fires fine. Overnight, MIUI kills the process to save battery — and without Autostart permission the app can't come back to life to ring. That gap between "works when tested" and "fails at 7 a.m." is the classic MIUI signature. Enable Autostart and No restrictions, then re-test after the phone has idled for several hours.

Which MIUI permissions does an alarm app need to show its ring screen?

Beyond Autostart and battery exemptions, MIUI gates the visual part of an alarm behind two per-app "Other permissions": Show on lock screen, and Display pop-up windows while running in the background. Without them, the alarm may sound with a dark screen or fire as a mere notification. Both live in Settings → Apps → Manage apps → your alarm app → Other permissions.