Hubbry Logo
Android AutomotiveAndroid AutomotiveMain
Open search
Android Automotive
Community hub
Android Automotive
logo
8 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Android Automotive
Android Automotive
Android Automotive
View on Wikipedia
from Wikipedia
Android Automotive
Android Automotive running on a Polestar 2
DeveloperGoogle
OS familyAndroid, Linux
Initial releaseMarch 2017; 8 years ago (March 2017)
Latest releaseAndroid Automotive 14[1] / 4 October 2023; 2 years ago (2023-10-04)[2]
Kernel typeMonolithic (Linux kernel)
Official websitebuilt-in.google/cars/

Android Automotive (AAOS), marketed as Cars with Google built-in or colloquially just Google built-in, is an open-source operating system designed for use in vehicle dashboards, based on Android. Introduced in March 2017,[3] it was developed by Google and Intel,[4] together with car manufacturers such as Volvo and Audi.[5] The project aims to provide an operating system codebase for vehicle manufacturers to develop their own distribution. Besides infotainment tasks, such as messaging, navigation and music playback, the operating system aims to handle vehicle-specific functions such as controlling the air conditioning.[5]

Android Automotive is an open source operating system and, as such, a car manufacturer can use it without the proprietary Google Automotive Services (GAS)[6][7]—which is a car equivalent to the Google Mobile Services, i.e. a collection of applications and services like Google Maps, Google Assistant, and Google Play—that OEMs can license and integrate into their in-vehicle infotainment systems. In contrast to Android Auto, Android Automotive is a full operating system running on the vehicle's device, not relying on a smartphone to operate.[8] As such, it has access to a limited number of apps on the aforementioned Google Play Store. Volvo, Renault, Ford and GM are using AAOS with GAS. In order to communicate with in-vehicle networks (IVI) such as the CAN bus, Android Automotive uses the Vehicle Hardware Abstraction Layer (VHAL), which serves as a bridge between the vehicle's hardware and software components.[9]

History

[edit]

The operating system was first announced by Google in March 2017.

In February 2018, Polestar announced the Polestar 2, the first car with built-in Android Automotive. The Polestar 2 with Android Automotive is available since July 2020.[10]

In September 2018, the Renault–Nissan–Mitsubishi Alliance announced a technology partnership to embed the Android Automotive operating system in the group's vehicles starting in 2021.[11]

In April 2019 Google opened up the APIs for developers to start developing applications for Android Automotive.[3]

In September 2019 General Motors announced that they will use Android Automotive to power the infotainment systems in its cars starting in 2021.[12]

In July 2020, Stellantis (formerly Groupe PSA and FCA Group) announced they would power their infotainment systems with Android Automotive OS. This announcement was revoked in 2022.[13]
Some vehicles from the group, like the 2021 Dodge Durango and Chrysler Pacifica, are already using the Android Automotive-based Uconnect 5,[14] without the Google Automotive Services (GAS).[15]

In February 2021, Ford announced a partnership with Google that would bring Android Automotive to Ford and Lincoln vehicles, starting in 2023.[16]

In May 2021, Lucid Motors revealed that the Lucid Air was using Android Automotive for its infotainment system,[17] but without the Google Automotive Services (GAS).

In September 2021, Honda announced that it would use Google's Android Automotive OS in its cars starting in 2022.[18]

In June 2022, BMW announced that it will be expanding its BMW Operating System 8 and integrating Android Automotive into certain models, starting in March 2023.[19] In January 2023, during the Consumer Electronics Show, BMW revealed that BMW Operating System 9 will be based on Android Automotive but without the Google Automotive Services (GAS). BMW OS 9 will feature the Aptoide app store, but lower OS versions will not.[20]

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

In May 2023, Google introduced Android Automotive OS 14 which enabled new capabilities for navigation apps allowing them to integrated with the gauge cluster and multi screen support to expand new experiences between the driver and passengers.[23]

In June 2023, Polestar announced its intention to use the Meizu Flyme Auto system in vehicles destined for the Chinese market.[24]

In October 2023, Porsche announced a collaboration with Google which will bring Android Automotive to the carmaker’s future vehicles. Google Maps, Google Assistant, and a wide variety of apps will be available through the Google Play Store.[25]

In December 2024, Hyundai Motor Group announced it adopted Google’s Android Automotive Operating System (AAOS) to further broaden its software ecosystem.[26]

In July 2025, Mazda revealed its all-new 2026 CX-5, the first model coming with Google built-in.[27]

Vehicles with Android Automotive (with GAS)

[edit]

Vehicles with Android Automotive (without GAS)

[edit]

See also

[edit]

References

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

Android Automotive

