Effective in 2026, to align with our trunk stable development model and ensure platform stability for the ecosystem, we will publish source code to AOSP in Q2 and Q4. For building and contributing to AOSP, we recommend utilizing android-latest-release instead of aosp-main. The android-latest-release manifest branch will always reference the most recent release pushed to AOSP. For more information, see Changes to AOSP.

Code location

This page describes the structure and how to access the source code.

Source code access

Start with Android Automotive - Accessing Source Code.

PDK and source

See the complete list of SDV source code here:

/system/software_defined_vehicle/platform contains specific libraries and wrappers related to built-in development: log, trace, and time synchronization.
/system/software_defined_vehicle/automotive_services contains the Automotive-specific services: diagnostics, configuration, calibration, vehicle mode, and user profile.
/system/software_defined_vehicle/vsidl and /system/software_defined_vehicle/middleware contain the VSIDL and middleware functionality.
/system/software_defined_vehicle/update_manager contains the Update Manager functionality.
/system/software_defined_vehicle/sdv_gateway contains the SDV Gateway for integration with IVI.
/system/software_defined_vehicle/telemetry contains the Telemetry source code.
/system/software_defined_vehicle/samples contains samples you can start with and run.
/device/google/sdv_display_safety contains the build targets for display safety. The code is located in /packages/services/display_safety/ and /packages/apps/Car/DriverUI.

Lunch targets

The Android products, or lunch targets, for SDV reside in a separate Git project, located in the /device/google/sdv folder. In addition, SDV uses a variety of AOSP components, including Binder.

Code location Stay organized with collections Save and categorize content based on your preferences.

Source code access

PDK and source

Lunch targets

Code location