Google suggests Android 8.0 downgrade for Pixel 2 multi-touch issue

If you remember, back in December last year, we highlighted an Android 8.1-induced Pixel 2 issue that – much to the dismay of gamers – broke the multi-touch feature. No, the problem hasn’t been resolved, and what we are about to reveal isn’t encouraging either.

A user revealed on Google’s issue tracking website that they got in touch with the company’s hardware team, and were informed that they are still investigating the problem. And as for the “best” work-around, the company is suggesting users to downgrade to Android 8.0.

Hey guys. Finally got through to Google’s Hardware team. Here’s the response:

Hello Samuel,

Thank you for the update. Also, upon looking more into this issue with multi touch. I have found that this issue is one we’re currently investigating, so it appears that your work-around of flashing the device to 8.0 would be the best resolution at this time. Google is committed to continually making improvements to our devices and regularly provides free software updates to customers – each update addresses concerns raised by customers like you, and includes improvements to the overall security of your device and data.

Please feel free to reply if you have further questions.

Thanks again for contacting Google Support!
Joe
The Google Support Team

That’s not good (to put it mildly). Adding to it, Google isn’t even providing a specific time-frame for the fix. For what it’s worth, another user updated on the same thread yesterday, saying Google Support has promised the fix will arrive “soon,” and asked them to wait for “next updates.”

I really hope this is fixed in the Feb 5th update. I talked to Google support about my options with this device if it is not fixed in the very near future, and they pretty much begged me to wait for the “next updates”. I assume this is in reference to the upcoming security patch. They wouldn’t tell me for sure it would be resolved, but “guaranteed” it would be soon. Soon isn’t really good enough in my opinion at this point, 2+ months have passed dealing with this bug. I don’t typically spend $800 on hardware to wait for the accompanying software function properly “soon”. I guess we will see what happens in a few days.

More Pixel 2 touch issues come to light

We stumbled upon another thread on Google Issue Tracker where Pixel 2 users have been complaining about swiping/scrolling issues with their units. Basically, reports say their units are incorrectly comprehending scrolls and swipes within apps.

I believe that there may be an issue with the touchscreen driver or software for the Pixel 2 XL. It seems like a touchscreen sensitivity issue. I have noticed an issue with vertical scrolling in apps (system or third-party, regardless of safe mode, restarting, or system resets, on multiple Pixel 2 XLs, clean screen, no screen protecter, from the Android 8.0 Nov update to the Android 8.1 January security update), where the hardware recognizes a diagonal swipe (as seen through input developer settings that show taps and pointer location), but reacts with a horizontal movement in the app.

This happens in the Google app (swipes back to the homescreen), in Google Chrome for Android (moves left to right instead of up and down) and in the Relay for Reddit app (swipes back to the home screen from the comments [option within app] or opens the menu [slides in from left with a horizontal swipe usually] from the home screen).

The following videos should give you a better idea of the problem:

More such user-shared videos can be found here and here.

Like those with the proximity sensor problem we highlighted yesterday, some users have also got their units RMAed over these scrolling/swiping problem. However, many say the replacement models also exhibit the same behavior. It’s worth mentioning issues with swipe gestures on lock screen and during calls are already known, but the one we’re highlighting now seem to be new.

That said, it’s highly likely that all these problems are related, as all are touch screen related and none of them have been resolved yet. We hope Google will fix them with a single update.

Stay connected with us on Twitter (@PiunikaWeb) to hear about all related developments as and when they occur