How long does HiCar certification actually take? I've seen the fastest done in 2.5 months, and I've seen cases grinding on for 10 months without finishing. The gap is this large, and it has little to do with lab efficiency. What determines it is your product type. Aftermarket wireless screens are fastest. OEM head units are slowest. That's the iron rule. Aftermarket products have finalized hardware and controllable software — one clean pass through the lab is usually fine. OEM head units are tied to the vehicle development cycle. Hardware changes mean retests, software iterations mean retests, and any single change can add a month or two.

1. Ask the Right Question Before Talking Timeline

So don't start by asking how long HiCar certification takes. First figure out which product category you fall under. Aftermarket wireless, aftermarket wired, OEM head unit, equivalent testing, and renewal — five paths with cycle times differing by several multiples. Many people set deadlines based on nothing during the project initiation phase, only to discover halfway through that there's not nearly enough time. Product type doesn't just determine testing scope — it determines whether you can use equivalent testing and affects queue times at every step.

  2. Product Type Determines the Cycle

Aftermarket products have the advantage of finalized hardware and independently controllable software — no need to align with the OEM's rhythm. OEM head units are the complete opposite. From hardware finalization to software version lock, everything follows the vehicle's SOP. Any component change along the way can trigger a retest. The more complex the product and the deeper the coupling with the vehicle, the longer the cycle. I've never seen an exception to this rule.

  3. The 8-Step Process — Each Step Can Trip You Up

The complete process has eight steps: developer registration, SDK integration, vehicle model creation, self-testing, test appointment, lab acceptance testing, release, and license agreement signing. Sounds smooth enough, but every single step can get you stuck.

Registration — Don't Step Into Low-Level Traps

The DevicePartner platform requires corporate identity verification, signing an MOU and security compliance agreement. Incomplete materials get bounced immediately. Huawei's review isn't a formality — a missing stamp means rejection. But one thing needs to be clear: there's no mandatory requirement for the business license's registered scope. Any legally operating enterprise can join. No need to run to the commerce bureau for a scope amendment.

SDK and Self-Testing — The Biggest Time Sink

SDK integration doesn't look complicated, but the reality is full of pitfalls. V6.0.0 requires minimum adaptation to Android 14 — it doesn't mandate Android 16. The 12 deprecated API replacements and 23 multi-channel audio APIs apply only to high-end models with full-screen desktop and multi-channel HD audio capabilities. Basic connectivity models don't need to adapt these.

  4. V6.0.0 Protocol's Actual Impact

The V6.0.0 protocol officially became mandatory on December 31, 2025 — not March 31, 2026. We're already in the mandatory enforcement period. There's no transition window. Don't misjudge the timeline.

84 New Test Cases — Depends on Your Model Type

V6.0.0 added 84 test cases covering file transfer, phone desktop, UI, audio, screen casting, and wireless connection modules. The 84 is the maximum for the full high-end package — basic models don't need to cover all of them. The actual modification workload for basic connectivity projects is far smaller than this number suggests. File transfer and audio modules got the most new cases — these two were already the modules prone to issues.

Audio Routing and Other Features Depend on Hardware

Audio routing, in-vehicle OTA, and concurrent audio recording — these three aren't blanket mandatory. In-vehicle OTA and concurrent audio recording are only mandatory for models with the corresponding hardware capabilities. Without that hardware, exemption applies. Audio routing isn't globally mandatory either — basic head units can exempt through feature trimming, no need to force hardware changes. The most common pitfall is assuming all of these must be implemented, burning budget and time for nothing.

Phone Desktop Has No 1080p Hard Threshold

Phone desktop functionality supports 720P and 1080P multi-resolution adaptation. There's no 1080P mandatory red line. Only the HD mirror casting high-end mode has higher resolution requirements. Basic desktop functionality doesn't require 1080P. Don't blindly swap screens or abandon features based on rumors about hardware thresholds.

Test Phone Requirements

Test phones can be Huawei Mate series or P series models released within the past 3 years. The system requirement is HarmonyOS 6.0 or above — not limited to just the current and previous year's models. If you don't have a compatible test phone on hand, sort out the hardware first before talking about certification timeline.

  5. Cycle Times by Product Type

Aftermarket Wireless — 2.5 to 4 Months

First-time certification normally takes 3 to 4 months. The fastest can be done in 2.5 months. The prerequisites: stable hardware, mature software, experienced team, and high lab cooperation. Miss any one of these four conditions and 4 months won't be enough. Don't use the fastest record as your normal planning baseline — you'll set yourself up for failure.

Aftermarket Wired — 2 to 3 Months

Wired solutions skip the wireless connection and screen casting module testing, shortening the cycle. 2 to 3 months is a normal pace.

OEM Head Unit — 6 to 12 Months

This is the longest path. Tied to the vehicle development cycle, with frequent hardware changes and software versions changing weekly. 6 months is smooth; 12 months isn't unusual. Leave enough buffer in your schedule.

Equivalent Testing and Renewal

Equivalent testing applies when only software changes, not hardware. Aftermarket takes 2 to 4 weeks; OEM takes 4 to 6 weeks. One thing to clarify: HiCar's first-time device certification certificate is valid long-term. If hardware doesn't change, no renewal is needed — consistent with HiPlay rules. Only software-only-change equivalent filing and temporary adaptation filing have a 1-year validity period. Don't confuse equivalent filing validity with the formal certificate validity.

  6. Controlling Time During the Lab Phase

First Testing and Remediation

OEM first testing generally takes 4 to 8 weeks; aftermarket takes 3 to 4 weeks. Each round of remediation adds 1 to 2 weeks. If self-testing is done thoroughly, lab testing goes smoothly. Cut corners during self-testing, and the time spent catching up in the lab doubles.

Huawei Final Review — 10 to 15 Working Days

Lab approval isn't the finish line — Huawei still has a final review. With complete documentation, it takes 10 to 15 working days. Issues requiring supplementary documentation extend it to 3 weeks. Keep a close eye on report quality during the lab phase — don't assume submitting the report means everything's done. HiCar has no official expedited channel. What's called "expedited" is just internal lab schedule adjustment — it cannot shorten Huawei's final review time. Don't be misled by that claim.

For more on HiCar certification cycle and duration, contact BlueAsia Testing & Certification — consultant Benson at 13534225140.