Android Automotive 25Q2

Google is pleased to share this Android 25Q2 release with Android Automotive partners. For Android 16, this Android Automotive 25Q2 release is compliant. We continue to fine tune features, aiming to recommend an upcoming release for OEMs.

Release details

This section summarizes major features and enhancements provided in the AAOS B release.

These updates apply to Android16, API level 36.

The Android Automotive 25Q2 release is compliant with Android 16.

New features

The 25Q2 release provides these new features.

AAOS Framework

  • Audio and radio:

    • Audio control HAL improvements: To configure car audio features, use APIs instead of XML file.

    • High definition (HD) radio Emergency Alert System (EAS): Pass EAS information to radio applications with an API. This applies to HD Radio (North America) and DAB EWS (European Union).

    • AAudio built-in library: AAudio AAudio supports OEM-defined Audio Attributes tags to customize app behavior. For example, audio routing and volume management.

  • Power management:

    • Power state notifications to built-in processes: The availability of power state notifications to OEM built-in processes (beyond Android apps) is extended.

  • Car framework:

    • Dynamic configuration of vehicle properties: Support the dynamic configuration of minimum and maximum and of supported values in vehicle properties.

Connectivity

  • Networking:

    • Minimal Telephony: A subset of the Android Telephony Hardware Abstraction Layer (HAL) for automotive OEMs to allow OEMs to use Android telephony on data-only devices (including TCUs). This reduces fragmentation and provides support for telephony functionality.

    • Connectivity Messaging Upsell API: Enhanced SubscriptionManager to provide APIs that can expose a user's mobile data subscription status. For example, active, inactive, trial, and expiration date.

    • Projected app support: Added support to let automotive OEMs configure the complete set of hostapd.conf parameters not available through the Android APIs. Added a disconnect reason to the SoftApCallback API so that OEMs can learn why clients disconnected from a Local Hotspot (LOHS). These features improve support for projected apps and reduce fragmentation.

AAOS System UI and Experiences

  • Scalable UI: This AAOS windowing framework provides OEMs with configurable components that let OEMs meet windowing requirements and facilitate custom experiences.

VHAL properties

  • Vehicle properties:

    • Added new vehicle properties to communicate vehicle characteristics and state.

    • Updated vehicle property constants from @SystemApi to public APIs to consolidate generated documentation at VehiclePropertyIDs. Any previously defined and documented permissions are still required to access vehicle property data.

  • Third party-accessible vehicle properties: This features makes eight existing vehicle properties relevant to navigation, voice assistant, weather, and driving state available to third party app developers. To learn more, see Integrate with Google apps and services.

Compliance

Android Compliance was executed on the internal reference hardware. The test suites run for this release include CTS, CTS-V, ATS, STS, VTS and CTS on GSI.

Except for the issues listed below, no known failures require a fix either in Android 16 code (android16-release) or to the Android 16 test branch (android16-tests-dev).

  • Test failing: CtsWindowManagerJetpackTestCases#MultiDisplayActivityEmbeddingPlaceholderTests

    Failure summary: One test fails in portrait display. When testing Activity embedding behaviors in Scalable UI builds that are based on windowing solutions that involve multiple root tasks each a WINDOWING_MODE_MULTI_WINDOW, known failures occur due to some activities launched in smaller bounds than expected, as in windowMetrics of the embedding rules. As a result, the placeholder was started and the test failed when launching an activity on the secondary display.

    The aosp/3659633 patch corrects windowing mode inheritance from multi-window rootTask.

  • Test failing: CtsAutoFillServiceTestCases

    Failure summary: Two categories of known issues occur in the Scalable UI builds based on windowing solutions that involve multiple root tasks each of WINDOWING_MODE_MULTI_WINDOW:

    • IME covers the Autofill fill dialog that prevents the buttons on the fill dialog from being pressed. You can temporarily disable the fill dialog with this platform ag/3664131 patch.

    • When the second field is auto-filled, such as PASSWORD, the LoginActivity is behind decor_grip, and loses the input focus. Patches can be found in the following links: ag/3679541, ag/3675628, ag/3675627.