GMS Requirements
This document enumerates the requirements for an Android partner device to properly
integrate with Google Mobile Services (GMS). The requirements are grouped by the following
categories:
• Overview
• Distributing GMS Components. Defines which GMS components must be distributed under
what circumstances.
• Boot-up Branding. Defines what a device should display during the boot-up procedure.
• Device Setup Experience. Defines the UX requirements when setting up a device for the first
time out of the box.
• Home Screen Appearance. Defines how GMS components must be initially presented to the
users after out-of-the-box setup is completed.
• Security Requirements. Defines what security features must be included on the device.
• Settings Requirements. Defines the behavior of the Settings app.
• Platform Feature Requirements. Defines what platform features must be made available
under what circumstances.
Fundamental Requirements
Please note the following fundamental requirements for shipping a device with GMS:
• Android devices that ship with GMS MUST comply with the Android Compatibility Definition
Document (CDD) and pass the Testing Suites like CTS, CTS Verifier, GTS.
• Every Android device that ships with GMS MUST have three physically separated buttons for
BACK, HOME, and RECENT functions.
• Every new Android device that ships with GMS MUST comply with the GMS Approval
Window requirement. Google only approves GMS distribution for new products on an API
level while its GMS approval window is open. Once a product is approved and launched, its
maintenance release (MR) builds and security MR (SMR) builds can be approved regardless
of its GMS Approval Window.
• The binary contents of GMS components MUST NOT be altered under any circumstances.
• New device launches MUST preload all Core apps and services in the latest GMS bundle not
later than 60 days after the latest bundle is released by Google. However, if Google has
released a later version of individual core component, partners MAY preload it instead of the
one in the GMS bundle, as long as such a build complies with this document. This
requirement is applicable to MR builds as well, but a waiver can be granted by Google.
• Partners SHOULD NOT include any GMS updates in security MR builds to ensure smaller
incremental update sizes, unless a GMS module has to be updated to comply the security
patch level declared by the build.
剩余27页未读，继续阅读
评论0
最新资源