-
-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Must unlock phone to dismiss alarm #376
Comments
Same here: |
As per #377, this issue is caused by the "Allow full-screen notifications" permission being disabled by default. It is possible to go into the notification settings and manually enable it, solving the issue, though it took me a minute to find the setting. |
The point is that it was disabled/reset by the update while it was enabled before the update. |
It might be due to disabling auto backup in the latest beta, which might have reset some permissions in the app. Although this has been reproduced in the past by others too so might be related to something else. Seems to be device specific too as I haven't been able to reproduce it on my end. Edit: I see now that @Maimas2 reproduced this in beta1, so might not be related to auto backup at all. |
Describe the bug
You need to unlock the phone to dismiss or snooze the alarm that goes off.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A screen appears over the lock screen to dismiss the alarm, as the default alarm app (on GrapheneOS, at least) does.
Smartphone Information
The text was updated successfully, but these errors were encountered: