Alarm Goes Off But No Sound? Find the Mute in 6 Checks

A silent alarm is actually good diagnostic news: scheduling, battery settings and permissions all did their job — the alarm fired. Something between the app and your speaker ate the sound. That's a much shorter list of suspects than a fully dead alarm, and every one of them is fixable in under two minutes. We build an alarm app; the "fired silently" report is one we've debugged so many times (including in our own code — more on that below) that the checklist writes itself. If instead nothing at all happened this morning, start with the broader guide: Android alarm not going off.

1. The alarm volume stream is at zero

Android keeps four independent volumes — media, ring, notifications, and alarm. The volume rocker adjusts media by default, so weeks of volume-button presses never touch the alarm stream, and one accidental drag in a settings panel can zero it without you noticing. This is the most common cause of a silent alarm, full stop.

Fix: Settings → Sound & vibration → find the dedicated Alarm volume slider → set it to 70%+. Tip: in many Clock apps, pressing the volume rocker while on the alarm screen adjusts alarm volume directly. If your alarm rings but weakly, that's a different fine-tuning problem — see alarm volume too quiet on Android.

2. The alarm itself is set to vibrate-only or "None"

Each alarm carries its own sound setting, and it's surprisingly easy to end up with a silent one: you experimented with settings, an app update reset preferences, or a "vibrate" toggle got flipped. The alarm dutifully fires — and buzzes.

Fix: open the alarm in your app, tap its sound/ringtone row, and confirm a real tone is selected and any "vibrate only" or "silent" option is off. Then play the preview — if the preview is audible at the volume set in check #1, these two checks are done. In our own testing of AVA we once shipped a bug in this exact class — an alarm that could fire vibrate-only under specific conditions — and it taught us to treat "sound settings" as reliability-critical code, not cosmetics.

3. Your custom alarm tone file is gone

If you picked a downloaded MP3, a file on an SD card, or something in a cloud-synced folder as your alarm sound, you created a dependency: the file must still exist at ring time. Deleted downloads, a cleaned "Downloads" folder, a re-formatted SD card, or a cloud file that's no longer cached — and the alarm has nothing to play. Some phones quietly fall back to a default tone; others just don't play anything.

Fix: re-open the alarm's sound picker. If the previously chosen file shows as unknown/missing or the preview is silent, re-select a sound. Prefer built-in tones or an app that bundles its sounds offline. If you like waking to music, see best wake-up songs — and make sure the app stores the audio locally.

4. Bluetooth stole your alarm

Fell asleep with earbuds connected? Left the phone paired to a speaker, TV, or the car in the garage? Some alarm apps play to "current audio output" — which means your alarm rang beautifully inside an earbud case on your desk. Well-engineered alarm apps force alarm audio to the phone speaker (or to both), but not all do.

Fix: check the Bluetooth icon in your status bar before sleeping, or disable Bluetooth at night. Then test your specific app: connect headphones, fire a test alarm, and listen to where the sound goes. If it abandons the speaker, that app is a liability for bedside duty.

5. DND is muting the wrong stream

Do Not Disturb has a dedicated alarm exception — alarms are supposed to cut through. But that only works when two conditions hold: your DND config actually allows alarms, and the app plays its wake-up audio on the proper alarm stream. An app that plays its morning audio as ordinary media gets muted by DND like any podcast would.

Fix: Settings → Sound → Do Not Disturb → confirm Alarms is in the exceptions. If the built-in Clock rings through DND but your third-party app doesn't, the app is on the wrong stream — report it or replace it. Full detail: Do Not Disturb blocking alarms.

6. A fade-in ramp starting from silence

"Gradually increase volume" is a lovely feature — until it's set to ramp over several minutes while your alarm auto-silences after one. Result: the alarm "rang" entirely below hearing threshold. Check your alarm app's settings for a fade-in/gentle-wake option and either shorten the ramp or turn it off. (Done right, an escalating alarm is genuinely great for heavy sleepers — our guide on escalating alarm volume covers the sensible configuration.)

The 2-minute silent-alarm test

1. Raise the Alarm volume slider to max, pick a built-in tone, vibrate off.
2. Disconnect Bluetooth, enable DND (yes, enable — you're testing the exception).
3. Set an alarm two minutes out, lock the phone.

If it rings loud through DND, your chain is healthy — restore your preferred volume and DND schedule. If it's still silent, the app itself is mishandling audio, and no setting will save it.

FAQ

Why is my alarm vibrating but not ringing?

Vibration and sound are controlled separately, so a vibrating-but-silent alarm means the trigger worked and only the audio failed. In order of likelihood: the alarm volume stream is at zero (it's a separate slider from media volume), the alarm itself is set to vibrate-only or its sound is set to None, the chosen custom tone file was deleted or moved, or the audio is being routed to a Bluetooth device in another room.

Will my alarm play through Bluetooth headphones instead of the phone speaker?

It depends on the app. Well-built alarm apps deliberately play alarms through the phone speaker, or through both speaker and headphones, exactly so a forgotten connection can't silence your morning. Simpler apps just play to the current audio output — so if your earbuds or car stereo are still connected, the alarm rings in the case on your desk. If you fall asleep with earbuds connected, test what your alarm app does.

Why did my alarm go silent after I changed the ringtone?

If you picked a custom sound file — from Downloads, an SD card, or a cloud folder — and that file was later deleted, moved, or the SD card unmounted, the alarm fires with nothing to play. Some phones fall back to a default tone; others fail silently. Re-open the alarm, check what its sound is set to, and prefer a built-in tone or an app with bundled offline sounds.

Does Do Not Disturb silence alarm sounds?

Not if everything is configured correctly: DND has a dedicated alarm exception, and alarms that play on Android's alarm audio stream ring right through it. Two failure cases exist though — your DND configuration has the alarms exception turned off, or the app plays its wake-up audio on the media stream, which DND does mute by default. Check Settings → Sound → Do Not Disturb and confirm alarms are allowed.