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.
Audio power management
Stay organized with collections
Save and categorize content based on your preferences.
To support vehicle-specific power management, Android provides a
CarPowerManagementService service and a CarPowerManager interface. The power
policy affects the Android Automotive OS (AAOS) audio stack and the audio HAL
with the audio component, android.car.hardware.power.PowerComponent.AUDIO. To
learn more, see Power Management.
In CarAudioService, a CarAudioPowerListener is registered on
CarPowerManagementService when the dynamic audio routing is enabled. This
allows CarAudioService to listen to power policy changes related to audio.
When audio is disabled by the power policy, the following actions take place:
Only focus requests of critical audio attribute usages are retained. Other
focus requests are abandoned.
All incoming focus requests of non-critical audio attribute usages are
rejected.
If car volume group muting is used, car volume groups that do not contain
audio context for critical audio attribute usages are muted.
The following audio attribute usages are considered as critical:
In
Sample configuration (version 2),
we recommend you use separate volume groups for system sounds, including emergency
and safety, from other contexts in the primary audio zone. In this way, volume
groups for all non-critical audio attribute usages are muted when audio is
disabled, while emergency and safety sounds remain unmuted.
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-08-29 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-08-29 UTC."],[],[],null,["# Audio power management\n\nTo support vehicle-specific power management, Android provides a\n`CarPowerManagementService` service and a `CarPowerManager` interface. The power\npolicy affects the Android Automotive OS (AAOS) audio stack and the audio HAL\nwith the audio component, `android.car.hardware.power.PowerComponent.AUDIO`. To\nlearn more, see [Power Management](/docs/automotive/power/power).\n\nIn `CarAudioService`, a `CarAudioPowerListener` is registered on\n`CarPowerManagementService` when the dynamic audio routing is enabled. This\nallows `CarAudioService` to listen to power policy changes related to audio.\nWhen audio is disabled by the power policy, the following actions take place:\n\n- Only focus requests of critical audio attribute usages are retained. Other\n focus requests are abandoned.\n\n- All incoming focus requests of non-critical audio attribute usages are\n rejected.\n\n- If car volume group muting is used, car volume groups that do not contain\n audio context for critical audio attribute usages are muted.\n\nThe following audio attribute usages are considered as critical:\n\n- Emergency\n- Safety\n\nIn\n[Sample configuration (version 2)](/docs/automotive/audio/audio-policy-configuration#sample),\nwe recommend you use separate volume groups for system sounds, including emergency\nand safety, from other contexts in the primary audio zone. In this way, volume\ngroups for all non-critical audio attribute usages are muted when audio is\ndisabled, while emergency and safety sounds remain unmuted."]]
