Related
No hoax here, i saw some vids about other phones having problems with their touch screen. So i decided to test em myself.
Get some software from the market or whatever that lets you see where the touch point is registered.
Divide the screen into four equal parts, by drawing an imaginary half-line on the two axis, and lets label them from the top left going clockwards, 1-4.
I put my finger on quadrant 1, and the other on quadrant 3.
Then, i moved quadrant 1 finger to quadrant 2
and the finger on quadrant 3 to quadrant 4.
And when i do that, the touch point becomes reversed, specifically, the touch points are registered left and right mirrored.
Anyone suffer those symtoms?
+ The phone can't register more than 2 points. Is that normal?
++ Just checked there is no other thread about this problem
Cheers
dongimin2 said:
No hoax here, i saw some vids about other phones having problems with their touch screen. So i decided to test em myself.
Get some software from the market or whatever that lets you see where the touch point is registered.
Divide the screen into four equal parts, by drawing an imaginary half-line on the two axis, and lets label them from the top left going clockwards, 1-4.
I put my finger on quadrant 1, and the other on quadrant 3.
Then, i moved quadrant 1 finger to quadrant 2
and the finger on quadrant 3 to quadrant 4.
And when i do that, the touch point becomes reversed, specifically, the touch points are registered left and right mirrored.
Anyone suffer those symtoms?
Click to expand...
Click to collapse
Yes: this problem is found in many smartphones, including the LG P500. Google for "axis inversion bug" if you wanna know more.
dongimin2 said:
+ The phone can't register more than 2 points. Is that normal?
Click to expand...
Click to collapse
It is normal. Cheaper multitouch screens don't support more than two fingers. Again, it's a limitation common to many other smartphones.
Thats why we cannot play Slice It.
I was wondering.. what if someone writes an app that runs in background, that intercepts the touches from the user and send the (reversed) input to the proper system "thingamabomb"?
I mean... this problem occours in a precise way (multitouch+slide): there has to be a way to fix it with some user-written software! come on dev community, surprise us!
Sent from my LG-P500 using XDA App
I've searched long and at any places, but nowhere was an answer. Everybody goes crazy if we talk about sensitivity, but what are the benefits of a higher sensitivity really?
I mean, here on mother earth, you can't get something better, without decreasing other features...
So if i turn the sensitivity higher (or lower), i mean if its more precise... Where are the disadvantages?
Higher battery drain?
Please help me to understand
I you slide you finger over the screen it takes a small distance before the phone reactes and moves the part of the display. Try it and you will notice this small distance on the homescreen. It is like a dead zone where you move your finger but nothing happens.
With the toch sensitivity fixes or apps or scripts you can decrease this distance to 0 or any other value. I think a value around 5 is quite common. I am not sure but I thought 15 is default, so you usually want to decrease it.
A disadvatage is, that if you set it too low, the phone might recognize klicks a swipes.
Schindler33 said:
A disadvatage is, that if you set it too low, the phone might recognize klicks a swipes.
Click to expand...
Click to collapse
That was the answer i wanted! Thank you!
On some older kernels, when your phone is on ac power, the screen becomes very unresponsive. That's why people came up with the need to change the touch sensitivity.
Sent from my GT-I9100 using Tapatalk
Hello, im about to get xperia mini pro , but want some users/owners opinions about the phone ,manly cause my last phone was a SEw380(headaches) ,this gonna be my first smartphone and im trying to avoid headaches , so i want a good choise .So here a few questions :
1) Reading this website i found that some(?) devices have cicada(electrostatic) noises . In other website i read that the new devices have new hardware and there was an upgrade to the software's phone, so the issue was solved? this noise could harm the phone?
2)Also read about the light sensor that some times go crazy , and the screen starts flickering .
3)The keys in the bottom of the phone , right and left(i think back and the other dont know) some times go crazy (?) .
Also i really appreciate if u could share ur opinions about the phone , adv and disadv and if have other problems . Thanks.
p/d : sry for my english
_Elixir said:
Hello, im about to get xperia mini pro , but want some users/owners opinions about the phone ,manly cause my last phone was a SEw380(headaches) ,this gonna be my first smartphone and im trying to avoid headaches , so i want a good choise .So here a few questions :
1) Reading this website i found that some(?) devices have cicada(electrostatic) noises . In other website i read that the new devices have new hardware and there was an upgrade to the software's phone, so the issue was solved? this noise could harm the phone?
2)Also read about the light sensor that some times go crazy , and the screen starts flickering .
3)The keys in the bottom of the phone , right and left(i think back and the other dont know) some times go crazy (?) .
Also i really appreciate if u could share ur opinions about the phone , adv and disadv and if have other problems . Thanks.
p/d : sry for my english
Click to expand...
Click to collapse
1.) new builds dont have this problem
2.) only n bad ligntning conditions when you put finger over sensor
3.) that issue was in xperia mini, not mini pro
> technically, no. noise is from hardware (to be precise, mic in keyboard) and the noise only appear if you're recording in an empty room or silent places
in crowd / festival / party / whatever the noise won't come
> sorry, didn't happen on my XMP
> in theory, no. but in practice I find it rather amusing too since my some part of my hand accidentally hit the sensor key if I don't use keyboard mode on landscape view :v
- - -
ps: sorry for my bad english
1. The electrostatic noise is there.. At least for me, the early adopter, not sure of new hardware revision sony might introduce w/o us knowing. But its really a faint clicks, only heard in very silent video which i doubt why you would want to rec a silent empty scene :-D.
2. The flicker issue that some might encounter maybe due to the sensor getting confused whether the scene is dark or bright. So it keeps flickering. Personally i never had experience with this issue.
3. The capacitive keys are fine, unless you're holding it in landscape mode without opening the keyboard, maybe your palm accidentally touch it.
4. PROS: A very nice piece of hardware. Great performance. Benchmark even surpass galaxy s on stock fw. Overclockable to 2GHz. Small screen? Not a problem, because you type with the hardware keyboard so all of the screen estate goes toward serving you visually unlike most touch screen phone the "onscreen" keyboard fils 3 quarter of the screen. So you see less of the text you're typing.
Cons: battery life is sometime frustrating, juice defender seems to make it better but it renders my whatsapp unusable because juice defender turn off the wifi/3g connection when screen is off. Wifi range is weak compared to my ipod touch. Maybe its an issue with all android phone because i've seen galaxy s suffers the same problem.
Sent from my SK17i using xda premium
Is anyone able to play with the Archos 80 9g?
I got the Turbo 1,5ghz version but im not able to play frontline commando or shadowgun because the touchscreen is.. how should i say.. maybe unresponsive?
it feels like the touchscreens resolutions itself is very low and you cant aim precisely. Using latest Archos ICS (4.06 atm)
cheers
*snip*
I have the same issue..maybe a anti reflex display protection might work? I know that they make a smooth and "soft" feeling!
Ncyde47 said:
Is anyone able to play with the Archos 80 9g?
I got the Turbo 1,5ghz version but im not able to play frontline commando or shadowgun because the touchscreen is.. how should i say.. maybe unresponsive?
it feels like the touchscreens resolutions itself is very low and you cant aim precisely. Using latest Archos ICS (4.06 atm)
cheers
Click to expand...
Click to collapse
I noticed the exact same thing.
I installed the following app from the Play store:
Input Benchmark (not allowed to post external links yet)
It's really simple and it has only three tests: Touch, Accelerometer, Multitouch.
Touch test shows the frequency of the touch events. My G9 shows only 50 to 52 touch events per second if you move your finger really fast. My phone (Samsung Galaxy Spica) shows 60 events per second.
Accelerometer shows around 130 events per second, and my phone shows around 100 events per second.
The multi-touch test shows the pixel positions of all touch points. My phone can detect sub-pixel changes. After you calculate the touch resolution it recognizes around 1024*1024 touch points on a 3.2 inch screen (480x320).
My Archos G9 80 Turbo shows only around 227*227 touch points. Usually the touch quantization works out to 3.37335 pixels vertical and 4.4978 pixels horizontal. This means that the touchscreen cannot resolve finer movements, and this is the reason why homescreen scrolling from left to right looks very choppy if you keep your finger on the screen, and much smoother if you fling (start the transition with rapid finger movement and take the finger off of the screen). Sometimes I got other pixel values that were about in between other the values I usually got. I think that this means that the touchscreen is at least capable of double the current precision (probably around 512*512 touch points), but it still lags behind my phone from 2009/2010.
In the teardown tread the touchscreen controller is identified as Cypress TMA 340. I found some Cypress presentations that classify this as a 3rd Generation touchscreen controller that is intended for screens with less than 5.1" diagonal, with a notice that 4 point multi-touch should be used on screens smaller than 4.6 inches.
I found that HTC Sensation (that had a lot of touchscreen issues) also uses a Cypress TMA 340 series 4-point multi-touch digitizer as a replacement digitizer (there are at least 4 different digitizers used on the Sensation production). On a international HTC Sensation I get around 1024*1024 touch points resolution @ 60 touch events per second, so the controller should be capable of at least that. It isn't ideal for our screen size but it would be a significant improvement over the current situation.
This means the issue could be either hardware (the capacitive matrix is low-res), or software (the driver is broken or poorly written). If the issue is hardware, we can't do anything about it (except to perhaps replace the digitizer with a better one, and add support for it in the kernel). If the issue is software, we maybe get some improvement later via improved or tweaked drivers (Cypress has released their drivers as open source)
Perhaps there is a trade off between 4-point multi-touch and 2-point multi-touch, and we could get better touch resolution if we allow only 2-point multi-touch.
neur0mans3r said:
...
My Archos G9 80 Turbo shows only around 227*227 touch points. Usually the touch quantization works out to 3.37335 pixels vertical and 4.4978 pixels horizontal. This means that the touchscreen cannot resolve finer movements...
Click to expand...
Click to collapse
This explains why when using a stylus and drawing a diagonal line I see an image that looks like a fine staircase rather than a smooth line.
So what can we do?
Does any1 know if Archos is aware of this fact?
Anyone willing to downgrade to honeycomb and test? Then we can know if its a kernel problem or a hardware problem
I made a basic test that displays the touch data provided by Android. For my G9 80 it shows a touchscreen resolution of 2048x2048, but in most cases the actual resolution is much lower.
When you move your finger horizontally or vertically, the difference between touch points on the main axis (the direction your finger is moving) is around 9 points (around 4.5 pixels horizontally and 3.37 pixels vertically). However, on the other axis you get much better results (all the way down to 1 touch point). The apparent touchscreen resolution depends on the angle between the motion of the finger and the horizontal and vertical axises of the digitizer.
To recap, in the most basic use case when moving your finger horizontally to navigate homescreen and app drawer, you get stuttering because the touch events are reported like that, not because the hardware is slow to render.
Since in games you usually move your fingers in the direction you need them to go this does not work as expected because the aiming jumps around too much.
I really hope this is a driver issue (some sort of poorly written averaging filter).
Shano56 said:
Anyone willing to downgrade to honeycomb and test? Then we can know if its a kernel problem or a hardware problem
Click to expand...
Click to collapse
I am on Honeycomb most of the time (my Gen9 doesn't like ICS)
Gen9 101 1GHz 512MB, using Input Benchmark:
Touch- 62-75 Hz
Accelerometer- 125-130 Hz
Multitouch- max x-y is correct (1280x800) but touch point move is registered
a)for "normal" speed- every 4-5 pixels for X and every 3-4 pixels for Y
b)for slow speed (press a finger to the touchscreen and tilt it slowly left/right)- readings are inaccurate- it registers 1 pix for X and 1 pix for Y but there is plenty of places where registered point "goes back" (eg- 630->tilt right->blinks between 627 and 631) and/or touch is not detected (this also flickers)
neur0mans3r said:
My phone (Samsung Galaxy Spica) shows 60 events per second.
Click to expand...
Click to collapse
I guess you use tom3q's CM7?
Were you by any chance using FrankenKenrel or FrozenLake previosuly?
gen_scheisskopf said:
I guess you use tom3q's CM7?
Were you by any chance using FrankenKenrel or FrozenLake previosuly?
Click to expand...
Click to collapse
Yes, tom3q's CM7 with the underclocked-overclocked-synced kernel (sound silly but is an accurate description) . I was mainly using Yonip kernels with FroYo.
I made a simple test app (attached in the above post) that shows the difference in the coordinates of touch events in pixels and touch points themselves. I tried it on a HTC Sensation and it's working OK with sub-pixel precision.
It looks like this behavior is not ICS specific, but Archos specific (maybe even G9 80 specific).
neur0mans3r said:
Yes, tom3q's CM7 with the underclocked-overclocked-synced kernel (sound silly but is an accurate description) .
Click to expand...
Click to collapse
I know what you mean, I did some pre-alpha tests for tom3q
neur0mans3r said:
I was mainly using Yonip kernels with FroYo.
Click to expand...
Click to collapse
Competition.....
FrankenKernel was for Ecalir btw
neur0mans3r said:
I made a simple test app (attached in the above post) that shows the difference in the coordinates of touch events in pixels and touch points themselves. I tried it on a HTC Sensation and it's working OK with sub-pixel precision.
It looks like this behavior is not ICS specific, but Archos specific (maybe even G9 80 specific).
Click to expand...
Click to collapse
Tested and
-"normal" speed 4-5 pixel precision for both X and Y
-slow speed- 4-5 pixel precision for the main movement axis and at the same time 1 pixel precision for the second axis
gen_scheisskopf said:
Tested and
-"normal" speed 4-5 pixel precision for both X and Y
-slow speed- 4-5 pixel precision for the main movement axis and at the same time 1 pixel precision for the second axis
Click to expand...
Click to collapse
I think the difference in touch points is more representative because we get an integer (4-5 pixels is 9-10 touch points).
Main question is can this be fixed (or atleast improved somewhat) with a driver update/fix, or is this a limitiation of the digitizer.
P.S. I skipped Eclair and went straight to criminal's CM 6.1.
neur0mans3r said:
I think the difference in touch points is more representative because we get an integer (4-5 pixels is 9-10 touch points).
Main question is can this be fixed (or atleast improved somewhat) with a driver update/fix, or is this a limitiation of the digitizer.
Click to expand...
Click to collapse
Main question- how outdated are drivers and touchscreen firmware (if present), and who wrote them (read: can we source newer/not broken/just better ones?)
neur0mans3r said:
P.S. I skipped Eclair and went straight to criminal's CM 6.1.
Click to expand...
Click to collapse
SM-Froyo by any chance?
gen_scheisskopf said:
Main question- how outdated are drivers and touchscreen firmware (if present), and who wrote them (read: can we source newer/not broken/just better ones?)
Click to expand...
Click to collapse
Look in the hardware hacking thread, it looks like we only need to set a smaller active distance value in the controller configuration. I think the default value (8) is used (maybe the active distance value is not even configured explicitly so it defaults to 8).
gen_scheisskopf said:
SM-Froyo by any chance?
Click to expand...
Click to collapse
I used Voku's CM Mod+X for quite some time also, but then the phone would freeze and/or crash when using 3G to surf while commuting. After I lost data due to a damaged /data ext2 partition, I switched to CM7.4. It's really stable for me (over 400h uptime today, battery lasts 3 days since I don't use the phone much).
neur0mans3r said:
Look in the hardware hacking thread, it looks like we only need to set a smaller active distance value in the controller configuration. I think the default value (8) is used (maybe the active distance value is not even configured explicitly so it defaults to 8).
Click to expand...
Click to collapse
I've seen your post. Unfortunately I don't have enough time to dig in sources now
neur0mans3r said:
I used Voku's CM Mod+X for quite some time also
Click to expand...
Click to collapse
...which is based on SpicagenMod
gen_scheisskopf, by any chance, have you tried new 4.0.7? What problems did your G9 have on ICS? I suggest you RMA that s***
Shano56 said:
gen_scheisskopf, by any chance, have you tried new 4.0.7?
Click to expand...
Click to collapse
Nope, last ICS I used was 4.0.6-test4
Shano56 said:
What problems did your G9 have on ICS?
Click to expand...
Click to collapse
-device gets hot quite fast and it's quite hot even when I use not very demanding apps (pdf readers mostly)
-connected with above- shorter battery life
-there are system freezes (reset required) even when using not very demanding apps
-there seems to be a problem with memory management- sometimes using "ram heavy" app (like Firefox or Aurora) shell restarts
Shano56 said:
I suggest you RMA that s***
Click to expand...
Click to collapse
I have to contact service anyway- charger died
Anyway before that I have to return to stock partition layout (and I need tablet right now, still 5 test to pass, all materials are in pdf and reading them on a PC is killing me)
Tell them your GPS doesn't work or something, they'll say its a hardware error and replace it
Shano56 said:
Tell them your GPS doesn't work or something, they'll say its a hardware error and replace it
Click to expand...
Click to collapse
I don't know what is required to replace the device (maybe I'll run an infinite benchamark loop on ICS with tablet wrapped in a blanket or something? )
gen_scheisskopf said:
I don't know what is required to replace the device (maybe I'll run an infinite benchamark loop on ICS with tablet wrapped in a blanket or something? )
Click to expand...
Click to collapse
my otg usb port/charger port stopped working like many others, i simply said the device no longer received a charge (wasn't sure if it was the chargers fault or the tablets fault) and they said to ship the tablet and shipped a replacement to me after they received.
Hello, recently i sent my phone to warranty because of serious screen burn in issues, they replaced my sceen, which had more light bleeding issues, but i wouldnt mind that, as the burn-ins were gone, but to my surprise, yesterday after about 3hrs of constant on screen texting in whatsapp, the burn-in started appearing on the new screen, i am seriously pissed off, i really like this phone overall with the features it offers and so on, but the quality control... Wtf LG.. I now have bought a phone which i should just send for warranty repairs after a period of time?
Just wanted to share my experience with you, i still have a gpad 8.3 thats is still rolling on the latest 7.1.1 and has no quality issues and a robust metal build whatsoever, but this is just annoying...
Im sorry to hear about your issues with g5. Its a great device, whats wrong with your screen? Light bleeding whad do this mean?
Gmobilize said:
...Just wanted to share my experience with you,..
Click to expand...
Click to collapse
If you want to do something for us, try to use the search engine first until you start a new thread!
There are a lot of threads around here which has described screen ghosting on LG devices!!!
See here:
1.) (English) ->https://forum.xda-developers.com/lg-g5/help/lg-g5-screen-ghosting-burn-problem-t3545769
2.) (German) ->http://www.android-hilfe.de/thema/displayflecken-nach-langem-aktiv-sein.790992/page-3
3.) (English) ->https://forum.xda-developers.com/lg-g5/how-to/panel-vs-panel-series-t3480270
4.) (English) ->https://forum.xda-developers.com/tmobile-lg-v10/help/ghost-images-screen-image-retention-t3395732
5.) (English) ->https://forum.xda-developers.com/g4/help/screen-ghosting-lg-g4-t3451879
YOU are not alone!
non-toxic said:
If you want to do something for us, try to use the search engine first until you start a new thread!
There are a lot of threads around here which has described screen ghosting on LG devices!!!
See here:
1.) (English) ->https://forum.xda-developers.com/lg-g5/help/lg-g5-screen-ghosting-burn-problem-t3545769
2.) (German) ->http://www.android-hilfe.de/thema/displayflecken-nach-langem-aktiv-sein.790992/page-3
3.) (English) ->https://forum.xda-developers.com/lg-g5/how-to/panel-vs-panel-series-t3480270
4.) (English) ->https://forum.xda-developers.com/tmobile-lg-v10/help/ghost-images-screen-image-retention-t3395732
5.) (English) ->https://forum.xda-developers.com/g4/help/screen-ghosting-lg-g4-t3451879
YOU are not alone!
Click to expand...
Click to collapse
Dont you think i am aware of this? How does it help me? I have wrote ot in threads before and i write it again, this one was about the same thing happening even after warranty repair, and the cause is a faulty panel, i am sharing my warranty experience, i dont really understand why would you post these links? How is this helpful?
i think it would be interesting for all of us to know the period when it started to happen for the first time and then when exactly after the replacement?
I for myself got the screen replaced about 2 month ago having the screen burn issue as well. Phone IME starts with 604. Since the replacement no issue for me so far..but i am not so sure if it the problem is solved with that and the screen burn in starts again after a while again......
Gmobilize said:
Dont you think i am aware of this? How does it help me? I have wrote ot in threads before and i write it again, this one was about the same thing happening even after warranty repair, and the cause is a faulty panel, i am sharing my warranty experience, i dont really understand why would you post these links? How is this helpful?
Click to expand...
Click to collapse
aking007 said:
i think it would be interesting for all of us to know the period when it started to happen for the first time and then when exactly after the replacement?
I for myself got the screen replaced about 2 month ago having the screen burn issue as well. Phone IME starts with 604. Since the replacement no issue for me so far..but i am not so sure if it the problem is solved with that and the screen burn in starts again after a while again......
Click to expand...
Click to collapse
Its indeed interesting as it really seems to not appear at the beginning, and once it shows up it starts to get more noticable over time, for example as i said, it occured after heavy using whats app for about 3hrs most of the time with auto brightness sometimes hitting the highest levels, right now i can notice the burn in, but its not at levels where it would become disturbing, ill see how it goes, if it progresses and so on..
Gmobilize said:
Dont you think i am aware of this?
Click to expand...
Click to collapse
No, it was not visible for me reading your post, that you have get all informations about LG display issue.
Gmobilize said:
i don't really understand why would you post these links
Click to expand...
Click to collapse
i want to be sure, that you can see, that this is no individual case!
Gmobilize said:
How is this helpful?
Click to expand...
Click to collapse
If you had read all of my linked threads, you should know...
...many people has this problem with different LG devices...
... it was recognized at LG G5 phones produced between march and jun. 2016 (see serial number starting with 604 up to 606)...
... there seems to be a new display without ghosting but with a little more power consumption recognized since serial number 609...
... it makes no difference witch country code your device was! all displays could be affected!
...that some users have installed "sFilter BlueLight" app to prevent this issue!
...as some users reports,it is not granted, that this issue never returns on changed displays because it seems to be a general fault...
Maybe that all this informations does not help to solve YOUR problem, but this is a forum for questions and answers ant i thought, that this informations could be helpful to know. But as it looks like,it seems that this will be for other users only!
So if you feel disturbed of me, feel free to set me to first position in top of your ignore list!
and at least: see my signature at 3.!
non-toxic said:
No, it was not visible for me reading your post, that you have get all informations about LG display issue.
i want to be sure, that you can see, that this is no individual case!
WITH
If you had read all of my linked threads, you should know...
...many people has this problem with different LG devices...
... it was recognized at LG G5 phones produced between march and Jjund 2016 (see serial number starting with 604 up to 606)...
... there seems to be a new display without ghosting but with a little more power consumption recognized since serial number 609...
... it makes no difference witch country code your device was! all displays could be affected!
...that some users have installed "sFilter BlueLight" app to prevent this issue!
Maybe that all this informations does not help to solve YOUR problem, but this is a forum for questions and answers ant i thought, that this informations could be helpful to know. Maybe only for other ons only!
So if you feel disturbed of me, feel free to set me to first position in top of your ignore list!
Click to expand...
Click to collapse
Sorry, but to me the reply seemed non-friendly, as it would be addressed to a rookie user, who hasnt done his research, maybe im wrong about your post...
But overall, yes i have seen all those threads, and unfortunatley, as i have mentioned in some other LCD display threads, the app could basically be a temp fix for the issue, when its not at a disturbing level, as its a cause of a faulty panel.
At this point where my panel has been already replaced, i cant really keep track of its model.
Gmobilize said:
Sorry, but to me the reply seemed non-friendly, as it would be addressed to a rookie user, who hasnt done his research, maybe im wrong about your post...
But overall, yes i have seen all those threads, and unfortunatley, as i have mentioned in some other LCD display threads, the app could basically be a temp fix for the issue, when its not at a disturbing level, as its a cause of a faulty panel.
At this point where my panel has been already replaced, i cant really keep track of its model.
Click to expand...
Click to collapse
Okay so lets go through this together.
A burn-in only happens with amoleds as this is permanent. We have LCD panels so we have image retention which is non-permanent.
A LCD is a liquid crystal display. Means you have a certain state of the crystals. When you apply a voltage the crystals rearrange themselves and block light. This is why we need a background illumination. Anyway once you use it for a longer period with a semi-static or a static picture (like whatsapp typing bar, google maps info boxes, keyboards etc) the crystals start to shift in their relaxed form towards another state. Blue light is due to its short wavelength energy consuming -> high voltage applied -> faster image retention.
That's why blue light filters do work to some extent. (With cf lumen and root you can adjust to use less blue instead of having an overlay draining additional energy)
This liquid crystal thingie is dependent on a lot of different parameters, that's why some get it faster and some slower. My 1,5k$ thinkpad has the same issue with the navigation bar being a persisting image after 10h+ of browsing.
TLR
So this is actually not a warranty issue. LG also returned phones unrepaired as this is the negative side of a lcd and considered standard behaviour. Go for an AMOLED the next time as they can't suffer from this, but once you have image burn-in you will never get rid of it. So doesn't really make a difference.
https://en.wikipedia.org/wiki/Image_persistence (helpful for that burn in issue which a lot of people seem to get wrong)
Cheers
lolmensch said:
Okay so lets go through this together.
A burn-in only happens with amoleds as this is permanent. We have LCD panels so we have image retention which is non-permanent.
A LCD is a liquid crystal display. Means you have a certain state of the crystals. When you apply a voltage the crystals rearrange themselves and block light. This is why we need a background illumination. Anyway once you use it for a longer period with a semi-static or a static picture (like whatsapp typing bar, google maps info boxes, keyboards etc) the crystals start to shift in their relaxed form towards another state. Blue light is due to its short wavelength energy consuming -> high voltage applied -> faster image retention.
That's why blue light filters do work to some extent. (With cf lumen and root you can adjust to use less blue instead of having an overlay draining additional energy)
This liquid crystal thingie is dependent on a lot of different parameters, that's why some get it faster and some slower. My 1,5k$ thinkpad has the same issue with the navigation bar being a persisting image after 10h+ of browsing.
TLR
So this is actually not a warranty issue. LG also returned phones unrepaired as this is the negative side of a lcd and considered standard behaviour. Go for an AMOLED the next time as they can't suffer from this, but once you have image burn-in you will never get rid of it. So doesn't really make a difference.
https://en.wikipedia.org/wiki/Image_persistence (helpful for that burn in issue which a lot of people seem to get wrong)
Cheers
Click to expand...
Click to collapse
Thanks for the interesting article on LCD artifacts, however, i wanted to say some things:
As my for my first panel, that got replaced, image retention was pretty hard, as when the phone got warmer, it became really disturbing and barely usable as the keyboard and status bar started to ghost on grey background apps such as xda, the only way was to let it cool down and wait till everything disappears, as soon as i started using my phone a bit longer, the problem resurfaced very quick. So it clearly wasnt a normal reaction. Just to add, no CF.lumen like apps were able to help back then.
My current replaced panel is showing only minor signs of this, it becomes more apparent on longer usage times with the same elements and the ghosting is barely visible with not so intense usage, so i hope that this wont eventually get stronger as before. As it would seem to be a natural usage reaction, i still consider this an issue however, cause none of my previous LCD phone had anything like it, not even my LG Gpad 8.3. So im gonna try to apply warranty again if needed, as repair services seem to be pretty helpful in my country at least, as long as they have spare panels in stock.
And about amoled, i think ill pass that for a while, i have seen enough samsung demo units in stores have serious homescreen burn-ins.
With LG G5 the quality really seems to be an issue, yes there maybe lucky people with good units and so, but overall it is pretty disappointing, as feature and hardware wise i really love this device.
lol
I see the so called expert stopped responding like a retard. I had the same problem I just lgup and flashed stock all over again about 4 times and it started to show improvements. As of now I got rid of the burnt images on my lcd