Photo: Sony
An odd glitch hitting a number of Android Auto issues causes the Bluetooth connection to no longer work when the phone is plugged in before starting the engine.
As weird as that may sound, several users explain on Google’s forums that the whole thing happens when the typical routing isn’t used, meaning that every time they connect their phone to the car after turning on the engine everything is working correctly.
On the other hand, if they plug in their mobile devices and only then start the engine, the head unit displays an error message and asks for a passcode or PIN.
The issue seems to happen mostly on the Sony XAV-AX100 unit, so it’s not yet clear at this point if this is related to Android Auto itself or a compatibility issue with this specific HU.
However, users complain that Android Auto no longer activates the Bluetooth connection if the aforementioned order isn’t used, making it impossible to use the app in their cars.
“It seems to only pair and stay paired when the head unit is powered on, Bluetooth connects, and then the USB is connected. Any deviation from that order such as plugging in the USB before starting the head unit seems to cause pairing to be lost from the Pixel's perspective. The head unit seems to remember the device, but the Pixel won't let it reconnect automatically due to ‘a bad passcode or pin,’” someone explains on the linked Google thread.
For the time being, neither Google nor Sony came up with a workaround, so users are all alone in their struggle to resolve the glitch.
Someone says they managed to resolve the problem by clearing the cache of Android Auto and the other linked apps, but also by resetting all Bluetooth settings both on the mobile device and the head unit. Of course, this doesn’t mean the fix works for everybody, but since no other solution exists, it’s probably worth a shot anyway.
On the other hand, if they plug in their mobile devices and only then start the engine, the head unit displays an error message and asks for a passcode or PIN.
The issue seems to happen mostly on the Sony XAV-AX100 unit, so it’s not yet clear at this point if this is related to Android Auto itself or a compatibility issue with this specific HU.
However, users complain that Android Auto no longer activates the Bluetooth connection if the aforementioned order isn’t used, making it impossible to use the app in their cars.
“It seems to only pair and stay paired when the head unit is powered on, Bluetooth connects, and then the USB is connected. Any deviation from that order such as plugging in the USB before starting the head unit seems to cause pairing to be lost from the Pixel's perspective. The head unit seems to remember the device, but the Pixel won't let it reconnect automatically due to ‘a bad passcode or pin,’” someone explains on the linked Google thread.
For the time being, neither Google nor Sony came up with a workaround, so users are all alone in their struggle to resolve the glitch.
Someone says they managed to resolve the problem by clearing the cache of Android Auto and the other linked apps, but also by resetting all Bluetooth settings both on the mobile device and the head unit. Of course, this doesn’t mean the fix works for everybody, but since no other solution exists, it’s probably worth a shot anyway.
Google News