Android Auto certification is not like CarPlay. Apple runs an MFi closed loop – Google has two separate paths: phone projection and AAOS (native system). The prerequisites for the two paths are vastly different – choosing the wrong one wastes time and budget. Over 90% of aftermarket head‑unit manufacturers use the projection solution – they do not touch the GMS ecosystem.

1. Android Auto Certification – Projection vs. AAOS – Different Entry Barriers

1.1 Phone Projection (Projection)
Aftermarket head units, portable projection dongles, and most in‑vehicle screens – if the head unit does not run Android – use the projection path. The head unit serves only as a display terminal – USB connection + Bluetooth pairing – Android Auto from the phone is projected.

This path does not involve GMS partner applications or MADA agreements. The real certification focus is projection compatibility testing – i.e., CTS‑Auto and PCTS. Do not be scared by AAOS requirements – most manufacturers simply do not need them.

1.2 AAOS Native Solution
The head unit itself runs Google's native Android system – that is the AAOS route. Mostly used by front‑load OEMs – rarely seen in aftermarket. This route requires GMS partner status and MADA agreements – high investment, long timeline – not chosen by ordinary in‑vehicle manufacturers.

Before starting certification, clarify: are you Projection or AAOS? The simple test – does your head unit run Android?

  2. Third‑Party Authorised Lab (3PL) – Formal Testing

- From 2026, 3PL is mandatory
There has been a change – from January 2026, Google has changed the rules – all new vehicle projects must complete Android Auto certification through third‑party authorised labs (3PL). The old route where manufacturers ran tests themselves and submitted reports to Google is no longer available.

- Manufacturers only have PCTS self‑test tools
What manufacturers can access is PCTS (Partner Compatibility Test Suite) – a self‑test tool to check compatibility before formal testing. Formal CTS‑Auto testing must be performed by a 3PL – manufacturers cannot run it themselves. When selecting a 3PL, confirm they have a valid Google authorisation – reports from non‑authorised labs are not accepted by Google.

  3. CTS‑Auto and CTS – Two Different Things

- Do not apply phone CTS to head units
CTS (Compatibility Test Suite) is for Android phones and tablets – verifying compliance with the Android Compatibility Definition Document. Android Auto projection products use CTS‑Auto and PCTS – not phone CTS. Applying phone CTS standards to head‑unit projection is comparing apples to oranges.

- What CTS‑Auto tests
CTS‑Auto focuses on projection protocols, touch response, audio routing, and connection stability – issues specific to in‑vehicle projection scenarios. It does not care about the head‑unit system's own API compatibility – that is phone CTS's job.

PCTS self‑test runs full scope – 3–6 weeks. Test items are numerous – failures must be fixed one by one. If the head‑unit base differs significantly from standard Android, the remediation workload can be heavy.

  4. 3PL Test Submission and Certification Approval

- From PCTS to 3PL
After PCTS self‑test passes, contact a Google‑authorised 3PL to schedule formal CTS‑Auto testing. The 3PL issues the test report – submitted to Google for review. Google checks report completeness and test results conformance. Testing: 2–4 weeks – non‑conformities require remediation and retesting. Google review feedback: roughly 1–2 weeks per round – two to three rounds are common.

- Certification record and launch
Google updates the product certification status in the Partner Portal. Certified products can pre‑install the Android Auto app and use the Android Auto brand marks.

  5. Receiver Application and Ongoing Maintenance

- Receiver is not developed by OEMs
The head‑unit Android Auto Receiver app (package com.google.android.embedded.projection) is developed and owned by Google LLC. The OEM's job is to integrate Google's official application into their own hardware and system – ensuring stable operation – not to develop or modify the app. Since the app is not written by the OEM, there is no restriction on "modifying core logic" – you never had permission to change it.

- Post‑certification compatibility maintenance
The Receiver receives official updates via Google Play. OEMs must ensure that subsequent OTA updates to the head‑unit system do not break compatibility with the new Receiver version. If the head‑unit update touches framework or audio‑related底层 logic, we recommend re‑running PCTS self‑test to confirm compatibility.

  6. Ongoing Compliance and Change Management

- System OTA risks
Head‑unit OTA updates that change framework layers, UI rendering engines, or audio frameworks – may affect Android Auto functionality. Pushing without verification – if users report issues to Google, subsequent handling is burdensome. A prudent approach: run at least one PCTS self‑test before major system updates.

- New device compatibility maintenance
Google releases new Pixel devices and Android versions annually – Android Auto certified products must continuously maintain compatibility with new devices. Some compatibility issues cannot be fixed via OTA – may require hardware changes. This long‑term maintenance cost must be factored into the initial certification planning.

For Android Auto certification steps, contact BlueAsia at 13534225140 (King) or king.guo@cblueasia.com.