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
- Confirm Android 9+ for the APK and 10+ for Wi-Fi Direct. Close other projection apps.
- 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.
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.
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 reportRelated GitHub issues
Closed does not necessarily mean fixed. The source is authoritative for later updates.