[VTS]VtsTrebleVintfTest#VtsTrebleVintfTest.InterfacesAreReleased_32bit fail

[DESCRIPTION]

VtsTrebleVintfTest#VtsTrebleVintfTest.InterfacesAreReleased_32bit fail

09-18 15:32:22 D/ModuleListener: ModuleListener.testFailed(VtsTrebleVintfTest#VtsTrebleVintfTest.InterfacesAreReleased_32bit, test/vts-testcase/hal/treble/vintf/vts_treble_vintf_test.cpp:256
Failed
android.hardware.biometrics.fingerprint not available.
)
09-18 15:32:22 I/ConsoleReporter: [1/1 armeabi-v7a VtsTrebleVintfTest 331234567890123354] VtsTrebleVintfTest#VtsTrebleVintfTest.InterfacesAreReleased_32bit fail: test/vts-testcase/hal/treble/vintf/vts_treble_vintf_test.cpp:256
Failed
android.hardware.biometrics.fingerprint not available.

[SOLUTION]

继续阅读“[VTS]VtsTrebleVintfTest#VtsTrebleVintfTest.InterfacesAreReleased_32bit fail”

[VTS 8.1-r5]CtsMediaTestCases--android.media.cts.StreamingMediaPlayerTest#testHlsWithHeadersCookies FAIL

[DESCRIPTION]
 android.media.cts.StreamingMediaPlayerTest#testHLS
fail

junit.framework.AssertionFailedError: Media player had error 100 playing video
android.media.cts.StreamingMediaPlayerTest#testHlsWithHeadersCookies
fail

junit.framework.AssertionFailedError: Media player had error 100 playing video

[SOLUTION]

继续阅读“[VTS 8.1-r5]CtsMediaTestCases--android.media.cts.StreamingMediaPlayerTest#testHlsWithHeadersCookies FAIL”

VTS Test suites required-use date

The November releases of the Vendor Test Suite (VTS) for Android 9.0, 8.1, and 8.0 are released on the GMS help center.

These releases contain continuous improvements of tests and test infrastructure and verify security patches up to November 2018.

These versions will be required for the GMS approvals as shown in the table below:

继续阅读“VTS Test suites required-use date”

[VTS 9.0_R3] fail项:VtsHalRadioV1_1Target

[DESCRIPTION]
 armeabi-v7a VtsHalRadioV1_1Target
Test Result Details
VtsHalRadioV1_1Target#RadioHidlTest_v1_1.setCarrierInfoForImsiEncryption(imsrild1)_32bit fail hardware/interfaces/radio/1.1/vts/functional/radio_hidl_hal_test.cpp:51
VtsHalRadioV1_1Target#RadioHidlTest_v1_1.setCarrierInfoForImsiEncryption(imsrild2)_32bit fail hardware/interfaces/radio/1.1/vts/functional/radio_hidl_hal_test.cpp:51
VtsHalRadioV1_1Target#RadioHidlTest_v1_1.setCarrierInfoForImsiEncryption(se1)_32bit fail hardware/interfaces/radio/1.1/vts/functional/radio_hidl_hal_test.cpp:51
VtsHalRadioV1_1Target#RadioHidlTest_v1_1.setCarrierInfoForImsiEncryption(se2)_32bit fail hardware/interfaces/radio/1.1/vts/functional/radio_hidl_hal_test.cpp:51
VtsHalRadioV1_1Target#RadioHidlTest_v1_1.setCarrierInfoForImsiEncryption(slot1)_32bit fail hardware/interfaces/radio/1.1/vts/functional/radio_hidl_hal_test.cpp:51
VtsHalRadioV1_1Target#RadioHidlTest_v1_1.setCarrierInfoForImsiEncryption(slot2)_32bit fail hardware/interfaces/radio/1.1/vts/functional/radio_hidl_hal_test.cpp:51
VtsHalRadioV1_1Target#RadioHidlTest_v1_1.setSimCardPower_1_1(imsrild1)_32bit fail hardware/interfaces/radio/1.1/vts/functional/radio_hidl_hal_test.cpp:51
VtsHalRadioV1_1Target#RadioHidlTest_v1_1.setSimCardPower_1_1(imsrild2)_32bit fail hardware/interfaces/radio/1.1/vts/functional/radio_hidl_hal_test.cpp:51
VtsHalRadioV1_1Target#RadioHidlTest_v1_1.setSimCardPower_1_1(se1)_32bit fail hardware/interfaces/radio/1.1/vts/functional/radio_hidl_hal_test.cpp:51
报错讯息如下:
09-27 10:08:35 D/ModuleListener: ModuleListener.testFailed(VtsHalRadioV1_1Target#RadioHidlTest_v1_1.setSimCardPower_1_1(se1)_32bit, hardware/interfaces/radio/1.1/vts/functional/radio_hidl_hal_test.cpp:51
Expected equality of these values:
  CardState::PRESENT
    Which is: 4-byte object <01-00 00-00>
  cardStatus.cardState
    Which is: 4-byte object <00-00 00-00>)
