Android Auto 17.2 Is Breaking Drives, Not Improving Them

Android Auto 17.2: An Update Drivers Should Treat With Caution

Android Auto 17.2 is the latest in-car software update from Google that is meant to deliver a safer, voice-driven experience for navigation, calls, and media, but it is currently causing frequent crashes, unstable connections, and forcing many drivers to downgrade to older versions to keep their dashboard working at all.

The key takeaway is blunt: if you rely on Android Auto every day, the 17.2 update is more risk than reward right now. Multiple reports link the 17.2.662404 build to repeatable Android Auto crashes within minutes of starting a session, whether on Android 16 or Android 17 and across different phone brands. The problem is not a one-off glitch; sessions collapse, you restart, and the same crash cycle begins again. As one outlet put it, version 17.2 has introduced app crashes severe enough that users are reverting to earlier releases. For a platform intended to reduce distraction and make driving safer, that should ring alarm bells for both drivers and Google.

Crashes and Connection Chaos: What 17.2 Is Doing Wrong

Android Auto crashes are not new, but 17.2 has turned them into a full-blown reliability crisis. Users report that the app repeatedly crashes during use, often within a few minutes, then repeats the failure every time they restart. Critically, this isn’t limited to wireless Android Auto; the latest wave of bugs hits both wired and wireless modes, and affects Pixel, Samsung, OnePlus, and Moto owners alike. That means almost any modern Android phone connected to a compatible car could be caught in the crossfire.

Wireless connections, already the weaker link in the Android Auto chain, appear to suffer most. Some drivers say the system barely runs at all, with sessions collapsing after just a few minutes. And this instability follows months of connection problems. Back in March, a Pixel Drop paired with an Android Auto app update broke wired connections entirely for some Pixel and Samsung Galaxy S26 owners, causing loops where Android Auto would connect, disconnect, reconnect, then fail again. Google pushed a Play System services update in June specifically to fix persistent Android Auto connection issues, but the fresh crashes arriving with 17.2 make that fix look under-tested at best.

Gemini AI: Innovation Colliding With Basic Reliability

The instability around Android Auto 17.2 isn’t happening in isolation—it is landing on top of Google’s aggressive Gemini AI rollout, which is already frustrating drivers. Google’s decision to push Gemini as the default assistant on Android Auto has made things worse instead of better for many users. Those who received the Gemini upgrade report app crashes triggered by hands-free commands, broken phone calls that return a “Something went wrong. Please try again” error, and a chatbot that talks too much while doing too little.

The pattern is alarming. In April, a bug in Android Auto 16.7 caused Gemini to randomly revert to Google Assistant without any user action. Separate reporting has documented five persistent failures: slow responses that lag several seconds behind voice commands, failure to recognize basic contacts such as “Mom” or “Dad,” navigation mistakes sending drivers to wrong addresses, broken third-party app integration with services like Spotify and Waze, and verbose answers that talk over music instead of executing simple tasks. Taken together, it looks less like an intelligent upgrade and more like a layer of instability laid on top of an already fragile platform. When an AI assistant can crash your in-car system or block calls mid-drive, it stops being a feature and becomes a liability.

Should You Update or Downgrade? Hard Choices With Little Guidance

The most frustrating part of the Android Auto 17.2 saga is the silence. Google has yet to acknowledge the crashing bug, and history suggests drivers should not expect a fast, transparent fix. Instead of clear guidance on whether to install the latest update or stay on older versions, users are piecing together advice from support threads and community posts. This leaves everyday drivers in a bad spot: upgrade and risk Android Auto crashes and connection chaos, or hold back and miss potential security and feature updates.

In practice, many affected drivers are choosing the safer option: an Android Auto downgrade. Rolling back to Android Auto v17 is working for some, and downgrading specifically to 17.1 is described as the most reliable fix for those hit by the 17.2 crashes. A few workarounds—clearing the Android Auto cache, swapping to certified USB data cables under three feet, and disabling strict USB restriction policies—have helped certain users, but none offer the broad stability that a functioning update should. If you heavily rely on Android Auto, the pragmatic stance right now is to avoid 17.2 when you can or be ready to revert fast if your car display starts freezing and disconnecting.

What Google Needs to Fix Before Drivers Trust Android Auto Again

Android Auto is supposed to be a safety feature, not a gamble. When an update like 17.2 makes the system barely usable and pushes people toward an Android Auto downgrade, that signals a deeper reliability problem than a single bad release. The irony that these crashes surfaced less than a month after a Play System update aimed at fixing persistent connection issues underscores how weak quality control and testing appear to be. Google’s pattern of reactive fixes—waiting until complaints pile up, then rolling out emergency patches and server-side changes—does not inspire confidence for a product embedded in daily driving.

To earn back trust, Google needs to prioritize stability over shiny additions like Gemini AI. That means acknowledging Android Auto crashes quickly, publishing clear guidance on affected versions, and testing updates against a realistic mix of phones, cars, wired and wireless setups before they land on dashboards. For now, drivers have to protect themselves: be cautious about installing the Android Auto 17.2 update, keep backup options such as mirroring from your phone or using native car apps, and be prepared to roll back if connection issues or crashes start appearing. Until Google proves it can keep Android Auto reliably connected and crash-free, the safest choice is to treat every new update as suspect, not automatic.