Some People Are Reporting Google's USB-C Headphone Adaptors Aren't Working

Kelley Robertson
December 20, 2017

Now a new problem has surfaced regarding the Pixel 2's included USB-C to 3.5mm headphone adapters.

Meanwhile, a YouTube posted by SertNeverdie SpeedForce showcases that there was a delay of about one to 1.5 seconds on Pixel 2 XL running Android 8.1 Oreo, while the other device unlocked nearly instantaneously.

It had been a couple weeks since we last heard about issues with Google's flagship phones, leading to wishful thinking that the worst of the Pixel 2 duo's dilemmas were finally behind them.

The new Google Pixel 2 and Pixel 2 XL have seen a plethora of problems ever since the devices went on sale.

Some people Pixel 2 and Pixel 2 XL owners are reporting that the supplied USB Type-C to 3.5 mm headphone jack adapter isn't working. According to multiple complaints over at Google's Product Forums, the phones fail to recognize the adapter or any pair of headphones connected to it, and simply continue to play media through the built-in speakers. "Am I missing something here?" said one of the user.

Notably, we didn't encounter fingerprint unlock delay in Pixel 2 XL unit post installing the Android 8.1 Oreo update. Google, on the other hand, suggested that users should restart their phones in safe mode to make sure that no other app is running in the background. On a related note, Pixel 2 users recently claimed that their handset's fingerprint sensor has become slow after the Android 8.1 Oreo update. The error is showing up even when the device is booted into safe mode so it's not any third-party app which is causing it.

Nearly more than 64 users are reporting that after the update the fingerprint scanner has been acting weirdly. Have you encountered any issues with Google Pixel 2 XL? If it is indeed a software problem, Google could just send out an OTA (over the air) software update to fix it.

In fact, Google official authority also came up with some steps to troubleshoot the bug, but that hasn't been working for these users. If you turn on the always on display (which consumers extra battery) to solve this issue.

Other reports by

Discuss This Article