Android Auto の Gemini 通話不具合、9 月修正期限迫る

*Follow ZDNET: *Add us as a preferred source* on Google.*

ZDNET key takeaways

• Google is removing Assistant as an option in September.
• This leaves only Gemini for things like hands-free calling.
• Gemini is not nearly as reliable as Assistant for this feature.

Google is officially shutting down its Assistant tool in September, leaving Android with only one official option for a digital assistant: Gemini. Unleash the chorus of groans.

We all know that Google is pushing Gemini into every corner of Android. The company wants it to write our emails, summarize web pages, doctor our photos, do our shopping for us, reserve tables at restaurants, and so much more.

Also: I've used Android Auto for years, and these 5 changes solved my biggest issues

But what is the cost of depending on AI for so much? For one, it'll come at the cost of reliable hands-free voice calling, especially when connected to Android Auto -- at least in my experience.

Gemini's voice-calling issues

Gemini has been riddled with voice-calling issues for some time, with the most recent being the "Something went wrong. Please try again" issue in June 2026 that affected both Android and Android Auto, prompting users to returnto Android Assistant.

The problem isn't limited to voice calling.

For instance, users have complained about Gemini not playing a song when connected to Android Auto, or even when it's not connected to Android Auto, as this Reddit thread clearly shows. In that same thread, one user shared this Gemini interaction:

*@166Donk3y / Reddit*

In this Reddit thread, a user shared this interaction:

*@my1stname / Reddit*

Assistant does it better

Assistant handled what should be simple tasks very well.

In fact, I rarely had any issues making hands-free calls with Assistant or with Assistant and Android Auto, nor did I ever have any issues with Assistant sending messages. For calls, all I had to do was say, "Hey Google, call Haversham Happenstance," and within seconds, the phone was ringing. I can't remember the last time Assistant failed to place a hands-free call.

Once I (reluctantly) switched over to Gemini, voice calling with Android Auto became so unreliable that I stopped using the feature. Even after clearing the Gemini cache and deleting its storage, the problem persisted.

A driver safety issue

Let's be clear about this: the combination of Gemini and Android Auto makes hands-free calling an unreliable feature. What that does is cause drivers who need to place phone calls to look away from the road and down at their phones. We all know where this story ends, and it often doesn't end well.

You could opt to skip connecting your phone to Android Auto, and the issue will be far less frequent. For some, that might be a viable solution, but if you rely on Android Auto, you're out of luck for the time being.

Also: I've used Android Auto with Gemini for 2 months now - it's transformed my drives in 4 ways

In 2024, 3,208 lives were lost in the US due to distracted driving. That was back when Android phones were a reliable source of hands-free calling. Imagine what happens to that statistic when Gemini becomes the only option for placing a phone call without having to look at your device.

To be fair, if you're having trouble with hands-free calling with Gemini when it's not connected to Android Auto, Google has offered several solutions to resolve the problem. Unfortunately, those solutions don't fix the Gemini/Android Auto issue.

I gave it my best shot

For a while, I gave it my best shot. I'd be driving along with my Pixel 9 Pro connected to Android Auto and ask it to call someone, only to be greeted with silence. Gemini failed over and over unless I disconnected from Android Auto.

The problem with that solution is that I depend on using Google Maps through Android Auto because I get lost very easily. If I need to place a call while using Google Maps, I have to either disconnect from Android Auto or place the call manually.

Also: 48 hours later with the Google Home Speaker, I can't stop talking to Gemini (even if it's imperfect)

To place the call without the hands-free option, I'd have to wait until my Jeep wasn't moving. I'm not putting someone else in harm's way simply because of Gemini's inability to play well with Android Auto. Yes, it's really just an inconvenience, and it's one that I'm more than willing to deal with. Fortunately, I can also opt to use my steering wheel controls to run through my phone book to place a call. However, that's not exactly safe either. To that end, I'll wait until I'm at a stoplight, or I'll pull over to place the call.

At least it's an option.

Launchers don't play well either

It doesn't end with Android Auto. Over the weekend, I discovered that third-party home screen launchers don't always play well with the Gemini overlay used to "listen" for the phrase "Hey, Google," or "OK, Google," which means I can't use a third-party home screen launcher if I want hands-free calling.

So, let me get this straight: Gemini regularly fails to make calls on my Pixel 9 Pro when using it with Android Auto and the Pixel Launcher. If I use a third-party home screen launcher, it won't work, period, whether I'm using Android Auto or not.

Also: Google Home Speaker vs. Amazon Echo Dot Max: I compared the $99 smart hubs by the specs

This should be a priority for Google because it is directly linked to driver safety. This isn't an aesthetic, agentic, or app issue; it's a life-threatening problem. Successful hands-free calling could mean the difference between a life lived and a life lost.

Google has two choices

The way I see it, Google has two choices: allow us to use Assistant or fix hands-free calling with Gemini on Android Auto. Those are the options. I'm sure that Google is aware of the problem and will hopefully fix this before Assistant is kicked to the curb.