View on Grokipedia
from Grokipedia
Android Automotive OS (AAOS) is an open-source operating system developed by specifically for in-vehicle systems, running natively on automotive hardware to deliver integrated , media playback, connectivity, and basic controls without relying on a paired . Unlike projection-based systems like , AAOS functions as a standalone platform, enabling direct app downloads from the Google Play Store and seamless access to services such as and . This architecture allows automakers to customize the OS for their vehicles while leveraging Android's ecosystem for scalability and openness. Development of Android Automotive OS began around 2014 as an internal project, with its public announcement in May 2017 through partnerships with automakers including and , and the first commercial deployments in production vehicles occurring in 2020 with the Polestar 2. The OS has progressed through annual releases aligned with core Android versions, such as Android Automotive 11 (based on ), Android Automotive 12 (based on Android 12L), and up to Android Automotive 15-QPR1 (based on Android 15) as of late 2025, incorporating enhancements in security, performance, and automotive-specific APIs. These updates have focused on improving system stability, supporting larger displays, and enabling features like predictive back gestures and enhanced privacy controls for in-car use. Key features of Android Automotive OS emphasize driver safety and personalization, including voice-activated controls via for hands-free operation, real-time navigation with that integrates traffic and EV charging data, and entertainment options through apps like and available directly on the head unit. The platform supports over-the-air (OTA) updates for continuous improvements, middleware for vehicle hardware integration (such as climate and seat adjustments), and developer tools for creating car-optimized apps with guidelines for distraction-free interfaces. Additionally, it provides robust connectivity options, including , , and telematics, while adhering to automotive standards for reliability in embedded environments. As of 2025, adoption of Android Automotive OS—often branded as "Google built-in"—has grown significantly, powering infotainment in vehicles from major manufacturers such as (e.g., XC40, XC60, XC90), (e.g., , 3), brands like (e.g., Lyriq, CT5) and Chevrolet, Ford (e.g., 2025 Explorer), Honda (e.g., 2025 Accord Touring, 2026 Prologue), and (e.g., ZDX). This expansion reflects its appeal for providing a consistent, updateable across diverse vehicle lineups, with supported in nearly 250 million vehicles worldwide as of May 2025 and over 50 models featuring Android Automotive OS.

Introduction

Definition and Purpose

Android Automotive OS (AAOS) is a full-stack, open-source variant of the Android platform, specifically optimized for automotive applications, that runs natively on in-vehicle hardware to power systems. As a base Android platform, it delivers core services such as , , and media playback directly within the vehicle, enabling the execution of pre-installed system applications alongside optional third-party apps downloaded by users. This extends the core Android framework with automotive-specific enhancements, providing a scalable foundation for in-vehicle experiences without dependence on external hardware. The primary purpose of AAOS is to empower car manufacturers, or original equipment manufacturers (OEMs), to create highly customized solutions that integrate seamlessly with various functions, including climate control, systems, and other onboard controls. By operating independently of smartphones, AAOS allows for a standalone interface where drivers can access and install compatible apps directly on the car's head unit, fostering a consistent and distraction-minimized driving environment. This design prioritizes openness and flexibility, enabling OEMs to differentiate their products through tailored user interfaces and features while leveraging Android's robust ecosystem of tools, APIs, and developer expertise. Initial development of AAOS focused on delivering a customizable platform that builds on Android's core capabilities to support advanced in-vehicle , distinguishing it from projection-based systems like that mirror content onto the car's display.

Comparison with Android Auto

functions as a mobile application that projects a 's interface onto a vehicle's display through a wired USB or wireless connection, thereby depending on the phone's processing power, storage, and installed applications to deliver features. In contrast, Android Automotive OS (AAOS) serves as a standalone integrated directly into the vehicle's hardware, enabling users to install applications natively on the car's system and sign in with a independently of any external device. This fundamental architectural distinction positions as a projection-based solution that mirrors the phone's capabilities and limitations, while AAOS operates as an autonomous platform optimized for in-vehicle use without requiring constant . A primary difference lies in their integration and customization potential: AAOS provides manufacturers with deeper access to the vehicle's in-vehicle network (IVN) and sensor data, facilitating native, vehicle-specific adaptations such as tailored user interfaces and hardware controls that align with the car's design and safety requirements. Android Auto, however, is constrained to a standardized projection layer that adapts phone apps for driving but cannot directly interface with vehicle-specific systems beyond basic display and audio output. Furthermore, AAOS supports offline functionality for core operations and installed apps, allowing the system to function without phone connectivity or internet access for essential tasks, whereas Android Auto ceases to operate effectively if the phone disconnects, inheriting the phone's connectivity dependencies and potential limitations in coverage or battery life. Regarding updates, AAOS incorporates over-the-air (OTA) capabilities inherent to the Android ecosystem, enabling direct and software updates to the vehicle's managed by the manufacturer or , which enhances and adds features without phone intervention. updates, by comparison, are phone-dependent, requiring the user to update the or device OS separately, with changes propagating only during active connections. In terms of , AAOS can include as an optional in compatible vehicles, allowing users to switch between the native OS and phone projection modes, but cannot host or emulate AAOS functionalities due to its reliance on external hardware. This one-way compatibility underscores AAOS's role as a more comprehensive, vehicle-centric platform in the automotive ecosystem.

