将GMS-5.1文件夹中的android-cts-verifier-5.1_r6-linux_x86-arm.zip压缩文件解压,找到android-cts-verifier文件夹,ctrl+alt+t打开终端,输入命令adb install CtsVerifier.apk安装ctsverifier.apk到手机上。


包含Camera FOV Calibration、Camera Formats、CameraITS Test、Camera Intent、Camera Orientation、Camera Video,其中Camera FOV Calibration、Camera Formats、Camera Video包含很多项测试,每个像素点的测试,因此要完全测试完毕,并保证查看左右两边的图片或者视频一致才能通过。


Car Dock Test:点ENABLE CAR MODEàCTS verifier—>Home键即可完成测试;












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

二、 测试命令

继续阅读“GMS认证(常见的cts—fail及解决方法)-清妮” Bug: 109824443

  Test: cts-tradefed run cts -m CtsShortcutManagerTestCases -t
Bug: 109824443

继续阅读“ Bug: 109824443”

【fail reason】:
Test failed to run to completion. Reason: 'Instrumentation run failed due to 'Process crashed.''. Check device logcat for details


GTS Business Logic authentication 业务逻辑影响 GtsPlacementTestCases fail

GTS Business Logic authentication

Google enforces GTS Business Logic (BL) authentication. GTS will fail if the testing environment is not configured correctly. To configure the testing environment, you need to obtain a key file from your TAM. If you are a 3PL partner, please contact your 3PL directly.

Google强制执行GTS业务逻辑(BL)身份验证。 如果未正确配置测试环境,GTS将失败。 要配置测试环境,您需要从TAM获取密钥文件。 如果您是第三方物流合作伙伴,请直接联系您的3PL。

BL authentication affects the tests below. More tests will require BL authentication in the future.


Troubleshooting GMS BL authentication

继续阅读“GTS Business Logic authentication 业务逻辑影响 GtsPlacementTestCases fail”

Updated headset information for USB Audio CTS Tests 音频测试

Headset information for USB Audio CTS Tests on has been updated with headsets approved and known to be compatible with associated CTS tests. Due to the short notice of peripheral update, CTS Verifier 8.0 R11 and CTS Verifier 8.1 R7 releases will not be enforced. However, we encourage the use of CTS Verifier 8.0 R11 and 8.1 R7 releases, if partners are already using the newly listed compatible headsets. Partners should update audio peripherals soon according toUSB Audio CTS Tests, as they will be necessary when running CTS Verifier 8.0 R12 and 8.1 R8 releases.

继续阅读“Updated headset information for USB Audio CTS Tests 音频测试”

Test suites and GMS releases required-use date

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.

These versions will be required for GMS approvals as described in the table below:


Release version

Required-use date


8.1 R8, 8.0 R12, 7.1 R20, 7.0 R24, 6.0 R31



8.1_r5, 8.0_r8 w Sept SPLs



8.1_201808, 8.0_201808


CTS August releases are available

CTS August releases are available

The Android Compatibility Test Suite (CTS) August releases for Android 8.1, 8.0, 7.1, 7.0 and 6.0 are available on the CTS Downloads page of These releases contain continuous improvements of tests and test infrastructure and verify security patches up to July 2018 Public Security Bulletin.

Details are available in the following change lists:

继续阅读“CTS August releases are available”



由于目前所有的手机都要求支持Android for work, 客户在测试CTS,GTS过程中,经常在profile_provisioning的过程中出错,这边对经常出错的地方进行分析,并提供对应的解决方案



广升ADUPS FOTA 过认证信息更新

- 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

什么是BTS?Build Test Suite (System Image Scanning)

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.

Note: Partners are still responsible for vetting and reviewing all software that is distributed on their devices. Google continuously updates our databases and detection techniques for malware and security threats, but we may not always be able to detect an issue at the time of your build submission.

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:

  1. Google Drive: Your TAM will share a Google Drive folder that you can copy your builds to.
  2. 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.
  3. Submission via 3PL: Submit firmware to your 3PL certifier using one of the supported formats.

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 formatThe 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: acme/acme_1/acme_3g:7.0/NRD90M/123456789:user/release-keys
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.

Build approval

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

Fastboot package

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.
Note: The vendor.img and oem.img are only required if the build uses separate vendor and oem partitions, otherwise it is expected this content is part of the system image.

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.

Note: Google does not accept firmware in self-extracting executables and does not accept password protected archive files.

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, Your TAM will need the public key to set up your SFTP account.

Partners using a Microsoft Windows system can use the PuTTY client to generate SSH keys following these instructions.


  1. It is strongly recommended to compress Spreadtrum '.pac' files to reduce the amount of data that needs to be uploaded. 

CTS 9.0 R1 released, new Android 9 platform and partner docs available

Android 9

Android 9 is the release of the development milestone code-named P. The source code for the following tests, including tests for instant apps, can be synced with the 'android-cts-9.0_r1' tag in the open-source tree.