Any fixed integer can be returned by vendor's APIs response.
Ideally it should be a random value for testing a vendor library.
Applying this to all the unit tests serial number.
Cherry-pick from:
https://googleplex-android-review.git.corp.google.com/#/c/2330821/
Bug: 38499889
Test: adb shell data/local/tmp/VtsHalRadioV1_0TargetTest
Change-Id: I491db829cca607fad9f6a21987de92269d115253
Merged-In: I491db829cca607fad9f6a21987de92269d115253
(cherry picked from commit 0e8a3be41c)
This reverts commit 6c0f76a684.
Since the root cause of the crash has been established, there is no need to keep this code around.
Bug: 36225019
Change-Id: I74e570e863a0cdec5d9029f1672e2e8066c246b5
Test: with BOARD_VNDK_VERSION := current
(cherry picked from commit 65af0612ce)
Merged-In: Ied49d6affe69099bc08a58e1d5e38052d018a2e8
Change-Id: I6278d659957829bce4ebdf44615ad25b371658d8
Bug:32023356
Test: make vts.
Merged-In: I83b454b999203fb94bc4cc50c91bd99f788131b3
secure buffer allocation for secure components
As of now, we see a crash in encoder test application on secure components
This is due to nullptr access. setting property media.mediadrmservice.enable
to 1 causes a different crash sigabrt(). In decoder securebufferallocation
call passes but we havent done anything with it. This commit needs more work.
Change-Id: I19127e39ad7daf66ac5277406e3857ec45c99e0a
add debug code
This can come in handy to view the decoded/encoded content or
for computation of psnr
Change-Id: I80e60349c76c02e5098df667223a0227f59b8324
video encoder test with anw input buffer
In this commit, anw buffers are provided as input for encoding
as opposed to byte buffers. In process IOmxNode, IGraphicBufferSource api
calls are tested
Change-Id: I7ec4af0746fe59221de42e56b344852d8fadc4f2
add support for additional color formats
Change-Id: Ia88ef9c95882958a68fee5cc68e146c3502a1b48
add eos and timestamp deviation test to video encoder
Change-Id: I9ebeaa53a986ec3f8a2ef55306877aec808d2add
add metamode support for video decoders
Change-Id: I7d6d6991cdc0ed36241d0e99c7a23675664acb10
add a timeout while processing input buffers
do not wait on input buffers processing to complete for an
indefinite amount of time. wait for a predefined duration and
leave
Change-Id: Icceaf0737a52e62f47bc052367e7ddbdc1868a46
move duplicate code to a library
move routines common across audio, video, component folders to a static
library
Change-Id: I55bf21e47571490e989b52b82c48c6e9a4b23745
add end of stream test for audio encoder
add eos test for audio encoder and some more code cleanup
Change-Id: I9d670ed53f6bba5802f919ec915e67bb0fa83518
Ensure all the buffers allocated are cycled
use all buffers provided by the component (even if it is greater than the
number of buffers needed by the bitstream)
Change-Id: I83b454b999203fb94bc4cc50c91bd99f788131b3
move duplicate code to a library - II
Change-Id: I375603feb9da303adc6a2d75ef59e43a11c3bd6d
Change-Id: I83b454b999203fb94bc4cc50c91bd99f788131b3
(cherry picked from commit 1da607c513)
HAL is allowed to return captureResult from different thread contexts.
Do not do ALOGW if this is the case.
Test: Run camera and check logspam is gone
Bug: 62068207
Change-Id: I86e77fc578953cefecf10ebc4d395edf33627e8c
Freeing the native handle isn't enough; we need to close the fence FDs
after sending them to the camera service, since that's the behavior
that the legacy HAL interface requires.
Test: Camera CTS continues to pass.
Bug: 38482274
Change-Id: I879de566dcafecc1b899d79e68b38ea39b91a37e
* changes:
Add <kernel> entry to framework compat mat
Update framework compatibility matrix
Fix automotive.* hals for oc-dev
Add evs and vehicle hal to compatibility matrix
3.18, 4.4 and 4.9 are the supported kernels in O.
Test: builds
Test: adb shell vintf (RuntimeInfo is compatible with
framework compat mat)
Bug: 38324908
Change-Id: I8b2c98e8168af651215a309c8b0b93d3c342f97d
Vts polls sensor events with max size of 1, which can cause
performance issue when batching. Increase it to 64 to help eliminate
potential performance issue.
Note this CL has no change in behavior of test.
Test: VTS target test pass on several devices
Bug: 62027156
Change-Id: I04a6791f407ec0a54eb6cd8df4d4ef41e8a89c12
Merged-In: I04a6791f407ec0a54eb6cd8df4d4ef41e8a89c12
(cherry picked from commit e337dfe3d2)
IEvsEnumerator::openCamera had a typo and the incorrect name of a related
interface in one of the descriptive comments. This fixes those issues
and updates the checksum for the interface.
Bug: 38508696
Test: build evs_app and evs default driver.
Change-Id: I24f3ca2bc3652711a4ee2ea9a37428d4bdafc509
Port of the retry logic added in HalDeviceManager for temporary IWifi.start()
failures when invoked immediately after IWifi.stop().
Bug: 38342536
Test: Run VTS tests
Change-Id: Ie58a08c45979bafa0c61fa1c8536a2c0a0cd8ed9
HAL may not support offloading, and a call to IEffect::offload
is allowed to return an error code.
Update the test to accept either OK or NOT_SUPPORTED.
Bug: 38437110
Test: still passes
Change-Id: I1822010eed73f61bb0e0ae1852739b47fa72eade
Test: bullhead, m manifest.xml -j
Test: marlin, m manifest.xml -j
Test: new devices, m manifest.xml -j
(for marlin and new devices, assemble_vintf
is invoked to check compatibility)
Bug: 38395193
Change-Id: I4201bec4753e7efe41678a736dd0a124b995fbf9
Those tests are failing because their fix
(I0ea1a4bf952527ac0711ed3cdd31c6aa53db4d2e) is dangerous to merge in O
so close to the final release.
The fix implements a rejection feature for unsupported audio format.
This rejection is required by the hal interface
but was only partially implemented in the hal.
The problem is that the framework was never tested with a hal supporting
this behavior nor some calls implemented with this requirement.
As a result I do not feel confident in merging it in oc-dev,
it might complex, hard to detect bugs.
The fix will be merged in master thus will be part of mr1.
The current patch will be reverted in master after the fix is merged.
Test: vts-tradefed run vts --module VtsHalAudioV2_0Target
Test: call/play music/record/video...
Bug: 36311550
Change-Id: Ia9e1dcec5442e2755f0bcb13d8d502663f507dbe
Signed-off-by: Kevin Rocard <krocard@google.com>
This caused b/38343526 which is a chase list issue, reverting for now.
This reverts commit 4e1fe736af.
Change-Id: Ib9ffcd11e575e3f05f54cbea17fda2f2eb3780b5
Hals are supposed to received normalized volumes, between 0 and 1.
Previously volumes outside [0,1] were clamp to this range.
This clamping has the capability to hide bugs thus return an error if
such volume is received.
Test: vts-tradefed run vts --module VtsHalAudioV2_0Target
Test: call/play music/record/video...
Bug: 36311550
Change-Id: Iab70f9c651540ea2434d10939d28c1c842db19e0
Signed-off-by: Kevin Rocard <krocard@google.com>
