DiPlay Versions: Latest Release, Regressions and Upgrade Notes

Faster USB startup, audio timing and phone diagnostics

What changed

• 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.
• Calls, Siri and navigation use the correct 16 kHz playback clock. Failed initial call-microphone reads retry up to three times; background music uses a 0.1 s decoder wait. First setup chooses navigation stream 14 for DiLink 3/4 and 15 for DiLink 5, preserving saved choices.
• DiLink 4 dashboard-map launch waits for window focus; reversing-camera transitions retain session size when another window hides the status bar. Smooth video/Direct video output restore the last picture; Android 9 and older regain dialog backgrounds. The CarPlay settings panel and narrow-screen search are adjusted, and an optional dashboard album-art card is added.
• Wireless adds MIUI 13 Bluetooth permissions, an immediate Bluetooth-off prompt and failure-specific recovery tips. Enter the actual second hotspot name ending in _5G when it exists. Wheel-key service recovery waits before re-enabling; hotspot-start reports give the cause.
• Settings → Diagnostics → Get the report on a phone offers Download report through a QR code or an address and six-digit code. Five wrong codes block typed entry until the page is reopened; QR access continues. Review the report before sharing; no automatic upload.
• Japanese joins the app's eight languages; Traditional Chinese is completed and 67 Arabic strings are translated. Source builds still omit runtime authentication assets. The public preview is experimental, not Apple-certified.

Why it matters

Consider 0.2.19 for slow USB startup, the matching call/Siri audio symptoms, dashboard/camera resizing or phone diagnostics. Test the exact APK while parked on your firmware; the changes do not guarantee every head unit works.

Validation and compatibility

Upstream reports 2,636 tests passed, one expected macOS skip, no failures; lint, source/production builds and archive checks passed. A local-build audio test on DiLink 3, the earlier Ford RFCOMM fix and contributor picture-restoration testing on a 2024 Tang retain their specific scope. No new maintainer vehicle or emulator test of the complete 0.2.19 release is claimed.

0.2.19: Android 7.1+ (API 25), target API 37, versionCode 38, com.shihab.diplay; eight app languages. Android 7.1–8.1 still needs vehicle testing; launcher embedding needs Android 11+. Legacy Bluetooth permissions now apply on every Android version and are granted without a prompt; other permissions are unchanged.

When to consider upgrading

Signing matches 0.2.18; update com.shihab.diplay in place to keep settings and pairing. Reproduce on 0.2.19, then Settings → Diagnostics → Save diagnostic report or Get the report on a phone. Android 7.1–9 requests storage access; Android 10+ normally saves to Downloads/DiPlay. View report/Share remain available. Review logs before posting; no automatic upload.

Existing limitations

• Public preview, not Apple-certified; bundled identity is extractable and future iOS acceptance is unresolved. Android 7.1–8.1 and repaired USB/audio/display paths need vehicle feedback. Optional experiments remain off by default; earlier or local-build tests do not validate this complete APK.

Vehicle checks still needed

• While parked, test 0.2.19 USB startup/permission, calls/Siri/microphone, background music, dashboard-map touch, reversing-camera return and phone reports on the exact firmware. Test optional features individually and retain diagnostics.

Last verified: 2026-10-12 · Original release notes

USB stability, wheel keys and settings backup

What changed

