Tested / Works:

• Google Pixel 1 Android Oreo 8.1
• Raspberry Pi 3B, Official touchscreen.
• Image 2018-02-24.

Tested / Works (issue #1):

• One Plus 3
• Raspberry Pi 3B, Official touchscreen.
• Image 2018-02-24.

Edit: Does not work with 7-inch HDMI screen, works with 7-inch official screen.

Tested / Does not work:

• Adafruits HDMI screen - Flickers, wrong aspect ratio. Raspberry Pi does not supply enough power to it. It will not flicker if you plug it in through a hub.
• Adafruits AR1100 touch controller - Does not work at all.
• Image 2018-02-24.

Tested / Does not work:
Galaxy Note8 (N950U1)
Raspberry Pi 3B, Official touchscreen.
Image 2018-02-24.

Additional Information:
Android 7.1.1 (N950U1UEU3BRA5)/Android Auto 3.0.570554-release

When Connected to the raspberry pi, Android Auto opened and started the "new device" setup, but then showed an error screen with the message "Communication error 2, the phone and the car are running incompatible software"

I will test with the official open auto instructions and see if that works.

EDIT: After following the compilation instructions for the aasdk and OpenAuto repositories, it appears to be working correctly.

Tested / Does not work:
Moto G4
Raspberry Pi 3B, external Display
Image: 2018-02-24.
Version: Android 7.0 / Android Auto Android Auto 3.0.570553-release

Error: (same as above). Communication Error 2

@kfechter How did you get it to work?

Tested/working (Linux x86_64/X11)

• Nexus 6P Oreo 8.1.0
• Desktop Linux (Thanks for the build instructions. Helped out a lot)
• Turned off the RPI3 build in the cmake flags and adjusted the paths to match my folders.

Tested / partially works

Huawai P8 lite android 6
android auto 3.0.570554
raspberry pi 3
Xenarc 7" hdmi touch screen.

Initial waiting for device screen is cropped
Phone connects ok, screen seems ok and working,
Touchscreen / usb mouse / usb keyboard not working.

Tested / partially works

• LG G4 H815 TWN
• Raspberry Pi 3B, official Touchscreen
• Image 2018-02-24

bluetooth does not work yet

Problem with Bluetooth is I think it depends on the HFP (hands free) profile working in Pulseaudio. I've been messing with it on my x86_64 testbed and while I do get a connection with Ofono running, no phone audio comes across from the phone.

EDIT: Turns out the chipset that particular computer was using wasn't compatible with the way Pulse/Ofono works.

Tried another computer and although I get handsfree audio from the phone ---> computer, nothing seems to happen in OpenAuto. Told it to use the local adapter but it only plays on the phone when making a call (the in call screen in Android Auto doesn't show the unavailable message)

EDIT2: Didn't realize Bluetooth was a separate toggle in the Android Auto phone side application. It is working for me now.

@VBMCBoy Assuming Pulse is setup for HFP on Crankshaft, you just need to toggle Bluetooth on in the AA settings phone side.

Working (so far):
Droid Turbo 2
Raspberry Pi 3B, Official touchscreen
Image 2018-02-24

Tested / Works:

Google Pixel 2 XL, Android Oreo 8.1
Raspberry Pi 3B, Official touchscreen.
Image 2018-02-28.

Tested / Works:

• Xiaomi Mi A1, Android Oreo 8.0.0
• Raspberry Pi 3B, Official touchscreen.
• Image 2018-02-24

Tested / Works:

Xiaomi Mi A1, Android Oreo 8.0.0
Raspberry Pi 3B, Official touchscreen.
Image 2018-02-28

Tested / Works:

Motorola Nexus 6, Android Nougat 7.1.1
Raspberry Pi 3B, Official touchscreen
Image 2018-03-03

Tested / Does not work

Motorola G5S, Android 7.1.1
Pi  3 model B / Official 7" screen.
Image: crankshaft-2018-03-02.zip.

Nothing happens at all when plugged in to USB (was same for the previous two versions as well)

Tested / Works :
Xiaomi A1 Android Oreo 8.0.0
Raspberry Pi 3 B, Official Raspberry Pi LCD 7 inch and
Waveshare LCD 10 inch HDMI (D) Touchscreen
Image 2008-02-2018
*) for Waveshare LCD no sound over LCD speaker

@nacbooth Just wanted to make sure, is it the G5S Plus? I am considering taking the plunge and buying one to test.

Tested / Works
Huawey P8 Lite 2017 (android 7.0 EMUI 5.0.1)
Raspberry Pi 3 B + Official screen
Image 2018-03-02

@htruong - it's not the plus variant: Motorola Moto G5S, 32 GB, (Single Sim), 3GB RAM, UK, SIM-Free

Updated: Changed USB cable, and now it looks like things work. Need to do further on-road tests, but looks OK in the workshop.

Motorola G5S, Android 7.1.1
Pi 3 model B / Official 7" screen.
Image: crankshaft-2018-03-02.zip.

@nacbooth That is indeed incredible. I am very happy to hear! I'd have to suggest it in the top post.

I have heard people have conflicting results about the same phone too and I was confused. This might have been why...

Tested / Works
Mi A1 Oreo 8.0.0
Pi 3 model B , Waveshare LCD 10 inch HDMI (D), touchscreen
Crankshaft-2018-03-02
for increase volume over LCD speakers :
enable HDMI audio over raspi-config and
add line in /etc/pulse/default.pa
set-sink-volume 0 32768

Updated: Changed USB cable

@nacbooth we had a similar issue in my wife's car w/ the real android auto. the usb in question worked fine elsewhere, but not in her car. but a different one did.

FWIW, Someone commented on my youtube video,
Gabriele Amodeo - "Working great with Samsung Galaxy S7 and Waveshare 7" inch LCD Touch, a little mod on config.txt is required but everything is good!"

Tested/Not Working:

Pixel 2 & Galaxy S4
Raspberry Pi 3 B, External 24" HDMI Screen.
Newest crankshaft build.

Probably because of Issue #1 not working, also I don't have an USB -> USB-C cable available at the moment, so I tried it with an USB -> Micro-USB cable with an Micro-USB -> USB-C Adapter attached.

Booting fine, Smartphone recognized and showing the Android Auto Splashscreen, but the HDMI screen is showing the default unconnected screen of Crankshaft.

Tested/Works

Essential Phone and Nexus 6P
Raspberry Pi 2, official 7" touchscreen
Crankshaft-2018-03-02

https://youtu.be/U3KxJ0raolU

it works fine w/ the GeeekPi 7 Inch 1024x600 Capacitive Touch Screen
if you do their config.txt adjustment:

hdmi_group=2
hdmi_mode=87
hdmi_cvt 1024 600 60 3 0 0 0
hdmi_force_hotplug=1

but i don't recommend it, as android auto only supports 480p*, and it looks fuzzy scaled to 600p.

(*) or 720p or 1080p if in dev mode, neither of which look any better at 600p.

Tested / Works

• Sony Xperia XZ Premium / Android 8.0 Oreo
• Raspberry Pi 3B / official 7-inch touchscreen
• Image 2018-03-02

Had to add lcd_rotate=2 to the config file to correct my display orientation with my case, but everything works as flawlessly as can be expected.

nostaxx I have. I use a raspberry pi 3 and a Google Pixel 3 XL running Android 10. It worked for me without any changes. I also use the official 7 in Raspberry Pi display, a USB sound card for AUX and microphone

I saw some videos on it with a pi 3b+ getting a little laggy at some times, is that the case for you as well?

I use pi 3b+ with my note10 running on Android 10. It get blank screen

nostaxx: The 3 B+ is what mine is, I haven't noticed much lag. I click an icon and within a second the app loads.
thanhtantran: What kind of a screen are you using? Also you would see the initial boot up whether you have a phone plugged into it or not.

I am trying with a 4B but no luck.
Any idea when it will be available?

I have built a version that should support rpi4 but i don't have one to test. I built the image to upgrade to Buster. Buster Crankshaft

matt2005: I've used your image and works on a 4B (4GB)
Not rock solid though. I have to re-initiate Wifi projection quite often (phone reboot required)
some audio lag and video lag

Configuration:
4B+, w/ build in sound, BT off (in case wifi projection)
Samsung A50 w/ Android 9
AA 5.1.500644

Working:
Both USB and Wifi projection
RTC
TSL2561/brightness, although lux number on screen doesn't refresh
Google Assistant
Google maps and Waze seem to work (no road testing yet)
WhatsApp messages get displayed/played

Moto G6 somewhat working. Sometimes will just quit randomly
Using Pi 3b with official touch screen.
Do sd cards or cables matter?
edit: OpenAuto crashed immediately after connecting phone. I think its the phone. It also dosen't register touches on older versions of crankshaft

Huawei Mate 10 Lite running the latest version of Android Auto on Crankshaft in Raspberry Pi 3 Model B+ - Higher resolution makes Crankshaft back to home screen and have to replug the phone again to relaunch Android Auto. Running at Wi-Fi has no problem.

Tested/working (Linux x86_64/X11)

• Nexus 6P Oreo 8.1.0
• Desktop Linux (Thanks for the build instructions. Helped out a lot)
• Turned off the RPI3 build in the cmake flags and adjusted the paths to match my folders.

Can you share on how you created the desktop linux build. Thnx

Tested / Works
Pixel 2 / Android 11
Raspberry Pi 4 + Official screen
"Crankshaft OpenCarOS NG Alpha7.2 2021-02-09"

Testing / Currently Working
Oneplus 7 Pro / Android 11
Raspberry Pi 3B + Test Monitor
"Crankshaft OpenCarOS NG Alpha7.2 2021-02-09"

This issue is stale because it has been open 120 days with no activity. Remove stale label or comment or this will be closed in 60 days.

Works OK on RP3B, China HDMI touchscreen, Nokia 8.3, Android 11, through USB. Not connecting through BT or WiFi (did not find how to enable Head Unit Server)

Works with Poco x3 NFC /custom Android 12 ROM
Raspberry pi 4 B 8Gb ram
Raspberry pi official 7inch touchscreen
Crankshaft NG OpenCarOS Version ea9e288
Build date 2021-09-22

Galaxy A52s 5G with preinstalled Android Auto + Raspberry Pi 4 Model B 4GB. Works with all three resolutions, touch screen not tested. (2021-09-22 build)

Update: One UI 4 / Android 12 not tested.

It works with a Raspberry Pi 4B 8 GB inside of a RasPad 3, the only problem is that at the 720p and 1080p resolutions the UI gets squashed. (although that could just be me)

Appears to be working (haven't yet mounted it and tested long-term / actual driving use):

Pixel 1 (root), latest (last) factory Android 10

Raspberry Pi Zero 2 W
Waveshare 7" 1024x600 Resistive IPS touch screen.

N.B.: The Pi Zero 2 W has the same amount of RAM (512 MB) as the Pi 3 A, so the GPU_MEM in /boot/crankshaft/crankshaft.env.sh needs to be changed to gpu_mem=128, like the Pi 3 A.

Touch screen drivers had to be installed from Waveshare's github repo, and as that overwrites /boot/config.txt, the original settings need to be merged manually (back /boot/config.txt up first!), and then calibrated with xinput_calibrator*.

In DEV_MODE, run startx, then start a new SSH session or tty with Ctrl+Shift+F2, then run DISPLAY=:0 xinput_calibrator, and then follow the instructions in the output of the xinput_calibrator in the second session and save in /usr/share/X11/xorg.conf.d/99-calibration.conf

As a side note, trying to flip the display 180° when testing initially on a Pi 3 B+ failed completely. (For cable management reasons, which are irrelevant with a working Zero 2, which is the case.)
With vc4-fkms-v3d set in config.txt (appears to be required for OpenAuto to run), the following methods of display rotation do not work:
config.txt
display_rotate=2 display_hdmi_rotate=2 display_lcd_rotate=2 lcd_rotate=2
/etc/crontab
@reboot root echo 2 > /sys/class/graphics/fbcon/rotate_all @reboot root sleep 30 && DISPLAY=:0 xrandr --output HDMI-1 --rotate inverted
/boot/cmdline.txt
video=HDMI-A-1:1280x800M@60,rotate=180

Whilst the above solutions that aren't set in config.txt work to at least flip the OpenAuto home screen, as soon as Android Auto connects, it returns to normal rotation and ignores the above settings.

I am aware that at least some of the config.txt settings are supposed to be calculated on the display itself (and the official Raspberry Pi screen supports this to reduce GPU load), and it appears that this specific Waveshare display does not seem to support this, but I don't understand why when OpenAuto is rotated, Android Auto isn't (as soon as the phone is connected).

Works with
s10+
Pi4 4GB
Raspberry PI 7" original LCD.

Q: Did any one try with Waveshare IPS displays? I see above post, but not able to configure.
I am planning to get new one - but not sure it will work or will give me any issues. Since height is less (60mm + 260MM) it will look good on a dashboard!
https://www.amazon.de/-/en/gp/product/B0B4S8S2CT/ref=ox_sc_act_title_1?smid=A3U321I9X7C9XA&th=1

rb69git maybe you could use:

Max_usb_current = 1
Hdmi_group = 2
Hdmi_mode = 87
Hdmi_timings = 400 0 100 10 140 1280 10 20 2 0 0 60 0 43000000 3

src: aliexpress.com/item/1005003394233624.html

Tested with
Nokia G10 and G21
Pi4 4GB
HDMI to CVS (NTSC) to Vehicle in built display (no touch)

Added small trackball to drive the onscreen cursor. Phone functionality only works from the phone as there is no BT connectivity in the vehicle. Music and navigation work via android auto, but unable to get the local media player working.

rb69git maybe you could use:

Max_usb_current = 1
Hdmi_group = 2
Hdmi_mode = 87
Hdmi_timings = 400 0 100 10 140 1280 10 20 2 0 0 60 0 43000000 3

src: aliexpress.com/item/1005003394233624.html

I'd also like to know if anyone has tried this. I was considering this exact unit, because I'm not satisfied with my aftermarket Amazon Auto-Screen. The boot/connection process is stupid slow and the refresh rates, buffering, etc. are not the best. So, I figured I could use my RP 4+ B or my Orange Pi Zero 2 and build something better. Also, with the thin form factor or the screen, I could hide the Raspberry Pi and lose all of the bulk, which will make it a more professional looking install. Sorry for the long post.

Tested with Nokia G10 and G21 Pi4 4GB HDMI to CVS (NTSC) to Vehicle in built display (no touch)

Added small trackball to drive the onscreen cursor. Phone functionality only works from the phone as there is no BT connectivity in the vehicle. Music and navigation work via android auto, but unable to get the local media player working.

Any pictures of this trackball configuration? I'm trying to imagine what this looks like.

Regular LG display connected to HDMI on mi Pi4. Connected phone and all worked as expected (I could see Google Maps etc.)
Then I switched to the WaveShare 8" DSI display(https://www.waveshare.com/wiki/8DP-CAPLCD). Installed the drivers as described by WaveShare. After the reboot, the Crankshaft GUI does show and all seems OK. But when I connect my phone I do see that it is connected (big tile shows USB OnePlus), but the Open Auto doesn't show, and I keep seeing the Crankshaft GUI (right top corner says "lock". Don't know if that is relevant though)
On my phone, it does show that I am connected to Android Auto.

Tested/working (Linux x86_64/X11)

* Nexus 6P Oreo 8.1.0

* Desktop Linux (Thanks for the build instructions. Helped out a lot)

* Turned off the RPI3 build in the cmake flags and adjusted the paths to match my folders.

Can you please share, how to build for x86 👍