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?

  • hendrik@palaver.p3x.de
    11·
    28 days ago

    If you google Ulephone and alarm clock, you’ll find some more people complaining. It’s likely something the manufacturer did to save battery. I’d say the preinstalled (native) alarm clock app is most likely to work, maybe they tested their own apps. Everything else is likely to be nuked on inactivity during the night.

    • Agent641@lemmy.worldOPEnglish
      3·
      28 days ago

      There was a fucky bloatwate app called Duraspeed which killed apps in the background to save battery which I suspected of making the issue, but removing it using adb didn’t make a difference.

      There may yet be still more bloaty apps contributing to the problem though. I’ll keep working thru them