分类： Android

GTS 6.0 R4 released 2019-04-11起切换

GTS 6.0 R4 released

 

Google Mobile Services Test Suite (GTS) version 6.0 R4 has been released on the GTS Download page. GTS 6.0_r4 will support Android 7.0 to 9 and will be enforced for GMS approvals starting April 11, 2019.

GTS 6.0_r4 replaces GTS 6.0_r3 for approvals of GMS distribution per MADA/ EMADA on phone & tablet devices running Android 7.0 to 9. Major changes compared to previous release are following:

继续阅读“GTS 6.0 R4 released 2019-04-11起切换”

CTS问题分析13-CTS问题分析10（续） | weiinter105

问题分析

这个问题不是第一次出现，详见CTS问题分析10；但当时有更紧急的问题，所以并没有继续深入分析，只是分析到持有大量的CompatibilityTestSuite导致retry时发生错误；

但是这次又出现了，因此有必要进行下调研，以确保下次不再复现此问题

retry 命令： run retry --retry 0 --shard-count 2 -s 7c6252f -s 7c62472

继续阅读“CTS问题分析13-CTS问题分析10（续） | weiinter105”

CTS/GTS/GSI/VTS无法提交报告问题复盘 | weiinter105

一.问题原因

这个问题是由于多个方面造成的，梳理下问题发生的流程

本次问题产生原因

1.首先这个是odm产生的问题，修改了修改model name不规范，只修改了system的属性，没有修改vendor下面的属性

2.odm的推送直接push到了dev上，但是有一条change又进了stable1x，dev上的默认被拉到了stable2x，但是gerrit上只有1x这个提交

3.士伟搜了gerrit上odm的修改，认为只进了1x，所以修复也只进了1x，注意对这个问题进行总结 (要不不进，要进进全)

4.打小数版时CTS测试没有按照上传报告失败问题总结进行检查，导致2x小数版没有发现该问题

5.整数包上传报告时暴露问题

继续阅读“CTS/GTS/GSI/VTS无法提交报告问题复盘 | weiinter105”

CTS9.0R6 造成3筆 location test cases: GNSS Measurement Before Location Test 、Measurement Values Test , testGnssStatusValues测试不通过

问题描述

 CTS9.0R6 造成3筆 location test cases: GNSS Measurement Before Location Test 、Measurement Values Test , testGnssStatusValues测试不通过

解决方案

继续阅读“CTS9.0R6 造成3筆 location test cases: GNSS Measurement Before Location Test 、Measurement Values Test , testGnssStatusValues测试不通过”

[CTS 9.0R5]com.android.cts.devicepolicy.MixedManagedProfileOwnerTest#testKeyManagement fail

问题描述

 com.android.cts.devicepolicy.MixedManagedProfileOwnerTest#testKeyManagement
fail
java.lang.AssertionError: On-device tests failed:

解决方案

继续阅读“[CTS 9.0R5]com.android.cts.devicepolicy.MixedManagedProfileOwnerTest#testKeyManagement fail”

swap 压缩原理及其配置

 当前手机中使用的swap 与 传统Linux中将磁盘的部分区域划分swap 有着很大的区别。当前swap分区方法是从内存中划分一块区域，首先将数据进行压缩，再放置到里面。这样可以让更多的数据放入到内存，又能避免从外存调整数据的延迟。
这种方式的原理是认为CPU 压缩，解压数据的性能成本要小于直接从磁盘中获得。
下面详细介绍其中原理，及其配置参数说明

继续阅读“swap 压缩原理及其配置”

开关机、重启时间优化

开机性能优化：是用功能和其它因素多方面平衡的结果，片面追求单方面的性能没有太大意义；
有些产品设计开机动画非常酷炫，动画图片过多、高帧率会影响开机速度，这时就需要看是开机速度优先还是体验优先；
1.zygote，预加载class、resources；加载的多了，会影响开机时间；
/sdcard/mtklog/bootprof
12450.516490 : 860-system_server : Android:PMS_READY
13136.536031 : 506-main : Zygote:Preload 4715 classes in 495ms
13263.841416 : 506-main : Zygote:Preload 64 obtain resources in 42ms
13271.525031 : 506-main : Zygote:Preload 41 resources in 6ms
13639.574263 : 860-system_server : AMS:systemReady
13645.305493 : 860-system_server : AMS:AMS_READY

