Test uses ::android::GetComponentRole to get OMX role for media type
that only supports standard types (on GSI where VTS is run).
Bug: 164550113
Bug: 171536493
Bug: 194827876
Test: atest VtsHalMediaOmxV1_0TargetStoreTest
Change-Id: Ia9e64c8d887518f6c7d8c650a942bad7ce3457f0
The current timout of 5 mins is not enough for
setActiveConfigWithConstraints to complete on devices
which have ~30 display modes and which can't do seamless
switching. The test needs 8 mins to complete locally --
increasing the timeout to 15 to have some margin.
Bug: 188686850
Test: atest VtsHalGraphicsComposerV2_4TargetTest
Change-Id: I07cf1825c23e2467852d5cd93436eb9dee23b408
This would ensure that 1.4 vts tests are run with
ISupplicant 1.4 support.
Bug: 194979754
Test: atest VtsHalWifiSupplicantV1_4TargetTest
Change-Id: Ifaa3e1bb27f1df350b83fb7a4c05b6251a7c2d10
For those high-resolution codecs, they are 24 or 32 bits per sample, so
the buffer size must be the LCM of 16, 24, and 32.
Bug: 194980528
Test: A2DP playing with aptX and / or LDAC
Change-Id: I788e185496dea4a1b40fa369e032a4f8491b835b
Merged-In: I788e185496dea4a1b40fa369e032a4f8491b835b
(cherry picked from commit a0cc24730e)
Not all devices have an IRemotelyProvisionedComponent HAL, so on those
devices 0 of the tests in VtsRemotelyProvisionedComponentTests will be
run.
Fixes: 194770385
Test: Ran tests on two devices: one with and one without the HAL.
Change-Id: I8624096158f29058189dfab7cd876804ae178e60
* changes:
IFace: update VTS test to pass std::nullopt for previewSurface
IFace: update default implementation to use optional previewSurface
IFace: annotate the previewSurface as @nullable in enroll
Update test case - CameraStreamExternalBuffering
Use native resolution instead of fixed test buffer 640x320
Bug: 190127973
Test: Manually run VTS on seahawk
Change-Id: I11043af4215fb9c5a2658591e9bdf9e468542a1b
This CL adds a comment that discourages use of this interface. The AIDL
interface, IFingerprint, should be used instead.
Bug: 160189286
Test: hidl-gen -L check android.hardware.biometrics.fingerprint@2.3::IBiometricsFingerprint
Change-Id: Ifafb191ac16e03e60d677fce6dc9e41e87bad0c0
If the previous setRadioPower_1_5_emergencyCall_cancelled test has just finished.
Due to radio restarting, modem may need a little more time to acquire network service.
Otherwise, the barring info will be empty.
Bug: 191866257
Test: atest VtsHalRadioV1_5TargetTest
Change-Id: I9ae4e7a07b9f47353554ffb63a23b6518aa344b7
Also add carrier frequencies to the mock GnssStatus and GnssAntennaInfo
Bug: 194117673
Test: atest GnssStatusTest
Change-Id: Ib22aefe8e4dc8389a933e9009e36872287546c7b
VtsHalRemotelyProvisionedComponentTargetTest was picking up the same
config file (AndroidTest.xml) as VtsAidlKeyMintTargetTest. When atest or
TF was used to run VtsHalRemotelyProvisionedComponentTargetTest, it
actually ran VtsAidlKeyMintTargetTest.
Add a separate test config file so that we run the correct test binary.
Test: atest VtsAidlKeyMintTargetTest
Test: atest VtsHalRemotelyProvisionedComponentTargetTest
Fixes: 192824779
Change-Id: I7ba0f8d364690209722f9a06c6c0ce2957781beb
Prior to V7 the test which exercises
IStreamIn.getActiveMicrophones was using a hardcoded
configuration for the input stream. This configuration no longer
works for some of new devices. To fix that, the part of the test
which calls getActiveMicrophones has been moved into a separate
test--a descendant of InputStreamTest which is parametrized
using the actual configuration of the DUT.
Tests for HAL versions prior to V7 are not affected
because they don't use a full parser for the DUT config.
Bug: 193849687
Test: atest VtsHalAudioV7_0TargetTest
Change-Id: I00fe8fedb6bfc6e034387b35c88f954cb2638dfa
If the major version is greater than or equal to 6, the test tries
to set the mode to AudioMode::CALL_SCREEN. However, it doesn't set
back to AudioMode::NORMAL. Replace all ASSERT with EXPECT to ensure the
test can reach to the explicit call to reset to AudioMode::NORMAL.
Bug: 194022995
Test: atest VtsHalAudioV7_0TargetTest
Change-Id: Ib9b6e310965a85b016853b72c60716fa054641c6
Update memtrack hal documentation to allow reporting the global
total GPU-private memory from the getMemory() API.
Specify how to handle unsupported memtrack operations.
Bug: 193226716
Bug: 193465681
Bug: 192621117
Test: N/A
Change-Id: I6fcebd16fafdc34cc662137784e86750ee907eee
Commit f18a8328a1 ("keymaster: Relax testing under GSI") disabled
some tag checks for devices running with GSI, but detected GSI by
looking for an absence of the ro.boot.vbmeta.device_state property.
This property is currently present on GSI, so instead detect GSI using
the existing is_gsi() helper, which checks ro.product.system.name
against "mainline".
Bug: 192513934
Test: atest VtsHalKeymasterV4_0TargetTest:PerInstance/AttestationTest
Change-Id: If3c7d84a9e091b9b0842e4d8919453600bc239ea
Ignore-AOSP-First: manual merge to aosp/master to follow