How DiPlay Compatibility Evidence Is Reviewed
Evidence levels
| Level | Meaning |
|---|---|
| Officially verified | Upstream documentation/source confirms a requirement or behavior; not a vehicle certification |
| Maintainer tested | Upstream maintainer explicitly reports a physical test, with stated scope |
| Community verified | An explicit first-hand test result; unknown versions and features remain unknown |
| Community reported | An owner describes a result; not independently reproduced |
| Partial / known issues | A setup has partial behavior or a documented limitation |
| Untested | No reliable report for the requested combination |
| System requirements not met | Below the minimum Android version for the selected release |
| Maintainer support scope | The project focuses on BYD; other brands may work but need their own testing |
How the checker avoids guessing
Every supplied field must match to count as exact evidence. Null source values cannot confirm a specified year, Android, iPhone, iOS or firmware. OS patches, DiLink subversions and builds are not silently merged.
A confirmation requires sufficiently specified versions and successful explicit test evidence. Single user success remains limited evidence; failure stays a report for that combination. Conflicting success/failure results are shown together.
Related model or generation reports are separate and can guide testing only. Compatibility is not inferred from a chipset, brand, installation success or Bluetooth pairing.
What gets published
Only reviewed normalized records enter the public data. API synchronization writes candidates for human review and never turns issue bodies into articles. Sources/notes preserve test-build versus release-artifact limits.
A model page needs at least three independent identifiable reporters plus useful successful version/transport evidence. Multiple issues from one reporter are not multiple independent tests.
0.2.9 evidence reviewed on 2 October 2026
The database now contains four 0.2.9 configurations from three reporters: Seal USB startup failure (#124), Yuan Plus wireless low frame rate and Siri issues (#126), and Song Plus DM-i Wi-Fi Direct audio stutter versus smoother built-in hotspot audio (#131). These are community reports, not vehicle certification; no report verifies the official APK origin or signing.
The upstream publication describes DiLink 5.1 test-build installation, not a separate test of the final signed APK. Old-version and unknown-version records remain separate. A model with older reports still has no 0.2.9 evidence unless a new version-specific report says otherwise; a model absent from the database has no reviewed model report.
Changes and checks in 0.2.10
Upstream reports 529 Linux tests with no failures or skips; local checks ran 528 tests with one macOS binding skip. Signed release build and lint passed; lint warnings remain. Signing matches 0.2.9. No new on-car validation was performed.
Android 9+ APK; Wi-Fi Direct requires Android 10+. Launcher map embedding retains its Android 11+ requirement. These targeted changes do not establish support for every car, launcher or Bluetooth firmware.
Changes and checks in 0.2.11
Upstream reports 773 unit tests passed, one host-specific skip and no failures/errors. Three source-only debug builds, debug lint, release lint and the signed release build passed; existing lint warnings remain. Signing matches 0.2.10. No fresh on-car validation is claimed.
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
Upstream reports 1,193 unit tests passed, one host-specific skip and no failures/errors. Four source-only debug builds and debug lint, release lint and the signed mobile release build passed; existing lint warnings remain. Signing matches 0.2.11. No fresh vehicle test of the complete repaired release is claimed.
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.
Same LAN supports open, WPA2-Personal and WPA2/WPA3 mixed networks; WPA3-only, enterprise and captive portals are outside its current scope. Allow multicast discovery. A contributor tested a standalone build on a 2022 Han DM-i / DiLink 4.0 / Android 10 / firmware 21.1.21.2401160.1; that is not a vehicle test of the complete signed 0.2.12 release.
本页依据公开项目文档及参考社区指南整理，保留实测边界与原始证据。资料快照不代表最新修复状态。