What's happening
You plug your phone into the car's USB port — or try to connect wirelessly — and instead of the familiar Android Auto interface appearing on the head unit, your phone shows a toast notification:
Android Auto has stopped. Please try again.
Sometimes the head unit throws a generic "Connection failed" screen. Other times Android Auto starts, runs for three or four seconds, then crashes. Occasionally the car doesn't recognize the phone at all.
What makes this maddening: the same setup worked fine yesterday. Nothing changed. And the error message tells you absolutely nothing useful.
Root causes (quick triage)
- Bad or charge-only USB cable — the #1 cause by a wide margin. Many cables sold alongside phone accessories don't carry data signals at all.
- Android Auto cache corruption — happens frequently after an OTA update, especially on Pixel and Samsung devices.
- Google Play Services out of sync — Android Auto offloads a lot of its core logic to Play Services. Version mismatches break the handshake.
- Failing USB port on the head unit — debris in the port, a loose connector, or a firmware bug can cause intermittent drops.
- Phone USB mode set to "Charging only" — Android Auto needs MTP or the dedicated Android Auto transfer mode to negotiate the connection.
- Head unit firmware mismatch — older Pioneer, Kenwood, and Sony units sometimes need a firmware push after a major Android Auto version bump.
Quick fix — start here
1. Swap the USB cable first
Grab a cable you're sure carries data — the one that came in the phone's box, or any USB-A to USB-C cable certified for data transfer. On forums like r/AndroidAuto, cable swaps alone resolve roughly 40% of "has stopped" complaints. Skip this step and you might spend an hour debugging something that costs two minutes to test.
# No command needed — physically swap the cable
# Test with: Settings → Connected devices → USB
# Confirm you see "File transfer / Android Auto" options, not just "Charging"
2. Force-stop Android Auto and clear its cache
Settings → Apps → See all apps → Android Auto
→ Force stop
→ Storage & cache → Clear cache
Leave storage alone — clearing it wipes your paired devices and preferences. Cache only is enough to break most crash loops.
3. Check the USB connection mode
Pull down the notification shade immediately after plugging in. Look for a "USB preferences" or "Charging this device via USB" notification. Tap it and switch to "Android Auto" if the option exists, or fall back to "File transfer (MTP)".
# Via ADB if the phone is reachable over Wi-Fi
adb shell am start -a android.settings.USB_PREFERENCES_SETTINGS
4. Full power cycle — phone and head unit both
Turn the car completely off. Not just the ignition — all the way off. Wait 30 seconds. This clears stale Bluetooth and USB pairing state that a simple restart misses. Start the car fresh, then reconnect.
Permanent fix — if the crash keeps coming back
Update Android Auto and Google Play Services
Android Auto ships updates through the Play Store independently of Android OS releases. Play Services is the part most people forget — an outdated version breaks the internal API Android Auto relies on.
# Check current versions
adb shell dumpsys package com.google.android.projection.gearhead | grep versionName
adb shell dumpsys package com.google.android.gms | grep versionName
Open Play Store, search "Android Auto", update if available. Then repeat for "Google Play Services".
Re-grant permissions after an OS update
Android 12 tightened permission enforcement significantly. After upgrading to Android 12, 13, or 14, Android Auto can silently lose permissions it had before — no warning, no explanation, just a crash on connect.
Settings → Apps → Android Auto → Permissions
# Ensure these are granted:
# - Phone
# - Contacts
# - SMS
# - Microphone
# - Location (for navigation)
# - Notifications
Reset Android Auto settings via developer mode
Buried inside the app is a reset option most people never find. It clears pairing history, permission cache, and connection state without touching the app install itself.
Android Auto app → bottom-right hamburger menu
→ Settings → scroll to bottom
→ "About" → tap version number 10 times
→ "Developer settings" appear → "Reset Android Auto"
Test the car's USB port with a second device
Borrow a friend's Android phone (or use a spare). Plug it into the same port and try Android Auto. Connects fine? The problem lives on your phone. Also fails? The head unit's USB port or firmware is the real culprit.
# Check if your car's head unit has a firmware update:
# Pioneer: System → Firmware Information → check pioneer.com
# Sony: Menu → General → Software Information → compare with sony.net/Products/Car-AV
# Kenwood: Menu → Settings → System Information → check kenwood.com
Wireless Android Auto: resolve Wi-Fi Direct channel conflicts
Wireless Android Auto runs over Wi-Fi Direct on the 5 GHz band. If your phone's personal hotspot is active, or your home router is on an overlapping channel, you'll see repeated drops that look exactly like app crashes.
# Check Wi-Fi Direct status
adb shell p2p_cli status
# Turn off hotspot if it's interfering:
Settings → Network & internet → Hotspot → turn OFF when using wireless Auto
When nothing above works
Still crashing? Check battery restrictions. MIUI, One UI, and third-party battery savers routinely kill Android Auto's background process — silently, without logging anything obvious.
Settings → Apps → Android Auto → Battery
→ Set to "Unrestricted" (not "Optimized")
Then verify Android Auto is on the system's doze whitelist:
# Check the doze whitelist
adb shell dumpsys deviceidle whitelist | grep gearhead
# Add it if it's missing
adb shell dumpsys deviceidle whitelist +com.google.android.projection.gearhead
Verify the fix
- Plug in (or enable wireless) — Android Auto should appear on the head unit within 5–10 seconds.
- Watch your phone for 2 minutes. No crash notification means you're past the usual failure window.
- Run a quick test: navigation, a phone call, and media playback. All three subsystems need to be stable.
- Disconnect, wait 10 seconds, reconnect. A clean second connection confirms the fix actually held.
Quick reference
Problem Fix
----------------------------------------------------------------------
Crash on connect Swap USB cable → clear AA cache
USB connects but no AA screen Change USB mode to Android Auto/MTP
Crash after Android update Re-grant permissions + update AA
Wireless drops repeatedly Disable hotspot, check Wi-Fi Direct
Head unit not recognized Test different phone → update head unit FW
Crash loop after clear cache Reset AA settings via developer mode