• USB keeps reads that finish at timeout, repairs Android 7.1 listener binding and retries configuration after detaching conflicting drivers. With network ADB already approved, missing VPN consent can be granted through ADB. These fixes still need vehicle acceptance.
• Connection stages and failures are localized. Wireless diagnoses unusable vendor Bluetooth, handles refused RFCOMM flushes and finds connected iPhones through car Bluetooth profiles. Hotspot names with non-English characters get a warning; try an English name when preparation stalls.
• Music waits up to 0.5 s instead of discarding AAC after 10 ms. Default-off experiments offer clearer USB navigation voice (calls unchanged), disabling media-key audio focus (wheel keys may stop), and car phone audio for CarPlay/VoIP calls (not validated with a real CarPlay call).
• Default-off display experiments add Harman full screen, square corners without safe area, MediaTek low-latency decoding and a cluster speedometer using approved ADB. The APK adds 32-bit x86 libraries. Screen length uses 25 mm steps; custom car-button icons are resized to 192 pixels.
• Foreground CarPlay can use next/previous keys without the wheel-key service, except during calls. Service restoration retries and foreground recovery improve. Geely/Lynk geely_fx11 gains media keys and Siri; HiCar may need disabling. Experimental call keys answer/decline; FCE cluster guidance is default-off and its CarPlay integration remains untested in a car.
• Settings → About backs up/restores listed settings on a phone via QR; pairing keys, authentication and hotspot credentials are excluded. The page stops on leaving or after 10 idle minutes. Updates allow another installer such as MT Manager and use the verified public Downloads copy when it matches.

Why it matters

While parked, test the exact 0.2.18 APK: USB stability, music, Bluetooth, wheel keys, settings backup and required experiments. Turn optional features on individually; record firmware and diagnostics.

Validation and compatibility

Upstream reports 2,498 tests passed, one expected macOS skip, no failures; lint and source/production builds passed. Earlier Harman-build tests, Android Auto FCE-path checks and contributor geely_fx11 results retain their exact scope. No new maintainer vehicle or emulator test of the complete 0.2.18 release is claimed.

0.2.18: Android 7.1+ (API 25), target API 37, versionCode 37, com.shihab.diplay; seven app languages. Android 7.1–8.1 still needs vehicle testing; launcher embedding needs Android 11+. MANAGE_OWN_CALLS is added only for default-off experimental car phone audio.

When to consider upgrading

Signing matches 0.2.17; update com.shihab.diplay in place to retain settings/pairing. Reproduce on 0.2.18, then Settings → Diagnostics → Save diagnostic report. Android 7.1–9 requests storage access; Android 10+ normally saves to Downloads/DiPlay. Use View report/Share fallbacks, review logs before posting; no automatic upload.

Existing limitations

• Public preview, experimental and not Apple-certified. Bundled identity is extractable; future iOS acceptance is unresolved. Android 7.1–8.1 and new repairs/experiments require exact-firmware testing. Earlier tests do not validate this complete APK.

Vehicle checks still needed

• While parked, test the exact 0.2.18 APK: USB stability, music, Bluetooth, wheel keys, settings backup and required experiments. Turn optional features on individually; record firmware and diagnostics.

Last verified: 2026-10-11 · Original release notes

USB recovery, Wi-Fi Direct and voice notes

What changed

• USB skips an isolated damaged NCM block instead of reconnecting; recurring damage still reconnects. Older iPhones get one identification retry without unsupported messages; iOS 13.6.1 session success remains unconfirmed. USB access auto-confirm recognizes Android 10+ and Chinese prompts, with a BYD accessibility-settings fallback. Interface claiming retries and failure diagnostics improve; iOS 15 or earlier may still need an iOS update or wireless.
• 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.
• Prefer the built-in car hotspot for Wi-Fi Direct stutter. With already-approved network ADB, 0.2.17 pauses Wi-Fi network search during Wi-Fi Direct on Android 7.1+, restoring it after the session. Car hotspot/Same LAN do not pause it. Diagnostics explains skipped pauses; this extension still needs vehicle acceptance.
• Messaging-app voice notes such as WhatsApp use the head-unit microphone; Opus 16 kHz packet timing is corrected. Calls and Siri are unchanged. These voice-note changes still need in-car acceptance.
• Experimental vehicle options include default-off suppression of BYD's call popup on Android 12L with approved ADB, restored when CarPlay leaves the foreground or ends; album-cover lighting, whose field-tested fork does not validate this port; and physical Bluetooth controller keys. These need vehicle feedback. A contributor confirmed the hotfix-firmware lamp-settings repair on a 2024 Tang.
• Setup recognizes DiLink generation from the controller version. Daily/open-time GitHub checks show Update available; About disables them, and downloads require a tap. Verified updates also copy to Download/DiPlay on Android 10+. Android 7.1–9 reports ask for storage access; denied/unavailable storage uses report-view/share fallbacks. Android 11+ also falls back when the Downloads provider fails.

