It turns out we had a bug (b/263844771) in how RKP support was
detected, and that was fixed. However, due to this bug, some S chipests
shipped without RKP support which is now required by the tests.
This change drops the RKP requirement from S chipsets. There should be
no new S chipsets, so this effectively grandfathers in the previous
ones that were skipped by the RKP VTS tests.
T+ tests (both VTS and other suites) will verify that RKP support is
there, so there is no gap introduced by this change.
Bug: 297139913
Test: VtsAidlKeyMintTargetTest
Change-Id: I387e5f058ada698747aac103c1745682291f2d1c
The test case for an auth-per-operation HAT with an invalid HMAC
is wrong -- it is re-using the previous HAT, which fails for a
different reason (has an old challenge).
Fix the test to use the HAT that's wrong in the intended way.
Bug: 297333975
Test: VtsAidlKeyMintTargetTest
Change-Id: I15fe9b0c1b53452df0f67dd44534fdb80a6c2a9c
This empty method is different from the old one - it aligns with
std::string definition.
Bug: 295394788
Test: make checkbuild
Change-Id: I98dad222b149e6052b7dc63c477d84c9eb011dd3
com.android.hardware.threadnetwork is a new VAPEX containing
threadnetwork HAL. It also includes ot-rcp.
Bug: 296966113
Test: vts-tf > run vts -m VtsHalTheadNetworkTargetTest
Change-Id: Id2028d755f9b0dcc06ccd817bddf3195efb5595b
This can be shared by many AOSP com.android.hardware.* APEXes defined in
hardware/interfaces.
Bug: 296524155
Test: m
Change-Id: I8d5bf7d9cf8fe4b502af9240027529d61c9776af
The variable `mDeathRecipient` will automatically free the allocated
memory when it is destructed. This CL deletes the code for manually
releasing the variable `mDeathRecipient` to avoid the same variable
being freed twice.
Bug: 296617022
Test: Run fuzzer test.
Change-Id: I733f7f8d26e48a9434d41c5098f39ad91208abeb
In the case when there is a problem with the legacy APM XML file,
the converter provides a default surround sound config. However,
the default implementation of IConfig::getSurroundSoundConfig did
not take an advantage of that, and was returning an empty config,
which is not accepted by VTS.
Also, improve logging messages: clarify the situation when no readable
audio policy XML file found, and use outer functions name for lambdas.
Bug: 293978054
Test: atest VtsHalAudioCoreTargetTest
Change-Id: Iae069a0498009605ef5ededb9c9112efab08548a
Ideally, we should migrate to std::filesystem, but libc++fs is not
available for vendor binaries until b/175635923 lands.
Bug: 295394788
Test: m checkbuild
Change-Id: If285034d7b343531082d0176ab26bf51390714d0
otherwise a negative offset will result in long sleep
Bug: 295055755
Test: atest android.media.audio.cts.AudioPlaybackCaptureTest
Change-Id: Ie941cc2525e3ea42b53106ae3a65242794b1dd1b
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)
Previously, .rc file is installed separately. Now it's installed as part
of the uwb-service binary installation.
Bug: 296487624
Test: launch cuttlefish / uwb-service runs with /dev/hvc9
Change-Id: I49108c74a5ca964818c90407cc7916d80439d5ab
