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.
-
Notification on the Deadline for Google Widevine L1 DRM Certification Applications for Android 11 and 12
Due to Google Widevine‘s latest security and policy upgrades — aimed at ensuring the security and compliance of the digital rights management (DRM) ecosystem — Google has now officially terminated the acceptance of new Widevine L1 DRM certification applications for Android 11, Android 12, and all lower versions. The minimum currently acceptable version is Android 13.2026-08-07
-
Google GMS Certification Software Development Services: Is GMS certification difficult? From testing to debugging, we offer a ‘one-stop, all-inclusive’ service
Android device manufacturers frequently encounter challenges during the Google GMS certification process, particularly regarding the complexity of bug fixes and delays in the certification cycle. As Android versions are updated, certification requirements become increasingly stringent.By offering a comprehensive, one-stop service covering everything from authorisation and testing to bug fixes and final certification.2026-07-23
-
Comprehensive services for Google GMS Keys/Google Keys and Widevine Keys, including application, flashing, splitting, testing, rewriting, and porting
Many enterprises frequently encounter the following issues during mass production, certification application, system upgrades or hardware modifications:
How to apply for Google Keys?
How to complete Widevine L1 certification?
How to securely flash keys onto devices?
Can keys be migrated after replacing the device mainboard?
How to split and import keys in batches for factory mass production?
How to verify whether keys are flashed successfully
Are GMS certification failures related to keys2026-06-13
-
Google Android Digital Car Key Testing and Certification Service
Google Android's Digital Car Key certification is based on the CCC (Car Connectivity Consortium) Digital Key global standard. As a core member of the CCC, Google recognizes this certification and supports product integration with Google Wallet. Additionally, there are specific requirements for in-vehicle systems when used with Google Android devices.2026-04-01
-
Google Works with Google Home/WWGH Certified Service
The “Works with Google Home” (WWGH) certification is an official device compatibility program launched by Google. It is designed to ensure that third-party smart hardware integrates seamlessly with the Google Home ecosystem and supports management via Google Assistant voice control and the Home app.2026-04-01
