DiPlay USB Not Working: Data Ports, Prompts and iOS Reports

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

1. Try a known data-capable cable and the vehicle’s documented data port. Keep the iPhone unlocked.
2. Approve Android USB access, iPhone Trust/CarPlay, and local VPN permission if shown.
3. Close competing projection apps and record whether the phone is discovered before the loop.
4. 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.

Changes and checks in 0.2.13

USB attachment switches transport within the activity; permission grants are checked. Narrow USBMUX trailer handling covers payload replies. Wireless can start without Android USB service, but wired/CH341 still requires it; the separate black-screen/decoder fault remains unresolved (PR #268/#298/#300).

The APK signing certificate matches 0.2.12. Update the same package in place to retain settings/pairing. Reproduce failures on 0.2.13 and save a fresh diagnostic report: Android 10+ uses Downloads/DiPlay, Android 9 a picker; View report/Share and app/private-storage fallbacks remain. No automatic upload occurs.

Changes and checks in 0.2.12

Apple-device USB attachment matching is corrected. Optional accessibility assistance confirms only DiPlay’s own system USB permission dialog; unrelated apps and dialogs are excluded. Normal USB authorization remains required (PR #170/#224).

Diagnostics add View report/Share fallback when the picker or Downloads provider fails. The confirmation shows Android/data/com.shihab.diplay/files/diagnostic-reports/ or private storage. No automatic upload occurs; export improvements do not prove startup fixed (PR #185/#219).

Changes and checks in 0.2.11

Reconnects use settled display geometry and normal readiness checks. The wired VPN must be scoped to DiPlay or startup aborts. A narrowly matched Android 10 P2P Builder failure gets one guarded Auto-mode recovery (PR #173/#168).

Reported setups

The following are source reports, not a universal affected-car list. Unknown fields remain unknown.

Related GitHub issues

Closed does not necessarily mean fixed. The source is authoritative for later updates.