You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's assume that you have an alarm which you normally use, set for Tomorrow, not set to specific days of the week
The alarm time does not really matter, let's say 8AM
The alarm is set to off
The clock app is open in the background, and it was open any time before 12 AM
It is now after 12 AM (so technically we are in the following day
Open the clock app, to enable the alarm
Under the large text of the time, we can still see written Tomorrow
Tick the checkbox next to the clock to enable the alarm
We now see a notification that the alarm will ring 1 day and 7 hours from now, instead of the expected 7 hours
To correct the issue, the user must tap on the time, as in to set the alarm, then press okay. The text under the time will show Today, and the correct notification of 7 hours left until the alarm goes off is shown
Video
untitled.mp4
Device info
Pixel 7
Graphene OS, latest build (based off Android 13)
App was downloaded from f-droid
My thoughts
I hope that this only a life cycle issue, and all you guys need is to make sure that the clock part is reset when re-focusing the app.
And I hope it's not something specific to Graphene OS and the restrictions it puts on apps behavior :)
The text was updated successfully, but these errors were encountered:
This issue is not specific to GrapheneOS. I'm experiencing the same problem on a Fairphone 4 running stock Android, and it's becoming increasingly frustrating.
Okay, this is a bit of a weird one.
The bug and steps to reproduce
Tomorrow
, not set to specific days of the weekTomorrow
Today
, and the correct notification of 7 hours left until the alarm goes off is shownVideo
untitled.mp4
Device info
My thoughts
I hope that this only a life cycle issue, and all you guys need is to make sure that the clock part is reset when re-focusing the app.
And I hope it's not something specific to Graphene OS and the restrictions it puts on apps behavior :)
The text was updated successfully, but these errors were encountered: