Commit f2ad5dca authored Mar 27, 2019 by Cheney Ni

A2DP: Initialize the UIPC HAL only when those binderized HALs are not enabled

When using BluetoothA2dp / BluetoothAudio HAL, the UIPC won't be used,
and is no need to do the initialization. If it is up, there will be an
uipc-main thread running, and we have to release by the UIPC_Close API
before the A2DP source restarting. If we are acquiring a new one before
released, some of its resource will be leaked, and causes the stack
abnormal.

Bug: 128256722
Test: Check uipc-main is running when using the legacy HAL only
Change-Id: Icc8ea102d29c92b58c77099979d17e85e5cb9a83

parent 88a942ec

system/btif/src/btif_a2dp_source.cc

+6 −2

Original line number	Diff line number	Diff line
		@@ -357,9 +357,13 @@ static void btif_a2dp_source_startup_delayed() {
		LOG(FATAL) << __func__ << ": unable to enable real time scheduling";
		}
		if (!bluetooth::audio::a2dp::init(&btif_a2dp_source_thread)) {
		if (btif_av_is_a2dp_offload_enabled()) {
		LOG(WARNING) << __func__ << ": Using BluetoothA2dp HAL";
		} else {
		LOG(WARNING) << __func__ << ": Using legacy HAL";
		btif_a2dp_control_init();
		}
		}
		btif_a2dp_source_cb.SetState(BtifA2dpSource::kStateRunning);
		}