Supported Head Units

Supported head units

Dashwheel runs on any Android head unit with Android 10 or newer: it is a launcher, so the map, music, widgets, OBD data and phone link work everywhere. What differs from one unit to the next is how much of the unit's own firmware Dashwheel can talk to: the ignition, the wheel keys, the CAN box's car data, the unit's Bluetooth phone, its pop-ups and its camera.

At start, Dashwheel works out which firmware family your unit runs and speaks to it accordingly. Settings → Head unit → Head unit shows the family it found, what that firmware gives Dashwheel and what each feature still needs (root, a shell, a permission). If it guessed wrong, you can name the family there.

Most of these units claim a newer Android than they run (12, 13 or 14 on the box, Android 10 or 11 underneath). That is normal and handled.

Families

Status: Daily use = the developer's own unit, every day · Full support, waiting for testers = everything below is built from the community's reverse engineering, but nobody has confirmed it on a real unit yet · Basics = plain Android plus what the firmware announces to every app.

Family	Typical units and brands	What Dashwheel uses	Status
QF	Hizpo / ROCO K706 (QF001 UIS7862, QF005 UIS8581a), sold as Ossuret, Hizpo and others	Everything: ignition, the CAN box's car data and the MCU stream (doors, fuel, range, trip computer, warnings, radar, steering angle), the wheel and panel keys, the unit's Bluetooth phone and players, its volume and launcher choice, its pop-ups, the reversing camera, the boot logo	Daily use (reference unit)
FYT / SYU	Joying, Atoto, Mekede, Junsun, Idoing, Isudar, NaviFly, Sinosmart, Winca, some Xtrons and Seicane, DUDU; UIS7862, UIS7870, UIS8581a, SC9853i	Speed and revs from the CAN module, the car signals the Signal Finder learns, calls on the unit's Bluetooth (ringing, answer, hang up), the wheel keys (opt-in, needs a shell), ignition on / off	Full support, waiting for testers
Microntek MTCD / MTCE, HCT MTCH	Dasaita, Xtrons PX5 / PX6, Eonon, Pumpkin, Erisin, Klyde; PX3, PX5, PX6, PX30, QCM6125	The wheel keys, power-off, the Vehicle app's car frame and the system settings as Signal Finder sources. The firmware force-stops apps it has not whitelisted when the ignition goes off: the Head unit card tells you what to do	Full support, waiting for testers
Topway TS	TS10 (UIS7862), TS18 (UIS8151 / UIS8581), TS7 / TS8; Hikity, Podofo, many no-name units	No public interface is known: plain Android, the common ignition and key broadcasts, the Signal Finder	Basics
Reglink	The cheapest MediaTek units (AC8227L, AC8257)	Plain Android plus help to survive the firmware's app killer: DuraSpeed turned off at each boot (needs a one-time permission), the firmware's whitelists written with root, Quick Boot counted as a boot	Basics
Allwinner	T3 / T8 units with their own firmware (Junsun, Umecity, older Seicane)	Plain Android and the common broadcasts	Basics
Nowadays (NWD)	K4811 and similar (UIS8581)	Plain Android, the unit's launcher choice pointed at Dashwheel (needs a shell), its wheel-key broadcast	Basics; a tester's boot fix is waiting for confirmation
Anything else	Plain Android units, tablets, phones	GPS speed, OBD, Android's own volume and keys; the common ignition and key broadcasts are still listened to	Works as a launcher

Teyes units are FYT inside but locked down: expect the Basics there.

What every unit gets

• The dashboards, widgets, looks and apps in tiles
• Live car data from an ELM327 OBD adapter (Bluetooth or USB) and the AI mechanic
• The phone link with the Companion app: notifications, messages, the phone's GPS, the drive log
• The steering wheel button map for any key the unit hands to apps

Features that need the firmware (the CAN box's own data, the call and door pop-ups, the reversing camera, the boot logo) only show on the families that have them. Some need root or a shell on top: see Root and PMPatch3.

Wheel buttons and the CAN box

On QF units the wheel buttons come from the CAN box in the harness. The box only passes the buttons it knows for the car model chosen in the unit's CAN settings, and the firmware sometimes turns two buttons into the same key (on the reference C4 Picasso, Voice and Phone both open the phone). Buttons the box never sends (there: the cruise control and the ✦ ★ ⟳ buttons) can't reach any app. If buttons are missing, try another car model in the unit's CAN settings first. See Hands-Free and Steering Wheel.

Help us confirm your unit

Only the K706 is in the developer's car, so every other family is confirmed by its owners:

1. Install Dashwheel and use it for a drive or two.
2. Open Settings → General → About → Report how it works, mark what works, and send it (scan the code with your phone, or open it on the unit). The report carries the unit's model and firmware, the family Dashwheel found and which firmware features answered, nothing personal.
3. Or open an issue with your unit, its firmware and what you saw.

Confirmed units move to Tested Hardware. The technical details per family (services, broadcasts, sources) are in docs/unit-platforms.md.