GMS Testing and Certification Process: Cycle, Version Types, and Test Content

I. Purpose of GMS Certification

The purpose of GMS (Google Mobile Services) certification is to ensure that devices meet the standards set by Google, enabling them to run Google's applications and services reliably and providing users with a consistent experience.

GMS certification helps device manufacturers and developers gain access to Google's ecosystem and ensures their devices achieve broad market acceptance.

II. GMS Certification Process

1. Sign the contract.

2. Submit the authorization agreement to Google for approval.

3. Review and modify software attributes.

4. After Google approves, integrate client ID and submit the case report.

5. Apply for a Google key.

6. Begin comprehensive testing.

7. Import the key and validate it.

8. Debug the software, resolve all issues, and test the new version.

9. Pass self-testing.

10. Start formal testing and complete Google approval.

III.GMS Testing Timeline

From starting comprehensive testing to resolving all issues and passing self-testing typically takes 1-2 months, depending on project issues and debugging speed. Formal testing takes about one week, and Google approval takes 2-3 weeks.
 

 IV. GMS Version Types

1. EMR and ESMR: Refers to emergency versions needed internally by customers to be released as quickly as possible; these are not part of Google's EMR process.

2. Google's EMR Process: Generally slow and not usually applicable.

3. RSA: An agreement signed separately between Google and OEMs. If not signed, it is not a concern.

4. Android 14 Devices: Require additional testing for AACT.

 V.GMS Testing Content

CTS: Compatibility Test Suite for Android platform compatibility, including CDD + Android SDK/NDK/APIs.

GTS: Google Mobile Services Test Suite to verify correct integration of GMS applications, including streaming media.

STS: Security Test Suite for testing the integration of security patches.

VTS: Vendor Test Suite for testing HAL, drivers, and kernel after replacing GSI.

CTS-ON-GSI: Compatibility testing after replacing GSI.

CtsVerifier: Supplementary testing for CTS, requiring manual assessment.

BTS: Binary Test Suite for scanning software packages uploaded to Google servers for potential security risks, security patches, and application permissions.

MADA Checklist: Manual testing of GMS application pre-installation and setup, including boot-up wizards.

VI.GMS Common Agreements

NDA: Non-Disclosure Agreement.

AFA: Anti-Fragmentation Agreement, which mandates that all Android products must pass GMS certification.

MADA: Mobile Application Distribution Agreement.

EDLA: Enterprise Device Licensing Agreement, a supplement to the MADA agreement.