GitPad
How it works
Back to board

shihabal3amri/DiPlay

shihabal3amri · personal account · GitHub id 42039842
GitHub

Independent CarPlay receiver for compatible Android head units. Wired and wireless public preview.

tools
Verify the dev 628 followerson GitHub since 201819 public repos Oman

Straight from the GitHub profile. The social links are the ones GitHub shows on github.com/shihabal3amri: nothing here is submitted to GitPad.

Stars
13k
Velocity
373.4★/day
Forks
1.6k
Language
Kotlin
Created
2026-09-24 (1mo)
Last push
2026-10-28
Category
tools
GitPad score
100/100
Fee lock

When this repo launches on GitPad, 100% of creator fees are locked on-chain to shihabal3amri's GitHub vault. The split can never be changed after launch, by anyone. shihabal3amri claims by connecting GitHub on pump.fun.

Gsw88ermLopJt1LNbUZrNt4kM2Laz3zpwzTj92JW4LTK
vault not created
Vault on Solscan How the lock works

In short

DiPlay is an independent Android app, written in Kotlin, that provides CarPlay on compatible BYD head units over wired USB or wireless connections, with a BYD-specific interface. The README states that it is not Apple-certified, that it bundles an experimental accessory identity, and that compatibility beyond the tested head units and iOS versions is not guaranteed, with the project focused on BYD cars and unsupported on other brands. Its features include BYD HUD navigation on verified firmware, car hotspot and Wi-Fi Direct connection paths, and local diagnostic export that is shared only when the user chooses.

Written by GitPad research from the repo’s public material. The full text follows below.

README · straight from GitHub

DiPlay

English · 简体中文 · 繁體中文

CarPlay for compatible BYD Android head units. Wired and wireless, with the familiar DiAuto interface. Independent app: com.shihab.diplay.

BYD support scope: These projects focus on BYD cars. They may work on other brands, but other brands are unsupported and there are no plans to add support or fix brand-specific incompatibilities.

Download & website · Release · Report a problem

DiPlay home

0.2.22 — public preview

Install on the car, not the iPhone. No jailbreak, dongle, Mac, account or authentication server is required for use. Core CarPlay does not require ADB; optional dashboard, battery, wheel-speed and parked-video features do. Your head unit must permit APK installation. The APK supports Android 7.0+ (API 24); on Android 7.0–8.1, wired CarPlay is confirmed on one car and wireless is not yet confirmed on a vehicle. Wireless supports Wi-Fi Direct, the car’s existing hotspot or Existing Wi-Fi / Same LAN. Android 7.0–9 Wi-Fi Direct uses a firmware-dependent legacy path with generated group credentials and unverified requested frequency; see Android 9 Wi-Fi Direct. Android 10+ verifies its negotiated group frequency.

  • Wired USB and wireless CarPlay with local authentication.
  • BYD HUD navigation with arrows, distance and street names on verified firmware.
  • Car hotspot support, improved audio buffering and saved receive diagnostics.
  • Automatic address discovery, fixed-channel Wi-Fi fallbacks and successful-configuration memory.
  • Icon/text size, resolution and frame rate; applying a display change reconnects CarPlay.
  • Local diagnostic export. Reports are sent only if you choose to share them.
  • Separate installation alongside DiAuto. Run one projection app at a time.

This is not an Apple-certified product. The APK bundles an experimental accessory identity recovered from public Carlinkit firmware, not a newly provisioned MFi identity for DiPlay. A bundled private key is extractable. Acceptance after future iOS updates, reliability across head units and suitability of that identity for general distribution are unresolved. This release invites community testing; it is not a guarantee of universal compatibility.

Earlier releases were tested on the development DiLink5.1 car: live windshield guidance and street names work, Car hotspot now starts CarPlay, and Wi-Fi Direct performance is substantially improved. Audio underrun recovery is improved in 0.2.15; remaining cutouts need current diagnostic reports. The 0.2.16 software Opus microphone fallback was accepted on a BOS Mini A1 head unit (Android 9) with an iPhone 12 on iOS 27. The floating-map test build was installed on the development DiLink 5.1 car; feedback led to the pinch corrections in 0.2.9. Earlier wheel-speed and video contributions were tested on a BYD Tang with DiLink 5.0 and an iPhone 15 Pro on iOS 27; wheel-speed dead reckoning in tunnels remains unverified. Broader head-unit and iOS compatibility is not guaranteed. The HUD firmware scope and cleanup limits are documented in BYD navigation.

What’s new in 0.2.22

  • Wireless CarPlay over the car hotspot connects again on BYD DiLink 3.0 and 4.0 head units where 0.2.21 stayed on "Opening CarPlay"; the Hotspot interface (optional) workaround can be cleared.
  • Music plays at the iPhone's speed over Wi-Fi again, from the first second of every song, without the 0.2.21 speed-up and stutter.
  • Over USB, WeChat voice messages, Voice Memos and dictation record your voice instead of silence.
  • Wired CarPlay connects on the first attempt after a replug, and the CarPlay screen and Home say why a connection failed and what to change.
  • DiPlay is available in Korean and Turkish.
  • New options, off by default: keep CarPlay in the launcher card, navigation prompts that ask for audio focus, calls at the call's own rate, a full-screen DiLink 3.0 dashboard map and the dashboard map on the Denza N9.

See 0.2.22 release notes and validation for contribution links and remaining physical tests. General stutter, calls/Siri, decoder and model-specific reports still need current-device evidence. 0.2.21 notes remain available as historical guidance.

If a problem remains, reproduce it on 0.2.22, then use Settings → Diagnostics → Save diagnostic report. Android 10+ normally saves to Downloads/DiPlay; Android 7.0–9 asks for storage access and saves there too. If unavailable, use View report or Share from the confirmation, which identifies external/private fallback storage. Review the .txt and attach it as a file to a matching existing issue, or create one. Include vehicle/head-unit model, exact firmware and Android/DiLink, phone/iOS, connection backend, relevant settings, steps and failure time. Reports are shared only when you choose; never post your hotspot password.

Documentation

Existing Wi-Fi / Same LAN keeps the iPhone and head unit on an external router. See the guide for setup, build requirements and the BYD DiLink 4.0 / Android 10 clean-install validation result.

The app and the website include English, Arabic, Russian, Ukrainian, Spanish, Simplified Chinese, Traditional Chinese (Taiwan), Japanese, Italian, Korean and Turkish. Traditional Chinese uses Taiwan wording; the app also recognizes Hong Kong/Macao and explicit Hant selections without claiming separate regional translations. Choose the app language in Settings; on Android 13+, it stays synchronized with Android’s per-app language setting. See the Traditional Chinese guide for installation, settings, troubleshooting, privacy and build instructions.

Source and credits

Based on xcertplay, GPL-3.0. The home/settings UI and website adapt DiAuto, AGPL-3.0; that license is included in docs/licenses. Preserve those notices when distributing modifications. CarPlay and its icon belong to Apple Inc.; no Apple or BYD affiliation or endorsement is implied.

This repository starts with a clean public source snapshot. Local research, tester reports and release-signing secrets are excluded. The complete source corresponding to the APK is provided with every release; experimental runtime identity assets are described separately in the build instructions and notices.

Local release packaging

The release APK intentionally contains the experimental accessory identity. The Git repository and source archive exclude all accessory and Android signing keys; tests generate synthetic identities at runtime. Source/CI builds omit runtime identity assets by default. Local release builds explicitly select an external asset directory. Publishing the APK makes its bundled identity extractable; building locally does not preserve that identity's confidentiality.