Is anyone else having an issue on their pixel watch 3 where after updating to wear os 6, all WFS watchfaces often don’t properly transition to their AOD state? It sort of fades between the two states but often gets stuck half way through? I’ve noticed this on my homemade faces, and all other that I’ve purchased on google play that was made with WFS…
Wondering if it’s just a Pixel Watch thing or it’s wear os wide?
3 Likes
Nope, my Watch 8 Classic does it too.
2 Likes
I do not actually use AOD on my watch . It has always seemed Broken since Day one on Faces from any Platform . Yes the current two step dimming is nonsense .
I’ve had a few users report this very recently on different watch faces.
They were all Pixel Watch 3 users who just updated to Wear OS 6, and one Pixel Watch 4 user.
I tried testing all these faces on Galaxy Watch 8 and 8 Classic (which I use daily), and couldn’t replicate the issue in any of them.
Unrelated (or perhaps not), another Pixel Watch 3 user reported an issue with some app shortcuts suddenly not working after a Wear OS 6 update, specifically the health://steps app shortcut in that case.
Looks like every year there has to be something wrong on Pixel Watch devices after a Wear OS update, before it’s fixed by a patch 
Hopefully Google issues a fix soon, it might help if we all send individual bug reports to Google about this.
3 Likes
I’m seeing it on my 6 Classic with WearOS 6 Beta 2, but not on my 2024 Ultra with WearOS 6.
2 Likes
I’ve also noticed the auto theme colour function doesn’t work on any of the WFS faces either :C
1 Like
I’ve also received several similar reports recently, all from users with Pixel Watches running Wear OS 6
2 Likes
I have the exact same issue on my Pixel Watch 4 with the watch face I created myself in the Samsung Watch Face Studio.
Is there already an issue in Google issuetracker?
Edit: Yes there is:
I hope Google (or possibly Samsung) will fix it quickly as it’s really annoying.
2 Likes
I strongly recommend anyone who’s experienced this issue to +1 it on the Google Issue Tracker, and provide additional info if possible. Google will prioritise the fix if they think it’s widespread, rather than just happening with one user or watchface.
+1’d and commented, nice!
1 Like
I’ve just suffered from the OS 6 AOD bug too. I added to the issue tracker.
There really should be an option in Samsung Watch Face Studio to disable this transition opacity fade (NORMAL → AOD), like it used to be before version 6.0.
It would be great if we could force the watch to switch instantly, without any transition.
Since the watch face layers also become semi-transparent during the fade, it causes additional visual glitches during the transition.
Samsung — would this be technically possible to implement?
Or is this more of a higher-level Wear OS “feature”? 
1 Like
I think it’s the latter. See the Google Issue Tracker link above. Ideally, +1 it!
Thanks for mentioning the existing issue above! Just hit +1 on it too 
2 Likes
Absolutely we should.
Fixed. At least on the Pixel watch. Yesterday there was an update called “Pixel watch face,” if I remember correctly.
What about Samsung?
1 Like
This issue never appeared on Samsung. On my Pixel Watch 3 the update hasn’t shown up yet, but I’m really looking forward to it.
1 Like
The issue tracker has 44 +1s, but I haven’t seen a single complaint about this issue on Google’s Pixel Watch user support forum. The only explanation I can think of is that the only people who use third-party watchfaces are developers (at least on Pixel Watches).
If this issue doesn’t affect OEM-provided watch faces, we could be in for a long wait.