Starting March 27, 2025, we recommend using android-latest-release instead of aosp-main to build and contribute to AOSP. For more information, see Changes to AOSP.
Added UXRE support on multiple displays, including physical and virtual
displays. This enables different UXREs to be applied on a per-display
basis, whether a physical or a virtual display. Displays can be identified
within a car occupant zone in the UXRE config. This allows for
passenger-only displays to continue to use NDO apps while driving.
Min and max volume levels. OEMs can now define minimum and maximum
volume levels to prevent sounds from being too quiet or too loud when
activated.
Dynamic audio devices. Allows audio configurations with dynamic output
devices, such as Bluetooth and USB headphones, to be selected by the user
when the devices are connected.
Audio crossover fade configurations. OEMs can now define crossover fade
configurations for automotive devices, which can be applied to apps upon
audio playback.
Improve support HD and DAB radio. Fully support the HD and DAB radio
standards so that OEMs can integrate radio features in automotive devices.
Richer instrumentation for system performance issues. The CarWatchdog
dumpsys proto reports cached metrics in a structured format for easier
analysis. CarWatchdog memory profiling is used to better understand the
impact of memory pressure on performance.
Serverless remote access. Added the ability to enable other ECUs, such
as the TCU, to trigger AAOS activity and for AAOS to schedule its own
wake-ups to process a queue of tasks.
Emergency shutdown support. Improves the car power management service to
alert system apps that an emergency condition has triggered a shut-down.
Power policy controls. Allows OEM system apps to change power policy
according to the situation.
Multi-display
You can enable the communication between the same apps running in
different occupant zones using the Multi-Display Communications API.
Safety display
You can now enable driver UI and cluster development outside the Android
source tree.
You can now monitor the Driver UI can generate alerts and notifications.
Connectivity
Bluetooth
Bluetooth headsets. Allows users to connect Bluetooth headsets to AAOS,
alongside connected phones, and to use headsets as an audio output device.
The user can use the new Audio Output Device setting on the Audio
Settings pageset to designate their headset as an output device. Only one
media or audio stream can be active over Bluetooth at a time, source or
sink.
Default Log Level. You can now control the default log level of the
Bluetooth stack from Developer Options or on the command line using the
new log.tag.bluetooth logging tag.
Data and subscription plan messaging. A reference UX to present the
option to renew paid connectivity at the user's point of need.
OEM-paid Wi-Fi. A reference UX for showing connections to restricted
Wi-Fi networks.
Wi-Fi hotspot persistence. Added a toggle to allow users to retain the
vehicle hotspot for every drive.
UWB
Settings update. Added new options to provide more control of UWB
devices.
System UI and core apps
Config aware System UI. Broaden the capabilities of AAOS emulators by
supporting simulated multiple device configurations using a single system
image.
Compatibility improvements. Made improvements to third party app facing
compatibility through the inclusion of core Android functionality, such as
DocumentsUI and Gallery.
Dock. Allow users to pin favorite apps to the system UI space to more
quickly launch apps.
Ambient view. Provide OEMs with a space in which to create
differentiated experiences when IVI screens are turned on but not in use
Refreshed profile lock challenge. Added a standardized screen lock
challenge across Android Automotive.
Improved support for EVS concurrent multi-camera clients. Improved
multi-camera and multi-client support in CarEvsService, allowing clients
to manage data streams more efficiently.
Camera2 user0 access. Enable apps running in the headless user to access
Camera2.
Camera2 privacy allowlist. OEMs can now designate certain camera apps to
be allowlisted to access cameras regardless of the state of camera privacy
toggle.
Camera2 early access. Privileged clients with UID AID_AUTOMOTIVE_EVS
can now access the camera before an Android boot is completed.
Ultrasonic sensors. Added new VHAL properties for ultrasonic parking
sensors.
Driver monitoring. Added new VHAL properties for driver attention
monitoring systems.
New VHAL properties. Added 10 new VHAL properties.
Car property performance improvements. To reduce CPU load, updated the
Continuous and On_Change properties.
Configurable resolution when subscribing to sensor data. Added a new
registerCallback API at the CPM level and added logic to the
CarPropertyService and VHAL interface.
VHAL: Access module granularity. OEMs can now specify access levels
(such as READ-only and READ-WRITE) per propertyId-areaId combinations
instead of specifying access levels for an entire property.
Compliance
Android compliance tests were executed on internal reference hardware. Test
suites run for this release include CTS, STS, VTS, and CTSonGSI.
Except for the following issues, we discovered no known failures requiring a fix
either in Android 15 code (android15-release) or in the Android 15 test branch
(android15-tests-dev).
CTS-Verifier. Chooser result.
If your device is based on the Car Portrait UI, these tests might fail, in
addition to those listed previously.
CTS.CtsWindowManagerDeviceWindow
CTS.CtsWindowManagerDeviceMultiDisplay
CTS-Verifier. Disable the status bar
Content and code samples on this page are subject to the licenses described in the Content License. Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates.
Last updated 2025-06-06 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-06-06 UTC."],[],[],null,["# Android Automotive 24Q3\n\nThis page summarizes new major features provided in Android Automotive 24Q3.\n\nFeatures\n--------\n\n### Car framework\n\n#### Display and window manager\n\nTo learn more, see\n[Instrument Cluster API](/docs/automotive/displays/cluster_api).\n\n1. **Added UXRE support on multiple displays, including physical and virtual\n displays.** This enables different UXREs to be applied on a per-display basis, whether a physical or a virtual display. Displays can be identified within a car occupant zone in the UXRE config. This allows for passenger-only displays to continue to use NDO apps while driving.\n\n#### Audio and radio\n\nTo learn more, see\n[Radio control implementation](/docs/automotive/radio/radio-control-implementation).\n\n1. **Min and max volume levels.** OEMs can now define minimum and maximum\n volume levels to prevent sounds from being too quiet or too loud when\n activated.\n\n2. **Dynamic audio devices.** Allows audio configurations with dynamic output\n devices, such as Bluetooth and USB headphones, to be selected by the user\n when the devices are connected.\n\n3. **Audio crossover fade configurations.** OEMs can now define crossover fade\n configurations for automotive devices, which can be applied to apps upon\n audio playback.\n\n4. **Improve support HD and DAB radio.** Fully support the HD and DAB radio\n standards so that OEMs can integrate radio features in automotive devices.\n\n#### Performance and system health\n\nTo learn more, see\n[Collect performance data](/docs/automotive/watchdog/wd_performance_health)\nand [Monitor system health](/docs/automotive/watchdog/wd_system_health).\n\n1. **Richer instrumentation for system performance issues.** The CarWatchdog dumpsys proto reports cached metrics in a structured format for easier analysis. CarWatchdog memory profiling is used to better understand the impact of memory pressure on performance.\n\n#### Power management\n\nTo learn more, see [Power management](/docs/automotive/power/power).\n\n1. **Serverless remote access.** Added the ability to enable other ECUs, such\n as the TCU, to trigger AAOS activity and for AAOS to schedule its own\n wake-ups to process a queue of tasks.\n\n2. **Emergency shutdown support.** Improves the car power management service to\n alert system apps that an emergency condition has triggered a shut-down.\n\n3. **Power policy controls.** Allows OEM system apps to change power policy\n according to the situation.\n\n### Multi-display\n\n1. You can enable the communication between the same apps running in different occupant zones using the [Multi-Display Communications API](/docs/automotive/displays/multi-display-comms-api).\n\n### Safety display\n\n1. You can now enable driver UI and cluster development outside the Android\n source tree.\n\n2. You can now monitor the Driver UI can generate alerts and notifications.\n\n### Connectivity\n\n#### Bluetooth\n\n1. **Bluetooth headsets.** Allows users to connect Bluetooth headsets to AAOS,\n alongside connected phones, and to use headsets as an audio output device.\n The user can use the new **Audio Output Device** setting on the **Audio\n Settings** pageset to designate their headset as an output device. Only one\n media or audio stream can be active over Bluetooth at a time, source or\n sink.\n\n2. **Default Log Level.** You can now control the default log level of the\n Bluetooth stack from **Developer Options** or on the command line using the\n new `log.tag.bluetooth` logging tag.\n\n#### Networking\n\nTo learn more, see\n[Maintain hotspots between driving sessions](/docs/automotive/connectivity/persist-access-point).\n\n1. **Data and subscription plan messaging.** A reference UX to present the\n option to renew paid connectivity at the user's point of need.\n\n2. **OEM-paid Wi-Fi.** A reference UX for showing connections to restricted\n Wi-Fi networks.\n\n3. **Wi-Fi hotspot persistence.** Added a toggle to allow users to retain the\n vehicle hotspot for every drive.\n\n#### UWB\n\n1. **Settings update.** Added new options to provide more control of UWB devices.\n\n### System UI and core apps\n\n1. **Config aware System UI.** Broaden the capabilities of AAOS emulators by\n supporting simulated multiple device configurations using a single system\n image.\n\n2. **Compatibility improvements.** Made improvements to third party app facing\n compatibility through the inclusion of core Android functionality, such as\n DocumentsUI and Gallery.\n\n3. **Dock.** Allow users to *pin* favorite apps to the system UI space to more\n quickly launch apps.\n\n4. **Ambient view.** Provide OEMs with a space in which to create\n differentiated experiences when IVI screens are turned on but not in use\n\n5. **Refreshed profile lock challenge.** Added a standardized screen lock\n challenge across Android Automotive.\n\n### Camera\n\nTo learn more, see [Camera](/docs/automotive/camera).\n\n1. **Improved support for EVS concurrent multi-camera clients.** Improved\n multi-camera and multi-client support in `CarEvsService`, allowing clients\n to manage data streams more efficiently.\n\n2. **Camera2 user0 access.** Enable apps running in the headless user to access\n Camera2.\n\n3. **Camera2 privacy allowlist.** OEMs can now designate certain camera apps to\n be allowlisted to access cameras regardless of the state of camera privacy\n toggle.\n\n4. **Camera2 early access.** Privileged clients with `UID AID_AUTOMOTIVE_EVS`\n can now access the camera before an Android boot is completed.\n\n### Sensors and VHAL properties\n\nTo learn more, see\n[Supported system properties](/docs/automotive/vhal/system-properties).\n\n1. **Ultrasonic sensors.** Added new VHAL properties for ultrasonic parking\n sensors.\n\n2. **Driver monitoring.** Added new VHAL properties for driver attention\n monitoring systems.\n\n3. **New VHAL properties.** Added 10 new VHAL properties.\n\n4. **Car property performance improvements.** To reduce CPU load, updated the\n `Continuous` and `On_Change` properties.\n\n5. **Configurable resolution when subscribing to sensor data.** Added a new\n `registerCallback` API at the CPM level and added logic to the\n `CarPropertyService` and VHAL interface.\n\n6. **VHAL: Access module granularity.** OEMs can now specify access levels\n (such as `READ-only` and `READ-WRITE`) per `propertyId-areaId` combinations\n instead of specifying access levels for an entire property.\n\nCompliance\n----------\n\nAndroid compliance tests were executed on internal reference hardware. Test\nsuites run for this release include CTS, STS, VTS, and CTSonGSI.\n\nExcept for the following issues, we discovered no known failures requiring a fix\neither in Android 15 code (`android15-release`) or in the Android 15 test branch\n(`android15-tests-dev`).\n\n- **CTS-Verifier.** Chooser result.\n\nIf your device is based on the Car Portrait UI, these tests might fail, in\naddition to those listed previously.\n\n- **CTS.** `CtsWindowManagerDeviceWindow`\n- **CTS.** `CtsWindowManagerDeviceMultiDisplay`\n- **CTS-Verifier.** Disable the status bar\n\n| **Note:** Fixes for these items, and any other required compliance patches, can be found in the [Android Open Source Project](https://android-review.googlesource.com/q/hashtag:%22aaos-24q3-cts%22+%28status:open%20OR%20status:merged%29). Changes provided here will be provided in the Android 15 24Q4 release."]]