Skip to content
ZynView

Troubleshooting

Most failures come from one of a handful of causes. Work through them in order.

The app says the head unit server is not running

Android Auto only projects while its head unit server is on. Open Android Auto’s settings, tap “Version” ten times if developer mode is not unlocked, then ⋮ → “Start head unit server”. It stops when the phone restarts. Some phones hide its state from other apps, so ZynView may ask you to confirm instead of checking.

It cannot find or join the dash Wi-Fi

  • Make sure the bike is on and the dash is on its screen-mirroring page. The dash only starts its Wi-Fi there.
  • Turn the phone’s Wi-Fi on. You do not need to join a network manually.
  • Re-scan the QR code if the dash was reset or you changed bikes.
  • Grant Nearby devices (Android 13+) or Location while using the app (Android 12 and older). On Android 17, also Local network.

It says connected but the dash shows nothing, or the picture is wrong

  • Open Fit to the dash in the app to adjust how the picture fills the screen.
  • Switch the dash away from and back to the screen-mirroring page, then connect again.
  • Make sure only one app that acts as an Android Auto head unit is installed (remove older test builds).

It keeps retrying

The app retries on its own after a failed Wi-Fi join and keeps the last problem on screen so you can see what to fix. Tap Cancel at any time to stop.

A permission is blocked

If you chose “don’t ask again”, Android will not show the prompt. Use “Open app settings” in the app and allow it there.

Still stuck?

Open Logs in the app and share them, then email us from the contact section with your phone model, Android version and bike model. Logs contain connection details for your dash, so share them only with people you trust.