Symptom
The app fails or closes while creating the P2P group, before CarPlay appears.
Possible causes
Older Android is below the Wi-Fi Direct requirement; Android 10 vendor API gaps, missing permissions, stale groups and rejected operating frequencies are separate possibilities.
Quick checks
- Check the actual Android version. On Android 9, use USB or investigate the built-in hotspot path; do not claim P2P compatibility.
- Grant Wi-Fi/Location or Nearby Wi-Fi permissions as requested and enable Location where required.
- Close other projection apps. For stale groups, use Settings → Wireless connection help → Reset CarPlay Wi-Fi and review the confirmation.
- 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
An Android 10 minimum or a 5 GHz capability flag is not proof that group creation succeeds. Track the exact error and build rather than labeling all DiLink 3 incompatible.
Reported setups
The following are source reports, not a universal affected-car list. Unknown fields remain unknown.
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 reportRelated GitHub issues
Closed does not necessarily mean fixed. The source is authoritative for later updates.