DiPlayCommunity Guide &
Compatibility Database
Choose language

Feature-by-feature permissions

FeatureADB requirementScope
Core USB / wireless CarPlayNoNormal app permissions and compatible hardware
Verified windshield HUD guidanceNo runtime starterExact stock firmware/receiver and map metadata
Basic dashboard mapNot a universal ADB requirementExposed projection display and supported firmware
DiLink 5.1 automatic theme/card followingOne-time Usage Access grant on affected firmwareUse the command shown for your installed package
DiLink 5.0 map stream pause / batteryOptional head-unit ADBSupported vendor properties; Check ADB access
0.2.8 wheel speed / parked videoOptional head-unit ADBOff by default; tunnels unverified; video only in P

What to do first

Make a basic CarPlay connection before enabling vehicle integrations. If your firmware requires ADB to install any APK, that is an installation restriction, not a DiPlay runtime requirement.

The app’s guided automatic-map setup displays the command for the installed package. A HUD Test package command is not automatically the correct command for your public-release package.

Limits of the advanced features

The optional head-unit ADB path documents localhost adbd on port 5555 and an explicit key approval from Check ADB access; the TLS wireless-debugging pairing flow is not supported. Enable only the features you need while parked.

Battery features require a reading at identification; if data becomes ready after connection, use Check ADB access / Apply and reconnect. Wheel-speed data does not mean tunnel accuracy is validated. Parked video requires a valid gear reading and closes outside P.

Sources