System Clock bugs out when alarm rings on lockdown mode, phone reboot required

CoffeeTime03

If you set an alarm using the default Clock app, it does ring as its supposed to.
However, if your phone is in lockdown mode (hold power button, then click on "Lockdown"), no display to disable the alarm is shown. Neither it can be disabled through a notification.
The only way to disable the alarm is to reboot the whole phone.

tmp

You can unlock the phone via pin/passphrase and toggle disable the activated alarm to silence it.

ReadOnlyUser

I faced similar today and already some time ago. Might be same/similar to https://discuss.grapheneos.org/d/1483-incoming-call-not-displaying/7

This morning the daily alarm was triggered but it wasn't possible to swipe it off. Unlocking the device did not stopped the alarm and there was no notification or dialog to do so. Only solution to turn the alarm off seemed to be rebooting.

As mentioned in the thread linked above, it may be related to lockdown mode. I tried the lockdown yesterday and logged in afterwards. Maybe this changed something that prevented the alarm notification this morning.

MetropleX

If you end up in either of the positions mentioned, please upon reboot go straight to dev options and select Big Report>Interactive, and take a bug report.

Let me know if you've got them and in the interim I will take time to find out what specific elements you need to grep for and provide.

ReadOnlyUser

MetropleX
Procedure to reproduce:

configure alarm
activate lockdown mode
login again
lock screen and wait for alarm
alarm triggered as expected but no chance to cancel, even not after login

Works in both owner and secondary user. Unfortunately, nothing happened when I tried to create bug report after this issue. Bug report worked before.

CoffeeTime03

MetropleX I apologize for my late response. I will file a bug report as soon as it happen again.

CoffeeTime03

MetropleX Hello, I've ended up in the said position again and did take an interactive bug report. Please let me know how I can share this to you privately / if I need to grep specific parts of it so I can review them for informations before posting it here.
I've also tried to reproduce it (by setting an alarm and going into lockout) without waiting for it so I could report but to no avail (as soon as I unlocked my phone the notification would immediatelly appear).
To describe the environment further:
I do have an alarm to wake myself up.
I used my phone for a (few) day(s) without rebooting.
When going to sleep, I always put my phone in lockdown.
It does not happen every time the alarm rings.

MetropleX

ReadOnlyUser followed the above process on my Pixel 6a twice to no avail I cannot replicate, it swipes away fine on latest release too btw.

mythodical

MetropleX Just for kicks, I decided to test this today and unfortunately, I was able to replicate the issue as well. Stock clock app, Pixel 7, and I followed the steps provided by @ReadOnlyUser. I was only able to dismiss the alarm by unlocking the phone, navigating to the clock app and toggling the alarm off.

mythodical

mythodical Replying to myself here, just to say that in addition to the alarm notification not appearing after lockdown/unlock, Signal notifications also stopped appearing until the phone was rebooted. I could hear the notification sounds of incoming messages, but the notifications were not visually displayed in the notification drop-menu. I had to poke around to determine the messages were coming from Signal.

dc32f0cfe84def651e0e

Here's my experience.

When I go to bed, I put my phone into lockdown mode. The alarm clock does sound, but I have to enter the passphrase first in order to stop or snooze it.

I've been using another locking solution recently, which makes use admin API to lock: https://f-droid.org/en/packages/com.wesaphzt.privatelock/ which didn't have such inconvenience. I dropped using it for the false positives though.