Root Cause: Even when proper DAB signals are available, the test-case
"BroadcastradioHalTest.DabTune" always fails. This is because the Pro
-gramSelector created as part of the test-case is not valid according
to the AOSP documentation; it passes only DAB_FREQUENCY as the Primar
-yId, but according to the AOSP documentation, DAB_FREQUENCY is not p
-art of proper acceptable PrimaryIds in a ProgramSelector
Fix: The test-case is modified to retrieve the station list before pe
-rforming any tune in the test-case; there are three possible outcome
-s:
- If there are no stations in the station list, the test-case shall b
-e skipped
- If there are stations in the station list, but there are no dab sta
-ions being transmitted/received, the test-case shall be skipped
- If there are stations in the station list, and if there are DAB ser
-vices, extract one service from the list, and create a ProgramSele
-ctor, and send a tune-request
Test: run "VtsHalBroadcastradioV2_0TargetTest from VTS; run the test-
case - "BroadcastradioHalTest.DabTune"
Bug: 208477956
Change-Id: I874d36f9eeb460fabadd06fe1e138a35b13a5816
bug:239667706
Problem:
test tunerhal vts fail with DVBS;
Solution:
set defualt frontend to DVBS;
Verify:
s905X4/ohm
Change-Id: I79386738783309b917ec5cff89c48b2bdc99bd7c
The audio_policy_engine_configuration.xsd schema was missing
four values for the usage enum. This was causing the VTS
test to fail. These usages must be specified in the audio
policy engine configuration file, otherwise a GTS test fails.
Bug: 245303963
Bug: 246231268
Bug: 246901091
Test: atest VtsHalAudioPolicyV1_0TargetTest
Change-Id: I0161ddb33e52cbca9b425c0cbb4f32f320c43af4
(cherry picked from commit 1cbe492d59)
Merged-In: I0161ddb33e52cbca9b425c0cbb4f32f320c43af4
The audio_policy_engine_configuration.xsd schema was missing
four values for the usage enum. This was causing the VTS
test to fail. These usages must be specified in the audio
policy engine configuration file, otherwise a GTS test fails.
Bug: 245303963
Bug: 246231268
Bug: 246901091
Test: atest VtsHalAudioPolicyV1_0TargetTest
Change-Id: I0161ddb33e52cbca9b425c0cbb4f32f320c43af4
(cherry picked from commit 1cbe492d59)
Merged-In: I0161ddb33e52cbca9b425c0cbb4f32f320c43af4
Certain mutation testing -- mutateOperandLifeTimeTest and
mutateOperandInputOutputTest -- can introduce potentially very large
CONSTANT_COPY operands, which can in turn create potentially very
large Models which must be passed across binder. To avoid overflowing
the binder buffer, we estimate the size of the mutated Model, and skip
the test if that size is too high. The old logic recognizes that our
tests only have a single active binder transaction at a time, and
assumes that there are no other clients using the same service at the
same time, and so we should have the binder buffer to ourselves; to be
conservative, we reject any Model whose estimated size exceeds half
the binder buffer size. Unfortunately, sometimes the binder buffer
still overflows, because it unexpectedly contains an allocation from
some other transaction: It appears that binder buffer memory
management is not serialized with respect to transactions from our
tests, and therefore depending on scheduler behavior, there may be a
sizeable allocation still in the buffer when we attempt to pass the
large Model. To fix this problem we become even more conservative,
and instead of limiting the Model to half the binder buffer size, we
limit it to half IBinder.MAX_IPC_SIZE (the recommended transaction
size limit). To confirm that this change does not exclude too many
tests, I checked how may times the size filter function
exceedsBinderSizeLimit is called, how many times it rejects a model
under the new logic (modelsExceedHalfMaxIPCSize), and how many times
it rejects a model under the old logic (modelsExceedHalfMaxIPCSize).
Test: VtsHalNeuralnetworksV1_0TargetTest --gtest_filter=TestGenerated/ValidationTest.Test/*-*dsp*
Test: # models = 3592, modelsExceedHalfMaxIPCSize = 212, modelsExceedHalfBufferSize = 18
Test: VtsHalNeuralnetworksV1_1TargetTest --gtest_filter=TestGenerated/ValidationTest.Test/*-*dsp*
Test: # models = 7228, modelsExceedHalfMaxIPCSize = 330, modelsExceedHalfBufferSize = 28
Test: VtsHalNeuralnetworksV1_2TargetTest --gtest_filter=TestGenerated/ValidationTest.Test/*-*dsp*
Test: # models = 52072, modelsExceedHalfMaxIPCSize = 506, modelsExceedHalfBufferSize = 28
Test: VtsHalNeuralnetworksV1_3TargetTest --gtest_filter=TestGenerated/ValidationTest.Test/*-*dsp*
Test: # models = 73342, modelsExceedHalfMaxIPCSize = 568, modelsExceedHalfBufferSize = 28
Test: VtsHalNeuralnetworksTargetTest
Bug: 227719657
Bug: 227719752
Bug: 231928847
Bug: 238777741
Bug: 242271308
Change-Id: I3f81d71ca3c0ad4c639096b1dc034a8909bc8971
VtsHalEvsV1_1TargetTest does not verify any behavior depending on
a frame buffer's color format.
Bug: 240685726
Test: atest VtsHalEvsV1_1TargetTest
Change-Id: I592a0a8de5fffd98178d624ee5aac4c28245d056
EVS HAL implementations are expected to support any of following color
formats:
- RGBA 8888
- BGRA 8888
- NV21
- YV12
- Or, YUY2
Bug: 240685726
Test: atest VtsHalEvsV1_1TargetTest
Change-Id: I9fbbf1d29e52b24d8a53854faa58ac578094b305
[Description]
If filter is started after playback thread, sometimes
filter cannot get data correctly because of timing issue.
Start playback thread after filter is started
so that filter will always get data correctly.
Bug: 235185563
Test:
1. Testcase pass
Change-Id: I97c38dab1ff81c31b4bb48c8015b626b3a6325ed
wifi hal is stopped before starting wifi.
Bug: 234853504
Test: atest VtsHalWifiSupplicantV1_0TargetTest # HIDL service
Change-Id: I413c3803a6607a72cc3aa8a5fa208551be1b1032
(cherry picked from commit bfe60cda4d)
This change is a back-port of http://aosp/1877245 but adapted to allow
for devices that passed the original (but incorrect) version of the VTS
tests.
Bug: 197096139
Bug: 230074335
Test: VtsAidlKeyMintTargetTest
Change-Id: I447e6dc9dc049922725160c48c2406d79a8cffb5
Future addition of extra curves means that key size is not enough to
identify the particular EC curve required. Use the EcCurve enum instead.
Bug: 226270116
Test: VtsHalRemotelyProvisionedComponentTargetTest
Change-Id: Ia6b7d86a387cfc06db05e4ba6ff8f331e9c6345f
Merged-In: Ia6b7d86a387cfc06db05e4ba6ff8f331e9c6345f
(cherry picked from commit 915ce253a8)
This change is cherry-picked from 0dc66a2c69 which
uses RunCommandTargetPreparer to turn off/on BT for
all users on VtsHalBluetoothV1_0.
Bug: 226452499
Test: run vts -m VtsHalBluetoothV1_1TargetTest
Change-Id: I5ef42c922a0b0a037d2cf70ca83790fc95196ccb
Merged-In: I5ef42c922a0b0a037d2cf70ca83790fc95196ccb
(cherry picked from commit cf52cb0307)
Using the current user for the command to disable
BT before the test and enable after the test.
This ensures the proper command is used for
devices running in secondary user
Bug: 202873250
Bug: 226452499
Test: run vts -m VtsHalBluetoothV1_0TargetTest
-t PerInstance/BluetoothHidlTest#InitializeAndClose/0_default
Change-Id: Ica83f4959a87b8fb498b535572738e4e790c6ddb
Merged-In: Ica83f4959a87b8fb498b535572738e4e790c6ddb
(cherry picked from commit 0dc66a2c69)
TV devices can list a lot of configurations and have low
performing CPUs which causes the test to run for a significant
amount of time. From b/229824670 it seems that 10 minutes
should be enough.
Bug: 229824670
Test: atest VtsHalAudioV6_0TargetTest
Change-Id: Id7fa8eaa98bf2437fd1f676b9e5a7290df260fbd
(cherry picked from commit 0b9b03eb71)
TV devices can list a lot of configurations and have low
performing CPUs which causes the test to run for a significant
amount of time. From b/229824670 it seems that 10 minutes
should be enough.
Bug: 229824670
Test: atest VtsHalAudioV6_0TargetTest
Test: atest VtsHalAudioV7_0TargetTest
Change-Id: Id7fa8eaa98bf2437fd1f676b9e5a7290df260fbd
(cherry picked from commit 0b9b03eb71)
* changes:
FL7: Refine MIRROR_PAD specification
FL7: Refine REVERSE specification
FL7: Add some AIDL_V3 test infrastructure
Freeze neuralnetworks AIDL version as v3 for FL7
Add NNAPI specification and infrastructure for FL7.
V6 and V7 use actual device audio configuration
when testing I/O streams functionality. On low-end
TV devices this can cause the test to run for
significant time due to lower CPU speed and the
amount of multichannel configurations.
From testing on real devices, the timeout value
of 5 minutes seems to be adequate.
Bug: 211945822
Test: atest VtsHalAudioV6_0TargetTest
Change-Id: Ie233e014f9f3650f58319c4d5f5a836cfdea87ba
(cherry picked from commit 57633e5a78)
$ m android.hardware.neuralnetworks-update-api
$ m android.hardware.neuralnetworks-freeze-api
(This cherry pick required hand editing to ensure makefile
references are changed from
android.hardware.neuralnetworks-V2-ndk_platform to
android.hardware.neuralnetworks-V3-ndk_platform.)
Bug: 202280925
Test: adb shell NeuralNetworksTest_static
Test: atest VtsHalNeuralnetworksTargetTest
Merged-In: I2b2755d7376bb847b15b395e280bf352b5b9ef55
Change-Id: I2b2755d7376bb847b15b395e280bf352b5b9ef55
(cherry picked from commit 68e4300c72)
Adds operations MIRROR_PAD and REVERSE.
Extends RSQRT to support QUANT8_ASYMM and QUANT8_ASYMM_SIGNED.
DOES NOT include tests or CPU reference implementation.
(This is a slightly non-trivial cherry pick that had to be
hand-edited to compensate for the fact that certain nn::Version
changes and makefile restructurings are absent from the target branch.)
Bug: 202280917
Test: NeuralNetworksTest_static
Test: VtsHalNeuralnetworksTargetTest
Merged-In: I0b2133346b996849faac00c46885e3633c78f024
Change-Id: I0b2133346b996849faac00c46885e3633c78f024
(cherry picked from commit 04ed8595b5)
Certain OEMs' new S launches with vendor freeze cannot implement
multi-camera API.
Bug: 189053514
Bug: 211709637
Change-Id: I71b46f1e8343a5848cbe3fa55bbcd427c87b05dd
Some GRF targets launched with S release do not support getBarringInfo()
API.
Check "ro.board.first_api_level" also to return from the test-case
when the response is REQUEST_NOT_SUPPORTED.
Bug: 212384410
Merged-In: I890f54f80ff3aca3dcb2c51f20db087d453c2927
Change-Id: I890f54f80ff3aca3dcb2c51f20db087d453c2927
(cherry picked from commit becb08fac0)
