Revert submission 2652627-vintf_compatibility_matrix_core_hals
Reason for revert: core HALs on product/system_ext FCMs are okay, just
not deprecated versions.
Reverted changes: /q/submissionid:2652627-vintf_compatibility_matrix_core_hals
Bug: 290408770
Change-Id: I72480d05ac9efc101c7045820d1a0ef10f191f80
This reverts commit 42d17688d4.
Reason for revert: core HALs on product/system_ext FCMs are okay, just
not deprecated versions.
Bug: 290408770
Change-Id: I1d9387b10b8a20151745eec0d662454bcdcaeb95
Create the default/reference implementation of Secretkeeper HAL. Status
quo, this is non-secure implementation. In reality, the HAL should be
backed by a privileged component such a trusted app.
Bug: 291224769
Test: Topic includes VTS
Change-Id: I6a4ad50482d537f5438de6201275f4020cd827df
This compatibility matrix has not be finalized or released yet, so it's
very important that releasing devices in the 'next' configuration don't
use its contents.
Test: m
Bug: 296930312
Change-Id: I843a24308a1653bff0b4842ff71e657304bea2c8
Merged-In: I843a24308a1653bff0b4842ff71e657304bea2c8
These are all marked updatable-via-apex in compatibility_matrix.9.xml.
Adding them to compatibility_matrix.8.xml to allow Cuttlefish to build
with the apexes on 'next'
Test: m
Bug: 296930312
Change-Id: I2910695dbb7a79ca7164f7ed69437f9636d4135b
Merged-In: I2910695dbb7a79ca7164f7ed69437f9636d4135b
- with defaults user don't have to change their Android.bp when there is
a update
- update AIDL audio interfaces with android.media.audio.common.types
- update Spatialization and HeadTracking AIDL usage
Bug: 273373363
Bug: 293370815
Test: m
Test: lunch panther-trunk_staging-userdebug; m; test Bluetooth Audio
Change-Id: Ic9d8afc1d4e19e4243c66065b0a5d29156632851
Merged-In: Ic9d8afc1d4e19e4243c66065b0a5d29156632851
Add an implementation for the AuthGraph key exchange HAL, to allow
testing and policy compliance.
In real use, IAuthGraphKeyExchange instances are expected to be
retrieved from some other HAL, allowing the AuthGraph instance to be
specifically correlated with the component that uses it.
Bug: 284470121
Bug: 291228560
Test: hal_implementation_test
Test: VtsAidlAuthGraphSessionTest
Change-Id: Ib064292d60bead663af7721fd1406f2a9b5d8ecd
Introduce the AIDL methods for key exchange and the CDDLs for
the relevant input/output types that are CBOR encoded.
Use a standard comment format in CDDL files to indicate where additional
structure definitions can be found, in the hope that one day tooling
will be available to automatically check schema syntax.
Add authgraph to compatibility matrix
This CL merges the CLs: aosp/2750484, aosp/2750485, aosp/2750486 by
drysdale@google.com
Co-authored-by: David Drysdale <drysdale@google.com>
Bug: 284470121
Test: validate schemas with https://cddl.anweiss.tech/
Test: VtsAidlAuthGraphSessionTest (with nonsecure default impl)
Change-Id: I2793666ede028f8abe91569587c09dcac21c67e0
These aren't HALs and don't really have owners, but adding the OWNERS
files here to be explicit and stick to the pattern used in all the other
subdirectories.
Test: none
Bug: 296950573
Change-Id: I7cd157c79965ca40eec9bfe80d3c8dfa4c460d58
AIDL deprecation checks are only implemented in U,
so the existing V2 requirement on the T matrix
did not take effect on T branches. Hence, we
shouldn't add requirements retroactively.
Test: TH
Bug: 298318354
Change-Id: Iaf38c6d6270f4aa9c7163540a396045be9d7865a
authsecret example instance is put in APEX.
Bug: 296522705
Test: authsecret HAL starts from APEX in cuttlefish/goldfish
Merged-In: I226fd57fb1ec5c8da98c07292431df055e6078d7
Change-Id: I226fd57fb1ec5c8da98c07292431df055e6078d7
The AOSP implementation of UWB HAL will be packaged in APEX.
Bug: 296487624
Test: m
Merged-In: I89004f6064fdd3ffae13e64b051208e136a03ac1
Change-Id: I89004f6064fdd3ffae13e64b051208e136a03ac1
(cherry picked from commit f019dd3d145434992b5ccb61c6892186abfabdd8)
Cuttlefish implementation for these HALs are moved into an APEX along
with VINTF fragments. Hence we need to mark them so in FCM.
Bug: 197988234
Test: aosp_cf_x64_64_phone boots
keymint service starts from apex
Change-Id: I669ef4e215abc203f51bb21b7251aff601531ac7
It never shows up in any matrices. Only bluetooth.audio@2
and beyond are accepted.
Test: TH
Bug: 255383566
Change-Id: I110b73b2ed610d86aa351216fe46d9f803f8c3cf
ShouldCheckMissingAidlHalsInFcm now accepts arguments of
the format android.hardware.foo@1.
Test: TH
Bug: 255383566
Change-Id: I891f749190a8db8725ec1e05b190e73ab4468254
Updates version from 1 to 1-2 to reflect the fact
that version 2 is released in Android 13.
Test: TH
Bug: 255383566
Change-Id: I290aefb51fcc54d5e5a02f8c7da5876e86f61cd9
This interface has been converted to AIDL.
Test: TH
Bug: 218588089
Change-Id: I091ff4acb38c42821e99f785404e922d7b71ffa2
Merged-In: I091ff4acb38c42821e99f785404e922d7b71ffa2
AIDL is going to have a new format in fcm_exclude:
android.hardware.foo@1. This cannot be excluded
properly when mixing with HIDL, so split.
Test: TH
Bug: 255383566
Change-Id: I3df9517f12b62f5112df307528d5c3deab12cfa0