Closed JanicePolito closed 2 months ago
Maybe missing permission
<uses-permission android:name="android.permission.FOREGROUND_SERVICE_SPECIAL_USE" />
I am also experiencing this issue in Clock You version 8.0 (from F-Droid). My device is Samsung Galaxy A15 running Android 14.
In addition to this issue with the timer, when the screen is locked, the alarm clock does not ring or end up ringing long after the time that I have set. I wonder if that alarm clock problem could be related to this timer issue. @markbara-git Do you have similar issues with your alarms?
It might be instructive to compare the permissions in Clock You's app manifest against another open source Android alarm clock app such as Fossify Clock, which rings its timers and alarms as expected on my device (Samsung Galaxy A15 running Android 14).
Compare:
I hope that this bug gets fixed soon. Otherwise Clock You is not usable for its intended purpose (i.e. timer, alarms) on Android 14.
I use previous clock you version 7.1 without any issues with Android 14
@flux77 It seems that in my case the alarm works properly. The problem is with the timer.
I have the same issue with 8.0 from F-Droid. And sometimes the timer is hanging while it runs.
Tried 7.1 and the timer runs properly for me
Android automatically killed the timer service when the screen is off and thus also the corresponding notification - the finished notification is now independent of the service (different ID)
Steps to reproduce
Expected behavior
The timer should ring even when the phone is locked.
Actual behavior
The phone not ringing after the timer reached 0:00, instead the notification bubble starts counting backwards and you have to force stop the app.
Clock You version
8.0 from F-Droid
Android version
Android 14
Other details
Acknowledgements