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

Timer alerts are late: alert is received from 3 to 5 minutes late when phone is locked and app is on background. #552

Open
fralacos opened this issue Nov 27, 2023 · 0 comments

Comments

@fralacos
Copy link

Timer alert of the end of set time triggers from ~3 to ~5 minutes late when the phone is locked and app is running on the background. Tested on Redmi Note 10 pro and POCO F5 phones, both running MIUI 14 Global / Android 13.

Steps to reproduce the problem:

  • Set a 10 minutes timer, start it, send the clock app to background, and lock the phone.
  • Wait for it to trigger, while taking the time with another clock.
  • 10 minutes passes, timer does not alert the end of the set time.
  • ~13 to ~15 minutes passes, timer alerts end of set time.

With the phone unlocked and the application running in foreground, there's no delay.
With the phone unlocked and the application running in background, there's no delay.
With the phone locked and the application running in foreground, there's no delay.

Fail scenario was also tested with the clock app from google, with no issues: alert comes at 10 minutes mark as expected.

Simple-clock app is set to "No restrictions" on battery saving settings, has the "lock" to prevent memory cleaner to close it, and all notification settings were given, including the ones related to show on lock screen.

Using version 5.11.2 installed with F-Droid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant