Google has launched an investigation into two main issues affecting Android Auto users

Google has launched an investigation into two main issues affecting Android Auto users

This is what’s happening right now with two serious problems happening after the most recent Android Auto updates. More specifically, a member of the Android Auto team has confirmed that two glitches reported by users have been forwarded for further investigation, so with a little luck, the upcoming app updates could include fixes as well. The first problem currently being dissected by the Android Auto team concerns a connectivity issue that showed up after the August update. Several users reported their phones are no longer detected when plugging in their phones in the car, so Android Auto no longer starts.

It’s challenging to be an Android Auto user these days, since network issues, software bugs, and features that no longer perform as intended might occur without any modifications on your end. The good news is that the Mountain View-based search giant is deeply devoted to enhancing the long-term stability and dependability of Android Auto, thus the firm normally investigates user-reported issues quickly. This doesn’t always imply that remedies will be delivered in a timely manner, but it’s still helpful to know that Google is looking into the faulty behaviour reported by users.

Highlights

  • The second is the odd behavior that we’ve reported earlier this week and which causes Android Auto to try to access the Secure Folder on Samsung devices. Users are therefore spammed with password requests that show up on their phones, and while this doesn’t prevent them from running Android Auto, it makes using the phone pretty much impossible because of the password prompts that show up on the screen over and over again. As said earlier, Google investigating these problems is no guarantee a fix is also on its way, so you’d better not hold your breath waiting for patches.

  • This is something that could normally indicate a bad cable or something else blocking the connection, but given the number of users reporting the same behavior after the early August update is increasing, Google has decided to look into it and see what exactly is happening.