android.hardware.cts.CameraTest#testJpegExif

[DESCRIPTION]
CTS测试时,android.hardware.cts.CameraTest 中的testJpegExif 测项fail ,测试报告一般会报出如下类似的错误:

junit.framework.AssertionFailedError: expected:<3.5> but was:<3.3> at android.hardware.cts.CameraTest.testJpegExifByCamera(CameraTest.java:843)

[ANALYSE]

该项cts测试主要是测试拍照时,拍出来的jpeg图片中的focal length的值(最终读取sensor 的相关设定)是否与parameters中的值一致,若不一致则fail。

由于目前平台上面parameters中的focal length只有一个默认的初始赋值,而没有真正从sensor driver去query,所以若要修改sensor设定的focal length的值,也要同步修改parameters中的focal length值,并且前后摄像头的这个值也需要保持一致。

继续阅读“android.hardware.cts.CameraTest#testJpegExif”

android.jvmti.cts.JvmtiHostTest911#testJvmti Fail

[DESCRIPTION]
D/ModuleListener: ModuleListener.testFailed(android.jvmti.cts.JvmtiHostTest911#testJvmti, junit.framework.AssertionFailedError: [android.jvmti.cts.JvmtiRunTestBasedTest#testRunTest java.lang.IllegalStateException: ###################
### Same thread ###
###################
 这项测试失败主要是因为手机里面的zygote进程创建进程时,所属进程中的线程不符合Google的要求。
一般是由客户自己加的功能引起的。
[SOLUTION]

继续阅读“android.jvmti.cts.JvmtiHostTest911#testJvmti Fail”

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

谷歌近期政策通知

谷歌最新政策如下:

1、express+设备MR也可以享受谷歌资金支持;

2、谷歌将在8月份开始释放Android 9.X版本, go的版本也同时放出;

3.Android 8.X的截止日期为2018-12-31,2019年起仅能送测Android 9.X项目;

4.2018年10月1日起,谷歌强制执行STS及BTS,相应的补丁会每月更新一次。

CtsIntentSignatureTestCases android.signature.cts.intent.IntentTest#shouldNotFindUnexpectedIntents FAIL

[DESCRIPTION]
CtsIntentSignatureTestCases android.signature.cts.intent.IntentTest#shouldNotFindUnexpectedIntents

Fail:
java.lang.AssertionError: [Package: com.android.systemui Invalid Intent: [android.intent.action.ACTION_SUBSIDYLOCK_STATE]]

[SOLUTION]

继续阅读“CtsIntentSignatureTestCases android.signature.cts.intent.IntentTest#shouldNotFindUnexpectedIntents FAIL”

Android 8.1 Google issue

Android 8.1 Google issue
特别注意:
1.有link的Google issue ,不需要再来申请分析报告,用link申请waive.
2.已得到Google回复的: You can get a waiver .

3.已提交google等待google 回复的: Waiting for google feedback.
所有Waiting for Google feedback的Google issue, 均需要客户与Google 确认是否可以waive, MTK 亦在努力与Google 沟通中,一旦拿到Google waiver, 会修改成:You can get a waiver
以下Google issue,不是全部Google issue, 其它fail 需要提供Log 来确认
同一个google issue可能在多个CTS版本 一直存在,因此豁免版本不仅限于标注的CTS版本。同一条case在CTS/CTS-ON-GSI测试下,fail root cause相同,则是同一个问题,同一个waive ID;

继续阅读“Android 8.1 Google issue”

CtsNetTestCases android.net.wifi.cts.NsdManagerTest#testNDSManager FAIL

[DESCRIPTION]
CtsNetTestCases android.net.wifi.cts.NsdManagerTest#testNDSManager
04-05 15:12:49 I/ConsoleReporter: [1/1 arm64-v8a CtsNetTestCases HGAE5WKC] android.net.wifi.cts.NsdManagerTest#testNDSManager fail: junit.framework.AssertionFailedError
at junit.framework.Assert.fail(Assert.java:48)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertTrue(Assert.java:27)
at android.net.wifi.cts.NsdManagerTest.testNDSManager(NsdManagerTest.java:361)
at java.lang.reflect.Method.invoke(Native Method)
[SOLUTION]

继续阅读“CtsNetTestCases android.net.wifi.cts.NsdManagerTest#testNDSManager FAIL”

android.hardware.consumerir.cts.ConsumerIrTest#test_timing fail

[DESCRIPTION]
run cts -m CtsHardwareTestCases -t android.hardware.consumerir.cts.ConsumerIrTest#test_timing
fail
06-12 15:34:34 D/ModuleListener: ModuleListener.testStarted(android.hardware.consumerir.cts.ConsumerIrTest#test_timing)
06-12 15:34:34 D/ModuleListener: ModuleListener.testFailed(android.hardware.consumerir.cts.ConsumerIrTest#test_timing, junit.framework.AssertionFailedError: Pattern length pattern:499995000, actual:926538
at junit.framework.Assert.fail(Assert.java:50)
at junit.framework.Assert.assertTrue(Assert.java:20)
at android.hardware.consumerir.cts.ConsumerIrTest.test_timing(ConsumerIrTest.java:94)
at java.lang.reflect.Method.invoke(Native Method)
[SOLUTION]

继续阅读“android.hardware.consumerir.cts.ConsumerIrTest#test_timing fail”

android.media.cts.CamcorderProfileTest#testGetWithId fail

[DESCRIPTION]
run cts -m CtsMediaTestCases - t android.media.cts.CamcorderProfileTest#testGetWithId
fail :
06-11 11:31:08 D/ModuleListener: ModuleListener.testStarted(android.media.cts.CamcorderProfileTest#testGetWithId)
06-11 11:31:09 D/ModuleListener: ModuleListener.testFailed(android.media.cts.CamcorderProfileTest#testGetWithId, junit.framework.AssertionFailedError: expected:<4500000> but was:<24000000>
at junit.framework.Assert.fail(Assert.java:50)
at junit.framework.Assert.failNotEquals(Assert.java:287)
at junit.framework.Assert.assertEquals(Assert.java:67)
at junit.framework.Assert.assertEquals(Assert.java:199)
at junit.framework.Assert.assertEquals(Assert.java:205)
at android.media.cts.CamcorderProfileTest.assertProfileEquals(CamcorderProfileTest.java:115)
at android.media.cts.CamcorderProfileTest.checkSpecificProfiles(CamcorderProfileTest.java:240)
[SOLUTION]

继续阅读“android.media.cts.CamcorderProfileTest#testGetWithId fail”

android.bluetooth.cts.BluetoothLeScanTest#testBasicBleScan fail

[DESCRIPTION]

android.bluetooth.cts.BluetoothLeScanTest

-- testBasicBleScan

--testBatchScan

-- testOpportunisticScan

-- testScanFilter

Fail信息如下:

fail junit.framework.AssertionFailedError: Scan results shouldn't be empty at junit.framework.Assert.fail(Assert.java:50)

[SOLUTION]
首先,请确保合入patch:ALPS03646285

继续阅读“android.bluetooth.cts.BluetoothLeScanTest#testBasicBleScan fail”

关于USB Accessory Test测试事项

[DESCRIPTION]
一、USB Accessory Test测试,不要求测试机端支持OTG;
因此取消usb.host不会影响此项测试;

<meta-data android:name="test_category" android:value="@string/test_category_hardware" />

<meta-data android:name="test_required_features" android:value="android.hardware.usb.accessory" />

<meta-data android:name="test_excluded_features"

二、USB Accessory Test测试方法:
1、Install the Cts Vefifier USB Companion app on a separate helper device;
2、Start the accessory test companion in the Cts Verifier USB compannion;
3、Connect the two devices, if using a otg adapter make sure the adapter directly conected to the helper device.if using an type-c cable make sure that the helper device is set as supply power to the attached device.

[SOLUTION]

继续阅读“关于USB Accessory Test测试事项”

android.media.cts.AudioTrackLatencyTest#testPlaySmallBuffer test fail

[DESCRIPTION]

android.media.cts.AudioTrackLatencyTest#testPlaySmallBuffer test fail
junit.framework.AssertionFailedError: testPlaySmallBuffer: did it play all the data? expected:<1539> but was:<1024>
at junit.framework.Assert.fail(Assert.java:50)
at junit.framework.Assert.failNotEquals(Assert.java:287)
at junit.framework.Assert.assertEquals(Assert.java:67)

[SOLUTION]

继续阅读“android.media.cts.AudioTrackLatencyTest#testPlaySmallBuffer test fail”

[CTS Test]项目不支持OTG,如何去除CtsVerifier测试中USB相关的测试项

[DESCRIPTION]
AudioFrequencyMicrophoneTest
AudioFrequencySpeakerTest
AudioFrequencyUnprocessedTest
这三条需要连接USB microphone麦克风才能测试
USB Audio Peripheral Attributes Test
USB Audio Peripheral Buttons Test
USB Audio Peripheral Play Test
USB Audio Peripheral Record Test
这四条需要连接USB Audio headset耳机才能测试

继续阅读“[CTS Test]项目不支持OTG,如何去除CtsVerifier测试中USB相关的测试项”

android-cts-8.1_r3 execution is not starting

Q:

On starting, facing the below issue[followed all the precondition steps]

03-29 04:49:11 W/DynamicConfigPusher: Cannot download and parse json config from URL https://androidpartner.googleapis.com/v1/dynamicconfig/suites/CTS/modules/CtsMediaStressTestCases/version/8.1_r3?key=AIzaSyAbwX5JRlmsLeygY2WWihpIJPXFLueOQ3U 03-29 04:49:11 I/MediaPreparer: Instrumenting package android.mediastress.cts.preconditions.app: 03-29 04:49:17 I/MediaPreparer: Downloading media files from https://dl.google.com/dl/android/cts/android-cts-media-1.4.zip 03-29 05:01:42 E/ModuleDef: TargetSetupError in preparer: com.android.compatibility.common.tradefed.targetprep.MediaPreparer 03-29 05:01:42 E/ModuleDef: Precondition class com.android.compatibility.common.tradefed.targetprep.MediaPreparer failed 03-29 05:01:44 I/MediaPreparer: Instrumenting package android.mediastress.cts.preconditions.app: 03-29 05:01:50 I/MediaPreparer: Downloading media files from https://dl.google.com/dl/android/cts/android-cts-media-1.4.zip

This is happening continuously. No test case run

继续阅读“android-cts-8.1_r3 execution is not starting”

Android GO GMS认证 

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

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

2、正式版本的CtsVerifier测试

3、正式版本的GTS测试

4、GSI user 版本的VTS测试

5、GSI user版本的CTS测试

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

继续阅读“Android GO GMS认证 ”

[CTS_8.1] android.autofillservice.cts.PreSimpleSaveActivityTest#testTapLink_changeOrientationThenTapBack android.autofillservice.cts.SimpleSaveActivityTest#testTapLink_changeOrientationThenTapBack

如下2条Case 可以申请豁免
android.autofillservice.cts.PreSimpleSaveActivityTest#testTapLink_changeOrientationThenTapBack
android.autofillservice.cts.SimpleSaveActivityTest#testTapLink_changeOrientationThenTapBack
Fail info
java.lang.AssertionError: negative button (NO THANKS): Not true that the subject is a non-null reference
[SOLUTION]

继续阅读“[CTS_8.1] android.autofillservice.cts.PreSimpleSaveActivityTest#testTapLink_changeOrientationThenTapBack android.autofillservice.cts.SimpleSaveActivityTest#testTapLink_changeOrientationThenTapBack”

IPV6 Configuration For Google GMS Test

谷歌官网对于CTS测试网络要求如下:(查看官网要求

WLAN 和 IPv6

CTS 测试需要满足以下要求的 WLAN 网络:支持 IPv6,可以将被测设备 (DUT) 视为隔离客户端,并可以连接到互联网。隔离客户端是一种配置,可使 DUT 无法接收子网络上的广播/多网消息;这种配置可通过 WLAN AP 配置或通过在未连接其他设备的隔离子网络上运行 DUT 来实现。

如果您无法访问原生 IPv6 网络、IPv6 运营商网络或 IPv6 VPN,以致无法通过基于 IPv6 的一些测试,则可以改为使用 WLAN 接入点和 IPv6 隧道。请参阅维基百科 IPv6 隧道代理列表

实际测试中很多小伙伴们没有符合要求的网络,大多数连能连接谷歌的网络也没有,就造成很多网络原因的测试失败项。

怎么配置符合要求的IPV6网络?

继续阅读“IPV6 Configuration For Google GMS Test”