The AOSP-version of wifi hal apex now contains the VINTF fragment in it.
Bug: 247018693
Bug: 266885060
Test: atest CtsWifiTestCases
Merged-In: Id8f196386967c3023cb5ee308d31b8cdeed7df0b
Change-Id: Id8f196386967c3023cb5ee308d31b8cdeed7df0b
The framework expects that "built-in mic" has address "bottom",
and the "buitl-in back mic" has address "back". This logic
will be incorporated into the XML to AIDL serializer later.
Bug: 205884982
Test: enable AIDL audio HAL on CF and run `atest CtsMediaAudioTestCases`
Change-Id: I5052b312b673e18e3148f917487b1f90a1e04ba6
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: atest vts_treble_vintf_vendor_test
Bug: 247575800
Change-Id: I0da1b10b2bf5c10b19b2713b56be72738a15eec1
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
Add new API to fetch IO handle which is
used for offloaded effects.
Test: atest VtsHalAudioEffectFactoryTargetTest
Test: atest VtsHalAudioEffectTargetTest
Change-Id: I82abe76036507e770f0e2aed2feef7905d85a5c9
- Rename keysToCertify to keysToSign to match param name in a few
places.
- Make clearer that P-256 is allowed in EEK.
- Make clearer that EEK curve should match that specified in
RpcHardwareInfo.supportedEekCurve.
- Add note about AAD for AES-GCM encryption.
- Add note about format of public key data in KDF context.
Test: None, comments only
Change-Id: Ie775a453b4d3941b7d24396da66681ab91978d81
In case we have a camera device that doesn't support the
Hal buffer management mode, services are required to use
the frame number and stream id to deduce the specific
buffer id and Hals are not mandated to return valid
buffer ids as part of the capture result.
Bug: 265092659
Test:adb shell
/data/nativetest64/VtsAidlHalCameraProvider_TargetTest/VtsAidlHalCameraProvider_TargetTest
--gtest_filter=PerInstance/CameraAidlTest.process10BitDynamicRangeRequest/0_android_hardware_camera_provider_ICameraProvider_internal_0
Change-Id: I3b10e91d38a13afcca45f26712cc5d5c241c2a32
These tests can now be found in the hdmi/connection directory, instead of the hdmi/directory.
Test: none
Bug:233026642
Change-Id: I60a8086e543d8a4714dda54456fd6e2dfb2a6069
Let's move canhalconfigurator from the system partition to the
system_ext partition to share a common system image across internal
AAOS builds.
Bug: 263516803
Test: build and confirm the files are relocated
Change-Id: Ibd68797aa9356e3e80662442434d939eca955576
"physicalCameraDeviceStatusChange" returns a default
ScopedAStatus that will not include a valid AStatus instance.
This will result in binder instabilities once the status
is being parceled.
Return "ScopedAStatus::ok" instead.
Bug: 253993253
Test: adb shell VtsAidlHalCameraProvider_TargetTest
Change-Id: I219f608a04aaec0631e3de58a7e0d47a30294e52