History

Origins and Early Development

The development of Android Automotive began around 2014 as an internal Google project, with collaborations starting in 2017 between Google and Intel, alongside automakers such as Volvo and Audi, to create a variant of the Android operating system tailored specifically for automotive infotainment systems. The platform was publicly announced in March 2017 as an open-source operating system designed to supplant proprietary solutions in vehicles and support the creation of dedicated app ecosystems for in-car use. This initiative aimed to leverage Android's flexibility to deliver seamless connectivity and user experiences directly embedded in vehicle hardware, independent of personal smartphones. Early development efforts prioritized hardware optimizations suited to automotive environments, including collaborations for testing on prototypes to ensure reliability under real-world conditions. software builds were based on Android 8.1 (), with a focus on accommodating constraints such as limited processing resources, power efficiency, and compliance with automotive safety certifications like ISO 26262. contributed significantly by supplying reference hardware platforms, notably the Atom E3900 series system-on-chips, which formed the basis for development kits distributed to original equipment manufacturers (OEMs) to accelerate integration and prototyping.

Key Milestones and Releases

The first commercial deployment of Android Automotive OS took place in 2020 with the , which used an early implementation based on Android 9 () and marked the initial to feature full Google integration including , , and Store directly embedded in the infotainment system. Key releases of Android Automotive OS have aligned with major Android versions, introducing automotive-specific enhancements while building on the core platform. Official stable releases for OEMs began with Android Automotive 11 (based on ), which arrived in 2021 and included foundational support for multi-display capabilities, enabling better management of instrument clusters and infotainment screens. The Android Automotive 12 (based on Android 12L) release in 2022 incorporated Material You dynamic theming adapted for automotive interfaces, along with improvements to system power and performance for cluster displays. Android Automotive 13 (based on ) in 2023 focused on enhanced privacy controls and new automotive-specific APIs for connectivity and framework integration. The Android Automotive 14 iteration in 2024 emphasized better power management through updates to the display and , optimizing resource use in hardware. Finally, Android Automotive 15 (based on Android 15) launched in late 2024 with quarterly platform updates (such as 24Q3 and 24Q4), including AI enhancements for improved system interactions. Significant milestones have shaped the platform's evolution. In 2020, Google expanded open-sourcing efforts by integrating more automotive components into the Android Open Source Project, facilitating greater OEM customization. By 2022, adoption expanded notably in electric vehicles through partnerships with additional OEMs, building on early EV implementations. In 2025, integration of Gemini AI was announced at , enabling advanced voice assistance and predictive features for safer, more intuitive in-car experiences. Additionally, hardware support shifted from initial processors to broader compatibility with and SoCs by 2022, supporting diverse vehicle architectures.
Android Version BaseRelease YearKey Automotive Enhancements
Android 112021Multi-display improvements
Android 12L2022Material You theming, power optimizations
2023Privacy enhancements, car APIs
2024Display and power management
Android 15Late 2024Quarterly updates, AI features

Technical Overview

System Architecture

Android Automotive OS employs a multi-layered designed to support in-vehicle while enabling customization and integration with automotive hardware. The topmost hosts user applications, including OEM-customized apps and third-party software, allowing vehicle manufacturers to tailor the experience without altering core system code. Beneath this lies the Framework Layer, which provides adapted Android APIs for automotive contexts, such as system UI elements optimized for driving scenarios, ensuring consistent app development across displays. The manages essential functions like the Human-Machine Interface (HMI) for interactions and the Vehicle Layer (VHAL), which standardizes access to vehicle such as speed and fuel levels. At the base, the Layer (HAL) interfaces with physical components, including the for communication with electronic control units (ECUs) and sensors for environmental . This structure rests on a optimized for real-time automotive requirements, incorporating low-latency scheduling to handle time-sensitive tasks like . Key components enhance security and communication within this architecture. Android's Trusted Execution Environment (TEE) supports secure boot processes and isolates sensitive applications, protecting critical operations like key management from tampering. Additionally, the Binder inter-process communication (IPC) mechanism enables efficient data exchange between processes, particularly in multi-display setups where instrument clusters and central infotainment screens require synchronized updates. As an open-source platform derived from the Android Open Source Project (AOSP), Android Automotive allows OEMs to modify upper layers for proprietary features while maintains dedicated branches, such as those in the automotive manifest at android.googlesource.com, to incorporate vehicle-specific extensions. This structure supports variants like non-Google Automotive Services (non-GAS), where manufacturers build from AOSP without proprietary integrations. In contrast to standard Android, which targets mobile devices, Android Automotive features embedded optimizations to minimize resource usage in constrained vehicle environments and support for automotive standards, including for risk classification via Automotive Safety Integrity Levels (ASIL). These adaptations ensure reliability in safety-critical contexts, with added frameworks like DrivingUxRestrictions to limit distracting features during operation. As of 2025, the architecture aligns with Android Automotive 15 (based on Android 15), incorporating enhancements in security and automotive-specific APIs.

