Google will issue an update to fix unresponsive spots on the Pixel 2 XL’s touchscreen

Google will issue an update to fix unresponsive spots on the Pixel 2 XL’s touchscreen

7 years ago
Anonymous $ZOEEBQ1zf0

https://www.theverge.com/2017/11/13/16643504/google-update-pixel-2-xl-touch-screen

If you’re the owner of one of Google’s Pixel 2 XL devices, there’s more bad news: some users are reporting that the touchscreen is not responding to touches along the edge of the device, as reported by Phandroid. Users reported the issue on the Pixel User Community, and one user posted a video that showed the screen not responding when being tapped on the edge of the right-hand side. There was also some unresponsiveness on the left-hand side in the video.

One user further states: “I have it towards the right lower quadrant of the phone. It happens all the time while I'm trying to scroll while reading. Screen doesn't move just sits there. I have to tap repeatedly to get it too scroll.” A Google community manager responded to the concerns, writing that Google has been investigating and the issue will be addressed “in a future OTA update. Stay tuned.”

Google will issue an update to fix unresponsive spots on the Pixel 2 XL’s touchscreen

Nov 13, 2017, 4:18pm UTC
https://www.theverge.com/2017/11/13/16643504/google-update-pixel-2-xl-touch-screen >If you’re the owner of one of Google’s Pixel 2 XL devices, there’s more bad news: some users are reporting that the touchscreen is not responding to touches along the edge of the device, as reported by Phandroid. Users reported the issue on the Pixel User Community, and one user posted a video that showed the screen not responding when being tapped on the edge of the right-hand side. There was also some unresponsiveness on the left-hand side in the video. >One user further states: “I have it towards the right lower quadrant of the phone. It happens all the time while I'm trying to scroll while reading. Screen doesn't move just sits there. I have to tap repeatedly to get it too scroll.” A Google community manager responded to the concerns, writing that Google has been investigating and the issue will be addressed “in a future OTA update. Stay tuned.”