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
0.2.22 — USB voice messages, Voice Memos and dictation use smaller microphone packets; vehicle confirmation is pending. Reconnect retries when the USB network opens; late wired startup can wait up to 45 s. This is a recovery limit, not a guaranteed connection time.
- 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.
USB handles bounded USBMUX control-reply padding and permits unfinished Manual hotspot settings for wired sessions (PR #114/#130). The USB correction targets captured iOS 27 framing. End-to-end wired media and reconnects on the non-BYD device in #100 still need confirmation.
#122 reports repeated access/pairing prompts without a CarPlay connection. Its exact DiPlay, firmware and iOS versions are incomplete; the report establishes neither a universal cause nor a fixed release. Keep that symptom separate from USBMUX framing failures and record the exact versions and diagnostics.
USB disconnects or shows no permission prompt?
Use a data port and short data cable, unlock iPhone and accept the actual USB/CarPlay/local VPN prompts. If charging or permissions restart, try Reduced/Low charging when available and reconnect. Idle read timeouts alone are normal; 0.2.18 fixes specific errors including USBMUX cancellation failure.
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.
Version notes for this guide
0.2.17 — If USB drops every few seconds, try Settings → Connection → USB connection → iPhone charging → Reduced (1.5 A), then Low (0.5 A), and reconnect. Normal remains 2.4 A. This changes the offer to the iPhone, not the port's physical limit; suspected Qin PLUS DM-i power insufficiency is unmeasured. Vehicle acceptance is pending.
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
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.