Vehicle Hardware Integration

Android Automotive OS interfaces with vehicle hardware through the Vehicle Hardware Abstraction Layer (VHAL), which provides standardized APIs for accessing critical car data such as vehicle speed, fuel level, and HVAC status. The VHAL abstracts underlying vehicle network protocols, including Controller Area Network (CAN), Ethernet, and Media Oriented Systems Transport (MOST), enabling the OS to retrieve and control vehicle-specific properties without direct dependency on proprietary hardware implementations. This layer ensures compatibility across diverse automotive architectures by defining properties in AIDL (Android Interface Definition Language) for Android 13 and later, or HIDL for earlier versions, allowing OEMs to implement custom mappings to their hardware while maintaining a consistent interface for the Android framework. Integration with display hardware, such as head units, instrument clusters, and rear-seat entertainment systems, relies on tailored display APIs and multi-window management capabilities optimized for automotive environments. The Presentation API enables apps to project content onto secondary displays, supporting resolutions from 720p up to 4K, while the WindowManager handles multi-display configurations for seamless operation across screens like LVDS-connected instrument clusters or HDMI-linked rear displays. For instrument clusters, virtual displays facilitate graphics rendering without requiring separate audio or touch inputs, using hardware interfaces like Ethernet AVB for low-latency data transfer between the main infotainment processor and cluster hardware. Rear-seat displays, similarly, leverage these APIs but with limitations on full activity projection and concurrent user sessions to prioritize safety and resource efficiency. The OS supports a range of automotive-grade processors, including series for high-performance and A3900 for earlier implementations, ensuring scalability from entry-level to premium vehicles. Power management features align with automotive standards by integrating with the Vehicle Master Control Unit (VMCU) via VHAL to handle states like full-on operation, suspend-to-RAM for quick wake-up, and or hibernate modes that minimize energy use during vehicle off cycles. The CarPowerManagementService orchestrates these transitions, supporting always-on capabilities for essential functions while complying with protocols like CAN for power state notifications, thus preventing battery drain in parked vehicles. Security in hardware integration emphasizes verified boot chains to ensure only authorized firmware loads during startup, combined with over-the-air (OTA) update mechanisms that use A/B seamless updates for rollback protection and full-disk encryption. These OTA processes, managed through the recovery partition, synchronize OS updates with ECU firmware flashing by leveraging VHAL for vehicle-wide coordination, allowing OEMs to apply signed updates to electronic control units via secure channels without compromising system integrity. This approach mitigates risks in connected environments by enforcing cryptographic verification at boot and during updates, aligning with automotive cybersecurity practices.

Features and Capabilities

Infotainment and User Interface

Android Automotive OS features a (UI) tailored for vehicular environments, emphasizing and through elements like multiple bars positioned on the left, bottom, and right sides of the screen. These bars can be toggled for visibility using physical controls such as the volume rocker or buttons, allowing seamless interaction while . The UI supports multi-window modes, including split-screen functionality, to enable simultaneous use of apps like and media without requiring full-screen switches. Layouts incorporate large icons and simplified visuals optimized for larger in-vehicle touchscreens, with gesture-based controls for swiping and tapping to reduce . Additionally, the accommodates physical input methods, such as rotary dials common in certain OEM implementations, for precise menu without diverting attention from the road. The infotainment capabilities of Android Automotive OS center on native app integration, particularly in vehicles equipped with Google Automotive Services (GAS), which provide access to the Store for direct downloads. Users can install and run media applications like and , offering streaming of music, podcasts, and radio directly through the car's . Gaming is supported via , allowing light titles to be played during parked sessions. Personalization in Android Automotive OS is facilitated through multiple user profiles, enabling distinct configurations for different drivers or passengers. Each profile can sync with a to restore settings, themes, and app preferences across vehicle sessions, ensuring a consistent experience without manual reconfiguration. This includes tailored home screen layouts, media libraries, and UI adjustments, all isolated for privacy in a shared device environment. Voice interaction forms a core part of the user interface, with built-in integration of for hands-free control of media playback, navigation queries, and general assistance. In 2025, this evolves with the introduction of Gemini, Google's advanced AI model, providing contextual suggestions and more for tasks in vehicles with Google built-in. Safety restrictions limit interactive UI elements during motion, prioritizing voice and minimal visual feedback to minimize driver distraction.

