DiPlay 0.2.15 Private Beta Wired Disconnection Feedback Report
- Feedback date:2026-10-08
- DiPlay version:0.2.15 Private Beta
- Authentication type:local experimental beta identity; no remote fallback
- iPhone:iPhone14,2 (iPhone 13 series), airplay=760.20.1 (≈iOS 18.x)
- Affected devices (two, different brands and Android versions):
- HUAWEI BAH2-AL10 (Android 9 / API 28 / hi6250 / 1920x1200)
- Xiaomi M2105K81AC elish (Android 13 / API 33 / qcom / 2560x1600)
1. Issue summary
When connected via USB cable,iAP2 authentication succeeds every time, and the AirPlay session is fully established (first video frame and audio both work),but after the session has been running for several to tens of seconds (observed 6s / 15s / 24s / 65s, at irregular intervals),the iPhone directly closes the AirPlay control connection over TCPwithout any protocol-level termination command. It then reconnects automatically and authenticates successfully again, creating a loop.
The disconnection logs are identical character for character on two devices with different SoCs and Android versions → The disconnection is consistently initiated by the iPhone (iOS 18.x), and is unrelated to the Android implementation, device hardware, or USB cable.
2. Reproduction steps
- Connect an iPhone (iOS 18.x) to an Android device using a USB data cable;
- Start a wired connection in DiPlay 0.2.15 (USB permission → re-enumeration → iAP2/USBMUX → authentication);
- The AirPlay session is established, the first video frame renders, and audio plays normally;
- After several to tens of seconds (variable), the iPhone actively closes the control connection, and the app reconnects automatically;
- Authentication succeeds again after reconnecting and the session is re-established, then terminated again (loop).
3. Evidence of consistency across devices (key)
| Disconnection characteristic | HUAWEI BAH2 | Xiaomi elish |
|---|---|---|
| Close command | airplay control closing reason=control I/O failed: Socket closed | airplay control closing reason=control I/O failed: Socket closed |
| Stream ID when closed | activeStreams=[100, 110] | activeStreams=[100, 110] |
| Protocol-level termination command (0x43xx) | None; direct TCP close | None; direct TCP close |
| Residual packet errors after disconnection | AirPlay transport error: Invalid NTB16 short-packet pad | AirPlay transport error: Invalid NTB16 short-packet pad |
| USB/iAP2 physical channel after disconnection | Normal (iAP2 0x5001 arrives continuously every 0.45s) | Normal (IAP2 READY within 1.5s after reconnection) |
| Re-authentication after disconnection | Authentication succeeds again | Within 8s iap2 authentication accepted |
Notes:The log lines in both columns of the table above are identical character by character and reproducible across devices.
4. Key log excerpts (original text)
4.1 Huawei BAH2 (30fps locked backwards)
airplay control closing reason=control I/O failed: Socket closed activeStreams=[100, 110]
AirPlay session ended peer=[ip]
AirPlay session ended; reconnecting from scratch
AirPlay transport error: Invalid NTB16 short-packet pad
Pre-disconnection signs: the iPhone stops sending data for about 1 seconds (maxGap≈1000ms、readMaxMs≈1000ms、rx drops from 28fps to 10.2fps), then the TCP connection closes directly. iAP2 messages continue arriving after disconnection, and the USB physical link is healthy.
4.2 Xiaomi tablet elish (wired USB, after VPN issue was fixed)
22:20:48.749 IAP2 READY [wired] ready=true
22:20:50.795 wired iap2 authentication accepted
22:20:52.791 wired iap2 rx=0x4300 carplay-availability
22:20:52.793 wired iap2 tx=0x4301 carplay-start-session
22:20:59.143 AirPlay session active controller=[identifier] peer=[ip]
22:20:59.930 Video: first frame rendered
(22:21:04–22:21:20 视频 83–151 包/5s、LPCM 48kHz 音频持续正常、无丢包)
22:21:23.079 airplay control closing reason=control I/O failed: Socket closed activeStreams=[100, 110]
22:21:23.098 AirPlay session ended peer=[ip]
22:21:23.181 AirPlay transport error: Invalid NTB16 short-packet pad
22:21:31.504 wired iap2 authentication accepted ← 8 秒内再次认证通过
4.3 Control group: same iPhone wireless path (Xiaomi tablet, successful)
21:56:50.914 wireless iAP2 CSM channel opened over RFCOMM
21:56:51.083 IAP2 READY [wireless-rfcomm] ready=true
21:56:51.597 iap2 authentication accepted
21:56:53.172 AirPlay session active
21:56:54.379 Video: first frame rendered
Wireless path (Bluetooth RFCOMM authentication/control + Wi-Fi hotspot data)Works normallywith no disconnection as described above.
Variables ruled out
❌ Android device implementation: The disconnection logs from both devices (Huawei hi6250 / Xiaomi qcom, Android 9 / 13) are identical character by character, ruling out device-specific issues
❌ USB cable/power supply: USB enumeration, USBMUX, NCM, and iAP2 were healthy throughout; iAP2 messages continued after disconnection, ruling out the physical link
❌ Authentication rejection: Authentication succeeds every time (100%), and the iPhone accepts new authentication again within seconds of termination
❌ Video/audio transmission quality: Before disconnecting, video was stable at 27–29fps, and LPCM audio had no dropouts or stuttering
❌ 60fps/rotation and other secondary factors: Locking to portrait + 30fps only extended the session duration (7s → 65s); the disconnection pattern remained unchanged
6. Hypothesis
The iPhone (iOS 18.x) actively terminates the CarPlay control session midway through the session, at irregular intervals and without a protocol-level termination command. This may be related to local experimental beta identity 's session-time revalidation/eviction mechanism. The wireless path (iAP2 over RFCOMM + Wi-Fi) is unaffected, while the wired path (iAP2 over USBMUX + NCM/VPN) is terminated. The difference between the two may offer a troubleshooting clue.
7. Areas where developer assistance would be helpful
- Is the experimental MFi identity used by 0.2.15 a type known to be evicted by iOS mid-session?
- Are there newer authentication assets or other identities available for testing?
- Could the differences between the wireless (RFCOMM) and wired (USBMUX/NCM-VPN) control/data paths be related to the termination behavior on the iOS side?
- The submitter can be contacted at any time for additional logs, reproduction data, or to participate in testing.
8. English Summary
Bug: Wired CarPlay sessions are terminated by the iPhone mid-session in the DiPlay 0.2.15 private beta.
- Devices: HUAWEI BAH2 (Android 9), Xiaomi elish (Android 13); iPhone 13-series, airplay=760.20.1 (iOS 18.x).
- Symptom: iAP2 authentication always succeeds; the AirPlay session starts, the first frame renders, and audio (LPCM 48kHz) plays normally. After 6–65s (at irregular intervals), the iPhone directly closes the AirPlay control TCP connection—without a protocol-level termination—then reconnects and re-authenticates successfully, and the cycle repeats.
- Cross-device evidence: The closing lines are byte-identical on both devices:
airplay control closing reason=control I/O failed: Socket closed activeStreams=[100, 110] followed by AirPlay transport error: Invalid NTB16 short-packet pad.
- Excluded: USB link (iAP2 keepalives continue after close), cable, authentication rejection (re-accepted within seconds), media quality (no drops before close).
- Note: The wireless path (iAP2 over Bluetooth RFCOMM + Wi-Fi hotspot) on the same iPhone works fine, which may help isolate the cause.
- Suspicion: iOS terminates sessions using the "local experimental beta identity" mid-run. Any updated identity assets or guidance would be greatly appreciated.