Why did Android Auto suddenly stop working in my car?

General
1

Android Auto was working fine until recently, but now it won’t start or keeps disconnecting from my car’s head unit. I’ve tried different USB cables, restarting my phone and car, and checking app permissions, but nothing fixes it. I need help figuring out if this is a settings issue, a compatibility problem after an update, or something wrong with my phone or car system so I can get Android Auto running reliably again.

2

Seen this a lot with Android Auto lately. Since you already tried cables, reboots, and permissions, I’d check these next, in roughly this order:

  1. Turn off battery optimization for Android Auto
    • On your phone go to Settings → Apps → Android Auto → Battery.
    • Set it to “Unrestricted” or similar.
    • Do the same for Google Play Services and Google Maps.
    Aggressive battery saving kills the AA process and causes random disconnects.

  2. Turn off data saver and VPN
    • Data Saver and some VPNs mess with Google services.
    • Disable Data Saver in Settings → Network.
    • If you use a VPN or “secure DNS” app, turn it off and test.

  3. USB mode and developer options
    • Plug into the car, pull down the USB notification on the phone.
    • Set USB mode to “File Transfer” or “MTP”, not “Charging only”.
    • Go to Android Auto settings on the phone.
    • Enable developer settings in Android Auto by tapping “Version” multiple times.
    • Inside dev settings, try:
    – Change USB mode to “Default” if it is on “Audio only”.
    – Turn off “Add wireless projection to settings” if your car does wired only.
    Some phones default to charge only after an update.

  4. Reset Android Auto and Google Play Services
    • Settings → Apps → Android Auto → Storage → Clear cache, then Clear data.
    • Do the same for Google Play Services.
    • Reboot the phone and re-set up Android Auto in the car.
    After big OS updates, the AA data gets messed up a lot.

  5. Check car head unit settings
    • Delete your phone from the car’s Bluetooth and Android Auto list.
    • On some cars there is a separate “Android Auto” toggle in the infotainment settings, make sure it is ON.
    • If the car has a software update through dealer or USB, check the maker’s support site.
    VW, Hyundai, Kia, Honda, and Ford had AA bugs that got fixed only after head unit updates.

  6. Test a different phone
    • Borrow another Android phone, plug it in to your car with the same cable.
    • If the other phone works fine, the problem is in your phone software.
    • If the other phone also fails, your head unit or USB port is the problem.
    This is the fastest way to narrow it down.

  7. Inspect the USB port and cable behavior
    • Even “good” cables sometimes only charge and do not pass data.
    • Use a known high quality data cable from a good brand, short length, no hubs.
    • Wiggle the connector gently. If it disconnects with light movement, the port is loose.
    A worn USB port in the car or the phone causes intermittent AA crashes.

  8. Android update rollbacks or patches
    • Some recent Android 13 and 14 updates broke AA for certain phones.
    • Check Play Store for Android Auto and Google updates.
    • Join the Android Auto beta in Play Store to see if the beta build fixes it.
    • On some brands, uninstall Android Auto updates, then let it update again from Play Store.

  9. Wireless Android Auto conflicts
    • If you used wireless AA or a wireless AA adapter, unplug or unpair it.
    • Delete the wireless device from Bluetooth and Wi Fi networks.
    • On the phone, turn off “Wireless Android Auto” in the AA developer settings, then try wired.
    Mixed wired plus wireless setups cause endless loops.

If you post your phone model, Android version, car make, model, year, and if the problem started right after a system update, people here can guess the likely cause faster. Right now the top culprits are new OS update, aggressive battery saving, or a flaky USB port even when the cable is fine.

3