Connectivity and Safety Enhancements

Android Automotive OS incorporates robust connectivity options to facilitate seamless integration with external networks and vehicle ecosystems, enabling features such as over-the-air (OTA) updates and cloud-based synchronization. The system supports connectivity, including mandatory profiles like Hands-Free Profile (HFP), Advanced Audio Distribution Profile (A2DP), Audio/Video Remote Control Profile (AVRCP), and Phone Book Access Profile (PBAP), with recommended support for (BLE) and Message Access Profile (MAP), allowing for hands-free calling, media streaming, and device pairing in the vehicle environment. Additionally, as an Android-based platform, it leverages standard capabilities for local network access and data transfer, while vehicles equipped with built-in services often include modem integration to support high-speed data for , streaming, and real-time vehicle diagnostics. technology is also compatible, enabling always-on cellular connectivity without physical SIM cards for subscription-based services like remote diagnostics and location tracking. For troubleshooting connectivity issues related to Google services, users should first check the connectivity status, often indicated by symbols or within settings menus that vary by manufacturer. Ensure that vehicle data plans, hotspots, or internet terms of service are enabled and active, such as by navigating to relevant privacy or connectivity settings. If no internet connection is available, restart the infotainment system by pressing and holding an appropriate physical button—such as the END CALL button on the steering wheel for General Motors vehicles or the defroster button for Volvo models—for 10-20 seconds until the system reboots, ensuring the vehicle is in PARK. Additionally, activate any required premium connectivity subscriptions through the manufacturer's app or online portal if not already enabled. Exact steps may differ by vehicle manufacturer and model. To enhance road safety, Android Automotive OS implements strict driving mode restrictions through its Driver Distraction Guidelines (DDG), which categorize app behaviors into distraction-optimized states based on vehicle conditions. In the parked state, no restrictions apply, allowing full app functionality; during idling, video playback is prohibited to minimize visual distractions; and in driving mode, interactive elements like keyboards, text input, and complex gestures are restricted, ensuring apps remain safe for use while the vehicle is in motion. These guidelines require apps to be explicitly tagged as "Distraction Optimized" to operate under restrictions, with the system automatically pausing or simplifying user interfaces to prevent driver diversion. Do Not Disturb (DND) modes further support this by providing configurable policies that suppress non-essential notifications and visual effects, accessible via a dedicated activity in the system's settings. These safety mechanisms align with international standards, such as UNECE regulations aimed at mitigating driver distraction through controlled in-vehicle interactions. Privacy protections in Android Automotive OS build on core Android security models, emphasizing controlled access to sensitive vehicle and user data. Scoped storage limits app access to external files, requiring explicit permissions for any shared resources and preventing unauthorized data modification or leakage. Vehicle-specific data, such as engine details, climate controls, and steering information, is governed by dedicated permission groups like CAR_MONITORING, which filter access through the Vehicle HAL (Hardware Abstraction Layer) to ensure only authorized apps can query or control automotive systems. For connected services, file-based and metadata encryption schemes protect stored data, with vehicle-bound encryption tying keys to the hardware to safeguard against unauthorized extraction during theft or transfer. End-to-end encryption is applied to communications involving Google services, such as cloud syncing for preferences and updates, maintaining data confidentiality across networks. These features collectively reduce risks associated with data exposure in a connected vehicular context.

Deployments

Vehicles with Google Automotive Services

