Google Assistant Not Listening
byu/bumpistheman inAndroidAuto
Google’s push to replace Google Assistant with Gemini across Android is well underway, and Android Auto has become one of the most visible fronts in that transition. Gemini began rolling out to cars late last year, promising smarter conversations and deeper AI capabilities behind the wheel.
But instead of a smooth upgrade, many drivers say the shift has turned into a frustrating experience. And in a twist Google likely didn’t expect, a growing number of users are actively switching back to Google Assistant, citing a degraded experience that feels like an early beta test rather than a finished product.
However, those attempting to switch back are discovering that the old reliable Assistant is currently in disarray, leaving Android Auto users with no fully functional voice control options.
Gemini struggles with the basics on Android Auto
The primary driver for the exodus away from Gemini is the AI’s inability to handle the fundamental tasks required behind the wheel. Users report that simple commands that worked perfectly for years are now hit-or-miss. Navigation is a major pain point; drivers frequently ask for directions, and while Gemini verbally acknowledges the request, the actual route often fails to populate in Google Maps.
Beyond navigation, the AI exhibits strange behaviors ranging from annoying to hallucinatory. Some users have reported Gemini providing wildly inaccurate travel times, claiming a destination is minutes away when it is actually hours distant.
Communication features have also taken a hit. In some instances, when a driver dictates a text message, Gemini interprets the content of the message as a command to the system rather than text to be sent, refusing to process the request. Music controls are similarly plagued, with the AI sometimes demanding premium subscriptions to YouTube Music to play specific artists, ignoring other installed media apps that previously worked without issue.
Google Assistant isn’t a safe haven
Naturally, the solution for frustrated users is to dive into their settings and revert to the legacy Google Assistant. However, this fallback plan is proving to be a dead end. A growing number of reports indicate that the classic Assistant is currently suffering from debilitating bugs that render voice commands nearly useless on Android Auto.
Even after disabling Gemini, drivers are encountering persistent “Sorry, I don’t understand” error messages for basic queries. The most prominent issue involves category searches. Historically, a driver could simply say “gas station,” “coffee shop,” or “grocery store” to see a list of results along their route. Now, the Assistant often fails to recognize these category prompts entirely or claims that the “app is not available” for what should be a native Maps function.

Users have found they must now use hyper-specific phrasing, such as “navigate to [Specific Store Name],” to get any result. This forces drivers to know their exact destination beforehand, defeating the utility of hands-free discovery while driving. Furthermore, international users have noted that the interplay between Gemini and the Assistant is causing language conflicts, where the system accepts input in a native language but attempts to execute commands in English, leading to failure.
This situation leaves Android Auto users in a precarious position. The new AI replacement feels undercooked and over-complicated for the driving environment, while the legacy system appears to be deteriorating, leading to speculation among users that the Assistant is being intentionally neglected to force adoption of Gemini.
For a platform predicated on safety and hands-free convenience, having both voice assistants in a state of disarray is a significant problem. It is currently forcing drivers to physically interact with their phone screens to set navigation or choose music, which is exactly the behavior Android Auto was designed to prevent.