Google's Gemini Takeover Is Killing Hands-Free Calling in Cars
With Assistant's September retirement, Android's only in-car voice option is Gemini — and on Android Auto, it's failing calls with alarming regularity.
Source material: zdnet.com
The September Ultimatum
Every Android user has a date circled on the calendar now: September. That's when Google pulls the plug on Assistant for good, leaving Gemini as the sole digital assistant on the platform. Anyone who has spent time with both knows the difference immediately. Assistant was a task runner — direct, fast, and quietly competent. Gemini is an AI engine, built for generating, summarizing, and predicting, not necessarily for executing simple commands. For hands-free calling, that distinction has turned out to be critical. The user who documented this issue did so on a Pixel 9 Pro, the device Google itself sells as its flagship showcase for Gemini's capabilities. If the feature fails there, it fails everywhere.
When Dialing Stopped Working
The contrast is stark. With Assistant, the routine was always the same: say "Hey Google, call Haversham Happenstance" and within seconds the phone was ringing. Failures were so rare they were memorable. Switching to Gemini changed everything, particularly when the phone was connected to Android Auto. The command gets acknowledged, then silence. The call never connects. Clearing the cache and deleting storage on Gemini doesn't resolve it, either — the problem persists through even the most thorough cleanup. The writer whose experience is documented here gave up entirely, choosing to skip placing calls altogether while driving unless the situation was urgent enough to warrant pulling over.
A Deadly Regression
This is not just an inconvenience, and the stakes are measurable. In 2024, 3,208 lives were lost in the US to distracted driving. That number came at a time when Android's hands-free calling was working as designed. Removing a functional hands-free option from drivers and replacing it with an unstable one creates a clear incentive: the driver who needs to make a call looks down at the phone instead of the road. The math is not complicated, and the risk is not theoretical. If the feature fails mid-route, the driver has to decide whether to risk manual dialing, find a safe place to stop, or just not make the call. None of those are acceptable outcomes for a feature Google has positioned as a core competency.
Two Paths Forward for Google
Google has essentially two options before the September deadline. The first is to reverse course and allow Assistant to remain as a selectable option for those who prefer its reliability. The second is to commit engineers to fixing Gemini's hands-free calling when paired with Android Auto before the old assistant is retired. The timeline is not generous. Fixing a deep integration issue like this is not a one-week patch; it requires testing against Google's own fleet of Pixel devices, the full array of Android Auto head units, and the chaotic variety of third-party launchers. The company has had months of complaints and has shipped no effective remedy. With Assistant's retirement now a matter of months away, the pressure is squarely on Google to prove Gemini can handle the fundamental task of making a phone call.
Where this came from. This breakdown is based on source material published at zdnet.com. Images above are used with the credits shown beneath each one.