Google Automotive Services (GAS) integrates a suite of Google applications directly into the Android Automotive operating system, enabling native access to services such as for real-time navigation, the Store for app downloads, for voice controls, and for video streaming, all without the need for phone tethering or projection. This bundle enhances the in-vehicle experience by embedding the Google ecosystem into the vehicle's system, allowing seamless interaction with familiar tools tailored for automotive use. Several automakers have adopted Android Automotive OS with GAS in their vehicles, starting with early implementations in electric models. The was the first to debut this integration in 2020, featuring a 11-inch touchscreen powered by GAS for navigation, media, and voice assistance. followed with the XC40 Recharge in 2021, incorporating GAS to provide over-the-air (OTA) updates for apps and system improvements directly from . In 2023, introduced GAS in the Cadillac Lyriq, an all-electric SUV on the platform, where it supports cloud-linked personalization such as syncing user preferences across devices. By 2024, adoption expanded to additional models, including the , which runs Android Automotive OS 12 with GAS for integrated services like built-in mapping and app ecosystem access. further broadened its rollout across Ultium-based , such as the , enabling OTA app updates for entertainment and productivity features while parked or in motion. Other notable 2024+ implementations include the and 4, and EX90, , , and (released starting 2024), all leveraging GAS for a unified experience. In 2025, began releasing new video streaming and gaming apps to certified GAS vehicles starting in February, expanding entertainment options. Additionally, select models like integrated Gemini AI for enhanced voice assistance. Looking ahead, announced plans to integrate Android Automotive with GAS starting in 2026 models across Hyundai, , and Genesis brands, emphasizing enhanced navigation and infotainment through collaboration. These implementations highlight a seamless , where OTA updates deliver new apps and features—such as video streaming expansions in 2025 for select models—and cloud-linked maintains user settings like playlists and routes across vehicles. The primary drivers for adopting GAS-enabled Android Automotive in these vehicles, particularly electric models, stem from the enhanced provided by familiar services, which streamline , , and connectivity to boost driver and passenger satisfaction.

Vehicles without Google Automotive Services

Non-GAS versions of Android Automotive OS leverage the open-source platform to enable manufacturers to develop and curate their own applications, thereby reducing reliance on 's ecosystem for improved data privacy and tailored vehicle integrations. This approach allows OEMs to prioritize proprietary services while maintaining compatibility with core Android features like vehicle layers for accessing systems such as HVAC and . Prominent examples include Rivian's R1T and R1S models introduced in 2022, which run a customized iteration of AAOS without GAS to deliver an integrated experience focused on Rivian-specific apps for navigation, media, and vehicle controls. incorporated non-GAS AAOS into vehicles like the 2024 iX and subsequent models, powering the iDrive 9 interface with BMW-curated applications for connectivity and entertainment while supporting projected . Audi's 2024 Q6 e-tron utilizes this configuration for its MMI system, emphasizing Audi-developed features alongside basic open-source capabilities. has deployed non-GAS AAOS in select 2024 models, with expansions by 2025 to additional lineup including legacy vehicles from brands like and ; in May 2025, pivoted from its Amazon SmartCockpit project to adopt Android Automotive OS more broadly. These implementations typically highlight OEM-specific applications, such as 's driver profiles and 's ConnectedDrive services, but face limitations including the absence of a native Store, relying instead on pre-approved or sideloaded apps for expanded functionality. Challenges in this space often involve slower growth of third-party app ecosystems and occasional integration hurdles with vehicle hardware, as evidenced in early and rollouts where custom UI adaptations led to varied user experiences compared to GAS-equipped counterparts. explored similar non-GAS adaptations in preliminary development before pivoting to proprietary solutions to address these integration complexities.

Market Adoption and Future

As of 2025, the Android Automotive OS (AAOS) market is valued at USD 895.6 million globally, reflecting its expanding role in vehicle systems. This valuation underscores adoption among new premium and (EV) models worldwide, particularly among manufacturers prioritizing connected and software-defined architectures. The platform's penetration is driven by its open-source foundation, which enables cost efficiencies for original equipment manufacturers (OEMs) compared to proprietary systems, alongside a burgeoning developer that has produced over 300 automotive-specific apps as of mid-2025. Key trends include rapid integration in the EV segment, where AAOS powers a majority of new Polestar and Volvo models, leveraging partnerships such as those with Qualcomm for advanced chipsets like the Snapdragon Digital Chassis. In 2025, adoption has continued to expand in various segments, with planned integration in Hyundai vehicles starting in 2026, facilitated by collaborations that enhance hardware integration and over-the-air updates. Regulatory mandates in the European Union and United States for enhanced vehicle connectivity and data security further propel this momentum, aligning with AAOS's support for standardized APIs and safety features, including the EU Data Act's requirements for data sharing in connected vehicles effective September 2025. Regionally, leads with strong uptake from brands like and , capturing a significant portion of premium segment deployments due to favorable policies on digital cockpits. follows closely, bolstered by implementations in and Ford vehicles, where AAOS facilitates seamless integration with local standards. In , adoption is growing through EV exports and international partnerships, though domestic systems like remain prominent. Overall, these dynamics highlight AAOS's maturation as a versatile platform, with OEMs and Tier-1 suppliers accounting for 78.6% of deployments in 2025 and over 50 models using Android Automotive OS with built-in as of mid-2025.

Challenges and Emerging Developments

