For 2026 Android Auto certification, the key to cycle length is not product type but "wired or wireless". The current system is AA 2.0 (full switch in January 2026), with the phone side requiring Android 9 or above. The same aftermarket head unit, if it only supports wired, certifies in 10 to 12 months; adding wireless pulls it straight to 1.5 to 2 years. That is an easily missed trap. Wireless adds antenna consistency, Wi-Fi certification and Google's extra experience testing, lengthening the chain.
OEMs wanting wireless need to plan six months ahead; aftermarket makers should prefer wired for shorter cycle and lower risk. Get the direction wrong and everything reworks, with money and time both spent. Many small makers chase "wireless is cooler", then stall on RF remediation for over half a year.
Register a Google developer account whose information must match the company qualification exactly; signing the ADA (Automotive Android Distribution Agreement) is mandatory, taking 2 to 3 weeks, and an information mismatch bounces back at least a month. Do not confuse ADA with MADA — MADA is for handheld device preload kits, and submitting MADA for a head unit gets rejected by Google outright.
Hardware selection is laborious: prefer Google pre-certified Wi-Fi 6 and Bluetooth 5.0-plus modules, and complete BQB and CE-RED RF certification early. Non-pre-certified modules have over a 60 percent RF rework rate, averaging two to three weeks of delay, and may force a component change.
The aftermarket projection head unit only runs the Android Auto compatibility test; version adaptation centres on the phone side. Embedded AAOS involves CTS/VTS and GAS authorisation — a different path — so separate the test items at project launch.
Pure software adaptation reusing mature hardware takes 1 to 2 months; building deep integration from scratch takes 4 to 8 months. The core is "solve the problems yourself before submission" — do not leave the mines for the formal lab, which charges per round; one dragged round burns a sum.
Aftermarket projection runs Google's AA compatibility test, not CTS/VTS, focusing on connection stability, audio quality, touch latency, voice wake and interference resistance. Voice-wake latency, 85-decibel-noise recognition rate and continuous-connection success rate are frequent failures that must be watched in self-test. Build an issue log in self-test, tracking each round's failures by category, and bring pass evidence before the lab accepts the sample — talking alone proves nothing.
At a Google-authorised lab, formal testing runs 4 to 6 weeks per round; the Android Auto compatibility test covers experience, audio, connection stability and extreme temperature. CTS/VTS appears only for embedded AAOS, not aftermarket. Multiple iterative fixes are normal, and the later a problem surfaces the higher the cost — pre-testing pays for itself.
Google's final review and certification take about 1 to 2 weeks; pass and you get the certification ID. Under AA 2.0 the certification ID is perpetual and the annual renewal has been abolished — not a one-year expiry to redo. A major hardware or system change needs re-evaluation per the current partner-channel document; holding the certificate is not the end, adaptation must follow the platform.
For Android Auto pre-testing, the work starts at the development stage, running against Google's AA compatibility test items early rather than exposing failures at formal submission — rework is expensive.
When RF, USB compliance and head-unit certification proceed together, BlueAsia's one-stop testing and certification merges the sample and documents into one schedule, queuing only once.
Wireless projects often fall on RF remediation; a module without pre-certification gets reworked round after round, and a cycle expected at one year dragging to two is not rare. Many teams underestimate this segment and then overrun — do not estimate optimistically.
Google's schedule is not in the lab's hands; peak-season submissions queue long. Do not treat the lab cycle as the whole cycle; leave a buffer and do not cut it close to the delivery date, because a last-minute insertion cannot be scheduled and one missed delivery date throws the whole line off.
Perpetual validity does not mean set-and-forget; a major change without re-evaluation can leave shipped products out of step with current compliance, and channel accountability is troublesome. Writing "re-evaluate on major change" into the milestone is steadier.
Contact: King Email: king.guo@cblueasia.comAddress: Building C, Hongjingda Industrial Park, No. 107 Beihuan Road, Shiyan Street, Bao'an District, Shenzhen, ChinaBlueAsia delivers more than service!
Related News
