Photo: Google
If you’re struggling with voice commands on Android Auto, you certainly aren’t alone, as this has been one of the biggest problems with the app for a long time.
But more recently, users have come across sometime a little bit different and which seems to signal yet another glitch hitting the support for voice commands on Android Auto.
When turning to voice input to set Android Auto to “navigate to” a specific destination, the app no longer recognizes the command properly and instead responds with an “I think you are trying to navigate” message.
Android Auto thus fails to determine the address that users are trying to navigate to, and this has already been confirmed by several users in this Google support forum thread.
The good news is that Google is already looking into the whole thing, though for now, there’s absolutely no word on a potential fix that could be released to users.
“Thanks for reporting this issue. We've forwarded your issue to the rest of the team. We'll reach out to you if we need more information,” a member of the Android Auto team said.
Oddly enough, the issue only seems to affect Samsung devices that are used to power Android Auto in the car, and the generic workarounds don’t seem to make any difference at this point.
“If I enter the address manually then the navigation works as expected. I have rebooted the phone and tried uninstalling and reinstalled updates for Android Auto, but still get the same error. This is a new issue that popped up recently since I have been able to use the voice command ‘navigate to’ with my car in the past without issue,” one user explains.
A new version of Android Auto is projected to land in the coming days, but at this point, it’s very unlikely to bring a fix for this glitch.
When turning to voice input to set Android Auto to “navigate to” a specific destination, the app no longer recognizes the command properly and instead responds with an “I think you are trying to navigate” message.
Android Auto thus fails to determine the address that users are trying to navigate to, and this has already been confirmed by several users in this Google support forum thread.
The good news is that Google is already looking into the whole thing, though for now, there’s absolutely no word on a potential fix that could be released to users.
“Thanks for reporting this issue. We've forwarded your issue to the rest of the team. We'll reach out to you if we need more information,” a member of the Android Auto team said.
Oddly enough, the issue only seems to affect Samsung devices that are used to power Android Auto in the car, and the generic workarounds don’t seem to make any difference at this point.
“If I enter the address manually then the navigation works as expected. I have rebooted the phone and tried uninstalling and reinstalled updates for Android Auto, but still get the same error. This is a new issue that popped up recently since I have been able to use the voice command ‘navigate to’ with my car in the past without issue,” one user explains.
A new version of Android Auto is projected to land in the coming days, but at this point, it’s very unlikely to bring a fix for this glitch.
Google News