One of the reasons Android Auto and CarPlay have become so popular is the lazy software efforts that carmakers have long been satisfied with.
On the one hand, users were happy to get access to top-notch navigation, such as Google Maps. On the other hand, carmakers saw the debut of Android Auto and CarPlay as an opportunity to reduce investments in software, giving in the infotainment to Google and Apple, something that many companies are now trying to undo.
However, returning to the OEM software available in the car is sometimes the only workaround. And a new bug plaguing Android Auto as of this week shows why.
“Oops, something went wrong.”
Photo: Bogdan Popa/autoevolution
A trending post on Google’s forums includes all the details about the bug that seems to wreak havoc on Android Auto today.
A recent update broke down voice commands, causing Google Assistant to be unable to process any requests. When users touch the microphone button or wake up Google Assistant with the dedicated phrase, Google Assistant launches correctly but fails to listen to the voice command.
It shows an error saying, “Oops, something went wrong,” with the animation going away to indicate that Google Assistant no longer listens for voice input.
The problem was first reported on February 1 but has since become more widespread, with tens of users confirming on the forums that they also encounter the same problem.
Users claim voice commands on the mobile device continue to work correctly, but the smartphone must not be connected to the infotainment system. Using Google Assistant without Android Auto running on the screen works as expected.
How to fix the “Oops, something went wrong” error
Photo: Bogdan Popa/autoevolution
Users who turned to Google’s forums to report the problem claim they’ve tried everything, from deleting the cache and the data to reinstalling Android Auto. They say nothing worked, as Google Assistant is still broken if the mobile device is connected to the infotainment unit.
The connection type doesn’t make a difference, as the error plagues Android Auto wired and wireless. Changing cables doesn’t help, as it’s obvious this isn’t a connection error but a glitch introduced by a recent app update.
While most users blame Android Auto for the voice command problem, the culprit is likely the Google app.
The Google app powers the voice command support on Android and Android Auto, so if Google ships a broken update, Google Assistant can be impacted on one or both platforms. Android Auto seems to be exclusively affected this time.
The workaround comes down to removing Google app updates. You can uninstall the latest versions from the Settings menu on your Android device. Make sure you don’t install newer versions, as once you update the Google app, the bug returns to Android Auto. Someone on Google’s forums confirmed this fix works, though they also explained that they configured voice commands from scratch and blocked automatic updates.
Google has already started an investigation, but it’s too early to tell when a patch could ship. However, considering the Google app receives updates regularly, it shouldn’t take more than a few days until the search giant releases a new version.
Going back to the OEM software
Photo: Bogdan Popa/autoevolution
Voice commands are integral to the experience behind the wheel, allowing users to interact with their apps without looking at the screen. They’re a critical feature that substantially reduces distraction, so when voice commands break down, many users feel lost.
It’s why some Android Auto users whose cars came with pre-loaded voice commands decided to drop Google’s app and return to the OEM software. It’s not the most convenient solution, especially because the digital assistants developed by carmakers lack the advanced functionality of Google Assistant, but it’s the only way to control certain systems without touch input.
The error doesn’t seem to be related to the Android Auto version installed on your device, so updating to the latest build doesn’t make a difference. The most recent Android Auto release is 11.3 beta, with the stable update likely to land in the coming days. However, if the Google app is responsible for the glitch, look for new releases in the coming days. If you have already enabled automatic updates on your device, the new Google app should be downloaded to the smartphone when it goes live.
A Google Community Specialist says they have already informed the Android Auto team about the error, and more bug information will be requested via email from the impacted users. You can join the conversation on Google’s forums on this page, and if you discover a fix, please share it with our readers using the comment box after the jump.
Alex Mitchell is your go-to expert for all things mobile. With a passion for the latest smartphones, apps, and mobile innovations, Alex provides in-depth reviews, insightful analyses, and breaking news about the ever-evolving world of mobile technology. Stay connected with Alex to navigate the fast-paced realm of mobile devices.
