Skip to content

Tested Hardware

deviloufr-ai edited this page Oct 10, 2026 · 5 revisions

Tested hardware

Dashwheel is developed on one real car and one real head unit, plus emulators. This page lists exactly what has been tried, so you know what to expect on your own setup. Tried something else? Please open an issue with your unit, firmware and what worked: this list grows from reports.

Legend: Daily use = in the project car every day · Car-tested = tried in the car at least once · Bench = runs on a desk, not in a car yet · Emulator = Android emulator only · Ordered = bought, not received yet.

Head units

Unit Details Status
ROCO K706 (QF001 firmware, Unisoc UIS7862 / UIS7862S, 8 cores) 1280×720 landscape, Android 10 (the settings say 12, the system is 10), sold as Ossuret / Hizpo and others (Shenzhen Jitu). Magisk + PMPatch3 installed; internal root ADB on port 9876 Daily use: the reference unit
ROCO K706, upright ("haiwai" build, 768×1024, Android 10) A user's unit with firmware bars (shortcuts on top, climate at the bottom); menus fixed to stay above them Reported by a user, fix not yet confirmed on that unit
NWD units A tester's unit (K4811) starts its own launcher at boot; Dashwheel used to bring it back over the dashboard a few seconds later. Fixed on 2026-10-10 Fix not yet confirmed by the tester
Joying units A user reports the unit refuses Bluetooth devices other than Joying's own; they use an OBDX Pro VT on USB. USB OBD adapters were added for this Reported by a user, USB support not yet confirmed there
HeadUnit_K706 emulator profile (API 29, 1280×720) Used for UI work. MapLibre's GL tiles crash on the emulator, so map tiles are tested in the car Emulator
Tablet API 29 emulator, phone emulators Upright layouts, phone screens, Canvas tabs Emulator
Other FYT / QF units, upright "Tesla-style" units Should work (Android 10+, landscape or portrait). ROM-specific features (boot logo, pop-up takeover, CAN box data, reverse camera) are only enabled on QF firmware and stay hidden elsewhere Not tested

K706 firmware specifics that Dashwheel uses

Firmware part Used for Status
Internal root ADB (:9876) Window placement, system-app install, boot logo, ROM settings Daily use
com.qf.bluetooth (phone via an external BT module, sd8761) Call state and answer / hang up; replacing the call pop-up Car-tested
com.qf.vehicle CAN box service (RZC Peugeot protocol) Doors, steering angle, rear radar, odometer, lights Car-tested (doors, reverse, radar, steering angle)
com.qf.backcar + AHD 1080p reversing camera (camera id 1, tp9950 switch) Dashwheel's own reverse view, camera takeover Car-tested
Unit key service (util_service) Steering-wheel and panel keys Car-tested, some buttons still missing
/great/bootanimation.zip, logo partition Boot Logo Emulator / scripts only
sys.freeform.fullscreen Hiding the unit's top bar over windows (opt-in) Mixed: misplaced windows on one unit, so off by default

Car

Car Details Status
Citroën C4 Picasso 2011, 1.6 HDi 110 (DV6TED4), BMP6 robotised gearbox, Exclusive trim CAN diagnostics (ISO 15765, 11-bit), engine ECU 7E0/7E8, gearbox also answers broadcasts; DPF with Eolys additive; electric parking brake; rear parking sensors Daily use
CAN box in the head unit's harness Set to a C4-family profile in the unit's factory menu Car-tested

Any OBD-II car should give the generic readings (speed, revs, temperatures, load, voltage, fault codes). Car-specific extras (fuel level from the CAN box, DPF advanced readings, gear estimation table) are tuned for this car.

OBD adapter

Adapter Notes Status
Generic ELM327 Bluetooth (classic SPP) Answers with headers on and spaces off; Dashwheel parses that Daily use
ELM327 USB cables (FTDI, CH340, PL2303, CP210x) and USB serial adapters (OBDX Pro VT, OBDLink) Added 2026-10-10; speed found by itself Not tested with a real adapter yet
Bluetooth adapter held by the phone (companion) The phone passes it on over the phone link Experimental
ELM327 Wi-Fi, BLE-only adapters Not supported (Bluetooth classic RFCOMM or USB only) –

Phones (Dashwheel Companion)

Phone Status
The developer's Android phone, as hotspot + companion Car-tested (link, notifications, calls)
Samsung phones Call handling path for app calls reported and handled (WhatsApp-style calls reaching the call state)
Android 13+ Needs Allow restricted settings for Notification access on a sideloaded app
Android 15+ (e.g. Galaxy S25) Hotspot link fixed 2026-10-04 (the companion turned the car away before); not yet confirmed on a phone

Second screen (Raspberry Pi)

Part Details Status
Raspberry Pi 3 Model B v1.2 2.4 GHz Wi-Fi only Car-tested on 2026-10-10: the Pi's own map with tiles over the phone hotspot. Earlier on the bench: 1920×1080 HDMI monitor, first picture about 17 s after power-up
Raspberry Pi OS Trixie Lite 64-bit Installer works on it; Bookworm supported (an installer stop there was fixed 2026-10-04) Bench
No-name "1 TB" microSD Fake card, used for the first test only: don't use one Bench (to replace)
Weak 5 V supply Undervoltage seen (throttled=0x50005): use a proper 3 A converter Bench (to replace)
7" 1024×600 HDMI panel (070JI42-HX-0, high brightness, keypad board) For the C4 Picasso's old RT5 screen spot Ordered
Raspberry Pi 3B+, Pi 4 / 5 Should work (3B+ adds 5 GHz) Not tested
RCA (composite) monitor via the 3.5 mm jack Supported by the installer (--composite) Not tested

See Second Screen (Raspberry Pi) ‐ experimental.

Root and patches on the reference unit

Status
Magisk (Zygisk on) Installed, daily use
PMPatch3 Magisk module Installed, daily use: apps inside tiles, Google Maps inside
No root, no patch Tested on the emulator and through the app's own fallbacks; see Root and PMPatch3 for what works

Clone this wiki locally