Makes a ABI preserving change to radio hal by adding deprecation
comments for following interfaces:
- startLceService
- stopLceService
- pullLceData
- lceData
- setSimCardPower
- setIndicationFilter
- setupDataCall
- deactivateDataCall
- startNetworkScan
- startNetworkScan_1_2
Bug: 170288130
Test: make
Merged-In: I4563b7081dec6fa64b7faff7c8e3c2c3b1239880
Change-Id: I4563b7081dec6fa64b7faff7c8e3c2c3b1239880
(cherry picked from commit 1fd7cb029b)
* Created utility method in v1_6 HAL to access radio hal capabilities
* Created static library to support getting the capaiblities response
* Created RadioResponseWaiter to encapsulate the notify \ wait logic
used when waiting for an asynchronous response from the HAL
* Usage: if (getRadioHalCapabilities().modemReducedFeatureSet1) { ... }
Bug: 181895757
Test: Accessed default hal capabilities
Change-Id: Ie0a727d4e9d268ad03cf3fa793aa456a95c89f5b
Merged-In: Ie0a727d4e9d268ad03cf3fa793aa456a95c89f5b
Specifies how HAL needs to handle the frame counter
for input and output streams on standby and flush.
Also add whitespaces before "Optional method" spec
for better readability.
Bug: 161253754
Test: in progress
Change-Id: I357739a2382f9425da74fcddbe7ab720be1f0e18
The format of test key was not PKCS8.
Correct it and add the generating command for reference.
Fixed: 181701819
Test: VtsHalKeymasterV4_0TargetTest --gtest_filter=*strongbox*
Change-Id: I7793c781eee976bc813b6fea77762b173f95e06a
A problem where credstore didn't always use the TA-generated challenge
in the verification token was fixed in aosp/1619825. With this bug-fix
we can now reliably check that the passed-in verification token is
always fresh.
Bug: 181893400
Test: atest android.security.identity.cts on emulator
Test: atest VtsHalIdentityTargetTest
Change-Id: Iffdf026475da6321764561972aae27a82ab94530
Detail what is expected to be returned by the different memtrack types.
Add what the device name is expected to be in getGpuDeviceInfo()
Bug: 181704406
Test: N/A
Change-Id: I5e9fe0bf5e630a8a0ec8394fa4f508657e4a56a7
Vendors can have vendor-extended device types and
audio formats supported by their HALs and frameworks.
VTS tests are built using AOSP sources, thus they don't
have these vendor modifications. Ensure that VTS tests
behave correctly when dealing with audio policy manager
configurations that contain vendor extensions.
Since verifying this behavior requires using specially
crafted APM configs, verification is done using
unit tests.
Test: atest HalAudioV6_0GeneratorTest
Test: atest HalAudioV7_0GeneratorTest
Change-Id: I9dc1a18863418a8fbd7d1dc14abc844fd9060ca5
This test tries to modify an encrypted message to ensure that the
result can't be decrypted, but if encrypting the messsage fails
first then there's nothing to modify.
Bug: None
Test: Ran against a Strongbox implementation that refuses to
encrypt the message using Digest::NONE
Signed-off-by: Bill Richardson <wfrichar@google.com>
Change-Id: Ib4d389a47702edd56a4e7d2b334dc89d0c3972a1