One significant challenge in Android Automotive OS deployment is software fragmentation across original equipment manufacturers (OEMs), which results in inconsistent user experiences due to varying customizations and update cadences. This fragmentation arises as OEMs like Ford and tailor the OS to their hardware and branding, leading to differences in feature availability and performance that hinder a unified ecosystem. High development costs also pose a barrier, for up to 20% of a vehicle's overall R&D , as integrating Android Automotive requires substantial in layers and testing for automotive-grade reliability. Security vulnerabilities in connected systems further complicate adoption, exemplified by 2024 hacking incidents where researchers demonstrated remote exploits in Android Automotive units via over-the-air (OTA) channels, exposing risks to vehicle controls. These incidents highlighted weaknesses in the OS's default configurations, prompting calls for enhanced and intrusion detection. Additionally, the slow app process, which involves rigorous safety and performance validations, limited early growth, though the has expanded to over 300 apps by mid-2025 with ongoing additions. Criticisms of non-Google Automotive Services (GAS) implementations include persistent user interface bugs, such as those reported in ' 2024 Ultifi system, where navigation glitches and slow responsiveness degraded user satisfaction. Moreover, dependency on for GAS updates creates bottlenecks for OEMs opting out, as they must independently manage security patches and feature rollouts, often lagging behind GAS versions. Emerging developments aim to address these issues through AI expansions in 2025-2026, integrating 's Gemini model for features that analyze vehicle to forecast component failures and suggest optimizations. OTA standardization in Android Automotive 16, released in 2025, introduced unified protocols for seamless updates across OEMs, reducing fragmentation by enforcing consistent delivery mechanisms. Increased integration with (V2X) communication and advanced driver-assistance systems (ADAS) is also underway, enabling Android Automotive to process real-time traffic and for enhanced . Market projections anticipate a push toward 50% adoption in new vehicles by 2030, driven by deepened -OEM collaborations that streamline licensing and co-development. Solutions in progress include Google's Automotive Summit initiatives, launched in , which foster unified standards through OEM roundtables focused on interoperability and shared APIs to mitigate fragmentation. Hardware advancements, such as 5nm process chips from partners like , promise better power efficiency and faster processing for Android Automotive, reducing thermal issues in embedded systems. Regulatory adaptations, including updates to UNECE WP.29 cybersecurity regulations in 2025, mandate robust and compliance for connected vehicle OS like Android Automotive, aiming to standardize protections against exploits.

