Google Pixel and Pixel XL 2

i like my hauwei watch, stainless with mesh band. the original not the new one. but i think the Apple watch looks like a toy, not a fan of the square shape.

I have the same one, got it last year for Christmas. I actually get compliments about it because at first glance, most people don't even realize its a smartwatch. I did go with the leather band, but I think I'll be swapping it out as it makes my arm hot.
 
For those freaking out about burn in; Android 8.1 dims the navigation bar buttons after about 2 seconds of not pressing them.
Axon 7 owners do not fear navigation button burn in, ZTE had the foresight to not light them at all:happy:
3:06
 
Speaking of color saturation, I found out some good info about how the Pixel 2 actually handles color spaces.

It turns out that one of Oreo's less talked-about features is that Google's trying to lay down the groundwork for better color management in Android, and everything defaults to the sRGB space unless an app specifically requests wide gamut like AdobeRGB or DCI-P3. Sensible, considering that sRGB is still the Internet standard, and wide-gamut PC monitors are still firmly within the realm of professionals and videophiles until HDR becomes mainstream.

The problem is that Google didn't update their apps alongside the OS to call for wide gamut yet, so you get problems like Google Camera and Google Photos not switching to the wider, more true-to-life gamuts, and instead defaulting down to sRGB. This would make for consistent viewing on other devices and the Internet in general, but if you actually wanted to show the vivid saturation you saw with your own eyeballs, being limited to sRGB would put a damper on that.

Nevertheless, it's a good move for the future regarding color accuracy and the big push for wider color spaces with HDR video, and it's something we really should've had this year.

Next up: ICC profile support. There's no reason they shouldn't be supporting something that Windows and Mac OS both supported back in the '90s, and it looks like Nougat broke X-Rite's ColorTRUE app every time it attempts to load a photo into its color-calibrated gallery, because while it runs on my Note 4 with Marshmallow 6.0.1, it just crashes on my Note 8 with 7.1.1 and that same Note 4 with LineageOS 14.1/7.1.2.

You want confirmed color accuracy, you get a colorimeter/spectrophotometer and make a profile. That goes double for OLED displays, since the blue subpixels wear out faster than red and green, skewing the white balance toward warmer yellows over time. If Android had ICC support, it wouldn't be limited to just one gallery app; the whole OS would be corrected, not just in terms of white balance, but the whole gamma ramp for each color channel.

EDIT: Why does the forum software insist on showing an entire Reddit post regardless of me trying to force it as a URL? The second one isn't so bad, but the first one turns it into even more of a WALL OF TEXT than my ramblings here did.
 
I hope in the new update, I would be able to remove the google search bar in pixel launcher.
 
Per the Google forums, the "ticking" noise in the Pixel 2's will be fixed via an update coming in a couple weeks. I just disabled NFC in the meantime.

I'm really liking the device now that I've gotten used to it. I dunno if much of that is attributable to the hardware (except the camera) but it's lightning quick and trouble-free.
 
I hope in the new update, I would be able to remove the google search bar in pixel launcher.

Same here. Either that or somehow connect it to Chrome so that the results for the bar and the browser line up. Half the time I'll use the search bar for something only to have my results seemingly go into the ether because it maintains its own list of searches/results/autocomplete/etc.
 
Just got an e-mail from Google support related to the clicking noise fix. I had contacted them via the in-phone chat support app. Coming from Motorola, Samsung, and Apple - I found this to be a breath of fresh air. No denials, "when we get around to it," or sugarcoating anything.
 
If the color issue is due to Oreo, then why does my nexus 6P still display colors just fine after the Oreo update? I hope my phone wasn't stolen out of the mail, it was supposed to be here last friday or saturday.
 
If the color issue is due to Oreo, then why does my nexus 6P still display colors just fine after the Oreo update?

I think that's nonsense. The Pixel 2 (smaller model) displays colors totally differently from the larger one. The larger one feels like the contrast is set at about 60% of every other phone on the market. The smaller model displays colors the same way my Moto X did. If Oreo is to blame, it's specific to that particular device.
 
I think that's nonsense. The Pixel 2 (smaller model) displays colors totally differently from the larger one. The larger one feels like the contrast is set at about 60% of every other phone on the market. The smaller model displays colors the same way my Moto X did. If Oreo is to blame, it's specific to that particular device.

Correct. The smaller Pixel has a Samsung panel, from what I understand, which is why it displays colors "correctly", like the Nexus 6P does. Incidentally, the Nexus 6P uses the same AMOLED panel as the Samsung Galaxy Note 5. :)
 
