Related
edit: *Burn in may not be noticeable at the early stages unless you examine the screen, I used "Screen Test" app from market, please download this or something equivalent, and examine your screen closely before you vote."
So this may not apply to those who just purchased their phone, but for those of you who got your phone around launch time, examine your phone for burn in. Use "Screen Test" from the market, and go through each color, looking for burn in. Oh this is a new addition, I noticed my burn in his worse when the screen is set to the lowest brightness setting. So repeat the test after you dim your screen.
I've had my phone over 2 months, downloaded "screen test" and guess what. The AM/PM up in the notification bar has burned in!
When you download "Screen Test" app, you will notice two things about your screen. Do not be alarmed, the following is normal.
1) Very thin green vertical line along left side of screen
2)Thin gray-shady horizontal bar on top, this is not the notification bar burning in.
What is not normal....BURN IN!
Can't believe the AM/PM is burnt in after 2 months. Shame.
Samsung has to update this by having the time hop around the notification bar instead of staying stationary.
Maybe a dev can work on this?
Got mine on launch day. No burn in.
Sent from my SGH-T959 using XDA App
Squirrelmaster22 said:
Got mine on launch day. No burn in.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Did you examine the screen using "Screen Test" or an equivalent app?
got mine on launch and my PM is burned in =/
Screen test, from the market as you suggested.
Sent from my SGH-T959 using XDA App
speedysilwady said:
got mine on launch and my PM is burned in =/
Click to expand...
Click to collapse
They really need to change the time and AM/PM stamp from being stationary, they need to make it hop around the notification bar, or something. This is horrible, 2 months and AM/PM is burning in!
I'm sure the signal bars, wifi, and other stuff in notification bar will start to burn in next.
I'm also worried about the battery full message that stays on all night, that will start to burn the screen too.
No burn in here. Got my phone the third week of August.
i always thought leds burned cooler so the idea of burn in never even occured to me on this phone or any other phone for that matter...i doubt a warranty calim would fix it because i think all these vibrants will eventually have burn in...it wouldnt be easy i think to have an animated notification bar, but CM6 does have an option to remove and modify stuff on the notification bar like time and signal, wifi etc.
For making me notice this, I hate you.
I don't always complain, but when I do, I #BlameWes
I have the green line on the left side and the gray bar up top, but no am/pm.
Do you guys leave the display on while it charges?
My display is only on while I use the phone, I got it around release date
Not totally for me, but I can see it faintly coming in. I have had this phone (my third one) for almost 2 months now.
I use beautiful widget works great had since day one in august screen is perfect
Sent from my SGH-T959 using Tapatalk
I'm kind of curious why an AMOLED screen would get burn-in. There's no backlight, so the only image we see is coming from emitting pixels. Is there a coating on the glass that burns in?
Kubernetes said:
I'm kind of curious why an AMOLED screen would get burn-in. There's no backlight, so the only image we see is coming from emitting pixels. Is there a coating on the glass that burns in?
Click to expand...
Click to collapse
Good question. Could the following be a possibility?
LED's eventually start to die off. Could areas that are always lit, for example the AM/PM is always on, thus those LED's are dying, which makes that area unable to to fully brighten, giving the impression of burning in, since the surrounding LED's are still bright.
That's just a guess on my part.
Also, are you sure Amoled's don't burn in, or is that just a guess/opinion/question on your part?
I can't really vote since I've only had it for a month and a few days, but I don't have any burn in. It's probably because it never disabled orientation flip and I do watch a some kind of video on the phone daily.
Had mine since day one. No burn in. my phone barely makes it to the charger most nights and some it needs an afternoon charge so I definitely use the phone quite a bit.
Sent from my SGH-T959 using XDA App
Damn it. Did screen test. Area where signal bars and time would be are clearly suffering from burn in. Awesome! This, combined with the generally bad software is making me consider selling this and never buying a Samsung phone ever again. (Sad, because their TV's are the best of the bunch.) To be fair, it's only noticeable when you look for it during a white screen and only in that area. Still, really Samsung? I've had this phone for 2 and a half months.
Had my phone for about a month and a half now, ran screen test and am seeing burn in
.
Got my Vibrant the day it launched - July 15th - no burn in, I use it quite a bit, but have the screen timeout after 30 secs.
Surely is burning in. Barely see it, but it is visible.
Sent via Galaxy S and Tapatalk
So, I stumbled across something really cool (quite) a few minutes ago: apparently our devices really can power a few pixels selectively. In my accidental confirmation of Samsung's claim, I was able to get one of NoLED's notification icons to show on the screen without lighting up the rest of the black area for literally a split second.
Here's how:
1. You will need the app "NoLED" in order to continue. In the NoLED settings, make sure you have the icon for sms activated as well as the proximity sensor. My sms icon is set to a lime green, but I doubt that will affect this "test."
2. Send yourself a text message either from your own phone or from some other sms capable device. If sending it to yourself from your own phone, quickly lock the device using the power button after pushing send.
3. Allow NoLED to start flashing around the icon for sms. Wait roughly 5 seconds for the proximity sensor to activate.
4. For steps 4 and 5, it would be wise to be in a completely dark room to be able to more easily tell the difference between the true black and the lit black. With the proximity sensor now active, place your finger over it. The screen should turn off.
5. Now, upon removing your finger pay close attention to the icon that will appear. The icon will show up a couple of milliseconds before the rest of the screen activates.
6. Repeat steps 4 and 5 if needed to witness the true black.
This is proof that our SAMOLED screens can display true black.
I am not a developer so I have no idea how to act upon this find to, if possible, adjust settings in the our software to allow true black.
If you happen to know someone who is capable of modifying the kernels or ROMs for our devices to allow this behavior, then by all means have them follow the above steps to see the proof.
Though I hope this minor find can give someone the inspiration and/or start place needed to make these adjustments, I realize this is but a pebble in a world of boulders. Therefore, I remain skeptical and strongly advise others not to get your hopes up.
If anything, it is at least nice to see that Samsung wasn't just lying about the capabilities of SAMOLED screens, but also makes one wonder why they don't allow true black from the start.
Now, time to hit the hay.
Goodnight all.
Sent from my SCH-I500 using Tapatalk
On the epic, when you power it up to the initial "galaxy s" screen, you can see true black...the fascinate doesn't have that opening animation?
Sent from my SPH-D700 using XDA App
A_Flying_Fox said:
On the epic, when you power it up to the initial "galaxy s" screen, you can see true black...the fascinate doesn't have that opening animation?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
It probably did at one point but since I changed kernels and boot animations trying to get rid of verizon crap that animation doesn't show up anymore, which sucks cause I actually liked that one.
Sent from my SCH-I500 using Tapatalk
When i power the device off in a dark room, at the end of the power off cycle I get a black screen that isn't black like the other black screens when the phone is on. It looks like it's glowing in the dark or some junk, and you can see a weird pattern like something smudged across the screen.
Is this the type of thing you're talking about? That our devices, when showing black, are actually working to show that black and not just "turning the pixel off" er whatever?
chronster said:
When i power the device off in a dark room, at the end of the power off cycle I get a black screen that isn't black like the other black screens when the phone is on. It looks like it's glowing in the dark or some junk, and you can see a weird pattern like something smudged across the screen.
Is this the type of thing you're talking about? That our devices, when showing black, are actually working to show that black and not just "turning the pixel off" er whatever?
Click to expand...
Click to collapse
Yes, if I'm understanding you correctly that is what I'm talking about. That glowing, almost grey effect shouldn't need to occur in order to show black. I hope it is something that can be hacked, but I don't know.
Sent from my SCH-I500 using Tapatalk
I guess this makes me lucky to have 1 pixel stuck on blue. I can easily see the screen turn off in almost any lighting condition.
Couldn't it be that what you're seeing is some kind of residual charge left at power off or some pixels that change states at slightly different rates? I've seen it too and it seems to be a different pattern every time. Also, some of the forums regarding screen burn have talked about samoled break-in so maybe that has an impact as well. Can't factor out power supply leakage either, I guess.
Sent from my SCH-I500 using XDA App
garywojdan81 said:
Couldn't it be that what you're seeing is some kind of residual charge left at power off or some pixels that change states at slightly different rates? I've seen it too and it seems to be a different pattern every time. Also, some of the forums regarding screen burn have talked about samoled break-in so maybe that has an impact as well. Can't factor out power supply leakage either, I guess.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
It is true all of those things could be probable, but in order to prove that the pixels aren't turning off you could disable the lock and screen dimming functions with an app and display a black image. Then in low light conditions you could easily see the blacks are actually a very dark shade of grey. If the pixels were turning off the image would over time obtain deeper blacks as the residual charge runs out.
I, and many others, suspect the phones are programmed to not turn off the pixels. Only question is, why? The only thing this type of test wouldn't be able to prove or disprove is power supply leakage.
Sent from my SCH-I500 using Tapatalk
atrich0608 said:
I guess this makes me lucky to have 1 pixel stuck on blue. I can easily see the screen turn off in almost any lighting condition.
Click to expand...
Click to collapse
That sucks to have a stuck pixel! Have you tried having the phone replaced? I don't know for sure but a stuck pixel might fall in the manufacturer defect category, so you might be able to have the phone swapped for free?
Sent from my SCH-I500 using Tapatalk
Or you can go and download Screen Test and get to the black screen part of the test. It is so hard to notice, but blacks are ever so slightly lighter than if you were to turn the screen off, but it is really hard to catch. Either way, they trump any LCD black levels. They even make my Panny plasma look bad
GoogleAndroid said:
Or you can go and download Screen Test and get to the black screen part of the test. It is so hard to notice, but blacks are ever so slightly lighter than if you were to turn the screen off, but it is really hard to catch. Either way, they trump any LCD black levels. They even make my Panny plasma look bad
Click to expand...
Click to collapse
Didn't know about that app but I'm sure it would work just as you say. And by the way that would be much easier to notice if you were in complete darkness. I'm completely satisfied with these amazing screens, but it would be awesome if we could obtain true black.
Sent from my SCH-I500 using Tapatalk
evilhunter101 said:
Didn't know about that app but I'm sure it would work just as you say. And by the way that would be much easier to notice if you were in complete darkness. I'm completely satisfied with these amazing screens, but it would be awesome if we could obtain true black.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I HAVE tested it in darkness. It is just such a small difference most people's eyes probably couldn't even pick up on it. Blacks are pretty black on this.
evilhunter101 said:
That sucks to have a stuck pixel! Have you tried having the phone replaced? I don't know for sure but a stuck pixel might fall in the manufacturer defect category, so you might be able to have the phone swapped for free?
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
It's only one and it's on the side, it does work sometimes. I use noled and it seams to come on at the exact same time as the notifications. Cover the proc sensor and it turns off.
Have you tried jscreenfix from the market? It's free and alot of feedback suggests it can work on stuck pixels.
Sent from my SCH-I500 using XDA App
GoogleAndroid said:
I HAVE tested it in darkness. It is just such a small difference most people's eyes probably couldn't even pick up on it. Blacks are pretty black on this.
Click to expand...
Click to collapse
Calm down man, was just a suggestion lol. But that's interesting, considering mine is extremely noticible in darkness even with the brightness turned all the way down. I suppose each phone would behave differently in this respect though.
atrich0608 said:
It's only one and it's on the side, it does work sometimes. I use noled and it seams to come on at the exact same time as the notifications. Cover the proc sensor and it turns off.
Click to expand...
Click to collapse
Well I guess that isn't too bad, hopefully it isn't a sign of things to come. Back when I had my Storm 1, I had a red stuck pixel. It wasn't too bad either until it started spreading a few months later. That's okay though, I was one of the lucky ones who got a Storm 2 as a replacement from Verizon. If you havent, you should definitely try that app mentioned above though.
Sent from my SCH-I500 using Tapatalk
Yep I tried that app. I kind of like it now, maybe I will name it lol. I will save it for later, if I scratch the screen or something It will give me an excuse to get a new phone
Since the Nexus S uses the same SAMOLED as the Galaxy S phones (which are prone to burn in due to its technology), I would expect it to have the same problem.
Just a heads up because someone is bound to come here complaining about it sooner or later.
The first thing people notice is the AM/PM burn in, so if you care, I recommend switching to military time
The a.m. / p.m. was removed in Gingerbread.
I will ALWAYS use ADW or Launcher Pro from now on to hide the notification bar to avoid screen burn. I also use a non-stock browser (Dolphin atm) to hide the notification bar as well.
My captivate has never burned in, but I do keep it on lowest brightness settings.
CaliLove310 said:
The a.m. / p.m. was removed in Gingerbread.
Click to expand...
Click to collapse
you know what? I just now noticed that!
My nexus one has burn in of the notification bar too. The white color causes it but now since its black it will reduce it. But the white text like the clock time can still cause it. Use launcher pro to hide the bar completely is recommended to reduce the time showing a static image in one spot.
RogerPodacter said:
My nexus one has burn in of the notification bar too. The white color causes it but now since its black it will reduce it. But the white text like the clock time can still cause it. Use launcher pro to hide the bar completely is recommended to reduce the time showing a static image in one spot.
Click to expand...
Click to collapse
Same here.... just became aware of this now...
Opened Angry Birds and there it was!
Already have Burn in on the Nexus S
LOL I am sure this will cause a ruffle tuffle. But I know how you guys like to ***** about stupid **** so here goes.
I have keyboard burn in on portrait mode. Simple test. With no notifications and keyboard up pull down the notification window. You will see that the keys's outline still show. Now hide the keyboard and do the same. You will see the outline still in the notification pull down.
Oh boy; I'll let others have a go at this post.
I don't know what your talking about. The keyboard does not show through the notification bar for me
Sent from my Nexus S using Tapatalk
I have it too, but it fades away after a few seconds.
don't see any outlines
*facepalm10char
zeeklancer said:
LOL I am sure this will cause a ruffle tuffle. But I know how you guys like to ***** about stupid **** so here goes.
I have keyboard burn in on portrait mode. Simple test. With no notifications and keyboard up pull down the notification window. You will see that the keys's outline still show. Now hide the keyboard and do the same. You will see the outline still in the notification pull down.
Click to expand...
Click to collapse
Its not permanant bro..
I've been turning the screen timeout off to prevent the screen from turning off while gaming until the game devs update for Gingerbread compatibility. Last night I left it on when I went to sleep and a scheduled backup woke the phone up in the middle of the night. Screen was on for 6 hours displaying the same image. Absolutely no image burn.
If you're seeing burn-in after using the phone normally, you need to exchange it.
mmas0n said:
I've been turning the screen timeout off to prevent the screen from turning off while gaming until the game devs update for Gingerbread compatibility. Last night I left it on when I went to sleep and a scheduled backup woke the phone up in the middle of the night. Screen was on for 6 hours displaying the same image. Absolutely no image burn.
If you're seeing burn-in after using the phone normally, you need to exchange it.
Click to expand...
Click to collapse
this.
its an lcd not plasma. you wont get burn in this quicly if any. you have an issue with your phone.
the other day someone posted something like that. about burn in issue in weird vertical lines. i thought he is talking about the screen grid pattern that its more obvious in some poor designed screen than others.
..............
HOW ON EARTH SAMSUNG MANGAED TO GET AN LCD SCREEN WITH A BURN IN ??????????????????????????????????????
is their QA/QT a big friggin ZERO ???????
Does the nexus s use a different type of screen than the galaxy phones? My vibrant uses a super amoled screen, which I believe have more of a chance for screen burn in than plasma.
Sent from my SGH-T959 using XDA App
ll_l_x_l_ll said:
this.
its an lcd not plasma. you wont get burn in this quicly if any. you have an issue with your phone.
the other day someone posted something like that. about burn in issue in weird vertical lines. i thought he is talking about the screen grid pattern that its more obvious in some poor designed screen than others.
..............
HOW ON EARTH SAMSUNG MANGAED TO GET AN LCD SCREEN WITH A BURN IN ??????????????????????????????????????
is their QA/QT a big friggin ZERO ???????
Click to expand...
Click to collapse
I actually have this problem lol Even the XDA app back button is burnt in and can be seen when a gray background is shown.....Basically every time you open the notifications tab.
ll_l_x_l_ll said:
this.
its an lcd not plasma. you wont get burn in this quicly if any. you have an issue with your phone.
the other day someone posted something like that. about burn in issue in weird vertical lines. i thought he is talking about the screen grid pattern that its more obvious in some poor designed screen than others.
..............
HOW ON EARTH SAMSUNG MANGAED TO GET AN LCD SCREEN WITH A BURN IN ??????????????????????????????????????
is their QA/QT a big friggin ZERO ???????
Click to expand...
Click to collapse
Umm its not an lcd, its an amoled and they absolutely suffer from burn in. Just ask the many nexus one owners. It took only one month from brand new for my notification bar to burn in to the screen. All Samsung amoled screens suffer from this, including the nexus s will too. Unless of course you're careful not to allow any one static image to remain on the screen for too long.
RogerPodacter said:
Umm its not an lcd, its an amoled and they absolutely suffer from burn in. Just ask the many nexus one owners. It took only one month from brand new for my notification bar to burn in to the screen. All Samsung amoled screens suffer from this, including the nexus s will too. Unless of course you're careful not to allow any one static image to remain on the screen for too long.
Click to expand...
Click to collapse
hmm weird i dont remember having this on my galaxy S. this is really weird to hear :/
Dear Friends,
In peripheral vision, I can see a the 6p screen flickering slightly. Mostly only noticeable on bright white and green screens on full brightness (without auto brightness adjustment)
Can you please do me a solid one and check it out on your device?
1. Turn Off brightness adjustment in Display settings
2. Set phone to full brightness
3. Load a completely white background (chrome browser starting page or any screen testing tool)
4. Hold the phone centrally close to your face and look at another object in the room while viewing the phone in your peripheral vision
5. Look back and forth at the object in the room and at the screen to see if you notice a slight flickering or restlessness in the screen
The flickering is very faint and hard to notice in peripheral vision but it is definitely there. I tired the same with an iphone 6plus and the iphone screen (my brothers Iphone, I'd never buy none) definitely has no flicker at all. It's very steady.
The screen is also not as bright as the iphone 6+ but I think that is well known.
I'd like to know if it is standard with all nexus 6p's and if it bothers you at all.... maybe I am just obsessing or maybe not and I need to RMA the device which is a huge pain in the ass.
Thanks!
Thomas
I do not have this issue at all. There are two possibilities, there is a defect with your device OR you are sensitive to the refreshing of the display. However, most modern displays have a refresh rate of 60Hz or higher (I assume the Nexus 6P and iPhone 6 are 60Hz, but I cannot find that info) so it's odd you haven't experienced this with other devices.
My best advice is for you to get your hands on a different Nexus 6P to see if you have the same problem. If you can't do that, I would suggest you try to see if you notice it in any other displays. Maybe go to a store and try it with a Samsung Galaxy S6/Note 5 as those have a similar AMOLED display, whereas the iPhone is LCD.
Thanks for your quick feedback. I am really surprised that noone has noticed this. I am looking at the device straight I don't notice it either it is only in peripheral vision that I can see it but even then it is very hard to catch. I think that indeed it must have something to do with the refresh rate of the screen.
Maybe other people can give it a try ? I have a gut feeling that it is an "issue" in all Nexus 6P devices but that most people don't notice it because it takes a very malicious mind to see it. Maybe it's because the device is brand new and the screen needs some time to "break in" or "adjust" ?
I just want to make sure that I don't have a defective device.
Thanks everyone
Maybe It's related to http://forum.xda-developers.com/nexus-6p/help/screen-flicker-pwm-question-t3228826 ??
exxi said:
Maybe It's related to http://forum.xda-developers.com/nexus-6p/help/screen-flicker-pwm-question-t3228826 ??
Click to expand...
Click to collapse
I have heard of that before, but you're seeing the issue on super high brightness. Perhaps try it on a lower brightness to see if it worsens.
PWM (Pulse Width Modulation) is used for making the display darker. For example, say that a phone has a 60Hz refresh rate, meaning all of the pixels update 60 times each second. To make the display dimmer, the pixels are on for a shorter period of time in between each refresh. For maximum brightness, the pixels are on for the entire time between each refresh. Thus, when the display is dimmer, some might notice flickering as the pixels turn on and off.
Billy, again, thanks for your response. I will give it a try.
The best way I can describe it is that the effect is extremely subtle; so much, that I don't notice it looking directly at the screen but it translates into a sort of "nervousness" of the screen in general because you are left with the feeling that the screen is constantly moving and not really 100% steady. I am not sure if it is something I can/will get used to over time but I am willing to give it a try for a few days.
I am also almost certain that I don't have a hypersensitivity of some sorts but rather that all Nexus 6P phones have this issue just that most of the people don't really notice it.
I'd love to hear from others about if they see it
It's normal, it's caused by PWM. I don't notice it much on my 6P,my Note 4 had it much worse. Some people are more aware of it than others and seem more succepatble to seeing it.
Sent from my Nexus 6P using Tapatalk
Batfink33 said:
It's normal, it's caused by PWM. I don't notice it much on my 6P,my Note 4 had it much worse. Some people are more aware of it than others and seem more succepatble to seeing it.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Thanks nice to hear that it is "normal" i was worried i had a defective unit
So you are saying if you really pay attention to it, you WILL notice some of it for ANY person, right?
I have a Galaxy S6 and I have not noticed it there. Does that mean that the S6 is not using PWM ?
Thanks
exxi said:
Thanks nice to hear that it is "normal" i was worried i had a defective unit
So you are saying if you really pay attention to it, you WILL notice some of it for ANY person, right?
I have a Galaxy S6 and I have not noticed it there. Does that mean that the S6 is not using PWM ?
Thanks
Click to expand...
Click to collapse
I think the S6 uses it also but some phones seem worse than others. As I said, I can see my 6P a little but my Note 4 was worse, I could see the flicker all the time.
I just checked my S6 for the issue (side by side with the 6P) and I can say with confidence that the S6 does not have the issue AT ALL. The screen does not flicker in peripheral vision and as a result appears steadier and calmer in general.
If i hold a video camera over each screen I can see scan-lines moving diagonally upward in regular intervals/spacing which both phones, however the lines are stronger and more visible with the 6P Screen. Which in my humble option explain why I am noticing this effect. I am just not sure if something like that warrants the effort of returning or swapping out my 6P
It doesn't really bother me but knowing that maybe other 6P devices have it less makes me think because I shelled out 699€ for it....
What would you do?
exxi said:
I just checked my S6 for the issue (side by side with the 6P) and I can say with confidence that the S6 does not have the issue AT ALL. The screen does not flicker in peripheral vision and as a result appears steadier and calmer in general.
If i hold a video camera over each screen I can see scan-lines moving diagonally upward in regular intervals/spacing which both phones, however the lines are stronger and more visible with the 6P Screen. Which in my humble option explain why I am noticing this effect. I am just not sure if something like that warrants the effort of returning or swapping out my 6P
It doesn't really bother me but knowing that maybe other 6P devices have it less makes me think because I shelled out 699€ for it....
What would you do?
Click to expand...
Click to collapse
Does it get worse on the 6P when you turn the brightness down? How about on the S6, if you turn the brightness down (which should exemplify the PWM issue) does it have the same effect as the 6P?
BillyTheRatKing said:
Does it get worse on the 6P when you turn the brightness down? How about on the S6, if you turn the brightness down (which should exemplify the PWM issue) does it have the same effect as the 6P?
Click to expand...
Click to collapse
Thanks for asking. When I turn the brightness down on the 6P it gets better; the effect is not noticeable anymore when it's set on 50% brightness. As soon as I have it on 100% I can see it from the corner of my eyes when set on a white background.
The question is really if I can expect it to be different on another 6P or if all the 6P's have this level of subtle "flickering" if I may call it.
I suspect the latter... and from this point of view it doesn't make sense to swap it out. if you are able to notice it ever so slightly on your device then changes are that it is present on all devices and that the 6P just has it more than for example the Samsung S6 because on the sammy I can't notice it at all, even on full or low brightness for that matter.
As you've said , if it were a PWM issue, It would worsen with low brightness, correct? In my case it worsens with high brightness. So what really is it then?
Quick question... Under normal day-to-day usage, you look at your screen out of the corner of your eyes and have the brightness set at 100%?
WizeGuyDezignz said:
Quick question... Under normal day-to-day usage, you look at your screen out of the corner of your eyes and have the brightness set at 100%?
Click to expand...
Click to collapse
You're asking the right questions here and the answer is no to both ?
However I hope your can understand my concern because in the beginning nothing is more important than having a flawless device to my very rigid mind.
Also im worries that the screen in general is not calm as compared to other models such as the s6. Basically that since the flicker is present I might still perceive it even when looking straight at the screen.
I decided to order another 6P to be able to compare the 2 and see if the issue persists on the new device. Depending on the outcome I will keep one or return both. The flickering is really evident and IMO unacceptable for a device with this pricetag.
I am not sure if this is the same thing, but see the flicker in the attached video. It's at 5th,10th and 15th seconds. But then I checked it on Galaxy S4 and see it there as well. I don't notice it in any other screen. May be NBA app is causing it.
https://youtu.be/wtAiMt32GfI
nsical said:
I am not sure if this is the same thing, but see the flicker in the attached video. It's at 5th,10th and 15th seconds. But then I checked it on Galaxy S4 and see it there as well. I don't notice it in any other screen. May be NBA app is causing it.
https://youtu.be/wtAiMt32GfI
Click to expand...
Click to collapse
that is indeed odd. I think the app is causing it
I am just surprised that noone else has noticed the flickering as i described above. It is quite evident when you hold the phone in front of your face and look at something in the room. I wish others would give me some feedback on it
exxi said:
I am just surprised that noone else has noticed the flickering as i described above. It is quite evident when you hold the phone in front of your face and look at something in the room. I wish others would give me some feedback on it
Click to expand...
Click to collapse
I have been searching for someone, anyone, who has this issue as I do. Everything you said previously, I experience as well. I've had a 6p since November, and the flickering was there from day one. It's easy to notice at >50% brightness on white or greenish screens. Less so on red and blue. It's something I've gotten somewhat used to, but sometimes it really bugs me. Have you had any success with trying things?
I have recorded the screens of the 6p and 5x. The difference and flicker of the 6p is clear.
Nexus 6p: https://www.youtube.com/watch?v=sEA41Uoehkg
Nexus 5x: https://www.youtube.com/watch?v=GCMEvUsA0TQ
Doesn't seem like the clock or battery icon move around like Always On mode. Will this eventually cause burn in?
Sent from my SM-G935T using Tapatalk
No. Amoled displays don't suffer from that. Even high quality LCD displays like found on the iPhone will have a hard time causing burn in.
Sent from my SM-G935F using Tapatalk
The information provided above is false. Amoled screens can suffer from burn in. However, with the Always On Display, the clock moves around every 3 minutes or so to avoid burn in.
CuBz90 said:
The information provided above is false. Amoled screens can suffer from burn in. However, with the Always On Display, the clock moves around every 3 minutes or so to avoid burn in.
Click to expand...
Click to collapse
He's asking about the night mode, which puts the clock on the edge of the screen. It doesn't move around in that mode.
I don't know the answer, but I don't use it for that fear.
berfles said:
He's asking about the night mode, which puts the clock on the edge of the screen. It doesn't move around in that mode.
I don't know the answer, but I don't use it for that fear.
Click to expand...
Click to collapse
Ah!
I imagine the night clock woukd cause burn in ad it does stay in one place.
Sent from my SM-G935F using Tapatalk
Well the numbers do change every hour and minute so I think it would be hard to get any noticeable burn in.
Sent from my LG-D851 using XDA Free mobile app
Richieboy67 said:
Well the numbers do change every hour and minute so I think it would be hard to get any noticeable burn in.
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
Unfortunately the battery icon and next alarm displayed doesn't change.
Sent from my SM-G935T using Tapatalk
I was wondering this and also worried about burn in , so I turned off night clock because it doesn't move, and I'm asleep so I don't need it on.
Sent from my SAMSUNG-SM-G935A using Tapatalk
I doubt it, the brightness would be low enough to minimize the risk of burn-in.
I don't think it would. I have mine set to only stay on from 1AM until 5AM (the hours I'm most likely to wake up in the middle of the night and want to see the time.)
I don't think 4 hours is enough to cause burn in being how the pixels are lit up very dim when using the night clock.
ydoucare said:
I doubt it, the brightness would be low enough to minimize the risk of burn-in.
Click to expand...
Click to collapse
The pixels are stilll active though, shortening their "life". Will you notice any burn in or difference in screen quality in that area within a month or six? Probably not, but it'll burn in (or, leave a mark if you want) no matter what after 24+ months. AMOLED is a tricky technology, so I personally stay away from "AMOLED black" themes and whatnot. Why? The black areas are turned off, while the colored/lightened pixels are lit up. The areas that are "off" will have a longer "pixel life" than the ones most used, so it'll make a sort of "ghosting" effect after a while (2 years+). Using a theme or whatever that's "even", i.e not on and off at different places will give me an even "burn out".
I have no idea how good the EDGE's panel is though, so this is pretty much pure speculation, with some facts mixed in!
At first I was also worried that the pixels don't change position, but having it on for a week, I think it's too dark to cause a burn-in.
The Always-On clock looks like it'll burn in more because it's bright even though it moves around every couple minutes.
I use a black background. I don't think it'll cause uneven wear. Every time I use a web browser, the background is mostly white. I think that's enough to evenly burn in the screen. I usually keep the screen little dimmer than normal to avoid burn in., but I'm not afraid of ramping up the brightness when I'm outside under the sun or reviewing photos.
One thing I don't like about the night clock is that it shows the alarm that's couple days out. I think Samsung really need to fix this as this is obviously a bug, or they didn't test it enough.
hp79 said:
At first I was also worried that the pixels don't change position, but having it on for a week, I think it's too dark to cause a burn-in.
The Always-On clock looks like it'll burn in more because it's bright even though it moves around every couple minutes.
I use a black background. I don't think it'll cause uneven wear. Every time I use a web browser, the background is mostly white. I think that's enough to evenly burn in the screen. I usually keep the screen little dimmer than normal to avoid burn in., but I'm not afraid of ramping up the brightness when I'm outside under the sun or reviewing photos.
One thing I don't like about the night clock is that it shows the alarm that's couple days out. I think Samsung really need to fix this as this is obviously a bug, or they didn't test it enough.
Click to expand...
Click to collapse
Everything is pure speculation regarding the AMOLED panel around here, so we won't really know anything concrete until something happens, or someone gets a nasty burn-in. I doubt anyone will get a nasty burn-in though, but I guess someone will get some burn-in down the road, but that's pretty much expected.
I have a Galaxy Note (first gen.) that I used for about 18 months before getting a new device, and I've borrowed it to my mom. I checked it out again this week after not checking it out for about two years, and the display looks like ****, but it doesn't look more **** as it did the day I gave it to her, so it's "bad" if I'm trying to edit some photos, but it's not catastrophically bad at all. The only place it's burnt in is the statusbar, which is black on pre-lollipop versions if I remember correctly.
Hi clever people
So I'm a bit confused. I found this thread because I was afraid of a burn-in caused by the night clock too.
And I won't use it. But how about the always on display, then - by using that, is there a risk of shortening the life of the pixels? In that case, I'd just turn it off. But if not, well, then it's a neat feature
Well, I have set night clock every night, It doesn't burn the AMOLED screen. It's completely safe. Try it on your own, no risk They prevent burn in, because of brightness help keep prevent burn-in.
kylelopez20 said:
Well, I have set night clock every night, It doesn't burn the AMOLED screen. It's completely safe. Try it on your own, no risk They prevent burn in, because of brightness help keep prevent burn-in.
Click to expand...
Click to collapse
Thanks. I was more curious, though, as to how the Always on Display feature might affect pixels and the screen lifetime too, and thus, if it'd be better to not use this feature
brawlysnake66 said:
No. Amoled displays don't suffer from that. Even high quality LCD displays like found on the iPhone will have a hard time causing burn in.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
False. AMOLEDS suffer burn in, and LCDs will rarely ever experience it.
---------- Post added at 11:43 PM ---------- Previous post was at 11:41 PM ----------
J.Biden said:
The pixels are stilll active though, shortening their "life". Will you notice any burn in or difference in screen quality in that area within a month or six? Probably not, but it'll burn in (or, leave a mark if you want) no matter what after 24+ months. AMOLED is a tricky technology, so I personally stay away from "AMOLED black" themes and whatnot. Why? The black areas are turned off, while the colored/lightened pixels are lit up. The areas that are "off" will have a longer "pixel life" than the ones most used, so it'll make a sort of "ghosting" effect after a while (2 years+). Using a theme or whatever that's "even", i.e not on and off at different places will give me an even "burn out".
I have no idea how good the EDGE's panel is though, so this is pretty much pure speculation, with some facts mixed in!
Click to expand...
Click to collapse
No offense that is the most stupid reason I've heard not to use dark/black themes. White themes ARE MUCH MORE LIKELY TO CAUSE BURN IN, PERIOD. You reduce burn in by reducing energy consumption and pixel usage.