• General

  • Alarm not working cross-profile

matchboxbananasynergy This is expected. Each profile has its instance of the alarm app with its own distinct app data. You've set the alarm on your owner profile, so it needs to be dismissed there.

I don't think that is the expected behaviour.

matchboxbananasynergy When you say that it sometimes works as you expect, could you please describe what that looks like?

If I set an alarm in one profile using the default Clock app, and switch to another user profile, the alarm will still ring cross-profiles and a screen will be shown where I can either dismiss or snooze the alarm.

I believe this is what @vvf69107 is expecting to see - to be able to snooze/dismiss alarms cross-profile - but for some reason they are not able to do so reliably.

        different apps dont work as well. installed them after having this problem for a while now.

        To be honest, I'm struggling to think of any troubleshooting ideas to try to work out why this is not working for you - it should just work.

        Note that this functionality is a standard upstream functionality from AOSP. It is not amended by GrapheneOS in any way.

          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?

            I dont have main profile notifications enabled for the other profiles. since the last update i can now at least disable after guessing the right profile without having to unlock it.. still i think it's a problem with cross-profile notifications. imo alarm should be excepted by that.

            spiral

            treequell

                  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.

                      treequell thank you, that's what i was hoping for. do you might have an idea what could be causing the issue then?

                        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?

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

                          • de0u replied to this.

                              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.

                                  9 days later

                                  de0u this option is not safe imo.
                                  an option to set a timer so it will reboot after not using the phone for a long time would be great, but also doesn't solve the alarm issue.

                                  • de0u replied to this.