Timer fails to go off on time

WestQuester

I have an issue similar to and probably related to the one in this thread.

A running timer does not always go off on time. Sometimes it's a few seconds late and sometimes it has been as much as a minute late, only going off at say, -54 seconds.

Timer in the default clock app. App battery usage is unrestricted. Notifications permission is on.

NEQA

WestQuester

Yes, I have experienced the same for many months now, across two devices (6a and 8) and across factory resets. Roughly about 30% of the time the timer I set goes off about 1-3 minutes too late, occasionally 4-5 minutes (but never more than that). It's therefore not a huge deal for me, as the time delay is not large.

Every morning I put on my espresso maker, which takes almost exactly 13 minutes to boil. I put on a timer at 13 minutes, then swipe the Clock app away from the app switcher (the recently open apps view) without force stopping it. I then lock the screen and don't unlock it again during that time. Sometimes the timer will go off a few minutes after the espresso is finished; the screen lights up, displaying how many minutes and seconds ago the timer supposedly went off, and the timer audio plays. If I'm using the device actively when the timer reaches the end, it will always go off at exactly the specified time.

I don't have this issue with alarms, which always go off at the specified time.

I had a theory that it's related to having set a custom timer sound (an audio file), but it also occurs when the default timer sound is set.

Note that I always keep GrapheneOS up to date, I don't use adb or Developer options, and I don't change system app permissions. The app battery usage for Clock has always been set to Unrestricted.

As I said, this is not a big deal for me, but I am vaguely curious about what might be causing it.

other8026

WestQuester NEQA Never heard of people having this problem, but if I were in your situation I'd clear the Clock app's storage (keep in mind this will delete alarms and other things in the app). To do that, go to Settings > Apps > All apps > Clock > Storage & cache and clear the storage.

WestQuester

Anyone else experience this?

NEQA

other8026 I did this after posting and will report back after a few days of coffee making. Since the issue persisted across factory resets I don't expect it to make a difference, but who knows right. :)

other8026

NEQA Since the issue persisted across factory resets I don't expect it to make a difference

Oh. I missed this part. I agree then that it probably won't make a difference.

JohnDoe67

I have the exact same problem. Often when the timer goes off it says something like -56 seconds.
I just did a clean install of GOS yesterday, this issue is out of the box.

fid03

JohnDoe67 I have the exact same problem. Often when the timer goes off it says something like -56 seconds.
I just did a clean install of GOS yesterday, this issue is out of the box.

Strange. Do you happen to have other profiles or private space running in the background when this happens? Or perhaps lots of other apps in the background?

WestQuester

fid03 it happens to me when I have nothing else running in the background except GmsCompat. No private space or other profiles. It's not every time but it's often.

JohnDoe67

fid03 I do have one other profile, but not much else running in the background. I have battery saver permanently turned on, but that was never an issue on stock Android.