DiPlay
English

Symptom

The app fails or closes while creating the P2P group, before CarPlay appears.

Possible causes

Legacy Wi-Fi Direct depends on firmware and cannot verify frequency: Android 7.0–9 in 0.2.21+, 7.1–9 in 0.2.15–0.2.20, and Android 9 in 0.2.13–0.2.14. Older Android still needs vehicle testing.

Quick checks

0.2.22 — CarPlay and Home explain failed pairing, hotspot, Wi-Fi Direct or USB starts. Android 8/9 detects Wi-Fi loss again; Bluetooth and stale P2P groups recover sooner. Same LAN can select a network interface, tested on one 2022 Seal EV with USB networking.

  1. Legacy Wi-Fi Direct depends on firmware and cannot verify frequency: Android 7.0–9 in 0.2.21+, 7.1–9 in 0.2.15–0.2.20, and Android 9 in 0.2.13–0.2.14. Older Android still needs vehicle testing.
  2. Grant Wi-Fi/Location or Nearby Wi-Fi permissions as requested and enable Location where required.
  3. Close other projection apps. For stale groups, use Settings → Connection → Wireless connection help → Reset CarPlay Wi-Fi and review the confirmation.
  4. Record requested and actual channel/frequency in diagnostics. Compare the car hotspot instead of changing country/driver properties.

Reported results & workarounds

The current source retains the requested SSID instead of reading config.networkName. In #79 the maintainer attributes a fix to 0.2.8; the reporter tested a custom build and had not retested the public APK.

Version status

Legacy Wi-Fi Direct depends on firmware and cannot verify frequency: Android 7.0–9 in 0.2.21+, 7.1–9 in 0.2.15–0.2.20, and Android 9 in 0.2.13–0.2.14. Older Android still needs vehicle testing.

Wireless startup can choose a free AirPlay port; Wi-Fi Direct handles unknown security reports, busy channels and bounded 5 GHz to 2.4 GHz fallback (PR #121/#143). Wi-Fi Direct packet loss, device-specific microphone input and reconnect problems still need hardware investigation; no universal fix is claimed.

Stuck preparing CarPlay: which connection checks apply?

Enable iPhone Bluetooth, Wi-Fi and Siri; allow CarPlay and select the correct paired phone. Car hotspot needs its actual name/password; Wi-Fi Direct needs working head-unit P2P and permissions; only existing Wi-Fi needs both devices on a reachable LAN. Then try re-pairing, normal restarts or USB. Start the hotspot manually if needed; try an English name if a non-English name stalls.

Stuck preparing CarPlay: which connection checks apply?
Original fault report; the interface and version may differ. #580 View original report

How do I handle periodic music dropouts?

Compare Wi-Fi Direct with the car hotspot, then USB; prefer stable supported 5 GHz. More buffering adds delay and cannot replace lost packets. 0.2.18 fixes a separate AAC dropout case; retest the matching symptom, without assuming it fixes Wi-Fi firmware.

Wireless adds MIUI 13 Bluetooth permissions, an immediate Bluetooth-off prompt and failure-specific recovery tips. Enter the actual second hotspot name ending in _5G when it exists. Wheel-key service recovery waits before re-enabling; hotspot-start reports give the cause.

Version notes for this guide

0.2.13 — 0.2.13 adds firmware-dependent Android 9 Wi-Fi Direct using actual group credentials. Requested channels remain unverified on Android 9; Android 10+ verifies frequency. Cleanup retains persistent profiles (PR #282).

Full updates, older version details and their validation limits are now collected in the version history. Follow the links below for the complete notes.

Reported setups

The following are source reports, not a universal affected-car list. Unknown fields remain unknown.

BYD Song Pro · DiLink 3.0 · Android 10

iPhone 14 Pro Max / iOS 27.0 · DiPlay 0.2.0
Reported incompatible

Bluetooth pairs but CarPlay startup crashes with getNetworkName error. AI-generated cause in the report is not accepted as proof. Do not generalize this to all DiLink 3.

View original report
Last verified: 2026-10-01

Related GitHub issues

Closed does not necessarily mean fixed. The source is authoritative for later updates.

Your next step

Sources

View source details (5)