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, use android-latest-release. The android-latest-release manifest branch will always reference the most recent release pushed to AOSP. For more information, see Changes to AOSP.
Automotive window layering
Stay organized with collections
Save and categorize content based on your preferences.
In Automotive device configurations where safety-critical components are
rendered in the same area of the screen as Android Automotive, it's imperative
that Android layers are behind regulatory layers. Although it's possible to have
transparent regions in Android, they aren't officially supported and can't
be relied upon. Automotive device implementations MUST NOT layer Android
Automotive OS on top of any safety relevant or regulatory components.
Figure 1. Window layers.
Devices can render non-critical components underneath Android. However, we
recommended you use Android as the base layer when multiple systems render in
the same space.
Recommended
|
Possible, not recommended
|
Figure 2. Recommended and not recommended layering.
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 2026-07-16 UTC.
[null,null,["Last updated 2026-07-16 UTC."],[],[]]