I for one welcome the LG panel if it happens to be better quality than Samsung's in other areas. My 2 XL replaced my GS7 that was just over a year old due to having a pink line down the right side of the screen. When I took it to AT&T the rep said, "Oh this is a common problem that we've seen with this phone." On Saturday night while I was at a PM5K concert I saw someone holding their phone up recording and it had a big, thick pink line down the same side of the screen and joked with my wife, "I bet that's a Samsung phone!"
 
I for one welcome the LG panel if it happens to be better quality than Samsung's in other areas. My 2 XL replaced my GS7 that was just over a year old due to having a pink line down the right side of the screen. When I took it to AT&T the rep said, "Oh this is a common problem that we've seen with this phone." On Saturday night while I was at a PM5K concert I saw someone holding their phone up recording and it had a big, thick pink line down the same side of the screen and joked with my wife, "I bet that's a Samsung phone!"

I highly doubt there is a single thing the LG P-OLED in its current form can do better than a Samsung panel. Having a pink line down the screen is even bound to happen to the LG panel or any AMOLED panel for that matter as well; it just means it's a defective screen, not that it's inherent to a Samsung panel.

http://www.androidpolice.com/2017/1...el-2-xl-display-issue-actively-investigating/
http://www.androidpolice.com/wp-content/uploads/2017/10/nexus2cee_1gn9Fww.jpg
 
Well, my Pixel 2 XL is on its way back to Google. Over the weekend while watching a YouTube video in full screen I noticed that the bottom (or right side in landscape) of my phone was a little bit lighter than the remainder of my screen. The navigation bar itself (not the buttons) was just starting to burn in. I ran videos on it for 30 min and it didn't go away, only got very slightly less noticeable. Normally I wouldn't care, but I started to notice the slight brightness difference during normal use and not when I was actually looking for it - so that automatically increased the impact it has on me. It wasn't bad by any means just yet, but I knew that it would only get worse from there so I decided to return the device while I was still within my return window. Such a shame because if it weren't for this (and the blue tint) the phone would be an easy keep for me, every other aspect of the phone is great.

Going to try the iPhone X and likely the OnePlus 5T. If Google revises the display (doubtful, but one can hope); I'll easily pick this phone right back up.
 
Well, my Pixel 2 XL is on its way back to Google. Over the weekend while watching a YouTube video in full screen I noticed that the bottom (or right side in landscape) of my phone was a little bit lighter than the remainder of my screen. The navigation bar itself (not the buttons) was just starting to burn in. I ran videos on it for 30 min and it didn't go away, only got very slightly less noticeable. Normally I wouldn't care, but I started to notice the slight brightness difference during normal use and not when I was actually looking for it - so that automatically increased the impact it has on me. It wasn't bad by any means just yet, but I knew that it would only get worse from there so I decided to return the device while I was still within my return window. Such a shame because if it weren't for this (and the blue tint) the phone would be an easy keep for me, every other aspect of the phone is great.

Going to try the iPhone X and likely the OnePlus 5T. If Google revises the display (doubtful, but one can hope); I'll easily pick this phone right back up.

Nice, did they happen to ask why you're returning the phone? I hope they get a considerable amount of returns for this and do something to fix it, even if it's lowering the price of the phone, because I'm sure I could completely live with it if it were reasonably priced to begin with.

