Android Auto sits inside Google's automotive ecosystem and interfaces directly with Google's own developer system — there is no third-party issuing body. The work splits into two implementation paths: AAOS native deep integration, and phone projection (mirroring). The two need different document sets, but company qualification and hardware design files are common baseline materials. Get the wrong counterpart and the whole document package gets reworked.
Do not confuse it with CarPlay: Apple CarPlay runs on the MFi licensing scheme, while Android Auto uses a Google enterprise developer account plus vehicle-device protocols — the two systems are fully independent. If MFi content slips into your submission, it signals weak upfront research and reviewers will flag the wrong direction outright.
Company qualification and agreements
Company registration details must match the Google developer account — legal entity information, registered address, and primary contact. A vehicle-hardware maker signs the GMS and Android Auto vehicle-device agreements; this is the legal basis for everything after. Without signed agreements you cannot enter the formal submission flow.
1. Business licence and ISO 9001 qualification files
Keep entity details consistent end to end — company name, registered address, and signatory must line up with the developer account.
2. Complete real-name verification on the enterprise developer account
Without verified real-name status you cannot launch a formal application. Many projects stall on a mismatch between the account entity and the business licence, wasting weeks. These two are the entry-level hard gates.
Product design documents
Hardware docs: BOM list, circuit schematics, and a hardware architecture block diagram marking key components like the USB controller, Bluetooth, and Wi-Fi modules.
Note: quad-core 64-bit, 1.8 GHz, 4 GB RAM, and 64 GB storage are reference hardware conditions for AAOS native integration — the ordinary projection version of Android Auto has no such mandatory hardware floor.
Software and interaction docs: the AAOS native route needs system architecture, HAL drivers, and CAN bus interface materials, plus proof of the corresponding system version. The projection route needs no AAOS materials. For interaction, prepare UI logic and voice-control flows, and enforce driving-mode constraints — for example, blocking video playback above 8 km/h — with UX design matching the Android Auto UX 4.2 specification.
Testing and compliance files
In-house self-testing must cover L-test, Sensor Log, Qsuite, VRRT audio, Plugbot, AOAP, and others. L-test supports in-house self-testing or third-party assistance; a third-party report is not mandatory.
1. Product compliance declaration and IP ownership statement
Prepare the declaration of conformity and a clear statement of intellectual-property ownership for the submitted design.
2. Region-specific privacy duties for overseas sales
For products sold overseas, you must handle duties like GDPR yourself — that is a market-access obligation and is not submitted to Google.
BQB, FCC, and RED are country-specific market-access certificates used for export clearance; they are not submitted to Google. You can coordinate wireless-ecosystem certification with a third party to cut duplicate work.
Sample requirements
Submit mass-production-definition units with production firmware, and reserve a log-export debug interface. Engineering samples are not accepted. Prepare wireless test fixtures as needed. Sample hardware and firmware versions must exactly match the schematics and BOM; any version mismatch means immediate rejection.
Document version alignment is critical: schematics, BOM, and firmware descriptions — every document version must match the sample. A hardware change made but not reflected in docs gets you stuck at review. Assign a dedicated owner to manage document versions and avoid last-minute scrambling.
Timeline and change notes
Front-end account registration and agreement signing take 1–2 months; development and self-test 3–5 months; L-test 1–2 months; remediation and retest 1–3 months; Google final review 2–4 weeks. Total project lead time is 6–10 months, floating with development and remediation progress.
Android Auto has no one-year physical certificate and no annual renewal fee. Once a product clears Google's ecosystem admission, you only re-run testing and evaluation when hardware or software changes substantively; on a major Google version iteration the maker just does compatibility adaptation.
Running Android Auto, HiCar, and CarPlay on one device lets you partially reuse hardware docs, but each ecosystem has independent testing and documentation requirements — plan the overall overseas rollout together.
Practical advice
Run a pre-check at project kickoff to catch common issues early — audio latency, touch response, and EMC interference. Cover L-test cases thoroughly in self-test to cut formal-test failure odds. Do not copy mobile UI directly; functional limits in driving scenarios are hard constraints.
1. Assign a dedicated owner for documents and sample versions
Sync the full documentation set on any hardware or software change, so the sample and the paperwork never drift apart.
2. Track Google automotive version iterations
Adapt in time to avoid later compatibility problems after a major platform release.
Android Auto documentation is not just "collect everything and submit." Version consistency between docs and samples, plus long-term compatibility maintenance, is what actually gets you through.
BlueAsia handles Android Auto along with HiCar, CarPlay, and multi-country automotive certifications in one place, helping you align documents, samples, and long-term compatibility so the ecosystem admission goes through smoothly.
Contact: King Email:king.guo@cblueasia.comAddress: Building C, Hongjingda Industrial Park, No. 107 Beihuan Road, Shiyan Street, Bao'an District, Shenzhen, China
BlueAsia delivers more than service!
Related News
