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?
No smart watch. Only connected devices are Bose qc45s and sony wf1000x, both of which I turn off at night.
Is it leaving a missed alarm notification?
Also, have you checked for battery optimisation for the clock app?
It does, but not for a few hours.
And yeah, one of the screenshots above show that I have battery optimisation unrestricted for clock app.
Ah, sorry, missed that. So the missed alarm notification is happening way later, like hours later, than the alarm time? That sounds like the background process is being killed in some way. In Android when you set an alarm it uses the intent system to wake itself again later. If this is failing for your alarm app only then it could be an issue with the app, but this looks like the default clock application, is that correct? It looks like you maybe installed it from the play store but it may just be an update, so just checking.
That all said, if the clock is the only app with this problem then I would address it by replacing the app. If this is impacting other apps I can only think of a few ways that it could be caused but it should be fairly obviously problematic for other apps and solving that is beyond my understanding.
I would recommend trying another alarm clock app from a source you trust. I would install something from IzzyOnDroid on FDroid but your milage may vary.
I have now uninstalled and reinstalled the clock app via the play store. And set up my alarms again. I didn't think of that before. Maybe that will help. I'll see if I get to work on time tomorrow.
I'm also trying out an alternative app.