Getting to approval
CTS, VTS & GMS Certification
Certification is where device programmes lose months. We set up the suites early, automate them in CI, and work the failure list down methodically — so approval is a scheduled milestone rather than an open-ended risk.
What this covers
Suite setup and automation
Standing up CTS, CTS Verifier, VTS, GTS, STS and CTS-on-GSI against your build, wiring them into CI on real device farms, and tracking pass rates over time so regressions surface the day they land rather than the week before submission.
Failure triage
Working the failure list down module by module — separating genuine platform defects from harness problems, test environment issues and legitimate waiver candidates, then fixing the platform defects at the layer that actually causes them.
GMS and approval
GMS requirements review against the current CDD, build fingerprint and configuration correctness, preparing submission evidence, handling waiver requests, and supporting the review cycle through to approval.
Keeping it passing
Security patch level maintenance, monthly bulletin merges, regression gates that block a release when a suite goes red, and re-certification support when you take a new Android version.
Next service
OTA Updates & Platform Security
A/B update infrastructure, verified boot and SELinux policy so the fleet stays updatable and locked down.