Verdict: Start by setting a new alarm in the phone’s built-in Clock app for a few minutes from now, lock the phone, and listen for its sound. If that test fails, check the alarm’s enabled state, sound, volume, and schedule before changing phone-wide settings. On iPhone, Silent mode and Do Not Disturb do not mute Apple’s Clock alarm; on Android, Do Not Disturb and Battery Saver settings can affect alarms.
A missed alarm is urgent, but the cause is not established by one silent morning. The alarm may have sounded too quietly, been scheduled for another day, been set to vibration only, or been suppressed by a device setting. This guide concerns built-in Clock and wake-up alarms, with device-specific paths for iPhone, Google Clock, and Samsung Galaxy. A third-party alarm app has its own permissions and behavior; do not assume Apple’s or Google’s built-in Clock rules apply to it. For push alerts that arrive late after opening an app, use our separate delayed-notifications guide.
Test a fresh alarm before changing anything major
- Open the phone’s built-in Clock app and set a new alarm for a few minutes ahead. Choose a built-in audible sound, switch vibration on if helpful, and confirm the alarm toggle is enabled.
- Lock the phone and leave it nearby. When the scheduled time passes, note whether the screen shows the alarm and whether you hear sound or feel vibration. Then dismiss the test alarm.
- Repeat after changing one relevant setting. If the fresh alarm works, compare its time, repeat days, sound, and volume with the missed alarm before resetting or reinstalling anything.
For an important appointment or medication time, use an independent backup alarm while you investigate. A successful short test increases confidence in the current settings; it cannot guarantee a future alarm on every device or third-party app.
| What happened | Likely area to check | Best first action |
|---|---|---|
| Alarm screen appeared but there was no sound | Alarm sound or alarm-specific volume | Select a built-in sound and raise the correct volume slider |
| Alarm vibrated but stayed silent | Sound set to None or silent; volume too low | Open that alarm’s Sound setting and repeat the short test |
| Only a particular weekday was missed | Repeat-day or Sleep schedule configuration | Check the enabled days and whether the next alarm is on |
| Android warns that Do Not Disturb silenced an alarm | Mode’s alarm filter | Allow alarms in the mode or turn it off for a test |
| Android warns Battery Saver may have prevented an alarm | Power-saving restriction | Test with Battery Saver off or follow the phone’s essential-app option |
| All phone audio is also missing or muffled | Possible broader audio setting or speaker problem | Test another built-in sound and follow audio troubleshooting |
1. Check the alarm itself: time, days, and sound
Open the missed alarm in Clock, confirm that it is switched on, and read its next scheduled time carefully. Check AM versus PM where the phone uses a 12-hour clock, the selected repeat days, and any pause or one-time setting. Google’s Clock help documents the alarm toggle and repeat-day controls; it also cautions that setting two alarms too close together may cancel the first and recommends at least five minutes between them. Samsung documents one-time and recurring alarms in its Galaxy Clock app. On Android, menu names can differ between Google Clock and Samsung Clock. Google’s alarm settings and Samsung’s Galaxy Clock guide show the relevant controls.
Choose a built-in alarm tone while testing. On iPhone, Apple says an alarm set to None can vibrate without sounding. In Google Clock, the selected sound and vibration setting belong to each alarm; Google also warns that a silent alarm sound can produce a missed audible alert. A downloaded track or streaming song adds another dependency, so use a built-in tone to isolate the phone’s alarm function first. Apple’s alarm checks and Google’s sound options support this test.
2. Adjust the correct volume, not media playback
On iPhone, open Settings > Sounds & Haptics and raise Ringtone and Alerts. Apple’s instructions identify that slider for a regular Clock alarm that is too quiet. Use a nearby test alarm after changing it; listening to music at high media volume does not verify the alarm level. Apple also says a built-in Clock alarm plays through the phone speaker as well as connected headphones at a set volume, so headphones alone are not a reason to assume the iPhone alarm will be silent. Apple’s alarm-volume instructions describe these behaviors.
On Android, open the alarm’s sound controls in Clock and adjust the phone’s Alarm volume, where provided, rather than only Media volume. Google Clock can display a warning when an alarm sounded below 30% volume. Galaxy volume menus and Clock alarm-sound controls vary by model, but Samsung documents the alarm sound and vibration options in Clock. Test after changing one control so you know which change mattered. Google’s alarm diagnostics and Samsung’s Clock controls provide the device guidance.
3. Do not confuse iPhone Silent mode with Android alarm filters
Apple explicitly says the Ring/Silent switch, Silent mode, and Do Not Disturb do not affect the built-in iPhone alarm sound. If an iPhone Clock alarm was silent, look at its selected sound, Ringtone and Alerts volume, schedule, and the short test rather than presenting Silent mode as the automatic explanation. That statement is about Apple’s Clock alarm, not every third-party alarm app. Apple’s support article states the distinction.
Android is more configurable. Google Clock can warn that Do Not Disturb silenced an alarm, and Android Modes include an Alarms & other interruptions filter. Check the active mode in Quick Settings, then review that mode’s alarm exceptions. On Galaxy, Samsung says Do Not Disturb can specify exceptions for alarms. Disable the mode briefly for a test if you are unsure how its filter is set, then restore your intended quiet-hours policy with alarms allowed. Android Modes guidance, Google Clock warnings, and Samsung’s exceptions guidance document these controls.
4. Check power saving and Clock notifications on Android
If Google Clock reports that Battery Saver may have prevented an alarm, turn Battery Saver off for a comparison test or, if your phone provides it, add Clock as an essential app in Battery Saver settings. Google also lists warnings for disabled Clock notifications, vibration, silent alarm sound, and low alarm volume. Use the warning actually shown on your device instead of disabling every battery feature without evidence. Manufacturer-specific power menus differ. Google’s alarm-issue table maps each warning to its next action.
If the problem occurs only in a third-party alarm app, inspect that app’s notifications, alarm permission, battery restrictions, and its own support instructions. First verify that a built-in Clock alarm works. If it does, a factory reset is disproportionate to an app-specific problem.
5. Check a separate wake-up schedule and the phone’s time
An iPhone Sleep schedule’s wake-up alarm is not the same setting as every regular Clock alarm. In the Health app’s Sleep schedule controls, Apple lets you turn the wake-up alarm on or off and choose its sound, volume, vibration, and snooze options. Check whether you changed only the next schedule or every day of the schedule. This is especially useful when a normal Clock test sounds but a scheduled wake-up alarm does not. Apple’s Sleep-schedule guide explains both scopes.
On any phone, verify the displayed date, time, and time zone after travel or a manual clock change. Apple cautions that manually changing time for app behavior can affect alarms. For Android, Google documents automatic time and time-zone controls in Clock settings. Correct the time only if it is wrong, then make a fresh short test. Restarting the phone and installing an available official system or Clock-app update can be sensible if the failure persists after settings are confirmed; do not clear Clock storage unless device support recommends it, because doing so may remove saved alarms. Apple’s time warning and Google’s time settings provide the basis.
When to use a backup or get device help
If two newly created built-in Clock alarms remain silent after checking their schedule, sound, volume, relevant Android mode and power settings, contact Apple, Google Pixel, Samsung, or your phone maker’s support with your model, software version, alarm type, and test results. If other sounds are also quiet or distorted, the issue may be broader than the alarm; our speaker-cleaning and sound guide covers safe first checks. Avoid poking the speaker or charging port to fix a scheduling problem.
Until the cause is understood, set an independent backup on another device or a standalone clock for commitments you cannot miss. That is a precaution, not evidence that any particular phone has a widespread alarm defect. An alarm may be configured correctly now and still merit a backup when its reliability matters to you.
Editorial note: This guide synthesizes manufacturer instructions into a symptom-led test. No alarm-failure rate was measured and no phone was tested for this article; menu paths and third-party app behavior vary.
[…] Phone Alarm Not Going Off? Android and iPhone Fixes […]