GMS Testing and Certification Process/Cycle/Version Types/Testing Content

I. Purpose of GMS Certification

The purpose of GMS (Google Mobile Services) certification is to ensure that devices meet the standards of Google Mobile Services, allowing them to run Google-provided applications and services reliably. This ensures a consistent user experience across devices.

GMS certification helps device manufacturers and developers gain access to the Google ecosystem and ensures that their devices are widely accepted in the market.

II. GMS Certification Process

1. Contract Signing 
   The certification process begins with signing a contract.

2. Submission of Authorization Agreement for Google Approval
   Submit the authorization agreement to Google for approval.

3. Software Property Check and Modification  
   Check and modify software properties as needed.

4. Client ID Integration and Submission of Project Report
   After Google approval, integrate the client ID and submit the project initiation report.

5. Google Key Application
   Apply for a Google key.

6. Full Testing Initiation
   Begin comprehensive testing.

7. Key Validation  
   Import and validate the key.

8. Software Debugging and New Version Testing
   Debug the software, resolve all issues, and test the new version.

9. Internal Testing Pass
   Once internal testing is successful, proceed to the next step.

10. Formal Testing and Google Approval
   Initiate formal testing and complete the Google approval process.

III. Testing Cycle

The period from the start of full testing to the resolution of all issues and passing internal testing typically takes about 1-2 months, depending on the specific issues encountered and the speed of software debugging. Formal testing takes about a week, and Google approval takes 2-3 weeks.

IV. Version Types

1. EMR and ESMR refer to internal emergency versions that need to be released quickly by the customer and are not part of Google's EMR process.

2. Google's EMR Process is generally slow and often not applicable.

3. RSA is a special agreement between Google and the OEM. If not signed, it can be disregarded.

4. Android 14 Phones require additional testing, such as AACT (Android App Compatibility Testing).

V. Testing Content

 CTS (Compatibility Test Suite): Ensures Android platform compatibility, including CDD (Compatibility Definition Document) + Android SDK/NDK/APIs.
  
GTS (GMS Test Suite): Verifies the correct integration of GMS applications, streaming playback, etc.

STS (Security Test Suite): Tests the integration of security patches.

VTS (Vendor Test Suite): Tests HAL, drivers, and the kernel after replacing the GSI (Generic System Image).

CTS-ON-GSI:Tests compatibility after replacing the GSI.

CtsVerifier:Supplemental tests to CTS that require manual judgment.

BTS (Binary Transparency System): Uploads software packages to Google servers to scan for harmful applications, security patches, and application permissions.

MADA Checklist: Manually tests GMS application pre-installation, placement, boot sequence, etc.

VI. Common Agreements

NDA (Non-Disclosure Agreement):An agreement to prevent disclosure of confidential information.

-AFA (Anti-Fragmentation Agreement):An agreement that all Android products must pass GMS certification to prevent fragmentation.

MADA (Mobile Application Distribution Agreement):An agreement governing the distribution of mobile applications.

EDLA (Enterprise Device Licensing Agreement): A supplementary agreement to MADA, specifically for enterprise devices.

Feel free to contact us for inquiries about Google GMS certification. We can also handle certifications for Google EDLA, Google MADA, Google Auto, Google Lens, Google ARCore, Google TADA, Google Android Watch, Google Android TV, GTV, Google Fast Pair certification and Spatial Audio certification testing for earphone,and other related projects.