It was added in aosp/3038254 and removed in a merge conflict resolution in ag/27273371
Test: m
Bug: 346861728
Change-Id: Ie1d3897697e40fca1067442348d400bf6bdee880
There are changes in common audio libraries that force the sounddose
implementation to be bumped if any of the other audio implementations
are bumped.
Since we want to deprecate the sounddose interface and remove it from
FCMs > 202404, we need to retroactively allow the new sounddose version.
The other audio interfaces don't need this treatment because the newer
versions are added to the newer FCMs and we allow older devices to
implement them.
Test: m
Bug: 361383071
Change-Id: I195053bb6c5b6cb01584398eafc86f8fbcdd1148
When supporting the audio AIDL HAL, we do not use the ISoundDoseFactory
anymore. Removing it from the compatibility matrix.
Flag: EXEMPT bugfix
Test: trivial
Bug: 356641174
Change-Id: I241c4b93ea6aa4e5499bc9e924d6df4f4bd464a7
Add a new attribute type which value could only be device_fcm and
product_fcm if set to the vintf_compatibility_matrix module type which
could be used to generate framework_compatibility_matrix.device.xml and
product_compatibility_matrix.xml in soong to convert the original Android.mk
Bug: 352234038
Bug: 344445679
Test: lunch aosp_cheetah-trunk_staging-userdebug
m framework_compatibility_matrix.device.xml \
product_compatibility_matrix.xml
Test: lunch aosp_trout_x86_64-trunk_staging-userdebug
m framework_compatibility_matrix.device.xml \
product_compatibility_matrix.xml
Test: lunch aosp_cf_x86_64_phone-trunk_staging-userdebug
m framework_compatibility_matrix.device.xml \
product_compatibility_matrix.xml
diff $ANDROID_PRODUCT_OUT/system/etc/vintf/compatibility_matrix.device.xml \
device/google/cuttlefish/system_image/compatibility_matrix.device.xml
Change-Id: I1690cf29462c91f5ab80f7a78f6df9cdb6abbf2f
After most compatibility_matrices Make modules have been moved to Android.bp there are some unused variables and logic, so remove them to reduce the complexity which helps conversion to Android.bp and reviewing.
Bug: 352234038
Test: CIs
Change-Id: Ic2f4538b3e50cc1ca573634cd46eb64c4013420a
Vintf finalization requires adding the new API levels to the libvintf
code. Add the automation script for that with the finalization
process.
This process will be skipped if the code already has been updated.
Bug: 331696132
Test: tools/finalization/build-step-0-and-m.sh
Change-Id: Ibd6a71337d88b71708ef378e3862e6c67364b92b
202404 FCM is now frozen and supported internally. Add the 202404 FCM to
all builds to allow freezing 202404 HAL interfaces and serving the new
versions in the next release config.
Create 202504 FCM for people to start working on the 202504 interface
changes. This new file is based on the internal 202504 file.
Merged-In: Ie6d38d27a287e258c30516e0030ad8c931d06432
Test: m
Bug: 328236210
Change-Id: Iaef8117a18441951070816344aecd24fdd4969f4
HIDL is no longer supported in devices targeting 202404 vendor
interface.
This removes the tmp FCM fragment that was being used to declare the
media.c2 HIDL dependency.
Test: m && launch_cvd
Bug: 218588089
Change-Id: I40973f5cdc9f4c9ca891929c8e8f865119322c17
We want to run bump.py during finalization. We don't want to have to
update Level.h and the VTS tests that early.
So this CL removes the dependency on Level.h and requires the
current/next letters of the API levels for the kernerl configs to be
passed as arguments.
Test: bump.py 202404 202505 v w
Bug: 279809333
Change-Id: If8f281eccf62d380949a5ea9f5d0d3bb2d7f19ab
The next year's compatbility matrix is added to a conditional statement
so it's only available on in-development release configurations.
The curent year's compatibility matrix is moved from the conditional
statement to always be added to all release configs.
The next year's compatibility matrix level is set to the next year's
level after copying the current matrix file.
Test: ./bump.py
Bug: 279809333
Change-Id: Id711ba79110c8775f715eddf37a9bf51b073ec91
Re-landing now that the downstream devices are targeting later FCMs.
Test: m
Bug: 279809679
5f679f3deb
Change-Id: I29de76f787cadb801b60724526fa2851ba599dcc
Put it in its own FCM so it's easier to manage while HIDL C2 is being
depregated with flagging.
This interface will not be allowed in the 202404 vendor interface.
Test: launch_cvd
Bug: 218588089
Change-Id: I24e14db4edd161a574a4404c8b7271c91dc1243a
This is the default now.
Test: TH
Bug: 247575800
Change-Id: I0d7156f4e526b276c47ac66a5125bf2a219b3ed8
Merged-In: I0d7156f4e526b276c47ac66a5125bf2a219b3ed8
On Cuttlefish, the implementation of the ISecretkeeper HAL runs
in-process in the HAL service, and so is deliberately marked as being
the /nonsecure instance to make that clear.
A real device that's running Secretkeeper inside a secure environment
should report that instance as being the /default instance.
So allow either in the compatibility matrix.
Bug: 306364873
Test: build, VtsAidlAuthGraphRoleTest, VtsSecretkeeperTargetTest
Change-Id: Ifb58d8bb9318707b714a345adc1b1b4198054f81
