Google’s latest Android Auto update, version 17.2, started rolling out to the stable channel in early July 2026, and within hours, reports of app crashes flooded online forums. The update, which was supposed to refine the in-car experience, is instead leaving many drivers without navigation, music, or hands‑free calling—especially those who connect wirelessly. The most jarring discovery: the only widely effective fix right now is to manually roll back to the previous version.
A Rocky Stable Release: What’s Really Going On
Android Auto 17.2 was pushed through the Play Store beginning on July 5, 2026, according to user reports and update logs. Unlike beta builds, this was a full stable release, intended for all compatible devices. Yet almost immediately, a cluster of complaints emerged on Google’s own support forums, Reddit, and Twitter. The common thread? The app crashes repeatedly—often within minutes—when running wirelessly.
Specific symptoms vary. Some drivers see the Android Auto interface freeze, then vanish, while their phone becomes unresponsive. Others report that audio cuts out abruptly, followed by a full disconnection. The crashes appear most often when a voice command is given or when the system tries to display a navigation prompt. For many, the trigger is the new Gemini assistant.
Google has been steadily replacing Google Assistant with Gemini across its products, and Android Auto 17.2 seems to mark a deeper integration. In this version, Gemini handles all voice interactions—from sending texts to changing music to routing navigation. But the rollout has not gone smoothly. Users recount that simply saying “Hey Google” or tapping the assistant button can tank the entire session. “Every time I try to start a call or reply to a message, Android Auto crashes,” wrote one user on the official support thread. Another noted, “Wireless worked perfectly on 17.1. Now, it’s unusable.”
The wireless connection itself appears to be a key factor. Wired Android Auto users are experiencing far fewer issues, though a small number of reports suggest instability there, too. The crashes seem to stem from a conflict between Gemini’s network‑dependent processing and the Bluetooth/Wi‑Fi handoff that wireless Android Auto relies on. While Google has not issued an official statement, the volume and consistency of reports make it clear this is a widespread bug, not an isolated glitch.
Who’s Affected—and What’s at Stake
Wireless Android Auto is no longer a niche feature. Most new vehicles sold in 2025 and 2026 offer it, and countless aftermarket head units have added support. For drivers who’ve come to rely on the seamless transition from phone to dashboard, a crashing app is more than an inconvenience—it’s a safety concern. Losing your navigation feed in an unfamiliar area or having a call drop just as you need to relay critical information can be dangerous.
The impact hits different groups in distinct ways:
- Everyday commuters might find themselves fumbling with their phone directly, which is both illegal in many regions and a distraction risk.
- Ride‑share and delivery drivers depend on Android Auto for turn‑by‑turn directions and order updates. Repeated crashes force them to rely on phone mounts, slowing down their workflow.
- Families using in‑car entertainment and hands‑free messaging for coordinating pickups and arrivals lose the convenience that made Android Auto essential.
- Fleet managers who standardize on Android devices for their drivers face a productivity hit and potential safety liabilities if vehicles become less connected.
Perhaps most frustratingly, the crashes can be intermittent. A drive might start smoothly, only for the system to fail after ten minutes. This unpredictability makes the experience even more maddening, as users can’t simply decide to “just use wired” for a bit—they have to anticipate a failure that may occur at the worst possible moment.
The Road to 17.2: How Gemini Took the Wheel
Android Auto’s journey has always been one of gradual refinement, but the last two years pushed the platform into an AI‑first direction. In early 2026, Google announced that Gemini would replace Google Assistant across all major surfaces, including Android Auto. Early previews promised a smarter, more context‑aware assistant that could handle multi‑turn conversations, remember preferences, and even proactively suggest actions.
The transition began with an opt‑in beta in March 2026, allowing users to try Gemini in Android Auto while keeping Assistant as a fallback. Feedback was mixed—some praised its accuracy, while others complained about slower response times and a tendency to misinterpret commands. Still, Google pressed forward. Version 17.0, released in May, expanded Gemini to all users but kept Assistant as an option. Then, with 17.2, Gemini became the only voice companion. The Assistant fallback was removed.
That removal is a critical part of the current crisis. Earlier versions allowed users to switch back to Assistant if Gemini acted up, but 17.2 eliminated that toggle. Now, if Gemini malfunctions, there’s no retreat. And the wireless‑specific crashes suggest that something in the Gemini stack—perhaps the way it negotiates data between the phone and the car’s infotainment system—isn’t ready for prime time.
This isn’t the first time an Android Auto update has caused turmoil. In 2024, a release temporarily broke compatibility with certain Mazda and BMW models. In 2025, a bug prevented Android Auto from launching at all on some Samsung phones. Each time, Google patched the issue within days or weeks. But the 17.2 outage feels more severe because it strikes at the core of the wireless experience, which now accounts for over 60% of Android Auto sessions, according to Google’s own developer data.
Immediate Steps to Stop the Crashes
If you haven’t yet updated to 17.2, stop Android Auto from updating automatically. Open the Play Store, go to Android Auto’s page, tap the three‑dot menu, and uncheck “Enable auto‑update.” This will keep you on a stable version (likely 17.1) until a verified fix arrives.
For those already on 17.2 and suffering crashes, the most reliable solution is to roll back to version 17.1. Here’s how:
-
Uninstall updates
- Go to Settings > Apps > See all apps > Android Auto.
- Tap the three‑dot menu (top right) and select Uninstall updates.
- This will revert Android Auto to the factory version that came with your phone. Note: this factory version might be older than 17.1, so you’ll need to install 17.1 manually. -
Download and install Android Auto 17.1
- Trusted APK repositories like APKMirror host old versions of Android Auto.
- On your phone, enable “Install unknown apps” for your browser.
- Download the 17.1 APK (ensure it’s the correct architecture for your device—arm64‑v8a for most modern phones).
- Install the APK, then open Android Auto. You may need to reconfigure your car connection. -
Prevent automatic re‑updates
- Immediately after installing 17.1, go to the Play Store and disable auto‑update for Android Auto as described earlier. Google may push 17.2 again if you don’t. -
Temporary workarounds (less reliable)
- Switch to a wired connection: Some users report fewer crashes when using a USB cable. However, this doesn’t eliminate the issue for everyone, and it negates the convenience of wireless.
- Clear cache and data: Go to Android Auto’s app info, tap Storage & cache, then Clear cache and Clear storage. Reboot your phone and reconnect. This sometimes stabilizes the app for a single drive, but crashes often return.
- Disable Gemini’s voice activation: If you can access Android Auto settings (either on the phone or while plugged in), try turning off “Hey Google” detection. This may prevent the voice trigger from initiating a crash, but you lose hands‑free functionality.
Advanced users comfortable with ADB can also use the command adb uninstall com.google.android.projection.gearll to completely remove the app, then reinstall 17.1 via APK. This ensures no leftover files from 17.2 interfere.
What’s Next: Watching for a Patch
As of July 8, 2026, Google hasn’t acknowledged the problem publicly. Historically, though, the Android Auto team moves quickly when a wave of crash reports surfaces. It’s likely that version 17.2.1 or a server‑side adjustment will arrive within a week. The issue tracker on Google’s issue tracker (issuetracker.google.com) shows several new entries tagged “Android Auto crash wireless,” and community managers are beginning to collect bug reports. That’s typically a precursor to a hotfix.
In the meantime, the community is banding together. XDA Developers forums are alive with discussions about which 17.1 builds are most stable, and some users are experimenting with beta versions of Gemini to see if a newer build resolves the conflict. If you’re desperate for a fix and don’t want to wait, joining those discussions can provide early, albeit unofficial, relief.
For Windows users who connect to the Microsoft ecosystem in their cars—for instance, via the Your Phone app or by using Windows‑based infotainment systems—the Android Auto crash is another reminder that cross‑platform integration remains fragile. As cars become rolling computers, updates like this can ripple across devices in unexpected ways.
One thing is certain: wireless Android Auto is too critical a feature for Google to let languish. The pressure is on, and a fix will likely come fast. Until then, the rollback is your safest route to a reliable drive.