More ios 26 woes.
May week I used the timer to ring after 1 hour which worked fine. Since
then every timer I set defaults to an hour. I don't notice this as mostly
my timers are 10-20 minutes so I only look at the minites "dial". That is until after a while I realise the timer hasn't gone off and there's now 55 minutes remaining. Resulting in overcooked meals.
Prior to setting that hour long timer the default was always 0 in hour "dial". Now it is 1.
Anyone else seeing this?
On 2026-01-27 01:18, Chris wrote:
More ios 26 woes.
May week I used the timer to ring after 1 hour which worked fine. Since
then every timer I set defaults to an hour. I don't notice this as mostly
my timers are 10-20 minutes so I only look at the minites "dial". That is
until after a while I realise the timer hasn't gone off and there's now 55 >> minutes remaining. Resulting in overcooked meals.
Prior to setting that hour long timer the default was always 0 in hour
"dial". Now it is 1.
Anyone else seeing this?
Nope.
I just launched the Clock app, and checked the timer, and it was set for whatever I used last.
I just set a 1 minute timer and locked the iPhone...
...and now that the minute has expired, I've unlocked the phone, opened
the Clock app again, and...
...naturally, the timer function is set to run a new 1 minute timer.
Alan <nuh-uh@nope.com> wrote:
On 2026-01-27 01:18, Chris wrote:
More ios 26 woes.
May week I used the timer to ring after 1 hour which worked fine. Since
then every timer I set defaults to an hour. I don't notice this as mostly >>> my timers are 10-20 minutes so I only look at the minites "dial". That is >>> until after a while I realise the timer hasn't gone off and there's now 55 >>> minutes remaining. Resulting in overcooked meals.
Prior to setting that hour long timer the default was always 0 in hour
"dial". Now it is 1.
Anyone else seeing this?
Nope.
I just launched the Clock app, and checked the timer, and it was set for
whatever I used last.
I just set a 1 minute timer and locked the iPhone...
...and now that the minute has expired, I've unlocked the phone, opened
the Clock app again, and...
...naturally, the timer function is set to run a new 1 minute timer.
That was the behaviour I saw as well; before setting the 1 hour timer.
Since then, the behaviour has changed.
Can you try setting a 1 hour or more timer and see what happens after that, please?
Alan <nuh-uh@nope.com> wrote:
On 2026-01-27 01:18, Chris wrote:
More ios 26 woes.
May week I used the timer to ring after 1 hour which worked fine. Since
then every timer I set defaults to an hour. I don't notice this as mostly >>> my timers are 10-20 minutes so I only look at the minites "dial". That is >>> until after a while I realise the timer hasn't gone off and there's now 55 >>> minutes remaining. Resulting in overcooked meals.
Prior to setting that hour long timer the default was always 0 in hour
"dial". Now it is 1.
Anyone else seeing this?
Nope.
I just launched the Clock app, and checked the timer, and it was set for
whatever I used last.
I just set a 1 minute timer and locked the iPhone...
...and now that the minute has expired, I've unlocked the phone, opened
the Clock app again, and...
...naturally, the timer function is set to run a new 1 minute timer.
That was the behaviour I saw as well; before setting the 1 hour timer.
Since then, the behaviour has changed.
Can you try setting a 1 hour or more timer and see what happens after that, please?
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 59 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 20:57:30 |
| Calls: | 810 |
| Calls today: | 1 |
| Files: | 1,287 |
| D/L today: |
11 files (21,026K bytes) |
| Messages: | 194,568 |