SCO over HCI is not an explicit VSR requirement
of the Android Bluetooth stack as SCO streams
are always offloaded.
Bug: 352247861
Bug: 297818112
Test: atest VtsHalBluetoothTargetTest
Change-Id: Id6fcec230e07897cb63c80eada47c9c58a869c73
Bug: 349290628
Bug: 315234036
Test: m packages/modules/Bluetooth
Flag: com::android::bluetooth::flags::is_sco_managed_by_audio and HFP session type only enabled when flag is enabled
Change-Id: I952f8baf347084d57162fdfd767259157f39962e
The following requirements apply only when the support API level
is lower than 34:
- [VSR-5.3.14-001]
- [VSR-5.3.14-002]
- [VSR-5.3.14-004]
Bug: 297818112
Test: atest VtsHalBluetoothTargetTest
Change-Id: I278681dfd9c30647110c55634d6e324786c48d73
Bug: 345303008
Change-Id: I0de7fcfaa64ae94e3a78d03685e661c51416ae64
Test: m packages/modules/Bluetooth
Flag: com::android::bluetooth::flags::is_sco_managed_by_audio and HFP session type only enabled when flag is enabled
We now prepare all settings that matched with the capabilities,
then find the correct context settings first.
This helps reuse the list of all settings for the next requirement.
Bug: 331490291
Test: atest VtsHalBluetoothAudioTargetTest
Change-Id: Ie27a471264f384700b754156b7db894b65b4cd82
The requirements for advertising sets are the same in the
published VSR requirements for TV and other Android devices,
so there should be no difference in the test.
Bug: 353619486
Test: mma -j32
Change-Id: I48189896138da4efacbe1ce8e46f4267e956771f
Match the supported allocation channels from the device's capability
and remove loose matching ability.
This helps with choosing the correct configuration respecting
the device's number of ASE.
We also add "name" field for easier debugging.
Bug: 331490291
Test: atest VtsHalBluetoothAudioTargetTest
Change-Id: Iefd406fcd913ce553a02242b0a2100cab431476e
New format eliminates the need for allocation and
deduplicates many configurations.
We change the file name of the default set configuration
for intergration with vendor's configuration.
We also support storing the configuration name in
the vendor's metadata for easier debugging.
Bug: 331490291
Test: atest VtsHalBluetoothAudioTargetTest
Change-Id: I0f6cfbdad1da05c35d7c758c69d7030527e1f46a
Support for the HAL android.hardware.bluetooth.a2dp@1.0 has been
removed by Ie0c624ca8e917af8e06208871a5353382fe3aada
Bug: 280901009
Test: TreeHugger
Change-Id: I745d6e0b4977fae9301b7ee344c72a63ed6c871d
Bug: 331941704
Flag: exempt, only turn on capability does not effect stack behavior
Test: m com.android.btservices
Test: atest VtsHalBluetoothAudioTargetTest
Change-Id: I36bf1e2183f237988cc77465a486e70b942409f5
Not all target device support high quality broadcast config.
Bug: 342672142
Test: atest VtsHalBluetoothAudioTargetTest
Change-Id: I87508c8deec994defb5653e51e75a00a8efcb873
Broadcast settings matching now base on context to
populate configurations
Bug: 306225778
Test: atest VtsHalBluetoothAudioTargetTest
Change-Id: I150754558ceb74f19888ef63210e2a42b3f00cd8
When we match with the remote capabilities, we don't filter by
preferred audio context, since they are suggestion.
Instead, we populate settings into 2 separated vector:
- Matched settings with matched preferred context,
- Matched settings,
We then filter by the first vector, then by the second vector.
Bug: 306225778
Test: atest VtsHalBluetoothAudioTargetTest
Change-Id: I03f322e8de509127d218a9de6b41dd39b2ebdcba
Add defaults for the case when the library is used
from within 'target/android'.
Also, switch 'BluetoothLeAudioCodecsProviderTest' to use
'defaults' instead of hardcoding the interface module version.
Bug: 307310023
Test: m
Change-Id: I7e5e70efe6a733367a8b5cbe5cffbfddf610cc6b
This increase number of test cases for new Multicodec feature
Bug: 320259251
Test: ateast VtsHalBluetoothAudioTargetTest
Tag: feature
Change-Id: I2150459bea53b522fe8da43ceed4c20eaeba7b16
Aconfig flagging storage is migrating to a new underlying storage, which
has new dependencies. Add the dependencies as a defaults.
Bug: 328444881
Test: m
Change-Id: Idca333a4f4198ac5c8724a9696a9f68433a5f39b
1s should really be the max limit, but it requires time to investigate
the failures and optimize this
Bug: 327273567
Fix: 332815453
Test: atest VtsHalBluetoothTargetTest
Change-Id: I43767b5241d967cb643401711fd7b2e015e99455
