Quick tips for when things go wrong.

Phone connectivity (USB)

If your phone is not connecting to your Crankshaft head unit via USB (as opposed to WiFi or Bluetooth) a common cause can be the USB cable. Not all USB cables are created equal. Some cables only provide charging capability and do not include the data wires.

Cables with a high American Wire Gauge (AWG) or mm2 (Europe) rating are more likely to provide reliable connection. Some Crankshaft users have had good results with cables from Volutz and Anker. However, if your cable can connect your phone to a computer and transfer files, the cable should be suitable for Crankshaft use.

Display flickering

Some users have reported display brightness flickering with their Official Raspberry Pi touchscreens.

This can be caused when the touchscreen is powered via GPIO due to contact resistance inherent to the GPIO pins and standard connection wires.

To resolve this problem, you can try:

• upgrading your GPIO wires
• powering your unit via the touchscreen's Micro-USB port instead of the Raspberry Pi's Micro-USB port
• using the Official, 90-degree, Type-A to Micro-USB Raspberry Pi Touch Screen USB Power Cable

Time is not remembered

Unlike traditional motherboards, the Raspberry Pi does not have a Real Time Clock (RTC) and battery to save the time between reboots.

If you frequently connect to the internet, system time can be set dynamically via Network Time Protocol (NTP). You can also update the time manually via Settings, CS HW, [NTP-Sync].

Alternatively, CS supports several hardware RTC add-ons.