There are some request/response pair that could be replaced in
higher-version hal. Radio service need to handle
these request/response pair specific to version number. For example,
e.g. getVoiceRegistrationStateResponse_1_2 replaces
getVoiceRegistrationStateResponse for getVoiceRegistrationState
in 1.2 radio service. We need to add util and update version number
of IRadio service to check the version for testing the correct
behavior.
Bug: 109839239
Test: run vts
Change-Id: I291690e77ea0e6e37fe75219e550f79fa44fb840
For device supporting getCapturePosition,
VTS only allowed unprepared stream to return INVALID_STATE.
Now also allow for the stream to return 0 frames similarly to the other
non started states.
Test: vts-tradefed run commandAndExit vts --module VtsHalAudioV2_0Target
Bug: 110367728
Cherry-piked from: d01dc3edac9e92981e7ae419d0e7622f753acf94
Change-Id: Ibdf8df8cb8809e98c40a50035371df6893fe4da4
Signed-off-by: Kevin Rocard <krocard@google.com>
Added RadioError::NONE as a possible return value for data call
setup API. The data call could be setup for emergency purposes
when no SIM inserted.
Test: VTS
Bug: 109767888
Change-Id: I4469c371f999b99d35f4078df000f05ee1f3c84d
Adds new EXPENSIVE_RENDERING power hint.
This adds a new library which does not affect any pre-existing
targets unless they create and add a new binary which uses this.
BUG: 110112323
Test: adb shell /data/nativetest/VtsHalPowerV1_3TargetTest/VtsHalPowerV1_3TargetTest
Change-Id: I5fb33abbbe4c4958882a106dfa400ad74013e40d
We are trying to tighten the APIs. However for this case since the
documentation was not updated, we are allowing NOT_SUPPORTED for
now and will be cleaned up in a later release.
Test: run vts -m VtsHalRadioV1_2Target
Bug: 110118713
Change-Id: Id9dd3d7bac99bed36ceb9c906189f1fea78d5a2c
This KM4 key agreement check is causing some pain on early units
that aren't completely provisioned in both locked and non-Green
(unlocked) states.
This doesn't impact KM3 devices (Pixel 2016/2017 etc.)
Bug: 110301629
Change-Id: I5a737ac8a335863b1099c29cf3c0496adeb41e15
- The VTS test checks if the time estimate is a sane value. Thus, any
arbitrary sane value is acceptable. Here we make it consistent to
IGnssDebug.hal, where a comment mentions 2017 Jan 1 as an example of
the value.
Bug: 110094003
Test: make vts, and tested on device.
Merged-In: Ic4f6b597a718ea3e98a67c7939f9e6930d44d224
Change-Id: Ic4f6b597a718ea3e98a67c7939f9e6930d44d224
(cherry picked from commit 5fa43c83e9)
This change was made for hal v2.1 but not cross-ported to 2.2.
Bug: 110167043
Test: $ adb shell ps -A | grep composer
system 630 ... android.hardware.graphics.composer@2.2-service
$ adb shell cat /proc/630/cpuset
/system-background
Change-Id: I40b8a0386a7cf67fe64b1e0e40d81b78891faaca
The .override module does not have correct rc and
sepolicy file_contexts configured, so let's allow
OEMs to keep healthd. If an OEM does want to remove
healthd they can provide a device-specific
health service impl.
Test: none
Bug: 110228707
Change-Id: I9ba32ae366df4ba58994ef0e3f9eb57cab5626f7
With this patch the KM VTS test apply the restricted requirements on
supported key sizes, EC curves, and Digests to Strongbox keymaster
implementations.
Also amend tests to use Update().
Test: Yes it is
Bug: 74519020
Change-Id: Ibec9c3398671f81dbc0ecf78e554726276160579
This is to match it with other 1.0 tests where general errors are
allowed. For newer tests we have decided to not allow these errors,
but a failure for this old test is reported when run with SIM
present.
Test: run vts -m VtsHalRadioV1_0Target
Bug: 109889468
Change-Id: If36083b7832706a50805932e8ba08e4eb397f3fe
The buffer is allocated by OPENSSL_malloc() in X509_NAME_oneline(name, nullptr, 0).
Should be reclaimed by OPENSSL_free() instead of free().
The patch is provided by vink.shen@mediatek.corp-partner.google.com
Bug: 109708231
Test: build pass
Change-Id: I66a864e3e28905eebac2e7d3a4517d4d5aaa39df
Legacy radio HAL named it SCAN and the name slipped through HAL 1.x
into HAL 2.0. I finally noticed it after HAL 2.0 was locked down.
Bug: 109740376
Test: build ow
Change-Id: I5ca4147227a7dd0c32248a279f03fb632d97258e
Per API specification "physicalCameraId" must not
contain any logical camera ids. The test case
should only use the physical ids it receives from the
camera static metadata.
Bug:109874630
Test:run vts --skip-all-system-status-check --skip-preconditions
--primary-abi-only --module VtsHalCameraProviderV2_4Target -l INFO
Change-Id: I82c5bf44f4572b3a6abdbb3101a11140907b1c9e
Status Response for basic channel can be only 2 bytes as well.
Update the test to test for 2 or more bytes.
Basic Channel if opened successfully should be closed.
Transmit test case should specify the channel number in the command.
Test: atest VtsHalSecureElementV1_0TargetTest
Bug: 109833790
Change-Id: I91c943b4297067f6ae6872efb038f1295f92f5c8
(cherry picked from commit d7700d216f0d854405bb9d99972c79f1af5b1b68)
