Why Your Pixel Watch “Always-On Display” (AOD) is Ghosting Third-Party Faces

Seeing double clock hands, faint leftover numbers, or shadowed complications lingering on your Pixel Watch’s Always-On Display (AOD) is alarming—especially when it looks like permanent screen burn-in. With third-party watch faces, however, this “ghosting” is far more often a software rendering or Wear OS ambient-layer bug than physical OLED damage.

Quick Answer

AOD ghosting on third-party Pixel Watch faces is usually a software frame-overlap bug rather than permanent OLED burn-in. Test by switching to a plain stock Google watch face and opening Settings: if the ghost image vanishes on menus, your screen hardware is fine. Update or replace the custom face, or toggle AOD off briefly.

What Is Actually Happening?

Your Pixel Watch uses an OLED display backed by a low-power co-processor that takes over whenever the watch enters Always-On Display (AOD) ambient mode. For AOD to look clean without burning battery or damaging pixels, every watch face must cleanly hide bright active-mode graphics, strip rapid animations, and hand off a stripped-down ambient frame to the co-processor.

Many third-party watch faces—especially older builds, faces converted from older companion apps, or custom designs overloaded with live complications—fail that handoff cleanly under newer Wear OS versions. Instead of swapping frames cleanly, two glitches occur:

  • Frame and layer overlap (software ghosting): The active watch face layer fails to clear out when entering ambient mode (or vice versa), leaving two sets of clock hands, stacked text, or faint widgets overlapping on screen.
  • Temporary OLED image retention: Bright white or high-contrast static third-party complications sitting unshifted in AOD can leave a faint temporary afterimage on OLED pixels for several seconds or minutes after waking before refreshing away.

How to Tell Software Ghosting From Real OLED Burn-In

Before worrying about warranty replacement, run this quick 30-second test to see whether the issue lives in software or hardware:

  1. Switch temporarily to a simple built-in Google watch face (avoid third-party faces or custom builders).
  2. Open Settings on your watch so a uniform dark-gray menu background fills the screen, or restart the watch and watch the dark startup screen.
  3. Look closely at the area where you saw ghosting:

What Can Cause Third-Party AOD Ghosting

  • Non-native Watch Face Format (WFF) code: Google shifted modern Wear OS versions toward the declarative Watch Face Format, which lets the co-processor render ambient mode safely. Legacy third-party faces or older companion-app faces that rely on outdated rendering code frequently drop frames or ghost layers on wake and sleep.
  • Broken or hanging complications: A single third-party weather, battery, or fitness complication stuck mid-refresh can hold an old graphic on the ambient buffer. See The “Third-Party Complication” Freeze: Why One App Can Brick Your Watch Face if the ghosted element also stops updating.
  • Static high-brightness elements without pixel shifting: Built-in faces subtly shift pixels over time and dim sharply in AOD; poorly designed third-party faces sometimes leave bright white borders or thick rings blazing at full contrast in ambient mode.
  • Mismatched system themes or animations: Dynamic color or Material 3 theme bugs can also create visual artifacts across watch face layers—covered in How to Fix “Material You” Theme Inconsistencies on Pixel Watch 4.

What to Do: Step-by-Step Fix

Step 1: Flush the Display Buffer

  1. Press and hold the watch face, switch to a clean stock Google face, and open Settings > Display.
  2. Toggle Always-on screen off, wait 10 seconds, and toggle it back on.
  3. Restart the watch via Settings > System > Restart so the display co-processor clears its ambient cache.

Step 2: Update or Trim the Third-Party Face

  1. Open the Google Play Store on your Pixel Watch, scroll to Manage apps, and install any updates for your third-party watch face and Google Play Services.
  2. Customize that third-party face and temporarily set its complication slots to Empty (or switch off optional ambient elements like AOD seconds, background glow, or step rings inside the face’s settings). Add complications back one by one to identify which widget causes the overlap.

Step 3: Switch to Watch Face Format (WFF) Faces or Disable AOD for That Face

If the ghosting returns only on one specific custom face even after updating and removing complications, the developer has not updated its ambient rendering code for current Wear OS rules. Either:

When It’s Actually a Hardware Problem

If the faint outline remains visible across Settings, solid-color menus, and a full restart—even after leaving Always-on screen switched off for several hours so temporary retention can clear—you are looking at physical OLED burn-in. Check your warranty coverage with Google Support, especially if the watch is still within its standard warranty window and burn-in interferes with reading menus.

Bottom Line

Do not panic if a third-party Pixel Watch face ghosts in Always-On Display—test a stock face and the Settings menu first to confirm your OLED screen is fine. Update the watch face, strip out problematic complications, and stick to native Watch Face Format designs (or disable AOD) if a third-party developer hasn’t patched ambient mode compatibility.