Android Automotive

Also, we'll dive into how Apple's Live Activities feature is changing the way iPhone and CarPlay users interact with real-time updates.

Later, we'll break down the differences between Android Automotive and Google Built-in, and what this means for the future of in-car infotainment systems.

CPU overclocking is fading into history as modern chips offer less room for performance gains.

Once a staple for PC enthusiasts, overclocking allowed users to push their CPUs beyond factory settings for extra speed.

With the upcoming iOS twenty-six update, CarPlay will also see enhancements, including a new liquid glass design that mirrors the iPhone's interface.

These updates aim to streamline user interaction and keep essential information easily accessible, enhancing the overall user experience.

Android Automotive and Google Built-in are reshaping the landscape of in-car infotainment systems.

But what sets them apart? While Android Auto is a familiar name, projecting your smartphone's interface onto your car's display, Android Automotive and Google Built-in take a different approach.

around.

And the new infotainment system in here is an Android automotive system.

So it's got Google built in.

But I couldn't actually use it and evaluate it because Mazda didn't have the connectivity turned on in the press car.

I am not sure if the Tucson is in that cohort.

Okay.

So looking more specifically at the Playos software stack, it's built on Android Automotive, but you're not using the Google Automotive services on that.

So for your marketplace, I'm curious, have you at least incorporated Play Services or you mentioned your SDK that you have.

The Model 3 contacted 34 advertising, tracking, and analytics domains, as well as 37 domains from apps integrated into the infotainment system.

Alphabet's domains were most frequently contacted, which is not enormously surprising given the penetration of Android Automotive OS into the sector.

They said, but there were many second level domains that were not necessary for core services like DoubleClick.net and GoogleSyndication.com, which are used for advertising.

Media streaming like Spotify, SiriusXM, and so on are also there, as well as mapping companies like here, TomTom, and Mapbox.

But more importantly, the new Tucson will be the first model from Hyundai in the US to feature the company's new infotainment platform called Cleos Connect.

It's based on Android Automotive's operating system, but users can still wirelessly integrate Apple CarPlay or Android Auto.

Breaking Cleos down to its basic functions, the platform brings a new interface that's meant to be more modern and user-friendly.

It offers more advanced navigation and a new AI voice assistant called Cleo AI.

Who cares? People, not you or I, don't care about platforms.

An expected Android automotive entertainment system will sort all that out.

Volkswagen has no powertrain specifics yet, but honestly, it doesn't really matter.

We know it'll be good enough.

It kind of all just gets bumped into the same thing in my brain.

But GM's infotainment system, which runs Android Automotive, is not as good as Android Auto is.

Yes.

And at this point, it's almost 2027.

This is the part that surprised me.

Android Automotive OS has an API specifically for this.

Named?

The Multi-Display Communications API.

The platform capability is ahead of the products.

It is.

Android Automotive's occupant zones and the multi-display comms API and LG and MediaTek's CMU framework already support exactly the tight two-device integration Daniel is asking about.

The gap is that no automaker has shipped a Waze-style synced navigation co-pilot on top of it.

And that is why you, our listeners, our peers sitting in the CISOs chair, the OT engineers, the PSI or T leads, dealing with these exact complex technical and business challenges are here today.

We are looking at a primary case today that just hit the radar in the August 2026 Android Automotive OS Update Bulletin.

The identifier is CVE-2026-24083.

We are talking about a critical vulnerability in Qualcomm's Snapdragon Auto platforms, specifically impacting chips like the SA8295P and the QCA6696.