Alarm not working cross-profile

I just tested two Apps, the stock Clocks app and Google Clock.

I set the alarms in one profile and switched to another, waiting for the alarms to sound.

Using each app in the separate profile, I was able to snooze/dismiss the alarm.

@vvf69107 perhaps you've unintentionally altered the Clock notification settings in the secondary profile which is not able to snooze/dismiss. Have you checked Clock's notification settings within that profile?

vvf69107 imo alarm should be excepted by that.

The Cross-Profile alarm notification is a standard upstream feature from AOSP. It is separate from the 'notification forwarding ' feature for normal notifications implemented by GrapheneOS.

Somewhat related but different question, if you have auto-reboot feature set to 4 hours (or any time period shorter then expected sleep time), what is the best practice to use an alarm with the standard AOSP Clock app?

Would the alarm ring after phone rebooted at night?

DeletedUser115 It will ring, as long as it's been set on the owner profile.

matchboxbananasynergy Thank you!

DeletedUser115 Would the alarm ring after phone rebooted at night?

I think you may need to use one of the default alarm sounds instead of a custom one.

de0u That is correct.

vvf69107 this is problematic because the device automatically restarts for updates instead of asking you to select a time or do it manually

Settings, System, System Update, turn "Automatic reboot" off.

vvf69107 Could you clarify exactly what you are trying to do?

Are you wanting an alarm to ring in a secondary user after you have rebooted the phone?

If so, I don't think that can work. I believe the alarm would need to be set in the owner profile for it to ring BFU.

vvf69107 this option is not safe imo.

Can you clarify the nature of the perceived threat?