Google has recently begun rolling out a significant update for Wear OS 6, introducing a host of visual changes and new features aimed at enhancing user experience. However, some users are encountering a perplexing bug specifically related to watch faces, which complicates the transition between the Always-On Display (AOD) and the home screen on their smartwatches.
Wear OS 6 Smartwatches Facing a Weird Watch Face Bug
Reports from users indicate that this issue predominantly arises when they wake their devices through touch or movement. During the transition from AOD to the home screen, while the primary display does engage, the AOD layer fails to fade out as expected. This malfunction results in an unsettling ghosting effect on the screen, where various elements, such as numbers, icons, or hands, can be seen overlapping one another.
The initial complaints about this glitch have primarily surfaced from users of the Samsung Galaxy Watch, although similar incidents have been reported across other Wear OS 6-powered devices. While the underlying cause of this issue is still unclear, many users attribute it to the new fade animation introduced with the update. This animation is designed to create a smoother transition by gradually fading the always-on display in and out.
The New Animation Seemingly the Key Reason
The newly implemented fade animation appears to be somewhat unrefined at this stage. In some instances, the animation concludes before the screen powers down, which can lead to software freezing mid-transition. When this freezing occurs, both the AOD layer and the home screen may overlap, exacerbating the ghosting effect. Users have expressed their frustration over the frequency of this problem, finding it disruptive to their experience.
Interestingly, it’s important to note that this bug only seems to impact third-party watch faces; stock options currently do not exhibit any known issues. Samsung has acknowledged the problem, indicating that it arises from the latest Wear OS 6 update. Meanwhile, Google has yet to respond officially to these claims. Given that the primary cause of the bug seems to be identified, many users are hopeful for a prompt patch in the near future.
For more insights and user experiences, you can refer to the original report here.
Image Credit: www.androidheadlines.com
