# One closed issue brought in 867 stars: DiPlay Legacy got old car head units running CarPlay, then the author disappeared · GitHub open source project > Source: https://stringers.io/en/github/gh_programmerguohuajing__DiPlay-Legacy-Android.html (Stringers / 什么值得做, generated 2026-11-08) > Stringers answers one question every day: what small product can one or two people build in a few months and actually make money from. Numbers come from 15 databases we collect daily, each with source and date. > For agents: these verdicts and the underlying databases (verified revenue, App Store / Google Play charts, ad libraries, GitHub, Product Hunt…) are queryable live over MCP — tools today / hot / products / directions / direction / data. Setup: https://github.com/komako-workshop/stringers (the user logs in at stringers.io → "配置 agent" to get a personal URL). Site index: https://stringers.io/llms.txt > The upstream only supports Android 9 and up, and closed requests for older systems as "not planned." It caught this batch of car owners the next day. In early October, a wave of Douyin and Bilibili tutorials on "CarPlay works on old head units too" pushed it up. [GitHub open-source project](https://stringers.io/en/github/index.md) · written 11-6 P programmerguohuajing/DiPlay-Legacy-Android · programmerguohuajing # One closed issue brought in 867 stars: DiPlay Legacy got old car head units running CarPlay, then the author disappeared **What it is** A port of the viral open-source CarPlay receiver DiPlay that lets old cars running Android 4.2 to 6.0 get CarPlay with a single APK install. **Why it blew up** Upstream only supported Android 9 and up, and closed requests for older systems as "not planned". This project picked up those owners the next day. In early October, a wave of Douyin and Bilibili tutorials on "CarPlay for old head units" pushed it up. **C** **How you could play it** Don't just fork this one. Copy the playbook: watch for popular open-source projects where the official maintainers rejected a request and the issue thread is full of people waiting. Ship a downloadable build within a day or two, then give short-video creators one line like "your device works too." Grade C: the playbook is worth learning, but this slot already has 116 forks and repackaged repos, the star ceiling is visible, daily growth has fallen to single digits, and the whole line still depends on authentication identity extracted from a converter box's firmware. The original author's account is gone. Circulating in small circles Data (updated daily) · repo created 2026-09-30 · 867 stars GitHub · stars Data 2026-10-09 → 2026-11-04 (27 days, 27 observations). Points before 10-28 come from deeply / archive backfill, not every day has one A Nissan Qashqai owner asked under the viral open-source project DiPlay: my head unit runs Android 4.4.2, can it be supported too? The next day a Chinese developer created a library called "DiPlay Legacy". In 37 days it got 867 stars and 50k+ APK downloads, then the repo and the author's account both vanished from GitHub. This piece covers how it took off, why it grew fast and fell just as fast, and whether you can run the same playbook. ### A car owner's request In Sep 2026 29, GitHub user ybshayu opened issue #31 on the DiPlay repo, titled "Add legacy Android 4.4.2 support". He was specific: a Nissan Qashqai, the factory head unit runs Android 4.4.2, can install third-party APKs, has a USB port, and no CarPlay; replacing the whole head unit is too much hassle. He even suggested a plan for the author: a separate "DiPlay Legacy" with minSdk 19, wired-only, resolution cut to 480p or 540p. "Even a Legacy wired-only mode would already be very useful." Replies piled up quickly: "My device is Android 4.2.2", "Mine is 4.4.2 too, I really need this". What is DiPlay? It appeared in Sep 24 as an open-source APK that turns an Android head unit into a CarPlay receiver: plug in your iPhone and the head unit screen shows the CarPlay interface, no need to spend two or three hundred on a converter box. It gained several hundred stars a day from late September to mid-October, reaching 13,380 by 11-06 (GitHub, 11-06). But its bar was Android 9. On Sep 30, the day after the issue was opened, programmerguohuajing created DiPlay-Legacy-Android, with a one-line description: "Modified from shihabal3amri/DiPlay, for compatibility with older Android systems and older Android head units." On Oct 7, the upstream author replied: the official build only supports Android 9 and up, PRs are welcome, and then closed the issue as "not planned". By then the Legacy version had shipped its first downloadable signed APK (v0.2.7, labeled "supports Android 4.4+"). ### Why this crowd Aftermarket Android screens and factory head units from a decade ago are largely Android 4.4 to 8 machines built on 32 chips: Allwinner T3, Zhangxun AC8227L, MediaTek; factory makers include Dongfeng Nissan's Hangsheng and Renault. When upstream DiPlay blew up, Douyin and Bilibili were full of install tutorials. These owners followed them and got "package parse error". Then they'd search "4.4 can it work?", and the first place to give an answer was this library. Its value to these people is simple: it's free, replacing a box that costs two or three hundred yuan, and across the 4.4 to 6.0 range it was the only pure-software option. ### Where the stars came from: the "good news for old head units" on Douyin From Oct 4 to 11, a batch of Chinese short-video tutorials appeared at once, all selling the same line: old head units can use it too. | Account | Date | Title | Data | |---|---|---|---| | Car head unit sharing club | 10-04 | Diplay car head unit version adapts to Android 4.4 | — | | Xiaoyu car head unit fun | 10-05 | — | 2,476 likes, 1,390 shares | | Cheng Qiaqia | 10-05 | Full CarPlay install tutorial for older car models | 3,791 likes | | Tutu loves gadgets | 10-06 | Good news for old head units: free CarPlay install | 4,875 likes | | Brother Kai drives | 10-11 | DiPlay for Android head units 4.0 and above | 3,237 shares | | Yan Ge gadgets | 10-18 | Diplay Android 4.1-9 universal package | 1,294 shares | Searching on Douyin, 11-06. On Bilibili, 10-06 has a video titled "CarPlay for car head units, supports old Android 4.4 head units" with 11k views in a few days; a Zhihu column published the same day "Android 4.4, 6, 7, 8 head units can also get CarPlay via DiPlay"; Smzdm and CSDN followed. This matches the star curve: 10-09 already had 287, 10-10 added +80 in a single day, the highest we saw, and 10-11 added another +74 (daily GitHub stars, from 10-09). A less visible force also helped: many Douyin accounts with names containing spoken-word-style hooks like "Yan Ge head unit" used "Android 4.4 universal package" as bait to drive traffic, selling head-unit software packages or pulling people into private groups. Their APKs often don't credit a source, but they all trace back to this library. Almost nobody in the English-speaking world mentioned it; on X we only found one tweet. ### What it did right: one release a day, turning "installs" into "works" The code, CarPlay authentication identity, and UI all come from upstream; its own contribution is the compatibility layer. But it fixed things extremely fast: the third-party directory diplay.org recorded 11-01 with 99 releases and 52,130 APK download requests, the most downloaded of the 250 third-party builds it listed. From 10-29 to 11-04, over these 7 days, it shipped a dozen-plus versions, up to 1 to 3 a day. The fixes targeted specific problems on older chips: a missing USB transfer method on Android 4.2 causing crashes, Zhangxun 8227 reverse-protection issues, wired video dropouts on Hangsheng head units, and media-key and codec fallbacks on 4.4. The approach was crowdsourced: the README asked users to export a "diagnostic report" and paste it into the issue, so most of the 263 open issues were device logs, each one a head unit the author didn't have. The README also recommended a community "real head unit version detection tool" aimed at catching aftermarket units labeled "Android 10" that were actually 4.4. ### Why it fell just as fast - **Upstream won half the people back.** Official DiPlay lowered its bar to Android 10-08, down to 7.0 from 7.1,10-17. Owners of 7 to 8 no longer needed it, and star growth dropped from several a day in early October to around 8 a day after 10-28 50. - **Results on old head units were unreliable.** diplay.org's review from mid-October said some 5.1 and 4.4 machines still wouldn't install, "no complete legacy CarPlay session confirmed yet"; later there was positive feedback from a Honda owner, but people kept reporting freezes and no sound on Allwinner T3/T4. - **The author disappeared.** 11-04 It still had 867 stars and 120 forks; when checked again at 11-06, the repo, download page, and author account were all 404. The reason is unclear: the public GitHub DMCA notices don't include it, and DMCA takedowns usually remove a repo rather than an entire account, so the more likely explanation is that the author deleted the account or was banned (inference). The author also had 15 other libraries for screen casting and TV apps, which were gone too. Someone stepped in the same day the slot opened: 11-06, an account named w-silence-w created DiPlay-Legacy-Android-Releases, rebuilt and published v0.3.16 through 0.3.18, and added in-app self-updating. In total there are 116 GitHub forks with the same name, and more than a dozen forks named "Legacy" targeting specific models: Nissan T32, Trumpchi GS5, an Android 4.2 version, a Huawei tablet version... ### Who is competing for the same crowd | Product | Scale | How it differs | |---|---|---| | DiPlay official | 13,380★(11-06) | Upstream; lowered the bar to 7.0, does not touch 4.4–6.0 | | DiPlay-CN | 873★ | BYD Chinese enhanced edition, bar 7.1 | | DiPlay-Geely-Android43 | 114★ | Only Geely, one 4.3 head unit | | CarLink | 185★ | CarPlay + Android Auto in one, for newer systems | | Carlinkit, ZLINK and similar adapter boxes | the big hardware brands | The certified chip lives in the box, so a 4.4 head unit works too, but you pay 50 to a few hundred yuan | GitHub stars were around 11-06. In the "4.4–6.0 legacy head unit, CarPlay in software only" slot, it was first and the only one with real scale; everything else was forked off it. ### If it were you **Verdict** : C. There's a useful playbook here, but following this one isn't worth it. The playbook: watch for issues on hit open-source projects that get closed as "not planned" with people queuing underneath asking for them, ship it the next day, and name it "upstream name + Legacy / car model". It proves this move can pull hundreds of stars in a week. But this exact spot is crowded now: 116 forks, a dozen model branches, and someone grabbed the mantle the day the original author vanished. The star ceiling is visible too: upstream sits at 13k, this one at 867, and in the last week it was adding single digits a day. What matters more: the whole DiPlay line uses CarPlay certification identity extracted from Carlinkit adapter firmware. The original author's whole account disappearing is probably tied to that risk (inference). **Who it fits** : Android developers with a few old head units who can flash and debug them themselves; people already making head-unit mod content on Douyin or Bilibili with an existing audience. **Who it doesn't fit** : anyone without real hardware who just wants to bump minSdk and ship (the old-chip pitfalls only show up on real devices); anyone who cares about account safety and doesn't want their GitHub profile to get banned along with the project. Don't use your main account for this kind of project. **How to do it** , ranked by how worthwhile: 1. **Applying the playbook to other hits** : whenever an open-source project gains thousands of stars in a week, go through its closed issues for requests like "old systems / other platforms / other languages / other hardware" that the maintainers explicitly said they won't do, and check how many people are piling on underneath. Pick one you can ship as a downloadable build within a day or two, and build it first. 2. **If you still want to go after the DiPlay line** , fill the gap it left: not another fork, but a compatibility list organized by chip and car model, plus a one-click checker that tells you "can your head unit run this, and which package should you install". Staying away from the certification identity cuts the risk a lot, and car owners and tutorial creators both need it. 3. **Taking over and maintaining it long-term** : the vacant spot is real, but you'd be competing with 116 forks and taking on ban risk. Only recommended for someone who already has that user base. **How to get users** : give Chinese head-unit mod creators a package they can download directly, with a line like "your old car works too". That hook is what they want, and they'll make tutorials on their own. Also keep a mirror outside GitHub and add in-app self-updates, so one ban doesn't cut off supply. **When to move** : the playbook works any time, but speed matters. Acting within a week of the upstream issue being closed is what captures the spillover. This DiPlay wave has mostly already passed. **Signs we misread this:** ① The original author or a fork gets back to dozens of stars a day within a month or two, meaning the old-car-head crowd is bigger than it looked and this should be scored higher; ② Apple shuts down the certificate identity in an iOS update and the whole DiPlay line stops working, so the 2 tool in the list loses its use too; ③ The upstream official project lowers the bar to Android 4.4, and this niche gets taken back immediately. ### Data and sources GitHub: shihabal3amri/DiPlay issue #31 and replies, repo star count (11-06); programmerguohuajing/DiPlay-Legacy-Android daily stars (10-09 to 11-04), 11-06 original repo and account 404; w-silence-w/DiPlay-Legacy-Android-Releases (11-06 new); README and commit history of fork mirror SmozX/DiPlay-Legacy-Android; github/dmca October and November notices. Wayback Machine 10-07, 10-13 snapshots. diplay.org /community/, /android/ (11-01, 11-05). Douyin search "DiPlay Android 4.4" "old head unit CarPlay" (11-06); Bilibili, Zhihu columns, Smzdm, CSDN related posts; X @realNyarime 10-06 tweet. Places marked "inference" are inferences. [GitHub repo ↗](https://github.com/programmerguohuajing/DiPlay-Legacy-Android) **Research notes: competitor table, acquisition evidence, full research report** Competitors | Name | Where | Launched | Scale | How it differs from this one | |---|---|---|---|---| | DiPlay official (shihabal3amri) | Open source | 2026-09-24 | 13,380★ / 1,714 fork(GitHub API 11-06) | Upstream; the code and certification identity both come from it. Its bar went from Android 9,10-08 to 7.1,10-17 to 7.0, and it never covered 4.4–6.0, only BYD | | DiPlay-CN(serein-morii) | Open source | 2026-10 | 873★, 11,783 downloads (diplay.org 10-12) | BYD Chinese enhanced edition, Android 7.1 minimum, no legacy systems | | DiPlay-Geely-Android43(xikai6282) | Open source | 2026-10 | 114★ | Geely Android 4.3 only, narrow scope | | CarLink(F-e-n-y-x) | Open source | 2026-10 base | 185★ | CarPlay and Android Auto in one, general head units, not focused on legacy systems | | Carlinkit / Chelianyi box, ZLINK / AutoKit | Other | Years | the big hardware brands | The certified chip lives in the box, so 4.4 head units work too, but hardware costs 50 to a few hundred yuan; this one is free and software-only | | Reddit private build "diplay for api 27 or less" | Other | 2026-10 | Not verified | Not open source, you need to comment or DM to get it | Where users come from - **Confirmed** **user spillover after upstream issue was rejected** : upstream issue #31 (09-29) proposed a "DiPlay Legacy / minSdk 19", with 4.2.2 and 4.4.2 car owners replying; 09-30 created the repo; 10-07 upstream closed it as not planned - **Confirmed** **Douyin / Bilibili / Zhihu tutorials** : Douyin has several "Android 4.4 old head unit CarPlay" tutorials from 10-04 to 10-11 (Tutu Aigaojii 4,875 likes, Cheng Qiaqia 3,791 likes, Xiaoyu Plays Head Units 2,476 likes, Kai Driving 3,237 shares); Bilibili has one video with 10-06 11,377 plays; Zhihu column 10-06; these line up with the star peaks of 10-10 / 10-11 - **Confirmed** **private-domain distribution** : a Douyin account name carrying a "咐置…叩苓" access code, using "Android 4.1-9 universal package" and "4.4 edition" as the lead-in hook - **Confirmed** **third-party SEO directory site** : diplay.org /android/ and /community/ link directly to its APK and recommend it under "Can Android 4.4 use DiPlay?" - Inference **X / media** : only one tweet from @realNyarime 10-06; x-radar search returns nothing; no tech media coverage ## Why DiPlay-Legacy-Android (programmerguohuajing) took off > Research date 2026-11-06. Data sources: our github repo tracking (repo_day, 10-09 to 11-04), GitHub API (same day), surviving fork mirror (SmozX/DiPlay-Legacy-Android, for README and commit history), Wayback Machine, diplay.org third-party directory, Jina web search, TikHub Douyin search, x-radar, github/dmca repo. The full analysis of upstream DiPlay is in the same folder, gh_shihabal3amri__DiPlay.md, and is not repeated here. ### The most important new development first: the original repo and the author's account are both gone - 2026-11-06 checked via the GitHub API. `programmerguohuajing/DiPlay-Legacy-Android` and the user `programmerguohuajing` both return 404, and the GitHub Pages download page is 404 too. The last time our tracking captured it was 11-04 (867★, 120 forks). So the account disappeared between 11-04 and 11-06. The whole account went, not just one repo. - The cause is not confirmed. The github/dmca repo's notices from October to 11-05 include no DMCA against it (only two BYD notices, 10-06 and 10-09, targeting the BYD-iOS / BYD-Android app repos, which are unrelated). DMCA usually takes down repos, not whole accounts, so the more likely explanation is that the author deleted the account or GitHub banned it. Which one, unverified. - The forks are all still up (116 same-name forks found). On 11-06, someone (w-silence-w, commits under the name wangshunqiang) created `DiPlay-Legacy-Android-Releases`, recompiled and republished v0.3.16–0.3.18, changed the package name to `com.shihab.diplay.legacy`, and added in-app self-updates. So someone is already taking over the vacated spot. ### One line A community port of DiPlay (the open-source APK that turns an Android head unit into a CarPlay receiver). Upstream DiPlay's bar started at Android 9+; the author ported it down to Android 4.4 (later 4.2 / API 17), for aftermarket and older OEM head units with Allwinner T3, Actions AC8227L, MediaTek, and 32-bit armv7/x86 chips (Dongfeng Nissan Hyundai-Autoplus, Renault, etc.). Created 2026-09-30, reached 867★ and 120 forks within 37 days; the author's account vanished afterward. ### Data - Star curve (github repo_day): 10-09 287 → 10-10 367 (**+80, highest single-day gain in the observation window** ) → 10-11 441 (+74) → 10-14 569 → 10-21 723 → 10-28 811 → 11-04 867. From 10-09 to 10-14 it averaged +56,10-28 a day; from 11-04 to 8 only +09-30 a day on average, a clear decay. We don't have the curve for 10-09 to 10-09, by which point it was already at 287★. - Releases and downloads: a diplay.org snapshot from 11-01 shows 99 releases and **52,130 APK download requests** , the highest download count among the directory's 250 third-party builds. The recall card's "11,783 downloads" is actually DiPlay-CN's figure, not this repo's. From the commit history, v0.3.5 to v0.3.16 shipped over the 10-29 to 11-04 period, 7 days, at 1–3 builds a day. - Issue numbers reached #373 (visible via commit references in forks), with 263 still open at that point. The author required a "diagnostic report" in the README, so most issues are device logs exported by users. - Author: a Chinese developer; commits are signed programmerguohuajing / jingguohua (email domain jxzm.net). Wayback 10-13 snapshots show he also pinned castlink, TVAPP, web-collection, mozi-agent and nexus-mind, work on screen casting and TV apps; search snapshots show 16 public repos. None of them are visible now. ### Why it took off 1. **Upstream explicitly declined, and this filled the gap.** On 2026-09-29, upstream issue #31 "Add legacy Android 4.4.2 support" (ybshayu, car is a Nissan Qashqai with an OEM Android 4.4.2 head unit) proposed a "DiPlay Legacy": minSdk 19, wired only, lower resolution. Below it, 4.2.2 and 4.4.2 more car owners replied asking for support. The next day (09-30) this repo was created, named DiPlay Legacy. On 10-07 the upstream author replied "officially only supports Android 9+" and closed the issue as not planned. Upstream effectively pushed those users over to this project. 2. **Riding the upstream surge to capture the largest existing user base.** Upstream DiPlay gained hundreds of stars a day from late September to mid October, and Douyin and Bilibili tutorials flooded feeds. But a huge share of aftermarket Android head units and older OEM units run Android 4.4–8 on 32-bit chips, and installing the upstream APK on them throws "parse package error". Owners who follow the tutorial and fail then search "4.4 compatible?", and this repo was the first on GitHub with a directly downloadable, signed APK (first release v0.2.7; Wayback snapshot 10-07: "Supports Android 4.4+, Release APK built with local MFi auth assets…"). 3. **Chinese short video promoted it as "works on old head units too" (main channel).** Searching Douyin with TikHub for "DiPlay Android 4.4" and "old head unit CarPlay" (2026-11-06): - Xiao Yu car-tech (10-05) 2,476 likes / 1,390 shares; - Tutu Gao Ji "Free install of CarPlay for old head units" (10-06) 4,875 likes; - Cheng Qia Qia "Full tutorial for installing CarPlay on older car models" (10-05) 3,791 likes; - Car head unit sharing group "Diplay head unit version supports Android 4.4" (10-04); - Yang Ge resource site "Currently supports Android 4.4 and above head units" (10-06); - Wei Qian "Android head unit diplay 4.0 to 4.3 install tutorial" (10-06); - Kai Ge drives "Android head units 4.0 and above diplay" (10-11) 3,237 shares; - Yan Ge tinkers "dipaly Android 4.1-9 universal package" (10-18) 1,294 shares; - ZhYi "Nissan old head unit upgrade + free CarPlay" (10-21) 407 likes. On Bilibili, 10-06 posted "Latest DiPlay update, CarPlay head unit version supports Android 4.4 old head units", which drew 11,377 views and 626 likes within days (cited by Smzdm 10-11). A Zhihu column 10-06 published "Many old car owners don't know: Android 4.4, 6, 7, 8 head units can also get CarPlay via DiPlay". On X, @realNyarime (10-06) posted "DiPlay now supports Android 4.4, you can run it on an old Android TV at home…". These clustered between 10-04 and 10-11, matching the star peaks of 10-10 / 10-11. 1. **Private-domain distributors were willing to push it.** Many Douyin accounts have passcodes in their names ("咐置彦哥车机叩苓"), using the "Android 4.4 universal package" as a hook to drive traffic and sell head unit software packages or funnel to private groups. They pushed the APK, often without credit, but both the APK and tutorials ultimately point back to this repo. 2. **Extremely fast iteration turned "it installs" into "it works".** 99 releases in a month, fixing old-chip issues one by one: `bulkTransfer` NoSuchMethodError on API 17, reverse-protection and hardware layer issues on Zhangxun PF8227, wired video dropouts on Hangsheng i.MX6, fallback paths for Android 4.4 media keys / notifications / codecs / multidex, and root hotspot via hostapd. It also linked up with community tools: the README recommends @493330227-wq's "head unit real-version detector" for spotting "fake Android 10 units that are actually 4.4" aftermarket devices. That speed kept long-tail owners around and drew a lot of forks. **Why people stuck with it:** it's free, versus a box that costs two or three hundred yuan; and it's the only viable pure-software option for these old head units. For 4.4–6.0 units there simply were no other choices. ### Competitors | Product | Where | Timeline | Scale | How it differs | |---|---|---|---|---| | DiPlay official (shihabal3amri) | Open source | 2026-09-24 | 13,380★ / 1,714 fork(GitHub API 11-06) | Upstream. The floor started at Android 9, v0.2.15 (10-08) lowered it to 7.1, v0.2.21 (10-17) lowered it to 7.0, but it never covered 4.4–6.0. BYD-only | | DiPlay-CN(serein-morii) | Open source | 2026-10 | 873★, 11,783 downloads (diplay.org 10-12) | BYD Chinese-enhanced edition, floor at Android 7.1, doesn't touch old systems | | DiPlay-Geely-Android43(xikai6282) | Open source | 2026-10 | 114★ | Geely single-model Android 4.3 port, narrower scope | | CarLink(F-e-n-y-x) | Open source | 2026-10 base | 185★ | Two-in-one CarPlay and Android Auto aimed at generic head units, focused on newer systems | | Reddit "modified diplay to work on api 27 or less" | Private distribution on forums | 2026-10 | Not verified | Poster asked people to comment or DM for the package, not open source | | Carlinkit / Chelianyi box, ZLINK / AutoKit | Hardware + closed-source APK | Years | Top brands | The auth chip sits in the box, so the head unit OS requirement is very low (4.4 works), but it costs 50 to several hundred yuan | | Carup / CarMore / MiAuto / Hiplay | Free domestic head-unit phone-mirroring APK | Not verified | Douyin "Principal Brother Talks Cars" Hiplay video 7,313 likes (08-18) | Mainly Android phone screen mirroring or CarLife-style solutions, not the CarPlay protocol itself | Bottom line: in the niche of "Android 4.4–6.0 old head units, pure-software CarPlay", it was basically the first and the only one at scale. Later entrants are brand or chip forks built on top of it. ### Growth tactics (evidence) - **Douyin / Bilibili / Zhihu tutorials (main channel, confirmed):** see the Douyin data above, the Bilibili 11,377 video with its views, and the Zhihu column. - **Spillover from upstream (confirmed):** the askers on upstream issue #31 and the audience of upstream tutorials; the diplay.org compatibility page ("Can Android 4.4 use DiPlay?") links straight to its APK. - **Third-party SEO directories (confirmed):** diplay.org lists it in the first tier of community builds, stating "Android 4.2+ / API 17", with a link to the latest release and download counts of 52,130. CSDN (10-20) and Smzdm (10-11) also ran "Android 4.4 old head units can run CarPlay too". - **Private-domain distributors (confirmed):** passcode-protected Douyin accounts were distributing the "4.4 universal package". - **X / HN / media (almost none):** nothing turned up in x-radar's 30–40 day corpus; only one @realNyarime tweet surfaced via web search. No ads found. ### How many people know about it / copycats - **Visibility:** it has spread widely in the Chinese car-modding scene (dozens of Douyin tutorials, Zhihu, Smzdm, CSDN), but almost nobody in English-language circles or tech media knows about it. No revenue involved. - **Many copycats:** - Documented, starred sub-forks: winkinwong/DiPlay-Legacy-Android-T32 (Nissan, 20★), JoeFee2024/DiPlay-Legacy-Android4.2, mp1314/DiPlay-Legacy-Nissan (11-04, Nissan custom build based on v0.3.15), MiniGrayGay/…-GS5 (Trumpchi), Ray-Hx/…-Android4.4, xssuper/DiPlay-HuaweiPad-M3, blblank (audio downgrade fix); - 116 same-named forks on GitHub in total; more than a dozen "Legacy"-named derivative builds in the diplay.org directory; - After the original author's account disappeared, a backup repo (w-silence-w) by someone who took over was published on the same day 11-06. ### Differentiation, and whether it's a manufactured ranking The differentiator is the **system floor** : Android 4.2–6.0 and 32-bit old chips that upstream officially doesn't support, which it did, with signed APKs, Chinese docs, and a diagnostic workflow. That's the only reason it took off: the code, auth identity, and UI all come from upstream (the README itself says "Independent app: com.shihab.diplay", and the bundled identity is the same one extracted from Carlinkit firmware). Its own contribution is the compatibility layer and extensive device fixes. This differentiation is thin and shrinking: - Upstream 10-08 dropped to 7.1 and 10-17 dropped to 7.0, pulling back the users between 7 and 8, and star growth fell from 50+ a day to single digits a day; - Real-world results are mixed. The diplay.org reviewer noted that Android 5.1 SD8227 and 4.4 users reported parse failures, and "no complete legacy CarPlay session has been confirmed yet" (the mid-October version). Later there was positive feedback on a Honda Pilot 0.3.11, but pairing was inconsistent; T3 / T4 still had freezing and no-audio problems. - The author's account disappeared and the project itself stalled, leaving a pile of forks competing to take over. ### What others can borrow - Watch for high-upvote issues closed as "not planned" in trending open-source projects. The people the official team turned down are ready-made users, and they'll act the next day. - Name it "upstream name + Legacy / model" directly, so search and tutorials naturally tie you to upstream. - Crowdsource long-tail hardware compatibility by having users "export a diagnostic report → paste it into an issue", and pair that with a release-a-day cadence. - Chinese short-video creators and private-domain distributors want hooks like "your car works too". Give them a directly downloadable APK and a one-line selling point, and they'll promote it for you. - Borrow the risks as well: depending on leaked identities and redistributing others' signed packages can get you banned or taken down at any time, so prepare mirrors and a self-update channel in advance. ### Still unclear - Why the author's account disappeared: self-deletion, a GitHub ban, or a complaint (none found in the public github/dmca records). - The star curve between 09-30 and 10-09, and the source of the first 287★. Likely from people who followed upstream issue #31 and the Douyin tutorials that started on 10-04, unverified. - How many of the 52,130 downloads were successful installs (old head units have high failure rates, so repeat downloads are common). - Whether Apple will revoke the bundled Carlinkit identity in an iOS update. That is a shared breakage risk for the whole DiPlay line. ### Sources - Our repo: github.repo_day (programmerguohuajing/DiPlay-Legacy-Android, 10-09 to 11-04) - GitHub API 2026-11-06: the original repo and user 404; fork search; shihabal3amri/DiPlay issue #31 and releases; github/dmca 2026/10, 2026/11 directories - Mirror README and commit history: [github.com/SmozX/DiPlay-Legacy-Android](https://github.com/SmozX/DiPlay-Legacy-Android) - Backup repo: [github.com/w-silence-w/DiPlay-Legacy-Android-Releases](https://github.com/w-silence-w/DiPlay-Legacy-Android-Releases) - Wayback: [web.archive.org/web/20261013053250/github.com/programmerguoh…](https://web.archive.org/web/20261013053250/https://github.com/programmerguohuajing) , [web.archive.org/web/20261007100219/github.com/programmerguoh…](https://web.archive.org/web/20261007100219/https://github.com/programmerguohuajing/DiPlay-Legacy-Android/releases/tag/v0.2.7) - [diplay.org/community/](https://diplay.org/community/) (11-05 snapshot), [diplay.org/android/](https://diplay.org/android/) - [zhuanlan.zhihu.com/p/2090743708509528665](https://zhuanlan.zhihu.com/p/2090743708509528665) - [post.smzdm.com/p/apqm2mq2/](https://post.smzdm.com/p/apqm2mq2/) - [bbs.csdn.net/weixin_29174013/article/details/100639050](https://bbs.csdn.net/weixin_29174013/article/details/100639050) - [x.com/realNyarime/status/2107547376902897880](https://x.com/realNyarime/status/2107547376902897880) - [www.reddit.com/r/Androidheadunits/comments/1wwfy9d/i_have_fi…](https://www.reddit.com/r/Androidheadunits/comments/1wwfy9d/i_have_finally_modified_diplay_to_work_with/) (403, only the search snippet was visible) - Douyin: TikHub search for "DiPlay Android 4.4" and "old head unit CarPlay", 2026-11-06 This article was written by AI from public data and the data we collect daily. Numbers are sourced, and inferences are labeled.