Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
My S6 arrived and I have the same problem. I keep "wake on wrist raise" turned off. After about a day and a half of experimenting this is what I can tell:

1. The time on the aod does lag behind the actual time.

2. The cause is almost always a lack of movement, a turn of my wrist and the time updates.

3. A lack of movement is not always the cause, sometimes the aod clock gets stuck and moving my arm/wrist up and down does nothing and I have to tap the screen or turn the crown for the clock to update to the correct time.

4. Changes in ambient lighting always causes the time to update. For example, when I wear my watch under a sleeve and then pull the sleeve back to check the time, the time is always behind for about a split second before it updates. It's almost instantaneous but I can see the lag.

5. When it gets stuck and moving my wrist doesn't fix it, if I angle the watch towards a light source and the screen gets brighter, the time instantly corrects itself.

This is an annoying bug. For example my wrist barely moves when I'm typing on a keyboard, when my eyes flick over to my watch the time is often 4-6 minutes behind. The whole point of an always on display (or having a watch on your wrist) is that it lets you see the accurate time without needing to make any overt movements, or having to interact with the watch at all.

I really hope Apple fixes this in 7.2.
 
Just had a call from Apple Support and the specialist assured me that this problem is being worked on and it will be fixed in an update. He couldn't tell me when this update will be released. His "workaround" was to disable always on display until the update is ready.......
Dear Jack,

I am having this problem too. I find it very annoying. But as you said, Apple Support told you that this problem is being worked on and will be fixed in an upcoming update so I am pretty relieved. Is there any chance you know when this update is going to come?
 
  • Like
Reactions: jackbauer1909
My S6 arrived and I have the same problem. I keep "wake on wrist raise" turned off. After about a day and a half of experimenting this is what I can tell:

1. The time on the aod does lag behind the actual time.

2. The cause is almost always a lack of movement, a turn of my wrist and the time updates.

3. A lack of movement is not always the cause, sometimes the aod clock gets stuck and moving my arm/wrist up and down does nothing and I have to tap the screen or turn the crown for the clock to update to the correct time.

4. Changes in ambient lighting always causes the time to update. For example, when I wear my watch under a sleeve and then pull the sleeve back to check the time, the time is always behind for about a split second before it updates. It's almost instantaneous but I can see the lag.

5. When it gets stuck and moving my wrist doesn't fix it, if I angle the watch towards a light source and the screen gets brighter, the time instantly corrects itself.

This is an annoying bug. For example my wrist barely moves when I'm typing on a keyboard, when my eyes flick over to my watch the time is often 4-6 minutes behind. The whole point of an always on display (or having a watch on your wrist) is that it lets you see the accurate time without needing to make any overt movements, or having to interact with the watch at all.

I really hope Apple fixes this in 7.2.
Great summary, I can confirm the lack of movement as a trigger for this behaviour. Really hoping for 7.2! Someone in the German Apple communities said that the recent beta fixed it for him. Lets hope that is really the case.

But I dont know when the official release will be.
 
I can add that turning on flight mode, with bluetooth and wifi both disabled on the watch (flight mode doesn't turn off bluetooth unless its manually turned off), forces this problem to happen permanently for me, i.e. the time will always lag unless I actively turn my wrist, not a little turn of my wrist but a full blown move my wrist parallel to my body and twist it. Rebooting the watch and phone doesn't fix it. I'm not flying anywhere but I wanted to see how much battery would get saved.

It's a good sign someone has seen this fixed in a 7.2 beta, lets hope it works out for everyone in the official release. I think it should be released in mid December, Apple said it would launch Fitness plus before the year end and that feature will come in 7.2. I wish they would focus their attention on bug fixes instead of new features. At this point I'm thinking of turning off the aod and simply tapping it for the time. It's disappointing. I returned my series 5 because I found it so incredibly buggy. The 6 is nowhere near as bad, it's quite good, I actually really like it but for this one problem.

I wonder if someone at Apple reads these posts? Watch currently reads 1615 as I type this. Computer clock says 1621.
 
  • Like
Reactions: jackbauer1909
I can add that turning on flight mode, with bluetooth and wifi both disabled on the watch (flight mode doesn't turn off bluetooth unless its manually turned off), forces this problem to happen permanently for me, i.e. the time will always lag unless I actively turn my wrist, not a little turn of my wrist but a full blown move my wrist parallel to my body and twist it. Rebooting the watch and phone doesn't fix it. I'm not flying anywhere but I wanted to see how much battery would get saved.

It's a good sign someone has seen this fixed in a 7.2 beta, lets hope it works out for everyone in the official release. I think it should be released in mid December, Apple said it would launch Fitness plus before the year end and that feature will come in 7.2. I wish they would focus their attention on bug fixes instead of new features. At this point I'm thinking of turning off the aod and simply tapping it for the time. It's disappointing. I returned my series 5 because I found it so incredibly buggy. The 6 is nowhere near as bad, it's quite good, I actually really like it but for this one problem.

I wonder if someone at Apple reads these posts? Watch currently reads 1615 as I type this. Computer clock says 1621.

In my opinion, they shouldn't wait for the release of the next major version... A small 7.1.x bug fix update would be great. After all, it's one of the most important that doesn't work here!
 
In my opinion, they shouldn't wait for the release of the next major version... A small 7.1.x bug fix update would be great. After all, it's one of the most important that doesn't work here!
I wish they would launch a small update and fix this. It's very annoying to have such a glaring bug on a premium product. At least I'm not alone and Apple have acknowledged it for other people. I spoke to Apple support too and they were unhelpful, wanted me to erase and set up the watch as new. They said nothing about a software update fixing it The watch is brand new and set up as new, no backups, just a few hours before the problem began so I'd say it's not worth trying to erase and set up again. I wasn't speaking to a specialist though, who I think are more knowledgeable than the regular support staff..

I have attached a video showing the issue. It's much worse on flight mode. Without flight mode it usually updates far quicker.
 
I have unpaired / repaired and set the watch up as new several (!) times on two series 6 devices, it changes nothing. The bug is always there. The support just has no other idea than erase and set up as new.
 
If you had hopes for 7.2 to fix this ... it does not. :-|
Please keep reporting this bug to Apple or we will have to live with the semi-useless AoD mode telling the wrong time sometimes.
 
  • Like
Reactions: jackbauer1909
I have returned my watch in part because of this bug. What good is a watch that I can't trust to tell the correct time when I look at it? If you bought it straight from Apple returns are open till Jan 8th I think. That at least is good of them.
 
  • Like
Reactions: jackbauer1909
It is absolutely ridiculous that this problem is still not solved. How on earth can such a big issue, when a WATCH does not show the correct TIME, last so long??? What are you doing Apple? And why are there so few complaints about this? I have my THIRD series 6 now, all have the same problem - so it must be software related.
 
Seems like not enough people are noticing&reporting this bug because it's still not fixed in watch OS 7.3 😢
 
This is why I can’t stand AOD. I mean it’s almost like not even having “always on display” ... so I leave AOD off. Just seeing the time catch up when I move my watch up (with AOD on) bugs the ever living .... out of me.
 
Yes the bug is still present in 7.3. It‘s unbelievable.

Last week I spoke to Apple Support and they told me the engineers are aware of that „time delay“ bug. Furthermore he said that the watch faces are the reason for this as some of them are not updated despite the new watchOS... Dont know, honestly I cant believe that...
 
Yes, this is SO annoying. I bought Apple watch 6 because i wanted to be able to check the time so that no one notices i’m doing so. I teach the piano and i need to check the time constantly so i’m aware how much time is left before the next student will come. I wanna do it so that the student won’t get distracted by me looking at my watch. That’s why i would like to see the CORRECT time without moving my wrist.
And now there’s a new problem: i need to raise my hand quite massively before the watch wakes up..😩 Is this even software related is is this unit broken? I paid 500€ for this ”watch” and i’m vey frustrated. Apple should stop selling this device as a ”watch” if it doesn’t act like one..!
 
Last edited:
  • Like
Reactions: jackbauer1909
Have you guys noticed whether any watch faces are unaffected by this problem?

So far, I've only seen the minute hand "jump" by 3-4 min on the California face.
 
  • Like
Reactions: jackbauer1909
I'm currently using Utility. Since I noticed the delay on California, I've paid more attention to the exact AOD time – so far no delay.
 
  • Like
Reactions: BigMcGuire
I have had a series 5 since it was released. I have never seen this jumping before, it is from a software update, not hardware. If it had been happening it would have bugged me quite a bit, hence the reason I am posting this. Here is the video.

 
  • Wow
Reactions: Nozuka
I have seen this behavior once since updating to the most recent OS. I rebooted the watch and it hasn’t done it again since.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.