Commit Graph

15152 Commits

Author SHA1 Message Date
Anil Admal
f22b39c457 Merge "VTS 1.1 TestGnssMeasurementCallback test must allow 1.1 or 1.0 versions" into qt-r1-dev 2019-07-19 18:12:24 +00:00
Valerie Hau
7f42547069 [automerger skipped] Merge changes from topic "FixSRGBSetColorMode_VTS_qt-dev" into qt-dev
am: 818fff840a -s ours
am skip reason: change_id Ie8f53effe3e6e29a4523ebfa450c79fdf96ed585 with SHA1 37d1599e0b is in history

Change-Id: I78053cd905db78c02ea6848a4b0fc9fb3d619b3c
2019-07-19 08:08:48 -07:00
Valerie Hau
818fff840a Merge changes from topic "FixSRGBSetColorMode_VTS_qt-dev" into qt-dev
* changes:
  DO NOT MERGE: Fixing SRGB for devices that do not support SRGB color mode
  VTS : fix vts fail [1/1]
2019-07-19 14:49:44 +00:00
Anil Admal
6abdaac714 VTS 1.1 TestGnssMeasurementCallback test must allow 1.1 or 1.0 versions
Fixes: 137839372
Test: atest VtsHalGnssV1_1Target
Change-Id: Ie3b1fa8b4738c03bff7924396b5eb5c6774841f1
2019-07-18 18:40:53 -07:00
Roshan Pius
354c2c6c55 Merge "hostapd(vts): Add a property for SAP interface" into qt-dev
am: 896c71a7d2

Change-Id: Ib1c81c3a07e8145edc00e783357079304eff9f75
2019-07-18 18:18:57 -07:00
TreeHugger Robot
896c71a7d2 Merge "hostapd(vts): Add a property for SAP interface" into qt-dev 2019-07-19 00:57:14 +00:00
Roshan Pius
9a8538b4ee hostapd(vts): Add a property for SAP interface
Changes to the VTS test to support OEM's who use a separate
dedicated SAP interface.

Note: This is a VTS test change only. The default implementation does
not still support a dedicated SAP interface (OEM's can obviously
customize the default implementation for their devices).

Bug: 136645414
Test: None (verified by partner OEM)
Change-Id: I42b87bf90cfa90c7c218309164ab2b77f3685f9e
2019-07-18 14:38:41 +00:00
nxp72763
a17bbf6d31 Merge "Align NFCEE ID range with NCI 1.0 in VtsNfcv1.2 test" into qt-dev
am: fc480f5904

Change-Id: Ifc02910c85e47515bc990de4b08a4f4930f6576b
2019-07-18 00:19:17 -07:00
zhangweiwei
588b4ead25 Adapt change clearkey to Lazy hal
am: 0a50473369

Change-Id: I9710b3b0caeb98853981728c47226bccce2445c6
2019-07-18 00:11:19 -07:00
TreeHugger Robot
fc480f5904 Merge "Align NFCEE ID range with NCI 1.0 in VtsNfcv1.2 test" into qt-dev 2019-07-18 07:06:16 +00:00
zhangweiwei
0a50473369 Adapt change clearkey to Lazy hal
Exempt-From-Owner-Approval

Bug:135896867
Test: vts-tradefed run commandAndExit vts-staging-default -m VtsHalDrmV1_1Target

