Here's the real reason Android Automotive is still kind of a mess in EVs

It's as good and imperfect as you've heard

02 Nov 2024, 18:00 · TechRadar

Features By Myriam Joire published 2 November 2024

(Image credit: Myriam Joire)

Typically these days, when you get in a modern car, there are two ways you can interact with the infotainment system: via phone projection (Apple CarPlay and Android Auto) or via the native infotainment software. Generally speaking, since auto manufacturers aren’t very good at making software, most native infotainment experiences stink, and that’s one of the main reasons why phone projection has become so popular.

But things are different with EVs. As I’ve written about before, good route planning requires access to real-time vehicle data such as battery capacity, state of charge, temperature, energy consumption (which is affected by factors like vehicle speed and climate control settings), tire pressure, etc… Your phone doesn’t have access to this real-time data, making Apple CarPlay and Android Auto ill-suited for accurate route planning.

...in the long run, Apple CarPlay and Android Auto simply aren’t the answer for in-vehicle infotainment

This is why quality native infotainment software is critical, especially in EVs. And this is also why, in the long run, Apple CarPlay and Android Auto simply aren’t the answer for in-vehicle infotainment. But there’s hope. EV startups like Tesla and Rivian are leading the way by offering top-notch native infotainment experiences that deliver best-in-class route planning and infotainment while also seamlessly integrating with your phone.

Basically, Apple CarPlay and Android Auto are band-aids for poor native infotainment software. You don’t project your iPhone’s screen onto your iPad. You login to your iPad with your Apple ID and all your iPhone’s content is immediately available. Chinese manufacturers like Xiaomi and Nio understand this well, providing vertically integrated infotainment experiences in their EVs and across other devices in their ecosystems, including their phones.

Say hello to Android Automotive

Google understands this too, and that’s why, back in 2017, the company launched Android Automotive OS (AAOS) an Android-based open-source OS for in-vehicle infotainment. As with Android on mobile devices, AAOS comes in two flavors. There’s a version without Google’s services and one with Google built-in, using GAS (Google Automotive Services) – the equivalent to GMS (Google Mobile Services) on phones and tablets.

Today, you’ll find Android Automotive (without GAS) on two dozen vehicles from Rivian, Audi, BMW, and Stellantis, and the quality of the infotainment experience varies widely – with Rivian leading the pack. But what’s more interesting is Android Automotive with Google built-in (with GAS), which has the potential to deliver the kind of Google-rich experience available on phones and tablets – complete with Play Store and familiar apps.

Sounds awesome, right? Unfortunately, things aren’t so great out there in the real world. To be honest, Android Automotive with Google built-in is kind of a mess right now. But fear not: there is hope. While some auto manufacturers are stumbling to implement AAOS with GAS properly (General Motors, Honda), others are doing it right (Polestar, Volvo). So, let’s explore what’s wrong, how to fix it, and the role Google and OEMs are playing in all this.

Get daily insight, inspiration and deals in your inbox

Contact me with news and offers from other Future brandsReceive email from us on behalf of our trusted partners or sponsors