Tell

Full Member
Staff member
Moderator
Its all about "GAS" more of this at the end if you get there... but to summarise your new infotainment system is Android Automotive OS (AAOS) without Google Automotive Services (GAS) called One.Infotainment and it's in the Raval, Tavascan and Born 2026. Attempting in the thread to determine what native apps it will run. Mystery magical tour.

Post two Vags test equipment ;) . AAOP is the Android Automotive Open Source Project. Anyone familiar with Android TV and Fire TV will catch the drift. Both Android projects but one missing Google services or Android verses Windows WSA (Windows Android Subsystem) missing Google services. It's a branch where one is proprietary and the other not. VW has taken the non proprietary route... some will say can I still use Android Auto or Car Play, yes you can but the car will also come with access to it's own AAOS apps... the stage is set.

A quick read of the Raval manual:


Describes online and off line map updates as we know for mib3/4 that use Here Maps cartography. So download is possible and it describes the zonal nature of the online updates which point to mib3/4 cartography.

If we do a Google


The AI overview and links for AAOS the cars system.

>>
2. HERE Navigation for Android Automotive OS (AAOS)Android Automotive OS is an embedded operating system built directly into vehicle dashboards (common in brands like Volvo, Polestar, and Renault). For this platform, HERE offers HERE Navigation, a deeply integrated, white-label connected solution.Key Features: Offers native integration with your vehicle's systems (such as battery and range data for EVs). It supports immersive 3D landmarks, online/offline hybrid capabilities, and highly accurate EV charge-aware routing.How to Use: Because HERE Navigation for AAOS is designed to be fully integrated at the manufacturing level, it is either pre-installed by the automaker or downloadable via the in-car Google Play Store. You can find more information about their commercial and in-vehicle solutions on the HERE Navigation page.
<<

AI generated overviews can be misleading at times however we do find Here Maps developer libraries being talked about on Google search engine..


As I muttered on the board before, for predictive braking and battery regeneration, they need cartography of the road. If you consider that drivers may be split 50:50 by Google Maps and Apple Maps that's a headache to take that data and digitised road speeds to feed into the cars systems, just use one in built system. Here Maps subroutine cartography library and travel information. This I think is the basis, users can optionally run Google Maps, Apple maps as AAOS apps or not. Waze and Sygic AAOS apps are also available on some platforms so may be coming to Vag. Here Maps HereWeGo isn't available as an AAOS but if it's the default it's not required. That may well be the clue.

I'm feeling pretty sure that the Vag AAOS will use Here Maps cartography as Mib3/4 does now as the default, but as now you can switch to the cartography and environment as you please, Android Maps, Apple Maps Carplay, Waze and possibly Sygic. Whatever is in the PlayStore of the car or wifi / usb connection as of now.

Once I see the default maps I'll know for sure whether they have moved away from Here Maps as the default system you see on the in built unit when you press navigation (mib3/4 and mib2 high plus olders mib1/2 standard). But either way drivers who are more happy with other systems still have that option whether through the built in AAOS store or simply connection via their mobile.

The Polestar in Europe uses Google Maps, China it uses Here Maps as the native maps so it doesn't need to be integrated to Google Maps. Given the relationship of Here Maps to the European car industry the pointer is in that direction.

At this point people get confused about Android Auto and Android Automotive about what apps are available. AAOS the later. In the Polestar some apps vanished so they reverted to Android Auto as a stop gap. A moaning point on that forum. Ditto Spotify.

Very much the device list for the car 🚘 is the one you go for, for the cars head end or the Android Auto / Car Play for the mobile 📳. I believe the AAOS apps will be around the brand. You will only see what is deemed to be relevant to the brand. Hopefully all the ones you want are included. But is it in the Playstore ?. Next section. Err...no.

So here we go to the nutshell - with GAS and without GAS it's in the wiki:


So what is GAS ?

//Google Automotive Services (GAS) is the suite of proprietary Google apps and services (like Google Maps, Google Assistant, and Google Play) that run in the vehicle. Android Automotive OS (AAOS) is the underlying open-source operating system that powers the car's digital dashboard.//


NO GAS then it wont be using the inherent Google Maps natively. The wiki above categories these into the two groups. Cupra is non GAS also Harman in association is working with the "Play Store" aspects. As per this from the wiki

In March 2023, the Volkswagen Group announced that its future infotainment system, called One.Infotainment, will be based on Android Automotive (AOSP version) and include an app store developed in partnership with Harman International.

AOSP ?


This is the link to One.Infotainment development:


Because VAG adopted non GAS you wont see the car on the Google Playstore as a device. Like the relationship of Fire TV and Android you don't see the other in their relative app stores since Amazon doesn't support Google services - similar situation - software branch. GAS cars you would see on the Google Playstore as a device. That's not to say you wont see your favourite app like Spotify etc in the cars store which will be currated by Vag.

