On July 18, 2018, the European Commission issued a decision regarding the distribution of Google’s mobile applications on Android in the European Economic Area (EEA). As such, we are making some changes to our agreements and updating the GMS technical requirements for Google Mobile Services (GMS) smartphones and tablets supplied into the EEA for sale to end users.
We recently updated the Unbundled GMS folder with the latest Google Play services (GmsCore) version 13.2.92 binaries. With this version, we introduced the additional APK variants as below:
- 13.2.92_API23+: APK Variant for the Android platform API Level 23 (Marshmallow) and higher but less than the API Level 28 (Pie).
- 13.2.92_API28: APK Variant for the Android platform API Level 28 (Pie).
- 13.2.92_Go: APK Variant for the Android devices in Low RAM (Android Go) configuration, API Level 27 (Oreo MR1) and higher.
Please make sure the right APK Variant was used on your device builds if you have downloaded this new version of Google Play services for production purpose.
These releases also contain continuous improvements of tests and test infrastructure and verify security patches up to September 2018 Public Security Bulletin.
These versions will be required for GMS approvals as shown in the table below:
Android P CTS Hightlight, CTS Instant, Waiver Process
CTS and GTS Best Practice
Android P GMS Req.
Camera Image Test Suite (ITS)
How to get Android tech help
sudo chmod a+x copy_media.sh
adb install CtsDeviceAdmin.apk
run cts --plan CTS //CTS全量测试
run cts -c .... -m ..... // 单项测试
run cts --continue-session sessionID //fail项测试
Google apps folder should contain applications in the following order from left to right; top to bottom.
Google Chrome, Gmail, Google+, Google Maps, Google Play Music, Google Play Movies, Google Play Books, Google Play Newsstand, Google Play Games, Google Drive, YouTube, Google Plus Photos, Hangouts
We have released GMS updates for Android 9, 8.1 and 8.0.
In this release, we:
- Updated the GoogleRestore app for Android 9 to fix an issue that caused the device to consume more power unnecessarily.
- Updated the Setup Wizard for Android 9 to support a setup flow specifically for devices having a dedicated hardware Assistant button.
- Updated the Setup Wizard for Android 8.1 to disable the feature that automatically adds a number into the contacts of users in India. Please see the public article by The Verge describing the issue.
- Updated some GMS build makefiles for Android 9. As a result, the stub WebView app will be preloaded as ‘WebViewStub’ instead of ‘WebViewGoogle’ when Chrome is preloaded and acts as the WebView provider.
- Updated GoogleDialer app to version 23, which does not rely on native libraries. The Android.mk file for GoogleDialer has been updated accordingly.
- Updated the privapp-permissions-google.xml file to reflect the privileged permission android.permission.PACKAGE_USAGE_STATS that was added to the Google app in version 184.108.40.206.
Find the updated apps in each release of the Google Product Geo-Availability on Android v2 spreadsheet tabs below:
ro.com.google.clientidbase) 来设置客户端 ID 值。客户端 ID 值将存储在内容提供程序中，以供所有 Google 应用访问。系统属性上的
/system (ROM) 或
/data 分区上预装 GMS 中的 Google 应用（.apk 文件）。由于 Android 编译系统是模块化的，因此您只需放入二进制文件和 makefile 即可在细分版本中包含 GMS 应用。
GMS EXpress Plus & Go Requirement – 10/2018 (GMS Express and Express Plus are not available in Russia)
From 1st of October 2018, Files (earlier Files Go) will become an exclusive requirement for the regular GMS Express Plus program. It is already an exclusive requirement for GMS Express Plus for Go. Please take note and plan accordingly.
Test suites and GMS releases required-use date
This month we have updated releases for the test suites listed below, as well as the GMS package itself.
August releases of the Android Compatibility Test Suite (CTS) for Android 8.1, 8.0, 7.1, 7.0, and 6.0 are now on the source.android.com CTS Downloads page; see the android-partners announcement for more details. August releases also contain continuous improvements of tests and test infrastructure and verify security patches up to July 2018 Public Security Bulletin.
These versions will be required for GMS approvals as described in the table below:
8.1 R8, 8.0 R12, 7.1 R20, 7.0 R24, 6.0 R31
8.1_r5, 8.0_r8 w Sept SPLs
The following files have been uploaded for you:
– ADUPS has recently released a patched version for com.adups.fota (version 5.22), that must be used for all new builds submitted to Google
– Google will continue rejecting and blocking any new build(s) submitted with com.adups.fota version 5.16 or older
– If you are using ADUPS as your FOTA provider, updates will be pushed to devices already active in the ecosystem automatically and no further action is required for those devices
– All new builds submitted to Google from hereon need to use ADUPS com.adups.fota version 5.22 or newer, or need to use an alternative FOTA solution
Build Test Suite (System Image Scanning)
The Build Test Suite (BTS) operates directly on software builds. It scans device images for preloaded malware and other Potentially Harmful Applications (PHAs) that may have been introduced by OEMs’ vendors and suppliers. BTS incorporates the same technology currently used for security scanning and analysis of applications installed via Google Play.
Starting April 1st, 2018, all partners MUST begin uploading their software builds to Google as described in their partnership agreements. Submission of software builds will be in addition to the existing test reports required for Google build approval.
Submitting builds for BTS
Partners must submit whole software builds. Submissions of individual APKs are not supported. Google only scans APKs in the context of the whole build. As BTS develops, we will look beyond just the APKs in the filesystem images.
Enrollment for MADA partners
Partners can upload software builds in one of the following ways:
- Google Drive: Your TAM will share a Google Drive folder that you can copy your builds to.
- SFTP Dropbox: You can ask your TAM to set up a Secure File Transfer Protocol (SFTP) account for you so that you can upload your build software.
- Submission via 3PL: Submit firmware to your 3PL certifier using one of the supported formats.
Caution: Submitting software builds using Google Drive will affect your Google Drive storage quota. Files placed in Google Drive are copied into the BTS pipeline once per day. Once the results show up in APFE, you can delete old images to recover the quota. If you are submitting a lot of images at the same time, you may need to purchase additional Google Drive quota or ask you TAM to set up an SFTP dropbox.
Submit software builds
For each build that you submit to APFE, you should upload a single compressed archive (.zip, .rar, or .tgz) containing the Software Build in a supported format. The archive should be named according to the build fingerprint, substituting forward slashes (“/”) and colons (“:”) with tildes (“~”). This helps reconcile the file with the reports in APFE.
If you have a zip file containing partition images that can be flashed using fastboot for a build with the fingerprint:
the file should be named:
Partners may submit additional software builds, although these submissions should be accompanied by at least a signature CTS report in APFE so that the results are available. Early submissions may help identify issues early on in the build process. We discourage submitting daily or continuous integration builds as those provide limited usefulness.
Build Test Suite analysis
BTS runs automatically on Google’s infrastructure in the background. The process depends on internal services that cannot be made available offline.
When BTS finishes, the results appear on APFE.
If BTS does not detect any issues, then the build approval process will proceed as normal, subject to the results of other test reports uploaded.
Any suspected PHAs or other issue will be treated as test failure and will prevent build approval. Google can only share the package name and class of malware for any PHA. We cannot provide details on the possible impact of the PHA, its behavior, or how that behavior was detected.
If Google finds an issue after the build has been approved, your TAM will contact you. Partners must address new issues promptly and release an updated build that fixes the issue in accordance with their partnership agreements. New builds that still contain the issue will not be approved.
If you believe that an APK was incorrectly flagged, escalate to your TAM and provide as much detail as possible about the intended functionality of the app. Include details about the file’s origin, particularly if it was made in-house or by a supplier. Google will investigate and deal with these apps on a case-by-case basis.
Supported software build formats
BTS requires the following partition images in a .zip (PKZIP) or .tgz (gzipped unix .tar) file:
- system.img – The filesystem image mounted at /system on the device.
- vendor.img – The filesystem image mounted at /vendor on the device.
- oem.img – The filesystem image mounted at /oem on the device.
- userdata.img – The filesystem image mounted at /data on the device. This is especially important if you pre-load or cache applications in the data partition to improve the out-of-box (OOB) boot time.
- boot.img – The Linux Kernel and Ramdisk used to boot Android.
- recover.img – The recovery image that the Linux Kernel and Ramdisk use for the device to boot to during recovery or to handle the command adb reboot recovery.
The images and filenames above are produced by the AOSP build system, and they can be applied to an unlocked OEM device using fastboot if the device’s bootloader support fastboot.
These filesystem images should be in Ext4, SquashFS, or F2FS format. Partners should use the sparse format for the partition image to reduce the space and upload size for filesystems with free space on them.
Other firmware formats
Google supports the following firmware formats used by various OEM, ODM, and SOC flashing tools:
- Mediatek firmware used with Mediatek’s spflashtool
- Spreadtrum PAC file format1
- Qualcomm’s QFIL format
- .NB0 format
Partners whose firmware is available in one of these formats may upload those formats, in a .zip, .tgz, or .rar file, instead of a fastboot archive. If you cannot provide firmware in one of the known formats, reach out to your TAM.
Requesting an SFTP account
Larger OEMs may prefer submitting builds using SFTP because
- SFTP does not require Google Drive quota.
- BTS begins as soon as the upload completes.
- Partners can use a wide range of SFTP client software.
- SFTP is easier to integrate into automated build, QA review, and submission processes.
Contact your TAM to set up an SFTP account for uploading firmware images. You will need to generate an SSH2 RSA identity key pair for authentication and share the public key with your TAM. Once your SFTP account and dropbox have been configured, your TAM will provide you with the connection details for your SFTP account.
Generating an SSH Identity key pair
On Linux, use the following command, replacing “my_key” with a suitable key name:
$ ssh-keygen -t rsa -f my_key
This command will generate a private key,
my_key, and a public key,
my_key.pub. Your TAM will need the public key to set up your SFTP account.
- It is strongly recommended to compress Spreadtrum ‘.pac’ files to reduce the amount of data that needs to be uploaded. ↩
- 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.
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.