Cable, phone, car, in that order
Android Auto sits between three things that all change independently: a phone that updates monthly, a car whose software was finished years ago, and a cable being bent double in a centre console. When it stops working, the cause is usually the cheapest of the three. Work through them in order of likelihood rather than starting with a factory reset, which is where most forum threads begin and where almost no fault actually lies.
Start with the cable, genuinely
- Try a different cable, ideally the one that came with the phone Charging cables and data cables look identical. A cable that charges perfectly may not carry data at all, and this is the single most common cause.
- Keep it short and avoid extensions Under a metre is ideal. Adapters, extensions and hub style chargers in the socket all introduce faults that appear only when the car moves.
- Check both ends for lint A phone socket that has lived in a pocket collects fluff that stops the connector seating fully. A wooden toothpick, gently, with the phone off.
- Wiggle test while it is connected If the session drops when the cable moves, that is the answer and no amount of software work will change it.
- Try a different USB port in the car Some ports are charge only. The one marked with a phone or the Android Auto symbol is the data port.
Advertisement
If the cable is not the problem
| Symptom | Likely cause | What to do |
|---|---|---|
| Nothing happens at all when plugged in | Charge only cable or port | Different cable, data port |
| Connects then drops within a minute | Cable fault or loose socket | Wiggle test, clean the socket |
| Worked until an update | Android Auto or car software version | Update both, clear the app cache |
| Says unsupported or asks to update | Play services or the Auto app out of date | Update through the Play Store |
| Wireless connects then drops | WiFi band or power saving | Disable battery optimisation for Auto |
| Music plays but no maps | Permissions revoked by a cleaner app | Re-grant location and notifications |
| Only works with one phone in the family | Paired device limit in the car | Remove old pairings in the car menu |
Two software causes are worth naming because they are invisible. Battery optimisation kills the Android Auto components in the background, which produces a connection that works for a few minutes and then dies, most often on a phone where a battery saving mode was turned on and forgotten. And permissions that an aggressive cleaner app revoked come back only when you grant them again by hand.
The apps involved, and the ones worth having in the car
Android Auto itself. On newer Android versions it is a system component rather than an app you open, but it still updates through the store and its cache can still be cleared.
The Play Store, which is also where Play system updates arrive. Check for one when Auto starts misbehaving after an update.
Play services. Out of date, it breaks Auto in ways that look like a hardware fault. It updates quietly and occasionally needs a nudge.
The default navigation, and the one most likely to be blamed when the actual fault is a permission it lost.
The alternative on Auto, better in heavy traffic, and worth having as a second option when Maps will not draw.
The most used audio app on Auto. If it appears and Maps does not, the fault is a permission rather than a connection.
Podcasts with proper Auto support, including sensible next and previous behaviour on the steering wheel controls.
The alternative, with strong offline downloads for a commute through a tunnel or a valley.
Audiobooks on Auto, where resuming exactly where you stopped matters more than anywhere else.
Messages read aloud and answered by voice, which is the feature Auto exists for.
Announces messages and takes a dictated reply on Auto, so the phone stays in the holder.
The same, for the family group that lives there instead.
Wireless, and whether it is worth it
Wireless Android Auto needs both a phone that supports it and a head unit that supports it, or an adapter between the two. When it works it is excellent. When it drops, the usual causes are the phone's power saving killing the connection, interference on the WiFi band the link uses, or an adapter that needs its own firmware update, and those are harder to chase than a cable.
- Short journeys with frequent stops
- A phone that stays in a bag
- Cars where the socket is awkward to reach
- Drivers who never use the phone on the move
- Long journeys where charge matters
- Older or borrowed phones
- Anyone who has had a drop out mid route
- Keeping the phone charged for after the drive
Cable, port, power saving, permissions, then updates on both sides. In that order it is usually a five minute fault, not an afternoon.
Frequently asked questions
Why does Android Auto work in one car and not another?
Head unit software differs widely between manufacturers and model years, and some ports are charge only. A phone that works in one car and not another points at the car or its cable rather than the phone.
Do I need the Android Auto app from the store?
On recent Android versions it is built in and the store entry exists mainly for updates and settings. On older versions it is a separate app that must be installed and kept current.
Will clearing the app data lose anything?
Only the Auto settings and the car pairings, which take a minute to set up again. Music, messages and navigation data are unaffected.
My phone connects but the car says unsupported. Now what?
Check for a car software update from the manufacturer, and check Play services and Play system updates on the phone. That combination resolves most version mismatches.
Read next
Nothing has infected your phone. Something you installed has permission, and the fix is a list in settings.
A phone will happily run a keyboard, a mouse and a memory stick. It will not power a desktop hard drive.
Hard and fast are different things. Almost every game confuses them, and these do not.
