DiPlay Audio Stutter: Reduce Load and Compare Connections

Symptom

Music skips words, breaks up or cuts out even while CarPlay remains connected.

Possible causes

Interference, radio firmware behavior and decoder stalls can all contribute according to upstream compatibility notes. High resolution, 60 fps or HEVC can add device-specific demands.

Quick checks

1. Set 30 fps, turn Efficient video / HEVC off and keep Default icon/text size. Apply and reconnect.
2. Try 80% resolution, then 60% if necessary, keeping other settings fixed.
3. Use the car’s 5 GHz hotspot when available and compare USB. A supported frequency is useful to test, not a guaranteed cure.
4. Save diagnostics after a repeatable sample, noting whether music alone or navigation/music together triggers it.

Reported results & workarounds

Seal 06 / DiLink 5 / XS Max / iOS 18.7.1 report #53 is for wireless 0.2.7; wireless method is unknown. The maintainer asks for 0.2.8 logs, but no confirmed retest is captured.

Version status

0.2.7 includes audio-reliability changes, while the current README still acknowledges occasional cutouts. Open PR #6 proposes buffer changes and is not included in the reviewed release.

Changes and checks in 0.2.13

Wireless prefers usable IPv4 with scoped IPv6 fallback; Auto channel selection has no band or stutter guarantee. Interface mDNS avoids an unused NSD service; handoff fallback requires rendered video. Experimental hotspot join repair needs Android 13+, a user-configured 5 GHz-only hotspot, supported APIs, authorized localhost ADB and explicit confirmation while disconnected (PR #251/#258/#283/#309/#313).

Siri timestamps are corrected for the captured 24 kHz stream, not every microphone issue. Experimental buffered AAC-LC music is off by default, reconnects and needs supporting apps; it is not lossless or a cure for a continuously slow link. Touch events use TCP_NODELAY without a latency guarantee (PR #295/#308/#311).

Retest Android 9 P2P, model-specific cluster restoration, hotspot repair and call/audio paths on the target firmware. Buffered music still needs physical pause/seek/navigation/call/Siri checks; contributor setups do not validate the complete signed release.

Changes and checks in 0.2.12

On eligible Android 10 hotspot/Wi-Fi Direct sessions, optional authorized local ADB can pause station scans. Same LAN is excluded; automatic joining of saved networks is unavailable while paused. Recovery markers and retries restore scans, including after reopening; this is not a universal stutter fix (PR #225).

Multi-window preserves video proportions, touch alignment and system bars; compact setup screens fit better. Resolution accepts integer 30%–160% values; decoder-incompatible enlargement saves 100% with a notice. Cancel restores previewed settings and keeps the session (PR #172/#179/#181/#191/#230).

Retest repaired DiLink 3/4 cluster routes, scan recovery, wheel modes and firmware-specific hotspot startup. General stutter, calls/Siri/microphone, iOS 15 startup and colour/theme reports still need fresh current-device evidence.

Changes and checks in 0.2.11

Wi-Fi Direct adds Preferred channel under Connection setup. Auto is the default; a saved manual channel applies on the next connection. Unsupported or mismatched channels report an error. This is not a confirmed audio-stutter fix (PR #175).

Incremental song updates retain an omitted artist; unchanged metadata/artwork is no longer repeatedly published. An Android 9 audio API correction addresses a concrete compatibility fault without proving all causes of #163 are fixed (PR #161/#162/#173).

Manual channel selection is not a confirmed fix for Wi-Fi Direct loss/stutter. Qin Plus startup, iOS 15 connections, Siri/microphone quality and day/night firmware behavior still need current-device evidence.

Changes and checks in 0.2.10

Wi-Fi Direct packet loss, device-specific microphone input and reconnect problems still need hardware investigation; no universal fix is claimed.

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.