If I set an alarm for two hours from now, it will go off. I've tested this a few times.
But my morning alarms, at 6:07 and 6:13 am, just don't go off. I've been testing this for like a week now and I cant figure it out. Later in the day, maybe 3 or 4 hours later, the phone will alert me that I missed the alarm, even when my body clock wakes me up before the alarm and I lay awake watching my phone tick past the alarm time without it ever twitching or doing anything.
So far, I've tried:
- Deleting all alarms and recreating them
- Clearing the app cache and data, then rebooting
- Removing Duraspeed system app which I suspected of causing problems
- Toggling every setting and widget related to alarms and DND I can find
Here's my alarm setup:
Clock app settings:
Android sound settings:
Now, I suspected it was some battery thing killing the app, or DND preventing it from going off, but these settings all look correct to me:
And just now, its warned me about the missed alarm that I laid awake watching not go off:
Any ideas about what else to investigate, or what else to do? Should I just download and rely on a different alarm app or something?
Gentlemen, it is with great pleasure that I announce my alarm went off this morning and I arrived at work on time.
Unfortunately, with all the fiddling around, I'm not sure quite what I did to fix it. I think that maybe just uninstalling and reinstalling the clock app from Google play fixed the problem. Either that, or fully disabling my scheduled Do Not Disturb function.
EDIT: I spoke too soon. My alarms didn't go off this morning. BUT I think I know why now.
It turns out that there were two apps called Clock. One that was cloned from my old phone, one that came with the new phone:
All my alarms were set up in my old clock. But when I'm giving permissions and exemptions in the battery manager, I reckon thats affecting the new app, which has no alarms. So the old clock app is still getting randomly killed in the night.
I've uninstalled the old clock app and set up alarms in the new clock app.
I reckon that will fix the problem tomorrow, but I'll have to wait and see.