Change-Id: Iadba7a7afdccfe8a6299e3c0e1e03f63a58c5ca8
2019-07-17 23:24:56 +00:00
Anil Admal
954f4fef65 Merge "Add GetLocationLowPower VTS 2.0 test" into qt-r1-dev 2019-07-17 21:38:29 +00:00
Valerie Hau
37d1599e0b DO NOT MERGE: Fixing SRGB for devices that do not support SRGB color mode
Bug: 135375302
Test: build, boot, VtsHalGraphicsComposerV2_2TargetTest
Change-Id: Ie8f53effe3e6e29a4523ebfa450c79fdf96ed585
2019-07-16 21:24:57 +00:00
Valerie Hau
2f3553e1ed DO NOT MERGE: Fixing SRGB for devices that do not support SRGB color mode
Bug: 135375302
Test: build, boot, VtsHalGraphicsComposerV2_2TargetTest
Change-Id: Ie8f53effe3e6e29a4523ebfa450c79fdf96ed585
Merged-In: Ie8f53effe3e6e29a4523ebfa450c79fdf96ed585
2019-07-16 14:24:02 -07:00
jie.yuan
70e5b556ef VTS : fix vts fail [1/1]
Problem:
VtsHalGraphicsComposerV2_1Target#GraphicsComposerHidlCommandTest.PRESENT_DISPLAY_NO_LAYER_STATE_CHANGES fail
the testcase setcolormode SRGB without check if current device support SRGB

Solution:
change setColorMode from SRGB to NATIVE

Verify:
verify in on franklin

Bug: 135375302
Test: build, boot, VtsHalGraphicsComposerV2_1TargetTest
Change-Id: I646c263d96b03f9d30e6563a45cff37835001609
Merged-In: I5eebe5f530e3b62037d669992cf2eca0849f10be
2019-07-16 14:19:05 -07:00
jie.yuan
0d7f7882e7 VTS : fix vts fail [1/1]
Problem:
VtsHalGraphicsComposerV2_1Target#GraphicsComposerHidlCommandTest.PRESENT_DISPLAY_NO_LAYER_STATE_CHANGES fail
the testcase setcolormode SRGB without check if current device support SRGB

Solution:
change setColorMode from SRGB to NATIVE

Verify:
verify in on franklin

Bug:135375302
Test: build, boot, VtsHalGraphicsComposerV2_1TargetTest
Change-Id: I5eebe5f530e3b62037d669992cf2eca0849f10be
Merged-In: I5eebe5f530e3b62037d669992cf2eca0849f10be
2019-07-16 13:39:09 -07:00
Anil Admal
03bc98e028 Add GetLocationLowPower VTS 2.0 test
- Run test only if LOW_POWER_MODE capability is supported.
- Modify the corresponding VTS 1.1 test to run only if the GNSS
  HAL version is 1.1.

Fixes: 127434062
Test: atest VtsHalGnssV2_0Target
Change-Id: Icbd18d80468e9e5a542f2eace5bfbe45af08ca47
2019-07-15 18:56:37 -07:00
Anthony Stange
f75cf1cf4d Verify mPollThread is joinable before detaching
am: 65945cfb15

