Users say outgoing calls started with Gemini in Android Auto fail when a Motorola Razr or Samsung Galaxy Z Flip is closed, and as of Oct. 10 no fix has been announced. Incoming calls reportedly work. Opening the phone is the reported workaround.

What users report

  • Symptom: Gemini says it is calling the contact, but the call never starts. One Reddit poster says the phone then shows "Flip open to continue."
  • Incoming calls: reported to work with the phone closed, per Android Authority and a Motorola forum poster.
  • Calling from the car screen: at least three forum posters say that starting a call manually from the car's display still places the call with the phone closed. Google has not confirmed this as a workaround.
  • Who is affected: these are user reports. The sources we read do not say how many people are affected.

Reported models

  • Motorola Razr: the Razr Ultra 2025 (60 Ultra) is named on Reddit and in Google's Android Auto forum. 9to5Google lists the Razr Ultra 2025 and 2026. Engadget says most posts mention the Ultra 60 and 70. One Google forum commenter reports a Razr 70 Ultra, and a Razr 50 owner also reports it.
  • Samsung Galaxy Z Flip: an April 17 Google forum post from a Flip 7 owner, which 25 users had marked "I have the same question" when we read it. Android Authority and Android Headlines report the issue on Z Flip phones.
  • Not only foldables: commenters on that thread also report failed calls on a Galaxy A54 5G and a Galaxy S26.

Is Gemini the cause?

  • What users say: many posters date the problem to when Gemini became active. Android Authority and Android Headlines say that is the common thread.
  • Assistant workaround: one Reddit user says switching back to Google Assistant restored calls. Engadget says Google began removing Assistant from phones on Sept. 4. 9to5Google says it was fully removed on Sept. 28.
  • Not universal: a Razr 60 Ultra owner says neither Assistant nor Gemini works on a replacement phone. Another Razr 60 Ultra owner reports the failure with Assistant on Sept. 15.
  • Other suspects: some posters blame Android 16. Android Headlines writes that neither company has confirmed the assistant change is the root cause.

What Google and Motorola have said

We found no public statement from either company. The replies are forum posts asking for details.

  • Google: Android Auto community specialists replied on May 7 (forwarded the report, emailed the poster) and on Aug 5 and 7 (asked for device and build details, then emailed).
  • Motorola: a Motorola agent asked a Reddit poster for details on June 25. On Motorola's forum, an agent replied on Sept. 11, 15 and 19; only the Sept. 19 reply asks the poster to submit a bug report.
  • How outlets describe it: 9to5Google says both are aware. Android Central says both are reaching out to users. Engadget says they "appear to be investigating."

Why it matters

Hands-free voice calling is a core use of Android Auto. If the reported workaround is to open the phone, the voice route loses much of its point for these users. One poster says it means taking the phone out and finding a place to set it while driving.

What is not confirmed

  • Cause. Neither company has named one.
  • Fix or timeline. None announced. We will update this story when a fix ships.