A common workflow for vendors is to develop their new launching devices
targeting N-1 compatibility matrix so they can update each of their HALs
independently at different times.
This works because the target (N-1) framework compatibility matrix is squashed
with the newer compatibility matrices allowing the use of newer
interfaces.
This doesn't work when converting a service from HIDL to AIDL when the
HIDL service is marked as optional="false". It allows for the use of the
new AIDL interface, but it still requires the old HIDL interface.
Marking the old HIDL interfaces as optional allows vendors to develop
before the device targets level 8.
Test: m
Bug: 247575800
Change-Id: I4446cdaa4a44b4dae1e9eee68089bf723dd25276
This CL adds Opus as a supported A2DP codec to the BT Audio HAL and
updates HAL compatibility matrix.
Bug: 226441860
Test: A2DP sink device using bds-dev
Change-Id: I21249e3e7e76412af7ed62a3fc9ec133434cf963
The current matrix is left in this same CL because this way, downstream
modifications to the current CL will automatically get absorbed into the
level 8 compatibility matrix. A CL on top of this will disable the 7
matrix and then get reverted in the aosp/master..goog/master merge
path.
Bug: 203103997
Test: boot, vts_treble_vintf_vendor_test
Change-Id: I5c04d26e2b4dd0aac6e7d6ce3c72496081e9539d