References

  1. https://source.android.com/docs/automotive/start/what_automotive
  2. https://developers.google.com/cars/design/automotive-os
  3. https://9to5google.com/2017/05/15/android-cars-audi/
  4. https://www.theverge.com/2017/5/15/15640596/google-android-auto-audi-volvo-apple-carplay-io-2017
  5. https://source.android.com/docs/automotive/start/releases
  6. https://developer.android.com/training/cars/platforms/automotive-os
  7. https://www.androidheadlines.com/android-automotive
  8. https://www.capitalone.com/cars/learn/finding-the-right-car/what-is-google-builtin/3926
  9. https://automobiles.honda.com/google-built-in
  10. https://android-developers.googleblog.com/2025/05/android-for-cars-google-io-2025.html
  11. https://developer.android.com/training/cars
  12. https://source.android.com/docs/automotive
  13. https://source.android.com/docs/core/ota
  14. https://arstechnica.com/cars/2017/05/android-automotive-hands-on-google-is-finally-ready-to-talk-about-its-car-os/
  15. https://venturebeat.com/business/google-opens-android-automotive-to-app-developers/
  16. https://www.media.volvocars.com/us/en-us/media/pressreleases/208072/volvo-cars-partners-with-google-to-build-android-into-next-generation-connected-cars
  17. https://arstechnica.com/cars/2021/05/android-automotive-os-review-under-the-hood-with-googles-car-os/
  18. https://newsroom.intel.com/press-kits/intel-atom-processor-e3900-series/
  19. https://lehtimaeki.medium.com/polestar-2-android-automotive-os-infotainment-system-a-review-ish-b610fb352cdf
  20. https://source.android.com/docs/automotive/start/releases/r_release
  21. https://source.android.com/docs/automotive/start/releases/archive_s_release
  22. https://source.android.com/docs/automotive/start/releases/t_release
  23. https://source.android.com/docs/automotive/start/releases/u_udc_release
  24. https://source.android.com/docs/automotive/start/releases/aaos-24q3
  25. https://www.p3-group.com/wp-content/uploads/2024/04/Android-Automotive-Embedded-OS-P3-Whitepaper-v2.pdf
  26. https://source.android.com/docs/automotive/vhal
  27. https://source.android.com/docs/automotive/security/vehicle_system_isolation
  28. https://source.android.com/docs/core/architecture/ipc/binder-overview
  29. https://source.android.com/docs/automotive/start/terms
  30. https://source.android.com/docs/automotive/displays
  31. https://source.android.com/docs/automotive/power
  32. https://source.android.com/docs/core/ota/ab
  33. https://source.android.com/docs/automotive/hmi/system_ui
  34. https://source.android.com/docs/automotive/scalableui/implement
  35. https://developer.android.com/training/cars/platforms/automotive-os/google-play/google-services
  36. https://developers.google.com/cars/design/automotive-os/product-experience/system-ui/profiles/how_profiles_work
  37. https://source.android.com/docs/automotive/users_accounts/accounts
  38. https://developers.google.com/cars/design/automotive-os/product-experience/system-ui/profiles/overview
  39. https://blog.google/products/android/gemini-for-cars/
  40. https://source.android.com/docs/compatibility/16/android-16-cdd
  41. https://source.android.com/docs/core/connect/esim-overview
  42. https://www.chevrolet.com/support/vehicle/smartphone-connections/voice/troubleshooting-google-built-in
  43. https://www.gmc.com/support/vehicle/smartphone-connections/voice/troubleshooting-google-built-in
  44. https://www.volvocars.com/us/support/topic/8705c9b3bb9754ccc0a801517358bc5a/
  45. https://source.android.com/docs/automotive/driver_distraction/guidelines
  46. https://appning.com/newsroom/incorporating-driver-distraction-guidelines-into-aaos-apps/
  47. https://wiki.unece.org/display/trans/Driver+Drowsiness+and+Distraction+Warning+Systems
  48. https://source.android.com/docs/core/storage/scoped
  49. https://source.android.com/docs/security/features/encryption/file-based
  50. https://source.android.com/docs/automotive/security/vehicle-bound
  51. https://source.android.com/docs/security/features/encryption
  52. https://built-in.google/cars/
  53. https://www.autoevolution.com/cars/renault-scenic-e-tech-2023.html
  54. https://automobiles.honda.com/prologue
  55. https://www.blazerevforum.com/threads/google-finally-approving-releasing-new-apps-to-vehicles-with-android-automotive.1977/
  56. https://www.volvocars.com/us/news/technology/google-gemini-is-coming-to-your-volvo-with-google-built-in/
  57. https://www.kiamedia.com/us/en/media/pressreleases/22941/hyundai-motor-group-and-google-collaborate-on-software-capability-for-future-mobility-innovation
  58. https://blog.google/feed/mobile-apps-cars-google-built-in/
  59. https://www.luxoft.com/blog/gas-or-not-gas-optimizing-aaos-for-automotive-ivi-systems
  60. https://valtech-mobility.de/en/news/android-automotive-os/
  61. https://carbuzz.com/rivian-uses-android-automotive-as-operating-system-base/
  62. https://www.bmwblog.com/2023/01/09/bmw-switches-to-open-source-android-automotive/
  63. https://www.audi-mediacenter.com/en/the-audi-q6-e-tron-electric-mobility-on-a-new-level-15929/infotainment-a-new-experience-of-digitalization-15942
  64. https://www.snappautomotive.io/blog/the-state-of-android-automotive-in-2024
  65. https://techcrunch.com/2025/05/28/stellantis-pivots-to-googles-android-as-in-car-partnership-with-amazon-ends/
  66. https://www.techradar.com/vehicle-tech/car-infotainment/heres-the-real-reason-android-automotive-is-still-kind-of-a-mess-in-evs
  67. https://www.futuremarketinsights.com/reports/android-automotive-os-aaos-market
  68. https://www.visteon.com/resources-insights/automotive-intellect-blog/automotive-intellect-blog-details/2025/Android-as-the-Common-Language-of-the-Automotive-Industry/default.aspx
  69. https://www.qualcomm.com/news/releases/2025/01/qualcomm-brings-industry-leading-ai-innovations-and-broad-collab
  70. https://www.media.volvocars.com/us/en-us/media/pressreleases/349455/volvo-cars-and-google-expand-partnership-with-gemini-integration-and-accelerated-automotive-innovati
  71. https://www.qualcomm.com/news/releases/2025/01/qualcomm-and-hyundai-mobis-to-power-next-generation-adas-and-dig
  72. https://www.automotive-iq.com/cybersecurity/how-to-guides/complying-with-the-eu-data-act-in-automotive
  73. https://www.towardsautomotive.com/insights/automotive-operating-system-market-sizing
  74. https://rsvp.withgoogle.com/events/ai-in-automotive-from-wow-to-how-summit_692824
  75. https://unece.org/transport/documents/2025/11/working-documents/iwg-cyber-security-and-software-updates-proposal
Add your contribution
Related Hubs
User Avatar
No comments yet.