/frameworks/base/config/preloaded-classes，因为少加载类会影响APP启动速度，开机过程会涉及到APP启动，此地没有优化空间；
继续阅读“开关机、重启时间优化”

谷歌Android 8.1 Go认证关闭窗口延期至2019-10-31

谷歌Android 8.1 Go认证关闭窗口延期至2019-10-31

We have previously reminded and posted (Launch Approval Windows) the deadline for requesting GMS distribution approvals of new device models launching with Android 8.1 running the “Android Go” or Android (go edition) configuration.

继续阅读“谷歌Android 8.1 Go认证关闭窗口延期至2019-10-31”

[CTS 9.0R5]android.hardware.camera2.cts.StillCaptureTest#testAeCompensation fail

问题描述

 android.hardware.camera2.cts.StillCaptureTest#testAeCompensation fail:
java.lang.Exception: There were 8 errors:
java.lang.Throwable(Test failed for camera 0: Exposure compensation ratio exceeds error tolerence: expected(0.250000) observed(1.000000). Normal exposure time 49996 us, sensitivity 211. Compensated exposure time 49996 us, sensitivity 211, value 4.0 is out of range [0.8, 1.2])
java.lang.Throwable(Test failed for camera 0: Exposure compensation ratio exceeds error tolerence: expected(0.500000) observed(1.000000). Normal exposure time 49996 us, sensitivity 211. Compensated exposure time 49996 us, sensitivity 211, value 2.0 is out of range [0.8, 1.2])
java.lang.Throwable(Test failed for camera 0: Exposure compensation ratio exceeds error tolerence: expected(2.000000) observed(1.000000). Normal exposure time 49996 us, sensitivity 211. Compensated exposure time 49996 us, sensitivity 211, value 0.5 is out of range [0.8, 1.2])
java.lang.Throwable(Test failed for camera 0: Exposure compensation ratio exceeds error tolerence: expected(4.000000) observed(1.000000). Normal exposure time 49996 us, sensitivity 211. Compensated exposure time 49996 us, sensitivity 211, value 0.25 is out of range [0.8, 1.2])
java.lang.Throwable(Test failed for camera 1: Exposure compensation ratio exceeds error tolerence: expected(0.250000) observed(1.000000). Normal exposure time 20000 us, sensitivity 113. Compensated exposure time 20000 us, sensitivity 113, value 4.0 is out of range [0.8, 1.2])
java.lang.Throwable(Test failed for camera 1: Exposure compensation ratio exceeds error tolerence: expected(0.500000) observed(1.000000). Normal exposure time 20000 us, sensitivity 113. Compensated exposure time 20000 us, sensitivity 113, value 2.0 is out of range [0.8, 1.2])
java.lang.Throwable(Test failed for camera 1: Exposure compensation ratio exceeds error tolerence: expected(2.000000) observed(1.000000). Normal exposure time 20000 us, sensitivity 113. Compensated exposure time 20000 us, sensitivity 113, value 0.5 is out of range [0.8, 1.2])
java.lang.Throwable(Test failed for camera 1: Exposure compensation ratio exceeds error tolerence: expected(4.000000) observed(1.000000). Normal exposure time 20000 us, sensitivity 113. Compensated exposure time 20000 us, sensitivity 113, value 0.25 is out of range [0.8, 1.2])

继续阅读“[CTS 9.0R5]android.hardware.camera2.cts.StillCaptureTest#testAeCompensation fail”

[CTS 9.0R5]com.android.cts.devicepolicy.MixedManagedProfileOwnerTest#testKeyManagement fail

问题描述

 com.android.cts.devicepolicy.MixedManagedProfileOwnerTest#testKeyManagement
fail
java.lang.AssertionError: On-device tests failed:

继续阅读“[CTS 9.0R5]com.android.cts.devicepolicy.MixedManagedProfileOwnerTest#testKeyManagement fail”

[GSI8.1R6]dEQP-EGL.functional.get_frame_timestamps#rgba8888_depth_stencil fail

问题描述

 CtsDeqpTestCases
dEQP-EGL.functional.get_frame_timestamps#rgba8888_depth_stencil fail
=== with config {glformat=rgba8888d24s8ms0,rotation=unspecified,surfacetype=window,required=true} === Fail: Composite to present latency is more than 3 vsyncs.!(131178320 < 66089160)

继续阅读“[GSI8.1R6]dEQP-EGL.functional.get_frame_timestamps#rgba8888_depth_stencil fail”

[STS 201901]android.security.cts.StagefrightTest#testStagefright_bug_110435401

问题描述

 CtsSecurityTestCases
android.security.cts.StagefrightTest#testStagefright_bug_110435401
fail
junit.framework.AssertionFailedError: operation not completed within timeout of 60000ms

继续阅读“[STS 201901]android.security.cts.StagefrightTest#testStagefright_bug_110435401”

CTS February releases are available

CTS February releases are available

The CTS February releases for Android 9.0, 8.1, 8.0, 7.1, and 7.0 are available on the Compatibility Test Suite Downloads page. These releases contain continuous improvements of tests and test infrastructure, and verify security patches up to January 2019 Public Security Bulletin.

For partners in China, the CTS packages can be downloaded from https://source.android.google.cn/ without using VPN for better reliability.

The details and delta from last release can be found in the following change lists:

继续阅读“CTS February releases are available”

GMS版本上Google Dialer拨打电话无法显示通话界面

问题描述

GMS版本上Google Dialer拨出电话后，无法正常显示出通话界面
定位问题方式：
1）依次点击进入下面页面： 设置 -> 应用和通知 -> 默认应用
2）检查"电话应用"是否提示为无
3) 点击进入"电话应用"，再次点击选择“电话”后返回上一级
4) 再次检查"电话应用"是否提示为"电话"
5) 回到Google Dialer中尝试拨打电话，通话界面可以正常显示
如果上述步骤2)中"电话应用"显示为无，步骤5)后又能正常显示“电话”， 代表是GMS适配有问题。

继续阅读“GMS版本上Google Dialer拨打电话无法显示通话界面”

【CTS_Verify】Camera ITS测试注意事项

CameraITS测试

       ITS测试分为两个部分，PartI和PartII

【PartI】

a、测试Scene0-Scene5详细的资料在官网和测试包里的说明文档已经是一份完整的SOP；

b、各场景需要的样张，可以在CameraITS下各Scene文件下打印

测试SOP：

1、简易测试方法可参考：CmaeraITS\CameraITS.pdf

2、IN-Box测试可参考：https://source.android.com/compatibility/cts/camera-its-box

继续阅读“【CTS_Verify】Camera ITS测试注意事项”

【VTS_P version】VtsTrebleVendorVintfTest 跟hash相关fail

问题描述

 VtsTrebleVendorVintfTest测试时可能会遭遇以下两种情况报hash的错误：
Case1：
01-05 12:25:53 D/ModuleListener: ModuleListener.testStarted(VtsTrebleVendorVintfTest#DeviceManifest/SingleManifestTest.InterfacesAreReleased/0_32bit)
01-05 12:25:53 D/ModuleListener: ModuleListener.testFailed(VtsTrebleVendorVintfTest#DeviceManifest/SingleManifestTest.InterfacesAreReleased/0_32bit, test/vts-testcase/hal/treble/vintf/SingleManifestTest.cpp:57
Failed
vendor.sw.swfingerprint@1.0::ISwfingerprint has an empty hash. This is because it was compiled without being frozen in a corresponding current.txt file.
test/vts-testcase/hal/treble/vintf/SingleManifestTest.cpp:57
Failed
Case2：

vendor.oppo.hardware.biometrics.fingerprint@2.1::IBiometricsFingerprint has an empty hash. This is because it was compiled without being frozen in a corresponding current.txt file.

继续阅读“【VTS_P version】VtsTrebleVendorVintfTest 跟hash相关fail”