In the in-vehicle export industry, eight out of ten clients asking about AA Certification actually have different understandings of it. Some think it enables Android phone connection for head units, some regard it as a certificate or logo issued by Google, and others confuse it with mobile GMS certification. None of these interpretations are completely wrong, yet none tell the full story.

1. Distinguish Three Easily Confused Concepts

1.1 GMS Certification

GMS (Google Mobile Services) applies exclusively to mobile phones and tablets. Devices pre-installing Google Play, Google Maps, YouTube and other Google apps must pass GMS compatibility tests and sign the MADA agreement to obtain mobile service authorization. It has no connection with vehicle head units.Although GMS and AA share partial underlying protocol stacks, they are two independent systems with different certification bodies, test standards and review channels. Google does not accept GMS test reports for AA applications. That said, some third-party labs may internally reference shared hardware test data for RF, USB and Bluetooth, so there is limited data reuse in actual operations.

1.2 AA Certification

AA stands for Android Auto Compatibility Program. Its core purpose is to verify that when users connect Android smartphones to vehicle head units, the projected Android Auto interface runs smoothly and stably. AA certification targets in-vehicle hardware instead of mobile phones.

1.3 AAOS

If a head unit runs the native Android operating system independently, it belongs to AAOS (Android Automotive OS). Its service authorization follows the GAS (Google Automotive Services) system. AA and AAOS are two completely separate partner programs with incompatible qualifications, test cases and authorized laboratories.In the domestic export market, "AA Certification" generally refers to mobile phone projection mode. However, overseas clients may collectively call AA and AAOS "Google In-Vehicle Certification". Do not mix up the two different application channels. Some all-in-one aftermarket head units support both AA projection and native Android system, which require separate applications for the two categories.

Working Mechanism of Android Auto Projection

Users connect Android phones to head units via USB or Wi-Fi. The Android Auto interface on the phone is projected to the vehicle display, while touch and knob operations are sent back to the phone. In this mode, the head unit acts mainly as an external device with display and audio functions.Note the updates for Android Auto 2.0: The new version adds local audio preprocessing and button event prediction on the head unit side, so the head unit is no longer a pure signal forwarder. Nevertheless, core computing power still resides on the mobile phone.

  2. Major Update: Android Auto 2.0 System

Google officially launched the 2.0 certification system in late 2025. According to schedules released by Google authorized labs, January 9, 2026 is the official termination date for the 1.0 system. All unfinished 1.0 projects must be resubmitted under the 2.0 framework after this date.

Key Practical Notes

Test logics differ significantly between 1.0 and 2.0. Products upgraded to the new version must complete all 2.0 tests, and old test results cannot be migrated directly. However, underlying hardware data such as RF characteristics and USB compatibility baselines remain valid, so only test cases and judgment criteria are updated.

  3. Core Changes Brought by AA 2.0

·SSL certificates are issued much earlier in the process, instead of being available only in the final stage as in the 1.0 system. Still, certificate issuance is tied to project review progress and cannot be obtained at project initiation.

·The approval process for compliance exceptions is simplified via the standardized CER (Compliance Exception Request) mechanism. Approved CERs can be referenced by subsequent projects under the same certification system, eliminating repeated document submissions. It does not mean permanent universal exemption for all projects; the exemption scope is limited to the specific technical scenarios applied for.

  4. Cycle of Google AA Certification

The qualification review for Google Partner accounts generally takes several weeks if all documents are complete. Delays over two months are usually caused by incomplete materials. The main time cost comes from R&D adaptation and testing:

·Mature hardware platforms for basic wired solutions: total certification cycle ranges from 3 to 5 months.

·Full-featured wireless solutions with large differences from Google’s standard architecture: the cycle extends to 5 to 7 months. Cycles longer than 7 months are abnormal, mostly caused by multiple rounds of revisions or laboratory scheduling issues.

Self-Testing & Lab Testing Timeline

·Full self-test with PCTS test suites: 1 to 3 days for one complete run; around 1 week including troubleshooting and retests.

·Third-party lab tests: 1 to 2 weeks for basic wired models per round; 2 to 3 weeks for full-featured wireless models.

·Google final review: normally 3 to 5 working days.

  5. Core Test Items for Google AA Certification

Google does not release the full public test list. Based on practical project experience, the key test modules include: USB protocol compatibility, BLE discovery & pairing, 2.4GHz & 5GHz Wi-Fi RF performance, full PCTS compatibility tests, echo cancellation and dual-talk performance for voice interaction.

Critical Clarifications

·Voice assistants run on mobile phones, while the head unit is only responsible for audio collection and transmission. Google’s voice tests focus on hardware acoustic indicators including echo suppression, noise resistance and microphone pickup clarity, rather than voice recognition accuracy. Claims of "95% recognition rate in noisy environments" have no basis in official standards. Acoustic tests adopt ITU-T P.1100 and P.1110 for in-vehicle hands-free evaluation.

·Products without built-in Wi-Fi and Bluetooth modules can declare "Wired Only" configuration during PPID application and be fully exempted from all wireless tests. Products equipped with wireless modules need to complete both wired and wireless tests. This rule applies to both 1.0 and 2.0 systems. There is no new rule requiring wired-only products to run wireless tests starting from 2026.

·Current standard AA projection certification only mandates tests for 2.4GHz and 5GHz Wi-Fi bands. 6GHz (Wi-Fi 6E) is reserved for AAOS and next-generation in-vehicle connectivity solutions, not a compulsory item for standard AA projection.

For Google AA Certification, please contact Benson at Blueasia: +86 13534225140