[ad_1]
One of the reasons Android Auto and CarPlay have become so popular is the lazy software approach that automakers have long been complacent with.
Photo: Bogdan Popa/autoevolution
About 10 years ago, users had no choice but to continue using poor navigation systems and applications provided by car manufacturers. So when Android Auto and CarPlay became widely available, everyone was eager to make the switch.
On the other hand, users were happy to have access to top-notch navigation such as Google Maps. Meanwhile, automakers saw the arrival of Android Auto and CarPlay as an opportunity to cut back on software investments and cede infotainment to Google and Apple, which many are now looking to cancel.
However, reverting to the OEM software available on your car may be 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 Forums has all the details about the bugs that seem to be wreaking havoc on Android Auto today.
A recent update stopped voice commands from working and Google Assistant was unable to process your requests. When a user touches her microphone button or launches her Google Assistant with a dedicated phrase, Google Assistant launches correctly but cannot hear voice commands.
You’ll see an “Oops, something went wrong” error and the animation will disappear, indicating that Google Assistant is no longer accepting voice input.
The issue was first reported on February 1st, but has since become more widespread, with dozens of users confirming on the forums that they are experiencing the same issue.
Users claim that voice commands on mobile devices continue to work properly, but without the need to connect the smartphone 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 reported the issue on Google’s forums claim to have tried everything from deleting cache and data to reinstalling Android Auto. They say that nothing worked, as Google Assistant still does not work if the mobile device is connected to the infotainment unit.
This error occurs with both wired and wireless Android Auto, so it makes no difference what type of connection you have. It’s clear that this is not a connection error, but a glitch introduced by a recent app update, so changing the cable won’t help.
While most users attribute voice command issues to Android Auto, the culprit is most likely the Google app.
Google apps are improving voice command support on Android and Android Auto, so if Google hands out a breaking update, Google Assistant could be affected on one or both platforms. It appears that only Android Auto is affected this time.
The workaround would be to remove the Google app update. Android device[設定]You can uninstall the latest version from the menu. Be careful not to install new versions of Google apps, as updating them will bring bugs back into Android Auto. Someone on the Google forums confirmed that this fix worked, but also explained that they had set up voice commands from the beginning and blocked automatic updates.
Google has already begun an investigation, but it’s too early to tell when a patch will be rolled out. However, considering that Google apps receive regular updates, it shouldn’t take more than a few days for the search giant to release a new version.
Return to OEM software
Photo: Bogdan Popa/autoevolution
Voice commands are integral to the behind-the-wheel experience, allowing users to interact with apps without looking at the screen. These are important features that greatly reduce distractions, so many users get lost when voice commands don’t work.
That’s why some Android Auto users with cars preloaded with voice commands have decided to ditch Google’s app and return to OEM software. This is not the most convenient solution, especially since the digital assistant developed by the car manufacturer does not have the advanced features of Google Assistant, but it is the only way to control certain systems without touch input.
This error doesn’t seem to be related to the version of Android Auto installed on your device. So updating to the latest build won’t change anything. The latest Android Auto release is the 11.3 beta, with a stable update likely coming in the next few days. However, if a Google app is causing the glitch, look for a new release within the next few days. If you already have automatic updates enabled on your device, new Google apps will need to be downloaded to your phone when they’re published.
According to a Google Community Specialist, the Android Auto team has been notified of this error and affected users will be asked to provide further bug information via email. You can join the conversation on the Google Forums from this page. If you discover any fixes, please share them with our readers using the comment box after the jump.
[ad_2]
Source link