To GAS or not to GAS that is the question covered here:


I suspose iPhone / Mac folk aren't to bothered about Google Playstore not being part of the cars eco system. Just give me something that works cry. If it's called an Apple car they would be more than happy. ;)

So going round the houses it's pretty certain the default maps will be Here Maps in AAOS (or is it AOSP) but you will be able to pull up any mapping apps within the car's store and use external links to your mobile as of now if it is not in the proprietary VAG store (One.Infotainment - may be a working title of it). Leave the phone at home if all apps were in the AAOS VAG Store... failing that take the phone. Will the dealers old one, use your phone 😉.

We got there :ROFLMAO: . I dont reckon @Syphon won't allow me to pin this, so I wont. Bit technical. Resource ?. Let's let the dust settle.

All exciting stuff and defines the next step in the infotainment unit for 2026 and beyond.... in post 2....
 
Last edited:
So if anybody wants to post up a picture of the apps in the Raval app store that would be helpful to give an idea of what apps are being offered to users. Should have asked @Syphon at the time. No doubt additional apps will be released...

Screen shots will be better than this :eek: ... what you can find on the net. Their test bed.


Feast your eyes on the development test equipment. Perhaps they have hundreds of these looking for bugs 😉.

Screenshot_20260519_230825_Firefox.jpg


Screenshot_20260519_230840_Firefox.jpg


Screenshot_20260519_230846_Firefox.jpg
 
Last edited:
Further reading Vag has taken the BMW approach of non GAS


Supported on BMW Operating System 8.5 and 9.

Listed on that wiki split and interesting to see the BBC sounds currently supports it, my other way in to check for what apps the BBC supports. Basically only BMW at the minute for AAOS and that has to be non GAS.


More about this:


Suspect we'll see BBC Sounds on the VAG system although the BBC have a rigid QA process that is well known on the release of their apps.

BMW also has YouTube in their store for AAOS. An example of the infotainment system implementation:


The last section of the video shows the BMW app store (Connected drive store) with Android Auto and Car Play ~ 6 minutes. This will be the area where the Vag allowed apps would appear, BBC sounds etc. I wonder if we'll get to see European streaming services in the library.

Suspect AAOS Non GAS apps are more easily ported between car platforms accepting screen sizes like Android itself where it comes packaged for different screens. Doubt you'll get side loading, so just what is authorised by the manufactures app store (developer menu locked down). Failing that the old dealer one... use your phone.
 
Last edited:
The Vag direction explained in 2019.


Briefing information for app developers in 2024


And Lifetime support of 15 years on the product


Everything you may need to knows about MIB (ICE cars) and ICAS3 (EV) infotainment software.

A Reddit poster covered the two citing a German website


6.x is the launch software for the Polo.ID


From 13:13 a demonstration of the store of the Polo.ID... apps around it. Well the store wasn't implemented on the button but the apps around it.
Screenshot_20260521_225319_Firefox.jpg



So something similar can be expected on the Cupra implementation of AAOS non GAS but failing that we know how to do it in a Polo.ID... bring up the apps and appstore.

The Harman app store which Vag are using is here. Again for developers but makes an interesting read. The Harman Ready Link Market Place with example screens:


Described:

Ready Link Marketplace is an in-vehicle app store built on Android Automotive OS, giving drivers easy access to their favorite digital content through an intuitive, unified interface. It helps automakers and developers create personalized experiences that generate new revenue streams. Unlike other platforms, OEMs stay in control of the app catalog, store design, and customer relationships.


Example images of the Harman store from that link:
Screenshot_20260524_080916_Firefox.jpg

Screenshot_20260524_080924_Firefox.jpg


Screenshot_20260524_080930_Firefox.jpg
Screenshot_20260524_080935_Firefox.jpg


It's those Cupra apps we are interested in to see what's possible. Leave your phone at home has been said with these cars but probably the iPhone fraternity wont and still use Car Play on it. Android users of the PlayStore apps may find that the apps in the car aren't logged in via the Android eco system, like calendar and dont exist. Spotify will be etc. People will have to get their head around that. A consequence of the non GAS approach and the "walled garden" adopted by car makers that took the non GAS route. Not the end of world you use Android Auto or Car Play and not bother with the Android Automotive apps. Question of choice.

More on the group application store here :


The lure of the apps and the built in mapping verses what is possible via Android Auto and Car Play will probably be a future discussion point for the board with Android Automotive. Obviously some apps will be free but from the screens like Amazon market place and the Google Playstore Harman envisage some apps could be chargeable.
 
Last edited:
On the LHD demo model doing the rounds in June the app store wasn't enabled. It does come with Here Maps cartography. The Sennheiser sound system worked with the immersive controllers sounded good.

Took some pictures for the technically minded:

20260629_160719.jpg


20260629_161849.jpg


