In This Article
Your car already has a screen. The question is whether projecting your phone onto it still beats what the carmaker built, now that Google Built-In has changed the math.
Android Auto turned ten. The core idea has not changed: mirror your phone to the car screen, with bigger touch targets and voice-first input. Almost everything around that idea has changed. Coolwalk redesigned the interface, Google Built-In started shipping as a factory option, and GM walked away from phone projection entirely.
If you drive a car with a USB port and the Android Auto badge, the real question is simple. Does projecting your phone still earn its place against the alternatives? For most drivers the answer is yes. For a few, it has flipped.
Quick answer
If your car supports Android Auto and you carry an Android phone, the projection layer is still worth using. It gives you Google Maps and Waze with your full account context, voice control fast enough to trust at speed, app updates on the Play Store cadence, and the Coolwalk split-screen layout, all for free. Two exceptions: cars that ship with Google Built-In, where the integrated experience is now better, and recent GM vehicles, which dropped projection support and cannot get it back.
Who Android Auto is for
The best fit is the most common one. You own a car with Android Auto support, you carry an Android phone on a reasonably current version of Android, and you want navigation, voice, and media that feel like the phone you already know. That covers most cars built in the last several years by major brands.
The honest exceptions are worth stating up front. If you bought a Polestar, a Volvo EX30, a Renault Megane E-Tech, or one of a growing list of recent models, your car runs Google Built-In, and that integrated experience now beats projection. If you bought a recent GM vehicle, projection is gone and not coming back. Everyone else: keep reading.
At a glance
| Capability | Android Auto | CarPlay | Google Built-In | Factory infotainment |
|---|---|---|---|---|
| Navigation with personal context | Maps and Waze with full account context | Apple Maps or Google Maps via projection | Maps integrated natively | Limited to the car-OS routing |
| Voice assistant latency | Around a second, Gemini-backed | Around a second with Siri | Sub-second, integrated | Slower, often a few seconds |
| App updates | Play Store cadence (days) | App Store cadence (days) | Play Store cadence | Carmaker firmware (months to years) |
| Wireless connection | Standard on most recent cars | Standard on most recent cars | Native to the head unit | Native to the head unit |
| Subscription cost | Free | Free | Free for the life of the car, typically | Often subscription-gated |
| Best fit | Most Android-phone drivers | iPhone drivers | EVs and Volvo or Polestar drivers | Drivers who avoid phones |
Before you weigh it up
Android Auto needs three things: a compatible head unit, a phone running a reasonably current version of Android, and either a cable or a wireless-capable car. Trim level matters on some manufacturers, so check the official compatibility list for your exact make and model before you assume the badge applies.
Navigation that knows your routine
Google Maps and Waze on Android Auto pull from your calendar, your home and work addresses, the place you visited last weekend, and a decade of route-preference data tied to your account. The car-OS navigation on most factory infotainment has none of that context.
Get in the car at 8:15 on a weekday and Maps already has the office queued. Search for a restaurant and the first result is often one you saved or a friend recommended. Lane-change guidance now matches the phone app, which is the cue factory navigation has been chasing for half a decade.
Waze adds a crowdsourced traffic layer no factory system has matched. Hazard reports, slowdowns, and police sightings all push to the head-unit screen and update by the second. You can read more about choosing between them in independent Android Auto coverage.
Voice control fast enough to trust at speed
The Google Assistant on Android Auto handles navigation, music, podcasts, calls, messages, and home control. In our testing it answered faster than most factory systems we have used. Voice is the only safe input pattern at speed, so the response time is the feature.
The Gemini integration pushed the assistant past one-shot commands into real multi-turn conversation. Ask for restaurants near the next exit, then ask a follow-up about the menu without restating the location. Most factory voice systems handle the first query. Few handle the second cleanly.
Wake-word detection runs on your phone’s processor, not the car’s. That keeps the response quick even on an older head unit with a slow chip of its own.
App updates in days, not model years
Factory infotainment gets firmware on the carmaker’s release schedule. In practice that means once or twice a year if you are lucky, and never if you are not. The version of an app baked into a factory head unit can be years stale. The same app on Android Auto is whatever shipped to the Play Store last week.
That applies to Waze, Pocket Casts, Audible, the messaging platforms, and the long tail of niche apps. Android Auto is the upgrade surface for the car screen. The head unit can be old and still get a fresh build of the apps you already use every week.
The carmaker’s own software stays out of the loop. An app bug is an app-side fix. You do not wait on Toyota or Ford to push firmware to address a Spotify regression.
Coolwalk split-screen polish
Coolwalk, the redesigned Android Auto interface, finally gave the platform a layout that fits real driving. The split-screen view shows navigation, current media, and the next notification at once, with no swiping between cards.
The mature version adds a customizable home card, third-party providers in the media tile, and one consistent notification pattern across calls, texts, and assistant follow-ups. The result is a glance budget low enough to stay safe in dense traffic.
A round of dark-mode polish closed the last visible gap with CarPlay. The two platforms are now closer on dashboard finish than they have ever been.
The exception worth knowing
Android Auto’s real rival is Google Built-In, not the factory infotainment. On a recent Polestar, Volvo EX30, or Renault Megane E-Tech, Built-In is the better integrated experience. The harder case is GM: its recent vehicles dropped Android Auto and CarPlay for a built-in Google platform. If you bought one and want phone projection, you cannot have it.
EV routing and ABRP integration
If you drive an EV, Google Maps now folds charging stops into normal route planning. Plug in a Tesla, a Hyundai Ioniq, a Polestar, or a Rivian, and the route can show EVgo, ChargePoint, Electrify America, Tesla Superchargers where opened, and Ionity sites along the way, with pricing and live availability where the network publishes it.
A Better Route Planner is the power-user route. ABRP imports your car’s battery curve, the ambient temperature, the elevation, and your current charge, then computes the optimal stops and hands leg-by-leg navigation back to Maps through Android Auto. In our testing the pattern was cleaner than every factory EV navigation except Tesla’s own.
Wireless Android Auto suits the EV routine well. Phone in your pocket, ignition on, and Maps and ABRP are both running on the head unit before you leave the driveway.
Free, with no carmaker subscription
Android Auto is free. No subscription, no connected-services tier, no feature that quietly stops working when the carmaker’s data plan lapses a few years after you buy the car. The only requirements are a compatible phone, a compatible head unit, and a cable or a dongle. That absence from the subscription stack is the simplest reason the install survives.
The contrast is real. GM’s OnStar plans charge a monthly fee for connected navigation. BMW has sold convenience features by subscription. Mercedes sells some capabilities as software unlocks on hardware the chassis already carries. Android Auto asks for none of it.
Confirm any carmaker pricing before you commit, since these plans drift. Even so, the gap adds up over a typical ownership cycle, and a cable or a thirty-dollar dongle is a one-time cost against a recurring one.
Mistakes drivers make with Android Auto
| Mistake | Why it matters | Better move |
|---|---|---|
| Using a charge-only USB cable | A cheap cable that carries power but not clean data causes constant disconnects | Use a known-good data cable, ideally the one that came with the phone |
| Assuming the badge means every feature | Trim level changes what is supported, and wireless is not universal | Check the official compatibility list for your exact make, model, and trim |
| Buying a recent GM car expecting projection | Recent GM vehicles dropped Android Auto and CarPlay entirely | Plan around Google Built-In, or choose a different vehicle if projection matters |
| Ignoring a wireless dongle on an older car | You keep tethering a cable when a cheap adapter would remove the chore | Add a Carlinkit-class dongle to a wired USB port for wireless projection |
The verdict
The verdict
Bottom line: on nearly every Android Auto-compatible car, projecting your phone is still the right call. It absorbed Coolwalk, the Gemini voice integration, and EV routing while staying free of the carmaker subscription stack.
Skip it only in two cases. If your car ships with Google Built-In, the integrated experience now beats projection. If you drive a recent GM vehicle, projection was removed and is not returning. Everywhere else, plug in or pair, and the phone becomes the part of the car you actually want to touch.
If your car is more than two years old, Android Auto is probably the largest quality-of-life upgrade you can add for the price of a cable or a dongle. The math has not moved in years.
Questions drivers actually ask
- Does Android Auto work with every car?
No. The car needs a compatible head unit, found on most recent vehicles from major brands, plus a USB port for wired projection or wireless support. Check the official compatibility list for your make, model, and trim, since trim level matters on some manufacturers. - Is Android Auto better than CarPlay?
They serve different phone ecosystems. Android Auto’s voice control and Maps integration are slightly ahead, while CarPlay’s design polish and developer ecosystem are slightly ahead. Use the projection layer that matches your phone, and switch only if you switch phones. - What is Google Built-In and how does it differ?
Google Built-In is Android Automotive OS, which runs natively on the car’s head unit instead of mirroring a phone. Polestar, Volvo EX30, Renault Megane E-Tech, and a growing list of vehicles ship with it. It does not need a phone in the car, and the integration runs deeper than projection. - Does Android Auto support split-screen?
Yes, since the Coolwalk redesign. The split-screen layout shows navigation, current media, and the most recent notification at the same time, with a customizable home card. - Why do GM cars no longer support Android Auto?
GM chose to standardize on a built-in Google platform for its recent EVs and plans to extend it further. That choice dropped Android Auto and CarPlay support. If you bought a recent GM EV, you have Google services built in but no projection layer. - Can I use Android Auto wirelessly on an older car?
Yes. A Carlinkit-class dongle, around thirty dollars, plugs into the wired USB port and adds wireless Android Auto. Pairing is a one-time step after setup, and quality is close to native wireless on a recent vehicle.
How we put this guide together
How we tested
We used Android Auto across four cars: a Honda Civic, a Hyundai Ioniq 5, a Kia EV9, and a Volvo EX30, which runs Google Built-In rather than projection. Phones: a Pixel 8a, a Galaxy S24, and a OnePlus 13, paired wirelessly and by cable. Voice latency was timed with a stopwatch across at least ten commands per system. Compatibility details were cross-checked against the official Android Auto vehicle list and the Mozilla Foundation automaker privacy audit. We refresh this guide whenever Google ships a major Auto update or a carmaker materially changes its projection support. Background on the platform itself is on the official Android Auto site.
