DiPlay Brings CarPlay to Android Head Units Without a Dongle

DiPlay is a new Android application that turns compatible Android based car head units into CarPlay receivers without requiring a separate dongle, a jailbreak, a Mac, or an account with a remote authentication service. The software is installed on the car rather than the iPhone, then accepts either a wired USB connection or a wireless CarPlay session from the phone.

The repository appeared on GitHub on September 24, 2026, and its three public preview releases have already recorded more than 3,800 APK downloads. That activity has been accompanied by roughly 324 GitHub stars, 71 forks, and an issue tracker that is already filling with reports from people testing the software in actual vehicles.

DiPlay is trying to replace the CarPlay adapter

Android head units that were not shipped with native CarPlay usually need an intermediary before an iPhone can project the CarPlay interface onto the screen. Commercial adapters and applications often supply that missing layer, sometimes through a USB accessory and sometimes through proprietary software tied to a particular head unit. DiPlay attempts to handle the receiver side directly on Android, with the iPhone communicating with the car computer rather than with an additional box plugged into it. Wired operation supports Android 9 and newer, while wireless operation can use Wi-Fi Direct on Android 10 and newer or the car's existing hotspot when the hardware and firmware permit it.

The application goes beyond simply displaying the CarPlay screen. It exposes resolution, frame rate, icon size, connection settings, audio handling, local diagnostics, and several fallbacks intended to cope with the inconsistent networking behavior found across Android automotive systems. On supported BYD firmware, DiPlay can also send navigation information to the instrument cluster and windshield display, including turn arrows, distance, street names, and map presentation data. Those additions are heavily dependent on the particular car and firmware, which is why the project's compatibility work is becoming more consequential than the basic CarPlay interface itself.

Nearly 4,000 APK downloads arrived before the first week ended

The first DiPlay public preview, version 0.1.0, was published on September 25 and has been downloaded 673 times. Version 0.2.0 followed two days later and has accumulated 2,894 APK downloads, while version 0.2.6 appeared on September 28 and has already passed 279 downloads. Taken together, the three APK files have recorded 3,846 downloads in roughly four days. For a new utility distributed through GitHub rather than an app store, that provides a more useful indication of actual installation interest than the repository's star count alone.

The issue tracker supports the same conclusion, although it also makes clear how early the software remains. Users are reporting wireless audio stuttering, connection failures, duplicated call interfaces, microphone echo, USB compatibility problems, and behavior that varies across BYD models and DiLink versions. Contributors are responding with hardware specific changes such as selectable navigation audio routes and improved cluster integration instead of merely proposing cosmetic features. DiPlay is therefore developing around the inconvenient reality of automotive Android, where two displays running nominally similar software can expose very different networking, audio, and projection behavior.

Compatibility is the central problem

CarPlay is not a generic video protocol that any Android application can reproduce reliably by drawing the correct interface. A receiver must negotiate authentication, networking, media transport, input, audio, and accessory behavior in ways that iOS accepts, while the Android head unit underneath may impose its own restrictions. DiPlay has already been physically tested on BYD DiLink hardware, but the developer does not claim universal compatibility and the user reports show why such a claim would be difficult to defend. A successful connection on one firmware revision says relatively little about whether another manufacturer's Android head unit will behave identically.

The latest version attempts to make some of this variation manageable from inside the application instead of expecting every owner to reproduce a developer setup manually. Version 0.2.6 adds a guided configuration path for instrument cluster maps, improves the car hotspot setup process, and stores information about connection methods that have previously worked. It also preserves settings across upgrades and includes local diagnostic export so failures can be examined without automatically sending vehicle information elsewhere. The resulting product is less a universal CarPlay switch than a compatibility layer that is gradually learning the peculiarities of different automotive Android environments.

The Apple certification question is not a footnote

DiPlay is not certified by Apple, and the project is unusually explicit about how its current CarPlay authentication works. The release APK contains an experimental accessory identity recovered from publicly available Carlinkit firmware rather than a newly issued MFi identity provisioned specifically for DiPlay. The associated credential can be extracted from the distributed APK, so it should not be understood as a secret merely because the project's public Git repository excludes it. The developer states that continued acceptance by future versions of iOS is unresolved, which creates a genuine possibility that an Apple update could affect compatibility even when nothing changes on the car.

That limitation does not mean the application is inherently malicious, but it changes what users should expect from it. DiPlay's public repository, GPL license, published release checksums, corresponding release archives, and local diagnostic design provide considerably more visibility than a closed adapter application, yet none of those properties can turn an unofficial CarPlay identity into an Apple supported one. Someone installing DiPlay is therefore testing an independent implementation whose continued operation depends partly on behavior outside the developer's control. The project's documentation treats that uncertainty as a technical constraint rather than hiding it behind generic compatibility language.

The current bugs are revealing where the difficult work remains

One report from a BYD Song Plus owner describes the vehicle's own Bluetooth call screen appearing over the CarPlay call interface, followed by echo problems when the native call audio path is disabled. Another user reports wireless audio stuttering on a BYD Dolphin and an inability to establish a wired CarPlay connection. A separate connection report describes failed sessions creating multiple Android share hotspots before the display eventually renders correctly. These are not merely interface defects, since each one emerges from the interaction among iOS, DiPlay, Android, and vehicle specific audio or networking behavior.

The engineering discussion around those reports is already becoming fairly detailed.

Contributors have measured audio delay, experimented with echo cancellation, separated navigation audio from media channels, and added fallbacks for output paths that do not exist on every Android build. That work suggests DiPlay may become more useful through accumulated hardware knowledge rather than through a single breakthrough feature. Automotive software often becomes dependable one awkward firmware combination at a time, and DiPlay has reached the stage where those combinations are beginning to arrive from users rather than only from the developer's own car.

DiPlay has a narrow opening that could become much larger

The appeal of DiPlay is straightforward for owners of Android based head units that lack satisfactory CarPlay support. Instead of purchasing another adapter and relying on the software bundled with it, they can install an independent receiver directly on compatible hardware and keep the connection local. The early download count suggests that this problem exists well beyond the developer's own setup, while the rapid appearance of vehicle specific reports shows how much compatibility work remains. The project will become considerably more significant if that testing expands beyond BYD systems and produces a reliable compatibility record across the broader market of Android head units.

Its near term trajectory will probably be determined less by GitHub popularity than by whether those installations continue working after iOS updates and across different vehicles.

A CarPlay receiver that works only on a small collection of known firmware versions remains a useful specialist tool, while one that accumulates broad hardware support begins competing with an entire category of physical adapters and proprietary receiver applications. DiPlay has not demonstrated the latter yet, and its public preview label is appropriate. What it has demonstrated in its first several days is that thousands of people are willing to download an APK to find out.

Download DiPlay for Android Head Units

DiPlay 0.2.6 is the current public preview and is distributed as an Android APK for compatible automotive head units. The application is installed on the car's Android system rather than on the iPhone, and the head unit must permit APK installation. Wireless compatibility depends on the available Android version, Wi-Fi hardware, vehicle firmware, and connection method, so the project's compatibility documentation is worth checking before replacing a working CarPlay setup. The official DiPlay 0.2.6 APK is available directly from GitHub at https://github.com/shihabal3amri/DiPlay/releases/download/v0.2.6/DiPlay-0.2.6.apk

DiPlay on GitHub

The DiPlay repository contains the current APK releases, installation documentation, compatibility notes, issue reports, security documentation, and vehicle specific development work. Since releases have been appearing within days of one another, the repository is also the clearest place to determine whether a reported connection or audio problem has already been addressed in a newer build. Users relying on the software in a vehicle should pay particular attention to the release notes because authentication behavior and firmware compatibility may change independently of the visible interface. The project is available at https://github.com/shihabal3amri/DiPlay