DiPlay Android Compatibility: Official Requirements and Legacy Ports

Version matrix

Minimum is not a support matrix

Android 10 meets the Wi-Fi Direct API baseline, yet some vendor frameworks lack the getter used in earlier builds. A version-specific software bug must not become a blanket DiLink incompatibility claim.

Android 13 is used in the maintainer’s verified DiLink 5.1 HUD firmware. That does not imply every Android 13 car has the same stock receiver.

Ports and forks

Independently modified DiPlay versions and related projects target older Android, specific head units, phones and browser displays. Compare source, public downloads and exact test scope before choosing a version.

Check the actual Android/API, CPU architecture, firmware and connection method. A brand name or lower minSdk alone does not establish compatibility.

The PSA Android 7.1.2 line is separate from Leapmotor; the author reports external Wi-Fi wireless use, while wired video remains unavailable.

New APK entries include Android 8.1 Universal v12, DiPlay-T8, OsnPlay, CS11/OneOS, RK3326 and GWM. Source, authentication and vehicle-test limits differ; check each directory entry.

HarmonyOS uses native HAP files rather than Android APKs. The public HAP needs personal signing and exposes only the UI; a complete connection requires local authentication resources and rebuilding.

• DiPlay Third-Party Versions: Legacy Android and Other Head Units

Changes and checks in 0.2.11

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

On Android 10, only the exact missing WifiP2pConfig.getNetworkName() framework-Builder signature before group creation permits one system-default attempt in Auto mode. Permission failures, timeouts and explicit channels do not use it. The old #15 report still needs a current-device retest.

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.

Changes and checks in 0.2.12

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

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.

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

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.

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

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

Related GitHub issues

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