Android Auto not connecting after One UI 9 update? Google says a fix is rolling out

Google has confirmed to Android Authority that a fix for Android Auto not connecting after the One UI 9 update is already rolling out. The company frames it as a broader "Android 17 / One UI 9" issue rather than a bug tied to one specific phone.

The confirmation follows a wave of complaints from Galaxy owners describing total connection failures or repeated drops right after updating. Google first acknowledged the problem yesterday, after forwarding a Galaxy A55 owner's complaint internally for review, according to Android Authority.

Here's what's actually confirmed, what's still murky, and which devices show up in the evidence so far. No device list, delivery mechanism, or rollout timeline has been published, so matching your own symptoms against the reporting below matters more than assuming your phone is already covered.

What the Android Auto connection issues on One UI 9 look like

Affected users describe two main failure patterns: Android Auto refusing to connect at all, or connecting and then dropping out repeatedly, according to Android Authority. 9to5Google adds stuttering performance to that list, alongside outright connection failure.

That distinction matters for anyone trying to confirm their issue matches this specific incident, since generic Android Auto complaints show up in forums for all kinds of unrelated reasons.

One detail stands out: switching to a wired connection did not resolve the problem for some users, which undercuts the usual advice to ditch wireless and plug in a cable, per Android Authority. Re-pairing devices and clearing app data reportedly didn't help either. Other Reddit users described similar failures, though some reported Android Auto working normally after the same update, according to Android Authority.

Not everyone running One UI 9 is hitting this. 9to5Google characterized the pattern as noticeable but not massively widespread, based on reports surfacing across Reddit, Samsung's community forums, and Google's own support forums over the past few weeks.

What Google's Android Auto fix confirms, and what it doesn't

A Google spokesperson told Android Authority today that a fix is already deployed, framing the problem as an "Android 17 / One UI 9" issue. The company says affected users "should see the issue resolved soon."

That's a real commitment, but a narrow one. Google hasn't disclosed a rollout date, named the delivery method (an Android Auto app update, a Google Play services update, or Samsung firmware), or specified which software builds are covered.

The timing is worth flagging. Just yesterday, 9to5Google reported there was "no official word on a fix" yet. That gap reflects how fast Google moved once reports piled up, not a contradiction between the two outlets.

It's also worth saying plainly what a company statement does and doesn't prove: confirmation that a fix is rolling out somewhere isn't the same as confirmation it's reached any specific phone. Google hasn't published a version number, build, or Android Auto app release that owners can check against. Until that exists, the only way to know if a given phone is covered is to test the connection directly.

Which Galaxy phones actually show up in the evidence

The device-level reporting is thinner than the headline suggests, and it's worth separating what's acknowledged from what's circulating on forums.

• Named in Google-acknowledged complaints: A Galaxy A55 owner's report was forwarded internally by Google's Android Auto team, and a Galaxy S24 Ultra reportedly reproduced the connection failure after updating to One UI 9, according to Android Authority.
• Comparative report: In a test cited by 9to5Google, a Galaxy S25 Edge still on One UI 8.5 connected without issue, while a Galaxy S24 Ultra on One UI 9 immediately reproduced the failure. That's suggestive of an update-related pattern, but it compared two different phone models rather than the same device before and after updating, so it doesn't isolate the update as the sole cause.
• Forum-only report: A Galaxy S26 owner described Android Auto breaking after updating to One UI 9 in a Samsung Community thread cited by Android Authority. That's a single unverified account, not something anyone has independently reproduced.
• A different thread that doesn't belong in this count: A Google Android Auto Community thread describes a Galaxy S25 Ultra that won't reconnect after the engine shuts off, requiring a full re-pair each time. The original poster says the problem started before updating to One UI 9 and simply continued afterward, so it reads like a pre-existing Bluetooth or reconnection bug rather than evidence of this specific post-update incident.

Google hasn't said whether its internal investigation is complete, whether these reports are being tracked as one issue, or whether One UI 9 itself is the root cause rather than something in how it interacts with Android Auto or Google Play services. Treat the A55 and S24 Ultra reports as the strongest signal, the S26 report as a data point to watch, and the engine-off thread as a separate problem entirely.

What to check if your Android Auto still won't connect

Google hasn't said whether the fix arrives through the Android Auto app, a Google Play services update, or a Samsung software patch, so there's no single setting that guarantees your phone has it.

That leaves a short list of things worth trying, with the caveat that none of them are confirmed to carry Google's fix specifically:

• Check the Play Store for pending updates to the Android Auto app and Google Play services. Neither is confirmed to carry the patch, but they're the only components under a user's control right now.
• Check Settings for a pending Samsung software update, since Google hasn't ruled out a firmware-side component.
• Restart the phone and test both wireless and wired connections. Results have varied across reports, so a successful connection is a data point, not proof the issue is resolved for good, according to Android Authority.

Hold off on factory resets, new cables, or dealer visits unless the problem persists after trying the steps above. Google has described a rollout in progress, not a finished fix that's already reached every device, so one failed attempt right now doesn't necessarily mean the patch skipped your phone.

What to do now

Google has confirmed a fix for the Android 17 / One UI 9 Android Auto issue is rolling out, but it hasn't published which devices, builds, or software channel are covered, according to Android Authority. The underlying cause, whether it sits in Android Auto, Android 17, One UI 9, or how the three interact, remains unidentified, and workarounds like re-pairing or switching to a wired connection have produced inconsistent results across the reports gathered so far.

For context, Google used a similar app-side update to resolve a separate Android Auto connection bug affecting Pixel and Galaxy S26 devices earlier this year, Android Police reported, though that precedent doesn't predict how this fix will be delivered.

Update the Android Auto app and Google Play services, check for a pending Samsung system update, and test the connection in the car. Then watch official Android Auto release notes or further Google statements before assuming the issue is resolved on your specific device, since nothing published so far confirms the fix has actually landed on any particular phone yet.