DANGER: Severe Burn-in on LCA44B

[Koopa777]

I don't know exactly what happened, but I think burn-in protection is NOT working on LCA44B. Since yesterday I've had Instaweather faces burn into my watch, and the Red face, which I've used intermittently for 9 months, has now burned into my screen in less than 12 hours of use. Screen brightness is less than 1, something is seriously messed up in the latest firmware. Anyone else experiencing this?

Sent from my Nexus 5 using Tapatalk

 

[Koopa777]

Display is shifting, turns out LG is absolutely stupid, so know that THE RED WATCH FACE WILL BURN IN TO YOUR SCREEN. They added massive grey circles to the date and month icons, which burn in. Every tick mark now burns in as well. I have never experienced any issues with burn in over the 10 months I've owned it, and now it's been burned in twice in 2 days. Something is amiss with the latest update, so definitely monitor your watch for signs of burn in.

Sent from my Nexus 5 using Tapatalk

 

[bogdi1988]

I've been experiencing burn in even with the previous update

 

[x10man]

I've experienced burn with all my watch faces on this update, and have had issues with burn in ever since flashing the custom kernel to gain WiFI, with the issues persisting even after the burn in was fixed. Sometimes however I do notice the face moving as expected, so I am not sure what is causing the problem overall. If anybody has any ideas as to solutions to this, I'm sure a fair few people would be glad to hear them, as it isn't much fun seeing the hour icons when you're say in the settings menu.

Thanks,
x10man

 

[Quad_Plex]

I highly doubt this has something to do with the latest update.

1. I've had the red face burn into my watch before lollipop was on my watch even, just because the hour marks are too big to be properly shifted in ambient mode

2. I've observed my current watch face (FORM) and it seems to shift just normally

 

[sierratango88]

Do you guys happen to have Developer Options enabled? I tried enabling it today and just noticed that the option Force Burn-in Protection was disabled by default.

I don't know whether it was because of that option, the newest update, or just the fact that reading over this thread made me inspect my watch more carefully, but I now notice some burn in on my watch for the first time. It is quite apparent when the notification shade is pulled down.

My watch face also has very thin graphics and I even put a black transparent overlay on my watch face to make it even darker in ambient mode.

Edit: seems the burn-ins are only a temporary (at least for me). Left the screen off for a while and its good again.

 

[x10man]

I have developer options enabled, and enabling force protection disables again after a reboot. Burn ins are temporary for me too, but I'd still rather they didn't have them at all. I don't just experience burn in on the analogue faces such as red, I currently have a "9" burn onto my watch from 25 minutes of the "together" face and watches with very thin lines such as F04 for Round Wear also burn in, after very short periods of time. It is easy to get these to go again, however I'd prefer the burn in protection to work properly. I never had these issues on 5.0, they've only started since 5.1 for me, although I am not sure if that was 5.1 overall, or 5.1 after the custom kernel flash.

Thanks,
X10man

 

[ro_explorer]

Forcing the burnin protection has no effect if you did not messed up the default burn-in protection files. The face will still shift no matter how the switch is being set.
If you will force the burnin protection settings file to not shift, then this switch will override that.

I have no burnin at all and I have the watch for almost a year now.

 

[timon12]

I don't have any problems with burn-in after update (or before). And I'm using Odyssey watchface red + disabled minimal ambient mode so according to everything I read here I should have huge burn-in. I have this watch over 6 months, 0 problems

this is how it looks also in ambient mode ( i have red color)

 

[x10man]

I don't have any problems with burn-in after update (or before). And I'm using Odyssey watchface red + disabled minimal ambient mode so according to everything I read here I should have huge burn-in. I have this watch over 6 months, 0 problems

this is how it looks also in ambient mode ( i have red color)

Are you rooted etc? I'm wondering if any of the non-stock portions of my watch are causing this. I have TWRP installed, and my bootloader unlocked. It doesn't seem to make sense that some people have it and some do not, on the same watch faces et cetera. I'm not rooted, and have the stock ROM and kernel installed.

Thanks,
X10man

EDIT: I have reflashed an entirely stock system, performed a factory reset and locked my bootloader, and I can verify my watch face is now moving. I will update further in regards to whether burn in is still an issue, or if this was a fix for me

 

[bogdi1988]

I'm full stock, never rooted or anything and I have some burn in

 

[timon12]

Are you rooted etc? I'm wondering if any of the non-stock portions of my watch are causing this. I have TWRP installed, and my bootloader unlocked. It doesn't seem to make sense that some people have it and some do not, on the same watch faces et cetera. I'm not rooted, and have the stock ROM and kernel installed.

Thanks,
X10man

EDIT: I have reflashed an entirely stock system, performed a factory reset and locked my bootloader, and I can verify my watch face is now moving. I will update further in regards to whether burn in is still an issue, or if this was a fix for me

Now I'm on stock rom, kernel and recovery, with unlocked bootloader, not rooted. I had Leedroid rom but voice recognition wasn't working that good like on stock (dunno why). Before Leedroid I was on stock without any modifications so IMO software does not affect this burn-in thing. also I'm using 6 brightness all the time + screen always on

 

[ro_explorer]

I'm using 6 brightness all the time

This is the perfect recipe for a nice burn-in. Of course it all depends on the colours used and the thickness of the lines involved ... but in general, max brightness on an OLED display means burn-in and shorter life.

// sent from my phone //

 

[timon12]

again, no burn in after many months I'm still using 6 brightness + screen always on.

 

[gabrymr]

again, no burn in after many months I'm still using 6 brightness + screen always on.

No burn in here either, had the same face for over 4 months at 3+ brightness and always screen on.