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

Selecting the Hour for an alarm and clicking ok immediately will result a non 00 minutes #80

Open
7 tasks done
fluoriteByte opened this issue Jul 3, 2024 · 0 comments
Labels
bug Something is not working niche Only relevant to a very small amount of people

Comments

@fluoriteByte
Copy link

Checklist

  • I can reproduce the bug with the latest version given here.
  • I made sure that there are no existing issues - open or closed - to which I could contribute my information.
  • I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
  • I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
  • This issue contains only one bug.
  • I have read and understood the contribution guidelines.

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

  • 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

@fluoriteByte fluoriteByte added bug Something is not working needs triage Issue is not yet ready for PR authors to take up labels Jul 3, 2024
@Aga-C 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is not working niche Only relevant to a very small amount of people
Projects
None yet
Development

No branches or pull requests

2 participants