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.
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.