Alarm clock not sounding after autoreboot

DeletedUser257

Hi all, I have come across a weird glitch in my GOS. If I set up an alarm and the device has rebooted whilst I am sleeping (i.e., auto reboot on), then the alarm will fire but no sound will come through, therefore, I will not awake. If I tick the 'vibrate' option, the device will still not sound when the alarm goes off but at least I will wake up with the vibration. This is less than optimal. I checked this on another device, with exactly the same setting and build number as my device and the alarm behaves properly and will sound after an auto-reboot. How can I fix this and why is this happening? Thanks!

treequell

DeletedUser257 I also had the same issue a while ago. I had inadvertently set the alarm volume to zero.

Go to Settings > Sound & vibration, and adjust the Alarm volume slider.

treequell

DeletedUser257 Note that alarms in only the stock AOSP Clock and Google Clock apps will work BFU (after auto-reboot).

GrapheneOS

treequell Other alarm clocks can implement Direct Boot too and it has been around for many years now so they should have done it by now.

DeletedUser257

Yeah, I am using the stock/default GOS alarm. The alarm sound slider is on max and it is still doesn't work after reboot. Not sure what else to do.

treequell

DeletedUser257 Do you have Do Not Disturb mode on? And if so, have you checked that alarms are allowed to ring when Do Not Disturb mode is on?

DeletedUser257

treequell DND is off at all times

[deleted]

GrapheneOS

Can someone confirm that Simple Clock (by Simple Mobile Tools, the oranges one) does not sound after reboot ? Nor Clockyou ?
For me, Clock You does even never sounds. Even BFU. It has notification permission. What to do ?

Or could someone suggest a private Material You clock app ?

DeletedUser257

I have solved the issue. Here's what I did:

Step 1: re-enabled Sensor permission for the Clock app.

This in itself did not fix it after trying. Then the following worked:

Step 2: Clearing the Storage and Cache of the Clock app.

treequell

[deleted] To ring after boot, the app has to have direct boot. AOSP has allowed third-party apps to have direct boot for a number of years now, but it's up to the app developer to implement that.

https://developer.android.com/training/articles/direct-boot

meiklmue

My stock alarm clock does not ring sometimes without any reboot.
So I set 3 alarms, all 5 minutes apart to wake up when one or two do not make any sound...
(DND is off when my alarms go off and the slider is on max.)
Might be a good idea to set a fourth one with vibration, thanks for that :)

[deleted]

I correct myself : ClockYou can sound AFU* but the it confuses 8 a.m. with 8 p.m. 😅 If I take this into account, it works. But not BFU.
So I use Google Clock :( (Because I demand a Material You app💁)

plantmom

Any fix for this yet? My alarm failed to ring this morning. Using the default clock app with sensors permissions. I never use DND.

Havok

Having this issue on the pixel 10 pro XL. Logs for the clock app at the time it's supposed to go off show:

12-06 14:00:00.327 4276 4606 W ActivityThread: Failed to find provider info for media (user not unlocked)
12-06 14:00:00.344 4276 4606 W ActivityThread: Failed to find provider info for media (user not unlocked)

It's the default clock app. It's set to use one of the stock sounds (Argon), and vibrate. It vibrates, but makes no noise. The alarm volume slider is at about 75%

x-pve

Just an idea - do you have set a custom sound for alarm clock? If yeas, the sound file is stored on encrypted drive which is not accessible in BFU state -> no sound. Or maybe I'm wrong.
Edit: the sound file is copied to /sdcard/Alarms which is (not sure) accessible in BFU (?)