The biggest change to Android Auto certification in 2026 is Google pushing the entire test suite to AA 2.0. Test cases have increased by nearly half compared to the old version. Previously, projection mode only tested basic functionality. Now audio routing, multi-display adaptation, and voice wake-up performance under vehicle noise conditions have all become mandatory test items. Google has also tightened performance benchmarks for the head unit side. Sustained frame drops or touch response latency will deduct points in the Qsuite experience scoring, but AA 2.0 documentation doesn't specify a fixed frame rate threshold as an automatic disqualification condition.
The PCTS self-test tool now takes several days to run through 300+ test cases. Formal CTS-Auto must be executed by an authorized third-party lab. The overall cycle is significantly longer than the old version. This article walks through the AA 2.0 test standard framework and core test categories, along with the most common failure points encountered during actual submission.
Google organized AA 2.0 testing into seven modules: AOAP protocol testing, projection display, phone and notifications, audio routing, Qsuite performance experience, Plugbot stability, and VRRT vehicle noise voice testing. The last three are the key new additions in AA 2.0.
AOAP protocol testing is the baseline threshold. AOAP stands for Android Open Accessory Protocol — what people in the industry casually call AOA. The standard abbreviation in official certification documents is AOAP. Incorrect USB enumeration sequence, AOAP handshake timeout, and HID touch coordinate mapping errors are the top three causes of test failure. CTS-Auto checks every protocol state machine step by step. One wrong state transition and you fail. USB compatibility is a major pitfall — not just external USB hub chips, but the head unit motherboard's built-in USB controller (USB PHY) timing mismatched with Google's reference design will also kill the AOAP handshake.
Projection display covers resolution adaptation, rotation direction switching, multi-window split screen, and dynamic resolution adjustment. AA 2.0 requires support for dynamic switching between 720P and 1080P. When the head unit screen resolution doesn't match the phone output resolution, the rendering engine must smoothly scale without hard-cutting to black. Portrait head units are a trouble spot — many apps default to landscape rendering, and portrait adaptation frequently has compatibility issues. For wireless projection, only products that claim wireless Android Auto support must run the full Wi-Fi Direct test suite. Wired-only products can fully exempt this — not every solution needs wireless testing added.
Phone and notifications module: Incoming/outgoing calls, contact sync, call log display, dual-SIM management, and whether navigation voice prompts lower the call volume during an active call. Message notifications check SMS and instant messaging app push notifications, read-aloud, and voice reply functionality. Group chat messages must not flood the entire screen.
II. Android Auto Certification Audio Routing and Voice Testing
The three audio routing paths were established back in the AA 1.0 era — phone audio over Bluetooth HFP, media audio over A2DP or USB Audio, notification sounds over an independent channel. These three paths must not interfere with each other. This priority logic is not new in AA 2.0. One key understanding: in Android Auto projection mode, all audio is decoded on the phone side. The head unit only does audio passthrough. Some projects mistakenly treat the vehicle's built-in player's 5.1-channel surround sound verification as an AA certification test item. These are not the same thing. Surround sound testing belongs to the head unit's own player scope and is not counted within the CTS-Auto scope for Android Auto projection.
Voice interaction testing runs through the VRRT suite's built-in noise library in noisy environments. The judgment logic: under noise, voice recognition is handled by the phone-side Google Assistant. The head unit only handles microphone capture and front-end processing. Beamforming and echo cancellation optimize capture quality — final recognition rate determination is on the phone side. You can't attribute recognition results to the head unit's algorithm.
III. Key Points for Submission
PCTS is the manufacturer self-test tool with 300+ test cases. What gets submitted to the Google backend is a streamlined compliance self-check list — not all 300+ items filled in one by one. Formal CTS-Auto testing must be executed by an authorized third-party lab. The manufacturer only has the PCTS self-test version. These are two different things. The Pixel phone is Google's mandatory test device. Samsung and domestic flagship phones are part of compatibility verification — the industry typically adds them, but they're not officially required.
Freeze firmware versions before submission. AA 2.0 introduced project grouping and CER exemption mechanisms. Changes limited to upper-layer UI, animations, color layout — where the underlying AOAP protocol stack and USB timing are completely untouched — can pass with a change description submission. What genuinely requires retesting is changes to AOAP protocol stack, USB enumeration timing, touch coordinate mapping logic, or audio routing priority. Treating all HMI rendering engine changes as major changes is too blanket an approach — it depends on whether the changes are surface-level or fundamental.
For Android Auto certification standards and CTS test items, contact BlueAsia Technology Testing & Certification consultant at 13534225140 (Benson).
相关新闻
