3PL MADA Partner

Program welcome kit

Last updated: June, 2016

Welcome to Google’s 3PL MADA program!
Thank you for choosing to include Google Mobile Services (GMS) onto
your mobile devices. We are excited to have you as part of our 3PL
MADA program and would like to provide you some additional
information and resources to get started.
We hope you find this information and if you have any additional
questions, please reach out to your Google Business Development
partner contact.
Review of MADA privileges &
process
Reminder of what MADA does / does not
mean to you as a partner & launch process
What does having GMS mean for your devices?
Reminder: You can choose to load GMS on a device-by-device basis
If you choose to load a device with GMS...
● You can distribute and sell devices with Google Play and
the other GMS apps
● Your customers will have access to >1M third party
apps and games on Google Play
● Your customers will know your device is from a
legitimate source* and that third party apps will run as
expected
● You may request Google approval to use GMS apps in
your marketing in accordance with GMS guidelines
If you choose to not load a device with GMS...
● Your devices can still use Android
● However, all Android devices still need to pass CTS per
the AFA
● Your devices cannot preload any GMS apps, including
Google Play
● Preloading any GMS without a license infringes Google
IP and Play Apps may not work - the device is not
approved by Google
● Google enforces its IP against infringers and
contributory infringers, including manufacturers,
suppliers, distributors, resellers and retailers
 How do I get my devices certified?
We have a set of authorized 3PL partners*. Please
reach out to find one you are comfortable with Steps to take with 3PL certifier:
1. Sign test & approval agreement with 3PL
Company Contact for approvals

Foxconn (Taiwan)
Service lab in: Taiwan
Pegatron (Taiwan)
Service lab in: Taiwan
vickylin@fih-foxconn.com
SarahLFCheng@fih-foxconn.com
jinny_Chang@pegatroncorp.com
Andrew_Hsiao@pegatroncorp.com
2. Submit your devices to the 3PL and fix
(or have fixed by your ODM) all bugs and
failures reported by the 3PL
3. Receive approval from the 3PL

Harman (US) Chris.Schoppa@harman.com

Service lab in: China, India,
US, Europe
4. Ship!
Robert.Kempf@harman.com
Ashishkumar.Gupta@harman.com
Role of 3PL certifier post-shipment:

Windriver (US) Rick.Anderson@windriver.com

Primary contact point for device launch &
Service Lab in: Vietnam execution (marketing, technical support, etc.)

*Allwinner is the authorized 3PL for Reference Design for Android (RDA) Program
General process flow for 3PL approval process
A: Preparation
Timing: Google BD to provide
guidance
1: Sign contract with 3PL:
NDA and Service agreement
2: Provide hardware devices
to 3PL
B: Implementation
Timing: 0 - N weeks, dependent on client
1: 3PL releases GMS package and
CTS tool. OEMs get access to GMS
site by Google and 3PL to provide
technical support
2: Customer integrates GMS and
runs tests
3: Customer needs to follow the
following 3 steps:
● Submit evidence of all 100%
“pass” reports to 3PL.
● Provide marketing
materials to 3PL
● Provide final Software Build
to 3PL
C: Review
Timing: 5-8 days / cycle
1: 3PL will conduct branding
review
2: 3PL will verify all of the
provided CTS test reports and
also perform own testing
● If all tests are verified
as “pass”, 3PL will
submit device to
Google
● If some tests “fail”,
3PL will contact
partner to address
issues
D: Google Approval
Process
1: 3PL submits approval
package to Google. This
includes marketing & brand
approvals.
2: Google does final review
and approval
3: 3PL informs partner of final
approval and partner is free
to launch
 General process flow where 3PL is SOC (for RDA Program)

A: Preparation B: Implementation C: Review D: Google Approval

Timing: 0 - N weeks Timing: 0 - N weeks, dependent on client Timing: 5-8 days / cycle Timing: 5-8 days / cycle

1: Sign contract with 3PL:
NDA and Service agreement
2: Choose ODM SKU
3: Finalize hw/sw
customization with ODM/SOC
4: Agree on Schedule
1: ODM/SOC does device bring
up, sets up GOTA and integrates
GMS
2: SOC creates 100% CTS “pass”
ready builds
3: OEM provides marketing
material to SOC
1: SOC will conduct branding
review
2: SOC will verify all of the
CTS test reports
3: SOC will verify all of the QA
reports (crashes,bugs,
battery, performance etc ..)
1: SOC submits approval
package to Google. This
includes marketing & brand
approvals.
2: Google does final review
and approval
3: SOC informs OEM of final
approval and partner is free
to launch

