Audio routing API updates in Android 14 for VoIP apps

Android 14 introduced API updates accompanied by user experience changes to audio routing behavior for Bluetooth LE Audio (LEA) devices, including hearing aids. These changes impacted how VoIP apps manage audio output selection. This document provides essential information for developers to adapt their VoIP apps to these changes and ensure a seamless user experience.

Behavior change in Android 14

LEA device routing: LEA devices are now enabled by default on Pixel phones and AOSP. However, to actively recognize and select LEA devices as audio output, apps must use the new APIs introduced in API level 31.
Hearing aid routing: Previously, audio would always default to hearing aids, even if the user explicitly selected the earpiece. In Android 14, hearing aids are now presented as one of the available audio output options, requiring explicit selection by the user.

Rationale for the change

Prior to Android 12, there was no API to explicitly use hearing aids for calls, leading to audio always defaulting to hearing aids when connected.
This made it difficult for users to switch from hearing aids to earpieces without disconnecting their hearing aids.
The same issue applied to Bluetooth LE Audio headsets.

To address these challenges, Android 14 introduced changes to provide VoIP apps with more control over audio routing and ensure consistent behavior across Bluetooth accessories.

Key changes in Android 14

Generic APIs for route selection: Android 12 introduced AudioManager.setCommunicationDevice to allow apps to specify audio routes, including hearing aids and LEA devices. However, in Android 12 and 13, hearing aids were not visible as devices, limiting the usefulness of this API.
Hearing aid visibility: In Android 14, hearing aids are now visible as devices, enabling apps to provide UI elements for users to select their preferred audio output.
API Deprecations: Several APIs related to audio routing have been deprecated in Android 14. Developers must migrate to the new APIs introduced in API level 31 to manage audio output selection effectively.

Required developer actions

Highly Recommended: Migrate to Telecom Jetpack Library. If possible, migrate your VoIP app to the Telecom Jetpack library for streamlined audio routing management.
Use setCommunicationDevice() or the latest APIs (listed below) if migration is not feasible.

Deprecated APIs and their replacements

Deprecated in Android 14	New APIs
AudioManager.isBluetoothScoOn()	AudioManager.getCommunicationDevice()
AudioManager.isSpeakerphoneOn()	AudioManager.getCommunicationDevice()
AudioManager.setSpeakerphoneOn()	AudioManager.setCommunicationDevice()
AudioManager.startBluetoothSco()	AudioManager.setCommunicationDevice()
AudioManager.stopBluetoothSco()	AudioManager.clearCommunicationDevice()
Connection.getCallAudioState()	Jetpack: CallControlScope.getAvailableEndpoints() CallControlScope.getCurrentCallEndpoint() CallControlScope#getIsMutedConnection.onMuteStateChanged() Platform: CallEventCallback.onAvailableCallEndpointsChanged() CallEventCallback.onCallEndpointChanged() CallEventCallback.onMuteStateChanged()
Connection.onCallAudioStateChanged()
Connection.requestBluetoothAudio()	Jetpack: CallControlScope#requestEndpointChange() Platform: CallControl#requestCallEndpointChange()
Connection.setAudioRoute()