- Add LC3 supported features in HFP 1.9

Bug: 278469604
Test: atest BtifHfClientTest
Change-Id: Ieb94cdeff6a3d85e22f4f6b2687172690fea5c24

Bug: 300174072
Test: m .
Change-Id: I6eeb9109530a6ec0f25f7691b67bc081fd3379bc

Merge "Move Profile connection state changes logic inside the handler to make sure concurrent counter updates are handled correctly." into main

Bug: 305066880
Test: m com.android.btservices
Change-Id: Id7d310b352384a8ec94926e74ad7199b285a0a6d

Bug: 307434706
Test: m .

Change-Id: Ib99dde5423c7699be2b06c5ca1d2290868597438

Also update stack_avrc_sdp

Bug: 299365655
Test: m .

Change-Id: Ibae5c10687d7c25a99e9c21caaa23b8f2d15af60

Move Profile connection state changes logic inside the handler to make sure concurrent counter updates are handled correctly.

Add flagging for queueing logic for Profile connection change in scan manager.

Bug: 302620968
Bug: 306033108
Test: atest com.android.bluetooth.gatt.ScanManagerTest#multipleProfileConnectionStateChanged_updateCountersCorrectly --rerun-until-failure=100
Change-Id: I72cb908bba21d87a4f429a679fdd26afc569d4c8

Bug: 305066880
Test: m com.android.btservices
Change-Id: Ia0326eaf1512fd514248ce8675c112205bec4f52

* changes:
  Rename service/binder to service/aidl
  Move system/binder to android/app/aidl

Both ASEs that are bonded with bi-directional ASEs should go to QoS
state once CIS is terminated. This change will guard for such
transition.

"If the server detects link loss of a CIS for an ASE in the Streaming
state or the Disabling state, the server shall immediately transition
that ASE to the QoS Configured state." ASCS 1.0 3.2
ASE state machine transitions.

Bug: 278621595
Tag: #feature
Test: atest bluetooth_le_audio_test
Change-Id: Ic6e91d63b9690771bd7da09f1a108a181369b861

Since the audio context notifications on the other thread invalidate the
existing audio set configurations. We should wait of rthe main loop to
finish the job before we start to use these configurations.

We are not consistent in every test with the synchronisation after the
injected notification. This patch moves the synchronisation to a
notification sendind helper function, eliminating the need for new tests
to call the synchronisation routine manually.

Bug: 302775890
Test: atest --host UnicastTest#StartStream_AvailableContextTypeNotifiedLater --rerun-until-failure=1000
Change-Id: I38a892c829779616ac20b0dbb283dcef5204c4e0

Unicast AIDL interface is supported after the HIDL 2.1. So it implies to
be supported for all AIDL version. Check the AIDL transport first that
could decouple the relation with actual version. It could avoid the crash as the version upgrade which is missing to add version into bluetooth stack.
No all HAL upgrade is relates to LE audio. It's risky to require the
version need to be added each time.

Bug: 307397549
Test: m .
Change-Id: I435938cfa31ff3cb2bd211b6db151cc5123b262b

Separating some security related fields from btm_cb.

Bug: 301661850
Test: mma packages/modules/Bluetooth
Change-Id: I2913d363bc5d68300498e5d16c3cb30c28078289

- Remove use of init flags in logging outside android / floss
  build environment
- Add missing library dependency libbt_shim_ffi to
  net_test_btif_hf_client_service

Bug: 305066880
Test: m com.android.btservices
Change-Id: Ib5ae419193bff22aa27b5ec5e89a167b6e668569

Test: m Bluetooth
Bug: 307406671
Bug: 307408418
Change-Id: I6c1b804dfd1fd8dddbcb4901062d26789530d9b0

This patch updates the StartScan method signature to accept a scan
settings parameter. If provided, the scan settings will be passed to the
native Bluetooth stack. Otherwise, default scan settings will be used.

Bug: 304681854
Bug: 300216447
Tag: #floss
Test: ./build.py --target test
Test: m -j
Change-Id: Ie262e34ed364134e9baacaf45885d9e275581fd0

Certain controllers (e.g., Realtek RTL8822CE and RTL8852AE) are
responding to the host Remote Name Request command with multiple
Remote Name Request Complete events. The excessive response events are
causing assertions. A temporary mitigation is implemented to suppress
the assertion until a firmware fix is available.

Bug: 306242235
Test: mma -j32
Test: bluetooth_AdapterCLHealth.cl_adapter_pairing_test.floss
Tag: #floss
Change-Id: I4be160f3880d5de68da6160ccc5ace84df31ad42

Bug: 307291692
Test: m aosp_panther-userdebug
Test: Flash and bootup AOSP panther
Change-Id: I0ff27b0f261b37c98008eb6473a72398e31d0c77
Merged-In: I0ff27b0f261b37c98008eb6473a72398e31d0c77

BT stack tries to find the remote device name before the actually
pairing with it. If remote device gets connected during name discovery,
the btm_sec may not continue pairing.

Test: m com.android.btservices
Bug: 306433775
Change-Id: I684e9bd114f29a706ef3be7a43b3a3cd5dc9b62c

If an application requests service discovery on a dual mode device with a public address without explicit preference for the transport, BT stack always prefers BR/EDR transport.
If the device is already connected over the LE transport, but not on the BR/EDR transport, then service discovery should be performed over LE transport.

Test: m com.android.btservices
Bug: 306435924

Change-Id: I43cbec21798be0fea2e23e6ecc550b75e9561f8f

These libraries provide pkg-config files, so use them for the build and
link flags since newer versions of protobuf include linker flags for
abseil-cpp libraries.

Bug: 303101747
Test: mmm packages/modules/Bluetooth
  # and emerge-${BOARD} floss
Change-Id: I247784a98b433f9f999342c680ea1bbe7476a106