Why it matters

Consider 0.2.17 for USB drops, Wi-Fi Direct stutter or voice notes; verify the exact firmware and optional features.

Validation and compatibility

Upstream reports 2,350 unit tests passed, one expected macOS skip and no failures; lint and source/production builds passed. Contributors tested hotfix-firmware lamp settings on a 2024 Tang and update notices on a head unit. No new maintainer vehicle or emulator test of the complete 0.2.17 release is claimed; earlier software Opus and fork tests remain version-scoped.

0.2.17: Android 7.1+ (API 25), target API 37, versionCode 36, package com.shihab.diplay; seven app languages. Android 7.1–8.1 still needs vehicle testing. Launcher embedding requires Android 11+.

When to consider upgrading

Signing matches 0.2.16; update com.shihab.diplay in place to retain settings/pairing. Reproduce on 0.2.17, then use Settings → Diagnostics → Save diagnostic report. Android 7.1–9 asks for storage access to save to Download/DiPlay; Android 10+ normally uses Downloads/DiPlay. Follow View report/Share or storage fallbacks; review logs before posting. Nothing uploads automatically.

Existing limitations

• Public preview, experimental and not Apple-certified; the bundled identity is extractable and future iOS acceptance unresolved. Android 7.1–8.1 and the new USB, identification, Wi-Fi Direct, charging, voice-note and experimental vehicle changes need exact-firmware acceptance. #572, #574 and draft #516 are excluded; no universal compatibility fix is claimed.

Vehicle checks still needed

• Test the exact 0.2.17 APK on your head unit while parked: USB recovery/charging, Wi-Fi Direct, voice notes and optional vehicle features. Contributor or older-build results do not validate other firmware or this complete release.

Last verified: 2026-10-10 · Original release notes

Calls on older Android, connection recovery and display controls

What changed

• On Android 7.1–9 without an Opus encoder, the software Opus fallback restores Siri and wireless-call microphone encoding, and diagnostics name the encoder. Echo cancellation now removes echo before noise suppression; buffered music adjusts its receive pacing. Call handling remains experimental and off by default, and needs mono audio to match.
• USB fixes NCM framing and Android 8 reads, shrinking rejected bulk reads down to 2 KiB retries. After a wireless timeout, DiPlay tries the hotspot on other address families, requests the Android 17 local-network permission, and handles a missing VPN consent screen. WPA3 and transition mode are added; when firmware cannot grant VPN access, the compatible connection path is still required.
• Advanced → Video and audio gains experimental low-latency decoding and direct video output, both off by default and disabled again if the picture corrupts or the app freezes. Direct output needs a reconnect and cannot adjust the picture; low-latency decoding takes effect on the next connection. Diagnostics add an FPS counter. Default video-backlog recovery and the initial day/night appearance at connect still need in-car feedback.
• Settings moves to inline search, and the quick menu confirms before discarding unapplied changes. Vehicle → CarPlay controls can disable the swipe-down gesture. Returning from an unchanged window keeps the connection alive. The sidebar supports three drag sizes and a passenger-side tab; on Android 12+ it blurs while being resized, and BYD tyre pressure and temperature are read through read-only ADB.
• Vehicle markers switch to 1% sliders, covering DiLink 4 and ADB paths, and take effect on the next connection. The steering-wheel card gains its own small-window layout and keeps the full-screen position until adjusted. DiLink 3 arrival time, the experimental Platform 21 on 2023 Tang DM-i, navigation steering-wheel volume, delayed Bluetooth pause and the music ambient light all await in-car acceptance. Experiments are off by default, and Bluetooth pause and lighting need authorized ADB.

What it means for you

Consider 0.2.16 when you need the corresponding call, connection or display fixes; test the optional features on your own firmware.

Validation and compatibility

