Does DiPlay Need ADB? Core CarPlay vs Optional BYD Features

Feature-by-feature permissions

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.

For the public package: adb shell appops set com.shihab.diplay SYSTEM_ALERT_WINDOW allow; adb shell appops set com.shihab.diplay GET_USAGE_STATS allow. Test builds use com.shihab.diplay.hudtest. Check the installed package before running either command.

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.

Network ADB battery reads select CAN/CANFD from the vehicle protocol. A saved show/hide setting controls the home-screen map mirror without disabling the cluster map (PR #123/#133).

Changes and checks in 0.2.10

Optional video adds seeking and ten-second skips. Network ADB and a valid P gear reading are required; leaving P or losing the reading closes playback. FairPlay video remains unsupported (PR #129).

Upstream reports 529 Linux tests with no failures or skips; local checks ran 528 tests with one macOS binding skip. Signed release build and lint passed; lint warnings remain. Signing matches 0.2.9. No new on-car validation was performed.

Changes and checks in 0.2.11

Advanced vehicle data under Location keeps the DiLink 5.0 default and adds explicit legacy detection. Its bounded read-only probe needs authorized network ADB; only accepted fields enable their battery, wheel-speed and parked-video controls (PR #158/#173).

Optional automatic startup of the car’s existing hotspot is off by default. It verifies permissions for DiPlay’s own package on supported BYD firmware and preserves the hotspot name/password (PR #164/#173).

Optional parked video still requires valid P gear and closes when leaving P or losing the reading. Wireless vehicle/location data now belongs to the Wi-Fi iAP2 link; this does not prove tunnel navigation uses wheel speed (PR #157).

Location reporting stays off until precise location is granted; changing it reconnects an active session. Vehicle controls now live in Location → Advanced vehicle data; the separate BYD ADB card controls hotspot startup. Saved legacy fields require acceptance before becoming runtime readings.

Changes and checks in 0.2.12

Hotspot startup checks the actual AP interface and bounds retries when AirPlay never connects. Optional automatic hotspot startup remains off by default; its fallback needs supported firmware commands, authorized local ADB and observed readiness, not just a successful command (PR #229/#235).

Apple-device USB attachment matching is corrected. Optional accessibility assistance confirms only DiPlay’s own system USB permission dialog; unrelated apps and dialogs are excluded. Normal USB authorization remains required (PR #170/#224).

On eligible Android 10 hotspot/Wi-Fi Direct sessions, optional authorized local ADB can pause station scans. Same LAN is excluded; automatic joining of saved networks is unavailable while paused. Recovery markers and retries restore scans, including after reopening; this is not a universal stutter fix (PR #225).

Virtual 16:9 maps support compatible launchers without a physical cluster. Experimental DiLink 3/4 routes add scoped cluster handling and retryable stock-state restoration; DiLink 5/5.1 keeps priority. No DiLink 3 windshield HUD or verified DiLink 4 HUD profile is claimed (PR #171/#182/#187/#213).

Retest repaired DiLink 3/4 cluster routes, scan recovery, wheel modes and firmware-specific hotspot startup. General stutter, calls/Siri/microphone, iOS 15 startup and colour/theme reports still need fresh current-device evidence.

Changes and checks in 0.2.13

Wireless prefers usable IPv4 with scoped IPv6 fallback; Auto channel selection has no band or stutter guarantee. Interface mDNS avoids an unused NSD service; handoff fallback requires rendered video. Experimental hotspot join repair needs Android 13+, a user-configured 5 GHz-only hotspot, supported APIs, authorized localhost ADB and explicit confirmation while disconnected (PR #251/#258/#283/#309/#313).

DiLink 4 native cluster casting and picture controls improve; contributor confirmation covers a 2022 Seal/DiLink 4/Android 10. DiLink 3 projection has checked recovery. Turn cards retain their two-minute expiry, map scale adds 125%, and battery/wheel-service recovery is scoped. Independent DiLink 3 call keys/dashboard cards are off by default; stock idle restoration is not a prior-state snapshot (PR #243/#260/#265/#285/#296/#297/#304/#306).

Retest Android 9 P2P, model-specific cluster restoration, hotspot repair and call/audio paths on the target firmware. Buffered music still needs physical pause/seek/navigation/call/Siri checks; contributor setups do not validate the complete signed release.