-
Notifications
You must be signed in to change notification settings - Fork 10
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
Timer will continue to run if it is set to less than 5 seconds. #5
Comments
I also made some tests, I find the same error as you. I am currently unable to find the solution. |
can you assign me ? |
Hi @qw123wh @CikiMomogi , i am interested by the issue , i would like to know if you are still active on the project because i can fin a solution . Thank you |
@GokhanKabar @Aladin056 the project is active, if you can solve the issue of pull requests, I will then join them to the main branch. I am looking for collaborators for this project, I have some nice ideas to make this app even more functional. Your help is greatly appreciated |
Impossible to find the cause... 😭 |
I test the app and i have some notes: The timer will continue counting negative (when foreground or background) if set to 1 or 2 secs. |
I've also noticed this, but I can't find the part of the code that causes this bad behavior. Note: it seems to be the same on the LineageOS clock application. |
No, @BlackyHawky I have another phone (with LineageOS 18.1 -Android 11- on it), and this problem is not found in the Clock app, except when you set the timer for 1 second (i think because the 1 sec. timer is very low or small to handle correctly) |
@MaroEldawwy6 It'll confirm what I've said... Watch videoSVID_20240529_203317_1.mp4 |
@BlackyHawky I found the solution, botxxxx/lib-com.android.deskclock@5f19c68 I tested it on the old AOSP clock, the first on the repository that I haven't updated for 3 years; the changes of TimerItemFragment.java works. Now see if you can adapt this to the new code, since the TimerItemFragment.java file no longer exists |
@qw123wh Did you find the same thing? |
@BlackyHawky Yes same problem, I didn't notice it. Partially resolved. Create a branch with the modification, then we may find some solution to solve it completely |
Steps to reproduce:
Expectation:
The text was updated successfully, but these errors were encountered: