Wear OS 6 “Overlapping UI” Bug: Fixing Ghosting Watch Face Elements (Material 3 Glitches)

Seeing old clock digits, blurred complication icons, or leftover Material 3 cards sitting faintly behind your live watch face on Wear OS 6 is jarring—and it is easy to confuse with a permanently damaged screen. In many cases, this overlapping UI glitch is a software compositor bug caused by Wear OS 6’s updated Always-On Display (AOD) layer or an outdated third-party watch face failing to clear old frames properly.

Quick Answer

Overlapping or ghosting UI elements on Wear OS 6 usually happen when the Always-On Display layer or a third-party watch face fails to clear old frames under Material 3 rendering rules. First test a solid gray screen to rule out OLED burn-in, then switch to a built-in stock watch face, toggle Always-On Display off and on, and reboot your watch.

Software Glitch vs. Hardware Burn-In: How to Tell in 10 Seconds

Before troubleshooting Material 3 software layers, make sure you are dealing with a software bug and not permanent OLED panel burn-in.

  1. Swipe down from the top of your watch and open Settings (or open a Flashlight or solid-color screen app).
  2. Look closely at the solid gray or white background—or take a screenshot using your phone’s companion watch app and look at the saved image on your phone screen.
  • It’s a Software Overlapping UI Bug if: The ghosted watch face elements vanish completely inside Settings, OR you can clearly see the overlapping graphics inside a digital screenshot on your phone.
  • It’s OLED Image Retention or Burn-In if: The faint clock outline stays visible on every single menu and solid background on the watch, yet does not appear in a screenshot.

For a deeper diagnostic breakdown between panel wear and display bugs, see Wear OS 6 “Screen Ghosting”: Is it Hardware Burn-in or a Software Bug?.

What Is Actually Happening?

Wear OS 6 brings stricter Material 3 Expressive rendering and updated Watch Face Format rules that separate how your screen draws ambient (Always-On Display) frames versus active wake frames.

When the system wakes up from AOD—or slides between a notification card, a tile, and the home face—the display compositor is supposed to wipe the ambient layer clean before drawing the colorful active watch face on top. If a legacy third-party watch face, a misbehaving complication widget, or a transition animation stalls mid-handoff, both frames render on screen at once, leaving semi-transparent “ghost” numbers or overlapping Material 3 pills stuck behind your live layout.

What Can Cause Overlapping Watch Face Elements

  • Outdated third-party watch faces: Faces built for older Wear OS versions that have not been updated for Wear OS 6’s rendering pipeline frequently glitch when transitioning out of AOD—a widespread symptom covered in Why Your Pixel Watch “Always-On Display” (AOD) is Ghosting Third-Party Faces.
  • Broken or stale complications: A single weather, calendar, or third-party fitness complication can freeze its rendering thread and cause overlapping layers on the watch face.
  • Transition animation race conditions: Rapidly raising your wrist while dismissing a notification or scrolling tiles can trap Material 3 transition frames halfway off-screen.
  • Custom Developer Options speed tweaks: Changing animation scales to 0.5x or 0x in Developer Options often breaks Wear OS 6 layer timing and creates overlapping UI cards.

What to Do: Fixing the Overlapping UI Bug

Work through these quick fixes from simplest to deepest until your watch face clears cleanly.

1. Switch to a Built-In Stock Watch Face

Long-press your current watch face, swipe to choose one of the default Google Pixel or Samsung stock faces that came preinstalled on your watch, and use it for a few minutes. Switching to a native Watch Face Format face immediately resets the watch’s rendering surface and proves whether your third-party face is the culprit.

2. Toggle Always-On Display (AOD) and Reboot

  1. Open Settings > Display on your watch and toggle Always-on screen / Always On Display Off.
  2. Hold the power/crown button (or swipe Quick Settings > Power) and Restart your watch to flush the graphics buffer.
  3. Once booted, turn Always-On Display back On and check if the ghost layer stays gone.

3. Strip Down Watch Face Complications

If the overlap only happens on one favorite watch face, edit that face and temporarily set all complication slots to Empty / None. Add your complications back one at a time over a couple of hours. If adding a specific weather, fitness, or battery widget brings the ghosting right back, leave that integration off and check The “Third-Party Complication” Freeze: Why One App Can Brick Your Watch Face.

4. Update Watch Apps in the Watch Play Store

Many Material 3 overlapping glitches are patched inside watch face companion packages and Wear OS system apps rather than full OS updates:

  1. Open the Google Play Store directly on your watch (not just your phone).
  2. Scroll down to Manage apps and tap Update all so Wear OS system services and third-party watch faces pull their latest Wear OS 6 compatibility patches.

5. Reset Animation Scales (If You Enabled Developer Options)

If you previously sped up animations in Developer Options, open Settings > Developer options on the watch and return Window animation scale, Transition animation scale, and Animator duration scale back to 1x. For stubborn stuttering or frame-layer overlaps during swipes, check Wear OS 6: Troubleshooting the “Race Condition” in Transition Animations.

What to Check If It Keeps Happening

If overlapping frames keep returning even on clean stock watch faces after updating all apps—or come paired with repeated System UI popups—clear the cache or update the watch companion app on your phone (Pixel Watch app or Galaxy Wearable app). On Samsung watches experiencing repeated screen freezes alongside UI overlaps, follow “System UI Has Stopped”: Troubleshooting Persistent Crashes on Galaxy Watch 7/8.

If a persistent ghost outline never disappears on any menu and does not show up in screenshots, avoid leaving static high-brightness watch faces running nonstop on Always-On Display, and contact the manufacturer for warranty screen evaluation if true OLED burn-in developed early.

Bottom Line

Wear OS 6 overlapping UI elements look like screen damage, yet most cases are harmless Material 3 rendering glitches triggered by older third-party watch faces, stuck AOD layers, or broken complications. Verify it on a solid gray menu first, then switch to a native stock watch face, toggle Always-On Display off through a reboot, and update all apps directly from your watch’s Play Store.