Skip to content

Troubleshooting

deviloufr-ai edited this page Nov 16, 2026 · 7 revisions

Troubleshooting

Install and updates

  • App not installed on update: the installed copy was signed with another key. Uninstall once, reinstall.
  • Update never shows: check the unit has internet; Settings → General → About → Check for updates. Want the newest builds first? Turn on Beta updates there.
  • The update dialog has no Update button on a 600 px screen: fixed on 2026-10-15, the notes now scroll inside it. Update once by downloading the APK.
  • Dashwheel crashed: it offers to send the error at the next start, once parked.

OBD

  1. Bluetooth adapter: pair it in Android's Bluetooth settings first, then allow Bluetooth when asked.
  2. An ELM327 takes one connection: unpair it from the phone or the unit's own Bluetooth app if they grab it.
  3. OBD dies when the phone connects to the unit: on QF units the phone and the adapter share one Bluetooth radio, and a phone whose Android Auto keeps trying to start wirelessly jams it. Turn wireless Android Auto off on the phone (or deny Android Auto the Nearby devices permission), or let the phone hold the adapter (OBD through this phone in the companion). Dashwheel then restarts the module by itself with root or the unit's ADB; the adapter is back about a minute later.
  4. The head unit refuses your Bluetooth adapter (some Joying units only take their own devices): use a USB OBD cable instead, see Car Data (OBD and CANbox).
  5. USB adapter not found: tap OBD and pick it at the top of the list. In Settings → Diagnostics → OBD adapter, OBD reached through must be Automatic or USB.
  6. Tyre pressures went blank after plugging in a USB TPMS receiver: fixed on 2026-10-12, Dashwheel no longer takes the receiver for an OBD cable.
  7. The Car problems tile shows the adapter's raw replies: include them in an issue.

Weather, speed limit or cameras empty

  • Weather unavailable (no internet connection): the unit is offline, check its Wi-Fi or hotspot. Nothing to do with root.
  • Map data server not answering: OpenStreetMap's Overpass servers are down; Dashwheel tries four of them and the tiles come back by themselves. Roads read on your drives are kept, and Settings → Driving → Speed limits on the unit downloads the area around the car ahead of time. You can set your own in Map and route servers.

Media, directions, notifications empty

Grant Notification access to Dashwheel (one switch covers all three). Start playback or navigation so there's a notification to read.

Split screen, keys, typing from the phone

Turn on Settings → Accessibility → Dashwheel. After an update that added key features, turn it off and on again.

A tile with an app inside is black

Wait ~10 s: a watch reopens it. Apps that block screen capture always show black. Check Settings → Head unit → Unit tools → Google Maps inside a tile says Set up (Root and PMPatch3).

The unit's top bar shows over Maps

Settings → Head unit → The head unit's top bar → Hide it over app windows (opt-in: it misplaced windows on some units).

Locked out of the car's screen

A wheel button that sends you somewhere, a look you can't leave, a stuck split or another launcher: from the paired phone, Companion → Tools tab → Rescue puts it right without touching the car's screen. See Phone Link and Companion.

The dashboard floats in a window or shrinks to half the screen

Older QF firmware keeps its home screen as a floating window. Since 2026-10-20 Dashwheel forgets the window the unit remembered, gives the NAVI key back to the unit, opens the map beside it in a window instead of a split, and grows the dashboard back by itself (root, Shizuku or the unit's ADB). Update Dashwheel.

Tyres went quiet, the TPMS app says "device error"

With root, Dashwheel unplugs and replugs the unit's TPMS box by itself: see Car Data.

Second screen

See Second Screen Setup and Pairing.

Some touches don't land

A screen that feels nothing in one upright strip: Settings → General → Expert → Lab → Dead touch strip. Slide a finger across the screen once, check the strip found in red, save: the Settings side bar then grows past it.

Dashwheel starts with no map and says safe mode

It failed to start twice in a row. Tap Retry on the dashboard; if it comes back, send the crash report it offers.

Logs

Settings → General → About → Unit log sends the unit's log to the phone, to share as a bug report. No phone linked? Save the unit's log here writes it to the unit's Download → Dashwheel folder, to copy to a USB stick. It includes how the unit started and what Dashwheel read from Waze and Maps (their screens and their tiles), every screen opened since the unit started, the unit's own launcher settings and which app it holds as its home screen. A copy is kept the moment the unit finishes starting, and a report too big for the phone link drops old log lines, never its summary.

The unit's screen-off key turns the screen back on

Fixed on 2026-10-10: update Dashwheel.

Waze in a tile: its search won't type

Fixed on 2026-10-10: the search goes back onto its tile, where the keyboard works. For the voice prompt, give Waze the microphone permission once.

From a computer on the same network as the unit: adb connect <unit-ip>:5555 (or the unit's own port), then adb logcat -s <Tag>. Useful tags: Obd, EmbeddedApp, DockShell, RomPopups, HeadUnitPhone, SecondScreen, DisplayLink, StreamDisplay.

Still stuck? Open an issue with your unit model, firmware, Dashwheel version and what you see.

Clone this wiki locally