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

* changes:
  le_audio: Introduce Unicast fallback after Broadcast stop
  broadcast: Introduce pending broadcast
  broadcast: Introduce broadcasts descriptor

* changes:
  Remove allocation_tracker
  Inline AlarmTestHarness in its only user

ACL packets always contain L2CAP packets, so the assembler
uses the size of the L2CAP packet to determine when a
packet is completed.  If packets are smaller than the size
of an L2CAP header, wait to see if more will come before
discarding them.

Bug: 292933138
Test: atest bluetooth_test_gd_unit
Change-Id: I010f9c8b31eb4d2298cc53c9ff0a9bd6b180dc01

* changes:
  leaudio: Improve rejecting stream from remote device
  leaudio: Do not start stream if context not available but supported
  leaudio: Make sure context and locations are updated correctly
  leaudio: Remove not needed operation and return parameter
  leaudio: Add helper functions to inject context types

Those two defaults are providing the same properties

Test: mmm packages/modules/Bluetooth
Bug: 279502784
Change-Id: I62ada5912eeee005b54c9009ef7fc4da28150aa1

Bug: 279502784
Change-Id: I44daefae142ddec521a4e245e57d6ab1e706e7fe
Test: mmm packages/modules/Bluetooth

Bug: 279502784
Change-Id: I8b6400eb70b5078287f4d2d6cff5b71010b42559
Test: mmm packages/modules/Bluetooth

If during stream configuration, remote device rejects any of the
configuration stream, instead of disconnecting link as a result of not
moving forward in the ASE state machine, Android will just drop creating
stream and notify audio framework about that

Bug: 294943711
Test: atest bluetooth_le_audio_test
Tag: #feature
Change-Id: I10b13448a8d43da8f13ced6ffa0b79dfc704ddc6

If remote device indicates a Context Type as supported but it is not in
Available context types, such stream will not be started by the Android

Bug: 281957456
Tag: #feature
Test: atest bluetooth_le_audio_client_test

Change-Id: I71f099aff1f93208d405143cfb8134b8be4bda79

With this patch available group contexts and locations are updated in following
points of time
1) When device got disconnected
2) When notification arrives but group is not streaming
3) when streaming ends
4) when device got connected

Also note, that whenever leaudio code get latest available context type
it just look into connected devices

Bug: 281957456
Tag: #feature
Test: atest bluetooth_le_audio_client_test

Change-Id: I7a86c6520a708291f2f05c1750c005732bc379d6

Cleanup in the context of the context type work

Bug: 281957456
Tag: #feature
Test: atest bluetooth_le_audio_client_test

Change-Id: Ic91d2cf515ff0a47ecde70de1879147caae99850

This is needed for future tests

Bug: 281957456
Tag: #feature
Test: atest bluetooth_le_audio_client_test

Change-Id: I94b49fe2b95653e261ef02839342764599852657

Bug: 285791484
Test: N/A
Tag: #refractor
Change-Id: I0e19576644e9b471fdcf31f0b2ff9c7c0ee4c8dd

When the Bluetooth Quality Report Event came too short the process
crashed. As per current implementation there is a possibility
that a BQR event is shorter, because not all controllers' vendors
extended the BQR event. A temporary solution is to only print
the error and return.

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

This change introduces support for fallback to Unicast streaming once
Broadcast streaming is finished. To make this happend Broadcast needs to
expropriate Unicast stream then this Broadcast needs to be stopped.

Tag: #feature
Bug: 294513510
Test: atest LeAudioServiceTest
Change-Id: I2cdd8f2576b2a1bdd30e1c8fd8cff870cd4be552

In handover scenario from Unicast to Broadcast there is need to wait
until Unicast would be INACTIVE before setting Broadcast.

Tag: #feature
Bug: 286598970
Test: atest LeAudioServiceTest
Change-Id: I8baede89a34bacb6e36a0f182522c56276cb48b9

This functionallity is provided by ASAN instead.
This change also enable ASAN in tests that where
using the AllocationTestHarness.

Test: mmm packages/modules/Bluetooth
Bug: 295430884
Change-Id: Ied955493ea456bc8920fb8661f444c62a6e07a3c

Test: mmm packages/modules/Bluetooth
Bug: 295430884
Change-Id: I0be369c4ff8dc34834ba9cd77072e5a5bdd4ebd0

Bug: 279665786
Test: m root-canal
Change-Id: I58a7f18f3b5ed86fba5d72d5013ac0c76718bec4

Change-Id: I0290d05a7b46817b57bf44120c081332f3483e60
Test: atest net_test_stack_btm
Bug: 295343511

Failures are reported in following tests, which are caused
by osi_calloc returning nullptr.
This fix uses stack allocated objects instead.

- OOB_in_btm_ble_add_resolving_list_entry_complete
- OOB_in_btm_ble_clear_resolving_list_complete

Bug: 288959177
Test: atest net_test_stack_btm
Change-Id: Iae721d2d40ced468d734f7737dddac447b96c5e9

The deleted files are generated by FlatBuffers compiler.

Bug: http://b/243773680
Test: m .
Change-Id: I217ff7466e18a1c6e484b7737c5bfca1573c059e

This separates broadcast descriptive objects to dedicated descriptor by
broadcast ID as key.

Tag: #feature
Bug: 294858173
Test: atest LeAudioBroadcastServiceTest
Change-Id: I45e810899c90827df9029b71193787b6943255b6

Merge "Update the javadoc for requestMtu() to reflect the latest behavior change on Android 14." into main

Bumble clients want more control over addresses in order to preserve
pairing information. The re-use of device ids is not sufficient
because it depends on the timing of device connection. Allow clients
to specify the BD_ADDR on device creation.

Bug: 294435861
Test: m root-canal
Change-Id: I829596b6b137b1ea190926181fd9645bd8aa8276