Galaxy Watch Faces Glitch: One UI 8 Watch Users Report AOD Transition Issues
A new bug impacting Galaxy Watch users running One UI 8 Watch (based on Wear OS 6) is causing watch faces to freeze during transitions from always-on display (AOD) mode, resulting in visual artifacts and a frustrating user experience. A potential fix is anticipated on January 12, 2025, according to recent reports.
AOD Transition Bug Affects Multiple Galaxy Watch Models
Users across a wide range of Samsung Galaxy Watch models – including the Galaxy Watch 8, Galaxy Watch 7, Galaxy Watch 6, Galaxy Watch 5, and Galaxy Watch 4 – are reporting the issue. The problem manifests when waking the watch, with the watch face getting stuck halfway through the transition from AOD to active mode. This results in elements from the AOD remaining visible on the active display, creating a “ghosting” effect and visual distortions.
Root Cause: Wear OS 6 Opacity Fade and Rendering Conflicts
The issue appears to be isolated to third-party watch faces, with stock watch faces remaining unaffected. According to sources, the problem stems from a new feature introduced in Wear OS 6: opacity fade for AOD transitions. This feature is designed to smoothly bring up or fade out the AOD mode of a watch face with an animation.
“If the animation doesn’t end before the screen suspends to save power, the rendering engine gets stuck, displaying both layers simultaneously,” one analyst noted. Essentially, the system is attempting to display both the AOD and active watch face layers at the same time, leading to the visual glitch.
Workarounds and Developer Solutions
For now, users experiencing the bug can temporarily mitigate the issue by switching to stock watch faces. Developers, meanwhile, have identified a potential workaround: adjusting the transition duration within the watch face’s XML code to zero (duration=”0″). This effectively disables the problematic animation.
Samsung Acknowledges Issue, Points to Wear OS 6
Samsung has reportedly acknowledged the bug, but has indicated that a resolution may be complex. “Samsung has hinted that it couldn’t do anything about the problem as it is a Wear OS 6 issue,” a source revealed. This suggests the company believes the core problem lies within the underlying operating system, potentially requiring collaboration with Google to implement a fix.
The situation highlights the challenges of software updates and the potential for unforeseen bugs to emerge with new features. While a fix is expected in January 2025, the ongoing issue serves as a reminder of the importance of thorough testing and collaboration between hardware manufacturers and operating system developers to ensure a seamless user experience.
