Symptom
DiPlay cannot discover the iPhone, loops at Connecting, or keeps asking for USB access.
Possible causes
Charge-only hardware, incorrect USB host/device roles and trust/permission problems differ from a protocol-stage loop. #44 shows a negotiated USB link can still fail later.
Quick checks
- Try a known data-capable cable and the vehicle’s documented data port. Keep the iPhone unlocked.
- Approve Android USB access, iPhone Trust/CarPlay, and local VPN permission if shown.
- Close competing projection apps and record whether the phone is discovered before the loop.
- Compare the same phone over built-in hotspot; export a report after the failure.
Reported results & workarounds
Han #11 reports working USB with repeated permissions on 0.2.0. That customized Android permission behavior has no documented universal bypass. Do not use ADB permission changes as an unverified cure.
Version status
Seal 06 #57’s failed iPhone 13 Pro / reported iOS 26 and successful XS Max / 18.7.1 are on 0.2.7. The issue is closed, but the captured discussion does not prove a 0.2.8 fix.
Reported setups
The following are source reports, not a universal affected-car list. Unknown fields remain unknown.
iPhone 13 Pro / iOS 26 · DiPlay 0.2.7
Reported incompatible
Reporter describes repeated USB reconnection with this phone. Issue closed; no confirmed 0.2.8 retest. Year supplied in a reporter comment.
View original reportiPhone XS Max / iOS 18.7.1 · DiPlay 0.2.7
Limited evidence
Same reporter says this phone connects over USB. Audio, controls and long-term stability not assessed.
View original reportiPhone 13 Pro Max / iOS 27.0 · DiPlay 0.2.0
Works with known issues
Projection and touch explicitly work. Steering-wheel media keys fail; USB permission repeats and startup takes about 15–25 seconds. Newer steering-wheel implementation exists, but this exact setup has no retest.
View original reportRelated GitHub issues
Closed does not necessarily mean fixed. The source is authoritative for later updates.