What it’s essential know
- A bug in Put on OS 6 is inflicting third-party watch faces to freeze mid-transition, making a “ghosting” impact the place the lively face and All the time-On Show overlap.
- Pixel Watch and Galaxy Watch customers are each affected, together with newer fashions just like the Galaxy Watch 8 and Watch Extremely.
- The difficulty particularly targets downloaded third-party faces; inventory faces pre-installed by Google and Samsung seem like immune.
Put on OS 6 was presupposed to be a quiet quality-of-life improve, resembling a extra polished always-on show expertise. As a substitute, it’s kicked off an sudden headache for Pixel Watch and Galaxy Watch homeowners who depend on third-party watch faces.
Customers have taken to each Google and Samsung boards to report that All the time-On Show (AOD) transitions are damaged on Put on OS 6 for a lot of third-party faces, as reported by PiunikaWeb. Beneath regular circumstances, a Put on OS watch shifts between its full, interactive watch face and a simplified AOD model easily when your wrist drops. On Put on OS 6, nevertheless, one thing in that handoff has gone sideways.
House owners report seeing a “ghosting” impact through which the lively watch face and the AOD model overlap. As a substitute of a easy fade from shiny to dim, you get a frozen, clear mess of overlapping numbers and fingers.
This isn’t restricted to at least one model. Studies are coming in from each Pixel Watch and Galaxy Watch homeowners, together with these operating the most recent Pixel Watch fashions and Samsung’s Galaxy Watch 8 and Watch Extremely. That’s necessary as a result of it suggests it is a Put on OS 6 platform-level drawback.
The basis of the issue seems to be a change in how Put on OS 6 handles AOD rendering for third-party watch faces. Google launched new APIs meant to enhance effectivity and consistency, however these modifications appear to have damaged compatibility with current watch face frameworks.
Inventory faces nonetheless work advantageous
The system will get caught midway, leaving a damaged, half-finished display screen. This bug principally impacts third-party watch faces. If you happen to use the watch faces that got here along with your gadget, you in all probability haven’t seen this drawback as a result of these faces work otherwise.
Some customers have briefly fastened the difficulty by switching to an official Pixel or Samsung watch face, however that’s extra of a workaround than an answer.
This isn’t the customization you anticipated, however it’s higher than a messy display screen each time you test your steps. Google and Samsung appear to pay attention to the issue, however since it’s a system subject, we now have to attend for an replace to repair it.
Till the replace arrives, keep away from third-party watch faces and look ahead to the subsequent firmware replace.
