authorizationValue checked the uion value tag twice instead of checking
the actual tag value.
Test: N/A
Change-Id: I348b5ac06801a04ca7243088d758374148910d39
* changes:
Update VTS tests for setDataWarningAndLimit
Add VTS tests for setDataWarningAndLimit HAL interface
Create VTS folder and put necessary setup code
[SP14] Add HAL to set warning quota to tehtering offload hardware
This change contains minimal modifications to perform test for
1.1 HAL. Test cases that exercise 1.1 HAL will be provideded
in follow-up patches.
Test: atest VtsHalTetheroffloadControlV1_1TargetTest
Bug: 149467454
Bug: 170699770
Bug: 170179169
Change-Id: I1df5b8d1241e9fd21930f0def395f98a8bbf3076
With current setDataLimit API, tethering offload hardware will
stop offload and trigger callback when the given limit bytes is
reached.
However, for data usage warning to work, an API that allows
tethering offload hardware to report event without stopping
offload hardware is needed.
Test: hidl-gen -Lformat android.hardware.tetheroffload.control@1.1
Bug: 149467454
Bug: 170699770
Bug: 170179169
Change-Id: I804d15f92251ef902dd2e1ff1c31ba157fa91067
* Added support for S-NSSAI within HAL
* Created struct SliceInfo that represents a S-NSSAI as defined
in 3GPP TS 24.501.
* Added slice info to setupDataCall and SetupDataCallResult
Bug: 169960538
Test: made ims phone call
Change-Id: I8d2c55bece07c599cb7d1ac0d16ad85c0acdeae5
Merged-In: I8d2c55bece07c599cb7d1ac0d16ad85c0acdeae5
In case devices don't have them.
I've also changed the version of these libraries which are used to be
explicit.
Fixes: 178483563
Test: libaidlcommonsupport_test
Change-Id: I4ebbbc84f8cb383b99d1e9a1ecc5ad6b28b8549e
Only devices with 5.10 or later kernel are required to
implement getGpuDeviceInfo().
At least one non-empty device name must be returned by
getGpuDeviceInfo().
Test: atest VtsHalMemtrackTargetTest
Bug: 176477627
Change-Id: I8c7121f4bed0e674407a22f0a772e95475243568
This format is known to the framework since Android Q, and its lack
from the XSD was an issue, which only got fixed in
Audio HAL V7.
Bug: 176536594
Test: atest VtsHalAudioV6_0Target
Change-Id: I6c312a72e50e6547bd7f206d18ba7548b7bf8556
This adds rust derive stanzas to TimeStamp, TimeStampToken, and
HardwareAuthToken.
Also removes an unused import from IKeyMintDevice.
Test: Compiles.
Change-Id: If41248f5cda8015ecb07bec5d1bc75317b803492
- Add IIdentityCredential.deleteCredentialWithChallenge()
- Deprecate IIdentityCredential.deleteCredential()
- Add IIdentityCredential.proveOwership()
- Add IIdentityCredential.updateCredential()
- Add ProofOfBinding CBOR to AuthenticationKey X.509 certificate
- Document which API versions new methods/features appeared in.
- Mention need to declare android.hardware.identity_credential system
feature (w/ feature version number) and do this for the default
implementation.
Bug: 170146643
Test: atest VtsHalIdentityTargetTest
Change-Id: Ib47c7caa5f3d6fff6919f019eee44a735dba9cf8
This format is known to the framework since Android Q, and its lack
from the XSD was an issue, which only got fixed in
Audio HAL V7.
Bug: 176536594
Test: atest VtsHalAudioV5_0Target
Change-Id: I32ccb926b5ad9202a5a6329d7069db37563ff45b
android.hardware.common.fmq.MQDescriptor needs to handle multiple file
descriptors, so changing from ParcelFileDescriptor to
android.hardware.common.NativeHandle.
android.hardware.common.fmq.GrantorDescriptor needs to keep track of the
fdIndex as well.
Bug: 176912570
Test: atest fmq_unit_tests fmq_test
Change-Id: I15f2393e6c420ae5394322b28c4523fa80f7dcc7
And add vts test to verify the tag appears in the key characteristics.
also if the tag is enforced in the hardware, afer the usage of the key
is exhausted, the key blob should be invalidated from the secure storage
(such as RPMB partition).
Bug: b/174140443
Test: atest VtsHalKeyMintV1_0TargetTest
Change-Id: Ic65b855c5a8692ab8d1281dd46562ad0844ab1b0
* Asks the device what set of capabilities are supported on the device
with respect to the Radio Hal
* The capabilities struct is left empty and will be filled
in once the first set of radio hal capabilities are nailed down later
in Android S
Test: Added cts, ran cts, and std tests
Bug: 163085807
Merged-In: I867f26bc649005e89ebf7a0b74f6fbeb2f44ac93
Change-Id: I837d82592e8ddfef5b1ff5eb0dd983a0d13383ed
In Japan FM frequency range is 76-95MHz thus FmTune test using
hardcoded 101.1MHz fails on devices preconfigured for this
region when TunerSession::tune returns INVALID_PARAMETER.
Proposed new frequency is valid in all regions.
Test: run VtsHalBroadcastradioV2_0TargetTest on hardware units
configured for Europe, US, Japan (and preferably other) analog
tuner regions
Bug: b/177916339
Change-Id: I86081fc3e1c0e0959039d5a00d96873fca454da6
This is by no means complete, but it validates basic functionality.
More is coming.
Test: VtsAidlKeyMintTargetTest
Change-Id: I0727a9f5b137b58b9a2f0aaf9935bfdc6525df8f
If a device launching with S VINTF uses health storage HAL,
it must use AIDL. If HIDL health storage HAL is used,
a build error will occur to complain about deprecated HALs.
Test: manual test that if the HIDL HAL is served on cuttlefish, then
`m check-vintf-all` shows the following error:
android.hardware.health.storage@1.0::IStorage/default is deprecated
in compatibility matrix at FCM Version 6; it should not be served.
Bug: 177470478
Change-Id: I3c28352f5f8d491ed0e1f9292b80d2083699f829