Upstream reports 2,224 unit tests passing, one expected macOS skip, and no failures; source builds and lint pass. The software Opus path was accepted on BOS Mini A1 (Android 9, MediaTek) and on iPhone 12 / iOS 27; no new maintainer in-car or emulator testing is claimed for the complete new version.

0.2.16: Android 7.1+ (API 25), target API 37, versionCode 35, package com.shihab.diplay, seven App languages. Android 7.1–8.1 still need in-car validation; the desktop map embed requires Android 11+.

When to consider upgrading

The signature matches 0.2.15, and installing over the same package keeps your settings and pairings. After reproducing an issue on 0.2.16, use Settings → Diagnostics → Save diagnostic report. On Android 10+ it usually saves to Downloads/DiPlay, while Android 7.1–9 uses the file picker; view or share it as prompted, or fall back to storage. Nothing is uploaded automatically.

Remaining limitations

• Still experimental, not Apple-certified, and the built-in identity can be extracted. Android 7.1–8.1, video backlog, decoding and output, the initial appearance and optional vehicle features still need per-firmware testing. Background update check #488 and draft #516 are not included, and older iPhone diagnostics do not mean compatibility is fixed.

Still needs in-car validation

• Re-test the exact 0.2.16 APK on your target head unit: older Android, calls / Siri, USB and wireless recovery, video and the optional vehicle features. Testing on BOS Mini A1 and contributor builds cannot validate other firmware or the complete new version.

Last verified: 2026-10-09 · Original release notes

Android 9 Wi-Fi Direct, layout controls and optional audio/call experiments

What changed

