Downgrade to Android 8.0 to Temporarily Fix Multi-touch Issue on Pixel 2: Google

Google released its Pixel ii back in October final year, since then both the Pixel 2 and the Pixel 2 XL have experienced a number of bugs and hardware problems. While some issues were patched by the company with software updates, a few new ones were introduced when the devices were upgraded to Android viii.i Oreo.

According to client reports on Google's product forums, some Pixel 2 (not XL) users encountered a multi-touch issue upon upgrading their devices to Android eight.one Oreo. The multi-touch issue resulted in "erratic and rapid movement" while using two or more than fingers at the same fourth dimension. The consequence was first identified in December last year and since then Google has not been able to deliver a fix. Now, a Pixel 2 user who contacted the company has revealed that Google is advising users facing the trouble to downgrade to Android viii.0 Oreo till the company rolls out a permanent ready.

In an electronic mail, a member of Google support team wrote:

Thanks for the update. Besides upon looking more than into this event with multi touch. I accept plant that this issue is i nosotros're currently investigating, so it appears that your work-around of flashing the device to 8.0 would exist the best resolution at this fourth dimension. 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 lot, and includes improvements to the overall security of your device and data.

As of now, Google hasn't given a specific time frame for the fix and is advising a downgrade every bit a temporary fix. This leads united states of america to believe that the problem might not be fixed anytime soon. However, according to another user in the same thread who also contacted the visitor, the ready is coming "soon" and Google has advised the user to await for the "side by side updates."

The user wrote:

I really hope this is fixed in the Feb 5th update. I talked to Google back up about my options with this device if it is not fixed in the very near hereafter, and they pretty much begged me to expect for the "next updates". I presume this is in reference to the upcoming security patch. They wouldn't tell me for sure it would exist resolved, but "guaranteed" it would be soon.