Installation is only the first check
01
Install the APK
Match Android/API, CPU architecture and the exact APK.
02
Launch and connect
Check startup, Bluetooth, authentication and the first CarPlay video frame.
03
Check the functions you need
Record music, navigation, calls, Siri and reconnection separately on the same build.
Can Android 4.4 use DiPlay?
The official DiPlay APK requires Android 7.0 or later. For an Android 4.4–6 head unit, check the Android version, CPU architecture and firmware before choosing a community build. The archived DiPlay-Legacy-Android v0.3.12 declares Android 4.2 / API 17 as its minimum installation requirement. Check the reports for your exact build and device before trying CarPlay.
Android 8.1: official APK or a third-party build?
Android 8.1 meets the current official APK minimum, but vehicle connectivity and individual features still need testing. The ORA Good Cat build targets the China 2024 Harman Intel x86/x86_64 head unit; it is not a general ARM package. Android 8.1 Universal is a separate four-architecture build with vehicle-test limits. Compare the exact device, package name, installation requirements and evidence instead of choosing by Android version alone.
Version matrix
| Android | Release scope | What has been tested |
|---|---|---|
| 7.0–8.1 · 0.2.22 | 0.2.22: Android 7.0+ (API 24), target API 37, versionCode 41, com.shihab.diplay; eleven app languages including Korean and Turkish. On Android 7.0–8.1, wired CarPlay is confirmed only on a 2020 BYD Han EV / DiLink 2.0 / Android 7.1.2; wireless needs vehicle testing. Launcher map embedding needs Android 11+. Adds one signature-level USB permission and one non-exported launcher-card activity. | Test the exact 0.2.22 APK and firmware while parked: hotspot, music speed/recovery, USB reconnect and voice recording, calls/Siri, launcher and cluster. Android 7.0–8.1 wireless remains unverified beyond the single-car wired report; test optional features separately. |
| 9 | APK / USB / Wi-Fi Direct (0.2.13+) | Requested channel unverified; no universal vehicle test |
| 10 | USB, built-in hotspot, Wi-Fi Direct paths | Vendor API crash reports; #79 official-APK retest pending |
| 11–13+ | Above the minimum | Radio, decoder, firmware and iPhone still determine actual success |
| 8 / 8.1 | Select the DiPlay version: 0.2.21+ needs Android 7.0+; 0.2.15–0.2.20 needs Android 7.1+; earlier reviewed releases need Android 9+. | DiPlay · ORA Good Cat: Only the recorded 2024 Harman Intel x86/x86_64 car. Full Siri, calls, USB and other firmware remain unverified. |
| 7 | Select the DiPlay version: 0.2.21+ needs Android 7.0+; 0.2.15–0.2.20 needs Android 7.1+; earlier reviewed releases need Android 9+. | DiPlay · ding2548-ui: The new hotspot path has no confirmed vehicle result. Earlier hotspot failures remain historical; external Wi-Fi needs a third network. |
| 6 | Below official APK minimum | DiPlay-Persona-Android6: No public Release APK; default build lacks authentication identity. Wireless/calls/Siri/long sessions pending. |
| 4.4 / 5 | Below official APK minimum | DiPlay-Legacy-Android: Public signed APK; Android 5.1 SD8227 and Android 4.4 users report parsing failures; Android 8.1 MT6737M users report USB setup failure. No complete legacy CarPlay session established. Copied upstream validation does not validate this port. |
| 4.3 | Below official APK minimum | DiPlay-Geely-Android43: Prerelease: H52 Wi-Fi Direct/iPhone still untested; no verified 5 GHz control. Android 4.4.2 music pauses and vendor Bluetooth access failures are reported. |
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.
APK parsing fails: what should I check?
Compare the actual Android/API and CPU ABI with this APK’s requirements. A 32-bit ARM system cannot use an arm64-only package. If they match, check the actual APK, full error and installer. Stop trying random packages; signature checks are not a required beginner step.
Version notes for this guide
Full updates, older version details and their validation limits are now collected in the version history. Follow the links below for the complete notes.
- 0.2.22 · Full version details
- 0.2.21 · Full version details
- 0.2.20 · Full version details
- 0.2.19 · Full version details
- 0.2.18 · Full version details
- 0.2.17 · Full version details
- 0.2.16 · Full version details
- 0.2.15 · Full version details
- 0.2.14 · Full version details
- 0.2.13 · Full version details
- 0.2.12 · Full version details
- 0.2.11 · Full version details
Related GitHub issues
Closed does not necessarily mean fixed. The source is authoritative for later updates.