Fuzzer fails to get defaultServiceManager due to hermiticity issues
when vendor is enabled in cc_fuzz which uses vendor variant of
libbinder under libbinder_ndk.
Test: m android.hardware.cas-service_fuzzer && adb sync data && adb
shell
/data/fuzz/x86_64/android.hardware.cas-service_fuzzer/android.hardware.cas-service_fuzzer
-runs=10000
Bug: 301768467
Change-Id: Ief27f75f4330973fc194c77ea36cdbb826f35807
Previously, CAS APEX used ":sphal" and `android_load_sphal_library` to
open plugins from /vendor/lib/mediacas. It was a workaround because
there's no way to limit the scope to /vendor/lib/mediacas. And CAS
plugins are not SPHAL libraries.
Now, the APEX uses more explicit requirements: ":mediacas", which
limitss the scope to /vendor/lib/mediacas.
Bug: 298542407
Test: atest CtsMediaMiscTestCases:MediaCasTest
Change-Id: Id91a87e0f6ef8a761e37cabed7da8b9fed0591c2
8b19286ce3
This relands the CAS HAL APEX.
Bug: 297467514
Test: atest CtsMediaMiscTestCases:MediaCasTest
Change-Id: I741d059688ac65f42bed45e068cd00ccc5d631f5
Revert submission 2742398-cas-apex
Reason for revert: culprit for flake b/300311777, verified with go/abtd with 15 runs to make sure the flake is gone https://android-build.googleplex.com/builds/abtd/run/L46500000963034919
Bug:300311777
Reverted changes: /q/submissionid:2742398-cas-apex
Change-Id: Ia13d761d7df501fb30170a69462427198bcf924d
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
Some devices may choose to use the lazy version of CAS HAL than the
regular one, but the default one is added to pretty much all devices in
the commit 4f5534b0d381a0968e81ee20e81b791aebe5493d in the
platform/build project. Adding the lazy version will duplicate the
implementation of CAS HAL.
This is what is done in the 1.2 HIDL implementation.
Bug: 291344726
Test: Only the lazy implementation is installed to devices that require
the lazy version.
Change-Id: I88ee8d2fa4c27720817e65e5c41ffc74d6b2d61f
None of these files are executable. The .rc and .xml files shouldn't be
installed to the device image as executables either.
Bug: None
Test: Files installed on the device aren't executables anymore.
Change-Id: Id15ecc7febb56ea108155fcbd338efeb8885709a
