Android Auto Won't Connect

Android Auto on Gen 6 Mazda Connect is wired only, and it needs four things at once: firmware v70.00.021A or later, the CarPlay/Android Auto USB hub, a data-capable cable, and an Android phone running Android 9.0 or higher with the Android Auto process allowed to run. A failure in any one of them looks the same from the driver’s seat: the phone charges, the screen does nothing. Find the layer that’s broken and fix that one.

This applies to every supported Mazda Connect car (MX-5, CX-5, Mazda3, Mazda6, CX-3, CX-9), because they all run the same CMU, Mazda’s Connectivity Master Unit. Menu names shift slightly by model year and firmware; the mechanism doesn’t.

Start With What The Car Has

Your situation	What’s missing	Where to go
Car never showed Android Auto, pre-2018 build	Probably the retrofit (hub + v70 firmware)	CarPlay/AA options, then this page
Android Auto worked, then stopped	Phone-side settings or stale pairing	Fast checklist below
Works only after replugging or over bumps	Cable or port hardware	Cable and hub sections below
Phone charges, never connects, any cable	USB hub or port fault	USB not working

If the car never had Android Auto, confirm the retrofit before troubleshooting anything. Gen 6 cars built before mid-2018 shipped without the CarPlay/Android Auto stack. The fix is the official retrofit: firmware v70.00.021A or later plus the dual-port USB hub. Neither works alone. Check your version under Settings → System → About (how to check firmware); if you’re below v70 or still have the single stock USB port, no amount of phone-side troubleshooting will help. The full decision guide is CarPlay and Android Auto options and the install procedure is the retrofit page.

Fast Checklist

Try these before factory resets or new hardware.

1. Plug into the phone-icon USB port. On retrofit hubs, only that port carries Android Auto data.
2. Use a short data cable. Google recommends under 1 m (3 ft), USB-IF certified. Charge-only cables are the most common failure.
3. Confirm Android 9.0 or higher. Google raised the wired minimum to Android 9 in July 2024; older phones lost support.
4. Set Android Auto’s battery usage to Unrestricted. Settings → Apps → Android Auto → Battery. Aggressive battery managers (Samsung, Xiaomi, OnePlus) kill the background process mid-handshake.
5. Approve the prompts. First connection requires unlocking the phone and accepting Android Auto’s permissions.
6. Clear the stale pairing. In phone Settings, search “Android Auto” → Previously connected cars → forget the Mazda, then reconnect fresh.
7. Update Android Auto and Google Play services from the Play Store.
8. Reboot the CMU. Hold Nav + Back + Volume/Mute for about 10 seconds; the unit restarts and erases nothing. See reboot and reset.

Wired Only: No Firmware Makes It Wireless

The OEM retrofit and every factory-equipped Gen 6 car run Android Auto over the cable, full stop. Wireless Android Auto exists only through an adapter (Motorola MA1, AAWireless) plugged into the working wired port, presenting itself to the car as a wired phone. That means an adapter inherits every wired fault: if wired Android Auto is broken, the adapter is broken too. Prove wired works before adding or blaming a dongle. Adapter trade-offs and settings are on wireless adapters.

One non-fault while you’re testing: Android Auto on Gen 6 ignores the touchscreen by design. All interaction goes through the commander knob. A screen that shows Android Auto but won’t respond to touch is working as Mazda built it, not failing. Detail on touchscreen while driving.

The Cable Is Guilty Until Proven Innocent

Android Auto negotiates a high-speed USB data session, and it is less tolerant of marginal cables than charging or USB music. The pattern to recognize: the phone charges fine, so the cable “works,” but Android Auto never starts or drops over bumps. Charging needs two wires; Android Auto needs all of them, intact.

• Use a cable explicitly rated for data, under 1 m. The cable that shipped with the phone is the safest test.
• Skip extensions, splitters, and cheap USB-C-to-A adapters; they drop the data lines.
• If a known-good short cable fixes it, throw the old one away rather than rotating it back in.

Phone-Side: The App Gets Killed Or Confused

When Android Auto worked yesterday and not today with no hardware change, the phone is the usual suspect.

• Battery optimization. Set Android Auto, Google Play services, and Google Maps to Unrestricted battery use. Vendor “deep sleep” and app-cleaner features on Samsung, Xiaomi, OnePlus, and similar phones are the classic cause of Android Auto dying seconds after it connects.
• Previously connected cars. Android Auto stores a record per car. Forget the Mazda in the Previously connected cars list (and the Mazda’s Bluetooth entry, since it carries phone metadata), delete the phone from the CMU’s device list, then pair fresh with one phone connected.
• Stale app data. Settings → Apps → Android Auto → Storage → Clear cache, then Clear storage if cache alone doesn’t help. You’ll redo the first-run prompts.
• USB mode. If the phone’s USB notification says “Charging only,” switch it to File Transfer and see whether the session starts.
• Work profiles and parental controls can block Android Auto entirely; test with a personal-profile phone if one is available.

Head-Unit Side: Hub, Port, Firmware

If multiple phones and known-good cables all fail, the car is the problem.

• Port carries no data at all. If USB music from a FAT32 thumb drive also fails in the same port, the fault is upstream of Android Auto: hub, harness, or port. Work through USB not working.
• Reboot before resetting. The Nav + Back + Volume/Mute chord clears a wedged CMU state without touching settings.
• Firmware. Check the version. Below v70 there is no Android Auto at all; v74.00.324A is the tested baseline and includes Android Auto fixes (v74’s rebuilt session handling lets CarPlay and Android Auto hand a phone back and forth cleanly). The path up is get to v74.
• Retrofit hubs can fail mechanically. A hub that works when you press the connector sideways is a worn hub or socket, a parts problem, not a settings problem.

Symptom Table

Symptom	Likely cause	Try
Charges, no Android Auto, any phone	Charge-only cable or wrong port	Short data cable in the phone-icon port
Connects, then drops after seconds	Battery optimization killing the process	Unrestricted battery for Android Auto + Play services
Worked before, dead after phone update	Stale pairing or app data	Forget car, clear Android Auto storage, re-pair
Cuts out over bumps	Worn cable, phone port, or hub socket	New cable first, then inspect ports
No Android Auto option anywhere in the car	Pre-retrofit car or sub-v70 firmware	Check firmware, then retrofit
Screen shows AA but touch does nothing	Normal Gen 6 behavior	Use the commander knob

Same problem, iPhone household: CarPlay won’t connect.

References

Resource	Link
Google: Get started with Android Auto (requirements)	support.google.com
Google: Android Auto app isn’t working	support.google.com
Google: choosing a compatible USB cable	support.google.com
Android 9 minimum, July 2024 change	9to5google.com
Mazda SA-026/21 retrofit FAQ	NHTSA PDF