Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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 ist should realise this and keep on contacting the support.
A problem like this, or even AOD not updating time should be corrected by resetting the watch as new. (reset, not restart)
 
Yes, it should be. But it doesn‘t. I have resetted and set up as new three times in the last weeks but this bug is always there.
 
Yes, it should be. But it doesn‘t. I have resetted and set up as new three times in the last weeks but this bug is always there.
Test this. Reset as new. Don’t restore from old backup, then don’t install any 3rd party apps.
 
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.

Most folks don't fly off the handle quite so quickly, or they edit/update their post when they realize they'd misunderstood something or when what they were replying to had been updated.

But hey, be who you gotta be. 👍

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.
Every time I actively look at my watch it shows the correct time.

The issue crops up with an idle watch and glancing at it without waking the watch. My experience with my S5 and S6 is that I rarely ever noticed the idle/AOD time fall behind -- and on the occasions it did the difference was 1-2 minutes. Maybe it did it often and I seldom noticed (for time sensitive scenarios I'm actively looking at the watch, thus waking it) or maybe it did it seldom.

Lagging several minutes behind is a bug - notice a reboot fixed it -- and presumably we'll see that one fixed in a future update. The x.0.0 watchOS releases have typically been kinda buggy in recent years - I'd usually suggest folks wait for at least an x.0.1 or even x.1 release if they're particularly sensitive to such things...

As for a WATCH not showing the TIME, where were you throughout the S0 through S4 models with blank idle displays? :D
 
Last edited:
I'm currently on Watch OS 8.0 (I have a S4 Apple Watch) and my iPhone (13 Pro) is on iOS 15.0.

I have a strange thing going on with a particular watchface on my Watch - its the Activity Analogue watchface specifically.

So this is the issue: Lets say the current time is 11:00am and I don't look at the watchface for a number of minutes, when I next go to look at the watchface, the hands of the clock correctly show the correct time however, the hands actually jump from the previous time to the correct time (so, for a fraction of a second, I will see the hands at 11:00 but then I actually see them jump to the current time) ??

Its like the hands get stuck at the last time at which I looked at the screen but then suddenly jump to the correct time??! This is happening every singe time I look at the screen and it is ONLY happening on this particular watchface (it does NOT happen on any other analogue watchface)??
 
...that doesn't unfortunately solve the issue - I've just rebooted my watch but that watch face is doing the same thing. It has to be a bug somewhere.....
That's so annoying. This bug should never have happened. I wish Apple fixes it ASAP.
 
  • Sad
Reactions: Dino F
Just discovered this bug on my Series 6. It only happened on my Nike Bounce Watch face but not the old Watch face that I used.
 
  • Sad
Reactions: Dino F
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.