https://drive.google.com/file/d/1UO84SCeykrD6Ecb9p3yWfoUe4KN2pJs2Eg/view
Above you can see detectable (under close scrutiny, ideal conditions) burn-in of my Nexus 6 screen after the following usage:
Only 8 weeks since I bought the phone
I'm reasonably sure that this was not present when I got the device because:
1 - it was "new" from Amazon in factory sealed box (although at a bargain price $299 for 64gb which makes me wonder slightly);
2 - inspected it pretty careully when I was reading about burn in shortly after I got my device;
My screen on time on a typical day is probably 2-5 hours per day over that 8 weeks. (although probably 5-6 hours per day during the very first week!)
Brightness is always in auto with the slider in the middle. And I don't spend a lot of time outside with my screen on.
You can see that's pretty mild usage for a relatively short time. And yet many others are reporting they absolutely can't detect anything whatsoever even after a year of use. . I'm led to believe I'm an outlier.
So what is it that might make me more susceptible than the next guy?
The "easy" answer is device quality. And it might be the right answer, but what if there's something else.
I thought about what it is in my usage (which seems relatively mild) that might possibly cause this.
Then I realized the one thing that struck me odd about this phone. I noticed the screen is warm to my fingers if I use it while charging. I didn't meausre that temperature, but I did download GSAM about a month in and and set a battery temperature alarm at 110F. If I do mild surfing while charging, battery temperature gets up to 110F within a few minutes. I don't let it go above that now, and the screen feels relatively cool compared to how hot I used to let it get. So I'm going to guess that my battery temperature used to routinely get to 115 or 120F while I was using my phone while charging. And although they're not equal, when battery gets hot screen gets hot (again I could feel the heat).
Would heat affect amoled deterioration? We wouldn't think that at first because we normally associate the deterioration with simply being energized brightly over time. But what about being energized causes that deterioration. What if it's the localized heat at the pixel from that brightly energized pixel that causes the damage. In that case, anything else which makes the phone/screen run hotter overall will tend to enhance that local damage mechanism also.
Does my phone run hotter than average? I'm not sure, but since day 1 I've been using this funky case Uniform Supcase Beetle Hybrid Pro.. It's built like an otterbox.... thick and rugged. Up to 1/4" inch thick and surrounds the phone on back, all sides, and even wraps around to cover the front bezel. Imagine that wrapping is an insulator (like a blanket), it helps to keep the heat inside so the phone underneath the blankets is hotter than it otherwise would be.
Is that case why I'm different? I dunno, all I've got is one phone as a data point and a scenario that seems plausible to me.
I'm interested to know if any others have associated elevated temperatures or a thick case with enhanced susceptibility to burn-in . Or if you believe it may be related.
By the way, I have to add my perspective this is a minor and managable thing. I still love this phone. I'm just curious about why...
There are of course many threads on subject of N6 burn-in. The biggest one here:
http://forum.xda-developers.com/nexus-6/general/burn-t2955765
electricpete1 said:
https://drive.google.com/file/d/1UO84SCeykrD6Ecb9p3yWfoUe4KN2pJs2Eg/view
Above you can see detectable (under close scrutiny, ideal conditions) burn-in of my Nexus 6 screen after the following usage:
Only 8 weeks since I bought the phone
I'm reasonably sure that this was not present when I got the device because:
1 - it was "new" from Amazon in factory sealed box (although at a bargain price $299 for 64gb which makes me wonder slightly);
2 - inspected it pretty careully when I was reading about burn in shortly after I got my device;
My screen on time on a typical day is probably 2-5 hours per day over that 8 weeks. (although probably 5-6 hours per day during the very first week!)
Brightness is always in auto with the slider in the middle. And I don't spend a lot of time outside with my screen on.
You can see that's pretty mild usage for a relatively short time. And yet many others are reporting they absolutely can't detect anything whatsoever even after a year of use. . I'm led to believe I'm an outlier.
So what is it that might make me more susceptible than the next guy?
The "easy" answer is device quality. And it might be the right answer, but what if there's something else.
I thought about what it is in my usage (which seems relatively mild) that might possibly cause this.
Then I realized the one thing that struck me odd about this phone. I noticed the screen is warm to my fingers if I use it while charging. I didn't meausre that temperature, but I did download GSAM about a month in and and set a battery temperature alarm at 110F. If I do mild surfing while charging, battery temperature gets up to 110F within a few minutes. I don't let it go above that now, and the screen feels relatively cool compared to how hot I used to let it get. So I'm going to guess that my battery temperature used to routinely get to 115 or 120F while I was using my phone while charging. And although they're not equal, when battery gets hot screen gets hot (again I could feel the heat).
Would heat affect amoled deterioration? We wouldn't think that at first because we normally associate the deterioration with simply being energized brightly over time. But what about being energized causes that deterioration. What if it's the localized heat at the pixel from that brightly energized pixel that causes the damage. In that case, anything else which makes the phone/screen run hotter overall will tend to enhance that local damage mechanism also.
Does my phone run hotter than average? I'm not sure, but since day 1 I've been using this funky case Uniform Supcase Beetle Hybrid Pro.. It's built like an otterbox.... thick and rugged. Up to 1/4" inch thick and surrounds the phone on back, all sides, and even wraps around to cover the front bezel. Imagine that wrapping is an insulator (like a blanket), it helps to keep the heat inside so the phone underneath the blankets is hotter than it otherwise would be.
Is that case why I'm different? I dunno, all I've got is one phone as a data point and a scenario that seems plausible to me.
I'm interested to know if any others have associated elevated temperatures or a thick case with enhanced susceptibility to burn-in . Or if you believe it may be related.
By the way, I have to add my perspective this is a minor and managable thing. I still love this phone. I'm just curious about why...
There are of course many threads on subject of N6 burn-in. The biggest one here:
http://forum.xda-developers.com/nexus-6/general/burn-t2955765
Click to expand...
Click to collapse
I can notice burn in on mine (I use no case at all) but its very mild and a "burn-in fixer" like the black and white rolling lines from "Display Tester" makes it go away if ever I'm that bored to do so. Also I only ever notice it on a grey background which honestly is rare to appear where the status and button bars are. On the terms of battery temp I really have to get something going to hit >105F for instance downloading videos using multiple streams to make it go faster which requires stitching the video back together at the end which basically pegs the cpu. General browsing reading some news stories etc stays ~85-90F. Differences in temps between phone for this one in particular can swing wildly due to there being upwards of 17 different CPU "bins" (compared to something like 3-4 on the Nexus 5) with each bin being a 10mV shift in the voltage table for the CPU meaning on CPU can have a 300mhz at 810mV (bin0) and another could have it at 650mV (bin16). For reference mine is a Bin 12 or 690mV on the 300mhz and 1110mV on 2.7ghz.
Both of my devices (had the old one for about 2 months, this guy for about 1) both show burn-in similar to yours already. First was caseless, this one I run with a case. I think that burn-in is just a very widespread issue with this panel and the people claiming to not have any simply don't notice it. Maybe I got 2 bad devices fresh from amazon but, I think that's just how it is. Good news is it really doesn't bother me and I can't see it without a gray background.
electricpete1 said:
https://drive.google.com/file/d/1UO84SCeykrD6Ecb9p3yWfoUe4KN2pJs2Eg/view
Above you can see detectable (under close scrutiny, ideal conditions) burn-in of my Nexus 6 screen after the following usage:
Only 8 weeks since I bought the phone
I'm reasonably sure that this was not present when I got the device because:
1 - it was "new" from Amazon in factory sealed box (although at a bargain price $299 for 64gb which makes me wonder slightly);
2 - inspected it pretty careully when I was reading about burn in shortly after I got my device;
My screen on time on a typical day is probably 2-5 hours per day over that 8 weeks. (although probably 5-6 hours per day during the very first week!)
Brightness is always in auto with the slider in the middle. And I don't spend a lot of time outside with my screen on.
Click to expand...
Click to collapse
That's an interesting theory.
I'm one of those who have absolutely NO detectable burn in, either permanent or latent. I also run a thick case -- Ballistic Maxx.... but... I have (used to, but don't any more) used it very hot. In particular google maps nav used to really make a lot of heat, enough that you could REALLY feel it on the screen, and even through the case. Somewhere along the lines, something changed enough in (firmware? OS? gmaps?) that this no longer gets it to heat up appreciably. Aside from that, I've *never* used it while charging -- kind of difficult to do so with wireless charging. Auto-brightness with the slider at about 1/3. I've owned it for a year now.
---------- Post added at 08:49 PM ---------- Previous post was at 08:39 PM ----------
StykerB said:
I can notice burn in on mine (I use no case at all) but its very mild and a "burn-in fixer" like the black and white rolling lines from "Display Tester" makes it go away if ever I'm that bored to do so. Also I only ever notice it on a grey background which honestly is rare to appear where the status and button bars are. On the terms of battery temp I really have to get something going to hit >105F for instance downloading videos using multiple streams to make it go faster which requires stitching the video back together at the end which basically pegs the cpu. General browsing reading some news stories etc stays ~85-90F. Differences in temps between phone for this one in particular can swing wildly due to there being upwards of 17 different CPU "bins" (compared to something like 3-4 on the Nexus 5) with each bin being a 10mV shift in the voltage table for the CPU meaning on CPU can have a 300mhz at 810mV (bin0) and another could have it at 650mV (bin16). For reference mine is a Bin 12 or 690mV on the 300mhz and 1110mV on 2.7ghz.
Click to expand...
Click to collapse
That operation *should not* be especially hard on the CPU. Its actually a fairly trivial task. Might be that your software is doing something stupid, like keeping all the different pieces separate until the end when it copies them all in sequence into a target file.
You might want to look into better downloader software. The *correct* way to perform this kind of a job, is to allocate the file in advance, and have each stream write to its correct offset in parallel. No final copy.
You might also save a heap of work if you get rid of userdata crypto. Big problem with the crypto on these when doing that kind of glue-job, is that it will be running decrypt on all the different pieces, and simultaneously running encrypt on the target file.
That operation *should not* be especially hard on the CPU. Its actually a fairly trivial task. Might be that your software is doing something stupid, like keeping all the different pieces separate until the end when it copies them all in sequence into a target file.
You might want to look into better downloader software. The *correct* way to perform this kind of a job, is to allocate the file in advance, and have each stream write to its correct offset in parallel. No final copy.
You might also save a heap of work if you get rid of userdata crypto. Big problem with the crypto on these when doing that kind of glue-job, is that it will be running decrypt on all the different pieces, and simultaneously running encrypt on the target file.
Click to expand...
Click to collapse
Well for 360p, 144p, and 720p which are the resolutions you can natively download from youtube as an MP4 do function this way (which if you download these resolutions the software just takes ~5 seconds to finalize the file after downloading). However since youtube is exactly keen on people downloading videos w/o Red (which I do have but I like having 1080p and/or 60fps for gaming style videos which Red does not allow for unfortunately). So those non-standard resolutions have to be downloaded in their little 4096 kb chunks with separate video and audio streams as if it were streaming it from the website itself and stitched together using an actual encoder. A 1080p60 video can put a sizable load ~50-100% i5 5200u laptop processor (depending on the complexity of the scene) while realtime streaming which arguably has more raw power than a N6 (part of the reason youtube still streams AVC codec to android). Now with the phone not having to actually render the video which VP9 codec isn't supported fully either device's GPU so a chunk of the load on the laptop would be rendering. The phone being able to finalize a 1080p60 30 minute video in ~1 minute is why the CPU is 100% while doing so and that just tells me it's using all the power it can to accomplish the task in parallel utilizing all 4 cores.
As for using encryption I've disabled it in the past with varied results (mostly kernel differences) but since I'm sticking with the stock rom and using the monthly ota's I've just left it on to stop any potential accidental encryption which could theoretically lead to data loss and/or the hassle of unecrypting again. In addition to this I see absolutely no gain in speed on the video stitching process which considering it performs the task at a ~15-20 MB/s rate where the limits of the encrypted storage are 200MB/s read and 90 write for sequential reading which is what the encoder is using. Since android 5.1 when the kernel was updated to take advantage of qualcomm's encryption instructions which would otherwise go unused to the OS anyway, encryption doesn't affect this type of workload.
I know this is kinda outside the scope of this thread but I have done some reading on this kinda stuff when I was trying to learn why the app needed an external app when downloading those difference resolutions which most apps wouldn't even do outside of PC software.
StykerB said:
Well for 360p, 144p, and 720p which are the resolutions you can natively download from youtube as an MP4 do function this way (which if you download these resolutions the software just takes ~5 seconds to finalize the file after downloading). However since youtube is exactly keen on people downloading videos w/o Red (which I do have but I like having 1080p and/or 60fps for gaming style videos which Red does not allow for unfortunately). So those non-standard resolutions have to be downloaded in their little 4096 kb chunks with separate video and audio streams as if it were streaming it from the website itself and stitched together using an actual encoder. A 1080p60 video can put a sizable load ~50-100% i5 5200u laptop processor (depending on the complexity of the scene) while realtime streaming which arguably has more raw power than a N6 (part of the reason youtube still streams AVC codec to android). Now with the phone not having to actually render the video which VP9 codec isn't supported fully either device's GPU so a chunk of the load on the laptop would be rendering. The phone being able to finalize a 1080p60 30 minute video in ~1 minute is why the CPU is 100% while doing so and that just tells me it's using all the power it can to accomplish the task in parallel utilizing all 4 cores.
As for using encryption I've disabled it in the past with varied results (mostly kernel differences) but since I'm sticking with the stock rom and using the monthly ota's I've just left it on to stop any potential accidental encryption which could theoretically lead to data loss and/or the hassle of unecrypting again. In addition to this I see absolutely no gain in speed on the video stitching process which considering it performs the task at a ~15-20 MB/s rate where the limits of the encrypted storage are 200MB/s read and 90 write for sequential reading which is what the encoder is using. Since android 5.1 when the kernel was updated to take advantage of qualcomm's encryption instructions which would otherwise go unused to the OS anyway, encryption doesn't affect this type of workload.
I know this is kinda outside the scope of this thread but I have done some reading on this kinda stuff when I was trying to learn why the app needed an external app when downloading those difference resolutions which most apps wouldn't even do outside of PC software.
Click to expand...
Click to collapse
I can't even bother to read that since (a) it is out of scope, (b) is from an end-user point of view, and (c) doesn't actually address anything related to what I've explained to you.
Every amoled screen I had was burned after some time. Mostly on the status bar. Once it was WhatsApp.
This time I want to prevent or delay it as long as possible. What recommendations do you have?
Never understood how people managed with burn ins. Well, stop watching a static picture with 100% brightness for 5hrs in a row is a good start.
i have owned more than a dozen samsung products with amoled screens, never had burn in on one of them. I always keep the screen very bright because my eyesight isnt that great. the one lg amoled phone i owned had terrible screen burn
The factors involved are: heat (ext), brightness (curr), uneven degradation rate of each color (rgb), persistent elements, and age (of panel). If half a screen is black and the other is blue, at max brightness, the blue subpixels are under the most stress. Their decay rate will overshadow the resting blue lights - plus that of green and red.
5yrs from now you're going to look at an all white image. Half of it will look awful.
Thanks guys, but not really helping, are you?
Fall asleep once with your phone under your face and you'll have a burn in your amoled screen. Probably many other ways.
This is a common issue that most people don't even notice.
I get how it happens. I'm looking for ways to prevent it.
Setting a screen timeout is helpful
Had every Samsung for years and never had this, so I've no idea.
Maybe some people don't have a screen timeout and fall asleep sometimes dunno
Sent from my SM-G975F using Tapatalk
Do i remember wrong, but didint Samsung add pixel shifting at least for their launcher elements which stay at same of screen all the time?
ivicask said:
Do i remember wrong, but didint Samsung add pixel shifting at least for their launcher elements which stay at same of screen all the time?
Click to expand...
Click to collapse
I don't remember that. I know they had it on their Plasma TVs. I thought the Pixel phones with OLED screens also had it but don't know about Samsung phones. I do think that 99.9% of people that use a phone normally will never experience burn-in for the time they own the phone.
Use full immersive mode to hide the status bar and the top and bottom. Turn off auto brightness because if you leave it on and go in sun the brightness get high.
Screen time out to 15 seconds
Leave the brightness slider 50 percent or less
If you use aod make sure to flip the phone so it turns off when not using it
Use youtube in full screen if you use it a lot
These are my tips as I've had my screen changed 4 times due to burn in on my note 8.now using these methods my screen so far has no burn in
For me it's always was the top status bar that would burn in
But now I should never experience burn in ever again now I've actively tried to avoid it
Everyone I know that swears blind they don't have burn and have never had that issue on any device I immediately grab there phone and look closely on a complety grey background and 100 percent of them have status bar burn in at the top at the very least
No way am I turning stuff off to avoid something I've never seen
900 quid to have to suffer immersive mode utter lols, if I have to did that I'll sell it
Sent from my SM-G975F using Tapatalk
I also honestly don't know what you're talking about. I've had s3, s5, s7, s9 and now to s10. Never had anything of the sort and since s7 I've been using AOD. Nothing happend. For the love of me I can't imagine how you may have had anything wrong with the display....
haircut123 said:
Use full immersive mode to hide the status bar and the top and bottom. Turn off auto brightness because if you leave it on and go in sun the brightness get high.
Screen time out to 15 seconds
Leave the brightness slider 50 percent or less
If you use aod make sure to flip the phone so it turns off when not using it
Use youtube in full screen if you use it a lot
These are my tips as I've had my screen changed 4 times due to burn in on my note 8.now using these methods my screen so far has no burn in
For me it's always was the top status bar that would burn in
But now I should never experience burn in ever again now I've actively tried to avoid it
Click to expand...
Click to collapse
Exactly, it's always the status bar. I think there is no immersive mode on s10+ yet, but I removed all the icons.
haircut123 said:
Everyone I know that swears blind they don't have burn and have never had that issue on any device I immediately grab there phone and look closely on a complety grey background and 100 percent of them have status bar burn in at the top at the very least
Click to expand...
Click to collapse
THANK YOU
I'm pretty sure many think they never had a burn in on their precious amoled screen, but they actually had.
Well they probably aren't looking for it that closely
Sent from my SM-G975F using Tapatalk
lumiden said:
Every amoled screen I had was burned after some time. Mostly on the status bar. Once it was WhatsApp.
This time I want to prevent or delay it as long as possible. What recommendations do you have?
Click to expand...
Click to collapse
Lol, sorry to see everyone busting you up on this....because you know, it's always more helpful to give someone a bad time to ensure a post count increment, than to be useful and offer up some insight.
Well, I have had screen burn in occur on 3 different galaxy phones. Not from falling asleep, not from being clueless...but from using my phone with games. 2 were mine and 1 on My wife's..hers occurred from youtube.
I used to play clash of clans tons, got burn in from the smaller stats numbers at the top- over time...But replaced the phone no sweat. Verizon insurance took the phone as a defect, noted as screen image ghosting, no charge. I just didn't realize that it was an issue playing, but it was over time. I think it was an s6. The reps in the store were as surprised as I was that it had occurred.
Different device & model, S7 , but same thing occurred, not in the same game either...This time with clash royale- the towers and little cloud icon burned in from too much playing and too often, apparently. I thought I had been a bit more careful, but i think it was the frequency in which I was playing versus overall time.
This time I simply contacted support in the chat about the ghosting, they replaced it again as a defect, no charge.
My wife's occurred on the s7, hers was the top bar because of YouTube, too much & too often. So, did the same for my wife's phone through Verizon insurance, they replaced as a screen ghosting defect.
After I noted what was going on, she made adjustments, didn't happen again to either of us.
Both of us are on the 10s now and very aware this can occur. So, you just need to make sure you're not on those static images or bars or icons for either long periods or frequent shorter periods...it takes time, but it happens, despite popular misconception.
It is only really noticable on a white background, like when looking at mostly blank new tab in chrome.
On the last device, the S7, I made sure to cut the amount of time spent on static images, especially the games. I still kept the brightness always max during the day, nights it was at the lowest setting.
And yes, I kept my settings the same after the replacement, just made adjustments to my gaming approach. I didn't want to baby the phone screen settings, shouldn't have to. No issues on that one after adjusting my approach.
So, it's certainly possible to avoid and I bet there's many out there that use certain apps for long periods and frequently just do not really notice it may have occurred, even if slightly.. and I'm taking heavy users.
A note app with a clean page or white blank background reveals it, most of the time you're not using that, so ignorance is bliss...and makes It's easier for folks to bust on someone else for asking about screen burn in because they themselves are simply clueless it even remotely occured with them.
Heavy user naysayers, check your old phones, just for the heck of it... and then keep the findings to yourself because no one actually cares about you being right or wrong.
Anyway, it was an inconvenient lesson at the time,for me but good to know and learn from. Didn't cost me much but time, as it just took up time set up the phones again.
I know Samsung isn't too concerned about it or they wouldn't have preinstalled games on the phone (ie. solataire).
Just do your best to adjust your screen settings, like those that mentioned, if you're into that. Or simply adjust your apps/usage habits.
Don't overlook the Digital Wellbeing settings on the S10...that may also help you target certain apps with a timer also. Might be something useful for you.
Hope that helps some.
Sent from my SM-G973U using Tapatalk
sainthooligan said:
Lol, sorry to see everyone busting you up on this....because you know, it's always more helpful to give someone a bad time to ensure a post count increment, than to be useful and offer up some insight.
Well, I have had screen burn in occur on 3 different galaxy phones. Not from falling asleep, not from being clueless...but from using my phone with games. 2 were mine and 1 on My wife's..hers occurred from youtube.
I used to play clash of clans tons, got burn in from the smaller stats numbers at the top- over time...But replaced the phone no sweat. Verizon insurance took the phone as a defect, noted as screen image ghosting, no charge. I just didn't realize that it was an issue playing, but it was over time. I think it was an s6. The reps in the store were as surprised as I was that it had occurred.
Different device & model, S7 , but same thing occurred, not in the same game either...This time with clash royale- the towers and little cloud icon burned in from too much playing and too often, apparently. I thought I had been a bit more careful, but i think it was the frequency in which I was playing versus overall time.
This time I simply contacted support in the chat about the ghosting, they replaced it again as a defect, no charge.
My wife's occurred on the s7, hers was the top bar because of YouTube, too much & too often. So, did the same for my wife's phone through Verizon insurance, they replaced as a screen ghosting defect.
After I noted what was going on, she made adjustments, didn't happen again to either of us.
Both of us are on the 10s now and very aware this can occur. So, you just need to make sure you're not on those static images or bars or icons for either long periods or frequent shorter periods...it takes time, but it happens, despite popular misconception.
It is only really noticable on a white background, like when looking at mostly blank new tab in chrome.
On the last device, the S7, I made sure to cut the amount of time spent on static images, especially the games. I still kept the brightness always max during the day, nights it was at the lowest setting.
And yes, I kept my settings the same after the replacement, just made adjustments to my gaming approach. I didn't want to baby the phone screen settings, shouldn't have to. No issues on that one after adjusting my approach.
So, it's certainly possible to avoid and I bet there's many out there that use certain apps for long periods and frequently just do not really notice it may have occurred, even if slightly.. and I'm taking heavy users.
A note app with a clean page or white blank background reveals it, most of the time you're not using that, so ignorance is bliss...and makes It's easier for folks to bust on someone else for asking about screen burn in because they themselves are simply clueless it even remotely occured with them.
Heavy user naysayers, check your old phones, just for the heck of it... and then keep the findings to yourself because no one actually cares about you being right or wrong.
Anyway, it was an inconvenient lesson at the time,for me but good to know and learn from. Didn't cost me much but time, as it just took up time set up the phones again.
I know Samsung isn't too concerned about it or they wouldn't have preinstalled games on the phone (ie. solataire).
Just do your best to adjust your screen settings, like those that mentioned, if you're into that. Or simply adjust your apps/usage habits.
Don't overlook the Digital Wellbeing settings on the S10...that may also help you target certain apps with a timer also. Might be something useful for you.
Hope that helps some.
Sent from my SM-G973U using Tapatalk
Click to expand...
Click to collapse
Thank you for your insight. I wouldn't be able to return it if it happens.
I'm also worry the AOD can cause burn in. I never used it before because I had a notification led...
I know it moves around, but is that enough? I also turn it off 8hs a day.
lumiden said:
Thank you for your insight. I wouldn't be able to return it if it happens.
I'm also worry the AOD can cause burn in. I never used it before because I had a notification led...
I know it moves around, but is that enough? I also turn it off 8hs a day.
Click to expand...
Click to collapse
You can set the schedule for the time for the AOD is active and either use the AOD auto brightness option or set the brightness lower, if that helps you feel more confident with it. The movement should help avoid issues.
FWIW, I used AOD with my previous phone without any issue and I anticipate the same with this one.
My burn in issue was only with the games & YouTube as noted.
Sent from my SM-G973U using Tapatalk
This is my main issue with AMOLED screens. They look nice but they wear out. The nature of Android means they will wear out unevenly which is why people see burn in. The wearing out of your screen is cumulative. Meaning that it isn't like an old CRT TV where it would take weeks of a static image to burn in but just showing the same image over time day in and day out. The only way to prevent it is to use the entire screen with moving images, like full screen movies, so that the panel wears evenly.
The status bar and navigation bar tend to be on the screen all the time those images will burn in first. Dark mode can also cause issues because if the area is dark it isn't being used and if it isn't being used it will look brighter than other areas that were used more frequently. The s10 has a full screen mode option for some apps. Some apps like Netflix will show the full screen movie even around the camera cutout and that is ideal. Youtube will also allow you to zoom in and show the video around the camera. cutout Chrome and the Samsung browser keep the status bar but it will change colors based on the site and if the bar is white it will invert the status icons which will help keep the panel wearing evenly. I have the dolphin browser which runs in full screen but the top portion of the panel is not used so that is less than ideal.
Auto brightness can be used but in the bright sun that panel is wearing much faster. The screen time out should be set to 15 seconds. These panels are designed to look great but not be super durable and in many cases that's what Samsung wants. They benefit when you have to buy a new device. It's sad to say but its business.
Greetings,
Just received a used device and noticed my unit won't physically lower in brightness at around 25 percent. What I mean is that at around the 25 percent mark, I am unable to perceive it getting any lower when set at a lower percentage. I've also noticed that when I have the brightness at a high percentage and then quickly lower it to the minimum, that the display will at first be quite dim then will suddenly raise itself to a slightly brighter minimum. I do not have auto brightness on, nor any filter apps active while testing. Just wondering if this issue is isolated to my device. Thank you for reading my concern. If anything is unclear, I could try taking a video of the issues. Anyone else with these issues? I've searched the web to no avail.
i just bought a used device as well and mine has the same issues. the backlight seems to flicker on the second screen at low brightness and below about half the second screen is noticably dimmer. its unfortunate that they didn't put a lot of effort into the screen software or quality considering its the main gimmick of this phone, but it is made by ZTE after all. the price you probably paid for one of these things is a lot more representative of the quality than the original MSRP. But its still a fun gimmick even with all the flaws.
stevegalaxius said:
i just bought a used device as well and mine has the same issues. the backlight seems to flicker on the second screen at low brightness and below about half the second screen is noticably dimmer. its unfortunate that they didn't put a lot of effort into the screen software or quality considering its the main gimmick of this phone, but it is made by ZTE after all. the price you probably paid for one of these things is a lot more representative of the quality than the original MSRP. But its still a fun gimmick even with all the flaws.
Click to expand...
Click to collapse
Thanks for your thoughts and input. Yeah this is quite unfortunate on how the phone turned out. I also see the flicker on the second display. But as you mentioned, the device is indeed quite fun. I'm actually thoroughly enjoying the device especially with books and comics reading in the extended mode. I tend to do some late night reading, so that was the reason why I brought up the display issue as I had wanted to get the display as dim as possible before applying a filter. Hopefully one day we'll get root to check out if we can lower the display minimum brightness level along with other lower level system modifications.
axxtran said:
Thanks for your thoughts and input. Yeah this is quite unfortunate on how the phone turned out. I also see the flicker on the second display. But as you mentioned, the device is indeed quite fun. I'm actually thoroughly enjoying the device especially with books and comics reading in the extended mode. I tend to do some late night reading, so that was the reason why I brought up the display issue as I had wanted to get the display as dim as possible before applying a filter. Hopefully one day we'll get root to check out if we can lower the display minimum brightness level along with other lower level system modifications.
Click to expand...
Click to collapse
apparently a few weeks ago someone released TWRP for this device. its not quite a root but it still gives you root access to change the build.prop and some low level system settings. TWRP is the sign that there is some kind of development happening but i wouldn't hedge your bets on anybody fixing the screen issues even with some kind of kernel modification
stevegalaxius said:
apparently a few weeks ago someone released TWRP for this device. its not quite a root but it still gives you root access to change the build.prop and some low level system settings. TWRP is the sign that there is some kind of development happening but i wouldn't hedge your bets on anybody fixing the screen issues even with some kind of kernel modification
Click to expand...
Click to collapse
That is definitely a most welcome update. I'm curious on what build your device is on since you mentioned having similar issues to mine. I am on b30 myself and will be flashing to b37 when I get a chance to see if there are any differences.
Hello,
Have been loving this phone since I got it early this year, around Feb, apart from the battery life.
Unfortunately, recently the display has been cooked (literally) after the phone was overheated while gaming. I'm not sure what happened exactly, but at low brightness settings there is now a very noticeable greenish gradient on the display, more intense closer to where the phone got hotter. There is also an odd black line down the centre of the screen that is only visible on certain parts of the lock screen (notification banners). There is also some noticeable graininess to the screen as well now. Seems fine when brightness is increased.
Has anyone else experienced an issue like this? Unfortunately I will probably be looking to replace the phone soon, as this has made it very frustrating to use in low-light, and I'm not sure whether the severity will increase over time. I doubt there is any fix other than replacing the display unit. Any overheating has probably shortened the already poor battery life as well, unfortunately.
I did try to get an image, but sadly the effects are not very obvious in a photograph.
Make sure you are on the latest firmware and that you are not using the 90Hz refresh rate, it is known to have weird colours/a green tint. Other than that, maybe it did in fact overheat and get damaged, but I think it is unlikely at the temperatures a phone can get to, so probably a defect screen. If you can get it checked by Asus they might replace it
Adaoh said:
Make sure you are on the latest firmware and that you are not using the 90Hz refresh rate, it is known to have weird colours/a green tint. Other than that, maybe it did in fact overheat and get damaged, but I think it is unlikely at the temperatures a phone can get to, so probably a defect screen. If you can get it checked by Asus they might replace it
Click to expand...
Click to collapse
I haven't had the issue prior to the overheating. Phone is always on 60Hz because the battery life is even worse otherwise, so definitely not that.
In fiddling around it looks like the issue only happens when DC dimming is enabled though. Sadly having it off makes the display look like an LCD for anything except pure black, where the pixels turn off.
Unfortunately I probably couldn't get it repaired by Asus (without a fee anyway), as I have the bootloader unlocked and root access, and the unlocker reports the serial # to Asus. I live in Australia and we haven't had right to repair enforced like America has.
I am on latest Android 12 firmware.