Alarm clock fails to go off

nid

Hi, I installed GrapheneOS a few days ago on my Pixel 4a. I'm satisfied with the overall experience so far, but one thing bothers me: alarm clock just straight up doesn't work.

I have an alarm set for 7:00 every day, and it has never went off yet. Thankfully I have other family members at home that wake me up, but for someone who lives alone, this might end up really badly.

Does anyone know how to fix this?

treequell

nid That's strange.

Have you tried testing it while you are awake? For example, set an alarm 5 minutes from now, and see what happens.

GrapheneOS

nid Clear the data for the clock app. You might have some kind of configuration issue from a past bug in the app that's interfering with current usage.

nid

treequell Yeah that's exactly what I did some minutes ago. A notification popped up that the alarm is about to go off, but it eventually didn't

treequell

Have you tried installing a different alarm clock app and seeing if that one works?

treequell

I don't know why it's not working, just thinking of some ideas to better diagnose the issue.

nid

I tested Google's alarm clock app and it seems to work. However, after testing the stock app again, it works too...

nid

I've set both apps to go off at a slightly different time in the morning. I'll post an update tommorow

Murcielago

GrapheneOS
clearing app storage has helped and the alarm now goes off as desired in BFU after a restart.

Now I can finally adjust the timer for automatic reboot to my needs, thank you very much.

nid

So apparently, the stock alarm clock app is working. I don't know what happened, perhaps I was dismissing the alarm and immediately falling back asleep so I forgot. I saw other people on the internet having a similar issue so I thought it's the OS' fault.
Apologies if I have caused any confusion.

Actually, wait, what if it happens randomly like people said? Whatever, I'll see in the next few days.

MetropleX

nid I've been using GrapheneOS on beta/alpha builds in the main since the Pixel 3 and rely upon my alarm also, I have never had the issue. You should be fine.

gggttt

it happens to me a couple of times, but only when I didnt update the phone, or app or when I didnt rebooted the phone after grapheneos update, I'm pretty sure it's related to app or OS update not finished or app not optimized, something like that.

jimmykaboila

Device: Pixel 6a
Build: UQ1A.2401015.002.2024010400

I've had this issue on a weekly basis since I got the device. Alarm does not trigger but there is a notification that says "Missed alarm <HH:MM>". Same issue with stock "Clock" app and other clock/alarm apps, which should mean that the root of the problem is somehwere in the OS, not the application. The issue in my case seems to be that the application fails to "wake" the device from the locked state. I suspect this because I have the same issue with timer notifications where the timer alarm/notification will not trigger unless I manually wake the phone from locked state by pressing the power button. I have tried clearing the application cache but problem persists. I have not found a noticable pattern for this bug, it seems to happen randomly.

After some searching (which led me here) I have found that I am far from the only victim of this issue. This is actually a real serious problem as it renders the device totally unreliable. People use timers and alarms for all kinds of purposes, some more critical than others

other8026

jimmykaboila I have never had this problem before and I don't see people saying this affects them all the time, so saying it's an OS issue isn't exactly accurate.

I have a few questions to see if someone here can help you figure out what the problem is:

Did you try clearing the apps' storage like the project account suggested earlier in this thread?
For the default clock app, are you using a different sound for the alarm, or is it just the default?
Do you have your phone set to automatically restart and the alarm isn't going off before first unlock?

missing-root

Sounds like your notifications where off tbh.

I recommend this clock which works well and has hardware button and more features.... and doesnt look BLUE