A frustrating glitch has been causing chaos for watch enthusiasts, specifically those with Pixel Watch and Galaxy Watch models. This issue, stemming from Wear OS 6, has left users scratching their heads and wondering why their beloved timepieces are acting up.
The problem arises with third-party watch faces, which are crucial for personalizing these devices. When users apply these custom faces, an unexpected bug occurs. The watch faces get stuck between their always-on display (AOD) versions and the full, unlocked face, leaving elements of the AOD lingering and making the main watch face harder to read.
Here's the kicker: this issue isn't an immediate red flag. It's a sneaky one that creeps up over time. Users report that after using a third-party watch face for a while, their Pixel or Galaxy Watch starts to overlay semi-transparent AOD layouts on top of the normal face. It's like the watch is having an identity crisis, showing two faces at once!
Both Google and Samsung have acknowledged this problem, with a Google IssueTracker case open since October. The issue seems to be related to a change in Wear OS 6, affecting how watches transition between AOD and full-face modes. It's a universal issue, impacting all Galaxy Watch and Pixel Watch models running Wear OS 6 or 6.1.
If you've noticed your watch misbehaving with watch faces, this could be why. Switching between third-party faces might provide a temporary fix, but a permanent solution is yet to be found. It seems Google might need to make some adjustments to Wear OS itself. In the meantime, sticking to pre-installed watch faces is the best way to avoid this bizarre display glitch.
So, there you have it. A simple bug, but one that's causing a big headache for watch lovers. It just goes to show that even the smallest details can have a big impact. What do you think? Have you encountered this issue? And if so, what workarounds have you found? Let's discuss in the comments!
