Photo: Bogdan Popa/autoevolution/Google
Android Auto was designed with a clear goal: to make the experience behind the wheel as straightforward and convenient as possible.
Android Auto can connect and launch automatically depending on the car and the infotainment unit, requiring no user input.
The behavior makes sense from a convenient perspective, especially when using Android Auto wireless. The no-cord experience allows users to keep their phones in their pockets, so Android Auto can launch on the infotainment screen with drivers interacting with their mobile devices or the head unit.
However, a bug first reported in October last year has returned for no clear reason to haunt users and become more widespread. Android Auto wireless no longer launches automatically in cars where this behavior was supported, so drivers must conduct the complete process manually.
Posts on Google's forums reveal that users must establish the Bluetooth connection, wait for Android Auto wireless to detect the head unit, and then touch the icon on the home screen to launch the app.
The bug never received a fix, but it has now returned, likely after a recent Android Auto update. It's also more widespread, with several users confirming the failed automatic launch in posts on Google's forums. In every case, Android Auto requires manual interaction to launch when the wireless connection is enabled.
A member of the Android Auto team says the reports have already been forwarded to developers, promising an update when more information is available. In the meantime, users can't do much about this glitch, though if a recent Android Auto update causes the problem, the easiest workaround is to downgrade.
Installing an earlier version of Android Auto should restore the expected behavior, with the wireless connection to launch correctly. Some users say Android Auto 9.9 breaks the automatic launch, so you should return to version 9.8 to test the fix.
If you use a wireless adapter, the culprit could also be the device itself. Android Auto wireless adapters have become more popular lately, allowing users to give up on cables and use the application without a cord. However, some of them, including Motorola's MA1, have encountered various glitches, including slow launches in certain cars.
If your car supports a wired connection, you can also return to the cable, at least temporarily, until Google comes up with a fix. I know this isn't the most convenient solution, but it's the only way to be sure Android Auto works correctly until Google ships a patch. The latest stable version of Android Auto is version 10.3, but it doesn't seem to produce any improvement for this bug. A new beta build should go live in the coming days, and I'll let you know if it fixes the wireless bug.
The behavior makes sense from a convenient perspective, especially when using Android Auto wireless. The no-cord experience allows users to keep their phones in their pockets, so Android Auto can launch on the infotainment screen with drivers interacting with their mobile devices or the head unit.
However, a bug first reported in October last year has returned for no clear reason to haunt users and become more widespread. Android Auto wireless no longer launches automatically in cars where this behavior was supported, so drivers must conduct the complete process manually.
Posts on Google's forums reveal that users must establish the Bluetooth connection, wait for Android Auto wireless to detect the head unit, and then touch the icon on the home screen to launch the app.
The bug never received a fix, but it has now returned, likely after a recent Android Auto update. It's also more widespread, with several users confirming the failed automatic launch in posts on Google's forums. In every case, Android Auto requires manual interaction to launch when the wireless connection is enabled.
A member of the Android Auto team says the reports have already been forwarded to developers, promising an update when more information is available. In the meantime, users can't do much about this glitch, though if a recent Android Auto update causes the problem, the easiest workaround is to downgrade.
Installing an earlier version of Android Auto should restore the expected behavior, with the wireless connection to launch correctly. Some users say Android Auto 9.9 breaks the automatic launch, so you should return to version 9.8 to test the fix.
If you use a wireless adapter, the culprit could also be the device itself. Android Auto wireless adapters have become more popular lately, allowing users to give up on cables and use the application without a cord. However, some of them, including Motorola's MA1, have encountered various glitches, including slow launches in certain cars.
If your car supports a wired connection, you can also return to the cable, at least temporarily, until Google comes up with a fix. I know this isn't the most convenient solution, but it's the only way to be sure Android Auto works correctly until Google ships a patch. The latest stable version of Android Auto is version 10.3, but it doesn't seem to produce any improvement for this bug. A new beta build should go live in the coming days, and I'll let you know if it fixes the wireless bug.
Google News