Recently, some Android Auto users have found that voice commands aren’t working quite as they should, but it looks like a fix for the problem is now coming in an update.
As reported by 9to5Google, the problem is that Android Auto only forwarded voice commands to Google Maps and not to the user’s preferred navigation app (such as Waze). If you already have a navigation app running, Google Assistant should send your Android Auto voice commands to that app (or if it’s not running, the last one you used should go).
However, Google Maps seems to have hijacked these commands, with all requests directed to the ‘default’ app. Apparently it was possible to work around this by completely disabling Google Maps on your phone, but it’s not exactly ideal – just because you find Waze (or another app) preferable for driving in your area doesn’t stop you from preferring Google Maps for walking directions or finding the nearest burger joint.
Fortunately, 9to5Google reports that some users are finding that the version 15.13.46.28 update for the Google app points Google Assistant back in the right direction and makes things work as they should again.
Despite being owned by Google, Waze has some great features that mean people prefer it over Google Maps – like useful new driving alerts – and it’s a similar story when using other driving apps that should support voice commands. Confusion about which app is directing you halfway through isn’t exactly ideal, so to speak – so it’s good that a solution to this problem is coming soon.