I got my phone two days ago, but I've noticed this from the very beginning. Completely stock with latest OTA (Sprint). I've been collecting screenshots and taking notes to try to find a pattern and to better understand the problem. Check out the 100% screen-shots below. I've added some arrows. Notice that once you see artifacts on a letter, the same artifacts appear on every occurrence of that letter (of the same size/font/etc). For instance, the lowercase letter "r" appears three times in big, white, heading font and all exhibit the exact same artifacts. The "r" in the grey subtext and the "r" in heading ("Wireless") do not. Both "F" characters in the "OFF" button look identical as welll (forgot to put some arrows here).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The problem seems random and affect random letters at random times. The fact that the screenshot sees it means that it is not a problem with the screen. It is actually in the screen buffer. It seems like a font rendering issue, since the artifacts are identical on all occurrences of the character.
Changing fonts doesn't fix it. Changing text size doesn't fix it. I can interact with the screen, and the artifacts remain. But if I change screens (select an option, open/close an app, etc.) then the artifacts change. By change, I mean it may go away but other artifacts may show up. It is not super common, but if I navigate around the options menu (because it has a lot of text), I will probably see it within 15-30 seconds. Some are so minor, that I don't easily notice.
Has anyone else seen these before?!
The attached zip file contains a few more untouched (except for hiding personal info in one) screenshots. I have a lot more screenshots if anyone is interested.
I get them too. Only noticed it in the system menu though.
kronium said:
I get them too. Only noticed it in the system menu though.
Click to expand...
Click to collapse
I rarely see it outside of the system menu, but it might be because there's a lot less text. But it does happen. The second screenshot above showed that it could happen in the homescreen (the alarm widget) and here's one in the "Reddit is Fun" app. All the letter "o" characters in the title bar are messed-up:
Solution??
Did you guys find a solution for this? Have you guys contacted Samsung?
universem2 said:
Did you guys find a solution for this? Have you guys contacted Samsung?
Click to expand...
Click to collapse
Does this mean that you have the same issue too? From the lack of replies to this thread, it seems not many people do or they aren't OCD enough to care. Anyhow, I'm exchanging my phone for another reason (two dead sub pixels and several random reboots) so it will be interesting to see if the new phone behaves the same way.
Well it seems I have this issue as well but what concerns me the most is if this is a hardware defect. If I can flash a drastically different ROM from the stock one and the corrupted fonts do not appear then it is most likely a software issue however at this point I think it is a hardware issue.
Nothing else is wrong with my phone so I would hate to give it back just for this reason and then get a phone that has dead pixels or a screen filled with those black dots people here are tacking about..
Here's mine
Sent from my SPH-L710 using Tapatalk 2
Hayabusa... Your font corruption is on a whole 'nother level!! Could you describe what happened? Is this a regular occurrence?
jacksparr0w said:
Well it seems I have this issue as well but what concerns me the most is if this is a hardware defect. If I can flash a drastically different ROM from the stock one and the corrupted fonts do not appear then it is most likely a software issue however at this point I think it is a hardware issue.
Nothing else is wrong with my phone so I would hate to give it back just for this reason and then get a phone that has dead pixels or a screen filled with those black dots people here are tacking about..
Click to expand...
Click to collapse
Good (?) thing mine has dead pixels and other issues, so I have no problem exchanging mine. If the new one does it too, then it is definitely more wide-spread.
Haha luckily I remember what to click on
It was the first time I seen it lol
Sent from my SPH-L710 using Tapatalk 2
I sincerely doubt this is a hardware issue. Have you guys tried changing from the default font? (settings, display, font style) I haven't noticed anything like this, but I switched to helvetica s on the first day of random customizing, just because I remember reading someone who liked it. Seems nice enough, but I don't have much basis to judge fonts.
bohiti said:
I sincerely doubt this is a hardware issue. Have you guys tried changing from the default font? (settings, display, font style) I haven't noticed anything like this, but I switched to helvetica s on the first day of random customizing, just because I remember reading someone who liked it. Seems nice enough, but I don't have much basis to judge fonts.
Click to expand...
Click to collapse
From my OP above:
ken830 said:
Changing fonts doesn't fix it. Changing text size doesn't fix it.
Click to expand...
Click to collapse
After seeing this issue, I switched to Helvetica and have been using that since.
I have started using the Helvetica font style as well now and I have not noticed the artifact/corruption at all yet however If I do I will be sure to post it in this thread.
Edit: issue still exists but not as prevalent. I noticed it in settings and on the word today in calender. :banghead:
jacksparr0w said:
I have started using the Helvetica font style as well now and I have not noticed the artifact/corruption at all yet however If I do I will be sure to post it in this thread.
Edit: issue still exists but not as prevalent. I noticed it in settings and on the word today in calender. :banghead:
Click to expand...
Click to collapse
I've tried messing with fonts and sizes myself from the very beginning and it did not help. In fact, changing the font was what caused me to look carefully at the text on the screen and that's when I first started to notice the problem.
I've noticed that it comes and goes in waves... Once it happens, it happens a lot and is more severe. Then, it kinda stops, or is so subtle that it's not noticeable.
Here's a bunch more with various fonts and sizes.
I wish there was a way that we could solve this issue without having to take the phone back... I am so surprised that not many users are reporting this issue, maybe they are not noticing it on there galaxy s3.
Here's an update from me. I received my replacement phone last night and have set it up the same way as my first phone. Same apps, same everything. I used it all night last night, and all day today. So far, so good. No font corruption at all. I got the LG2 update this morning, so I have tried both LF9 and LF2 on the new phone. It's still a little too early to call, but I think this phone won't exhibit the font corruption. Just wanted to let you guys know in case you are near the end of your return period and have a chance to get a replacement phone.
On another note, the old phone had two dead subpixels. One red, one green. The new phone has a single dead blue subpixel. Blue is better, and one is better than two. I think I'll just settle. But boy, Samsung AMOLED screens just kinda suck. They feel like big power hogs and they aren't anywhere near bright enough outdoors.
EDIT: Just updated the old phone to LG2 as well and played with it for just a few minutes before I started to notice the messed-up fonts again.
It's been a couple of weeks and my new replacement phone has not shown any font corruption at all. jacksparr0w: You may want to see if T-Mobile can replace yours. Sprint did it, but I used the dead pixels as the reason for my replacement.
T-mobile here and nothing of that sort. My guess would be corrupt font packages.
-Sent from my T999 / T-Mobile Galaxy SIII
Related
For a while I was doing this almost every call. Now it happens about 50% of the time.
Am I the only one who accidentally disconnects calls with my chin pressing the "End Call" button?
Is there a fix or am I just not used to this phone....?
(I realize that I am opening myself up to some serious smart ass comments)....
Thanks
Clean off the sensor top left of the screen. It automatically turns off the screen when you have the phone at your face. There is also a setting somewhere to control this. Check that it is on.
atwnsw said:
For a while I was doing this almost every call. Now it happens about 50% of the time.
Am I the only one who accidentally disconnects calls with my chin pressing the "End Call" button?
Is there a fix or am I just not used to this phone....?
(I realize that I am opening myself up to some serious smart ass comments)....
Thanks
Click to expand...
Click to collapse
It happens to me all the time, I've cleaned the sensor many times and it doesn't help. I think its just a design flaw from them putting it behind the mesh for the speaker, this is also why you can't see the led unless your looking straight at the phone. Luckily I don't make a lot of calls because this device wasn't designed to be a phone, it seems like that was just a feature that was tacked on in the last minute because of the horrible proximity sensor, bad call clarity/speakers and mic
Download myLock utilities (free at the market) and enable 'In Call Screen Lock'. It wont solve the prox issue, which seems to be a software flaw, but it will prevent accidental screen touches. Also, make sure the 'back button' option is checked, since the phone does not have a camera or nav key.
Sent from my StarTAC
atwnsw said:
For a while I was doing this almost every call. Now it happens about 50% of the time.
Am I the only one who accidentally disconnects calls with my chin pressing the "End Call" button?
Is there a fix or am I just not used to this phone....?
(I realize that I am opening myself up to some serious smart ass comments)....
Thanks
Click to expand...
Click to collapse
Try Settings->Call Settings->Always Use Proximity.
Sometimes orientation can overrule proximity if that's off so holding it between your cheek and shoulder allows the screen to turn on.
I've found that after I connect the call that pressing the power button to turn off the screen prevents all of these issues
Sent from my ADR6400L using Tapatalk
Absolute_Zero said:
Try Settings->Call Settings->Always Use Proximity.
Sometimes orientation can overrule proximity if that's off so holding it between your cheek and shoulder allows the screen to turn on.
Click to expand...
Click to collapse
I went to Menu=>Settings=>Call=> and don't see anything that lists "Always Use Proximity".
Can you please walk me through this again? I must be missing a step.
Please note that I am rooted and using Das Bamf 1.8 Remix which might be the problem for not having this option available....
superchilpil said:
I've found that after I connect the call that pressing the power button to turn off the screen prevents all of these issues
Click to expand...
Click to collapse
The only problem with that is that it comes back on as soon as the sensor no longer senses your face (unless it doesn't senses it when you shut it off or anytime thereafter)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Kinda OT but damn I hate it when I accidentally call somebody and the screen keeps turning on and off and I can't freaking end call!! i especially hate it when it's to somebody random. arg... just wanted to get that out there... Small price to pay for a touch phone i guess.
atwnsw said:
I went to Menu=>Settings=>Call=> and don't see anything that lists "Always Use Proximity".
Can you please walk me through this again? I must be missing a step.
Please note that I am rooted and using Das Bamf 1.8 Remix which might be the problem for not having this option available....
Click to expand...
Click to collapse
Yea, sorry...that may have been introduced in GB or just aosp based. I've been on it too long to remember.
PhillyCheez said:
Kinda OT but damn I hate it when I accidentally call somebody and the screen keeps turning on and off and I can't freaking end call!! i especially hate it when it's to somebody random. arg... just wanted to get that out there... Small price to pay for a touch phone i guess.
Click to expand...
Click to collapse
Most touch phones don't have this problem, at least none of the 3 I had other than the tbolt. I think this is because of the horrible proximity sensor placement, they shouldn't have put mesh over it.
eraursls1984 said:
Most touch phones don't have this problem, at least none of the 3 I had other than the tbolt. I think this is because of the horrible proximity sensor placement, they shouldn't have put mesh over it.
Click to expand...
Click to collapse
Ah. Yeah... Happened on my dinc quiet a bit. Maybe an HTC thing?
eraursls1984 said:
I think this is because of the horrible proximity sensor placement, they shouldn't have put mesh over it.
Click to expand...
Click to collapse
Putting a mesh over it is a very bad idea. I suppose that why they didn't do that. The sensor is under the glass, at the very top, in the "check mark" part of the Verizon logo. Dust can get in through the small crack at the top of the screen, and cause problems - a shot of air will clean it out.
mike.s said:
Putting a mesh over it is a very bad idea. I suppose that why they didn't do that. The sensor is under the glass, at the very top, in the "check mark" part of the Verizon logo. Dust can get in through the small crack at the top of the screen, and cause problems - a shot of air will clean it out.
Click to expand...
Click to collapse
Your right, I guess its not a bad design, just poor build quality/parts.
PhillyCheez said:
Ah. Yeah... Happened on my dinc quiet a bit. Maybe an HTC thing?
Click to expand...
Click to collapse
Maybe its the crappy sensor they use, out of two Motorola and two blackberry phones none had this problem (not all were mine, but I use my wife's phone a good bit) this is my first HTC phone and the longer I have the more its looks like it will be the last also
Ok heres my problem.
I have an unlocked atrix running on redpill and this morning i noticed that i have a "dead line" across my screen. About 1 inch down on my screen there is about a centimeter space where the touch does not register. So I downloaded a touch test and it sometimes does not register at all and sometimes it registers even when I'm not touching it.
I also checked and the screen is flat across (no dents/cracks etc...).
Do you think that this is a hardware or a software problem?
And any ideas how to fix it?
Thanks!
Try flashing the pds image. There's a thread about that in General.
I cant find that post i've been looking for an hour and a half, can you help me with a link?
sorry...
Also will reflashing my rom help?
Ah, you asked nicely..
http://forum.xda-developers.com/showthread.php?t=1131649
Try flashing another rom, you never know. Doubt it though..
We have the same problem I think. I missed this thread and started a new one.
After installing Faux's 2.0 enhanced kernal on my CM7, I now have a dead region of my touchscreen which is a little above the middle of the screen, 1/4 inch all the way across (horizontally). I verified this by using the touch test app from the market.
It is also very obvious as scrolling is extremely laggy.
I have already tried wiping my phone with fastboot, performing the PDS fix, and then wiping again in recovery and reinstalling CM7.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can see the dead space, very frustrating.
I have even tried flashing back to 1.83 using fruitcakes, then downloading the official moto gingerbread update so I am as close to stock as can be other than being unlocked and still no go.
Is this a hardware failure (that others are having too apparently?)
fsturbo15 said:
I have even tried flashing back to 1.83 using fruitcakes, then downloading the official moto gingerbread update so I am as close to stock as can be other than being unlocked and still no go.
Is this a hardware failure (that others are having too apparently?)
Click to expand...
Click to collapse
although the OTA update is essentially the same thing, i would say your last glimpse of hope is using rsd lite to flash a gingerbread sbf. (2.3.4 sbf file, just to clarify)
and if that doesn't work, at least your phone will be in a completely stock state to go in for a warranty replacement?
Just flashed it, i'll check back in later
Sent from my MB860 using XDA App
Well I just felt like a fool.
I did absoloutely nothing from yesterday (when I went back to 100% stock, reset phone) to today.
At 1:30, I did the same test with Touch Test and got the same dead zone. By the time I got to ATT for a warranty exchange, the screen worked flawlessly. Other than turning on airplane mode and having an extremely low battery @ 5% I did nothing in that hour.
I'd rather have the problem come back at this point and get a new phone than it work fine until my warranty ends and i'm stuck with a dud.
My dead spot is a little higher... but same thing.
Can you think of anything that happened to the phone that would damage it like this. My wife plays coin dozer (there is a lot of tapping) and the dead spot is around that area.
And wow that's bad luck. Mine was going on and off (more dead then alive). Did yours die again or is it back to normal?
I just want to figure out if this is a software or a hardware problem.
On another note i just flashed redpill v4 and it hasent happened yet... maybe. I can only hope...
Well, my phone fixing it self was only temporary.
After going home and doing nothing to my phone other than charging it, the dead zone is back.
This is a hardware issue for sure, the digitizers seem to be failing after some time.
Get a replacement.
thanks.
more money into this phone...
fsturbo15 said:
Well, my phone fixing it self was only temporary.
After going home and doing nothing to my phone other than charging it, the dead zone is back.
This is a hardware issue for sure, the digitizers seem to be failing after some time.
Get a replacement.
Click to expand...
Click to collapse
But what about orange's fix?
http://www.motorola.com/staticfiles...4.4.20_Orange_GB_Upgrade_Release_Notes_GB.htm
"Screen Touch Sensitivity | Fixed touch-screen ghosting and phantom touch events."
Your digitizer connector is cracked.
prove it by pushing on the top left above the glass and use touch test and watch the difference. You need a new digitizer it cost $60 and about 30min to an hour of work.
What's the difference should be? One time touchscreen wasn't reacting but only one time. But how could it prove digitiser problem?
Sent from my MB860 using XDA App
gekster said:
What's the difference should be? One time touchscreen wasn't reacting but only one time. But how could it prove digitiser problem?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
because that's where the digitizer connector is, and pushing on the screen there will cause it to move.
when mine cracked, it caused it to double the effected area when I was to push there.
also, I had made a typo in my previous post.
it's the top left, not top right; i apologize.
Milenko2121 said:
because that's where the digitizer connector is, and pushing on the screen there will cause it to move.
when mine cracked, it caused it to double the effected area when I was to push there.
also, I had made a typo in my previous post.
it's the top left, not top right; i apologize.
Click to expand...
Click to collapse
I have from 2 to 5 ghost fingers, which a) moving horizontally toward the edges of dead zone, b) located motionless at the edges of the dead zone. What behaviour of screen should be if I press that point on the healthy phone?
Is it what I need to replace?
http://www.ebay.com/itm/Original-NE...aultDomain_0&hash=item19cb8661c6#ht_756wt_906
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My screen is flickering!!
these saples shows how my sm850f has problem with content of screen, this problem dosnt affect the screenshot, and more distingushable in low light
TEST!
please reup your screenshots (only see your thumbnails).
I have exactly the same problem
AT&T Galaxy Alpha Screen Flickering
MOMO1265 said:
My screen is flickering!!
these saples shows how my sm850f has problem with content of screen, this problem dosnt affect the screenshot, and more distingushable in low light
TEST!
Click to expand...
Click to collapse
I have the same problem. I assume it might be a hardware issue, as long as only the lower third of the screen is affected. My screen only starts flickering when on low brightness only (<20%). Also, if I set the brightness the lowest possible setting, the RGB color balance seems to be distorted and shifted to the green (the screen seems 'greenish').
I've had this phone for over a year. The problem manifested a couple months ago, maybe in Oct-Nov 2015 and has been pretty stable since then.
Same problem. Just up your brightness a bit.
shevtsof said:
I have the same problem. I assume it might be a hardware issue, as long as only the lower third of the screen is affected. My screen only starts flickering when on low brightness only (<20%). Also, if I set the brightness the lowest possible setting, the RGB color balance seems to be distorted and shifted to the green (the screen seems 'greenish').
I've had this phone for over a year. The problem manifested a couple months ago, maybe in Oct-Nov 2015 and has been pretty stable since then.
Click to expand...
Click to collapse
How did you solve this problem?
AceyWAR said:
Same problem. Just up your brightness a bit.
Click to expand...
Click to collapse
but continue in dark
Rojikaft said:
please reup your screenshots (only see your thumbnails).
Click to expand...
Click to collapse
fixed
it become worse...
now I have 3 part in my screen that have 3 different light when the screen in AUTO mode in dark or when it's in low set of light...
is the any help?
I experienced the exact same problem, Samsung replaced the screen under warranty in their 24 hour repair service about a week ago. Haven't experienced any problems since repair.
Has anyone figuered out a solution for this problem without replacing the screen?
Is there any help??
Did you tried factory reset?
Neither of doing a factory reset nor reinstalling original frimware helped...it just stops for sometime when i set to manual mode and then set it to the highest level then return it to the lowest level
gtrs36 said:
Did you tried factory reset?
Click to expand...
Click to collapse
no help
even safe mode
Markus263 said:
Neither of doing a factory reset nor reinstalling original frimware helped...it just stops for sometime when i set to manual mode and then set it to the highest level then return it to the lowest level
Click to expand...
Click to collapse
you think it is a hardware problem? if not who can help us??
@MOMO1265 yes it's probably a hardware problem because i used to have epsilROM when i encountered this problem for the first time and i reinstalled the official firmware and it didn't help and i've sent an email to samsung and they couldn't help me all they said is that it's probably because of the custom rom i used to have all they will tell you to do is to replace the screen and it's probably your fault not their ****ty materials fault...maybe if there's an international email to samsung we can send our complaint to,maybe they will be more helpful
Samsung does nothing about it
I have the same problem so sent it back under Samsung warranty and they did nothing. They claimed to have repaired it but the problem is still occurring. Anyone have a fix? Anything would help. Thanks
Possible solution...
I had the same problem, seems like enabling soft-key back light solves the issue. I installed Screen Filter app and now, if I set the filtering to 50% from the app an brightness to 2 on Auto, no flickering happens. The app also helps if you want a dimmer screen than the standard minimum brightness setting can give you.
I hope it helps.
Replaced the screen ...still happening!!
A couple of months ago before my warranty got expired i went to samsung and they changed my screen. intially the problem disappeared but it came back recently and i don't know what to do.
Hello.
Today i noticed that my main screen has a burn in.
I used AMOLED Burn in fix and i can see the message bar from whatsapp and also the bottom screen buttons etc.
Anyone else had this problems?
Considering the v10 uses LCD, not OLED or AMOLED....no
Sent from my LG-H901 using Tapatalk
But why can I see whatsapp text entry bar thing on the grey background. And also the home/back buttons etc
LCD does not burn in. I don't know what you could be seeing, but it seems very highly unlikely.
Sent from my LG-H901 using XDA Free mobile app
aniqpirzada said:
Hello.
Today i noticed that my main screen has a burn in.
I used AMOLED Burn in fix and i can see the message bar from whatsapp and also the bottom screen buttons etc.
Anyone else had this problems?
Click to expand...
Click to collapse
i have the same issue. i dont know what to do. it has some kind of image retention issue. after that i also noticed a lot of deas pixels.
davidcastyalexandra said:
i have the same issue. i dont know what to do. it has some kind of image retention issue. after that i also noticed a lot of deas pixels.
Click to expand...
Click to collapse
mines seemed to fix itself
aniqpirzada said:
Hello.
Today i noticed that my main screen has a burn in.
I used AMOLED Burn in fix and i can see the message bar from whatsapp and also the bottom screen buttons etc.
Anyone else had this problems?
Click to expand...
Click to collapse
I've had this problem for a few days about 2 weeks ago, I could still see AT&T in the top corner. It did look like it was burned in but I knew it wasn't since it's LCD so I didn't worry about it too much. It randomly fixed itself. I wonder what caused it.
I have the same exact problem. And it heals itself but 5 mins of whatsapp use and there it is again. It is so annoying. I m thinking of returning it!
I would suggest to get rid of what's app. That seems to be the common cause for the majority here. Could be what's app is bad app to run on V10
If you dont call this a screen burn then what is it:
http://imgur.com/a/zQWIR
After 3hrs of wave navigation
Grey background to show effect
This won't be too helpful since I can't remember for sure what I was looking at when it happened but...
Earlier today I noticed that my keyboard was showing "in the background" of an app as though it was burned in.
It was definitely strange looking.
I think it was the weather channel app (which had no need for a keyboard popup) yet it almost looked like the app was transparent with the keyboard behind it.
It's definitely not doing it now but it was really weird looking!
Sent from my pretty nifty brand new LG V10
Guys please relax that's just image retention as far as LCDs are the topic. Unless if you stay at the same thing for like 5 hours (this [might] cause a permanent retention i guess).
the only thing that is prone to burn ins are OLED screens. And burn ins are permanent... because they are a burn.
LCDs only retain images because the crystals in their display tends to stay at the same position they are in after a long period of use but this doesn't actually produce damage and doesn't stay permanently. Once the display changes (either turned off or a different thing is displayed) they would eventually return to their normal state and work just fine.
Interesting. I wasn't really "unrelaxed" though... Just never saw it before so I figured I'd share my experience.
Sent from my pretty nifty brand new LG V10
I just noticed a burn-in, or some kind of image retention. I accidentally left my phone on all night while sleeping and the next morning there was a burn in on the top of the screen. It's only noticible when I pull down the notification bar because it's gray. I can only see it in the gray. The whole status bar is burned-in. It has been gradually dissipating. I also noticed a little bit of this when I used Waze for a long road trip a couple weeks ago, but it wasn't as severe of a burn in. At least it is disappearing slowly.
SuhasTheBest said:
I just noticed a burn-in, or some kind of image retention. I accidentally left my phone on all night while sleeping and the next morning there was a burn in on the top of the screen. It's only noticible when I pull down the notification bar because it's gray. I can only see it in the gray. The whole status bar is burned-in. It has been gradually dissipating. I also noticed a little bit of this when I used Waze for a long road trip a couple weeks ago, but it wasn't as severe of a burn in. At least it is disappearing slowly.
Click to expand...
Click to collapse
Same happened to me today. Slept through an amber alert that caused my screen to stay on. When i woke up my phone was off and hot to the touch. Switched batteries and noticed after powering on the amber alert was still faintly visible in the backgound. After about 10 minutes of screen use it gradually faded away.
LG V10 From TMobile Image Burn !
My LG V10 Its Haves A Problem When Im Waching Netflix At My V10 I Can See The V10 Google Search Bar Like In The Back Of The Screen Can This Be Fix ??? Help Please And At The Main Screen I Can See Like Logo Of Things Im Not Using ???
rvnlvrz said:
Guys please relax that's just image retention as far as LCDs are the topic. Unless if you stay at the same thing for like 5 hours (this [might] cause a permanent retention i guess).
the only thing that is prone to burn ins are OLED screens. And burn ins are permanent... because they are a burn.
LCDs only retain images because the crystals in their display tends to stay at the same position they are in after a long period of use but this doesn't actually produce damage and doesn't stay permanently. Once the display changes (either turned off or a different thing is displayed) they would eventually return to their normal state and work just fine.
Click to expand...
Click to collapse
Apparently officially termed "image persistence". Your post recreates a lot of the language from that article. Yeah, LCDs don't burn-in so this topic seemed rather odd to me. What could start showing up is the "dynamic contrast" done with LED backlights to LCDs burning-in; the fact that I've never heard any reports may mean it is uncommon, but I'm cringing at it happening in the future.
emdroidle said:
Apparently officially termed "image persistence". Your post recreates a lot of the language from that article. Yeah, LCDs don't burn-in so this topic seemed rather odd to me. What could start showing up is the "dynamic contrast" done with LED backlights to LCDs burning-in; the fact that I've never heard any reports may mean it is uncommon, but I'm cringing at it happening in the future.
Click to expand...
Click to collapse
Or image retention. It does go away though. Maybe a bad batch too? I drive from Ohio to Orlando, FL with Google maps on the entire time and bendy had a retention issue. All the ones with the issue also said the screen was hot. Corks that be a factor?
Sent from my LG-H901 using XDA Free mobile app
I have had my V10 since December (from T-Mobile). Initially no problems to report, but the image retention issue has become progressively worse (as I type this, the image of this site is being temporarily "burned in"). my father also got a V10 the same day, but does not report this issue. User activity may be leading to a faster declining lifespan of phone, but both phones have had a drastic increase in overheating since receiving the Marshmallow update, which may also be playing a role in the even greater amounts of image retention (a single game of candy crush leaves a residual image).
I'm 19, so like most millennials, I use my phone constantly which is possibly why I have this issue, but it is unfortunate to think there's a chance my phone is slowly dying from general use.
same issue with my v10 (bought a month back)
i think my culprit is Deer hunter 2016...as its the only game i play& only notice it more once i have played it.. i have also seen that if i keep my phone off during the night.. it usually goes away.. while if my phone is ON (standyby) during the night.. it stays. i didnt turned my phone off for the past 2 nights & the burn is pretty much there as you can see. my phone is an ATT v10 h900 on lollypop.. any suggestion will be appreciated.
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