Strongbox may not support 1024 bit key size for RSA.
So in NoUserConfirmation test updated the key size to
2048 so that the test works for both TEE and Strongbox.
Bug: 280117495
Test: run VtsAidlKeyMintTarget
Change-Id: I32bb28001aca9b69eedb1bd3d0bcff43052d06e4
No tests are instantiated if KeyMint is present on the the device.
Explicitly allow that.
Bug: 277975776
Test: VtsAidlKeyMintTargetTest
Change-Id: I88f1c0a81f36d198dabcb1420b62a00bacdbb6e7
Revert submission 2215484-pica_cf
Reason for revert: DroidMonitor: Potential culprit for Bug X - verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.
Reverted changes: /q/submissionid:2215484-pica_cf
Change-Id: Ifd9f5cf04631e19a33b29b4b2917eaab2b506e23
Enable some tests that are bypassed on strongbox implementation.
Bug: 262255219
Test: VtsAidlKeyMintTargetTest
Change-Id: I548bddcd16c0a1ee1c1cb8266d4d99dbdff3d39b
Currently getSlicingConfigAPI always returns NOT_SUPPORTED.
But GetSlicingConfig is supported in Android U. and VTS will fail.
This change updates the expected errorcodes for getSlicingConfig API.
Tests: Builds, Boots, RadioDataTest
Bug: 228996685
Change-Id: I10cf7b0b9ba09e56605d5a498ec48c4b8972f00b
If the device is depth-only, use threshold with Y16 format rather than
IMPLEMENTATION_DEFINED.
This fixes the regression introduced by the fix for b/265984260.
Bug: 276957901
Test: atest VtsAidlHalCameraProvider_TargetTest
Change-Id: If9023f1ed17bb761abbb9be36e567264f8bf0689
The camera HAL may signal release fence after processCaptureResult.
If the VTS test waits for the release fence in the context of the
capture result, there is possibility of deadlock.
Rather, we should wait for the releaseFence in a different thread
context to really emulate the real application behavior.
Test: atest VtsAidlHalCameraProvider_TargetTest
Bug: 241281568
Change-Id: Id1d92e901aae1cab084846d252ef090fcda182d7
Requirements are tested separatedly, in vts_treble_vintf_test.
New requirements are reflected in vts_treble_vintf_test. See change
If922f97cbf9fc.
Test: TH
Bug: 247575800
Change-Id: I2ffb16e226a5bcf5166a99fc6199276b9230cf50
Merged-In: I2ffb16e226a5bcf5166a99fc6199276b9230cf50
Requirements are tested separatedly, in vts_treble_vintf_test.
New requirements are reflected in vts_treble_vintf_test. See change
If922f97cbf9fc.
Test: TH
Bug: 247575800
Change-Id: I6bc267dee4ca6145b9e7b40abde773ce5fc52e8c
Clarify what should happen to mix port profiles after
connection of an external device. Add a test to verify
this behavior.
Also, add an XML file for the test runner for
VtsHalAudioCoreTargetTest.
Bug: 273252382
Test: atest VtsHalAudioCoreTargetTest
Change-Id: I3381dd29c5922bf31fa3a8ae6fa273597e8333a1
Merged-In: I3381dd29c5922bf31fa3a8ae6fa273597e8333a1
Add 'isDefaultAudioFormat' to Utils.h.
Print the module type in 'setModuleDebug'.
Align 'suggestDeviceAddressTag' with framework code.
Bug: 273252382
Test: m
Change-Id: I0248d2e866522a63a745d4af6132b7d2b6a01564
Merged-In: I0248d2e866522a63a745d4af6132b7d2b6a01564
