Notices


Reply
Thread Tools
Community Council | Posts: 4,157 | Thanked: 10,034 times | Joined on May 2012 @ Southerrn Finland
#11
Thank you @pichlo, your explanation might be correct!

I am aware of the 1st fact you describe, I too played with watch LCD displays and batteries when I was a kid and remember that the number segments only blackened for a moment when DC voltage was applied over the electrodes.

However I never came across the 2nd phenomenon that you describe, that there was permanent change in the display when the charge was left on longer. That indeed seems to be what's happening here.
 

The Following 4 Users Say Thank You to juiceme For This Useful Post:
coderus's Avatar
Posts: 6,070 | Thanked: 11,250 times | Joined on Nov 2011 @ Open Mobile Platform, Innopolis, Russia
#12
Originally Posted by juiceme View Post
Any idea what's the root cause and physical phenomenon that this is based on?

From the description I understand that it is nothing like "burn-in" of old CRT's or plasma tubes which results from the same intensity of light being constantly exited off the luminence material which leads to physical wearing-out of the said material.

Also same kind of phenomenon might be possible on OLED displays where bright pixels are worn out, maybe via electomigration of the materials? However this also happens only when the same image is burned to the display for a long time...

But LCD's are a different thing, the colour change in pixels is achieved via polarization change of the material, and in these descriptions the image did not "burn-in" when the same image was shown for a long time but somehow instantly when the device rebooted spontaniously?
And is it so that the image was visible also when the device was turned off?
for me it looks like video memory/framebuffer corruprion
__________________
Twitter | Openrepos | GitHub | PayPal.Me
 

The Following 3 Users Say Thank You to coderus For This Useful Post:
Community Council | Posts: 4,157 | Thanked: 10,034 times | Joined on May 2012 @ Southerrn Finland
#13
Originally Posted by coderus View Post
for me it looks like video memory/framebuffer corruprion
Might look so, but then it would be cleared when the device is switched to POWER-OFF, hmm?
 

The Following 2 Users Say Thank You to juiceme For This Useful Post:
coderus's Avatar
Posts: 6,070 | Thanked: 11,250 times | Joined on Nov 2011 @ Open Mobile Platform, Innopolis, Russia
#14
Originally Posted by juiceme View Post
Might look so, but then it would be cleared when the device is switched to POWER-OFF, hmm?
well, probably, but mobile devices are powered always and who knows maybe video ram is also powered somehow while switched off
__________________
Twitter | Openrepos | GitHub | PayPal.Me
 

The Following 2 Users Say Thank You to coderus For This Useful Post:
velox's Avatar
Posts: 291 | Thanked: 939 times | Joined on Dec 2009
#15
Originally Posted by coderus View Post
well, probably, but mobile devices are powered always and who knows maybe video ram is also powered somehow while switched off
That's the thought I had when I tried to drain the power as much as possible perhaps I just wasn't able to do drain it enough.

Quick update:
I've noticed the device is now freezing more often than before. Thrice in the last 24 hours, mostly when idling with display on, showing display glitches. But this could be random, as well. After rebooting swiftly, there are no new visible artifacts.
__________________
slumber: sensors enabled sleep timer for SFOS (translations/input/ appreciated if you've got some spare time)
talefish: directory based audiobook player for SFOS
___
list of i486/noarch packages on openrepos (jolla tablet)
 

The Following User Says Thank You to velox For This Useful Post:
Reply

Tags
burn in, lcd damage

Thread Tools

 
Forum Jump


All times are GMT. The time now is 05:42.