Android 8.x - RESSRC

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”

[GTS_6.0.R1]GtsPlacementTestCases 下6条CaseFail

问题描述

GtsPlacementTestCases 下6条CaseFail

com.google.android.placement.gts.DefaultIntentTest#testDefaultIntentHandlers
com.google.android.placement.gts.HomescreenLayoutTest#testFolderPlacement
com.google.android.placement.gts.HomescreenLayoutTest#testShortcutPlacement
com.google.android.placement.gts.HomescreenLayoutTest#testWidgetPlacement
com.google.android.placement.gts.InstalledAppsTest#testAppsInstalled
com.google.android.placement.gts.InstalledAppsTest#testSystemAppsInstalled

第一种报错信息：
java.lang.AssertionError: Unable to execute because authorization failed, please ensure the service account key is properly installed..

解决方案

继续阅读“[GTS_6.0.R1]GtsPlacementTestCases 下6条CaseFail”

[cts-on-gsi 8.1_R6/CTS8.1 R10] CtsAutoFillServiceTestCases android.autofillservice.cts.SessionLifecycleTest#testDatasetAuthResponseWhileAutofilledAppIsLifecycled 测试 fail

问题描述

cts-on-gsi 8.1_R6 CtsAutoFillServiceTestCases android.autofillservice.cts.SessionLifecycleTest#testDatasetAuthResponseWhileAutofilledAppIsLifecycled 测试 fail