*Allwinner is the authorized SOC for Reference Design for Android (RDA) Program
Do devices that have similar characteristics all have to be certified by
3PL as unique devices?
Devices must be unique and certified at the ‘Build’ level. You can use the Google APIs or 3PL to determine
when devices will be treated as different devices. Some examples of frequently asked questions are below:
FREQUENTLY ASKED QUESTIONS FOR CERTIFICATION YES NO

● My device(s) have a different chipset

● My device(s) have a different screen size and / or resolution
● My device(s) are of a different form factor
● My camera and DRM settings on my device(s) are different
● The RAM / ROM on my device(s) are different
● The colors of my device(s) are different
● The battery size(s) in my devices are different
● My device(s) have different UI skins / Wallpapers
Services offered by Google

● GOTA is a Google offered FREE service for Android partners that allows
○ delivering android update packages to end user devices using Google Infrastructure
○ It includes key features like
■ Testing
■ Production Rollout
■ Tracking
● Play Auto Install is a new app distribution mechanism, so that apps can be installed:
○ During device activation
○ Into the user partition
○ Dynamically based on device attributes (like software version, carrier, country)
How long can I certify devices with X.X Android OS version?

GMS approval window open

Android OS API version GMS approval window close
(AOSP Release date)

Jelly Bean 4.2 (API Level 17) 13-Nov-2012 24-Apr-2014.

Jelly Bean 4.3 (API Level 18) 24-Jul-2013 31-Jul-2014

KitKat 4.4 (API Level 19) 31-Oct-2013 30-Jun-2015

Lollipop 5.0 (API level 21) 03-Nov-2014 31-Oct-2015

Lollipop MR1 5.1 (API level 22) 09-Mar-2015 30-Jun-2016

Marshmallow 6.0 (API level 23) 05-Oct-2015 31-Jan-2017

Nougat 7.0 (API Level 24) TBD TBD

 What territories can I operate Google Mobile Services in?
Google Mobile Service apps have wide coverage across the world. For precise coverage maps for all GMS,
please visit the matrix here.

China, North Korea,

Sudan, and Syria are
notable exception
where most Google
Mobile Service apps are
not offered
Partner management
Our mutual responsibilities as a partner
Responsibilities of partners to remain in “good standing” - violations of
any of these could result in significant consequences
Three areas to keep in mind:

No “unapproved” Sub-license Communicate new

devices permitted approvals tracked brand launches
All devices that are launched
Any sub-licenses (for ODMs) Companies launching
must be “approved” at the
must be documented and multiple brand(s) must
build level by 3PL and
pre-approved by Google on a notify Google of each new
Google. Android apps may
device-by-device basis brand name that is launched
not function properly on
these unapproved devices
Partner management expectations
Start of Expiration of 1 yr
1-yr 3PL MADA contract
MADA 3 mo new partner 9 mo. MADA
check-in renewal check-in

Partner check-in Agenda: Potential outcomes:

meeting:
● Review forecast vs. ● If no issues, next
At a minimum, to be actuals meeting at next
completed at 3 mo and 9 ● Review unlicensed scheduled checkpoint
mo checkpoints for new devices ● If issues arise, another
3PL MADA partners ● Discuss other Android check-in will be
news and opportunities scheduled for 3 mo
later
Keeping in touch

While your Google BD resource will be a good source for program / broader
Android updates, we also recommend signing up to the following two listservs for
more information:
(1): Apply membership on security patch monthly bulletin To join these groups:
1. Create a google account with your corp email (NO gmail)
2. Ensure you logout from all google/gmail accounts on your
(2): Technical Android partner announcements browser
3. Visit the links provided
(3): Android partner security information 4. Click "sign-in to view this group"
5. After logging in with your google account created in #1, click
(4) General Android Open Source "Apply for membership"
6. Make sure you enter the answer to the question asked in the
project information (no signup needed) popup: "Please provide the e-mail address of the employee at
Google who referred you to this list.” Only work email addresses
(5) Join GMS Announcement Group by sending are accepted. Requests from personal email address will be
ignored.
corp email address to 3PL. Once Joined, GMS 7. Click apply to join the group
Distribution website can be accessed