New Pixel 10 screens are freezing with bizarre 'snowy' static - what to do if you see it
Briefly

New Pixel 10 screens are freezing with bizarre 'snowy' static - what to do if you see it
"The Google Pixel 10 series has only been available for about two weeks, but users are already encountering some big glitches. Also: A week later with Google Pixel 10, I'm wondering why anyone should buy pricier flagships Over the past several days, users of both the Pixel 10 and the Pixel 10 Pro a "snow" that totally overtakes the screen. The best way to describe it is like the static that appeared on an older TV with no signal, except it's colorful."
"Google is investigating As scary as this issue looks (especially for a phone barely out of the box), most users say the problem eventually goes away on its own. The screen is responsive during and after the glitch, but your device is unusable while the screen is snowy. Also: I'm a longtime Pixel fan - but I'm skipping the latest model, and here's why Google hasn't issued a fix, but it is investigating the issue."
"Also: I tried every new AI feature on the Google Pixel 10 series - my thoughts as an AI expert Since it's not clear what's causing this issue, there isn't a way to resolve it right now other than restarting your device and hoping for the best. If you're experiencing the issue, it would be a good idea to even if your screen fixes itself. You can reach them through your phone's settings app"
Pixel 10 and Pixel 10 Pro devices are experiencing a colorful "snow" glitch that overtakes the screen like static on an old TV. The screen remains responsive during and after the glitch, but the device is unusable while the display is snowy. Most reports indicate the problem eventually resolves on its own. Google is investigating the issue but has not issued a fix. The Pixel 8 Pro experienced similar launch problems that prompted replacement devices. No definitive cause is known; current advice is to restart the phone and contact Google support through the phone's Settings if the issue occurs.
Read at ZDNET
Unable to calculate read time
[
|
]