As of VNDK deprecation, any libraries that defines vndk is no longer
valid anymore. This change removes all VNDK definition(s) from modules
which was VNDK.
Bug: 328994089
Test: AOSP CF build succeeded
Change-Id: Ifdade9c052db29c989ce7d804ba725361c4c0f8e
Merged-In: Ic4f19113c1a25dc1fb60cdfbf9c0f2d8d7d09726
This CL is created as a best effort to migrate test targets to the new Android ownership model.
It is based on historical data from repository history and insights from git blame.
Given the nature of this effort, there may be instances of incorrect attribution. If you find incorrect or unnecessary
attribution in this CL, please create a new CL to fix that.
For detailed guidelines and further information on the migration please refer to the link below,
go/new-android-ownership-model
Bug: 304529413
Test: N/A
Change-Id: Ibe1360ca3f7eb919834715aa90b0b842fbcd0692
Exclude logical camera devices from CameraUseStreamConfigToDisplay test
case.
Bug: 275049370
Test: atest VtsHalEvsV1_0TargetTest and
atest VtsHalEvsV1_1TargetTest
Change-Id: If6b31d94bdbffd2f4e9ab9bd5c8957ec85904187
(cherry picked from commit d5732b6bbf)
- HighPriorityCameraClient test case is not executed against logical
camera devices because clients are not allowed to change camera
parameters via logical cameras.
- CameraStreamExternalBuffering test case closes logical camera device
explicitly, to avoid any influence on following test scenarios.
Bug: 319165229
Test: atest VtsHalEvsTargetTest
Change-Id: I734d701a2056ab84fe74179b083c3f6c5463447b
- 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)
Remove H2BGraphicBufferProducer usages from the default EVS HAL
implementation.
Bug: 297601247
Bug: 298091684
Test: Run evs_app on the cuttlefish emulator.
Change-Id: Ibca21d8e9cf87deb79c0050f9adcf02b5f16d34b
- Fix a typo on ExposureParameters.coarseIntegrationTimeLShift.
- Add a comment that describes a descriptor field of GridStatistics.
Bug: 276675923
Test: build
Change-Id: Ida93c21c9de7f7c1d661c790d82342750d5f29fe
They are mostly copied from the HIDL 1.0 display test cases, with some minor changes.
Test: `atest VtsHalEvsTargetTest`
Bug: 275626422
Change-Id: Ica5379e7f021083b65ad8abf320f7751c1432c9e
This reverts commit d12e05929a.
Bug: 218588089
Test: 1. Build cf_x86_64_auto lunch target.
2. Launch cvd in the accelerated graphics mode.
3. atest VtsHalEvsTargetTest and confirm that EVS HAL
implementation passes all test cases except
CameraStreamExternalBuffering that is not supported yet in new
implementation.
4. Run evs_app and confirm the color bar pattern is shown on the
display.
> adb root && adb shell evs_app --test
5. Do the same on sdk_car_x86_64 lunch target.
Change-Id: I4647d0ef7a2bd98fdfcb3833bfb060b4063bc42e
Multiple displays can be opened concurrently, so display ID
is needed when getting status of active displays.
Test: build
Bug: 262779341
Change-Id: I12af698be85ba72f0fb81f143441956dd0bfe1d2
This implementation is used for the emulators.
Bug: 218588089
Bug: 270753093
Test: 1. Build cf_x86_64_auto lunch target
2. Launch cvd in the accelerated graphics mode
3. Run evs_app and confirm the color bar pattern is shown on the
display.
> adb root && adb shell evs_app --test
Change-Id: I8179e74fc9f0b9547316368fca507e5c62ca5680
To make the sensor embedded data available to EVS clients, this change
adds new fields to BufferDesc and declare necessary data types.
Bug: 191939108
Test: build
Change-Id: Iaa41554e49c7ff30c11d391b00eae12dfef9e99b
