Develop Bugs

I'm seeing some status bar "Burn-In"

Please read everything before posting an insulting comment towards me for sharing an observation I've had.
I love this phone, and what I love most is the beautiful display. One thing concerns me though.
Reading Google Currents which removes the status bar to go full screen, I noticed what I thought was a blue haze border at the top of the screen. At closer inspection it wasn't a border...it's where the status bar should be, and it was putting off a noticeable light blue haze across the screen which persisted when going landscape. I cranked up the brightness to full, and it had little effect on it.
I kind of shake my head at people who load up a pixel checker app in a dark room and analyze every last pixel on the screen in every color. But, if it is already noticeable in normal use after a few weeks... it concerns me what the top and bottom of the phone may look like in a year.
I know the black bar should be turning the pixels off, which should result in no burn in... I can't explain why it is leaving a mark...but it is obvious that it is doing something.

Yes I'm seeing some slight burn in as well on my notification bar, specifically the click numbers on the right. I just make sure I have the web browser on full screen so it hides the status bar and gives those pixels a break.
My nexus one had burn in within the first month. So with this phone I make sure to avoid this immediately.
And yes the on screen buttons was my first concern about burn in. That white icon on black contrast is just asking for burn in. My criticism of these on screen keys is that Google didn't take advantage of them at all. They never move at all and never change, and they only disappear in one place during video. What a waste. Might as well have regular keys if that's all you're gonna do as it just wastes screen space.

Wow. I see it too.
:/

I thought I noticed some burn-in the other day but wasn't sure, since no one was complaining I assumed that I'm imagining things. The "all applications" button from the bottom-center of the home screen is visible like a ghost on the grey background of the settings application.
Do you guys see it as well?

Just a suggestion (and i'm not claiming this is a real solution)...
Download ADW and turn the status bar off. Swipe-down for notifications. That's what I do, at least.

bennettm89 said:
Just a suggestion (and i'm not claiming this is a real solution)...
Download ADW and turn the status bar off. Swipe-down for notifications. That's what I do, at least.
Click to expand...
Click to collapse
I appreciate your input.. but as you stated I don't see it as a solution. The status bar is a rather important part of the OS. Not to mention if that tiny black bar is causing it to distort...I can't imagine wast the on screen buttons will look like when apps start using that real estate (like games)

Grims said:
I appreciate your input.. but as you stated I don't see it as a solution. The status bar is a rather important part of the OS. Not to mention if that tiny black bar is causing it to distort...I can't imagine wast the on screen buttons will look like when apps start using that real estate (like games)
Click to expand...
Click to collapse
I understand. Just trying to promote a temporary solution to a possibly permanent problem

I have horrible burn in on my N1 - both the status bar and keyboard keys have burned in..
It doesn't really bother me though as it is only visible in certain situations..
Sent from my Nexus One using Tapatalk

OP I don't think what you are seeing is burn in. I think that is just how the screen is. I have the same slight blue hue at the top of the screen when I'm using the browser, and it has been there since day one. Every GNex that I have seen also have this. I think that is just how the screen is, I don't think it has anything to do with burn in or the status bar.

That sucks. I am not seeing any burn in on my GNex, but maybe I don't use mine as much as you guys.
Outside of the ADW solution is there anything else we can do about this...seems like a big design flaw if this is really the case.
Sent from my Galaxy Nexus using xda premium

no issues here at all. in addition, to all the burn in complaints on the nexus one, i had that for 20 months, and never got burn in. and always had the statusbar shown.

I think the problem lies with the technology itself. The Super AMOLED displays, like the base OLED technology, use organic material that degrade over time.
http://en.wikipedia.org/wiki/OLED
So, there is something of a trade off between the vibrant Super AMOLED displays with deep blacks and the lifespan of them.
There also the problem that although the Super AMOLED display consumes less power when displaying dark images it can consume more power when displaying light images like you see on many web pages.
Brian

Raptor1956 said:
I think the problem lies with the technology itself. The Super AMOLED displays, like the base OLED technology, use organic material that degrade over time.
http://en.wikipedia.org/wiki/OLED
So, there is something of a trade off between the vibrant Super AMOLED displays with deep blacks and the lifespan of them.
There also the problem that although the Super AMOLED display consumes less power when displaying dark images it can consume more power when displaying light images like you see on many web pages.
Brian
Click to expand...
Click to collapse
If that is what we were seeing here, wouldn't the status bar actually be more white than the rest of the display, due to it getting much less use because of the black bar?

I have screen burn in that fades away after time on my G2 as well. I noticed a slight bit on the GN, but it fades away too.

neok44 said:
no issues here at all. in addition, to all the burn in complaints on the nexus one, i had that for 20 months, and never got burn in. and always had the statusbar shown.
Click to expand...
Click to collapse
Like I said, I have some pretty significant burn in on my N1. On a pure grey screen, I can see the keyboard and the keyboard keys as well as the status bar...
However, I really don't care 99% of the time it is unnoticeable.
I just took my GN out of the box and the bottom bar is burned in. On a pure grey screen, I can actually see the home icon burned in... Does samsung run these screens before shipping?
However, it is very insignificant so I do not mind. This screen is simply amazing! I have no extreme banding or other issues mentioned here. I also got a yakju device

mysterioustko said:
OP I don't think what you are seeing is burn in. I think that is just how the screen is. I have the same slight blue hue at the top of the screen when I'm using the browser, and it has been there since day one. Every GNex that I have seen also have this. I think that is just how the screen is, I don't think it has anything to do with burn in or the status bar.
Click to expand...
Click to collapse
Its burn in, I can actually see the clock numbers on a white background. This isn't a new issue, all Samsung amoled screens have dealt with this over the years. My nexus one also has the entire keyboard permanently burnt in after a year of use.
ADW launcher was a good solution back in the day as hiding the status bar gave those pixels a break and broke up the constant static image.
I'm just making sure to rotate the screen and hide the bar often.

NPuter said:
Like I said, I have some pretty significant burn in on my N1. On a pure grey screen, I can see the keyboard and the keyboard keys as well as the status bar...
However, I really don't care 99% of the time it is unnoticeable.
I just took my GN out of the box and the bottom bar is burned in. On a pure grey screen, I can actually see the home icon burned in... Does samsung run these screens before shipping?
However, it is very insignificant so I do not mind. This screen is simply amazing! I have no extreme banding or other issues mentioned here. I also got a yakju device
Click to expand...
Click to collapse
yes most manufacturers run each phone with the screen on for a certain number of hours for testing and loading the factory image etc. But I thought it was usually special diagnostics tests and not just displaying the regular home screen. Maybe its both?

No burn in here. Also still have the Vibrant and no burn in on that either.
Sent from my Galaxy Nexus using Tapatalk

RogerPodacter said:
yes most manufacturers run each phone with the screen on for a certain number of hours for testing and loading the factory image etc. But I thought it was usually special diagnostics tests and not just displaying the regular home screen. Maybe its both?
Click to expand...
Click to collapse
Who knows. I just know that I noticed the burn in within ~3min of turning it on...
Sent from my Galaxy Nexus using Tapatalk

I see it on mine too :/ All these small issues are begining to build up....

[Q] Fix major AMOLED screen burn in?

Hi everyone, on my Galaxy Nexus I have MAJOR screen burn-in from the navigation bar. (black bar at bottom, back/home/apps) Whenever I turn the phone sideways (i.e. in a full-screen video or game), the navigation bar moves to the side as usual, and gets narrower...when it does this, I see a purple (why purple?) line that "fills up" where the navigation bar would be on portrait. Of course when it is portrait, this cannot be seen, as the navigation bar covers it. In ClockworkMod Recovery, at the bottom of the screen, I can see a strong burn-in of the navigation bar. It is incredibly annoying, and I heard that by displaying white on the entire screen for a long time (full brightness) this can be weakened or fixed. I have seen apps for this, but have no clue how long I should run them for. Is it REALLY possible to fix something MAJOR, or is it a "maybe..sometimes" or just a hoax?

you can try to take a snapshot of your screen and invert the colors of the image in a program (like photoshop online, idk). then you put that inverted image on your phone and view it full sreen.
I don't really know if this helps, but I read it somewhere when I had some sreen problems with my GNex (I sent it to warranty)

Rayaxe said:
you can try to take a snapshot of your screen and invert the colors of the image in a program (like photoshop online, idk). then you put that inverted image on your phone and view it full sreen.
I don't really know if this helps, but I read it somewhere when I had some sreen problems with my GNex (I sent it to warranty)
Click to expand...
Click to collapse
I'm not really sure how that would do anything. The rest of the screen is fine, there's only a problem at the navigation bar. Leaving an image like that might just burn in other colors. If it really was SAMOLED, then it should not have a burn in there at all...because it turns off "black" pixels. It's confusing and annoying.

Or try a Kitkat ROM with Google Experience Launcher which doesn't have the black nav bar and status bar...

atlantic00 said:
I'm not really sure how that would do anything. The rest of the screen is fine, there's only a problem at the navigation bar. Leaving an image like that might just burn in other colors. If it really was SAMOLED, then it should not have a burn in there at all...because it turns off "black" pixels. It's confusing and annoying.
Click to expand...
Click to collapse
maybe rest of the screen actually burned, so only not burned part is navbar and seems weird.
there is a tool: https://play.google.com/store/apps/details?id=com.codefortravel.amoled_screen_burn_in it has an option, that makes all your screen black and your nav bar white, using it for a while makes your navbar also burned, so it would eventually catch other parts and be the same level in theory..

antypas said:
Or try a Kitkat ROM with Google Experience Launcher which doesn't have the black nav bar and status bar...
Click to expand...
Click to collapse
I tried Cyanogenmod 11 and the navigation bar looked weird...it looked like I applied some sort of linear burn to the screen. It was ugly.
drmxmyt said:
maybe rest of the screen actually burned, so only not burned part is navbar and seems weird.
there is a tool: https://play.google.com/store/apps/details?id=com.codefortravel.amoled_screen_burn_in it has an option, that makes all your screen black and your nav bar white, using it for a while makes your navbar also burned, so it would eventually catch other parts and be the same level in theory..
Click to expand...
Click to collapse
It's not that. The rest of the screen is beautiful. It doesn't really seem like AMOLED, though, because the black glows in the dark...also, as I said, if I go on a white image, I see a burn-in of the navigation bar, so it's not that. And, I've already got a burn-in app. I use https://play.google.com/store/apps/details?id=com.feetstech.screenburn

atlantic00 said:
I tried Cyanogenmod 11 and the navigation bar looked weird...it looked like I applied some sort of linear burn to the screen. It was ugly.
It's not that. The rest of the screen is beautiful. It doesn't really seem like AMOLED, though, because the black glows in the dark...also, as I said, if I go on a white image, I see a burn-in of the navigation bar, so it's not that. And, I've already got a burn-in app. I use https://play.google.com/store/apps/details?id=com.feetstech.screenburn
Click to expand...
Click to collapse
Did you buy the GNexus brand new? Reason why I ask is because you mentioned that the blacks doesn't seem like Amoled and how it glows in the dark.
I'm wondering if you or the previous owner had the screen replaced because of a crack and the screen was replaced with a LCD from eBay.
Sent from my Galaxy Nexus using xda app-developers app

OuncE718 said:
Did you buy the GNexus brand new? Reason why I ask is because you mentioned that the blacks doesn't seem like Amoled and how it glows in the dark.
I'm wondering if you or the previous owner had the screen replaced because of a crack and the screen was replaced with a LCD from eBay.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
No, I got it off of eBay as a 'replacement' phone. This is my first smartphone (but not Android device) but I am still in a 2 year contract with Verizon and can't get an upgrade yet. It's not really a problem, just an inconvenience.

This was one of the reasons I always try too run in extended desktop mode(no on screen buttons/status bar) and use PIE controls instead.
Also helps running the stock browser in full screen mode.
Even after less than a few months of first owning my GN I've gotten a tiny little burn in on the bottom bar, but luckily it's not easily noticeable.

I have also got a burn-in. It's not too major, but it's there. Please do update us if you find any solution which actually fixes this thing.

I'm going to do some tests with different things.
I heard leaving a white image on full brightness for a long time will help, so I'm going to try that. Another thing I might try is color alternations for long periods of time to just get different colors all over the screen. Probably won't do much, but it's worth a try. I thought I'd also see what it's like using the phone locked upside down. (rotate upside down, lock rotation) This is the app I'm using if anyone else wants to experiment with it: https://play.google.com/store/apps/details?id=com.feetstech.screenburn
Wish me luck, I'll post what happens!
Update 1: I have noticed that on higher brightness levels, the burn is less noticeable. I left a white screen on full brightness for what was probably just over 2 hours, and it hasn't really seemed to help much. I'm going to try color flashing and see what happens.

Try this app. It is specifically developed to solve the navbar burn-in issue of the Galaxy Nexus.
https://play.google.com/store/apps/details?id=com.bengigi.screen.diagnostic
Sent from my Galaxy Nexus using Tapatalk

AbhishekS said:
Try this app. It is specifically developed to solve the navbar burn-in issue of the Galaxy Nexus.
https://play.google.com/store/apps/details?id=com.bengigi.screen.diagnostic
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
just try that apps on my nexus, thanks the burn got worse than before :crying:

That's not possible.
Check it again after an hour or so. Maybe the screen colors haven't 'settled in' yet.
Sent from my Galaxy Nexus using Tapatalk

AbhishekS said:
That's not possible.
Check it again after an hour or so. Maybe the screen colors haven't 'settled in' yet.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
before using that apps, my burn only a little transparent blueish, after using that apps overnight , my burn becoming a visible blueish :crying: also i think someone posted the same result as my gnex too.i think the only soluton is : just accept that burn in is the weakness of amoled screen., and considering to buy a the amazing n5 cuz its didnt use amoled thank God for that.

Are you sure the burn-in is persistent? Usually it goes away after a while.

Almost forgot I started this thread! I don't really know if the burn in apps helped any, but I've noticed that the lower the brightness is, the more imminent the screen burn is. Around 1% if you touch one of the navigation buttons it turns.......purple. Once you get above around 20%, it's more grey and natural....(not purple)
._.

amoled + low brightness = nearly unusable.

TheImpossibleEnemy said:
amoled + low brightness = nearly unusable.
Click to expand...
Click to collapse
Depends on your environment. In a dark room it's fine all the way down. If you're outside in the sun, even 50% seems a little dark.

atlantic00 said:
Depends on your environment. In a dark room it's fine all the way down. If you're outside in the sun, even 50% seems a little dark.
Click to expand...
Click to collapse
exactly

Image Burn ALREADY?!

I just came across this tweet this morning and am wondering if anyone is already experiencing this on here.
https://twitter.com/alexdobie/status/922060857659547648

It's probably image retention and not actually burn in.
Sent from my Pixel 2 XL using Tapatalk

This is exactly why all phones with on screen navigation need to have auto hide capabilities.
Sent from my Pixel XL using Tapatalk

Not at all. I just activated immersive mode via adb anyways because I like the way it looks with the curved display and taking up the entire display. I also use unique controls to put a pie on the right side since the bottom of the screen is so low, it's easier to use a pie on the side to navigate for reachability with one hand.
To elaborate on your question, I have no burn in and no retention. People talked about burn in early on with the Pixel 1 (and XL), but mine still has none even though I used the on screen navbar.

My Nexus 6, 6p Pixel 1 and my 2 XL have zero burn in. https://play.google.com/store/apps/details?id=pl.damianpiwowarski.navbarapps&hl=en fantastic app.

Yeah. Checked mine. No burn in.
Sent from my Google Pixel 2 XL using XDA Labs

zetsumeikuro said:
My Nexus 6, 6p Pixel 1 and my 2 XL have zero burn in. https://play.google.com/store/apps/details?id=pl.damianpiwowarski.navbarapps&hl=en fantastic app.
Click to expand...
Click to collapse
Yup yup.. I'm running them and I use SystemUI tuner to auto hide navs when I wish.. Excellent [emoji1303]
Sent using Tapatalk

https://www.theverge.com/2017/10/22/16518298/google-investigating-pixel-2-xl-screen-burn-in
Apparently Google are looking into it.

I got mine on Oct 18th and did a quick test.
I do (slightly) see what is described as burn-in, but I see it only when I go beyond 50% brightness.
I usually use my phone at around 40% brightness. Hoping it doesn't get worse.

I always wondered why someone asked me to add a blank or transparent Navbar to my Amazed Navbar theme, now I know. The navbar is there and def no chance of screen burn in LOL.

Archangel said:
I always wondered why someone asked me to add a blank or transparent Navbar to my Amazed Navbar theme, now I know. The navbar is there and def no chance of screen burn in LOL.
Click to expand...
Click to collapse
LOL nice. It actually has more to do with Google's ingenious idea of making the navbar/statusbar black vs some dynamic color or transparent. That causes uneven wear of the screen and burn-in occurs as a result.

https://android.gadgethacks.com/how...re-screen-real-estate-no-root-needed-0177297/
Would this work for my pixel 2 XL?
Sent from my Pixel 2 XL using Tapatalk

As fond of this device I am. I just checked and I've got the screen burn in as well. I've had mine since the 20th. This really is sad. I don't mind the panel and all the complaints people had with the blue hue when you tilt it. But this is simply unacceptable. I will be returning both of my devices

I've had mine since the 20th as well. I checked and I have the screen burn as well. Something like this can't be fixed after it has already happened, correct?

not defending the screen at all (sending mine back, not RMA, just return for money back because of the extreme blue shift), but i had the burn in yesterday when i checked (very faint but could see the bottom bar) and now this morning i rechecked first thing and i dont see it anymore...so again, might be a retention thing over a burn in thing. but still this panel is garbage.

bkdodger said:
Yup yup.. I'm running them and I use SystemUI tuner to auto hide navs when I wish.. Excellent [emoji1303]
Sent using Tapatalk
Click to expand...
Click to collapse
How do you do that?
Sent from my Pixel XL using Tapatalk

Cannot say that I like burn-in issues. But this is nothing new. Reported as an issue with Samsung S8 after a week...
https://android.gadgethacks.com/how...laxy-s8-prevent-from-happening-again-0177379/
Sent from my LG-D855 using Tapatalk

phyl0x said:
not defending the screen at all (sending mine back, not RMA, just return for money back because of the extreme blue shift), but i had the burn in yesterday when i checked (very faint but could see the bottom bar) and now this morning i rechecked first thing and i dont see it anymore...so again, might be a retention thing over a burn in thing. but still this panel is garbage.
Click to expand...
Click to collapse
I experienced the same thing. Last night using the grey screen image from Android Central, I noticed the burn in and then this morning using the black and red screen images from Android Central, there was no burn in. However, when I use the grey one again, the "image burn" is still there. Not sure why it comes up on some color screens and not others, and I dont know why Android Central switched the test image. I guess we wait on Google.

Verizon Agent store employee here: Just wanted to give some feedback about burn in. I set up the demo units at my store four days ago on Friday. Both the Pixel 2 XL and the Pixel 2 have slight burn in at the navigation bar already. The buttons can't be seen, but there is a horizontal line across where the navbar would start.
Granted, these phones run 12 hours a day with the screen on and are always charging, but they are on 50% brightness and operate with night mode turned on (lowest intensity) to lessen the speed burn-in takes hold. No OLED panels survive demo modes on any manufacturer! Keep this in mind when going to a retail location to check out phones.
I hope that those experiencing burn-in with normal use are a legitimate few. I pre-ordered a Pixel 2 XL despite having a distaste for LG's build quality with phones. I've come around in the last couple years because of their improvements. Don't let me down, LG!

Andebad said:
https://android.gadgethacks.com/how...re-screen-real-estate-no-root-needed-0177297/
Would this work for my pixel 2 XL?
Click to expand...
Click to collapse
Probably. I just tried it on my XL and it works.
Sent from my Pixel XL using XDA Labs

Nav Bar Color Changing Apps & Long Term Burn-In Prevention

We're approaching 2 months since the first Pixel 2 XL's started getting into our hands. We all know there were initial reports of premature screen burn-in from the nav bar on this phone. So immediate prevention tactics started to pop-up, including enabling immersive mode, disabling the nav bar with a build.prop edit, or using custom apps like Navbar Apps and Custom Navigation and Simple Control to simply eliminate all instances of the black nav bar from showing up and replacing it with other color variations such as green, red, white, yellow, blue etc..
I've personally gone the route of disabling the nav bar entirely with a build.prop edit and using Pie Control for my navigation needs. I'm now over a month of usage with the phone on this setup and have absolutely no burn-in. But I must admit that I would prefer the static nav bar because some apps simply won't fill the entire screen, leaving a black bar where the nav bar would normally be and occasionally I'll get stuck in an app because Pie Control won't activate the nav bar pop-out.
However, I will only go back to the static nav bar if I can be 100% sure I can avoid burn-in through the use of a custom nav bar coloring app, listed above. So, with that in mind, I'm looking for the input of others who have used something like Navbar apps to change their nav bar color to be anything but black. How long have you been using a setup like this and do you have any burn-in?

I've been using navbar apps since having gotten this phone. It's been about two months now-ish. I can barely, and by barely I mean BARELY, see the remnants of the navbar line at the bottom. I can't see any of the buttons in it though, I can just barely see the line. Ultimately however, like many have said before, you pretty much have to jump through hoops to see it. It never shows up when I'm viewing photos or watching videos or anything like that. So, even if it's BARELY there when viewing a solid gray wallpaper, it doesn't really bother me much. Also, this could just be image retention. I haven't watch a solid-color, full-screen wallpaper for 10 to 15 minutes to see if it eventually faded away.
Sent from my Pixel 2 XL using XDA Labs

sn0warmy said:
....I will only go back to the static nav bar if I can be 100% sure I can avoid burn-in ....
Click to expand...
Click to collapse
Cannot be guaranteed ever, using an amoled screen.

uicnren said:
Cannot be guaranteed ever, using an amoled screen.
Click to expand...
Click to collapse
Truth.
Sent from my Pixel 2 XL using XDA Labs

sharkie405 said:
I've been using navbar apps since having gotten this phone. It's been about two months now-ish. I've attached a screenshot with a solid grey wallpapers set as the background. I can barely, and by barely I mean BARELY, see the remnants of the navbar line at the bottom. I can't see any of the buttons in it though, I can just barely see the line. Ultimately however, like many have said before, you pretty much have to jump through hoops to see it. It never shows up when I'm viewing photos or watching videos or anything like that. So, even if it's BARELY there when viewing a wallpaper like this, it doesn't really bother me much. Also, this could just be image retention. I didn't watch the wallpaper for 10 to 15 minutes to see if it eventually faded away.
Click to expand...
Click to collapse
You expect us to see burn-in/image retention on a screenshot?

I believe Google is doing more than enough for this overblown issue. They've already update the nav bar to dim, and are slowly changing Google apps to white and gray reversing the colors. Personally I'm happy everyone lost their $#!+ over this as we are finally getting another color for the nav bar than the black we've been looking at for years.

mkouk said:
You expect us to see burn-in/image retention on a screenshot?
Click to expand...
Click to collapse
Oh, I didn't realize that you couldn't. Oh well. I'm certainly not going through all the hassle of taking a photo with some other device and all that.
Sent from my Pixel 2 XL using XDA Labs

uicnren said:
Cannot be guaranteed ever, using an amoled screen.
Click to expand...
Click to collapse
Agreed, but if you can take actions to prevent it for as long as possible, why not do that?
AndrasLOHF said:
I believe Google is doing more than enough for this overblown issue. They've already update the nav bar to dim, and are slowly changing Google apps to white and gray reversing the colors. Personally I'm happy everyone lost their $#!+ over this as we are finally getting another color for the nav bar than the black we've been looking at for years.
Click to expand...
Click to collapse
I'll agree that the blue shift is definitely an overblown issue but this premature burn-in is not. My 6 month old S8 doesn't have any sign of it and neither does my 2 month old V30. At this point it's no secret that the 2 XL screen is subpar and for the price point that is a serious issue and is not overblown. Don't get me wrong, it's great that the Google apps are being updated. But honestly, what percentage of the apps you use for long periods on daily basis are Google created apps? In my case it's a small percentage. It will be a while (if ever) that all Play Store apps eliminate the black nav bar with white buttons. I'm not waiting around for that.
I don't mean to create a big argument over the burn-in issue. There are already plenty of threads about it. The moral of the story is that sharkie's post alone is enough for me to stick with disabling the nav-bar by editing the build.prop and using pop-out pie controls. I'm over a month with the phone and absolutely no burn-in with this method so I'll continue to stick with it. Minimal or not, if I can avoid it for as long as possible, I will.

sn0warmy said:
Agreed, but if you can take actions to prevent it for as long as possible, why not do that?
Click to expand...
Click to collapse
Because, I buy a device to work for me, not the other way around.
If I need to take precautions, then the device would be returned, regardless of price.
If you are willing to compromise how you use the device, then thats fine, more power to you, I personally won't.
Just out of curiosity, after the first couple of weeks the phone was out, how many posts/blogs/articles about burn-in have you seen since then?

uicnren said:
Because, I buy a device to work for me, not the other way around.
If I need to take precautions, then the device would be returned, regardless of price.
If you are willing to compromise how you use the device, then thats fine, more power to you, I personally won't.
Just out of curiosity, after the first couple of weeks the phone was out, how many posts/blogs/articles about burn-in have you seen since then?
Today 10:20 AM
Click to expand...
Click to collapse
Fair points. Little to no posts/blogs/articles after the first couple of weeks. Part of that could be due to the topic already being covered enough and any additional coverage would just be kicking a dead horse. But it could also just be that people stopped caring.
Admittedly, I'd prefer to not have to utilize a work-around, which I mentioned in my first post. But if I can prevent it with a slight compromise (which also gives me some more screen real estate) then I'll continue to do so.

sn0warmy said:
...Part of that could be due to the topic already being covered enough and any additional coverage would just be kicking a dead horse. But it could also just be that people stopped caring...
Click to expand...
Click to collapse
Or maybe its just not an issue anymore?
Personally with ALL of the talk about it, I only saw about 7 or 8 (unfortunately they seemed to be popular bloggers/vloggers) actual individual people who actually had burn-in, and a few here on XDA who may also have said they had it. The rest were just parroting, or simply adding fuel to the fire (or blogging about it to garner clicks).
Anecdotal evidence to say the least, but to me, thats an insanely small number that actually had the issue.
Personally I saw many more posts that people did NOT have it, than I did that DID/DO have it.
I think it is funny however, while talking about this, just haw many people who said it was bad because it was a $1000 phone, but they could look past it, if it was $500, which to me is insane, bad is bad!

uicnren said:
Or maybe its just not an issue anymore?
Personally with ALL of the talk about it, I only saw about 7 or 8 (unfortunately they seemed to be popular bloggers/vloggers) actual individual people who actually had burn-in, and a few here on XDA who may also have said they had it. The rest were just parroting, or simply adding fuel to the fire (or blogging about it to garner clicks).
Anecdotal evidence to say the least, but to me, thats an insanely small number that actually had the issue.
Personally I saw many more posts that people did NOT have it, than I did that DID/DO have it.
I think it is funny however, while talking about this, just haw many people who said it was bad because it was a $1000 phone, but they could look past it, if it was $500, which to me is insane, bad is bad!
Click to expand...
Click to collapse
In addition, I think it's only fair to point out that I've given exactly 0% of my time in trying to avoid burn-in with the status bar area which has plenty of instances of black background and white icons. However, in looking closely for screen burn-in on the screen, I've found absolutely no burn-in in the status bar area either, indicating that what you are saying could be completely true in that it really is not an issue. Now I'm starting to wonder if some people really did just get unlucky with bad screens.
Maybe at some point I'll stop caring and just switch back to stock nav bar and see what happens, but for now I'll stick with Pie Controls.

sn0warmy said:
In addition, I think it's only fair to point out that I've given exactly 0% of my time in trying to avoid burn-in with the status bar area which has plenty of instances of black background and white icons. However, in looking closely for screen burn-in on the screen, I've found absolutely no burn-in in the status bar area either, indicating that what you are saying could be completely true in that it really is not an issue. Now I'm starting to wonder if some people really did just get unlucky with bad screens.
Maybe at some point I'll stop caring and just switch back to stock nav bar and see what happens, but for now I'll stick with Pie Controls.
Click to expand...
Click to collapse
Im not saying its not an issue at all, clearly there are some people who did have it. In my small view of the over-all, it appears to me that it was mostly people who got early review units, and an even smaller number of the general public.
Maybe they got units that were used for burn-in testing? I have no clue if thats the case, but there were people who actually got phones with no OS installed at all, so its not entirely out of the realm of possibility.
I haven't seen anything new to indicate to me that its an on-going issue, thats more my point Im trying to make. After the initial reports, its gone silent.
Anyway, enjoy your device!

With regard to viewing navbar apps as a workaround, I didn't install it as a workaround or preventive measure, I installed it because I like having a dynamic navbar. And every device I've had before this I would always modify the framework-res.apk to have the dynamic navbar more naturally, but we're not yet able to mod framework-res.apk on the pixel 2 XL, so I had to settle for a third party app. Dynamic navbar has always looks cooler, but it is especially looks cool on the pixel 2XL because it allows the bottom curve of the screen to be seen, whereas having a black navbar makes the screen look like it's not curved at the bottom. Just my two cents.
Sent from my Pixel 2 XL using XDA Labs

Buying Google Pixel 2 XL in 03\2018

So it's time to change my old phone to the new one. I want to buy Pixel 2 XL but I'm so frightened because this phone has launched with a poor screen quality. Did someone buy this phone in february or in march and could tell me something about Pixel 2's blue-shift, burn-in or grain?

I think the screen it's good I don't have a lot of blue shift, but I think you must pay attention to the 4gb of ram , I have 4 mobiles and 3 of them are 4 and 3 GB of ram and they suffer a lot on multitasking.
And now I have a one plus 5t with 6gb of ram and that's much better.
By the phones are , Google pixel 2 xl, s8+ , ipx .
But the rest you're be good with pixel 2 XL , speed , fast updates, by the way the android P its right on the corner

I purchased the pixel 2 xl 15 days ago and yes, it has blue shift, but no more defects or burn in. My aunt has a S8 and I'd recommend the pixel 2 over the S8.

In my opinion, blue shift is overrated. Burn in issues seemed to be solved. Only the first batch at launch seem to be affected. Plus Google gives you a 2 year warranty so that should give you some peace of mind.
My girlfriend has the iPhone X and my roommate has the Note8. I highly recommend the Pixel 2 XL over both the phones.

Goog1e Phone said:
In my opinion, blue shift is overrated. Burn in issues seemed to be solved. Only the first batch at launch seem to be affected. Plus Google gives you a 2 year warranty so that should give you some peace of mind.
My girlfriend has the iPhone X and my roommate has the Note8. I highly recommend the Pixel 2 XL over both the phones.
Click to expand...
Click to collapse
Agreed about the blue shift. Way over criticized. I only notice it when... I read someone post something about it then I go look, say to myself, yep, its there, then continue on like nothing at all.
However, if I was buying a phone right now, I would hold off until I can hold the S9+ in my hands. With most sites saying its just a refreshed S8+ I would prolly pass and stay with Pixel.

This phone is top notch. Switched from the S8+. No looking back.

I'll weigh in:
I just got mine last week (third week of Feb '18) via a Best Buy deal. The phone was built in Oct of '17. I was coming from a Note5 which I really loved.
Lots of things to like, a few things to niggle naggle about and a few things to really hate.
Likes:
Oreo 8.1+
Squeeze Assistant
Fingerprint reader gestures
Google Lens - It's amazing.
Camera. Just wow.
Lots of things you can customize without root (via ADB)... You can move the nav buttons around, etc...
Battery life is simply great. I get 4+ hours of screen time and can go 8+ hours while sleeping and only loose a percentage or two. It's quite amazing actually.
Dislikes:
Not a fan of the fingerprint reader on the back... to use it, you always have to pick up the phone... on other models where the reader is on the front, you can unlock the phone while it's flat on the table or work desk or whatever. Having it on the back does have some upsides though... so this one isn't a big deal.
Not a fan of the power button and volume keys all being on the same side and so close together... I find myself pressing one when I mean the other.
Rounded corners on the screens... seems like a good idea aesthetically but you actually loose a fair amount of real estate... for example, the status bar icons are moved in a fair amount to compensate for the rounded corners so you get a lot of black space to the left and right of the ends in the status bar... I would never sacrifice function for form like that. Dumb.
Blue shift. It's there... not a big deal but it's there.
Hate:
Extremely long charging times. Just to go from 90 to 100% is like an hour++. This is in NO way a quick charging phone.
No charging LED indicator. Boo. I did load an app for that but Boo.
No wireless charging. Boo and boo.
Double Hate:
Screen protectors are a nightmare with this device. I've never had such issues finding decent, inexpensive protector that doesn't curl, bubble, etc... and I can't find any quality tempered glass protectors. There are a couple liquid adhesive protectors out there but they cost 1 arm and 1 leg. Really?
I'm really hoping the charging time issue can be fixed in a future OS update. It seems that this started happening after the Feb '18 update. We'll see.

I was going to give mine to try an iPhone X and then to come back to pixel but i have felt in love with this device.. Blue shift exists a little bit but I had forget that issue.. I agree with the charging time that sucks from 90-100% but overall it's an fantastic device.. On mine i have deleted nav bar, i use only gestures and its a pleasure all this huge screen with these nice rounded corners..

Jinthegodstyle said:
I was going to give mine to try an iPhone X and then to come back to pixel but i have felt in love with this device.. Blue shift exists a little bit but I had forget that issue.. I agree with the charging time that sucks from 90-100% but overall it's an fantastic device.. On mine i have deleted nav bar, i use only gestures and its a pleasure all this huge screen with these nice rounded corners..
Click to expand...
Click to collapse
Can you give some details on your nav bar deletion decision? Do you have to root for that? What launcher, Nova? How to you get your recents, back, home functionality and map them to gestures?

simpsonr said:
Can you give some details on your nav bar deletion decision? Do you have to root for that? What launcher, Nova? How to you get your recents, back, home functionality and map them to gestures?
UPDATE: Oh, I guess in Nova you can just turn the nav bar off. Will it allow for all the proper gestures for recents, back, home?
Click to expand...
Click to collapse
Yes I am rooted. I am using nova launcher but it doesn't matter. I used all in one gestures app from play store. The nav bar hide automatically if you don't use it. You can set it on premesive mode threw app. But now i have deleted at all nav bar with an command on build editor and i use only gestures.
Here I made a video month ago how I had it and how will work. (now it's totally different )
https://youtu.be/BA7jey09SXw

Jinthegodstyle said:
Yes I am rooted. I am using nova launcher but it doesn't matter. I used all in one gestures app from play store. The nav bar hide automatically if you don't use it. You can set it on premesive mode threw app. But now i have deleted at all nav bar with an command on build editor and i use only gestures.
Here I made a video month ago how I had it and how will work. (now it's totally different )
https://youtu.be/BA7jey09SXw
Click to expand...
Click to collapse
Thx!

I purchased mine 3 weeks ago, it was produced in November 2017, and the screen doesn't have any of all the issues reported right and left.
It has a very slight blue tint maybe when you look at it at an angle... but you know what? My Galaxy S7 edge has it too. AMOLED displays HAVE blue shift, no technology is perfect.
I'm pretty happy with mine. I'm far from being your typical Google/Nexus/Pixel apologist, but after having Samsung flagship phones for years, I can honestly say the Pixel 2 XL is the best phone I've ever owned :good:
It doesn't have all the bells and whistles a Galaxy or Note has, but it works so great, without any issue. Everything with this phone feels silky smooth, without a single dropped frame. Everything you try to run looks "effortless" and easy for the Pixel. I'm amazed by that phone

simpsonr said:
Can you give some details on your nav bar deletion decision? Do you have to root for that? What launcher, Nova? How to you get your recents, back, home functionality and map them to gestures?
Click to expand...
Click to collapse
You don't have to root to get rid of the nav bar. There is a Substratum theme that changes the nav bar to any size you want including 0. I found it here on XDA. I'll see if I can find it and link to it when I get home.
*edit
Here is a link for the nav bar height
https://forum.xda-developers.com/ne...-height-changer-android-nougat-t3447956/page1
and here is one I use to fix the lock screen swipe issue
https://www.xda-developers.com/fix-lock-screen-swipe-gesture-issues-android-81-oreo/

I just sold my 7 plus and received my pixel 2 xl yesterday. The blue shift isn't bad, it's only noticable to the person on the side of you looking at your screen. Screen quality doesn't seem bad but colors may be dull to some. There is a Oreo colorizer app that will force the display in wide color gamut mode which richens up the color. Google does offer a new vivid saturated display mode but that app works way better. Only thing I don't like is how Snapchat looks like poo.. which it does on every Android but yeah.. this is probably the best camera quality you will get on Snapchat Android due to visual core enhancing the photos which does a pretty damn good job!
On a cold rainy cloudy dark Washington day, camera doesn't look as nice as what my iPhone 7 plus would've took with it's camera..