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
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
This is needed to upgrade the android_logger crate from 0.12.0
to 0.13.3.
with_max_level provides the same functionality as with_min_level.
The renaming is admittedly confusing, but the new name is accurate
and it makes sense that they deprecated and then removed the
previously poorly named with_min_level.
See crate documentation [1] and code [2].
[1]: https://docs.rs/android_logger/0.12.0/android_logger/struct.Config.html#method.with_min_level
[2]: https://docs.rs/android_logger/0.12.0/src/android_logger/lib.rs.html#227
Bug: 322718401
Test: build and run CF with the change.
Test: m aosp_cf_x86_64_phone
Change-Id: I0ca9596433967be70e9d55acb6cfbf9322741bf8
Since finder/ranging/lmp_event HAL services are new and their interfaces
are not frozen yet, they can't register services in -next-
configuration.
Bug: 322204309
Bug: 319155748
Test: run CF in -next- build
Change-Id: I4729d8763842c719682ce0124bbaaed86164a7d5