I've noticed a bit of image retention (not burn-in) from the nav bar on my 6P while watching some videos, but it does go away for the most part after several mins. I can live with that on a phone I paid half as much for 18 months ago, but not on a $850+ phone that also has worse color shifting as well. Fortunately my 6P is still a great phone overall though, so I don't have much incentive to replace it anyways other than just for the sake of having a newer/faster phone. I might consider the 2 XL if there's any BF deals on it, but that's doubtful outside of Verizon (which I'm not on). Next phones on my radar are the Mate 10 and 5T I guess.
 
Once they "fix" the saturation on the Pixel 2 and if they every swap to a different screen, I'd consider the Pixel 2 XL to be the cream of the crop. I very specifically noted that it had an unsatisfactory screen (for a $1000 phone) in the comments section of the return form.
My concern with waiting on them to fix the screen is that by the time that happens, it might be time for the Pixel 3 to roll out. If they're doing these launches yearly, it might not even be worthwhile for them to care.
 
Nice, did they happen to ask why you're returning the phone? I hope they get a considerable amount of returns for this and do something to fix it, even if it's lowering the price of the phone, because I'm sure I could completely live with it if it were reasonably priced to begin with.

They require comments for defective items (which I marked mine as, don't care if Google claims that it is within line of other OLED panels). Tried to squeeze as much info as I could in those 300 characters they allot you.

I think Google might go with a different polarizer to eliminate or reduce the blue tint in a future revision - but I imagine that is as far as they'll go with display changes for the 2 XL. We'll likely see most display improvements with the Pixel 3 next year after LG spends the billions Google and Apple has invested in them to R&D their mobile OLED technology further.
 
To me the blue tint didn't matter at all. What did matter was the massive amount of motion blur and the weird smudgy look. Mine looked almost like it had fingerprints under the screen. You don't notice it all of the time, but in a dim room I was trying to wipe away fingerprints that weren't there. I've seen it called "halos" but to me it looked smudgy.
The motion blur was a bigger offender. To me it was like the first "HD" (aka 720p) projection LCD TV I ever got back in 2005. That's fine for value-priced phone, but that monster is the 2nd most expensive mainstream phone. To me, that's the thing I couldn't overlook. The burn-in thing compounds it.
 
To me the blue tint didn't matter at all. What did matter was the massive amount of motion blur and the weird smudgy look. Mine looked almost like it had fingerprints under the screen. You don't notice it all of the time, but in a dim room I was trying to wipe away fingerprints that weren't there. I've seen it called "halos" but to me it looked smudgy.
The motion blur was a bigger offender. To me it was like the first "HD" (aka 720p) projection LCD TV I ever got back in 2005. That's fine for value-priced phone, but that monster is the 2nd most expensive mainstream phone. To me, that's the thing I couldn't overlook. The burn-in thing compounds it.
Still have never seem this on mine at all
Very odd.
 
Just got my Black 64gig XL 2. I love this phone. I don't see any problems with the screen. The blue tint is there (meaning its noticable at extremely odd viewing angles but even then its not bad) but its also on my 6P. My two co workers interested in the phone also said the screen looks great and the colors are fine. I'm very impressed so far. I think the screen issues were blown out of proportion by early reviews and people want something to complain about.
 
I've been really happy with the smaller Pixel's screen. No motion blur, it's crystal clear, and the color scheme looks like what I'm used to. It also has the same camera as the larger model.
The caveat for it is that the screen is comparably tiny. It feels almost like going back to the iPhone 5 days. For a phone that's only about 15% smaller than the XL, the screen is about 1/3 smaller. Well, that and there's the "tick tock" noise whenever NFC is turned on...which it is by default. Luckily that has been acknowledged and a patch is on the way "in a few weeks."
 
Mine appears to have been lost in the mail or something. It was supposed to ship all the way from Lost Angeles to Northern San Diego and arrive on Friday, but it seems to have disappeared....
 
Mine appears to have been lost in the mail or something. It was supposed to ship all the way from Lost Angeles to Northern San Diego and arrive on Friday, but it seems to have disappeared....

Can't tell if this is supposed to be a pun or not...
 
Just got my new pixel 2 XL !!!
 

Attachments

  • 20171030_194316.jpg
    20171030_194316.jpg
    65 KB · Views: 31
  • 20171030_220303.jpg
    20171030_220303.jpg
    174.8 KB · Views: 30
That sucks. Guess you'll be un-getting your new Pixel 2 XL. Have you contacted Google? How fast for a replacement?
 
I was out all day long yesterday and got to sit around and use the phone for a good while. This is what the battery profile worked out to for me. I used it until it died.

Screenshot_20171031-111559.png Screenshot_20171031-111605.png

Edit: Also, had to power the phone back on after it died. Could see no evidence of burn-in at the bottom of the screen. That is the only time I ever see the area of the screen under the buttons.
 
Last edited:
That sucks. Guess you'll be un-getting your new Pixel 2 XL. Have you contacted Google? How fast for a replacement?


I purchased the phone on Project Fi and I have spoken with them many times. A hardware specialist is supposed to call me today in a few hours. (For whatever reason they wish to waste as much of my time as possible.) I'm starting to think that this may be a battery swelling issue due to the fact that it is working a lot better today after not being used or charged for many hours.
 
So much for preordering, I called google and they marked the order as stolen and they issued me a refund which will take a few days to clear. They did not have a replacement available to ship me, so I guess I have to join the waiting list and start the waiting over again. Ordered October 5th :mad:

On the bright side, if ontrack finds the phone I get a free pixel2 XL
 
Last edited:
Back
Top