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
When adding an alarm, click the default time value to set it, and when you finish selecting the hour immediately after lifting your finger, click ok
Expected behavior
clicking ok immediately after setting the hour only should basically give a time of XX:00 XX being the hour selected
Actual behavior
it gives a minutes value based on the location of the clock hand when the animation stops
Screenshots/Screen recordings
screen-20240703-062132-smol.mp4
Additional information
This bug also happens on google's clock app (the one that comes with google services, not aosp)
Might be a material UI bug
"Discovered" after seeing this https://wetdry.world/@lexd0g/112708483036528818
The text was updated successfully, but these errors were encountered:
Aga-C
added
device/software specific
Issues that only happen on some devices or with some specific hardware/software
niche
Only relevant to a very small amount of people
and removed
device/software specific
Issues that only happen on some devices or with some specific hardware/software
needs triage
Issue is not yet ready for PR authors to take up
labels
Jul 3, 2024
Checklist
Affected app version
1.0.0
Affected Android/Custom ROM version
Android 13 - Lineage OS 20
Affected device model
Redmi Note11S
How did you install the app?
F-Droid / IzzyOnDroid
Steps to reproduce the bug
When adding an alarm, click the default time value to set it, and when you finish selecting the hour immediately after lifting your finger, click ok
Expected behavior
Actual behavior
Screenshots/Screen recordings
screen-20240703-062132-smol.mp4
Additional information
This bug also happens on google's clock app (the one that comes with google services, not aosp)
Might be a material UI bug
"Discovered" after seeing this https://wetdry.world/@lexd0g/112708483036528818
The text was updated successfully, but these errors were encountered: