Every watch face is 10:09 then updates to correct time

[Asthmatic Kitty]

Agree that it's an annoying bug that they should fix. This didn't used to happen; it was only after they removed the swipe-to-change-face feature and then put it back in a point update that it started happening, afaik. It's pretty sloppy that the bug hasn't been fixed in all this time, think it was something like 10.1 or 10.2 where the swipe-to-change-face feature returned (with the bug).

 

[Shirasaki]

was only after they removed the swipe-to-change-face feature and then put it back in a point update that it started happening,

Afaik, Apple Watch Ultra can’t swipe to change watch faces, at least that’s whats happening on mine running watchOS 11.0.1.

 

[Howard2k]

Afaik, Apple Watch Ultra can’t swipe to change watch faces, at least that’s whats happening on mine running watchOS 11.0.1.

It's under Clock settings on the Watch app on the phone. Disabled by default.
EDIT: Nevermind, I'm still running OS10. But check there anyway.

 

[Shirasaki]

It's under Clock settings on the Watch app on the phone. Disabled by default.
EDIT: Nevermind, I'm still running OS10. But check there anyway.

Turns out I turned that feature off a while ago because it triggered too many unintended face switches. After turning it back on, I can see what OP is complaining about. The best I can guess is watchOS is loading the watch face first before setting the time to the current time.
Still, I consider this a non-issue. Btw, updating the watchOS to 11 won’t solve that “issue”.

 

[iMacDragon]

I have to agree that this behaviour has annoyed me, it definitely 'feels' like a kludge to restore the swipe behaviour as easily as possible after the initial change to require long press.

 

[Ta_whirimatea]

I’ve had a series 0, 3, 6 & now 10. It never happened on my 0 or 3 but did /does happen on my 6 & 10 when swiping faces.

I find this 10:09 thing annoying too but tbh it’s typical of apple nowadays to have some daft software bug visible for years on end. My mac has had other software issues that have been present for years after software ‘updates’. I’ve given up & accepted it’s just down to poor coding / laziness. They have ur money & don’t care..

 

[Howard2k]

I’ve had a series 0, 3, 6 & now 10. It never happened on my 0 or 3 but did /does happen on my 6 & 10 when swiping faces.

I find this 10:09 thing annoying too but tbh it’s typical of apple nowadays to have some daft software bug visible for years on end. My mac has had other software issues that have been present for years after software ‘updates’. I’ve given up & accepted it’s just down to poor coding / laziness. They have ur money & don’t care..

Sure. It's a bug and laziness. Or it might be that it's more efficient for the watch to not keep all faces and complications loaded at the same time.

If it is super bothersome you can submit feedback to Apple.

 

[jonblatho]

For the record, 9:41 on iOS and 10:09 on watchOS is the time when the first generation of such product category was introduced Back then.

Neither of these is true.

Apple reportedly chose 9:41 AM for the iPhone (and later other iOS devices and Macs) because that was about the time they expected to get to the first appearance of the iPhone when announcing it at Macworld 2007. They ran a few minutes late. Some of the early iPhone marketing shots also displayed 9:42 AM.

The watch wasn't remotely close to 10:09. That Apple event began at 10 AM Pacific (as most do) and the watch was unveiled about an hour in. Others have already pointed out that ~10:09 is often used by watchmakers in marketing shots to neatly distribute the clock hands.

 

[tolili alert]

This also happens with the world clock complication and yes… It’s annoying.

if you want to take a quick/glance at the time… It is certainly not ideal to see one hour and then see another the next moment. It is simply unnecessary.

I don't understand so much criticism of the user who opened the thread.


Try this:

Counter face.

Upper complication: Digital hour

Lower complication: Digital hour (not the sane as the other)


Lower complication will not be affected by this 10:09 situation. It’s ridiculous.

 

[johnmacward]

The OP's use case is quite unique and something that I'd imagine very people use - changing the watch face 4 times per day, and hence going back to watch face choice page which automatically sets the time to 10:09 (a design choice, and not at all a bug) and sets default visual values for complications like fitness rings, weather etc.

Can't an Apple watch be programmed to change its watch face depending on the context or the Concentration mode. For example, OP, you could set up a driving concentration mode for your phone and watch and it changes the watch face to your desired without having to see the 10:09.

This also happens with the world clock complication and yes… It’s annoying.

if you want to take a quick/glance at the time… It is certainly not ideal to see one hour and then see another the next moment. It is simply unnecessary.

I don't understand so much criticism of the user who opened the thread.


Try this:

Counter face.

Upper complication: Digital hour

Lower complication: Digital hour (not the sane as the other)


Lower complication will not be affected by this 10:09 situation. It’s ridiculous.

It seems to me to be probably more related to efficiency for such a lower powered SOC in displaying an example of the complications and the time, rather than downloading a bunch of information which seems to take literally a few seconds per complication (again Apple Watch SOC's are not very quick, they take significant time to load weather info, fitness info, calendar info) leading a user to believe the watch is sluggish and slow (which to be fair, it is, at least my series 6 is)... Instead they have some default numbers to reference which is quick and provides a visual idea without slowing the user down. It's also a nod to the watch industry that sets all their example watch faces to 10:10 / 10:09 as its "aesthetically pleasing" (whatever you think about that).

Ethos talks about it here: https://www.ethoswatches.com/the-watch-guide/why-all-clocks-show-10-10/

Sure. It's a bug and laziness.

It's really not, it's a design choice for a piece of hardware that's not very fast.

EDIT: I now see the stupidity of this issue when you restore the "Swipe to change watch face" option. The watch face always reverts to 10:09 before showing the correct time, and personally it is stupid. I thought the OP tapped long on the screen and changed the watch face in the watch face selector screen for which seeing a standardised 10:09 is totally normal.

@Howard2k, I agree with you - it is a bug, at the very least its very poor coding.

 

[MarkFlynn11]

Watch faces always show 10:09 before switching to correct time. This is annoying and intolerable for an expensive product. Rolex or Seiko wouldn't force 10:09 on owners before updating to current time. Apparently 10:09 is used in marketing as it is aesthetically pleasing for visuals. Apple needs to neuter their marketing ****s.

Apple Watch 4 10.6.1

Honestly who cares...

 

[captchasverybadman]

Watch faces always show 10:09 before switching to correct time. This is annoying and intolerable for an expensive product. Rolex or Seiko wouldn't force 10:09 on owners before updating to current time. Apparently 10:09 is used in marketing as it is aesthetically pleasing for visuals. Apple needs to neuter their marketing ****s.

Apple Watch 4 10.6.1

What would Apple be without marketing?

 

[JustinKent]

I've also noticed this issue and find it bothersome. Yes it's a regression having to do with removing and then re-introducing swipe to change faces feature.

 

[childu]

Watch faces always show 10:09 before switching to correct time. This is annoying and intolerable for an expensive product. Rolex or Seiko wouldn't force 10:09 on owners before updating to current time. Apparently 10:09 is used in marketing as it is aesthetically pleasing for visuals. Apple needs to neuter their marketing ****s.

Apple Watch 4 10.6.1

I noticed when it came out and it’s super annoying. I wrote a complaint to Apple in the Feedback section of their website. Together with the need to push a button for control center.

 

[ignatius345]

Rolex or Seiko wouldn't force 10:09 on owners before updating to current time

Good point. When I actively swipe between a hundred different faces on my Rolex, they all show the correct time.

 

[hagjohn]

Watch faces always show 10:09 before switching to correct time. This is annoying and intolerable for an expensive product. Rolex or Seiko wouldn't force 10:09 on owners before updating to current time. Apparently 10:09 is used in marketing as it is aesthetically pleasing for visuals. Apple needs to neuter their marketing ****s.

Apple Watch 4 10.6.1

Really? With all the things you could complain about, this is what you chose?

 

[Yimbaz]

I just tried switching between faces on my watch (Series 5, 10.6.1) and I do see the 10:09 placeholder for a very brief moment when the new face slides in. I think it says something about the seriousness of this "issue" that I've had this watch for five years and this is the first time I've noticed it.

 

[Bandeeto]

I see this issue as a rather unimportant one, and frankly kind of like the design/style approach.

That being said, for the people that this bothers, would you accept an impact to the battery life if all of your faces required some resources to keep them spooled up in the background? I know I wouldn’t, and maybe there wouldn’t be a battery implication. I think it’s unfair to assume this is sloppy programming.

 

[Mr.Fox]

Watch faces always show 10:09 before switching to correct time. This is annoying and intolerable for an expensive product. Rolex or Seiko wouldn't force 10:09 on owners before updating to current time. Apparently 10:09 is used in marketing as it is aesthetically pleasing for visuals. Apple needs to neuter their marketing ****s.

Apple Watch 4 10.6.1

It's a miracle! Time has stopped ))))

 

[BeefCake 15]

I agree, it feels clunky when switching faces and having to wait a second for it to update to the right time, wouldn't be an issue if it was not doing that before to begin with....

 

[Jumpthesnark]

If I understand correctly, this "issue" only shows up when a wearer is actively changing the watch face. Not when the watch is glanced at or used in any other way, correct?

So the user knows that they are not getting an accurate display of the time in the moment that they are making this one change.

Maybe I'm not OCD enough, but.... who cares? The user is causing this display to change to a default (presumably, it's so wearers can see what a different face looks like when it's being used) while they change the face. It's not something the watch is doing on its own, something that could fool the wearer into getting the wrong time. User changes face, face temporarily switches to its default display while the user is making the change, watch goes back to normal, displaying the correct time.

I just don't see how this matters, in the least. Does the wearer even need to know the correct time in that one moment when, presumably, they just looked at their watch before changing the face? I mean.... the correct time was right there a second ago. Time did not change. The user is making the change. No confusion.

If I'm wrong in my understanding of what's happening then please let me know. But if all it is is people who can't bear to look at 10:09 for a moment while they're actively changing the face, when they know they are causing the change themselves, then I just don't see the issue.

 

[Howard2k]

If I understand correctly, this "issue" only shows up when a wearer is actively changing the watch face. Not when the watch is glanced at or used in any other way, correct?

So the user knows that they are not getting an accurate display of the time in the moment that they are making this one change.

Maybe I'm not OCD enough, but.... who cares? The user is causing this display to change to a default (presumably, it's so wearers can see what a different face looks like when it's being used) while they change the face. It's not something the watch is doing on its own, something that could fool the wearer into getting the wrong time. User changes face, face temporarily switches to its default display while the user is making the change, watch goes back to normal, displaying the correct time.

I just don't see how this matters, in the least. Does the wearer even need to know the correct time in that one moment when, presumably, they just looked at their watch before changing the face? I mean.... the correct time was right there a second ago. Time did not change. The user is making the change. No confusion.

If I'm wrong in my understanding of what's happening then please let me know. But if all it is is people who can't bear to look at 10:09 for a moment while they're actively changing the face, when they know they are causing the change themselves, then I just don't see the issue.

If only there was a way to look at the time both before and after swiping the face change outside of the brief 10:09 display. This would be a total non-event, then you'd know for sure that it's really not 10:09. In the absence of any sort of mechanism to do that I can see the confusion though. Is it really 10:09? Who could possibly say.

 

[DrWojtek]

How DARE they tell you what time it is! Even for a slight second!

 

[tolili alert]

If I understand correctly, this "issue" only shows up when a wearer is actively changing the watch face. Not when the watch is glanced at or used in any other way, correct?

So the user knows that they are not getting an accurate display of the time in the moment that they are making this one change.

Maybe I'm not OCD enough, but.... who cares? The user is causing this display to change to a default (presumably, it's so wearers can see what a different face looks like when it's being used) while they change the face. It's not something the watch is doing on its own, something that could fool the wearer into getting the wrong time. User changes face, face temporarily switches to its default display while the user is making the change, watch goes back to normal, displaying the correct time.

I just don't see how this matters, in the least. Does the wearer even need to know the correct time in that one moment when, presumably, they just looked at their watch before changing the face? I mean.... the correct time was right there a second ago. Time did not change. The user is making the change. No confusion.

If I'm wrong in my understanding of what's happening then please let me know. But if all it is is people who can't bear to look at 10:09 for a moment while they're actively changing the face, when they know they are causing the change themselves, then I just don't see the issue.

The same happens with digital hour as complication and that's not something to be happy about.

 

[Yimbaz]

Thank you, now it makes sense, but still annoying if I want to use the swipe method, it is somewhat understandable using the long press.

It just goes to show that when there's a OS upgrade, one is expected to pore over the release notes to acquaint one's self with new "features" that are not readily obvious.

I'm a user that want's a watch that "just works"

It sounds like you have a watch that "just works," you just didn't know how it worked.