Slashdot Mirror
Google Addresses Pixel 2 XL Display Issues, Pixel 2 Clicking Sounds With Software Updates (phonedog.com)
An anonymous reader quotes a report from PhoneDog: Google explains that it's been investigating reports about the Pixel 2 XL's display and that this has given it "confidence that [its] displays are as great as [it] hoped they would be". Still, Google will be taking steps to respond to consumer complaints about the screen. Google plans to issue a software update that'll add a "saturated" color mode that will make the colors more saturated and vibrant, but less accurate. This way, consumers that feel the Pixel 2 XL's screen is too muted can punch up the color saturation themselves.
When it comes to burn-in, Google says that its investigations of the Pixel 2 XL's display found that its "decay characteristics are comparable to OLED panels used in other premium smartphones." Google does plan to take further steps to fight burn-in, though, and it's testing an update that'll add a new fade-out of the navigation bar buttons after a short period of inactivity. Google is also working with more apps to use a light navigation bar to match the app's color scheme. Additionally, the update will reduce the maximum brightness of the Pixel 2 XL's screen by 50 nits, which Google says will be "virtually imperceptible". This will reduce load on the display with very little change on its observed brightness. This update will roll out to the Pixel 2 XL "in the next few weeks." Google also touched on the reports that some Pixel 2 phones are emitting some clicking sounds. The company plans to release an update in the coming weeks to address the issue, but until then, it says that Pixel 2 owners can turn off NFC by going into Settings > Connected Devices > NFC.
When it comes to burn-in, Google says that its investigations of the Pixel 2 XL's display found that its "decay characteristics are comparable to OLED panels used in other premium smartphones." Google does plan to take further steps to fight burn-in, though, and it's testing an update that'll add a new fade-out of the navigation bar buttons after a short period of inactivity. Google is also working with more apps to use a light navigation bar to match the app's color scheme. Additionally, the update will reduce the maximum brightness of the Pixel 2 XL's screen by 50 nits, which Google says will be "virtually imperceptible". This will reduce load on the display with very little change on its observed brightness. This update will roll out to the Pixel 2 XL "in the next few weeks." Google also touched on the reports that some Pixel 2 phones are emitting some clicking sounds. The company plans to release an update in the coming weeks to address the issue, but until then, it says that Pixel 2 owners can turn off NFC by going into Settings > Connected Devices > NFC.
Anyone who is willing to slash out a premium for a smartphone is getting an iPhone, or possibly a Samsung. I have a hard time believing Google is selling > 100k of these to actual customers who are not Google employees.
This sounds more like something that was tested as a "feature", not chosen as #1 by the consumer group that tested it, and now played back to the people as though this were a fix.
--
"It's a sign" - E. Corp
It would seem that the newer OLED panels suffer more from burn-in than LED. I'm glad this was brought up. I'll be refraining from upgrading to OLED until this sort of thing is made better or a newer technology supersedes it. More details here for those who are interested. The burn-in is not permanent but can occur when a static image is present in as little as 45 minutes. The ghosting is not permanent like older CRT and Plasma screens but it's annoying to have to run through steps to clear it up periodically.
We'll make great pets
Near field communication is what it is; and wikipedia knows more about it than I do: https://en.wikipedia.org/wiki/...
If you don't want to read that: It's a wireless communication protocol that requires very close proximity, used for mobile payment, and sometimes to transfer settings to new phones.
Why is that related to the clicking noise? Well my first guess of interference is thrown out by the fact that they can fix it in software; maybe someone can shed light on this?
What is NFC, and why is that related to clicking noises?
If you google on "TCP/IP Over Bongo Drums", you'll find that NFC on smartphones clicks because the phones are so small. If the Pixel was the size of a Bongo Drum, the NFC would sound like a Bongo Drum, but the test consumer target group wasn't very comfortable with Bongo Drum sized smartphones.
On the other hand, test consumer target groups have responded very positively to shoe phones, the only complaint being the whining emitted from Agent 13 hiding in the shoes.
Schroedinger's Brexit: The UK is both in and out of the EU at the same time!
The clicking noises are probably noise leaking into the audio amplifier from the modulation of the NFC radio. The frequency of the radio is out of hearing range but the modulation is not, and intermodulation can appear as low frequency noise. My iPhone lte radio has done the same thing to land lines on several occasions.
There seems to be a discrepancy between the title of the story, and the summary... The title says Google addressed, and the summary says Google plans to release. To me it sounds like they haven't addressed anything yet. Shouldn't we wait to see if their software "fix" fixes anything before claiming they've addressed the issue...
"Addressed" means "spoke about". As opposed to, "released fix for", which is what you seem to be looking for.
Apparently, the new Pixel 2 XL screens made by LG have a blue tint. No comments from Google about that problem.
In a time of universal deceit, telling the truth is a revolutionary act. George Orwell
When the iPhone X launched and they showed how you swipe up from the bottom of the screen to get back to home, I thought it was a bit odd, but their decision to avoid onscreen buttons does look smart now they've switched to OLED. Will Android follow suit now that phones are converging on an all-screen front with no hardware buttons?
Apparently Google judged the burn-in on their displays in line with the industry despite problems being reported in the first few weeks where as industry standard is for the situation to be unnoticeable for several years.
Apparently the screen is fine but we'll make software changes to make the totally not problematic screen less likely to cause a problem which totally doesn't exist in the first place.
Apparently Google's answer to problems with display colours changing with viewing angles are a software update to make them more saturated?
Like what the heck? Why not just give customers the middle finger? At least there would be less reading involved.
Faraday cage protection case.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
How do I know that Apple is such a good citizen themselves? I am getting a new iPhone, not due to some loyalty or trust towards apple, but just the fact I have some paid apps that I don't want to purchase again, and still more apps are made for iOS then Android. Android Phones and the Pixel isn't necessarily a bad phone.
Don't worry there are plenty of excuses of saying what your choice to get an iPhone is a good one vs getting an Android. Also if you want an Android you can get a bunch of different excuses to show why that is a better product.
I have seen a speed test comparison of the Pixel/2 vs the iPhone 8. The Pixel/2 held its own fairly well. It just failed when it needed to do some big processing job, But it seemed to be faster with smaller jobs, and loading data.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
Ooh! I really really want to implement TCP/IP Over Bongo Drums, but I don't think that's supported on Red Hat. If I install Ubuntu, are there third party bongo providers?
... you bought a phone from the company most known for its tracking and its ads and you want to disable tracking on a piece of hardware made by them? That's like buying an iPod and bitching about iTunes.
#DeleteFacebook
Every GSM phone has done this to any amplifier and speaker within a foot or so when the radio was active. Was super annoying and I'm glad it's gone with the shift to LTE.
Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
I'm sorry but the iPhone 8 and iPhone X are crap. The best phone on the market right now is the iPhone SE.
#DeleteFacebook
I've not used a Pixel device, but is there really a lack of a close app control? I can do that just fine on my Shield K1 tablet, but it is a software button - did they remove this because... reasons?
Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
WTF?
After another power cycle failed to clear it, I called Google, who immediately arranged for a replacement to be shipped (Thanks Google!). I really expected to hear something about some process I should go through to 'fix it' in some way. After another day of use, the problem HAS been reduced. In fact, if it were no worse that this in the first place I would likely not have called at all. Meanwhile, I'm charging it with power off to be safe.
Bottom line, I still like this phone very much. It's wonderfully fast, and easier on the hand than my Nexus 6 was. The prompt replacement just reinforces my already long and happy relationship with Google hardware.
It's not related to both noises being reported. I got a Pixel 2 XL and it's currently being RMAd for a dead pixel and for this reason. The noise is like a static, interference hiss that lasts about a second or so then goes away, and comes back again anywhere from 1-10 seconds later. It was not related to NFC for me, I disabled it and still had the issue. It seems to be more linked to wifi. My switch lights would all flash the moment the noise began, such as a broadcast packet being sent. I'm assuming it's actually a grounding or shielding issue, since the noise is very clearly something inducing a current in the speaker.
That being said, my phone also could not see GLONASS navigation satellites (other Pixel 2 XLs could), so I had more RF issues than just the earpiece noise.
It's not the cause of both interference related noises. Mine was not caused by NFC (disabling it did not fix it). It seemed instead to be linked to wifi activity, and was very clearly caused by current being induced in the speaker. My phone also was unable to receive GLONASS navigation signals (other Pixel 2 XLs could), so I had more RF issues than just the earpiece speaker. Anyway, it's being RMAd currently, we'll see if the next one has the same issues.
By not forgetting to wear your tinfoil hat darlin'
Of course, Android is the only major mobile OS that doesn't force you to use the vendor's services in order to use the OS. You don't even have to use the Google Play Store service. There is F-Droid and Amazon's App Store and you can sideload those stores as apk files using Bluetooth. Instead, you have to use Apple's App Store if you want to install any app on your device. But please, don't let facts get between you and your beliefs. Google is teh ebil, I luvs you Apple!!!111
> How do I know that Apple is such a good citizen themselves?
A perfectly valid question. But then what's this...
> Android Phones and the Pixel isn't necessarily a bad phone.
What does that have to do with your first statement?
The OP is saying you shouldn't buy a phone from a company who's primary business is tracking you. You can agree or disagree with that statement, but you went really non-linear there.
I'm sorry but the iPhone 8 and iPhone X are crap. The best phone on the market right now is the iPhone SE.
Not sure if you're being sarcastic, but there's only two choices if you want a current generation only choice. Because somewhere along the line, every Android phone manufacturer simply decided to concede that market to Apple.
---
DRM is like antifreeze, to the MPAA/RIAA it's sweet, to the consumers it's poison.
Somehow part of my post disappeared, and I didn't pay attention to the preview. It was supposed to read:
Not sure if you're being sarcastic, but there's only two choices if you want a current generation sub-5" smartphone: Sony's Xperia Compact line, or the iPhone. If you want a 4" smartphone that isn't a clamshell packaged pile of crap, permanently stuck on an outdated version of Android, the iPhone SE is your only choice. Because somewhere along the line, every Android phone manufacturer simply decided to concede that market to Apple.
---
DRM is like antifreeze, to the MPAA/RIAA it's sweet, to the consumers it's poison.
The iPhone SE is the perfect size and still has a headphone jack. It's two wins vs the iPhone 8 and the iPhone X.
#DeleteFacebook