Gemini in Android Auto has been stuck asking drivers who to call since early October

Gemini in Android Auto has been stuck in a loop since early October, repeatedly asking drivers who they want to call or text no matter how clearly a name is spoken. Reports of the failure span more than a month, and the report that surfaced it on Nov. 5 carried no statement from Google.

Tech news in one quick read: Get the most interesting stories in startups, tech and programming, each with a short TLDR, in one daily email from TLDR.

Subscribe to TLDR →

We may earn a commission if you sign up.

The fault shows up in the most routine hands-free task in a car: telling the dashboard to phone a contact. Instead of placing the call, the assistant asks again, and again, then starts over, which pushes drivers back to tapping the screen.

The who-to-call loop on Android Auto

Ben Schoon of 9to5Google wrote on Nov. 5 that Gemini does not recognize names when a driver tries to place a call or send a text by voice, and gets caught in a loop of asking for the recipient. Repeating the name does not complete the command. The assistant simply restarts the question.

Schoon described the problem as not isolated to any particular phone or Android Auto build, which rules out the easy explanation of one handset maker or one app release. The article carried no statement from Google, and its only forward-looking line was the author’s own expectation that a fix is likely a matter of time because Google constantly ships updates.

A separate and more isolated complaint covers Android Auto automatically answering calls. That one is tracked in a Reddit thread and is not part of the Gemini loop, though both land in the same category of unreliable phone handling.

The timing matters because Gemini is a recent arrival in cars. TechCrunch reported that Google began rolling Gemini out to Android Auto globally on Nov. 20, 2025, in 45 languages, replacing Google Assistant for people who had already upgraded on their phones. The new assistant was pitched around natural speech and a set of messaging features, including replying to texts, summarizing messages and adding an ETA, which makes recipient recognition central to the product.

Google support threads dating to early October

The earliest evidence sits in Google’s own help forum. Two threads from early October, one and another, describe the assistant asking who to call after a name has been given. A later thread was trending by the time of 9to5Google’s report, and that trending thread had drawn the most reports.

A more recent thread shows the behavior still occurring in November, which is the basis for describing the issue as continuous since early October rather than as a one-week glitch. The wider rollout is documented in TechCrunch’s Nov. 20, 2025 report, which listed route questions, Gmail lookups, playlists and Gemini Live conversations among the features, none of which depend on the contact lookup that is now failing. Because the threads come from different users and devices, they point to something on the assistant side rather than a single phone.

That inference is the reporter’s reading of user posts, not a diagnosis from Google. No engineer or spokesperson has named a cause, a version number or a rollout date for a correction.

The reports also coexist with a related complaint. Users have separately described Android Auto answering calls on its own, a problem that surfaced on Reddit and that Schoon treated as distinct from the name-recognition loop. Together they leave phone handling, the reason many drivers connect a handset to the dashboard in the first place, looking uneven.

For drivers the stakes are practical. Hands-free calling exists so eyes stay on the road, and an assistant that keeps asking for a name pushes people toward the screen or the phone, the opposite of the design goal. The four forum threads cited by 9to5Google, numbered 470941048, 470959369, 474105781 and 475089314, span the entire period and give Google a ready list of cases to examine.

Readers should weigh the evidence for what it is. Forum posts and a single trade-press write-up establish that many drivers see the loop and that it began in early October, but they do not measure how many Android Auto users are affected, which phones or cars are involved most often, or whether the loop appears on every call or only some. Google’s silence leaves those questions open, and the count of affected drivers is unknown.

Workarounds drivers have while the loop persists

With no official statement, the practical options are limited to the ones that avoid the broken step. Drivers can fall back on touch controls such as the dialer or a saved contact on the Android Auto screen rather than a spoken name.

The 9to5Google article describes the failure only in the call and message path, with no mention of other voice commands being affected.

What remains unknown is the trigger. Nothing in the reporting ties the start of the problem to a specific Gemini update, and Google has not said whether a server-side change or an app update would carry the fix. Until it does, the support threads are the running record of whether the assistant has recovered.

This article was produced with the assistance of AI and reviewed by Morning Overview editors prior to publication.

Tech news in one quick read: Subscribe to TLDR →

We may earn a commission if you sign up.