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
Provide a waitable fd as a param for IComponent::createBlockPool()
along with IGraphicBufferAllocator interface. This will remove one IPC
call from HAL to client to get a waitable fd during blockpool creation.
Test: m
Bug: 254050314
Change-Id: I38d9bde987793e352299385fb141e484c758f89d
To make the binary smaller in APEX, use static linking.
For aosp_cf_x86_64_phone target, the APEX is reduced from 1576960 to
643072 (by 933888).
Bug: 306314086
Test: m
Change-Id: I1d745f64fb98a97e7adb417870034044a03ce88c
- moved apex definition beside the HAL binary definition
- updated README.md about installation
Bug: 306314086
Test: follow README.md to test the virtual FP HAL
Change-Id: I4bb2572ca79c93cb32a273625f4e965c2505e48a
The following are the updates to the fuzzer:
1. Randomized order of apis.
Test: ./keymaster4_utils_fuzzer
exec/s: 4950
Bug: 302149569
Change-Id: Ie5d80a4e1d28ddd76a9c16609d20995d93710965
This bundles the default implementation used by the cuttlefish.
Bug: 300011111
Test: VtsHalSecureElementTargetTest
Change-Id: Ib723fcbb6748675f6dae2449aad5a71a54cce594
- CameraStreamBuffering test is modified to use the minimum number of
frame buffers that is required to run a camera pipeline for a single
client instead of using an arbitrarily chosen number, which may not
work for certain device implementations.
- Fix a name of v1.0 EvsManager implementation in
VtsHalEvsV1_0TargetTest.cpp
Bug: 305642713
Test: atest VtsHalEvsV1_0TargetTest and
atest VtsHalEvsV1_1TargetTest
Change-Id: Ieec986dbdf947311e0bc86871432da8a988d37ad
(cherry picked from commit 2d8834dc96)
- CameraStreamBuffering test is modified to use the minimum number of
frame buffers that is required to run a camera pipeline for a single
client instead of using an arbitrarily chosen number, which may not
work for certain device implementations.
- Fix a name of v1.0 EvsManager implementation in
VtsHalEvsV1_0TargetTest.cpp
Bug: 305642713
Test: atest VtsHalEvsV1_0TargetTest and
atest VtsHalEvsV1_1TargetTest
Change-Id: Ieec986dbdf947311e0bc86871432da8a988d37ad
- Removes a requirement of the landscape aspect ratio of the captured
frames because the Extended View System now allows the video streams
in any aspect ratio
- Increases the maximum latency of the video stream start request from
500 ms to 1 second to accommodate the camera system design with the
additional processing units outside of the head unit
- Reduces a number of additional buffers to allocate from 6 to 2 in
CameraStreamBuffering test, to be consistent with comments
Bug: 204835095
Bug: 305642713
Test: atest VtsHalEvsV1_0TargetTest and
atest VtsHalEvsV1_1TargetTest
Change-Id: Id41bde10964b650f78e76d4f97a4588367f7c7fc
Merged-In: Id41bde10964b650f78e76d4f97a4588367f7c7fc
(cherry picked from commit 7bc98ce6ed)
There are several reasons why parsing the canonical XML
configuration for the remote submix module will not work
correctly (see the commend in the code).
Since de facto all vendors use the canonical configuration
XML for the remote submix, substitute parsing it with
a correct hardcoded version.
Bug: 205884982
Test: atest VtsHalAudioCoreTargetTest
(cherry picked from commit ea604d50de)
Change-Id: Ib9d9da25d315ff4ce36c1870241fb61d95fcca88
For external (non-attached) device ports that have dynamic
profiles, 'connectedProfiles' must be provided. They are
used when 'ModuleDebug.simulateDeviceConnections' is enabled.
Bug: 205884982
Test: atest VtsHalAudioCoreTargetTest
(cherry picked from commit a29393db39)
Change-Id: I69707d610c34f8f1eae9ef81768b76c40e985c0f
Added a virtual method Module::getMicrophoneInfos
so that vendor implementations can provide actual
data about device microphones. This information
is not part of the APM config file.
Bug: 205884982
Test: atest VtsHalAudioCoreTargetTestTest
(cherry picked from commit dc9d1a4b42)
Change-Id: I3ea9ba8da79fd29f8d69c5a575a57851d73df7b8
Since the parsed XML uses compliant separator for lists
in attribute values, there is no need to use legacy
'maskFromString' function.
Bug: 305281224
Test: atest VtsHalAudioCoreTargetTest
Change-Id: Ib257fd010b923ac651931e5976f9b1363d693f1b
The default implementation now loads the HAL configuration
from the legacy XML configuration file which was previously
consumed by the framework directly.
Note that errors in the config file will lead to crash
of the XML parser, pointing out to the source of the problem.
IMPORTANT NOTES:
- Never use untested legacy config files with production
devices.
- Make sure that all possible configurations (for example,
BT offload on/off) are tested.
Bug: 205884982
Test: atest VtsHalAudioCoreTargetTest
(cherry picked from commit 00a7307862)
Change-Id: Id1002cb065e7cc19bdd520aca15b3fe5d39e5853
