Commit ab48d444 authored Jun 09, 2023 by Pranav Madapurmath

Resolve CallEndpoint nullability in BT audio route

There was an issue which came up where the endpoint name received in
HeadsetMediaButton#onCallEndpointChanged was null. CallEndpoints are
expected to hold non-null names. In the bug report, we see that the
error was invoked coming from the ActiveBluetoothRoute and looking at
the instantation of the endpoint for BT, we find two binder calls to
retrieve the bluetooth device name. It is likeley that the 2nd binder
call fails, which is resulting in the null value here. The resolution is
to remove the redundant binder call and instead store the value returned
from the first invocation.

Fixes: 286310499
Test: atest TelecomUnitTests
Change-Id: I2338d6675cb401f237a4022a5afcd9a5a4328846

parent 1feb0f28

src/com/android/server/telecom/CallEndpointController.java

+2 −1

Original line number	Diff line number	Diff line
		@@ -247,8 +247,9 @@ public class CallEndpointController extends CallsManagerListenerBase {
		for (BluetoothDevice device : state.getSupportedBluetoothDevices()) {
		CallEndpoint endpoint = findMatchingBluetoothEndpoint(device);
		if (endpoint == null) {
		String deviceName = device.getName();
		endpoint = new CallEndpoint(
		device.getName() != null ? device.getName() : "",
		deviceName != null ? deviceName : "",
		CallEndpoint.TYPE_BLUETOOTH);
		}
		newAvailableEndpoints.add(endpoint);