[Update: fix incoming] Google confirms multiple Android Auto issues, including one that prevents service from launching

Update (March 10):

For what it’s worth Google has provided another update on the matter, and here’s what they have said:

Several factors (car, phone, USB cable, software, etc) affect the Android Auto connectivity issues reported here in the forum. Further, the solutions are complicated by the fact that different underlying issues can show similar symptoms that are difficult to tease apart. For example, the Android OS February security update resolved certain specific technical problems that eliminated the connectivity problems for some, but not all of you.

Several investigations remain ongoing for each category of the symptoms. Bug reports are always helpful for us understand the individual issues. We deeply appreciate those who filled in in this form and shared bug reports with us. If you are willing to help the investigation with your bug report, please let us know through the form. Please understand that we are not usually able to provide immediate resolution for individual cases.

It bears repeating that some users were able to resolve the issue by changing the USB cable with one of the recommended USB cables (or short USB cables under, say 12-18″ – we are especially interested in hearing about these cases), so please take a look if you haven’t, yet. Here’s another reference for USB connectivity.

Update (February 17):

Here’s a recent update on the story:

The Android Auto team is actively working with the Pixel and Android OS teams to address what appear to be multiple interrelated issues that exhibit similar outward symptoms

Regarding the “Android Auto intermittently fails to start” issue: As we announced earlier last month, a fix for one of the underlying issues went out in Android OS February security update.

• Some of you asked how to get the February security update. See here
• While the February security update did solve reported problems for some people, we are aware that other problems remain to be addressed. If you are willing to capture and share bug reports for this specific issue, please let us know here

Update (January 22):

The fix for Android Auto’s launch glitch will be rolling out in the upcoming monthly security update (should be the February one). For more information head here.

Original story:

Rife with bugs, Google’s smart driving companion – Android Auto – has had connectivity issues for quite some time now, be it related to Bluetooth or USB. While the company is already working on fixing at-least some the existing problems, a new one has popped up. What’s now coming to light is, Android Auto users are unable launch the service on their cars’ head units.

Take a look at how some of the users have explained the matter in question:

What’s relieving is that Google has officially acknowledged the problem this morning. A few hours back Yurrim (from the Android Auto team) took to the official help forum to inform the affected users that they are:

working with the Android OS team to get the fix out as soon as possible

Furthermore, she also updated that the company is also working to resolve the random reboots/disconnection issue, and suggested those affected to wait for the next update.

We are also actively working to address the issues like random reboots or disconnection. Please wait for the next update on this thread

Here’s the complete statement:

Note: Google is already investigating certain phone crash/reboot use cases involving Android Auto.

Currently, it’s not known how long will it take to fix the launch glitch. We hope the problem will be resolved sooner than later. Meanwhile, we’ll keep updating all related developments here, so keep watching this space.

Android Auto User Community

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