WatchOS 8 Always On Display issue

[Person08]

I don’t know if this is an issue on my part, but my always on display on AW Series 6 ProductRED 44mm is lagging behind by 4-6 minutes. It will say 12:00 when its not fully on, but i raise my wrist and it will say 12:04. Anyone else seeing this? Thanks!

 

[drumcat]

Yes, same. I have a AW5, and whenever it's on 1hz mode, the time is no longer updated. It only happened with WOS8.

Very annoying to think the time is that far off.

 

[BugeyeSTI]

This was happening in WatchOS 7 also. It's a known issue that's never been addressed

 

[drumcat]

It wasn't an issue on my watch in WOS7. ¯\_(ツ)_/¯

 

[Person08]

I also wasn’t affected in WOS7

 

[owaint]

Same with my series 5 - it was fine on os7 and broken now. There’s literally no point to always on display if the time doesn’t update. How did this get through beta testing??

 

[drumcat]

Same with my series 5 - it was fine on os7 and broken now. There’s literally no point to always on display if the time doesn’t update. How did this get through beta testing??

How did this get through testing?

It's the basic function of the watch. Imagine an iOS update that prevented phone calls unless the phone was unlocked...

 

[bricktop_at]

This was happening in WatchOS 7 also. It's a known issue that's never been addressed

Yep, I occasionally noticed it also on OS7. Didn‘t bother me much then and also not now.

 

[drumcat]

Yep, I occasionally noticed it also on OS7. Didn‘t bother me much then and also not now.

So if your iPhone was showing the incorrect time until you unlocked it, that wouldn't bother you?

 

[bricktop_at]

So if your iPhone was showing the incorrect time until you unlocked it, that wouldn't bother you?

Yep, I don’t use my phone to check the time
Plus: The Watch shows the incorrect time (for some people) unless they raise the wrist to look at it, not until they unlock it ;-)

 

[matrix07]

How did this get through testing?

Because it doesn’t happen to everyone.

 

[andyw715]

It also seems to go into AOD mode quickly. To duplicate the OT's issue I used to have to turn my wrist to activate it. Now I can raise my wrist and within 5 seconds it goes into AOD mode.

 

[deeddawg]

Saw this in watchOS7 on my series6 every now and then.

Can't say as it ever was an issue for me - anytime I've really needed to know exact time I'm moving my wrist to look at the watch and it's updated. At other times a couple or three or four minutes is immaterial.

 

[Dobbel]

When you turn your wrist - you only want to see time - it stays on 5 sec.
However when you touch the screen it stays on 1 minute.

 

[andyw715]

When you turn your wrist - you only want to see time - it stays on 5 sec.
However when you touch the screen it stays on 1 minute.

ahhh....is that new to WatchOS 8?

 

[bricktop_at]

ahhh....is that new to WatchOS 8?

Nope

 

[Dobbel]

Actually the minute is 70 secs, and settable in settings to 15 sec.

 

[drumcat]

It's very annoying to me… it defeats the purpose of "always on". I'm looking at it now as I type, and it's sitting there 14 minutes behind.

The always-on feature is literally based on the fact that this won't happen. Otherwise, why would you have an always-on screen? There's no point in having an inaccurate always-on; in fact, you'd want to turn the always-on feature _off_ in order to make sure you don't get the wrong time.

Interestingly, a notification came through, saw that, and the time *still* wasn't updated.

Really poor.

 

[Howard2k]

Some folks have said that restarting the watch has solved the issue.

 

[drumcat]

You know what… I did it again. Reboot this time has cleared it up. Thanks Howard.

 

[deeddawg]

It's very annoying to me… it defeats the purpose of "always on". I'm looking at it now as I type, and it's sitting there 14 minutes behind.

14 minutes is excessive. A couple minutes isn’t uncommon though and would generally be immaterial.

glad a reboot cleared it up. We’re on an x.0.0 software release. These are usually a bit buggy. First order of business is do a reboot and see if the issue the issue repeats or how long until it comes back.

 

[drumcat]

14 minutes is excessive. A couple minutes isn’t uncommon though and would generally be immaterial.

I’m surprised you hadn’t already done a reboot before reporting the problem? We’re on an x.0.0 software release. These are usually a bit buggy. First order of business is do a reboot and see if the issue the issue repeats or how long until it comes back.

Back up Hee Haw, I did a reboot before. This reboot was under 15.0.1 on the phone, so I imagine something changed.

 

[deeddawg]

Back up Hee Haw, I did a reboot before. This reboot was under 15.0.1 on the phone, so I imagine something changed.

Read the edited-before-you-replied post before going off your rocker.

 

[drumcat]

Read the edited-before-you-replied post before going off your rocker.

You'll see in my reply that I answered your unedited reply because that's what was there. I'm good, but I don't predict future edits.

 

[jackbauer1909]

It‘s really interesting that most of you aren‘t bothered by a WATCH not showing the correct TIME. Come on, this bug is just ridiculous and it‘s a shame that it isn‘t immediately adressed by Apple.

I have talked many times with the apple support when this same bug was there in watchOS 7.0 until 7.4. They never really knew what was going on. And now it has returned.

A restart solves the problem for a day or two but never longer. The idea of the AoD is completely destroyed by this bug. All of us should realise this and keep on contacting the support.