Fact-checked by Grok 2 weeks ago

Android Automotive

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 , playback, , 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 () 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 , while adhering to automotive standards for reliability in 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, (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 platform, specifically optimized for automotive applications, that runs natively on in-vehicle hardware to power systems. As a base platform, it delivers core services such as , , and 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 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 and features while leveraging Android's robust ecosystem of tools, , and expertise. Initial development of AAOS focused on delivering a customizable 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 .

Comparison with Android Auto

functions as a mobile application that projects a 's onto a vehicle's 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 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 and hardware controls that align with the car's design and safety requirements. Android Auto, however, is constrained to a standardized layer that adapts apps for driving but cannot directly with vehicle-specific systems beyond basic and audio output. Furthermore, AAOS supports offline functionality for core operations and installed apps, allowing the system to function without connectivity or internet access for essential tasks, whereas Android Auto ceases to operate effectively if the disconnects, inheriting the phone's connectivity dependencies and potential limitations in coverage or 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 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 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 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 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 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 9 () and marked the initial to feature full Google including , , and Store directly embedded in the infotainment system. Key releases of Android Automotive OS have aligned with major 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 and . 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 for automotive contexts, such as system 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 (), 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 without proprietary integrations. In contrast to standard , 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 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 () 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 supports multi-window modes, including split-screen functionality, to enable simultaneous use of apps like and 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 , 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 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. 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 , , and brands, emphasizing enhanced navigation and infotainment through collaboration. These implementations highlight a seamless , where 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 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 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 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 vehicles, where AAOS facilitates seamless integration with local standards. In , adoption is growing through 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 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 () 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 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 expansions in 2025-2026, integrating 's model for features that analyze vehicle to forecast component failures and suggest optimizations. 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 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 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 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. [1]
    What is Android Automotive? | Android Open Source Project
    Android Automotive is an operating system and platform running directly on the in-vehicle hardware. It is a full-stack, open source, highly customizable ...
  2. [2]
    Automotive OS - Design for Driving | Google for Developers
    Dec 10, 2024 · Android Automotive OS (AAOS) is an infotainment platform built into cars by car makers. Drivers can download compatible apps directly into their cars.
  3. [3]
    Android Automotive OS review: Under the hood with Google's car OS
    May 10, 2021 · It controls not just maps and media, but the air conditioning, lights, ride settings, seat location, camera views, and most other car settings.
  4. [4]
    Android Automotive OS releases
    The pages in this section describe key features and updates made to these releases of the Android Automotive OS (AAOS).
  5. [5]
    Android Automotive OS overview | Android for Cars
    Sep 3, 2025 · Android Automotive OS allows OEMs to control whether or not apps can show or hide the system bars to enter and exit immersive mode. By ...Learn about Android... · Understand Android... · System UI · System featuresMissing: key | Show results with:key
  6. [6]
    Cars with Google Built-In: Everything You Need To Know
    What vehicles support Goole Built-In? · Acura ZDX (2024+) · Cadillac Celestiq · Cadillac CT5 (2025+) · Cadillac Escalade IQ · Cadillac Lyriq · Cadillac XT4 (2024+) ...
  7. [7]
    What Is Google built-in? | Capital One Auto Navigator
    Sep 24, 2025 · A vehicle must run Android Automotive to add Google built-in, while Google built-in is not necessarily a part of all Android Automotive ...
  8. [8]
    Cars & SUVs with Google Built-in Technology - Honda
    2026 Prologue · 2026 CR-V Sport Touring · 2026 Passport · 2026 Civic Sedan Sport Touring Hybrid · 2026 Civic Hatchback Sport Touring Hybrid · 2025 Accord Touring ...
  9. [9]
    New in-car app experiences - Android Developers Blog
    May 20, 2025 · Android Auto is now supported in nearly all new cars sold, with almost 250 million compatible vehicles on the road. We're also seeing ...<|control11|><|separator|>
  10. [10]
    Android for Cars overview - Android Developers
    Android Automotive OS is an Android-based infotainment system that is built into vehicles. The car's system is a standalone Android-powered device that is ...Android Automotive OS · Test Android apps for cars · Add Android Automotive OS...
  11. [11]
    Android Automotive - Android Open Source Project
    Dec 12, 2024 · Android Automotive is a full-stack, open source, highly customizable platform running directly on in-vehicle hardware.Get Started · Android Automotive 14 release... · Android Automotive 13 release...
  12. [12]
    OTA updates - Android Open Source Project
    OTA updates allow Android devices to install updates to the system, app software, and time zone rules, upgrading the OS and read-only apps.
  13. [13]
    Android Automotive hands-on: Google is finally ready to talk about ...
    May 19, 2017 · After years of rumors and speculation, Google finally announced a plan to put a Google-blessed, car version of Android in a production vehicle.
  14. [14]
  15. [15]
    Volvo Cars partners with Google to build Android into next ...
    May 15, 2017 · Volvo Cars partners with Google to build Android into next generation connected cars. Volvo Cars, the premium car maker, has announced a ...Missing: Audi GM
  16. [16]
  17. [17]
    Automotive Audio - Android Open Source Project
    Multi-zone audio starting in Android 10 enables OEMs to configure audio into separate zones. Each zone is a collection of devices within the vehicle with its ...
  18. [18]
    Android Automotive 11 release details | Android Open Source Project
    Oct 9, 2025 · Major features and enhancements · System UI and core apps improvements · User management · Bluetooth · Multiple displays · Connectivity · Audio.Major features and... · System UI and core apps... · User management · Audio
  19. [19]
    Android Automotive 12 release details
    Oct 9, 2025 · Features · Platform: System power, performance, and cluster · System user interface and improvements to core apps · User management · Bluetooth.Features · System user interface and... · Camera
  20. [20]
    Android Automotive 13 release details | Android Open Source Project
    This page summarizes new major features provided in Android Automotive 13. ... Added new properties for fog lights, EV charging, trailer, vehicle weight ...Car Framework · Connectivity · PrivacyMissing: announced | Show results with:announced
  21. [21]
    Android Automotive 14 release details
    Oct 9, 2025 · This page summarizes new major features provided in Android Automotive 14. Features: Car framework, Display and Window Manager, Audio.
  22. [22]
    Android Automotive 24Q3 | Android Open Source Project
    Oct 9, 2025 · Features · Car framework · Multi-display · Safety display · Connectivity · System UI and core apps · Camera · Sensors and VHAL properties.Missing: OS | Show results with:OS
  23. [23]
    [PDF] Android Automotive Embedded OS | P3 Group
    In this technical white paper, we will give an overview of Android Automotive Embed- ded OS features and architecture to support the decision-making process for ...<|control11|><|separator|>
  24. [24]
    Overview | Android Open Source Project
    The VHAL interface defines properties OEMs can implement, using AIDL in Android 13+ and HIDL in Android 12 and lower. New implementations must use AIDL.VHAL interface · Property configurations · ADAS vehicle properties · Debug VHAL<|separator|>
  25. [25]
    Trusty TEE - Android Open Source Project
    Jun 18, 2025 · Trusty is a secure Operating System (OS) that provides a Trusted Execution Environment (TEE) for Android.
  26. [26]
    Binder overview | Android Open Source Project
    Oct 9, 2025 · Binder is a system for interprocess communication that lets two processes on an Android-powered device communicate. Binder provides a means to ...
  27. [27]
    Terminology | Android Open Source Project
    Android Automotive uses the following terms and acronyms. ... Risk classification scheme defined by the ISO 26262 (Functional Safety for Road Vehicles) standard.
  28. [28]
    Overview | Android Open Source Project
    This page describes the key elements to integrate instrument cluster and other displays into an Android Automotive IVI system.
  29. [29]
    Overview | Android Open Source Project
    Android Automotive requires near-zero power while parked, fast power-on, quick boot, and a low-power "Garage Mode" for maintenance.<|separator|>
  30. [30]
    Vehicle system isolation | Android Open Source Project
    Mar 13, 2025 · To make these functionalities safe and streamlined, they are isolated in an abstraction layer, separate from the rest of Android.
  31. [31]
    A/B (seamless) system updates - Android Open Source Project
    Oct 9, 2025 · A/B system updates, also known as seamless updates, ensure a workable booting system remains on the disk during an over-the-air (OTA) update.
  32. [32]
    Implement the System UI | Android Open Source Project
    The Automotive System UI can have three navigation bars on the left, bottom, and right of the screen. The visibility of each system bar is toggled with the ...Customize The System Ui · Overlays · System Ui Source Code...
  33. [33]
    Implement advanced windowing - Android Open Source Project
    Oct 22, 2025 · Android Automotive 25Q2 · Android Automotive 25Q1 · Android Automotive ... Confirm that any legacy windowing or split-screen features that ...
  34. [34]
    How profiles work | Design for Driving - Google for Developers
    Jul 23, 2024 · Car profiles allow users to have secure and personalized experiences in the car. Users can use profiles to set up their unique driving and infotainment ...Missing: sync | Show results with:sync
  35. [35]
    Manage users and accounts - Android Open Source Project
    Android Automotive OS provides a reference user experience and interface for managing Users and accounts.Missing: sync | Show results with:sync
  36. [36]
    Profiles | Design for Driving - Google for Developers
    Jul 23, 2024 · The profile-based identity system in Android Automotive OS is designed to give drivers a personalized experience while protecting their privacy in the car.Missing: sync | Show results with:sync
  37. [37]
    Driving just got more productive — and fun — with Gemini and more
    May 13, 2025 · Gemini will be available on cars that support Android Auto in the coming months, and cars with Google built-in later this year, including ...
  38. [38]
    Android 16 Compatibility Definition
    This document enumerates the requirements that must be met in order for devices to be compatible with Android 16.
  39. [39]
    Implement eSIM | Android Open Source Project
    Oct 9, 2025 · Embedded SIM (eSIM, or eUICC) technology allows mobile users to download a carrier profile and activate a carrier's service without having a physical SIM card.
  40. [40]
    Driver Distraction Guidelines | Android Open Source Project
    Driver Distraction Guidelines (DDG) are recommendations to reduce distraction, allowing apps to run when moving. Apps must be tagged as Distraction Optimized, ...
  41. [41]
    Incorporating Driver Distraction Guidelines into AAOS Apps - Appning
    Dec 7, 2021 · All Apps that run on AAOS need to be tagged as 'Distraction Optimised', otherwise they will not run in any of the restricted states.
  42. [42]
    UN Regulations on Cybersecurity and Software Updates to pave the ...
    Jun 24, 2020 · Two new UN Regulations on Cybersecurity and Software Updates will help tackle these risks by establishing clear performance and audit requirements for car ...
  43. [43]
    Scoped storage - Android Open Source Project
    Oct 9, 2025 · Scoped storage limits app access to external storage, protecting user data and preventing apps from modifying files without permission. Apps on ...
  44. [44]
    File-based encryption - Android Open Source Project
    Oct 9, 2025 · This article describes how to enable file-based encryption on new devices and how system apps can use the Direct Boot APIs to offer users the ...Implementation · Enable File-Based Encryption · Internal Storage<|control11|><|separator|>
  45. [45]
    Use vehicle bound file encryption | Android Open Source Project
    The primary goal of the vehicle binding seed feature is to further protect the user's privacy by guarding data on the In-Vehicle Infotainment (IVI) system ...
  46. [46]
    Encryption - Android Open Source Project
    Oct 9, 2025 · Starting March 27, 2025, we recommend using android-latest-release instead of aosp-main to build and contribute to AOSP.Full-disk encryption · File-based encryption · Metadata encryption · Enable adiantumMissing: AI | Show results with:AI
  47. [47]
    Cars with Google built-in | A more connected, personal, and helpful ...
    Cars with Google built-in receive automatic updates directly from Google while parked or on the go, delivering new apps, features, and more.
  48. [48]
    2024 Renault Scenic E-Tech Specs, Performance & Photos
    Sep 5, 2023 · The R-Link infotainment system ran on Android Automotive OS12. In the back, the automaker installed a bench seat fit for three adults ...
  49. [49]
    Hyundai Motor Group and Google Collaborate on Software ...
    Dec 11, 2024 · Hyundai Motor Group (the Group) is expanding its partnership with Google to deliver next-generation navigation and infotainment experiences.
  50. [50]
    Dozens of new mobile apps are coming to cars with Google built-in.
    Feb 19, 2025 · Starting this week, cars with Google built-in will get dozens of new apps to enjoy while parked. This launch is part of our car ready mobile apps program.
  51. [51]
    To GAS or Not to GAS: Optimizing AAOS for Automotive IVI Systems
    Jun 27, 2024 · It comes in two flavors: With or without Google Automotive Services (GAS). Either way, it has become the next-generation in-vehicle infotainment ...<|control11|><|separator|>
  52. [52]
    Android Automotive OS: GAS vs. NON-GAS - Valtech Mobility
    Apr 2, 2024 · Android Automotive is an extension of the Android OS that runs directly on the IVI module itself. An external mobile device is therefore not required.
  53. [53]
    Rivian Uses Android Automotive As Operating System Base - CarBuzz
    May 21, 2024 · Rivian uses Android Automotive as the "base OS" for its in-vehicle software. CarBuzz has contacted the automaker to find out more.Missing: non- GAS
  54. [54]
    BMW Switches to Open Source Android Automotive OS Coming 2024
    Jan 9, 2023 · BMW is switching to an open source Android Automotive operating system beginning in 2024. Here's what it means for the brand.Missing: non- | Show results with:non-
  55. [55]
    Infotainment - a new experience of digitalization | Audi MediaCenter
    Jun 28, 2024 · The new infotainment system uses Android Automotive OS as its operating system ... Android Auto is also on board the Audi Q6 e-tron. Sound ...
  56. [56]
    The state of Android Automotive in 2024
    Feb 7, 2024 · The brands who have, or announced, non-GAS cars are Stellantis, BMW, MINI, Dacia, Lucid, Rivian, Lotus, and Lynk & Co.
  57. [57]
    Here's the real reason Android Automotive is still kind of a mess in EVs
    Nov 2, 2024 · The infotainment experience isn't intuitive or attractive and lacks the modern design touches of Tesla or Rivian's infotainment software. It ...
  58. [58]
    Android Automotive - Wikipedia
    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 ...
  59. [59]
    Android Automotive OS (AAOS) Market - 2035 - Future Market Insights
    Oct 27, 2025 · Germany is expected to maintain its leadership position with a 42.6% market share in 2025, declining slightly to 41.8% by 2035, supported by ...
  60. [60]
    Android as the Common Language of the Automotive Industry
    Oct 27, 2025 · Accelerating ecosystem innovation by enabling app development, OTA updates, and personalized digital services. In practice, this means ...
  61. [61]
    Qualcomm Brings Industry-Leading AI Innovations and Broad ...
    Jan 6, 2025 · Qualcomm Brings Industry-Leading AI Innovations and Broad Collaborations to CES 2025 Across PC, Automotive, Smart Home and Enterprises.Missing: Android Stellantis<|separator|>
  62. [62]
    Volvo Cars and Google expand partnership with Gemini integration ...
    May 21, 2025 · This includes Google Gemini™, which the companies demonstrated together at Google I/O 2025 in a Volvo EX90.​ ​Also, Volvo​ car ...
  63. [63]
    Qualcomm and Hyundai Mobis to Power Next-Generation ADAS ...
    Jan 6, 2025 · Qualcomm Technologies, Inc. and Hyundai Mobis announced the companies are collaborating to revolutionize the next generation of High- Performance Computer (HPC ...Missing: Android Stellantis
  64. [64]
    Qualcomm and Stellantis Announce Multi-Year Deal
    Qualcomm and Stellantis announced a multi-year agreement to bring Snapdragon® Digital Chassis Solutions to 14 Stellantis brands.Missing: Hyundai | Show results with:Hyundai
  65. [65]
    Automotive Operating System Market Size Driven by 14% CAGR
    Aug 28, 2025 · The automotive operating system market is set to grow from USD 14.25 billion in 2025 to USD 46.34 billion by 2034, with an expected CAGR of 14% ...Automotive Operating System... · What are the Trends of the... · OS Type Insights