09-27 10:08:35 I/ConsoleReporter: [8/42 armeabi-v7a VtsHalRadioV1_1Target 0123456789ABCDEF] VtsHalRadioV1_1Target#RadioHidlTest_v1_1.setSimCardPower_1_1(se1)_32bit fail: hardware/interfaces/radio/1.1/vts/functional/radio_hidl_hal_test.cpp:51
Expected equality of these values:
  CardState::PRESENT
    Which is: 4-byte object <01-00 00-00>  期望插卡
  cardStatus.cardState
    Which is: 4-byte object <00-00 00-00>  实际无卡
[SOLUTION]

继续阅读“[VTS 9.0_R3] fail项:VtsHalRadioV1_1Target”

Test suites GMS July release GMS Client ID update

These versions will be required for GMS approvals as described in the table below:

Release Release version Required-use date
CTS 8.1 R7, 8.0 R11, 7.1 R19, 7.0 R23, 6.0 R30 2018-8-21
VTS 8.1_r4 and 8.0_r8 w August SPLs 2018-8-21
GMS 8.1_201807, 8.0_201807 2018-9-18

GMS Client ID update
Updated H3G country list to include ITWe've updated the GMS Client ID mapping (direct link), effective for new devices only. Check with specific carriers to confirm which values to set. Here's a summary of the changes:

  • Removed AT, BE, CH, FR from Vodafone list of countries
  • Added a row for Vodafone AU

VtsHalKeymasterV3_0Target模块Fail

[DESCRIPTION]
VtsHalKeymasterV3_0Target模块里面这2条case Fail

AttestationTest.EcAttestation ”“AttestationTest.RsaAttestation fail

GTS也有2条对应的case 会Fail
com.google.android.gts.security.AttestationRootHostTest#testEcAttestationChain
com.google.android.gts.security.AttestationRootHostTest#testRsaAttestationChain

[SOLUTION]

继续阅读“VtsHalKeymasterV3_0Target模块Fail”

Android GO GMS认证 

一、2018年最新的GMS需提供5份测试报告,其中包括以下测试:

1、正式版本的CTS测试  (正式版本指的是要拿来送认证的的版本)

2、正式版本的CtsVerifier测试

3、正式版本的GTS测试

4、GSI user 版本的VTS测试

5、GSI user版本的CTS测试

具体测试步骤查请看后面几点

继续阅读“Android GO GMS认证 ”

刷入GSI之后无法开机或者是VTS环境下Case无法执行

[DESCRIPTION]
 刷GSI之后经常会遇到开不了机或者是在VTS环境下Case不执行,结果全为0的情况
[SOLUTION]
一、  如何确保GSI版本的正确性,刷入方法的正确性?

继续阅读“刷入GSI之后无法开机或者是VTS环境下Case无法执行”

no permissions (udev requires plugdev group membership)

在 ubuntu 64位機終端上輸入  adb devices

顯示如下的不愉快:

0123456789ABCDEF    no permissions (udev requires plugdev group membership); see [http://developer.android.com/tools/device.html]

這會導致無法測試 CTS 和 GTS。查找 android 官方資料,解決方法如下:

继续阅读“no permissions (udev requires plugdev group membership)”

Android O 8.0 8.1 VTS测试环境配置

要进行 VTS 测试,首先需要搭建测试环境,我们需要以下配置:

+ 64-bit Ubuntu Linux

+ Java 8
openjdk version "1.8.0_151"
OpenJDK Runtime Environment (build 1.8.0_151-8u151-b12-0ubuntu0.17.10.2-b12)
OpenJDK 64-Bit Server VM (build 25.151-b12, mixed mode)

+ Python 2.7
Python 2.7.14

+ ADB 1.0.39
Android Debug Bridge version 1.0.39
Version 0.0.1-4500957

具体的搭建步骤是:

继续阅读“Android O 8.0 8.1 VTS测试环境配置”