• 0.2.13 adds firmware-dependent Android 9 Wi-Fi Direct using actual group credentials. Requested channels remain unverified on Android 9; Android 10+ verifies frequency. Cleanup retains persistent profiles (PR #282).
• 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).
• 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).
• Fixed dock choices can change live; Automatic transitions reconnect. Optional square-canvas rotation and split-window areas preserve video/touch mapping but increase decoder load. The experimental side panel is off by default and closes on rotation/split-screen changes (PR #245/#246/#277/#284).
• DiLink 4 native cluster casting and picture controls improve; contributor confirmation covers a 2022 Seal/DiLink 4/Android 10. DiLink 3 projection has checked recovery. Turn cards retain their two-minute expiry, map scale adds 125%, and battery/wheel-service recovery is scoped. Independent DiLink 3 call keys/dashboard cards are off by default; stock idle restoration is not a prior-state snapshot (PR #243/#260/#265/#285/#296/#297/#304/#306).
• 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).
• Traditional Chinese (Taiwan) is the seventh app language; Android 13+ system language selection is synchronized. Settings drafts, ambient-light controls, car-button editing and day/night placeholders are corrected. This community website has thirteen languages, separate from the app (PR #239/#252/#281/#286/#302/#305/#314/#317).

Why it matters

Consider this preview for firmware-specific wireless, USB and display problems or deliberate testing of the default-off experiments.

Validation and compatibility

Upstream checked 1,487 unit cases: 1,486 passed, one existing host-specific skip, no failures/errors. Four source-only debug builds/lint and the signed mobile release build/lint passed; existing warnings remain. The APK embeds build commit 6fb0fa4a09e77a84a437da5159147a6f6141ed61. No new maintainer vehicle test of the complete corrected release is claimed.

0.2.13 requires Android 9+ (API 28), targets API 37 and has versionCode 32. Wi-Fi Direct on Android 9 needs firmware APIs and cannot verify frequency; Android 10+ keeps frequency verification. Launcher embedding needs Android 11+. Optional BYD integrations retain firmware/permission limits.

When to consider upgrading

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.

Existing limitations

• Experimental, not Apple-certified; the bundled accessory identity is extractable and future iOS acceptance is uncertain. General stutter, decoder/black-screen, Siri and old-iOS reports are not universally resolved.

Vehicle checks still needed

• 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.

Related issue history / unresolved checks: #15, #151, #163, #174, #131, #117

Last verified: 2026-10-06 · Original release notes · Supporting source 1 · Supporting source 2 · Supporting source 3 · Supporting source 4 · Supporting source 5 · Supporting source 6 · Supporting source 7 · Supporting source 8 · Supporting source 9 · Supporting source 10

New connection choices, dashboard controls and recovery fixes

What changed

• Existing Wi-Fi / Same LAN connects the car and iPhone to the same external network. Join it in system settings, save its credentials, keep Bluetooth on and disable client isolation. DiPlay does not join Wi-Fi or change the default route (PR #223).
• Hotspot startup checks the actual AP interface and bounds retries when AirPlay never connects. Optional automatic hotspot startup remains off by default; its fallback needs supported firmware commands, authorized local ADB and observed readiness, not just a successful command (PR #229/#235).
• 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).
• 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).
• Virtual 16:9 maps support compatible launchers without a physical cluster. Experimental DiLink 3/4 routes add scoped cluster handling and retryable stock-state restoration; DiLink 5/5.1 keeps priority. No DiLink 3 windshield HUD or verified DiLink 4 HUD profile is claimed (PR #171/#182/#187/#213).
• 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).
• CarPlay appearance supports system, ambient-light, day and night modes. Main-video brightness, contrast, saturation and warmth adjust live, separately from Android’s app theme and the cluster stream; these controls do not prove colour faults fixed (PR #178/#211).
• Custom turn cards add 30%–95% sizing, opacity and phone-supplied arrival data. Unknown/expired guidance clears. Supported dashboard contents switch live with delivery checks; incompatible layout changes still reconnect (PR #193/#232).
• Optional wheel-map zoom and main-screen joystick are off by default. Configure keys while parked; call/media actions and matched press/release handling remain. Route and session checks reject commands for old phones or streams (PR #214/#231).
• Song-only-on-change cards show new metadata for five seconds with protected timer ownership. Artwork remains while a replacement is pending; confirmed failed transfers clear stale covers, but a never-ending transfer has no new timeout (PR #215/#228).
• 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).

Why it matters

Useful for testing an existing external network, supported cluster and wheel features, and obtaining reports on restrictive head units.

Validation and compatibility

Upstream reports 1,193 unit tests passed, one host-specific skip and no failures/errors. Four source-only debug builds and debug lint, release lint and the signed mobile release build passed; existing lint warnings remain. Signing matches 0.2.11. No fresh vehicle test of the complete repaired release is claimed.

Android 9+ APK; Wi-Fi Direct requires Android 10+, launcher map embedding Android 11+. Optional BYD routes still require supported firmware and permissions. Android 7/8 and other brands’ specific issues remain outside upstream support scope.

When to consider upgrading

Install over the same signed package to retain settings and pairing. Reproduce unresolved problems on 0.2.12, then use Settings → Diagnostics → Save diagnostic report and the shown location or View report/Share fallback.

Existing limitations

• The APK remains experimental and not Apple-certified; future iOS acceptance is not guaranteed. Force-stop can defer OEM, cluster or Wi-Fi restoration until DiPlay reopens.

Vehicle checks still needed

• 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.

Related issue history / unresolved checks: #15, #151, #163, #174, #131, #117

Last verified: 2026-10-05 · Original release notes · Supporting source 1 · Supporting source 2 · Supporting source 3 · Supporting source 4 · Supporting source 5 · Supporting source 6 · Supporting source 7 · Supporting source 8

Channel controls, vehicle settings and compatibility fixes

What changed

• 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).
• A custom dashboard turn card offers three sizes and position changes in 2% steps. Unknown arrows stay blank and expired guidance clears. The iPhone’s original video turn card cannot move independently (PR #155).
• The settings swipe accepts two, three or four fingers, with three as the default. D-pad/remote navigation is added for non-touch devices while retaining normal touch and knob behavior (PR #156/#146).
• Advanced vehicle data under Location keeps the DiLink 5.0 default and adds explicit legacy detection. Its bounded read-only probe needs authorized network ADB; only accepted fields enable their battery, wheel-speed and parked-video controls (PR #158/#173).
• Optional automatic startup of the car’s existing hotspot is off by default. It verifies permissions for DiPlay’s own package on supported BYD firmware and preserves the hotspot name/password (PR #164/#173).
• 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).
• 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).
• Bounded wireless, media, theme and own-app exit diagnostics add no automatic uploads or diagnostic permissions and omit audio/video/packet payloads. Reports still need review before public sharing.

Why it matters

Useful for comparing supported Wi-Fi Direct channels, configuring supported vehicle features and diagnosing connection or media failures.

Validation and compatibility

Upstream reports 773 unit tests passed, one host-specific skip and no failures/errors. Three source-only debug builds, debug lint, release lint and the signed release build passed; existing lint warnings remain. Signing matches 0.2.10. No fresh on-car validation is claimed.

Android 9+ APK; Wi-Fi Direct requires Android 10+, and launcher map embedding Android 11+. BYD support remains firmware-specific; Android 7/8 and other brands’ specific issues are outside upstream support scope.

When to consider upgrading

Install over the same signed package to retain settings and pairing. Reproduce unresolved problems on 0.2.11, then export Settings → Diagnostics → Save diagnostic report. For boot problems, reboot first and open DiPlay manually to export.

Existing limitations

• The APK remains experimental and not Apple-certified. Future iOS acceptance and suitability for general distribution remain unresolved.
• 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.

Vehicle checks still needed

• Check TV/knob input, turn-card placement, legacy fields and ADB denial/loss, automatic hotspot startup, app-only wired networking, channel selection, reconnects and long music sessions on the actual device.
• Optional parked video still requires valid P gear and closes when leaving P or losing the reading. Wireless vehicle/location data now belongs to the Wi-Fi iAP2 link; this does not prove tunnel navigation uses wheel speed (PR #157).

Related issue history / unresolved checks: #15, #151, #163, #174, #131, #117, #118, #127

Last verified: 2026-10-04 · Original release notes · Supporting source 1 · Supporting source 2 · Supporting source 3 · Supporting source 4 · Supporting source 5

Connection fixes, song artwork and richer diagnostics

What changed

• USB handles bounded USBMUX control-reply padding and permits unfinished Manual hotspot settings for wired sessions (PR #114/#130).
• Wireless startup can choose a free AirPlay port; Wi-Fi Direct handles unknown security reports, busy channels and bounded 5 GHz to 2.4 GHz fallback (PR #121/#143).
• CarPlay song metadata, playback position and scaled album artwork reach compatible launchers through Android media sessions (PR #82).
• Calls can use available Android echo cancellation and noise suppression; head-unit support varies and Siri capture is unchanged (PR #116).
• Network ADB battery reads select CAN/CANFD from the vehicle protocol. A saved show/hide setting controls the home-screen map mirror without disabling the cluster map (PR #123/#133).
• Optional video adds seeking and ten-second skips. Network ADB and a valid P gear reading are required; leaving P or losing the reading closes playback. FairPlay video remains unsupported (PR #129).
• More Ukrainian translations and Bluetooth, USB, reconnect, boot and microphone diagnostics; diagnostic additions are not a microphone-routing or Siri fix.

Why it matters

Useful for the targeted USB/wireless startup cases, compatible-launcher music displays and collecting clearer failure reports.

Validation and compatibility

Upstream reports 529 Linux tests with no failures or skips; local checks ran 528 tests with one macOS binding skip. Signed release build and lint passed; lint warnings remain. Signing matches 0.2.9. No new on-car validation was performed.

Android 9+ APK; Wi-Fi Direct requires Android 10+. Launcher map embedding retains its Android 11+ requirement. These targeted changes do not establish support for every car, launcher or Bluetooth firmware.

When to consider upgrading

Update over the existing signed installation to retain settings and pairing. For unresolved problems, reproduce on 0.2.10 and export a fresh report via Settings → Diagnostics → Save diagnostic report; for boot issues, reboot first, then open DiPlay manually to export.

Existing limitations

• Android 7/8 support was not added; HarmonyOS wireless compatibility remains unverified.
• Wi-Fi Direct packet loss, device-specific microphone input and reconnect problems still need hardware investigation; no universal fix is claimed.

Vehicle checks still needed

• 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.
• Fresh 0.2.10 logs are needed for wireless timeouts (#98/#134/#137/#142), rotation/reconnects (#119/#141), audio stutter (#131) and calls/Siri (#103/#115/#117/#138).
• Recheck boot startup (#118/#127) and display size (#92). An accepted boot activity request does not prove the app appeared on screen.

Related issue history / unresolved checks: #98, #134, #137, #142, #119, #141, #131, #103, #115, #117, #138, #118, #127, #92, #100, #124

Last verified: 2026-10-03 · Original release notes · Supporting source 1 · Supporting source 2 · Supporting source 3 · Supporting source 4 · Supporting source 5

Floating maps, launcher widgets and broader audio routing

What changed

• Floating centre-screen map with drag/pinch controls while DiPlay is backgrounded. Enable the instrument-cluster map and overlay permission; Usage Access limits it to home screens.
• Dashboard song display needs network ADB. Navigation widgets need a compatible launcher; BYD's built-in home does not accept arbitrary Android widgets.
• Optional live-map sharing and developer launcher samples require Android 11+. Sharing is off by default; when enabled, any local app can request the map.
• BYD day/night tracking, camera-window continuity and audio stream choices 0–20; 0 selects automatic routing.
• Ukrainian app language and GPS bearing correction. Some new Ukrainian feature strings still use English.

Why it matters

Useful on supported BYD setups for floating maps, launcher widgets or broader audio routing choices.

Validation and compatibility

At publication, upstream reported 420 tests and a signed build, plus DiLink 5.1 test-build installation; no separate final APK on-car test was recorded. Later 0.2.9 community reports (#124/#126/#131) do not verify APK origin or signing.

Android 9+ APK; Wi-Fi Direct needs Android 10+ and launcher map embedding needs Android 11+. Broader vehicle, launcher, calls/Siri and long-drive validation remains incomplete.

When to consider upgrading

Consider 0.2.9 for these features or the reported 0.2.8 channel-selection limit. Update in place to retain pairing; a stable setup does not automatically need an upgrade.

Existing limitations

• Occasional audio cutouts remain. Calls, Siri and long-drive reliability still need broader testing.
• BYD's built-in home cannot host arbitrary Android widgets. The Home and map-host samples are separate developer apps supplied as source.

Vehicle checks still needed

• Test day/night changes, camera-window resizing, touch alignment and background transitions on additional vehicles.
• On affected head units, verify channel 15 preview and navigation with music, including saved settings after reconnect.
• Test song clearing, widget route expiry, floating-map controls and home-screen restriction. Verify map-sharing revocation and a fresh attach after re-enabling.
• Check Home sample widget binding, app/back navigation and return to BYD home. Verify valid and unknown GPS course reports.

Related issue history / unresolved checks: #124, #126, #131

Last verified: 2026-10-02 · Original release notes · Supporting source 1 · Supporting source 2 · Supporting source 3 · Supporting source 4 · Supporting source 5 · Supporting source 6 · Supporting source 7

Location handoff fixes and optional vehicle data

What changed

• Location reporting follows the wireless Bluetooth-to-Wi-Fi handoff, capped at one update per second.
• Optional ADB wheel-speed and gear reporting; tunnel dead reckoning still unverified.
• Optional parked-video playback on reported iOS 27; ADB required, off by default, closes outside P.

Why it matters

Useful if you rely on head-unit location reporting or want to test the optional vehicle features on supported firmware.

Validation and compatibility

Contributor in-car testing: BYD Tang, DiLink 5.0, iPhone 15 Pro, reported iOS 27. Final packaged release APK has not had a separate on-car test.

Android 9+ remains the APK minimum; Wi-Fi Direct requires Android 10+. Maintainer reports #79 fixed, with custom-build confirmation only.

When to consider upgrading

If wireless location reporting stops after handoff, this release contains the relevant change. If your setup is stable and you do not use these features, there is no evidence-based universal upgrade recommendation.

Reported problems

• Navigation channel 14/15 selection reported unavailable (#85, #86).
• CarPlay size remains unchanged after reconnect on Seal EV / DiLink 4 / Android 10 (#92).

Related issue history / unresolved checks: #53, #72, #79, #85, #86, #92

Last verified: 2026-10-01 · Original release notes · Supporting source 1 · Supporting source 2 · Supporting source 3 · Supporting source 4

Steering-wheel controls, languages and dashboard choices

What changed

• Five app languages and Android app-language integration.
• Supported BYD steering-wheel media controls and long-press Siri while CarPlay is visible.
• Dashboard map / turn-card choices and optional ADB battery / map-pause features.

Why it matters

Owners on tested BYD firmware gain media-key handling and clearer dashboard choices.

Validation and compatibility

324 unit tests and signed build reported; no new physical-car validation for the packaged release.

Android 10 report #79 says earlier 0.1.0/0.2.0 worked; 0.2.7 failed. This is a version-specific report, not all DiLink 3.

When to consider upgrading

Consider the feature change if steering-wheel media controls are missing in your older build. Check the exact firmware scope in PR #8; other units need testing.

Reported problems

• Android 10 Wi-Fi Direct crash reported (#79).

Related issue history / unresolved checks: #1, #53, #57, #79

Last verified: 2026-10-01 · Original release notes · Supporting source 1 · Supporting source 2

Built-in hotspot becomes the default; cluster maps

What changed

• Built-in car hotspot is the default; legacy Local hotspot selection migrates.
• Instrument-cluster map and one-time automatic theme setup on verified DiLink 5.1.
• Diagnostic export and connection setup become easier to find.

Why it matters

A clearer hotspot setup without manually joining the phone, plus dashboard map options on verified firmware.

Validation and compatibility

Maintainer confirmed candidate hotspot and layouts on DiLink 5.1/Android 13. Final production APK not separately session-tested.

The hotspot workflow changed; old tutorials describing Local hotspot are obsolete.

When to consider upgrading

For built-in hotspot setup or supported cluster layouts, review this change. Owners upgrading from 0.2.0 should check saved hotspot details; connection loops were reported.

Reported problems

• Upgrade connection loops (#26, #42).
• Android 10 Wi-Fi Direct crash (#44).

Related issue history / unresolved checks: #26, #42, #44

Last verified: 2026-10-01 · Original release notes · Supporting source 1 · Supporting source 2 · Supporting source 3

Verified BYD HUD path and connection improvements

What changed

• HUD guidance on one verified DiLink 5.1 firmware.
• Built-in hotspot startup works on the development car.
• Wi-Fi Direct and audio buffering improvements, with cutouts still present.

Why it matters

Supported development-car firmware gains navigation arrows, next-turn distance and street names.

Validation and compatibility

234 tests reported; physical candidate HUD, hotspot and Wi-Fi Direct feedback, with broader driving coverage still needed.

Independent contributor reports DiLink 5.0 operation; official verified DiLink 5.1 scope stays narrow.

When to consider upgrading

If upgrading from 0.1.0 for HUD, check the exact firmware fingerprint. This is not a universal BYD HUD enablement.

Related issue history / unresolved checks: #1, #11, #15, #41

Last verified: 2026-10-01 · Original release notes · Supporting source 1

Restored public preview release

What changed

• Public APK restored after local rebuild on September 25.
• Same app version, version code and signing identity as the earlier 0.1.0 artifact.

Why it matters

Existing users can retain their installation; restoration itself is not a compatibility improvement.

Validation and compatibility

172 tests reported; no fresh physical-car test for the restored artifact.

Historical release instructions required Android 10+ Wi-Fi Direct for wireless; current hotspot guidance has since changed.

When to consider upgrading

Do not reinstall solely because the restored release has the same version. Review newer release behavior before changing a working setup.

Related issue history / unresolved checks: #1, #2

Last verified: 2026-10-01 · Original release notes · Supporting source 1