Many manufacturers confuse two Google automotive solutions: Android Auto (phone projection) and AAOS (native in‑vehicle system) – their cost logic is completely different. Compared to CarPlay’s single MFi system, Android Auto costs split into three parts: ecosystem compatibility testing, supporting RF compliance, and post‑change maintenance – many agents conflate pre‑requisite compliance with Google certification, inflating budgets.
Key boundary: This article describes phone‑projection Android Auto – the head unit acts only as a display/interaction terminal – underlying OS can be Linux/QNX – no need for Android or GMS. Android Automotive OS (AAOS) is a separate native system – certification rules, costs, and requirements are completely independent – we distinguish them at the end.
A widespread myth: you must first obtain GMS authorisation for Android Auto projection. Not true. GMS, CTS, GTS, VTS, and MADA apply to Android phone terminals and AAOS – projection‑only head units do not need to pre‑install Google services, sign MADA, or run the Android compatibility test suite. Do not let agents bundle GMS tests – that is an unnecessary expense.
Google does not charge a separate Android Auto licence fee to projection head‑unit makers. Total cost comes from third‑party authorised lab testing, supporting RF compliance, and later change retesting – fundamentally different from Apple’s hardware‑chip‑based MFi model.
2. Android Auto Official Test Fees
2.1 Google‑authorised lab test fees
Android Auto projection compatibility tests can only be done at Google‑listed authorised labs – more labs worldwide than CarPlay – Asian hubs in China, Korea, Taiwan.
Test coverage: USB connection stability, Wi‑Fi Direct link, touch latency, Google Assistant voice, navigation rendering, audio switching, Bluetooth hands‑free, and repeated plug/unplug stress.
·Basic wired projection: 5–8 working days – RMB 15,000–30,000.
·Wireless Android Auto: adds Wi‑Fi Direct handshake, Bluetooth wake‑up pairing, and seamless switch – additional RMB 3,000–8,000.
If the device supports both wired and wireless, both sets must be fully run.
2.2 Third‑party app interoperability – beware of unbundling
Some agents list a separate “3PL third‑party app test” fee – clarification: Google’s official test suite already includes interoperability with mainstream apps (Google Maps, Waze, music streaming, messaging) – it is built‑in – there is no official standalone “3PL test”. When requesting quotes, reject any attempt to break out this item. Test scope depends on declared features – navigation‑only + audio‑only models have smaller scope than those with messaging support.
2.3 Google backend review
After lab reports are submitted, Google’s backend review takes 2–3 weeks – the review fee is usually bundled in the lab service. If sample firmware mismatches, functional defects, or missing documents cause rejection, resubmission costs RMB 2,000–5,000 – and the schedule extends.
3. Bluetooth, Wi‑Fi, Voice – Distinguish Mandatory Boundaries
3.1 Bluetooth BQB
Wireless Android Auto uses Bluetooth for initial discovery – BQB is not a Google‑mandated prerequisite. BQB is a market‑access requirement for exports (EU, North America, Korea) – independent – plan it separately. Front‑load: RMB 5,000–10,000; aftermarket portables: RMB 3,000–6,000.
3.2 Wi‑Fi Alliance certification and RF compliance
Wireless uses Wi‑Fi Direct – Wi‑Fi Alliance TID is also market‑access – Google does not check it. WFA certification: RMB 2,000–5,000. RF compliance (FCC, CE‑RED, KC, etc.) is independent – if using a certified module, check its scope to avoid duplicate whole‑product testing.
3.3 ITU‑T voice quality testing
Android Auto head units with hands‑free calling typically need P.1100 and P.1110 – P.1120 usually not mandatory. Pure media devices (no call path) may be exempt – confirm with the lab. Full P‑series: RMB 6,000–12,000 – if the same device already completed equivalent ITU‑T testing for CarPlay, that data can be reused if the lab accepts it – no need to pay twice.
4. Incremental Adaptation Costs – Multiple Vehicles, Screens, Controls
4.1 Screen resolution and display changes
The same mainboard adapted to different vehicle models with different resolution, size, and touch parameters – navigation rendering and touch latency must be re‑verified – cannot assume only minimal testing – any change requires a change assessment with the Google‑authorised lab – often significant regression tests. Incremental test per configuration: RMB 3,000–6,000.
4.2 Touch vs. rotary knob
Android Auto supports both touch and rotary control – if your device supports both, both sets of test cases are run – touch‑only runs touch cases. Adding rotary‑control to an existing touch model adds RMB 2,000–4,000 for rotary‑specific tests.
4.3 Distinguish Android Auto projection vs. AAOS
Many budgets go wrong by mixing the two: we are describing phone‑projection Android Auto – AAOS is a standalone system running Android, no phone required, with Google Automotive Services (GAS) certification – its test scale and costs are much higher – the two certification systems are not interchangeable – choose your route at the architecture stage.
5. Ongoing Compliance and Change – Hidden Costs
5.1 Google Play Services version updates
Android Auto functionality evolves with phone‑side Play Services – but there is no fixed half‑year or annual mandatory retest cycle. Only when Google officially releases a major Android Auto test‑spec update and issues a formal notification do you need to assess compatibility. You can run internal self‑tests and retain reports; if you need an official lab retest report, cost is RMB 3,000–8,000. A simple Android version bump with no spec update does not trigger mandatory retesting.
5.2 Hardware change retest rules
After product release, if you replace the main SoC or Bluetooth/Wi‑Fi RF module – that is a major change – high probability of full Android Auto retesting. Only housing/colour and UI‑colour changes (no effect on communication, touch, or audio) can be filed as simple documentation. Even a screen supplier change with the same resolution must be reported – if optical/refresh‑rate changes affect display, the lab may add interaction tests.
5.3 Regional market test differences
Android Auto has different app/feature availability per country – but the baseline certification test suite is uniform – you cannot delete test items based on target sales regions. Functional differences are typically handled by region‑specific firmware trimming – they do not reduce upfront certification workload.
For Android Auto certification costs, contact BlueAsia at 13534225140 (King) or king.guo@cblueasia.com.
Related News