So Android 13 which is a bit here nor there since its just the OS it runs on. Two lines above will probably be discussion points as the AAOS rolls out people will say... what have you got.

The fun fact that plastic wrinkle skin on all recent Cupras across the interior is the Basque country earth snake. It came out on one of the launches. Tavascan I recall and is fairly common now inside... doesn't bite.

 
Last edited:
So Android 13 which is a bit here nor there since its just the OS it runs on.

It's interesting that you skip quickly past that point.
Android 13 is the oldest version that is still supported (current version is 16 going on 17). For security reasons, Cupra recently stopped allowing the Cupra App to run on v11 and v12, immediately rendering older smartphones unable to run the app. Users were forced to buy new phones. because there was no mechanism available to upgrade to a newer Android OS.

Now, I don't expect for one minute that Cupra will force owners to buy new cars :eek:, but it will be interesting to see how they plan to upgrade the OS in the car when Android 13 loses support.
 
It's interesting that you skip quickly past that point.
Android 13 is the oldest version that is still supported (current version is 16 going on 17). For security reasons, Cupra recently stopped allowing the Cupra App to run on v11 and v12, immediately rendering older smartphones unable to run the app. Users were forced to buy new phones. because there was no mechanism available to upgrade to a newer Android OS.

Now, I don't expect for one minute that Cupra will force owners to buy new cars :eek:, but it will be interesting to see how they plan to upgrade the OS in the car when Android 13 loses support.
Well its the operating system which is closed to AAOS on their implementation so nodoubt they think its fully protected since they are the gate keeper of the apps and the firmware that runs under it. Presumably they can if they wish update that version of Android.

Bit like my Nvidia Android TV box which runs an old version of Android. Nvidia also customise some of the apps like the BBC one. But unlike AAOS version that Vag use, you can put on it apps from outside the walled garden. They wont work if they are too new since the manifest of the app doesn't allow it. You wouldn't get this with Cupra apps since you dont get anything that isn't managed by the Harman library into it if they block off the developers menu to stop tinkering.

Nvidia did update from one release to another a few years back. This caused a certain amount of chaos with users. Took several months for their staff to finally debug all of it. You could get by. This is where in the mobile / tablet business is better resourced. Bigger business although Nvidia itself branched out from graphic cards and their TV media player to the big business they are now in. But still service and make the trusty Android TV box I have.

Expect if Vag did update Android using those test beds as per the photo they would debug the process. Probably Android developers in closed systems will pile in.

You wouldn't be totally happy to find the car on an update process although that does happen with the mib3/4 where you touch to run the update when home, not in a car park as, has been advised by one poster in the past that was stranded for a couple of hours or so whilst it did it's thing.

For sure Vag will test out shifting between Androids if they feel the need. There will be the AAOS business across car manufacturers so no doubt the mothership will say we are changing the version of Android Automotive based on best practice. Presumably the ones that use Google Automotive Services (GAS) there would be more of a push to change Android version if required than the ones that are non GAS using the manufactures own walled garden of apps. So I dont think its a big deal but it would be if you found an update when wrong.
 
Well, I didn't need a history lesson about every app that might be affected.

My point is that Cupra simply said "Android 11 & 12 are no longer supported, you can't run the Cupra app unless you upgrade and you can't upgrade because your device won't run Android 13 or higher. It's beyond our control. Sorry for the inconvenience."

Therefore, the question is simple, can the Raval MIB be upgraded from Android 13 to a higher version? If Cupra Connect stops running, it doesn't matter what other apps still run, the car is pretty useless.

I'm sure it will be possible, and I'm very familiar with OTA updates as I've had a Born for almost 4 years. I merely pose the question, and I will be asking Cupra Support.
 
That is "consumer" Android you are talking about this is the nuts and bolts Android which is different. Now you will be able to connect your Android phone to it but ofcourse they could say update your consumer Android whilst theirs is lower on release.

We dont know what the process is for AAOS upgrades is. That release 6 you see on the screen I think is their firmware release withing the AAOS wrapper based on the version 13 of Android. All clear as a bell. Dont get too hung up about the "Android 13" bit its their under the covers stuff. Nodoubt enthusiasts will try to fiddle with AAOS but if they get the developers menu locked down they wont get very far. Vag are getting good at locking stuff down these days. So having to buy a new phone thanks to Cupra hasn't got anything to do with what they are using to drive AAOS. Why I brushed over "Android 13" since it isn't a consumer version as such. Just a program. It's walled garden so isn't liable to be hacked but obviously if there are update then they will happen.

Further reading that the AAOS security updates similar to the Windows ones you find:


The May release shows apparently some are on Android 10. Like scientific equipment that contains old code since nothing newer is required. Cash tills are Iike this with long life versions of Windows. Division of consumer development and practical requirements for a business application. AAOS is the business deployment of Android for connected cars.
 
Last edited: