Imagine your smartwatch, the one you rely on for everything from notifications to fitness tracking, suddenly becoming less functional because of a pesky bug. That's exactly what's happening to Pixel Watch and Galaxy Watch users right now. A glitch in Wear OS 6 and 6.1 is wreaking havoc on third-party watch faces, making them nearly unusable. But here's where it gets controversial: while both Google and Samsung have acknowledged the issue, a permanent fix remains elusive, leaving users frustrated and seeking workarounds.
Earlier this month, Wear OS 6.1 rolled out to Pixel Watch devices, promising a slew of improvements. However, users quickly noticed something odd: third-party watch faces were malfunctioning. The problem isn’t just limited to Pixel Watches; Galaxy Watch users on Wear OS 6-based One UI 8 Watch are experiencing the same headache. As reported by AsPiunikaWeb, users on both Google and Samsung forums have been complaining about watch faces getting stuck between their always-on display (AOD) versions and the full, unlocked watch face. This results in lingering AOD elements that make the full watch face difficult to read—a major inconvenience for something as essential as telling time.
And this is the part most people miss: the issue doesn’t appear immediately. It creeps up after using a third-party watch face for a while, with both Pixel and Galaxy Watches displaying semi-transparent AOD layouts over the normal watch face. This behavior seems tied to a change in Wear OS 6 that alters how watches transition from AOD to the full watch face. Both tech giants have confirmed the problem, with a Google IssueTracker case open since October. Yet, a definitive solution remains out of reach.
Here’s the kicker: this bug only affects third-party watch faces, not the pre-installed ones. This has led to speculation about whether the issue lies in how Wear OS 6 handles these transitions or if third-party developers need to adjust their designs. Either way, it’s a frustrating situation for users who rely on custom watch faces to personalize their devices.
If you’re experiencing this issue, swapping between third-party watch faces can temporarily alleviate the problem, but it’s far from ideal. A permanent fix likely requires Google to tweak Wear OS itself. For now, the safest bet is to stick with pre-installed watch faces—hardly a satisfying solution for those who love customizing their smartwatches.
But here’s a thought-provoking question: Is this a sign of deeper compatibility issues between Wear OS and third-party apps, or just a temporary hiccup? Let us know your thoughts in the comments. Are you affected by this bug? How are you coping with it? And do you think Google and Samsung are doing enough to address the issue? Your insights could spark an important conversation about the future of smartwatch customization.
