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.
Multi-zone audio
Stay organized with collections
Save and categorize content based on your preferences.
To learn more about the use of multi-zone audio in automotive rear-seat entertainment systems, see Multi-Zone Audio.
Device manufacturers can link a display to an audio zone in a vehicle. For instance, for a car with one primary and rear seat entertainment zone, a device manufacturer can have the following configuration on the vendor partition:
<?xmlversion="1.0"encoding="utf-8"?> <carAudioConfigurationsxmlns:car="http://schemas.android.com/apk/res-auto"> <zones> <zonename="primary zone"> <volumeGroups> <group> <deviceaddress="bus001_media"> <contextcontext="music"/> </device> <deviceaddress="bus002_others"> ... </device> </group> </volumeGroups> <displays> <displaycar:display="<display-id-1>"/> </displays> </zone> <zonename="rear seat"> <volumeGroups> <group> <deviceaddress="bus100_all"> ... </device> </group> </volumeGroups> <displays> <displaycar:display="<display-id-2>"/> </displays> </zone> </zones> </carAudioConfigurations> </xml>
CarAudioService parses this configuration file and sets up the
audio routing by its audio context (or audio usage) at boot time. During
runtime, CarAudioService further detects an app launch event and dynamically
assigns the app to the zone based on UID.
Implementation
For the stable ID that device manufacturers can include in their configuration file, see Static display identifiers.