Skip to content
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

Open
Maimas2 opened this issue Nov 11, 2024 · 4 comments
Open

Must unlock phone to dismiss alarm #376

Maimas2 opened this issue Nov 11, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@Maimas2
Copy link

Maimas2 commented Nov 11, 2024

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:

  1. Set alarm
  2. Lock phone before it goes off
  3. When the alarm does go off, the sound plays, and a notification is pushed, but you need to unlock the phone to get to the screen to swipe to dismiss it.

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

  • Device: Pixel 8
  • OS: Android 15
  • App version: 0.6.0-beta1
@Maimas2 Maimas2 added the bug Something isn't working label Nov 11, 2024
@aronovgj
Copy link

aronovgj commented Nov 11, 2024

Same here:
#377

@Maimas2
Copy link
Author

Maimas2 commented Nov 11, 2024

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.

@aronovgj
Copy link

aronovgj commented Nov 11, 2024

The point is that it was disabled/reset by the update while it was enabled before the update.

@AhsanSarwar45
Copy link
Collaborator

AhsanSarwar45 commented Nov 11, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants