Android Auto Greyed Out While CarPlay Works: Phone Fixes
A greyed-out Android Auto entry in Mazda Connect is a phone-side fault: Android below Google’s 9.0 floor, a broken Android Auto app update, stale app data, USB stuck in charge-only mode, or a policy blocking the app. Working CarPlay in the same car proves the firmware, USB hub, and port, which both systems share; that leaves the phone and the Android Auto app.
The entry only renders at all on a Gen 6 Mazda Connect car that has the CarPlay/Android Auto stack: firmware v70.00.021A or later plus the dual-port USB hub. A pre-retrofit car shows no entry anywhere.
Confirm the symptom: greyed out, not missing or failing
Section titled “Confirm the symptom: greyed out, not missing or failing”| What you see | What it means | Where to go |
|---|---|---|
| No Android Auto entry anywhere in the menus | Pre-retrofit car, or sub-v70 firmware | Add Android Auto |
| Entry exists but is greyed out, won’t launch | Phone or Android Auto app blocking the session | This page |
| Connects, then fails or never finishes starting | Cable, port, battery optimization, pairing | Android Auto won’t connect |
| Starts fine, then drops mid-drive | Cable wear, power management, session handling | Android Auto disconnects |
The fix stack: Android version first, wiring last
Section titled “The fix stack: Android version first, wiring last”Work top to bottom.
- Check the Android version. Wired Android Auto requires Android 9.0 or higher; Google raised the floor from Android 8 in July 2024. A phone that worked in this car last year can fall below the floor silently, and the CMU (Mazda’s Connectivity Master Unit, the computer behind the dash) shows the entry greyed out rather than an error. Settings → About phone → Android version.
- Update or roll back. Update Android Auto and Google Play services from the Play Store. If the entry greyed out right after an Android Auto app update, go the other way: Settings → Apps → Android Auto → Uninstall updates, then retest. Owner reports track several greyed-out waves to specific app versions; once it works, let the app update again, since the broken version is usually superseded within days.
- Clear app data. Settings → Apps → Android Auto → Storage → Clear cache, retest, then Clear storage if cache alone doesn’t do it. Clear the Google app’s storage too; Android Auto leans on it, and stale Google app data produces the same greyed-out entry. You’ll redo the first-run prompts.
- Fix the USB mode. Pull down the notification shade while plugged in, tap “Charging this device via USB,” and pick File Transfer. Charge-only mode never opens the data session, and the CMU shows a device it can’t talk to as a greyed-out entry.
- Reset the pairing. Do it on both sides: in the phone’s Android Auto settings, open Previously connected cars and forget the Mazda, then delete the phone from the CMU’s Bluetooth device list. Re-pair with only one phone in the car; a second paired phone can contend for the session and keep the entry greyed out.
- Force-launch the entry. Unplug, replug, then scroll to Applications with the commander knob and select Android Auto directly. Sometimes the session is ready but the CMU doesn’t auto-launch, and selecting the entry manually starts it. Android Auto on Gen 6 Mazda Connect is commander-knob only; Mazda disables the touchscreen in Android Auto by design (details).
- Verify the wire. Short data cable, under 1 m, into the phone-icon port; that’s the only port on the retrofit hub carrying Android Auto data. The full wired chain, cable to hub to firmware, is on Android Auto won’t connect.
If you changed phones and the entry greyed out with the new one, steps 1, 4, and 5 cover it.
Profiles and policies that block Android Auto outright
Section titled “Profiles and policies that block Android Auto outright”- Work profiles. Company-managed devices can have Android Auto disabled by IT policy. The entry stays greyed out and nothing on the phone’s settings screens says why. Test with a personal phone; if that works, the fix goes through your IT department.
- Parental controls. Family Link and similar supervision can block Android Auto on a child’s account.
- Carrier builds. Some carrier-customized phones ship without Android Auto support or with it restricted. Google’s compatibility page is the reference for whether a given phone qualifies.
The tell for all three is consistency: the phone fails the same way in every car, while other phones work in yours.
Related
Section titled “Related”- Android Auto error 8: when the entry launches but throws a communication error
- Wireless Android Auto: adapter options once wired works
References
Section titled “References”| Resource | Link |
|---|---|
| Google: Get started with Android Auto (requirements) | support.google.com |
| Android 9 minimum, July 2024 change | 9to5google.com |