Samsung Alarm Not Working? Start With Sleeping Apps

Samsung phones are unusually good at one thing that ruins mornings: putting apps to sleep without telling you. If your alarm failed today — especially if it's a third-party alarm app while Samsung's built-in Clock seems fine — the odds are very high that One UI decided your alarm app was "unused" and cut its background access. Here's every cause we see on Galaxy devices, ranked, with the exact One UI menu paths. (Menu names below match recent One UI versions; older versions word things slightly differently but the structure is the same.)

1. Sleeping apps and Deep sleeping apps (the big one)

One UI ships with "Put unused apps to sleep" turned on. Any app you haven't opened for a few days gets auto-moved to the Sleeping apps list (background work throttled) and eventually to Deep sleeping apps (background work banned entirely). An alarm app is a perfect victim: you set it once and never "use" it again — you just expect it to ring. To One UI, that looks like an unused app.

Fix — takes two minutes:

1. Open Settings → Battery and device care → Battery → Background usage limits.
2. Tap Sleeping apps and Deep sleeping apps. If your alarm app is in either list, remove it.
3. Tap Never sleeping apps → Add apps and add your alarm app. This is the step that stops One UI re-sleeping it next week.
4. Optionally turn off Put unused apps to sleep altogether if you'd rather manage it yourself.

In our testing this single change resolves the majority of "alarm works for a week, then stops" reports on Galaxy phones. The general Android version of this problem — Doze, buckets, other brands — is covered in battery optimization killing alarms.

2. Battery optimization on the app itself

Separate from sleep lists, each app has its own battery setting. If it's on "Optimized" (the default) the system may defer its background work; "Restricted" is worse.

Fix: Settings → Apps → [your alarm app] → Battery → Unrestricted. A well-engineered alarm app that schedules through Android's setAlarmClock() API will fire through Doze even without this — but Unrestricted removes the remaining failure modes, and the battery cost of one alarm app is negligible.

3. Bedtime mode or a scheduled Mode muted the night

One UI's Modes and Routines (Sleep mode/Bedtime mode) can switch on Do Not Disturb, grayscale, and sound restrictions on a schedule. DND is supposed to let alarms through — Android has a dedicated alarm exception — but that only holds if the exception is enabled and the app rings on the proper alarm audio stream.

Fix: open Settings → Modes and Routines and inspect anything scheduled overnight. Then Settings → Notifications → Do not disturb and confirm Alarms is in the allowed list. The full logic of DND vs alarms is in Do Not Disturb blocking alarms.

4. The Alarm volume slider is down

Samsung, like all Android, keeps alarm volume on its own stream — the volume rocker normally moves media volume, not alarm volume. It's entirely possible to have a loud phone and a silent alarm.

Fix: Settings → Sounds and vibration → Volume — you'll see four sliders; raise Alarm specifically. If alarms ring but weakly, our guide on alarm volume too quiet on Android covers fade-in ramps and tone choice, and loud alarm sounds helps you pick something with more punch.

5. The alarm fires but the screen stays dark

On Android 14 and later, showing a full-screen ring screen over the lock screen requires special permission. Without it, the alarm may arrive as a quiet notification — technically "fired," practically useless. Check Settings → Apps → [alarm app] → Alarms & reminders and the app's notification settings. This whole failure class has its own guide: alarm doesn't ring when the phone is locked.

6. Housekeeping causes

• Force-stop / "clean now" buttons: Device care's optimization sweep and any force-stop cancels the app's scheduled alarms until you reopen it. Don't run cleaners at bedtime.
• Power saving mode: Samsung's stronger power-saving profiles limit background activity broadly. If you enable one on a low battery night, exempt your alarm app first — or charge instead.
• Simple scheduling slips: AM/PM, repeat days, an alarm left toggled off. Twenty seconds of reading the alarm rules this out.

Verify it's fixed

Set a test alarm 10–15 minutes out, lock the phone, and don't touch it. For the strict version, test again after the phone has idled a few hours — that's when sleep lists bite. A reliable setup rings on time, at full alarm volume, with the ring screen appearing over the lock screen. If you sleep through alarms even when they ring properly, that's a different battle — see heavy sleeper alarm tips.

FAQ

Why does my Samsung keep putting my alarm app to sleep?

One UI ships with "Put unused apps to sleep" enabled. If you haven't opened an app for a few days, Samsung automatically moves it to the Sleeping apps list — and later to Deep sleeping apps, where it can't run in the background at all. An alarm app you only interact with at 7 a.m. looks "unused" to this system. The fix is to add it to the Never sleeping apps list so One UI stops auto-sleeping it.

Does Samsung's built-in Clock app get killed too?

Practically never — Samsung's own Clock is a system app that One UI's battery management leaves alone. That's why the classic symptom is "the built-in alarm works but my alarm app doesn't." It isn't proof the third-party app is broken; it usually means One UI put it to sleep. Exempt the app from sleeping and battery limits and it should behave like the built-in one.

Why does my Samsung alarm work some days and not others?

Intermittent failure is the signature of automatic sleep lists. Days you open the alarm app, it counts as recently used and survives the night; after a few days of not opening it, One UI moves it to Sleeping apps and the next alarm dies. Bedtime mode schedules and weekend Do Not Disturb routines produce the same some-days pattern. Check Never sleeping apps first, then your Modes schedule.

What is the difference between Sleeping apps and Deep sleeping apps?

Sleeping apps can only run in the background occasionally — enough to break time-critical alarms. Deep sleeping apps never run in the background: they only work while you have them open on screen, which makes a morning alarm impossible. Both lists live in Settings under Battery → Background usage limits. An alarm app belongs in neither; put it in Never sleeping apps.