In case remote device removes some available context types, code should
do double check on metadata which are about to send in update. Otherwise
we mind end up sending same metadata which is reduntant.

Bug: 296830689
Test: atest bluetooth_le_audio_test
Tag: #feature

Change-Id: I858edeaae54f477ce23aee917caf6b6449f3a0bf

Bug: 288519040
Test: atest bluetooth_test_gd_unit
Change-Id: If2646a878bfe4c0f4364c065ee46497b0f366cb5

Bug: 288519040
Test: atest bluetooth_test_gd_unit
Change-Id: I49d2b4ca7bc0b93fcc77d8b523224d602c8fa550

In addition, there is no need to check ASEs for a device which is not
connected.

Bug: 294750981
Test: atest bluetooth_le_audio_test
Tag: #feature

Change-Id: I412cbc0b6a542fd5013e6fa746c3316d7259b603

If GATT reported service disconvery completed when link is not
encrypted, LeAudio profiles should not to start any operations.

Bug: 290879124
Test: atest bluetooth_le_audio_client_test bluetooth_vc_test
bluetooth_has_test bluetooth_csis_test
Tag: #feature

Change-Id: I0981f8bc46a518de6bebd7ae484c0437bf8dee13

Bug: 296137900
Test: mmm packages/modules/Bluetooth
Change-Id: Ica87c6504d1259ed9ef4cdf905f274b281c822e4

Bug: 296137900
Test: mmm packages/modules/Bluetooth
Change-Id: If056a4572169cbbd5963ada752c5999d13d7fd1f

Remove unneeded import and call to into_iter().

Bug: 295883071
Test: m libbluetooth_core_rs
Change-Id: I7f8ab535a7993fa249df710505dd19e8a43c2f48

During set member pairing, there is additional verification of the SIRK
which happens after pairing.
This patch fixes possible issue which could lead to situation that
temporary device was not cleared properly

Bug: 294604632
Test: atest bluetooth_csis_test
Tag: #feature
Change-Id: I293d0a5b9c04001f974d76ee2140d52233b8e367

This CL removes the usage of broadcast intents with
BluetoothAdapter.ACTION_STATE_CHANGED action in ActiveDeviceManager,
and SapService.

Bug: 289879962
Test: atest BluetoothInstrumentationTests
Change-Id: Iaa75a3f82842b53746ec07d44ce23193b061762f

* changes:
  BQR: Fix event len for v5.0 incompatible devices
  Revert "BQR: Log error instead of crash if event too short"

Bug: 292162606
Test: atest BluetoothOppBtEnableActivityTest
Change-Id: Ie128f73dba172aaec2f9bd1800922fafcabaef61

Resolved 'Missing Library' error for android.hardware.bluetooth.audio-V2-ndk.so

Test: ./btcore_property_fuzzer
Bug: 216476246

Ignore-AOSP-First: Code of git_master is ahead of AOSP master
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:295c1b256a2717151574e24d05377ebf0a6193bb)
Merged-In: I8485a6ce391a021975fa6123e4d5932ba9aa8f5d
Change-Id: I8485a6ce391a021975fa6123e4d5932ba9aa8f5d

Bug: 263885771
Test: mmm packages/modules/Bluetooth
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:6efec2e9a2a2fcff96df585921bc8683fe1e4630)
Merged-In: Id7dd3d538d67f3d1b280bddfe629f248dced45c9
Change-Id: Id7dd3d538d67f3d1b280bddfe629f248dced45c9

When removing state machines from our maps and dropping their
references, there's a chance we leak their underlying threads if the
state machines are not quit.

This change adds doQuit() or quitNow() calls in places where we remove
state machines and drop their references.

Tag: #stability
Bug: 293920022
Test: atest BluetoothInstrumentationTests
Change-Id: I1ff69590a204eb7e92619d0ed6584ba2c27b1b3d

Test: m Bluetooth | no-op change this is just owners
Change-Id: Idbec9a0e8fa95acc88ffe2402355ae198f98a64b

Bug: 293849013
Test: m libbtif-core
Test: manual - check BQR event logs

Change-Id: Ic9bced9c1f19527c586d9f62ee02fcda8e294fc8

Bug: 292010892
Tag: #bug
Test: atest bluetooth_test_broadcaster bluetooth_test_broadcaster_state_machine
Change-Id: I0e09aa8d22b0e94c60426052e50d09ee739dbc5d

Bug: 293849013
Test: m libbtif-core
Test: manual - check BQR event logs

This reverts commit f809cb86.

Change-Id: I7f572aabb7f201d7e7ca84a082346cc0886959c7

This imports log_panics to print log when panic! is reached.
An example of the log is:
thread 'main' panicked at 'xxx': system/gd/rust/linux/stack/src/
bluetooth_admin.rs:118

Bug: 295133385
Test: mma -j32
Test: locally modify the code to trigger panic and verify the log is in
/var/log/bluetooth.log
Tag: #floss

Change-Id: I217ccd30542c5e429abfcd58626a251307353049

Test: mmm packages/modules/Bluetooth
Bug: 263885771
Change-Id: Ie39288c2d7a0b607c5ba2896e4d37812bc3ea0b1