Vendors picking up Huawei-ecosystem projects this year ask most about how to run HiPlay. Plenty treat it as a HiCar sub-feature and only learn after submission that it is two separate systems — a wasted round. HiPlay is Huawei's own wireless casting protocol that only handles the audio-video chain, not the whole-vehicle deep interconnection that HiCar does. This piece lays out the 2026 changes and the pitfalls.
1.1 Very different positioning
HiCar does deep phone-to-head-unit interconnection — navigation, voice, apps, the lot. HiPlay handles one thing: casting phone audio-video to a playback device. One is a full-scenario solution, the other a single transport protocol. Get the direction wrong and the rework is large.
1.2 Passing HiCar does not mean passing HiPlay
The most common misunderstanding in vehicle projects. Passing HiCar whole-vehicle validation does not mean HiPlay audio-video metrics pass; the audio link and casting performance are tested separately, with separate acceptance nodes.
1.3 Which products need it
Not by what it is called, but by two tests: the firmware integrates the HiPlay SDK, or it is marketed as supporting Huawei wireless casting. Touch either and you certify. (1) Factory-fitted IVI hosts, aftermarket large-screen head units and casting boxes are on this line. (2) Home wireless speakers, projectors and TV boxes can also apply, but under a different category with completely different metrics and effort. ① Pure wired passthrough that only supplies power and carries no data does not need it.
2. The 2026 developments
2.1 Pre-test authority opened to third parties
At the HiPlay ecosystem summit during HDC on 14 June 2026, Huawei formally opened pre-test authority to third-party authorised laboratories. Previously only Huawei internally could run this step; now labs can do early assessment and standard alignment, so de-risking before formal testing is faster.
2.2 Pass judgement retained by Huawei
Do not read this backwards. The authorised lab only executes the formal test and cannot self-judge a pass; all data goes back to Huawei's backend for final review. The report is only a process artifact; the certificate is issued only after Huawei's review passes.
2.3 Leave extra time for final review
(1) Formal testing returns results in five to seven working days, excluding rectification. (2) Huawei backend review usually adds seven to fifteen working days. ① Rectification re-test is extra. HiPlay certification is routinely four to eight weeks; it is a wireless audio-casting protocol with no whole-vehicle deep integration, so do not borrow another vendor's whole-vehicle interconnection cycle.
3. How to choose the three connection modes
3.1 LAN mode
Phone and playback device connect to the same router and transfer over the local network. Fewer test items, lower implementation difficulty.
3.2 Wi-Fi Direct mode
No router in between; the phone connects directly to the terminal. Testing withdraws the external network and singles out the direct channel's stability at varying distances and under movement.
3.3 Smart dual-link
LAN and direct channels are both online; when the network degrades it auto-switches to the better one. (1) This mode has the most test content, adding link-switching latency assessment. (2) Aftermarket casting boxes mostly take this route. ① Declare honestly which modes you support; adding a mode later means a supplementary test — another round of money and effort.
4. The two metrics that trip people up most
4.1 Connection success rate
One round in normal conditions and one in a simulated-interference environment, 110 connection attempts each, overall success rate no lower than 98%, and no fewer than 108 passes. (1) Many vendors self-test clean in a quiet office, then drop constantly in the lab. (2) The problem is usually that self-test did not replicate real electromagnetic-interference conditions, so a return is likely at submission.
4.2 A/V sync in three tiers
(1) Tier B is minus 185 to plus 90 milliseconds — the overall audio-relative-to-video-source sync deviation. The lower bound minus 185 means audio lag beyond 185 ms, which users perceive as out of sync; the upper bound plus 90 means audio leading beyond 90 ms is equally unacceptable. Aftermarket head units and ordinary peripherals pass at this line. (2) Tier A is minus 125 to plus 45, Tier S is minus 80 to plus 25, for high-end factory-fitted and flagship display devices respectively. ① Single-link products get a looser latency standard; pick the tier by positioning, no need to force the top. Command-response latency like play/pause has an upper bound of 600 ms; beyond that users clearly notice.
5. Where people lose out
5.1 Do not submit an engineering sample
Usually 2 mass-production units, plus 1 unit with a serial debug port to capture protocol messages. Engineering samples are not accepted; discovering this right before submission wastes the slot.
5.2 Hardware changes mean re-submission
Swapping the Wi-Fi antenna, swapping the audio-decoder chip, or upgrading the HiPlay SDK version — all three changes require a redo. Only UI tweaks or minor decoder-parameter adjustments need no re-test.
5.3 Do not advertise before the certificate arrives
A common blow-up: testing is still running and the e-commerce page already says "supports lossless casting." One Huawei trademark-compliance complaint and the product is pulled across all channels. Plenty have eaten this loss.
BlueAsia helps clients separate HiPlay from HiCar early, pick the right connection mode, and plan the Huawei-backend review window so the cycle is not underestimated.
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
