| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 42 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 01:43:54 |
| Calls: | 220 |
| Calls today: | 1 |
| Files: | 824 |
| Messages: | 121,543 |
| Posted today: | 6 |
Anyone else noticed recently that whenever using a timer for, say, cooking that there's a noticeable delay from the timer ending to the alarm actually going off?
It used to be that the alarm would go off immediately the timer hits 0. Now there's a 3-5 sec delay. I can see it on the display where when it hits 0
the screen goes blank, waits, waits and then rings. Or if I'm listening to some music, the music pauses, waits, waits and then the alarms rings.
I'm not using any unusual alarm tone.
I think it's since updating to 17.7.
Anyone else noticed recently that whenever using a timer for, say, cooking that there's a noticeable delay from the timer ending to the alarm actually going off?
It used to be that the alarm would go off immediately the timer hits 0. Now there's a 3-5 sec delay. I can see it on the display where when it hits 0
the screen goes blank, waits, waits and then rings. Or if I'm listening to some music, the music pauses, waits, waits and then the alarms rings.
I'm not using any unusual alarm tone.
I think it's since updating to 17.7.
Chris <ithinkiam@gmail.com> wrote:
Anyone else noticed recently that whenever using a timer for, say, cooking >> that there's a noticeable delay from the timer ending to the alarm actually >> going off?
It used to be that the alarm would go off immediately the timer hits 0. Now >> there's a 3-5 sec delay. I can see it on the display where when it hits 0
the screen goes blank, waits, waits and then rings. Or if I'm listening to >> some music, the music pauses, waits, waits and then the alarms rings.
I'm not using any unusual alarm tone.
I think it's since updating to 17.7.
Not an issue for me using 18.1.
Chris wrote:
Anyone else noticed recently that whenever using a timer for, say,
cooking that there's a noticeable delay from the timer ending to the
alarm actually going off?
It used to be that the alarm would go off immediately the timer hits
0. Now there's a 3-5 sec delay. I can see it on the display where
when it hits 0 the screen goes blank, waits, waits and then rings. Or
if I'm listening to some music, the music pauses, waits, waits and
then the alarms rings.
I'm not using any unusual alarm tone.
I think it's since updating to 17.7.
How do you know there's a delay unless you're actually looking at the
timer count down?
If you're actually looking at the timer count down,
then you know the the set time is over and you can take the cooked egg
off the stove.
Alan Browne <bitbucket@blackhole.com> wrote:
On 2024-11-05 03:38, Chris wrote:
Anyone else noticed recently that whenever using a timer for, say, cooking >>> that there's a noticeable delay from the timer ending to the alarm actually >>> going off?
It used to be that the alarm would go off immediately the timer hits 0. Now >>> there's a 3-5 sec delay. I can see it on the display where when it hits 0 >>> the screen goes blank, waits, waits and then rings. Or if I'm listening to >>> some music, the music pauses, waits, waits and then the alarms rings.
I'm not using any unusual alarm tone.
I think it's since updating to 17.7.
I'd put it at 1.5 steamboats late (iOS 18.1).
It's definitely three mississippis minimum, here.
When starting a timer on the phone or watch by voice (Siri), it seems to
record when I pressed the side/stem button, so you see the timer already
2 seconds or so "in" the count by the time it's displayed and announced.
The alarm on the watch is less than 0.5 steamboats late. But then I use
the timer a lot every day (timing coffee in the presse-café to many
other things), so maybe it's "readier").
It's every time, now.
I'll try a few reboots and see if that makes a difference.
Paul Goodman <no_email@invalid.invalid> wrote:
Chris <ithinkiam@gmail.com> wrote:
Anyone else noticed recently that whenever using a timer for, say, cooking >>> that there's a noticeable delay from the timer ending to the alarm actually >>> going off?
It used to be that the alarm would go off immediately the timer hits 0. Now >>> there's a 3-5 sec delay. I can see it on the display where when it hits 0 >>> the screen goes blank, waits, waits and then rings. Or if I'm listening to >>> some music, the music pauses, waits, waits and then the alarms rings.
I'm not using any unusual alarm tone.
I think it's since updating to 17.7.
Not an issue for me using 18.1.
Thanks for the data point. Do you use it regularly?
Alan Browne <bitbucket@blackhole.com> wrote:
On 2024-11-05 12:41, Chris wrote:
Alan Browne <bitbucket@blackhole.com> wrote:
On 2024-11-05 03:38, Chris wrote:
Anyone else noticed recently that whenever using a timer for, say, cooking
that there's a noticeable delay from the timer ending to the alarm actually
going off?
It used to be that the alarm would go off immediately the timer hits 0. Now
there's a 3-5 sec delay. I can see it on the display where when it hits 0 >>>>> the screen goes blank, waits, waits and then rings. Or if I'm listening to
some music, the music pauses, waits, waits and then the alarms rings. >>>>>
I'm not using any unusual alarm tone.
I think it's since updating to 17.7.
I'd put it at 1.5 steamboats late (iOS 18.1).
It's definitely three mississippis minimum, here.
Well if you're going to change units ...
You started it :p
When starting a timer on the phone or watch by voice (Siri), it seems to >>>> record when I pressed the side/stem button, so you see the timer already >>>> 2 seconds or so "in" the count by the time it's displayed and announced. >>>>
The alarm on the watch is less than 0.5 steamboats late. But then I use >>>> the timer a lot every day (timing coffee in the presse-café to many
other things), so maybe it's "readier").
It's every time, now.
I'll try a few reboots and see if that makes a difference.
A solution: the s/w engineer could setup a 2nd timer to pre-load
resources a few seconds ahead of the actual timer.
Or set the timer to 4 sec less than required.