autoevolution
 

We Should All Help Google Fix This Nerve-Racking Android Auto Glitch

Google says it needs users' help to fix this error 15 photos
Photo: Bogdan Popa/autoevolution/Google
Android Auto CoolwalkAndroid Auto CoolwalkAndroid Auto CoolwalkAndroid Auto CoolwalkAndroid Auto CoolwalkAndroid Auto CoolwalkAndroid Auto CoolwalkAndroid Auto CoolwalkWaze on CarPlayWaze on CarPlayWaze on CarPlayWaze on CarPlayWaze on CarPlayWaze on CarPlay
One of the main reasons I use Android Auto in my car is to handle phone calls, as I can see caller information, end the conversation, put it on hold, or dial a new number from the dashboard screen.
But as many long-time Android Auto users certainly know already, phone calls on Android Auto are a huge mess, as they occasionally malfunction for no reason.

Users who took to Google's forums to report an issue claim the phone call switches from the car's stereo system to the mobile device repeatedly. The bug appeared in April and has been occurring ever since, with user reports claiming the problem affects all types of calls, including phone calls and Microsoft Teams calls.

The weird behavior typically comes down to the phone call disconnecting from the car's stereo system and switching back to the mobile device. After a few seconds, the call returned to the vehicle, suggesting it reconnected to Bluetooth.

Users explain that phone calls work correctly when Android Auto isn't connected, regardless of the car model or the phone brand. They believe an app update introduced the glitch, but no further information on what version causes this behavior is available.

In the meantime, Google has already started an investigation, but the company needs additional details before developing a fix.

A member of the Android Auto team posted on the forums earlier this week to ask users to contribute with phone logs, as the developers must determine when and how the phone call disconnecting occurs.

It's too early to tell when a potential fix could roll out, considering Google is still investigating the bug. However, users should keep Android Auto up-to-date, as Google doesn’t typically announce bug fixes in new app versions.

If an Android Auto update is responsible for the glitch, downgrading to an earlier version could help. The first stable version shipped in April was Android Auto 9.1, so any other older build should help you determine if an update is the culprit. You can find all Android Auto APK installers on this page, but make sure you configure your device correctly. Android must allow the app installation from third-party sources – by default, the operating system blocks other sources and uses the Google Play Store as the only whitelisted app repository.

Google has recently released the first Android Auto 10 beta build, with the rollout to production devices projected to begin later this month. The new version doesn't address the phone call issue, so the investigation must continue until a full fix goes live.

You can join the conversation and send your phone logs to Google using the discussion on the company's forums, but keep in mind that installing beta builds is not recommended on your primary device. Beta builds typically have an increased likelihood of bugs, potentially causing other problems in Android Auto.
If you liked the article, please follow us:  Google News icon Google News Youtube Instagram
About the author: Bogdan Popa
Bogdan Popa profile photo

Bogdan keeps an eye on how technology is taking over the car world. His long-term goals are buying an 18-wheeler because he needs more space for his kid’s toys, and convincing Google and Apple that Android Auto and CarPlay deserve at least as much attention as their phones.
Full profile

 

Would you like AUTOEVOLUTION to send you notifications?

You will only receive our top stories