If all that stuff from @chasseurdetoiles didn’t fix it, I’d start looking at things slightly outside the usual “phone & cable” bubble. A few ideas that bite a lot of people lately:

  1. Recent Google app / Maps / AA bug
    This sounds dumb, but I’ve seen Android Auto die after a random Google app update rather than a system update. Try this combo:

    • Open Play Store → search “Android Auto,” “Google Maps,” and “Google.”
    • If any of them show “Update,” do it.
    • If they’re already updated and the problem started right after that, hit the three dots and choose “Uninstall updates” for Android Auto and Google Maps, then re-update them fresh. Corrupted app updates cause AA to crash before it even shows up on the head unit.

  2. Bluetooth conflict
    Even if you’re using wired AA, Bluetooth can still nuke the session.

    • In the car’s Bluetooth menu, delete your phone from the paired devices list.
    • On your phone, delete the car from Bluetooth devices.
    • Re-pair from scratch, but when it asks to sync contacts / messages, temporarily say “No” and test AA. Some head units choke on contact sync and silently kill Android Auto.
      If it suddenly works with contacts turned off, that’s your smoking gun.

  3. Messaging / call apps crashing AA in the background
    Telegram, WhatsApp, Samsung Messages, some carrier dialer apps, etc. can crash AA when they fight for notification / call control.

    • Temporarily disable your non-stock messaging apps’ notification access: Settings → Notifications → Advanced → Notification access.
    • Turn off access for “Android Auto” addons, custom call recorders, bubble overlays, or anything that “floats” on top of apps.
      If AA stays stable after that, re-enable them one by one to find the troublemaker.

  4. Overlays and “screen helper” tools
    Stuff like brightness overlay apps, blue light filters, “Edge lighting,” game boosters, or “floating button” utilities can mess AA.

    • Disable: screen dimmers, blue light filters, gaming modes, pop-up heads-up bubble apps, and ad blockers with local VPNs.
    • Also kill any “auto rotation controller” or “gesture navigation enhancer.”
      AA is super touchy with overlays and will just refuse to launch properly.

  5. Car side USB weirdness that isn’t obvious
    Since you already swapped cables, try changing USB ports in the car if you have more than one. A lot of manufacturers have:

    • One port only for charging.
    • One specific port for Android Auto / CarPlay.
      Also, some cars have a hidden “projection” priority: if CarPlay is enabled and the car “thinks” an iPhone was paired before, it can sometimes break AA until you go into car settings and:
    • Turn off CarPlay entirely.
    • Delete any ghost iPhone profiles.
      Sounds unrelated, but I’ve watched AA work again instantly after nuking old Apple profiles.

  6. Time & date / region mismatch
    AA can be super picky if your phone and car disagree about time/date or region.

    • Set your phone to automatic time and automatic time zone.
    • Make sure the car clock is reasonably accurate too.
      If you changed region or used a travel SIM recently, worth checking.

  7. Corrupt car profile for your phone
    Slightly different from what @chasseurdetoiles said about deleting Bluetooth: some cars keep a separate Android Auto profile.

    • In the car, look for something like:
      Settings → Smartphone → Android Auto → Devices
    • Delete your phone there specifically, not just in Bluetooth.
    • Then on the phone: Settings → Connected devices → Android Auto → Forget all cars.
      Then plug in and set it up like it’s brand new.

  8. Hidden “work profile” stuff
    If you have a work profile from your employer / MDM:

    • Some corporate policies block Android Auto silently.
    • If your company recently pushed a new policy, that can explain why it suddenly died.
      Quick test: temporarily pause or remove the work profile (if possible) and try AA. If it works, you’re at the mercy of IT.

If you can, post:

  • Phone model
  • Android version
  • Car make/model/year
  • Whether the problem started right after: system update, app update, dealer visit, or installing some new app

At this point I’d bet on: a buggy recent Google/AA update, a Bluetooth/contact-sync conflict, or some overlay / VPN / work-policy thing that quietly changed in the background.

4

Couple of angles that haven’t really been covered yet and that I’ve seen kill Android Auto out of nowhere:

  1. Storage & corrupted media

    • If your phone’s internal storage is close to full, AA can crash before it negotiates with the head unit.
    • Clear a few GB: delete big WhatsApp/Telegram media, downloads, offline Spotify/Maps data.
    • Also, if you have an SD card with a ton of corrupted tracks or weird tags, some head units flip out when AA tries to index. Temporarily pop the SD card out, reboot, then test.

  2. USB negotiation timing & connection “order”
    Slight disagreement with what people usually say about “just plug it in and wait.” Some cars are very picky about sequence:

    • Start the car, wait until the head unit is fully booted.
    • Then unlock the phone, stay on the home screen, and only then plug the cable into the AA port.
    • If that works but “plug in before start” does not, your car’s USB controller is slow to negotiate data mode.

  3. Phone-side “privacy” features
    Newer Android builds have extra toggles that look harmless but break projection:

    • In Settings → Privacy, temporarily turn off any “limit USB data” or “Restrict USB accessories when locked” type options.
    • On some OEM skins, there is also a “Protect USB” / “USB security” setting that blocks unknown devices. Turn that off and retry.

  4. OEM specific junk (Samsung, Xiaomi, OnePlus, etc.)
    @caminantenocturno and @chasseurdetoiles covered a lot, but vendors add their own gremlins:

    • Samsung: Disable “Android Auto is a sleeping app” in Device care → Battery → Background limits. Also turn off “Put unused apps to sleep” for Android Auto, Google Maps, and Google Play Services.
    • Xiaomi / Redmi / POCO: Turn off “MIUI optimization” temporarily in Developer options. AA sometimes starts working instantly after that.
    • OnePlus / Oppo: In “App battery management,” pick “Allow background activity” for AA and Maps, not “Smart.”

  5. Head unit “mode clash”
    Some cars only want either Bluetooth audio or Android Auto audio, not both:

    • In the car audio source menu, set source to “Android Auto” or “USB” instead of “Bluetooth audio” right after plugging in.
    • If your car shows both icons at once and keeps switching back to BT, manually choose the AA source and leave it there.

  6. Dealer or shop changes that look unrelated
    If the problem started right after a service visit:

    • Ask if they reset or updated the head unit, or changed battery / ECU. A “factory reset” sometimes disables the “Android Auto” projection flag on the car side.
    • Check if they changed regional settings (for example, from EU to US) in the infotainment system. Region mismatch can silently stop projection.

  7. Heat & thermal throttling
    Especially in summer:

    • If the phone is in the sun or charging fast, it may thermal throttle and kill AA but keep charging.
    • Test with the phone in a cooler place, screen off, brightness low. If AA suddenly becomes stable, overheating is likely your culprit.

  8. Hardware degradation on the phone itself
    Not just the car USB:

    • Plug your phone into a PC with the same cable. If it repeatedly drops the connection or randomly flips from MTP to charging only, the phone’s USB controller or port is wearing out.
    • In that case, cleaning the port with a wooden toothpick or compressed air sometimes gives you a few more months of stable AA.

  9. Last resort: full network stack & settings reset
    When all else fails and you know it is phone-side:

    • Settings → System → Reset options → Reset Wi Fi, mobile & Bluetooth.
    • If that does nothing, “Reset all settings” (not erase data) can clear hidden UI / permission bugs that only hit Android Auto.
      This is more aggressive than the app-only resets suggested earlier, but it often fixes those random “was fine, now never works” scenarios.

On the product side, something like a dedicated high quality USB data cable marketed specifically for Android Auto can help, but the unnamed product you referenced has its own pros and cons:

Pros:

  • Usually thicker conductors and better shielding so the data link is more stable under vibration.
  • Shorter length often means fewer drops and faster negotiation between phone and head unit.
  • Some versions are rated for high current, so your phone charges faster while using Android Auto.

Cons:

  • Price is often higher than generic cables, and not all “Android Auto compatible” labels are honest.
  • Stiffer cables can put extra mechanical stress on older or slightly loose USB ports.
  • If the real problem is software (updates, permissions, VPN, overlays) a better cable will not fix anything and can send you on a wild goose chase.

Competitor-wise, the troubleshooting paths suggested by @caminantenocturno and @chasseurdetoiles are solid for battery, Bluetooth, permissions, and overlays. What I would do next, in order, is:

  1. Free at least 3–5 GB phone storage.
  2. Remove SD card if you have one and test.
  3. Disable OEM “optimizations” / USB protection.
  4. Reboot head unit, reset phone’s network settings.
  5. Test phone on another car, and test another phone on your car.

If you share phone model, Android version, car brand/year, and whether a dealer visit or update happened right before this started, people can usually pinpoint which of these quirks is most likely.