Ing. Calogero Bono
Since early October, some Pixel and Samsung Galaxy users have been unable to make calls or send messages by voice on Android Auto. The assistant understands the name, but keeps asking who you want to contact. The problem coincides with the broader arrival of Gemini on the car system. It matters because hands-free calling exists precisely so you can keep your hands on the wheel.
A few terms before we get into the facts. Android Auto is Google's system that brings your phone's apps to the car screen. Gemini is Google's AI-based assistant, gradually replacing Google Assistant. Hands-free calling means making calls by voice, without touching the phone. A loop is a cycle that repeats without reaching a result. A fix is the correction of the defect.
What is happening to calls on Android Auto?
You tell Gemini to call a contact. The assistant shows the correct name on screen, then asks you again "Who do you want to call?". You repeat yourself, and the question comes back the same. This is described by Android Authority, SamMobile and Smartworld.
According to reports, sending voice messages is also affected. Gemini understands the task, but cannot find the contact and complete it.
Which phones are involved?
The reports, collected on Google's support forums, concern Pixel 10 and Pixel 10 Pro and, among Samsung models, Galaxy S24, S25 Ultra and S26. SamMobile specifies that "there may be others". Complaints have been piling up since early October.
We do not know how many users are affected. The sources speak of "numerous" users, without figures, and the sample is made up of people who post on forums.
What is the cause of the bug?
No source confirms a cause. According to Smartworld, in some cases dictating the number works while calling by name does not. This suggests a problem in matching the voice request to saved contacts, but it is a hypothesis.
Technicians want to understand whether the defect involves Gemini, the older Assistant or both. For context on the assistant, also read Gemini 4 Carbon.
What is Google doing?
According to SamMobile, the Android Auto team is responding to complaints, collecting data and investigating. Android Authority mentions community specialists gathering diagnostic details.
Smartworld lists what is being asked of users.
- phone model
- Android Auto version
- wired or wireless connection
- when the problem started
There is no solution and no date for a fix.
Limits to know
The cause has not been verified, and it is unclear whether the fault lies with Gemini, Assistant or both. There are no figures on how many users are affected and no official confirmation of the models, which only come from forums. SamMobile itself says the timing may be a coincidence with the rollout. Google has given no timeline for a correction, so the list of phones could change.
What changes for those who work with digital tools
If you use Android Auto for work, for example to call clients while driving, hands-free calling can stop working without warning. The only workaround mentioned by Smartworld is typing the number by hand, and only when stopped. If you manage a fleet or sales staff, it is worth letting them know. The case is a reminder that a change on the service side can arrive even if you install nothing. Developers of Android apps need a backup plan for when a voice assistant fails to respond.
Our take
The problem is small in scope but serious in context. A voice assistant in the car cannot afford a loop, because every repetition distracts the person driving. It is striking that Gemini understands the request and fails to carry it out, a sign that the switch from Assistant needs better testing. Google is responding, which is good, but without a date the impression remains that the rollout went faster than the testing.
Frequently asked questions
Which phones have the Android Auto bug?
According to reports, Pixel 10, Pixel 10 Pro, Galaxy S24, S25 Ultra and S26. There may be others. The list comes from support forums.
Android Auto won't call by name, what can I do?
For now, type the number by hand, and only when stopped. Smartworld reports that in some cases dictating the number works. There is no official solution.
Does the bug also affect messages?
Yes. According to the sources, both calls and voice messages are affected. Gemini understands the task but cannot find the contact.
Has Google confirmed the problem?
Google is investigating. According to SamMobile, the Android Auto team is responding to users and collecting data. No cause has been confirmed.
When will the fix arrive?
It is not known. The sources say there is no expected date for the fix. It is best to follow Google's support forums.
What to watch in the coming weeks on Android Auto and Gemini
The key question is whether Google identifies the cause and whether the defect spreads beyond the models already reported. The answers on the forums will matter.
- Follow the threads on Google's support forums, where the first replies appear.
- If the bug affects you, report your model, Android Auto version, connection type and the date it started.
- Check for updates to Android Auto and the Google app, which may bring the fix.
Sources
- sammobile.com, Android Auto gets stuck in a loop for some Galaxy and Pixel phone users after Gemini update
- smartworld.it, Android Auto non chiama i contatti – il bug che sta facendo impazzire gli utenti Pixel e Galaxy
- androidauthority.com, Android Auto’s endless calling loop is driving Pixel and Galaxy owners crazy
