Photo: Bogdan Popa/autoevolution
Google has started the rollout of a new Android Auto version, and while the release notes have remained unchanged, it looks like the company has introduced a feature that should better be a bug.
Android Auto 11.7 skipped the beta phase and landed directly in the stable channel, meaning that it's now rolling in waves to production devices through the Google Play Store.
Fortunately, the APK installer allows everyone to download and install this update manually, skipping the automatic Play Store rollout that typically takes weeks to complete. Download the APK file, browse to its location, and tap the installer to begin the update. Follow the on-screen wizard to complete the installation.
Meanwhile, if you're looking for changes in Android Auto 11.7, our reader Jim spotted a controversial change that could eventually enforce Google Maps on Android Auto (I'm hearing antitrust bells if this is the intended behavior).
When sending a navigation command to Google Assistant on Android Auto 11.7, the voice request is processed correctly but by ignoring the application running on the screen. It means that even if you run another navigation app on Android Auto, such as Sygic's GPS Navigation, Google Assistant sends the command to Google Maps. It closes whatever app you have in focus and launches Google Assistant to run the request.
This behavior doesn't allow the user to stick with a different navigation app, enforcing Google Maps as the only navigation solution supported by Google Assistant on Android Auto. I strongly believe it's just a bug, possibly due to a change in Google Assistant, though it's uncanny to see it in the production channel. However, considering Android Auto 11.7 skipped the beta stage, such a bug making its way to the stable channel is less surprising.
The bug happened on a Samsung Galaxy S22+, which has already been updated to Android 14, and a RoadTop aftermarket unit. I installed Android Auto 11.7 on my Galaxy S22 Ultra but Google Assistant offers the old behavior when receiving navigation commands. This makes me think that this odd navigation change could be just a bug affecting certain devices, but it could also be a new feature rolling out in phases to users worldwide.
Google did not announce any changes in Android Auto 11.7, as the company typically doesn't comment on new app updates unless they include big new features (in which case it publishes a blog post without updated release notes).
We'll learn more about this mysterious change in the coming weeks when Google releases the next Android Auto beta. Based on Google's calendar, a new preview build should make its way to the beta program in the next couple of weeks, with a stable build to land by the end of the month.
Fortunately, the APK installer allows everyone to download and install this update manually, skipping the automatic Play Store rollout that typically takes weeks to complete. Download the APK file, browse to its location, and tap the installer to begin the update. Follow the on-screen wizard to complete the installation.
Meanwhile, if you're looking for changes in Android Auto 11.7, our reader Jim spotted a controversial change that could eventually enforce Google Maps on Android Auto (I'm hearing antitrust bells if this is the intended behavior).
When sending a navigation command to Google Assistant on Android Auto 11.7, the voice request is processed correctly but by ignoring the application running on the screen. It means that even if you run another navigation app on Android Auto, such as Sygic's GPS Navigation, Google Assistant sends the command to Google Maps. It closes whatever app you have in focus and launches Google Assistant to run the request.
This behavior doesn't allow the user to stick with a different navigation app, enforcing Google Maps as the only navigation solution supported by Google Assistant on Android Auto. I strongly believe it's just a bug, possibly due to a change in Google Assistant, though it's uncanny to see it in the production channel. However, considering Android Auto 11.7 skipped the beta stage, such a bug making its way to the stable channel is less surprising.
The bug happened on a Samsung Galaxy S22+, which has already been updated to Android 14, and a RoadTop aftermarket unit. I installed Android Auto 11.7 on my Galaxy S22 Ultra but Google Assistant offers the old behavior when receiving navigation commands. This makes me think that this odd navigation change could be just a bug affecting certain devices, but it could also be a new feature rolling out in phases to users worldwide.
Google did not announce any changes in Android Auto 11.7, as the company typically doesn't comment on new app updates unless they include big new features (in which case it publishes a blog post without updated release notes).
We'll learn more about this mysterious change in the coming weeks when Google releases the next Android Auto beta. Based on Google's calendar, a new preview build should make its way to the beta program in the next couple of weeks, with a stable build to land by the end of the month.
Google News