Are your iPhone or Apple Watch alarms not going off? Here's how to fix it
If you've never had this problem, we're not surprised because it is really rare. However, we also envy you tremendously, because when you do get it, it is extraordinarily inconvenient. As yet, Apple has no fix for it -- but we do have a workaround.
We use our alarms a lot. And they don't always work.
There are untold millions of iPhone and Apple Watch users who have no problems with their alarms whatsoever. Yet that's no help if you're one of the few for whom an alarm will occasionally just not sound.
So far, Apple has simply not got to the bottom of this years-old bug.
Nor have we, but after repeatedly getting it ourselves, we have developed a workaround. There isn't a solution, even when talking with Apple Support they haven't been able to find a fix. However, it is a workaround that has prevented us ending up with important alarms that simply haven't sounded.
There are two problems, which we believe are not related, but they have the same effect. One is on the Apple Watch and is particularly exasperating.
It's just that sometimes it hasn't done any such thing.
On the left, the alarm going wrong. On the right, what you should see every time.
When you do this on the Watch and you get that Siri response, you also get a line on the screen showing you the time of the alarm. Next to that is a typical on/off switch and of course it's switched to on.
Except when it isn't.
There are times when Siri says it has set the alarm, and it may even have entered the right time, but hasn't switched the alarm on.
We have suspected that the problem occurs most often if you are setting an alarm for a time you have previously had one. Once we even told Siri to "set an alarm for 5am called 'Stupidly Early,'," and it set it but the name was "Airport." Siri and Apple Watch had kept the name from when we previously set a 5am alarm, and it also failed to switch that alarm on.
Whatever the fault is, though, it isn't solely tied to any one thing. We can't reliably reproduce the error, and nor can Apple. It does seem more common with these existing alarms, but that could just be because we happen to set these same alarms often and so notice it.
Apple's advice to us, by the way, was to unpair and re-pair the watch to our phones, and to cycle off the "Hey Siri" feature on both devices.
It didn't appear to improve anything, but since the problem is rare, it's only when it fails again that we ever know if an actual fix has achieved much.
In this case, what happens is that you set an alarm -- by Siri or by hand -- and everything looks right. If you go into your alarms, you'll see that the time is set and the alarm is switched on.
It's rare, but you can pick up your iPhone to see that the alarm is sounding and yet there's been no sound. It isn't your ears.
Yet the next morning, or whenever, nothing appears to happen.
We have now many times idly turned to our iPhones on the bedside table and discovered that we were late. What's more, we have discovered that the iPhone screen is showing us the alarm as ringing -- but there's been no sound.
First, you'll suspect your hearing, then you suspect the volume control, lastly you'll cross your fingers that somehow switching the phone to vibrate has done it, but no. At some times, for no repeatable or discernible reason, the iPhone alarm does not sound.
And do the same with your iPhone, too. Just every once in a while.
Setting an extra alarm for one minute later somehow makes the iPhone sound the first alarm correctly.
Then whenever you set an alarm that's important to you, set it twice and use the one-minute-trick.
To use our iPhone's 5am example, we promise you this works. Set an alarm for 5am and then immediately set another one for 5:01am.
Let us be really clear here: we're not talking about snoozing, and we're not even really doubling up on the alarms. For some reason, if you also set a 5:01am alarm, your 5:00am one will sound correctly.
Frankly, that's less a fix and more like alchemy. But it works.
It works on both iPhone and Apple Watch and until Apple squashes this years-old bug in iOS, it's what we do with every important alarm.
Keep up with AppleInsider by downloading the AppleInsider app for iOS, and follow us on YouTube, Twitter @appleinsider and Facebook for live, late-breaking coverage. You can also check out our official Instagram account for exclusive photos.
We use our alarms a lot. And they don't always work.
There are untold millions of iPhone and Apple Watch users who have no problems with their alarms whatsoever. Yet that's no help if you're one of the few for whom an alarm will occasionally just not sound.
So far, Apple has simply not got to the bottom of this years-old bug.
Nor have we, but after repeatedly getting it ourselves, we have developed a workaround. There isn't a solution, even when talking with Apple Support they haven't been able to find a fix. However, it is a workaround that has prevented us ending up with important alarms that simply haven't sounded.
Here's the problem
If only to help anyone Googling for a solution as desperately as we have done, this is what happens, this is what goes wrong with Apple Watch and iPhone alarms.There are two problems, which we believe are not related, but they have the same effect. One is on the Apple Watch and is particularly exasperating.
Apple Watch bug
"Hey, Siri," we'll say, "set an alarm for 6pm." And every time, Siri will reply with "OK, I've set your alarm."It's just that sometimes it hasn't done any such thing.
On the left, the alarm going wrong. On the right, what you should see every time.
When you do this on the Watch and you get that Siri response, you also get a line on the screen showing you the time of the alarm. Next to that is a typical on/off switch and of course it's switched to on.
Except when it isn't.
There are times when Siri says it has set the alarm, and it may even have entered the right time, but hasn't switched the alarm on.
We have suspected that the problem occurs most often if you are setting an alarm for a time you have previously had one. Once we even told Siri to "set an alarm for 5am called 'Stupidly Early,'," and it set it but the name was "Airport." Siri and Apple Watch had kept the name from when we previously set a 5am alarm, and it also failed to switch that alarm on.
Whatever the fault is, though, it isn't solely tied to any one thing. We can't reliably reproduce the error, and nor can Apple. It does seem more common with these existing alarms, but that could just be because we happen to set these same alarms often and so notice it.
Apple's advice to us, by the way, was to unpair and re-pair the watch to our phones, and to cycle off the "Hey Siri" feature on both devices.
It didn't appear to improve anything, but since the problem is rare, it's only when it fails again that we ever know if an actual fix has achieved much.
Alarms on the iPhone
The similar problem on the iPhone is, as far as we can tell, even rarer. We tended to get it quite often during the iPhone 5 and 6 days, and it's only come up once on our iPhone XS Max model.In this case, what happens is that you set an alarm -- by Siri or by hand -- and everything looks right. If you go into your alarms, you'll see that the time is set and the alarm is switched on.
It's rare, but you can pick up your iPhone to see that the alarm is sounding and yet there's been no sound. It isn't your ears.
Yet the next morning, or whenever, nothing appears to happen.
We have now many times idly turned to our iPhones on the bedside table and discovered that we were late. What's more, we have discovered that the iPhone screen is showing us the alarm as ringing -- but there's been no sound.
First, you'll suspect your hearing, then you suspect the volume control, lastly you'll cross your fingers that somehow switching the phone to vibrate has done it, but no. At some times, for no repeatable or discernible reason, the iPhone alarm does not sound.
The workaround
Do this. Every other day or whenever it enters your head, say to your Apple Watch "Hey, Siri, delete all my alarms." Wipe the list clean. You know you've already got twenty different ones in there, let them go.And do the same with your iPhone, too. Just every once in a while.
Setting an extra alarm for one minute later somehow makes the iPhone sound the first alarm correctly.
Then whenever you set an alarm that's important to you, set it twice and use the one-minute-trick.
To use our iPhone's 5am example, we promise you this works. Set an alarm for 5am and then immediately set another one for 5:01am.
Let us be really clear here: we're not talking about snoozing, and we're not even really doubling up on the alarms. For some reason, if you also set a 5:01am alarm, your 5:00am one will sound correctly.
Frankly, that's less a fix and more like alchemy. But it works.
It works on both iPhone and Apple Watch and until Apple squashes this years-old bug in iOS, it's what we do with every important alarm.
Keep up with AppleInsider by downloading the AppleInsider app for iOS, and follow us on YouTube, Twitter @appleinsider and Facebook for live, late-breaking coverage. You can also check out our official Instagram account for exclusive photos.
Comments
apparently, my sleep is deep enough that it could take more than 15 minutes for me to actually react to an alarm.
But: I observed that iOS‘s and watchOS‘s Alarms would stop making any sound after 15 minutes of chiming. The snooze and stop buttons remain on the screen, but the device remains silent. This has caused me several times being late at work - since I spotted the culprit, I installed Alarmy because that app keeps ringing until I do something about it.
Anyone else knows this problem? Anyone who knows what the reason is or knows any workaround?
Thanks in advance.
When a text or Messenger message comes in, the phone usually makes a sound. But every once in a while it doesn’t. No vibration either. Unlocking the phone shows a message has been received, but no alert heralded its arrival.
My bigger complaint with notifications is that they aren’t synched to my Mac correctly. I’ll turn on my Mac after leaving it asleep for days or weeks, and it’ll show all my alerts for reminders that have come and gone in all the time I’ve not used it, even though I’ve dismissed them on my iOS devices. There’s no way to clear them all. I have had to go to reminders repeatedly to get it to synch with iCloud.
Speaking of broken features and voodoo, here are two that really irritate me:
1. iOS repeatedly downloads music while on cellular data, just because my car has selected my iPhone 6s (wrongly) to play music and there is none on that phone. Every setting that supposedly controls data usage and iTunes is set to NOT download anything, but it does it anyway. You will find other people online reporting this problem and there is no solution at all. I’m not sure why we should trust security on these devices when crap like this happens regardless of having all settings set correctly.
2. I have not been able to use Universal Clipboard in months. All settings are correct. Nothing solves the problem.
So so I guess even if I was affected by this bug I wouldn’t be affected by this bug.
Is it possible to create a Siri shortcut for this? So when you ask for an alarm it always sets two alarms?
Also, as a simpler work around: If you know you take more than 15 minutes to wake up, simply set two successive alarms, the second for 15 minutes after the first.
also this forum system...
FWIW -- I've notcied that my WatchIOS seems to now randomly set the alert s off. Phone might ring, but not watch -- slide up, there it shows disabled. Now before everyone tells me I must have covered the screen at some point -- it's summer, no sleeves, and no reason to put my hand over the screen to silence it.
One other data point, the randomly disappearing sounds was occuring well in advance of current IOS, and disabling and re-enabling sound after an IOS update seemed to fix that issue. Again, up until most recent update.
However, I do recall a few years back Apple had an oddball bug with alarms that was specifically related to daylight saving time. Something about the time changing by an hour in the middle of the night would sometimes screw up alarms. And since that change only happens twice a year, it took a while to nail down from what I recall.