Google AA Certification is a hardware compliance verification focusing on USB interfaces, Bluetooth protocol stacks, voice links and display latency. The entire process is calculated in months instead of days. Below are the 5 standard steps and corresponding timelines.
Step 1: Apply for Google Automotive Partner Qualification
Submit company information, brand documents, product plans and target market details, and sign NDAs and AA certification agreements. If all materials are complete, qualification review and contract signing take 2 to 4 weeks. Delays over one month are caused by repeated document supplementation.Misunderstanding Correction: Google’s automotive partner program does not set minimum shipment volume requirements. Startups with complete documents and qualified quality control systems can also pass the review.
Step 2: Product Development & Internal Self-Testing
Develop products in accordance with Google specifications after signing agreements:
·Products based on mature hardware platforms: Complete development and self-tests within 1 to 2 months.
·Brand-new hardware platforms from scratch: Usually take 3 to 6 months. Most aftermarket and revised products do not need the full 6-month cycle.
Key development items include AOAP protocol compatibility, Bluetooth pairing, GPS processing and display latency control.Practical Tip: Arrange pre-tests at authorized 3PL labs in the late development stage. Partial pre-test data can be reused in official 2.0 tests to shorten the overall cycle.
Step 3: Document Submission & Project Kick-Off
Submit product specifications, UX interaction documents and system design reports for Google review. Standard document review takes 1 to 2 weeks. Reviews lasting over 3 weeks result from severely non-compliant documents.
Key Changes in AA 2.0
·SSL certificates are issued earlier, cutting the waiting time by about 2 to 4 weeks compared with 1.0.
·Approved CER compliance exceptions can be referenced by subsequent projects with the same hardware architecture. CERs require re-application if main control chips, wireless modules or core USB circuits are replaced.
Note the official timeline for version transition: New projects launched after December 1, 2025 must adopt the 2.0 system. Existing 1.0 projects can be completed before March 31, 2026.
Step 4: Official Testing at 3PL Labs
This is the most likely bottleneck in the whole process. All tests must be conducted at Google-authorized third-party labs. Core test items include PCTS protocol compliance, AOAP protocol, Plugbot hot-swap tests, Bluetooth & Wi-Fi links, in-vehicle acoustic tests and log verification. Test quantity is dynamically adjusted based on product configurations.
·Wired models: 1 to 2 weeks per full test round; customized models with multiple buttons and interfaces take 2 to 3 weeks.
·Wireless models with dual links: 2 to 4 weeks for regular tests; full-band RF and multi-phone compatibility tests take 4 to 6 weeks.
Products with thorough pre-tests have a high one-pass rate. Multiple retests are usually caused by skipped pre-tests or inherent hardware defects.
Step 5: Google Final Review
Labs submit formal test reports after testing. Standard review takes 3 to 5 working days. Reviews with disputed items or supplementary materials take more than one week.
2. Overall Certification Timeline Summary
·Mature wired solutions with smooth progress: 3.5 to 5 months.
·Regular wireless models with 1 to 2 retests: 5 to 7 months.
·Brand-new hardware platforms with multiple revisions and additional functions such as DAB+: 8 to 10 months.
The 2.0 system effectively shortens the overall cycle compared with the old 1.0 system.
3. Rules for Hardware Modification After Certification
·Minor adjustments such as PCB layout optimization and antenna appearance modification: Only simple change filing is required, no retests needed.
·Major changes including main control chip replacement, Bluetooth/Wi-Fi module replacement and core USB circuit modification: Partial regression tests are mandatory. Full re-certification is not required, but these changes will consume extra project time. It is recommended to finalize the hardware solution in the early planning stage.
For Google AA Certification, please contact Benson at Blueasia: +86 13534225140
