“Cannot find iPhone; unlock the phone and check Bluetooth”: what should I check?
Unlock the intended iPhone and enable Bluetooth and Wi-Fi. Check that this phone is paired in the head unit’s Bluetooth settings and selected in DiPlay; accept any CarPlay prompt. Confirm Siri is enabled and CarPlay is not restricted. Then check the chosen transport: a real car hotspot with matching saved credentials, Wi-Fi Direct with P2P support and permissions, or an existing Wi-Fi network shared by both devices. This message alone does not identify the cause. If it persists, compare USB where available and save a diagnostic report before resetting pairing or app data.
Symptom
CarPlay never appears, or DiPlay returns to the home screen during setup.
Possible causes
Missing permissions, incorrect saved hotspot details, unsupported P2P APIs, and competing projection apps are different failure paths. Match the log to the stage.
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.
- Select the DiPlay version: 0.2.21+ needs Android 7.0+; 0.2.15–0.2.20 needs Android 7.1+; earlier reviewed releases need Android 9+. Wi-Fi Direct needs Android 7.0+ in 0.2.21+, 7.1+ in 0.2.15–0.2.20, 9+ in 0.2.13–0.2.14, and 10+ earlier. Select the exact version.
- Choose Built-in car hotspot, enable the real car hotspot, and save its exact name/password; keep iPhone Bluetooth/Wi-Fi enabled.
- Pair through car Bluetooth settings, select the intended iPhone and accept CarPlay prompts. Review requested Wi-Fi/Location/Nearby permissions.
- Try USB with a known data path. If one transport works, record it rather than calling the whole car incompatible.
Reported results & workarounds
For 0.2.0→0.2.6 loops, first re-check the migrated hotspot selection and saved details. #26 reports clearing app data as a workaround; it erases settings/pairing and should follow diagnostic export, not precede the basic checks.
In #98, the reporter relays the manufacturer’s statement that this auto_rk_t21 / RK3326 firmware lacks RFCOMM support; both secure and insecure connect() attempts time out. This is firmware-specific second-hand evidence, not proof that every RK3326 fails or that every RK3326S works. This report applies only to the described firmware; other setups need separate testing.
Version status
For Android 10 getNetworkName failure, #79’s maintainer says 0.2.8 includes a fix. Only a custom-build retest is confirmed in the captured thread. A successful connection with the public APK still needs to be confirmed on the affected setup.
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.
New car icon blocks connecting, or an edge is blank?
Restore the default icon if connecting stopped after changing it; 0.2.18 resizes large images. Its Square corners, no safe area option can test edge gaps; Physical length affects iOS icon layout. Save and reconnect. For black video first disable HEVC/enabled video experiments, then follow the matching device issue.
USB startup avoids repeated two-second waits and requests CarPlay mode first on iOS 26. Auto-confirm recognizes the system USB dialog; on Android 7.1–9 with no permission page, already-approved network ADB can grant USB access. Vehicle acceptance remains pending.
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
Full updates, older version details and their validation limits are now collected in the version history. Follow the links below for the complete notes.
- 0.2.22 · Full version details
- 0.2.21 · Full version details
- 0.2.20 · Full version details
- 0.2.19 · Full version details
- 0.2.18 · Full version details
- 0.2.17 · Full version details
- 0.2.16 · Full version details
- 0.2.15 · Full version details
- 0.2.14 · Full version details
- 0.2.13 · Full version details
- 0.2.12 · Full version details
- 0.2.11 · Full version details
- 0.2.10 · Full version details
Reported setups
The following are source reports, not a universal affected-car list. Unknown fields remain unknown.
? / iOS 27 · DiPlay 0.2.6
Reported incompatible
Connection loop after updating from 0.2.0 with auto-connect enabled. Reporter says clearing app data restored connection; this erases preferences/pairing and is not a first step.
View original reportiPhone 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? / iOS 18.7.1 · DiPlay 0.2.6
Reported incompatible
After 0.2.0→0.2.6 upgrade, Wi-Fi Direct exits and hotspot stalls. iPhone model not stated.
View original report? / iOS ? · DiPlay ?
Reported incompatible
Wi-Fi Direct fails at getNetworkName on a Song Plus with a 17 Controller. App and Android versions were not supplied.
View original reportiPhone 15 / iOS 26.7.1 · DiPlay 0.2.7
Reported incompatible
Car-hotspot connection fails before CarPlay. Follow-up reports an RFCOMM connect() timeout; #99 quotes #98 and is not an independent test.
View original reportRelated GitHub issues
Closed does not necessarily mean fixed. The source is authoritative for later updates.