You say the name. Your car screen shows the name. Then Android Auto asks, again: “Who do you want to call?” According to PhoneArena's November 6 report, that loop is a real, reported bug on Samsung Galaxy and Google Pixel phones — not a broken phone, and not you mumbling.
As of today there is no confirmed fix and no official cause. Google's Android Auto team is collecting details from affected drivers, according to Android Authority and SamMobile. And if you were thinking of switching anyway: this is software, so your phone still pays like a healthy one at JustSell — a Galaxy S26 Ultra pays $1,010–$1,110 in Like New condition, anchored on the 512GB model at $1,010.
Picture the drive home on the 401. Traffic is crawling, both hands stay on the wheel, and you do the safe thing: you ask the car to call home. The screen finds the contact instantly. The voice asks who you want to call. You repeat it, louder. It asks again.
That loop — funny once, infuriating by the third time — is the week's most-reported Android Auto story. Here is what is happening, what the reporting does not prove, and what to try while parked.
It hears you perfectly. It just won't dial.
This detail makes the bug so strange. According to PhoneArena, the assistant often recognises the command accurately: the contact's name appears on the car display. It then fails at the next step, answering “Who do you want to call?” or “Who do you want to text?” instead of dialling or sending.
Shouting does not help — owners who retry louder stay in the same loop, PhoneArena reports. Your voice was never the problem: the name was heard and displayed. The breakdown happens after understanding, when the assistant should match that name to your contacts and act.
Texting is caught in the same loop, according to SamMobile's November 5 report: Gemini understands the task, then fails to find the contact. Nor is it one car or cable — reports span wired and wireless setups, which is why Google's team asks about both.
The phones named in forum-based reporting are the Galaxy S26, Galaxy S25 Ultra and Galaxy S24, and the Pixel 10 and Pixel 10 Pro. Treat that as a reported list, not a verified one — Android Authority notes it comes from forums, not a Google-published list, and other models may be affected.
How we got here: a new assistant, then a loop
No timeline here is confirmed by Google — but the sequence is hard to ignore.
| When | What the reporting shows |
|---|---|
| September 29 | Gemini replaced Google Assistant on Android, according to AndroidPure's summary of the rollout. |
| Early October | Call-loop reports begin piling up on Google's Android Auto Help forum, with more surfacing this week, according to 9to5Google. |
| November 4 | An Android Auto team member replies in forum threads asking affected users for diagnostic details, per AndroidPure. |
| November 5 | Android Authority and SamMobile report the loop, the affected models named in forums, and Google's data-gathering. |
| November 6 | PhoneArena reports users have dealt with it for weeks, with no official patch yet — while noting Google patched a separate Android Auto connectivity bug this same week. |
PhoneArena is careful, and so should we be: complaints spiked after an October update whose timing coincides with Gemini replacing Assistant. That pattern is worth reporting. It is not proof of cause — and no outlet has reported a confirmed one.
The screen shows the right name. The call never happens. Whatever is broken sits between understanding you and finding your contacts.
The phone-number clue is the most telling detail yet
Here is the niche fact buried in the coverage — the one that points at where the fault probably lives. In some cases, speaking the actual phone number works, while asking by name does not, according to Android Authority.
Dialling by digits skips a whole step: matching a spoken name against your saved contacts. If digits work and names loop, the microphone, speech recognition and dialler are all doing their jobs — the suspect is the contact-matching layer in between. Android Authority raises exactly that suggestion, while stressing the cause remains unknown.
That also explains why two brands are hit at once. A Galaxy and a Pixel share little hardware, but they share this assistant and this contact lookup. A flaw there travels across both lineups — which is what the reports show.
Before you reset anything
Resist the factory reset. Gadget Hacks notes there is no evidence in the cited coverage that resets, re-pairing or swapping cables fix this loop — none is a Google-confirmed solution yet. Try the small things first.
What Google is asking affected drivers to send
The requests double as the most useful thing you can do if the loop has you. According to Android Authority, Android Auto community specialists are asking for:
- Your phone model — Galaxy or Pixel, and which one
- Your Android build number
- Your Android Auto version and Google Play Services version
- Your vehicle or head-unit details
- Whether your connection is wired or wireless
That is a net cast deliberately wide: phone, car, connection and three software layers — what a team does when it cannot yet pin a fault to one place. Adding your details to the Help forum thread genuinely helps narrow it.
Try these while parked, in this order
The workaround with real reports behind it. Recite the 10-digit number instead of the name. It will not help with texts — but for a call you need today, it is the best-documented bypass.
PhoneArena suggests checking contacts and call permissions. In Settings, open Android Auto's permissions, turn Contacts off and back on, and do the same for Phone — forcing the app to re-ask for the access the bug seems to lose.
Also from PhoneArena's list: clear Android Auto's cache. It is reversible and keeps your settings; resetting the phone is a bigger hammer with no evidence behind it here.
If the loop survives all three steps, send Google the details they are asking for, and watch the release notes for a fix that names this issue.
One honest note: some guides suggest switching back to the legacy Assistant. Other reporting says Gemini became the only assistant on September 29, with no way back. If your phone still offers the switch, try it. If not, do not burn an evening hunting for it.
A software loop is not a condition grade
Now the money question, because many owners hear “bug” and think “my phone just lost value.” At JustSell, a quote is built from model, storage, condition and battery health — the physical phone. An assistant loop a patch can erase overnight is not wear or damage to your handset.
Here is what the affected flagships actually pay today, from the live price book. Each range is anchored on the model's second storage tier, in Like New condition:
| Model (anchor configuration) | JustSell pays |
|---|---|
| Galaxy S26 Ultra, 512GB — Sealed | $1,060 |
| Galaxy S26 Ultra, 512GB — Like New | $1,010 |
| Galaxy S26 Ultra, 512GB — Good | $910 |
| Galaxy S26 Ultra, 512GB — Fair | $810 |
| Pixel 10 Pro, 256GB — Sealed | $790 |
| Pixel 10 Pro, 256GB — Like New | $610 |
| Pixel 10 Pro, 256GB — Good | $550 |
| Pixel 10 Pro, 256GB — Fair | $510 |
The full ladders run higher: the S26 Ultra reaches $1,110, the Pixel 10 Pro $910. Other named models pay strongly too — a Galaxy S26 (512GB) pays $600 Like New, a Galaxy S24 Ultra (512GB) $610, and a Pixel 10 (256GB) $460. See your model on the Galaxy S26 Ultra page or the Pixel 10 Pro page.
Money tip
A quote at JustSell is locked for 7 days. If you are even thinking of switching, get the number now while you wait for the patch — the lock means a slow fix cannot cost you a slow price drop in the meantime.
Keep it, wait it out — or let the loop make the decision?
If hands-free calling is a nice-to-have and you love the phone otherwise, wait: a team actively collecting data, and a separate connectivity bug already patched this week, point to a fix arriving as an update, not a repair bill.
If you spend your workday in the car, though, “wait for a patch with no date” is a daily tax on a safety feature. For drivers already eyeing a switch, this is a clean moment to act: your hardware value is untouched, and the frustration ends with the handset.
And if you do sell, the handover does not need to become another errand — JustSell offers free pickup from your doorstep if you are within the service area, so it is worth a moment to check whether your city is covered before you plan a trip.
The bottom line
The Android Auto loop is real, reported across Galaxy S26, S25 and S24 and Pixel 10 models, and unfixed as of November 6 — with Google's team collecting the details a fix needs. It is a software story, not a hardware verdict: a Galaxy S26 Ultra still pays $1,010–$1,110 and a Pixel 10 Pro $610–$910 at JustSell today.
Frequently asked questions
Why does Android Auto keep asking who I want to call?
According to PhoneArena, Android Authority and SamMobile, a reported bug in Gemini-era Android Auto makes the assistant loop on that question even after displaying the correct contact. Google has not confirmed a cause, and no fix had been announced as of November 6, 2026.
Which phones are affected by the Android Auto call bug?
Forum-based reporting names the Galaxy S26, Galaxy S25 Ultra and Galaxy S24, and the Pixel 10 and Pixel 10 Pro. It comes from user reports, not a verified Google list, so other models may be affected too.
Is there a fix or a workaround that works?
There is no confirmed fix yet. The best-reported workaround is saying the 10-digit number instead of the contact's name, which works for calls in some cases. Checking permissions and clearing the cache are also suggested by PhoneArena, but none is confirmed.
Did the Gemini update cause the Android Auto loop?
That has not been proven. Complaints spiked after an October 2026 update, and the timing coincides with Gemini replacing Assistant — a pattern several outlets note. Google has not named a cause.
Does this bug lower what my Galaxy or Pixel is worth?
No — it is a software issue affecting multiple brands at once, not damage to your phone. At JustSell, a Galaxy S26 Ultra pays $1,010 to $1,110 in Like New condition and a Pixel 10 Pro pays $610 to $910, based on model, storage, condition and battery health.
How do I report the bug so it gets fixed faster?
Add your details to the Android Auto Help forum threads, where the team is collecting them: phone model, Android build, Android Auto and Play Services versions, vehicle or head unit, and wired or wireless connection.
Know your number before the patch lands
Whether you wait or switch, knowing your number takes about 30 seconds — and the price is locked for 7 days while you decide. Pixel owners, yours is the Pixel quote tool. Either way, you get paid the same day you hand the phone over.
Sources: PhoneArena, November 6, 2026, Android Authority, November 5, 2026, SamMobile, November 5, 2026, AndroidPure, November 6, 2026
