分类： Android

GMS Funding Eligibility Condition 已过认证设备需提交上市状态

  • Funding Eligibility Condition: From July 1, 2018, Google has monitored activations of devices after certification for future funding eligibility. Based on activations, if Google finds that a funded device has not been commercially launched within 3 months after the certification date, Google will request for justification from the partner. If a satisfactory justification is not provided by partner repeatedly, then the Funding Program may be suspended for that partner for few months by informing all the 3PLs and the partner.

继续阅读“GMS Funding Eligibility Condition 已过认证设备需提交上市状态”

GMS Requirements: Rich Communications Services (RCS)

Google believes that interoperable IP messaging based on the open Rich Communications Services (RCS) specification is a viable direction to improve the Android messaging experience for users beyond SMS/MMS and is becoming a fundamental technology expected on the devices for which we’re licensing GMS.


Therefore, we plan to add the following in the upcoming Q4 GMS Requirements (to be announced with other changes in November), which will be enforced 60 days after the announcement.

继续阅读“GMS Requirements: Rich Communications Services (RCS)”

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.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

被欧盟重罚340亿！谷歌警告：Android可能不再免费！

欧盟宣布将对谷歌罚款43.4亿欧元，约合人民币340亿元，理由是谷歌在原生Android系统强制预载Chorme浏览器和谷歌搜索引擎，涉嫌违反欧盟反垄断法。对此，谷歌CEO警告称，由于欧盟的决定，Android可能无法保持免费，或许将向手机厂商收取授权费。

欧盟对Alphabet Inc. (GOOG)旗下谷歌(Google)开出创纪录的43.4亿欧元（合50.6亿美元）反垄断罚单，并命令谷歌调整其业务，这可能让谷歌失去对手机这个该公司最大增长引擎的控制。

对于少数科技巨头的影响力，欧盟作出了迄今最严厉的指责，欧盟反垄断监管机构周三认定，谷歌滥用其Android操作系统的主导地位推广并强化自己的手机应用和服务，尤其是该公司的搜索引擎；全球超过80%的智能手机都搭载了Android系统。

Android手机预装了谷歌应用和服务，包括谷歌搜索。竞争对手长期以来都抱怨，Android的主导地位让谷歌具备了不公平的优势，吸引用户使用谷歌的应用程序，然后利用应用数据来设计并推出有针对性的广告。欧盟表示，预装的应用阻止了其他竞争性的应用。

谷歌近期政策通知

谷歌最新政策如下：

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”