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
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
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
This implementation of the HAL is used by pixel devices.
The implementation of GetProviderInfo is test only
Bug: 324570010
Test: TreeHugger
Change-Id: I67d17fb07c1288317290a0b1c4b07cd3be1e48c6
Previously, android.hardware.bluetooth.audio-impl was installed with no
use and the attached vintf was fulfilled by the
com.android.hardware.audio apex.
For cleanup, we no longer install android.hardware.bluetooth.audio-impl
separately (for cuttlefish) and install the VINTF inside the apex.
Bug: 312265159
Test: atest VtsHalBluetoothAudioTargetTest
Change-Id: I31e0ccd6a8c3c00565159f2be7fe3bf4d70e9ddf
Bug: 319669518
Test: m android.hardware.bluetooth.audio-update-api && make && m VtsHalBluetoothAudioTargetTest
Change-Id: Id128ed1eb09ada1e98b15351dc353fedc90fcbc8
GSI used mixed testing procedures, making some HFP session
and LE Audio related functions unavailable when testing with the
latest VTS. This fix enable HAL version checking when testing.
Bug: 315338603
Test: atest VtsHalBluetoothAudioTargetTest
Change-Id: Idb0a780a67857c76c93b13f7b3a64436f6fc647f
ParseFromLeAudioOffloadSettingFile() fails when `GetLeAudioCodecCapabilities()`
was already called in the past and `leAudioCodecCapabilities` vector is already
populated. That makes some of the VTS tests fail on
`IsOffloadOutputProviderInfoSupported()` and just return and PASS without
actually checking enything.
The doubtful checks check variables set at parsed content verification,
and should not prevent us from parsing the file again.
Bug: 319090769
Test: atest VtsHalBluetoothAudioTargetTest
Change-Id: Iab6235b5d265bb254ae6075b8c32d0eae0fc1829
When the xml file contains the "invalid" entry in the scenario record,
which do not refer to any valid config in the 'configurationList`
section, the invalid, default constructed codec configuration (a2dp codec)
was created.
Bug: 319090769
Test: atest VtsHalBluetoothAudioTargetTest
Change-Id: I19b7d1af81e5f2be3fb7261fba8781b3dc47fa12