11-13 15:36:50 D/ModuleListener: ModuleListener.testFailed(android.autofillservice.cts.SessionLifecycleTest#testDatasetAuthResponseWhileAutofilledAppIsLifecycled, android.autofillservice.cts.RetryableException: Timedout out after 2000 ms

解决方案

继续阅读“[cts-on-gsi 8.1_R6/CTS8.1 R10] CtsAutoFillServiceTestCases android.autofillservice.cts.SessionLifecycleTest#testDatasetAuthResponseWhileAutofilledAppIsLifecycled 测试 fail”

[CTS-8.1R10] android.content.pm.cts.shortcutmanager.ShortcutManagerFakingPublisherTest#testSpoofingPublisher

问题描述

[CTS-8.1R10] android.content.pm.cts.shortcutmanager.ShortcutManagerFakingPublisherTest#testSpoofingPublisher

junit.framework.AssertionFailedError: Expected exception type java.lang.SecurityException was not thrown

解决方案

继续阅读“[CTS-8.1R10] android.content.pm.cts.shortcutmanager.ShortcutManagerFakingPublisherTest#testSpoofingPublisher”

谷歌通知：Android 8.x 认证窗口关闭提前至12月23日

[Android GMS Announcements] Brand Approvals Reminder for Android 8.0 and 8.1

Please note that the GMS approval window for device models launching on Android 8.0 and 8.1 (Oreo) officially ends on December 31, 2018.

As Google is officially closed for the holidays from December 24 to 25 and from December 31 to January 1, please submit all Android 8.0 and 8.1 assets for approval by December 23, 2018 to provide yourself ample time for any potential revision.

继续阅读“谷歌通知：Android 8.x 认证窗口关闭提前至12月23日”

8.x 2018.12.31 关闭窗口 O window closure on 31 December 2018 reminder

The 8.0 and 8.1 (non Go) new device certification window closes on 31st Dec 2018. No builds will be approved after that date by Google. Kindly submit your build approval requests well in advance to your 3PL test labs so that they are certified before 31 Dec 2018.

继续阅读“8.x 2018.12.31 关闭窗口 O window closure on 31 December 2018 reminder”

[cts-8.1-r7]CtsOsTestCases--android.os.cts.SecurityFeaturesTest#testPrctlDumpable

问题描述

[cts-8.1-r7]CtsOsTestCases--android.os.cts.SecurityFeaturesTest#testPrctlDumpable

08-08 15:59:40 I/0123456789ABCDEF: android.os.cts.SecurityFeaturesTest#testPrctlDumpable FAIL junit.framework.AssertionFailedError: expected:<0> but was:<2> 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.os.cts.SecurityFeaturesTest.testPrctlDumpable(SecurityFeaturesTest.java:82)

解决方案

继续阅读“[cts-8.1-r7]CtsOsTestCases--android.os.cts.SecurityFeaturesTest#testPrctlDumpable”

Android O版本的文件media_profiles.xml解析

考虑到Android O的media_profiles.xml/media_profiles_stereocam.xml(双摄项目)变化较大，后续可能会有较多疑问，做如下介绍：

1、确认codec格式及目前的支持情况
打开media_profiles.xml，media_profiles.xml最前面可以看到系统支持的文件格式，codec 格式等等，比如
<!ELEMENT EncoderOutputFileFormat EMPTY>
<!ATTLIST EncoderOutputFileFormat name (mp4|3gp) #REQUIRED>就表示支持mp4/3gp这两种文件格式

2、<CamcorderProfiles cameraId="0">

==>

0是后摄

1是前摄

2是双后摄中的副摄像头

3是双前摄中的副摄像头，

如果需要添加cameraId，直接copy整个cameraID目录下的item并按需要修改特定的item即可
<EncoderProfile quality="low" fileFormat="3gp" duration="30">==>

在Android O中，如果要添加新的item，quality的值一定要在/frameworks/av/media/libmedia/MediaProfiles.cpp的const MediaProfiles::NameToTagMap MediaProfiles::sCamcorderQualityNameMap[]中能够找到，而且不能自行在此map表中添加，否则会VTS 测试fail。

继续阅读“Android O版本的文件media_profiles.xml解析”

Android O版本行为变更

Android O 除了提供诸多新特性和功能外，还对系统和 API 行为做出了各种变更。本文重点介绍您应该了解并在开发应用时加以考虑的一些主要变更。

其中大部分变更会影响所有应用，而不论应用针对的是何种版本的 Android。不过，有几项变更仅影响针对 Android O 的应用。为清楚起见，本页面分为两个部分：针对所有 API 级别的应用和针对 Android O 的应用。

继续阅读“Android O版本行为变更”

com.google.android.permission.gts.PreloadAppsTargetSdkVersionTest#testPreloadedAppsTargetSdkVersion fail

[DESCRIPTION]

使用GTS新工具GTS6.0R1测试 module:GtsPermissionTestCases，com.google.android.permission.gts.PreloadAppsTargetSdkVersionTest#testPreloadedAppsTargetSdkVersion fail
java.lang.AssertionError:All preloaded apps must target SDK 26 or higher:
com.mediatek.ppl targets 24,
com.mediatek.ygps targets 23,
com.mediatek.simprocessor targets 25,
com.mediatek.engineermode targets 23,
com.mediatek.omacp targets 25,
com.mediatek.emcamera targets 23,
com.mediatek.duraspeed targets 24,
com.mediatek.lbs.em2.ui targets 23,
com.mediatek.mtklogger targets 23,
com.mediatek.mtklogger.proxy targets 23,

继续阅读“com.google.android.permission.gts.PreloadAppsTargetSdkVersionTest#testPreloadedAppsTargetSdkVersion fail”

[GTS_6.0.R1]GtsPackageManagerHostTestCases中com.google.android.pm.gts.PackageManagerHostTest#testSoundPool FAIL

[DESCRIPTION]
GtsPackageManagerHostTestCases中com.google.android.pm.gts.PackageManagerHostTest#testSoundPool Fail]

Fail:
07-07 11:24:13 I/RemoteAndroidTest: Running am instrument -w -r --user 0 -e timeout_msec 600000 -e class 'com.google.android.gts.packagemanager.InstantAppTestCases#testSoundPool' com.google.android.gts.packagemanager.instant/android.support.test.runner.AndroidJUnitRunner on alps-k80_bsp-0123456789ABCDEF
07-07 11:24:19 I/XtsHostTestBase: Test com.google.android.gts.packagemanager.InstantAppTestCases#testSoundPool: FAILURE
07-07 11:24:19 W/XtsHostTestBase: java.lang.AssertionError: Instant App should be able to access Media / DrmManager.
Please apply patches r.android.com/502604, SHA d2b3a45, and SHA b93f049
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)

继续阅读“[GTS_6.0.R1]GtsPackageManagerHostTestCases中com.google.android.pm.gts.PackageManagerHostTest#testSoundPool FAIL”

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”

谷歌近期政策通知

谷歌最新政策如下：

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，相应的补丁会每月更新一次。

谷歌Key的申请条件以及方式

Google 有2种Key ，申请条件如下:

1. Wedvine level 1 keybox[询问平台商是否支持Level1]

2. Attestation keybox [Android O必需］

3.10万台内可以共用同一个，详细如下：

MUST support key attestation where the attestation signing key is protected by secure hardware and signing is performed in secure hardware.The attestation signing keys MUST be shared across large enough number of devices to prevent the keys frombeing used as device identifiers. One way of meeting this requirement is to share the same attestation key unless at least 100000 units of a given SKU are produced. If more than 100000 units of an SKU are produced, a different key MAY be used for each 100000 units.

申请资料如下：

继续阅读“谷歌Key的申请条件以及方式”

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”