Change-Id: Iee183865223aa993241c19924245177b3462d4da
2019-07-15 17:50:18 -07:00
Anthony Stange
65945cfb15 Verify mPollThread is joinable before detaching
If HidlSetUp() bails before startPollingThread() is called (which can
happen if the HAL isn't implemented on the given device), mPollThread
will initialize with the default constructor resulting in joinable()
returning false which means calling detach() throws an exception.

Checking joinable() before detaching allows the test suite to be skipped
successfully.

Fixes: 136736906
Test: Run vts-tradefed on VtsHalSensorsV1_0Target and verify that it is
    skipped successfully on a device that doesn't support HAL 1.0

Change-Id: Ie685ae2dc314edb8df2f3cc7112141a2f5e46008
2019-07-15 19:17:25 +00:00
Youming Ye
f829d25956 Add REQUEST_NOT_SUPPORTED to startNetworkScan
Test: VTS
Bug: 137298570
Change-Id: I99df8495c5f654cb1420b7da36d7f5128ce14dbc
2019-07-12 15:15:58 -07:00
Youming Ye
5feccfb513 Merge "Disable startNetworkScan tests with parameters." into qt-dev
am: c69700441e

Change-Id: I92c7c4470d10dc4ef107b289c3df88269d8d2ec7
2019-07-12 05:09:37 -07:00
TreeHugger Robot
c69700441e Merge "Disable startNetworkScan tests with parameters." into qt-dev 2019-07-12 11:41:24 +00:00
Willy Hu
54362fd37e VTS: Change stopNetworkScan from 1_1 to 1_2
am: fb1616eb94

Change-Id: Ie8eb6ff232906a7dbb7f529958d8e586770fbf44
2019-07-11 20:23:39 -07:00
Youming Ye
bc5f18aae1 Disable startNetworkScan tests with parameters.
Network scan tests with parameters are disabled because of vendors
failed to fully implement startNetworkScan in HAL 1.4, and GSM rat scan
with parameters will get REQUEST_NOT_SUPPORTED error from modem.

Test: VTS
Bug: 137298570
Change-Id: I99df8495c5f654cb1420b7da36d7f5128ce14dbc
2019-07-12 00:07:25 +00:00
Willy Hu
fb1616eb94 VTS: Change stopNetworkScan from 1_1 to 1_2
Change stopNetworkScan from 1_1 to 1_2 when testing VtsHalRadioV1_2Target.

Symptom:

When vts process slot2 "startnetworkscan", it will call "stopnetworkscan()" when startnetworkscan
success. But from current design it will set stopnetworkscan to slot1(wrong slot, expect is slot2)
as bwlow log.

CTS fail log:
hardware/interfaces/radio/1.2/vts/functional/radio_hidl_hal_test.cpp:111

//Device request NwScan on 2nd Sim
06-28 11:30:22.770 radio   873  1213 F RILQ    : RIL[1][Log.cpp: 48] [DispatcherModul(873,1213)]
d: [DispatcherModule]: Handling msg = RIL_REQUEST_START_NETWORK_SCAN

//But Device want to abort on Primary Sim
06-28 11:30:22.776 radio   923  1205 F RILQ    : RIL[0][Log.cpp: 48] [DispatcherModul(923,1205)]
d: [NasModule]: Handling msg = RIL_REQUEST_STOP_NETWORK_SCAN[Context: IRadio(1681692777)]

Bug: 135982495
Test: Build pass. Local test VTS pass.
Change-Id: Ic53c24ab2a670e806b4ac7f192e6eb81252ade84
(cherry picked from commit 5cef297cb2)
2019-07-11 18:53:58 +00:00
nxp72763
67306b3aa6 Align NFCEE ID range with NCI 1.0 in VtsNfcv1.2 test
As per spec,NFCEE_ID value dynamically assigned by NFCC
has the following range
- In NCI_2.0,  0x80 <= NFCEE ID <= 0xFE.
- In NCI_1.0,  0x01 <= NFCEE ID <= 0xFE.

Bug: 137053584
Test: VtsHalNfcV1_2TargetTest with NCI1.0 & NCI2.0 supported device.
Change-Id: I09adaca8b36900a92d737b176e09234251aae2bc
2019-07-11 15:30:28 +08:00
Pawin Vongmasa
fe4f9ebb45 Merge "Support IMapper@3.0 in OMX VTS" into qt-dev
am: 56e9dd901e

Change-Id: I5f05c76194a5a29aa31216dd06a85b82a6ca7539
2019-07-09 11:06:26 -07:00
TreeHugger Robot
56e9dd901e Merge "Support IMapper@3.0 in OMX VTS" into qt-dev 2019-07-09 17:25:39 +00:00
Pawin Vongmasa
94a3234219 Support IMapper@3.0 in OMX VTS
Test: vts-tradefed run vts -m VtsHalMediaOmxV1_0Host

Bug: 135422812

Change-Id: I9a37b4f926813b0cd90f96e318760eecafd04e06
2019-07-08 21:31:33 -07:00
zhangweiwei
7e49059a05 Camera: Vts: Fix missing session close
am: d21dd860ce

Change-Id: I9123734328af0b696926b446a19d9602ba7f9d60
2019-07-08 17:11:10 -07:00
zhangweiwei
d21dd860ce Camera: Vts: Fix missing session close
Test: vendor testing, Camera VTS on Pixel
Bug:135898951
Change-Id: I61f5a90d62732a00d0bc9abad05db0a1a9cc2b63
2019-07-08 08:45:18 -07:00
TreeHugger Robot
1b1c6e42c9 Merge "VTS: Change stopNetworkScan from 1_1 to 1_2" into qt-r1-dev 2019-07-04 11:20:16 +00:00
Willy Hu
5cef297cb2 VTS: Change stopNetworkScan from 1_1 to 1_2
Change stopNetworkScan from 1_1 to 1_2 when testing VtsHalRadioV1_2Target.

Symptom:

When vts process slot2 "startnetworkscan", it will call "stopnetworkscan()" when startnetworkscan
success. But from current design it will set stopnetworkscan to slot1(wrong slot, expect is slot2)
as bwlow log.

CTS fail log:
hardware/interfaces/radio/1.2/vts/functional/radio_hidl_hal_test.cpp:111

//Device request NwScan on 2nd Sim
06-28 11:30:22.770 radio   873  1213 F RILQ    : RIL[1][Log.cpp: 48] [DispatcherModul(873,1213)]
d: [DispatcherModule]: Handling msg = RIL_REQUEST_START_NETWORK_SCAN

//But Device want to abort on Primary Sim
06-28 11:30:22.776 radio   923  1205 F RILQ    : RIL[0][Log.cpp: 48] [DispatcherModul(923,1205)]
d: [NasModule]: Handling msg = RIL_REQUEST_STOP_NETWORK_SCAN[Context: IRadio(1681692777)]

Bug: 135982495
Test: Build pass. Local test VTS pass.
Change-Id: Ic53c24ab2a670e806b4ac7f192e6eb81252ade84
2019-07-03 10:16:10 +08:00
Shuo Qian
a4b9197e0b [automerger skipped] Merge "Hang up EmergencyDial after Trigger in VTS" into qt-dev
am: 33e8a3668d -s ours
am skip reason: change_id Iecba54b93b96d33b57bc59e00f082ff133d2e57b with SHA1 07a53471c4 is in history

Change-Id: Iad4e837b9ee892ae9d35cc6a57788baab14a618e
2019-07-02 15:17:53 -07:00
Anthony Stange
80a247e090 Merge "Deactivate sensors after flush events are received" into qt-dev
am: 8913d1df2c

Change-Id: Ie32a5d1c5f1308060af6ae8c3b7d4c25ebdc9301
2019-07-02 15:14:45 -07:00
Shuo Qian
33e8a3668d Merge "Hang up EmergencyDial after Trigger in VTS" into qt-dev 2019-07-02 17:11:16 +00:00
TreeHugger Robot
8913d1df2c Merge "Deactivate sensors after flush events are received" into qt-dev 2019-07-02 16:28:53 +00:00
TreeHugger Robot
a8baf71318 Merge "Hang up EmergencyDial after Trigger in VTS" into qt-r1-dev 2019-07-02 00:22:49 +00:00
Emilian Peev
137f202385 Merge "Camera: VTS: Don't access invalid resources" into qt-dev
am: d016fd7949

Change-Id: I18c479d1c511af56ccf6d73a7e9fec744ef519ef
2019-07-01 15:24:33 -07:00
TreeHugger Robot
d016fd7949 Merge "Camera: VTS: Don't access invalid resources" into qt-dev 2019-07-01 21:55:58 +00:00
sqian
b2e7c71f39 Hang up EmergencyDial after Trigger in VTS
The whole test case run emergencyDial.RadioHidlTest_v1_4 first and then
 come after startNetworkScan.RadioHidlTest_v1_4 test case immediately
 (within ~3 secs) the NWscan failure is device in emergency call in
 progress/connected while doing emergencyDial.RadioHidlTest_v1_4 test

Although emergencyDial.RadioHidlTest_v1_4 only care about command/response
 is successful or not and don't care call is established or not, modem do
 care about call condition is in idle/progress/connected state before it
 can do NWscan

When there's dedicated channel established, modem can not perform AP
 request NWscan in parallel as we are single HW modem restriction.

Test: run vts
Bug: 135595082
Change-Id: Iecba54b93b96d33b57bc59e00f082ff133d2e57b
Merged-In: Iecba54b93b96d33b57bc59e00f082ff133d2e57b
2019-07-01 21:48:22 +00:00
Anthony Stange
4d90400985 Deactivate sensors after flush events are received
The VTS flush test case was previously deactivating sensors before
waiting for flush events to be received causing any pending flush events
to be discarded per the HAL contract.

Bug: 136472044
Test: Run test and ensure it passes
Change-Id: I23b94e650c6dbbc33640768bee356a49565ba753
2019-07-01 21:29:01 +00:00
sqian
07a53471c4 Hang up EmergencyDial after Trigger in VTS
The whole test case run emergencyDial.RadioHidlTest_v1_4 first and then
 come after startNetworkScan.RadioHidlTest_v1_4 test case immediately
 (within ~3 secs) the NWscan failure is device in emergency call in
 progress/connected while doing emergencyDial.RadioHidlTest_v1_4 test

Although emergencyDial.RadioHidlTest_v1_4 only care about command/response
 is successful or not and don't care call is established or not, modem do
 care about call condition is in idle/progress/connected state before it
 can do NWscan

When there's dedicated channel established, modem can not perform AP
 request NWscan in parallel as we are single HW modem restriction.

Test: run vts
Bug: 135595082
Change-Id: Iecba54b93b96d33b57bc59e00f082ff133d2e57b
2019-07-01 21:26:32 +00:00
nagendra modadugu
7e0d497ae0 Merge "keymaster: Relax testing under GSI" into qt-dev
am: d10841a83d

Change-Id: If9329d4a3630dd772ebb0b2183207823dc9261c1
2019-06-29 12:03:43 -07:00
TreeHugger Robot
d10841a83d Merge "keymaster: Relax testing under GSI" into qt-dev 2019-06-29 18:27:43 +00:00
nagendra modadugu
f18a8328a1 keymaster: Relax testing under GSI
GSI images do not have AVB verification enabled and therefore lack
several properties the keymaster HAL test depended on.  Selectively
disable those parts of the test that would fail with AVB verification
disabled.  Also disable date format checks under GSI.  When invoked from
GSI the TEE-backed keymaster doesn't use the correct date format.

Bug: 130843899
Test: VtsHalKeymasterV4_0TargetTest
Exempt-From-Owner-Approval: change only affects VTS-on-GSI behavior
Change-Id: Idaafb7b515c41290c766a8132f35d498ca15f48a
2019-06-29 18:27:38 +00:00
Yifan Hong
7d70d6ecb9 Merge "Q matrix: use radio.config@1.2::IRadioConfig" into qt-dev
am: 30ecfabab5

Change-Id: If76dca517960cbc4c878b6e0cf707ddf09e0ec6b
2019-06-28 22:21:04 -07:00
TreeHugger Robot
30ecfabab5 Merge "Q matrix: use radio.config@1.2::IRadioConfig" into qt-dev 2019-06-29 05:06:32 +00:00
Yifan Hong
7d350fed1e Q matrix: use radio.config@1.2::IRadioConfig
1.1 IRadioConfig does not exist. radio.config@1.2 is a
minor version uprev that only updates the sub interfaces,
not the top level interface.

Test: builds
Test: on device with target-level 4, w/o this change,
      with radio config 1.1, see test failure on deprecated
      radio config HAL
Test: on this device, with this change, with radio config 1.1,
      deprecated radio config HAL failure goes away.

Bug: 135172251
Change-Id: Id51870a8a757af0895577a27723cff8ee3ba0fdd
2019-06-28 16:28:54 -07:00
Ilya Matyukhin
6ba6c35ac7 Update VTS tests to support the latest BiometricsFace.hal
am: 00bc962dea

Change-Id: I9bab3f83d79518391e3641aaf4e4def398dc98fe
2019-06-28 12:11:04 -07:00