Alarm Clock - Android 14 not working properly

GrapheneOS / os-issue-tracker

Issue tracker for GrapheneOS Android Open Source Project hardening work. Standalone projects like Auditor, AttestationServer and hardened_malloc have their own dedicated trackers.

https://grapheneos.org/

355 stars 21 forks source link

Alarm Clock - Android 14 not working properly #2487

Open LunchBoxC opened 1 year ago

LunchBoxC commented 1 year ago

Let me preface this by saying I use the Alarm clock for medication reminders so I'm well versed in how the Alarm Clock works.

Phone: Pixel 7a stable release - 2023100900 (Android 14)

Multiple alarms did not go off but were set from before update and were toggled to on.
-New alarms set would go off, old ones would not. -Force stopped the Alarm Clock and still only new alarms would go off -Figured out that Alarm toggles although showing on from before the update, needed to be toggled off and then back on again. -Also noticed that default settings were all reset. Eg: "Silence after" and "Gradually increase volume"

Hope this helps everyone.

thestinger commented 1 year ago

We haven't updated or changed the clock app code for a long time so that's very strange. We haven't moved to the Android 14 clock app code since we're stuck with an older version due to huge upstream regressions.

LunchBoxC commented 1 year ago

@thestinger Thanks for getting back to me. It is quite strange.

It didn't happen with today's update.

Regards

joeyboon commented 1 year ago

I would just like to say I had the same issue on my Pixel 6 running build number UP1A.231005.007.2023101100

LunchBoxC commented 1 year ago

I had more problems today. 2 of my alarms didn't go off at the time despite being toggled on/off a few days ago.
Then when I turned off the repeat daily function and turned that back on it seemed to be working again.

As I use this for medications throughout the day, I ended up deleting all my alarms then deleted the cache and data for the app and setting them up all again after a phone restart. It appears to be working properly again.

I'll update the thread in a couple of days and let everyone know if it seems to be a data/cache problem with this app specifically after the 14 update.

LunchBoxC commented 1 year ago

Seems to be a cache / data issue. All alarms working perfectly now that I cleared those and added all my alarms back to the app.

mst5295 commented 1 year ago

Have the same issue here on my Pixel 7 Pro and my partners Pixel 6 Pro after the Android 14 Update a several days ago. We use several alarm clocks with repeat (some daily some every second day, etc). For some we are using the standard alarm sounds and some with Spotify. It is kind of random which alarm clock is going off and which doesnt.

The alarm clock which was going off yesterday maybe dont go off today and so on 🙈 until know I cant find a pattern.

The only thing I have noted two times now, that if there are multiple alarm clocks in a time gap of 10 minutes mostly only one is going off

gmgtamz commented 10 months ago

I confirm the bug: the alarm didn't go off Then, after update and reboot, I got a "missed notification of 'alarm' " from the notification panel)

it happens to me a couple of times (at least 3 times the last month, I'm a new user of GOS) on a 4a5g (last time 2 day ago) with the latest GOS versions, but only when I didn't update the phone (rebooted in fact).

It happens to me every-time I have a pending update to apply, I think only reboot was needed (and couple of so called "app optimizations" I'm waiting on at reboot) I'm pretty sure it's related to some app or OS update not finished or app not optimized needed reboot, or something like that.

it's pretty annoying, I cannot trust my alarm anymore to wake up on time 😳

740racing commented 10 months ago

I too have the same problem with my Pixel 6a Build number UQ1A.231205.015.2023121200. Overslept and waking up to "Missed alarm" notification far too many times now so I had to add redundancy in my morning alarm system!

It is not only set alarms, but timers also have this issue. Timer alarm won't trigger unless manually waking the screen. Have not been able to decern a pattern in these behaviors, it seems random.

orionszbelt commented 9 months ago

Alarm not working after autoreboot:

set autoreboot in 10 min
set alarm to now+15min
set alarm sound Neon (one of provided by default)
leave the phone alone
in 10 minutes the phone restarts
in 5 min more the alarm screen pops up but
-- either no sound at all
-- or the sound is NOT Neon but something else. Repeatable every time, pixel 6a, all stable updates

P.S. there is no setting "Gradually increase volume" anywhere, but when it plays that unknown sound, it does increase volume gradually.

matchboxbananasynergy commented 9 months ago

I have not adjusted the sound from the default, as far as I remember, and my alarm works fine after a reboot. Not every sound is available in BFU.

muhamedkarajic commented 6 months ago

My sister had the same problem. Not sure which exact part fixed it but here is how I got it working:

Close application by swiping it, then force stop it, clear cache and data. Then open it again and approve the permission.
Go into the deep sleep applications are remove file storage from it
Go into the never sleeping applications and add alarm clock
There was a option when going into the settings of the Alarm Clock to never put that app on standby when using low power mode but I doubt that was the issue cause by her that one was working totally fine.

Its probably the first thing which I did that fixed it for her. Hope it helps someone out.

thestinger commented 6 months ago

Go into the never sleeping applications and add alarm clock

It has unrestricted battery by default unless users disable it.

RTechSn commented 3 months ago

I have restarted after an automatic update yesterday. Today i missed my medication and was late for my job for two hours.