The Google Pixel Watch has been out right around a week at this point, having launched last Thursday, October 13. And we’re still learning about the Pixel Watch. Like OLED burn-in. We’ve seen a few people on Reddit talking about it, and now we’re seeing it from YouTuber M. Brandon Lee, who posted on Twitter overnight about it.
Looks like my Google Pixel Watch is suffering from burn in after using it for about a week now.
Look at where the heart rate complication is and how it shows up in the pill of the app list.
Bummer. #teampixel #giftfromgoogle @GooglePixel_US pic.twitter.com/PtDPzYnnHI
— M. Brandon Lee | THIS IS TECH TODAY (@thisistechtoday) October 20, 2022
You can clearly see the time as well as the circles from the complications on the apps screen. That’s not good, considering the watch is just barely a week old at this point.
Now, he does mention in his Twitter thread that he has had AOD on. Which is likely attributing to this issue. But it shouldn’t be that noticeable after seven days. That’s no good.
On our model, which we’ve been using for about two weeks now, we are not seeing burn-in. However, I have only used AOD for one day (to test out the battery and see if it makes a difference). So that’s likely why I’m not seeing it on my unit.
Turning off AOD would likely fix this issue
As some have voiced on Twitter, turning off AOD should fix this issue within a few days. As Wear OS does like to keep the watch face in the background for always-on display. So it might not be true burn-in, and just a part of the operating system. Some have said they have seen the same thing on the Galaxy Watch 4 and 5 with AOD turned on.
So, moral of the story here is that if this “burn-in” is happening to you, and you want it to stop, turn off AOD. It’s a good reason to turn it off, along with the increased battery life. The tilt-to-wake function works really well, and uses less battery. That’s the option I’ve been using. So that’s probably the best way to go here.
The Google Pixel Watch has been out right around a week at this point, having launched last Thursday, October 13. And we’re still learning about the Pixel Watch. Like OLED burn-in. We’ve seen a few people on Reddit talking about it, and now we’re seeing it from YouTuber M. Brandon Lee, who posted on Twitter overnight about it.
Looks like my Google Pixel Watch is suffering from burn in after using it for about a week now.
Look at where the heart rate complication is and how it shows up in the pill of the app list.
Bummer. #teampixel #giftfromgoogle @GooglePixel_US pic.twitter.com/PtDPzYnnHI
— M. Brandon Lee | THIS IS TECH TODAY (@thisistechtoday) October 20, 2022
You can clearly see the time as well as the circles from the complications on the apps screen. That’s not good, considering the watch is just barely a week old at this point.
Now, he does mention in his Twitter thread that he has had AOD on. Which is likely attributing to this issue. But it shouldn’t be that noticeable after seven days. That’s no good.
On our model, which we’ve been using for about two weeks now, we are not seeing burn-in. However, I have only used AOD for one day (to test out the battery and see if it makes a difference). So that’s likely why I’m not seeing it on my unit.
Turning off AOD would likely fix this issue
As some have voiced on Twitter, turning off AOD should fix this issue within a few days. As Wear OS does like to keep the watch face in the background for always-on display. So it might not be true burn-in, and just a part of the operating system. Some have said they have seen the same thing on the Galaxy Watch 4 and 5 with AOD turned on.
So, moral of the story here is that if this “burn-in” is happening to you, and you want it to stop, turn off AOD. It’s a good reason to turn it off, along with the increased battery life. The tilt-to-wake function works really well, and uses less battery. That’s the option I’ve been using. So that’s probably the best way to go here.