Why won’t my Android Auto connect in my car anymore?

General
1

Android Auto suddenly stopped connecting in my car even though it used to work fine with the same phone, cable, and vehicle. I’ve checked Bluetooth, USB, app permissions, and tried restarting everything, but it still won’t launch on my car’s display. What else should I try to fix Android Auto not connecting or figure out what’s causing this issue?

2

Had this a few months ago. Same phone, same cable, same car, then one day, nothing. Here is what fixed it, step by step.

  1. Check Android Auto version

    • On your phone, open Android Auto app.
    • Go to Settings, scroll to the bottom.
    • If there is a “Try the new Android Auto” or similar toggle, turn it off and test. That update broke things for some users.

  2. Reset USB defaults on the phone

    • On the phone, go to Settings → Apps → Android Auto.
    • Force stop.
    • Storage → Clear cache. Do NOT clear all data yet.
    • Then go to Settings → System → Developer options.
    • Find “Default USB configuration”.
    • Set it to “File transfer / Android Auto”.
    • If you do not see Developer options, tap Build number 7 times in About phone.

  3. Turn off USB debugging

    • Still in Developer options.
    • Turn off “USB debugging”.
    • Some head units hate when this is on.

  4. Forget the car and re-pair
    On the phone:

    • Android Auto → Previously connected cars → Forget all cars.
    • Reconnect with USB.
      On the car:
    • Go to the infotainment settings.
    • Delete your phone from Android Auto / Smartphone connection menu.
    • Also delete it from Bluetooth devices.
    • Reconnect from scratch, starting the pairing from the car side.

  5. Try a different USB port and a short data cable

    • Use a short, known data cable, ideally the one that came with the phone or a full USB 2.0 data cable.
    • Avoid long or “charge only” cables.
    • Try every USB port that supports data. Many cars have power only ports that look the same.

  6. Disable battery optimizations

    • Settings → Apps → Android Auto → Battery.
    • Set to “Unrestricted” or similar.
    • Also do this for Google Play Services and Google app.
    • Turn off any aggressive battery saver or “optimizaton” apps.

  7. Check USB preference when plugged in

    • Plug the phone into the car.
    • On the phone, pull down the notification shade.
    • Tap USB options.
    • Make sure it says “File transfer / Android Auto”, not “Charging only”.

  8. Check for system updates

    • Update Android Auto in Play Store.
    • Update Google Play Services.
    • Check for system update for the phone.
    • Some cars need a head unit firmware update from the dealer site or via USB stick. Look up your exact car model and year.

  9. Turn off wireless Android Auto if you used it before

    • If your car supports wireless, and your phone keeps trying wireless, it can mess with wired.
    • Android Auto → Settings → Wireless Android Auto → Turn off.
    • Then plug in with USB and test.

  10. Try another phone and another cable

  • If another phone works with the same cable and port, your phone is the issue.
  • If no phone works on that port, the port or the head unit might be failing.
  • Some people report loose center console USB modules after a few years, especially if the plug gets bumped a lot.

My specific fix was a combo of: clearing cache, setting default USB to File transfer, turning off USB debugging, and re-pairing the car and phone. It started working again right away.

If none of that works, I would suspect:

  • Head unit firmware bug after an update.
  • Physical USB port failure in the car or on the phone.
  • Third party “cleaner” or security app killing Android Auto in the background.

Try the quick stuff first: new cable, new port, USB mode check, forget and re-pair. Then move into the deeper settings.

3

Had the exact same “it worked yesterday, now it just hates me” situation. Since you already checked Bluetooth/USB/permissions/restarts, and @viajantedoceu covered most of the sane stuff, here are a few other angles that bite people:

  1. Hidden “projection” / “smartphone integration” toggle in the car
    Some cars randomly turn this off after a software update or low‑voltage event.

    • Dig into the infotainment menus that are not labeled Android Auto directly.
    • Look for “Projection,” “Smartphone Mirroring,” “Phone Projection,” “Connected services,” etc.
    • Make sure it’s enabled for your USB port and not set to some proprietary system instead of Android Auto.

  2. Time & date mismatch
    Sounds dumb, but head units can be super picky.

    • Check the car clock and the phone clock.
    • If the car lost power, its time may be way off and Google services can freak out.
    • Set both to automatic network time, or manually make them match pretty closely.

  3. USB power / voltage weirdness
    The connection can silently fail if the port is under‑powering the phone.

    • If you have a 12V socket + separate USB in the car, unplug other hungry USB stuff.
    • Some cars split power between ports; try with only your phone connected.
    • If you’re using a hub or adapter (USB C‑to‑A dongle, etc.), test without it.

  4. Screen lock & security settings
    On some Android versions, super aggressive lock methods or work profiles block projection.

    • Temporarily set lock to a simple PIN (no work profile, no “device policy” app controlling things) and test.
    • If you use a company MDM / work profile, check if IT pushed a policy recently that disables Android Auto.

  5. Car’s “privacy” / data sharing consent
    A bunch of newer cars have a “consent to data sharing / connected services” prompt that, if declined or skipped, silently kills Android Auto.

    • Look for something like “Data privacy,” “Connected services agreement,” or “Terms & Conditions” in the vehicle/settings menu.
    • Accept whatever it wants, even if it reads like a mild soul‑selling contract, and try again.

  6. Disable weird overlay & “helper” apps
    This is where I slightly disagree with just focusing on battery optimizations. In my case, it was overlays and “assist” apps.

    • Turn off things that draw over other apps: chat heads, floating widgets, screen filters, blue‑light apps.
    • Also temporarily disable call recorders, “driving mode” apps, VPN‑based parental controls, or firewall apps.
      A lot of them hook into notification access or accessibility and somehow break Android Auto’s handshake.

  7. Android Auto dev settings
    Hidden but useful:

    • In Android Auto app, tap “Version” repeatedly to enable developer options.
    • Open the 3‑dot menu → Developer settings.
    • Turn off any experimental flags you may have toggled: “Unknown sources,” “Allow AA in unsupported cars,” “Force logging,” etc.
      A bad flag here can nuke an otherwise fine setup.

  8. Car software “soft reset” that isn’t obvious
    Many head units have a reset that is not the big “Factory reset everything” nuke option. Examples:

    • Press and hold the volume knob for 10–15 seconds.
    • Hold power + home, or power + track skip, depending on the brand.
    • Check the manual for “restart infotainment” or “reset display” only.
      That clears glitches without wiping your radio presets and settings.

  9. Check if Android Auto itself is blocked on the car’s USB
    Some cars let you configure the port: media only, charging only, Android Auto, CarPlay, etc.

    • There might be a submenu per USB port. Make sure the one you’re using is actually set to allow Android Auto.
    • If the car supports both CarPlay and AA, make sure it didn’t randomly lock that port to Apple mode.

  10. System‑level USB stack corruption
    When things got really cursed on my phone, nothing helped until I did:

  • Boot to safe mode and try Android Auto. If it works there, it’s an app conflict.
  • If it still fails in safe mode, back up and consider a full OS repair:
    • On some phones you can reinstall the same firmware with the OEM’s tool (Samsung Smart Switch / Pixel Repair Tool) without wiping data.
    • If your OEM doesn’t support that, a factory reset is the nuclear option, but it has fixed really stubborn AA issues for people.

If you want a quick triage path so you don’t lose your mind:

  1. Test your phone on a different car with Android Auto.
  2. Test a different phone on your car.
  3. Try safe mode on your phone in your car.

That 3‑step combo usually tells you if it’s the phone OS, some third‑party app, or the car/head unit at fault instead of guessing forever.

4

Couple of angles that haven’t really been covered by @jeff or @viajantedoceu, focusing more on “why it suddenly died even though nothing obvious changed.”

1. USB-C wear & “just-a-bit-bad” hardware

Phone ports and car USB modules often fail gradually. Everything still charges, so you assume the port is fine, but data lines are flaky.

Try this very specific test:

  • Plug the phone into a laptop with the same cable.
  • Wiggle the connector gently at the phone side and see if file transfer / MTP drops or reconnects.
  • If charging is stable but file transfer disconnects, that is a classic “data pins worn” problem.

If that is the case, Android Auto will be the first thing to stop working, long before charging does. At that point, software tweaks do almost nothing.

What to do:

  • Clean the phone port with a wooden toothpick (very carefully) to remove lint.
  • If you can borrow a different Android Auto compatible car, test there to confirm it is your phone’s hardware, not your head unit.

2. Corrupted Google Play Services / account side issue

People often hammer on the Android Auto app but forget AA is basically a front end to Google Play Services.

Try:

  1. Remove your main Google account from the phone.
  2. Reboot.
  3. Add the account back.
  4. Then clear cache for:
    • Google Play Services
    • Google app
    • Android Auto

This occasionally fixes weird “handshake” issues where AA never fully initializes when the USB link is detected.

3. In-car profile vs overall system behavior

Some cars treat each driver profile as an isolated environment. If your vehicle switched profiles because of a different key fob or a random glitch, Android Auto can be disabled only on that profile.

Do this:

  • Switch to another driver profile in the car (if available).
  • Try pairing Android Auto there.
  • If it works, then your usual profile is corrupted or misconfigured.

Sometimes a simple delete-and-recreate of your driver profile is faster than digging through obscure menus.

4. Warranty and recall / TSB angle

If your car is relatively new, check for:

  • Technical Service Bulletins (TSBs) about smartphone mirroring or USB hub failures.
  • Extended warranties on the “USB media module” or “connectivity hub.”

Dealers occasionally replace the center console USB module due to known defect, and Android Auto failures are often the only visible symptom.

5. Phone-side logging & reality check

Instead of endlessly guessing, get some data:

  • Enable Android Auto developer mode (tap the version multiple times).
  • Turn on logging.
  • Plug into the car and wait for the failure.
  • Export the logs and skim them for:
    • “USB transport error”
    • “Projection service timeout”
    • “Headunit not authorized”

If you see repeat USB errors, it is almost always hardware. If the logs show projection starting and immediately being killed, that points to software conflict or policy (like a work profile restriction).

6. When to stop tweaking and pick a path

If you have already:

  • Tried multiple cables
  • Tested another phone in your car
  • Tested your phone in another car

and you still have no reliable pattern, I would personally:

  • Prioritize phone warranty repair if the port shows any flakiness with a PC.
  • Or push the dealer to inspect / replace the car’s USB module if multiple phones fail consistently only in that car.

At some point, more toggles and secret menus just waste time.

About the unnamed product title you mentioned: since there is no clear context or actual product description attached, there is not much to recommend or criticize. In general, any Android Auto accessory or tool should be evaluated with the usual pros and cons:

Pros (generic for dedicated AA accessories):

  • Can simplify connection issues if they replace weak OEM hardware.
  • Sometimes add features your car’s stock head unit does not support.

Cons:

  • Another failure point in the chain.
  • Might conflict with firmware updates on either the phone or head unit.
  • Not guaranteed to fix a fundamentally bad USB port or software corruption.

Compared with the very detailed walkthroughs from @jeff and @viajantedoceu, I would not keep looping through the same app / settings recipes forever. Once basic software and pairing checks are done, move quickly to hardware verification and, if needed, warranty or dealer intervention. That is usually where the stubborn “worked yesterday, dead today” Android Auto problems actually live.