Photo: Sony
As we reported earlier this week, some Android Auto users have come across a new problem when trying to launch the app in their cars, and it all seems to come down to the way the Bluetooth connection is initiated.
More specifically, many of those who noticed this unusual behavior claim that whenever they connect their phones to the car before actually starting the engine, the Bluetooth connection fails to be established, with Android Auto then no longer launching.
The problem is only happening for those using a Sony XAV-AX100 head unit in their cars. The phone model doesn’t seem to be making a difference, as the glitch has been reported on Samsung and Google’s very own Pixel phones.
In a response offered a few hours ago, Google confirmed it’s investigating the reports, but for the time being, there’s no ETA as to when a fix could get the go-ahead.
“Thank you for the all the feedback, we have forwarded the ‘bluetooth disconnect on Sony XAV-AX100’ to the team to investigate, we will share the update when it is available,” a member of the Android Auto team explained.
This is the good news. The bad news is that there’s no workaround available at this point other than following the classic routine when trying to launch Android Auto.
In other words, you need to first start the car, wait for the head unit to power on and the Bluetooth connection to be initiated and only then to actually connect the phone using the USB cable. If you follow these steps, Android Auto should then run correctly with no Bluetooth connection error to be encountered.
Some users claimed they are provided with a “Can’t connect to XAV-AX100 due to bad passcode or PIN” message when the connection fails, but if you stick with these steps, everything should run correctly and the error should no longer show up.
The problem is only happening for those using a Sony XAV-AX100 head unit in their cars. The phone model doesn’t seem to be making a difference, as the glitch has been reported on Samsung and Google’s very own Pixel phones.
In a response offered a few hours ago, Google confirmed it’s investigating the reports, but for the time being, there’s no ETA as to when a fix could get the go-ahead.
“Thank you for the all the feedback, we have forwarded the ‘bluetooth disconnect on Sony XAV-AX100’ to the team to investigate, we will share the update when it is available,” a member of the Android Auto team explained.
This is the good news. The bad news is that there’s no workaround available at this point other than following the classic routine when trying to launch Android Auto.
In other words, you need to first start the car, wait for the head unit to power on and the Bluetooth connection to be initiated and only then to actually connect the phone using the USB cable. If you follow these steps, Android Auto should then run correctly with no Bluetooth connection error to be encountered.
Some users claimed they are provided with a “Can’t connect to XAV-AX100 due to bad passcode or PIN” message when the connection fails, but if you stick with these steps, everything should run correctly and the error should no longer show up.
Google News