Hardware Compatibility List
htruong opened this issue · 179 comments
Please comment here devices that are known to work and not work. Specifically:
- Phone
- Raspberry Pi version/hardware.
- Any customization done to the distro.
- If it doesn't work, have you tried with other USB cables?
For people using custom HDMI touch screens, please try Starting Crankshaft in X11 mode on image 2018-03-10 or later.
There is very likely that OpenAuto will work with your phone regardless of whether Crankshaft works or not. If Crankshaft does not work for you yet, there is a big chance that if you know how to compile OpenAuto yourself, it will work.
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
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.
For people using custom HDMI screens, please try Starting Crankshaft in X11 compatibility mode on image 2018-03-05 or later.
@htruong is there any hope for the Adafruit AR1100 touch controller or other touch controller in the near future? I'm hoping to add a touch overlay and HDMI to RCA converter to my Pontiac G8 factory radio for a really clean installation,
@tehniemer I no longer have the ar110 touch controller to test. Do you have one available to test with X11 mode?
Samsung Galaxy S8 + Crankshaft v0.1.6 works fine.
Pi 3 model B / Official 7" screen.
Tested / Works*
- LG Nexus 5 / Android 7.1.2
- Dell U3415W (HDMI)
- Image 0.1.6
*The display works fine without using X11 mode, but since the screen is not touch enabled I cannot confirm full functionality.
@kfechter so you did get it to work with the note 8? What did you have to do?
Tested / works (update to works)
- Pixel 1
- pi 3
- image 2018-03-05
- ebay 7 Inch TFT LCD Touchscreen + Driver HDMI VGA w/ backup camera
Touchscreen is eGalax. And the y-axis is flipped and setting the inverty option causes autoapp to crash. This has been resolved in issue #18.
@Xseam @ubergeekseven I ended up installing normal raspian and compiling the aasdk and OpenAuto projects manually. everything seemed to work after that. I haven't tried to install a new crankshaft image since I got it working.
Tested / Works:
Google Pixel 2, Android 8.1.0
Raspberry Pi 3B, Official touchscreen.
Image 0.1.6 2018-03-05
Tested / Works:
- Samsung Galaxy S7 Edge, Android 7.0
- Raspberry Pi 3B, Official Touchscreen v1. 0
- Image 0.16 (2018-03-05)
Tested / Works:
- OnePlus 5T, Android 8.0
- Raspberry Pi 3B, Official touchscreen.
- Image 0.1.6 (2018-03-05)
Tested / Works:
OnePlus 2, Android 7.1.2
OS: LineageOS 14.1, Build from 10/2017
Kernel (Phone): Boeffla-Kernel-6.1-beta8 (custom built with alternative charging drivers)
Raspberry Pi 3B, Official touchscreen.
Image 0.1.6 (2018-03-05)
Tested / Works:
MotoZPlay, Android 7.0
Raspberry Pi 3B, Official Touchscreen v1. 0
Image 0.16 (2018-03-05)
Tested / Works
Google Pixel 2, Android Oreo 8.1
Raspberry Pi 3B, Official touchscreen.
Image 2018-02-28
Google Pixel 2, Android Oreo 8.1
Raspberry Pi 3B, Official touchscreen.
Image 2018-03-10
Tested / Not Working
Google Pixel 1 XL, Android Oreo 8.1
Raspberry Pi 3B, Official touchscreen.
Image 2018-02-28
Google Pixel 1 XL, Android Oreo 8.1
Raspberry Pi 3B, Official touchscreen.
Image 2018-03-10
Both scenarios produce the same result. The Pi boots and gets the the "waiting" screen.
(NOTE: the 03-10 has a very different waiting screen)
When the Pixel is plugged in, the Pixel reacts, showing "Welcome to Android Auto", offering two choices:
- NO THANKS
- GET STARTED
On either build, when I choose "GET STARTED", the Pixel returns to its desktop screen. Nothing else happens. The Pi does not react at all when the phone is connected.
Pixel 1 XL
Android version 8.1.0
Kernel version 3.18.70-g0de8712 (Wed Jan 17 18:39:52)
Build number OPM1.171019.021
Android security patch level March 5, 2018
@bhwithun Do you mind trying with another USB cable? The Pixel has to be one of the most thoroughly tested devices - I have a Pixel 1 myself. The "plug phone in" screen is OK, it changed quite a bit between version.
Perhaps trying to remove and reinstall Android Auto too?
TESTED WORKING!
LG G4 Running H-Rom V20 PORT V2.2 (Android 7.0))
Kernel version 3.10.84
Android security patch level July 1,2017
Raspberry Pi 3B
Raspberry Pi 3B, Official touchscreen.
Image 2018-03-05
Everything working flawlessly; THANK YOU!
Tested work with
- RPi 3
- Waveshare 5inch screen (must enter dev mode to edit screen resolution and touch driver)
- Moto Z Play (XT1635-02)
Re-Tested
I tried the Pixel 1 again. Same results. I have tried 2 different USB C cables. The same cables that do not work with my Pixel 1 XL work fine with my Pixel 2.
Plugging in the Pixel 2 has worked 11 out of 11 times.
Plugging in the Pixel 1 has worked 0 out of 15 times.
Drive Test
I did a brief couple of road tests today.
Raspberry Pi 3 - Model B - ARMv8 with 1G RAM (powered by dedicated RavPower Turbo-Series 2.4A)
Pi Foundation Display - 7" Touchscreen Display for Raspberry Pi (powered by dedicated Anker IQ)
Jabra 510 Speaker (USB connected/powered by RPi)
Google Pixel 2 (8.1.0)
My RPi was showing the "lightning bolt" icon almost constantly. I'm not sure why it would be experiencing underpower, but apparently it was.
Navigation Only
The navigation worked fine, the audio also worked fine. No issues.
Music Only
Listening to music worked fine, no issues.
Music + Nav + Map
After selecting a destination and beginning navigation, I chose some music to listen to. The music began fine, but it was pretty clear that the audio was affected by the graphical navigation. When the map is zooming or panning, the audio gets choppy.
When the navigation voice begins speaking, the music audio gets considerably worse. After making one left turn, the music remained choppy and laggy (it was painfully unlistenable) for almost a full minute. It did eventually recover and sound like music again after that minute.
Music + Nav
After a while I changed the display so that I was no longer looking at the map. I chose the music screen. The audio and the navigator voice worked much better this way. Maybe the RPi just doesn't have enough power to do music + navigation + maps.
I noticed that the display changed song titles about 1 minute before the song ended. I don't think that's normal. I think the on-screen song title is supposed to always reflect exactly what I'm listening to.
While I was looking at the music screen I did notice that the periodic instructions from the navigator would produce a "pop-up" banner at the top of the screen, telling me about the upcoming turn. These pop-ups were very well coordinated with the navigator voice.
Music Fade
I noticed that the music would fade periodically. This sounded like the decreased-volume that would be associated with navigation voice saying something, but the music fade was not coordinated with the navigators voice. Sometimes it was, but usually it was not. Sometimes the navigator spoke while the music was full volume, and sometimes the navigator spoke while the music volume was decreased.
End-of-Trip
After reaching my destination I noticed that the music still faded (lowered its volume) periodically. The navigation was certainly not active at this time, so I'm not sure why the music volume would be reduced at all, but it continued to do so. Maybe that lightning bolt on the screen is relevant. Maybe my system is chronically underpowered.
I disconnected the Pixel 2 and the display returned to the "waiting for connection" screen (3/10/2018 build). I pushed the power icon. I think this normally shuts down the system. This time it did not shutdown. Instead, I was shown the terminal and all the "[ OK ] Started LSB: Switch to ondemand cpu governor ..." kinds of messages. I seem to recall seeing these before as the system was shutting down, but this time they stayed, along with these other messages
[ 76.951557] Under-voltage detected! (0x00050005)
[ 83.191573] Under-voltage detected! (0x00050005)
[ 112.311574] Under-voltage detected! (0x00050005)
[ 126.871557] Under-voltage detected! (0x00050005)
- Pixel 2 XL
- Android 8.1.0
- Official 7" Touchscreen
- Raspberry Pi 3B
- Versions:
- 0.1.6 2018-03-05: ✓
- 0.1.7 2018-03-10: ✓
- 0.2.0 2018-03-13: ✓
Notes:
- USB Y-connector has solved power issues.
Still getting "Under-voltage detected!" as USB adapter only outputs 2.4A but that should be resolved with Y connector
@bhwithun Thanks for the detailed report. The audio should no longer jank with the latest release :) Enjoy
Tested / Works
Pixel 2 / Android 8.1.0
0.2.0 / 2018-03-13
Raspberry Pi 3B
Official 7" Touchscreen
Tested / Not Working
Pixel 1 XL / Android 8.1.0
0.2.0 / 2018-03-13
Raspberry Pi 3B
Official 7" Touchscreen
Developer says that this works with Pixel 1 XL, and I'm inclined to believe that, but it's not working with mine. Are there steps I can take to troubleshoot this? I have un/reinstalled Android Auto. AA actually works fine on my phone as a stand-alone, but when connected to the Pi, it's not working. The Pi doesn't acknowledge that a Pixel 1 XL has been plugged in.
When I unplug the Pixel 1 XL and plug in a Pixel 2 it works perfectly. (The music/nav voice problems seem to be gone). I trust the cable, the Pi, the Screen, the power source. The one variable I cannot change is my Pixel 1 XL. I only have one of them. It's nothing weird. Not rooted. Not hacked. Not jailbroken -- if those terms even apply to the Pixel phones.
Here's a pic for fun. I've drawn the USB cable in to show how that it's connected.
The Raspberry Pi is flat-out ignoring my Pixel 1 XL.
Tested with Makibes 7 inch touch Screen ( https://www.amazon.co.uk/Makibes-Capacitive-1024X600-Resolution-Raspberry/dp/B01AW8POBE/ref=sr_1_1_sspa?ie=UTF8&qid=1521136451&sr=8-1-spons&keywords=makibes+7+inch+capacitive+touch+screen&psc=1 ) and Leagoo S8.
Just followed this tutorial: https://www.youtube.com/watch?v=Q9gHsR4foLM with the 13th of March release.
Only issue is that I can't get voice by bluetooth speaker or by my phone.
I can say 'Ok Google' and shows speech recognizer, but not recognizes my voice/anything.
Thank you for your efforts!
Greets from Spain.
Tested/working
LG V30 (included usb-c cord)
Pi 3b
Version alpha0.2.0 2018-03-13
w/ Official display
Edit: Have not tested "OK Google" yet.
Tested without touchscreen: Working
One Plus 3 (USB C cable from amazon - not official)
Pi 3b+
Version: 2018-03-13
Display: Lg 23in HDMI monitor no touchscreen
Ok google works.
Didn't try bluetooth.
Tested / Works
LG Nexus 5x / Android 8.1.0
HP Pavilion 23xi display
Image 0.2.0
Tested working:
HTC 10 Android Oreo 8.0
Raspberry Pi 3B, Official touchscreen.
Image 2018-03-13.
Tested not fully working but with workaround:
Sound Blaster Play! 2 external USB sound card. Filed https://github.com/htruong/crankshaft/issues/50
Phones: Pixel XL 1, Nexus 5
Raspberry Pi 2B
Raspbian Stretch Lite, manually compiled aasdk and openauto.
CannaKit power adapter
Initially neither phone worked. After connecting either, openauto would not respond in any way. dmesg would show that the Pis detected both phones, but the app would only sit waiting. I tried stopping Android Auto on the Pixel, deleting its cache and data, then reinstalling, but that had no effect. I also tried plugging each phone into a USB hub and the hub into the Pi.
I ran rpi-update to pull the latest firmware, and everything worked after the reboot.
Tested/Working
Phone: Asus Zenfone 3 Laser
Android:7.1
Raspberry Pi 3B
Image:2018-03-13
Custom Touchscreen: CTF 800 wmsl (www.cartft.com)
USB DAC (soundcard):Hiresfi usb dac 5122A
To get the HDMI Output to 800x480 vga Resolution I have edited config.txt:
disable_overscan=1
hdmi_force_hotplug=1
hdmi_group=2
hdmi_mode=87
#set specivic CVT mode
hdmi_cvt 800 480 60 6 0 0 0
config_hdmi_boost=4
Tested/Working
Phone: Xiaomi redmi Note 4X
Rom: Pixel Experience
Android: 8.1
Raspberry Pi 3B
Image: 2018-03-13
Generic HDMI Display 6.5" (V59.AV2 controller + AT065TN14 + touch panel)
Touch: eGalax generic controller
To get the HDMI Output to 800x480 I have edited config.txt:
hdmi_group=2
hdmi_mode=1
hdmi_mode=87
hdmi_drive=1
hdmi_cvt 800 480 60
I had the y flip touch problem, i resolved using X11 mode and xinput_calibrator on raspbian and copying the calibration result.
It's not necessary use: option "InvertY" "1"
And now i have a better precision input of the touch and correct Y.
This is my 99-configuration.conf :
Section "InputClass"
Identifier "calibration"
MatchProduct "eGalax Inc. USB TouchController"
Option "calibration" "80 1960 1880 160"
EndSection
Tested/Working
Phone: Nexus 5
Android: Lineage 14.1
Raspberry Pi 3B
Image: 0.2.0
Custom Touchscreen: Pontiac G8 factory infotainment (RCA no HDMI), touch overlay, Adafruit AR1100 touch controller (eGalax also works)
X11 mode w/ xinput_calibrator on raspbian and copying the calibration result.
I was able to calibrate the AR1100 by installing Jessie and https://github.com/tom-2015/rpi-AR1100 on a second SD card, much better results than using xinput_calibrator since the settings are saved on the AR1100
Tested/working
Phone: OnePlus 5T running Oreo8.1
Raspberry Pi 3B
Custom 1024 X 600 Touchscreen from Aliexpress running from hdmi port with the config.txt file modified wit the following text
hdmi_force_hotplug=1
hdmi_group=2
hdmi_mode=1
hdmi_mode=87
hdmi_cvt 1024 600 60 6 0 0 0
hdmi_drive=1
Tested /Works:
- Motorola Z2Play (XT1710-09/Android 7.1.1)
- RPI 3B, Playstation Eye (for the mic array), Samsung TV P2770HD in X11mode
- crankshaft-2018-04-01-1.zip / Android Auto 3.1.581053
btw: the Playstation Eye might be a very cheap but excellent noisecancelling mic according to:
https://medium.com/snips-ai/benchmarking-microphone-arrays-respeaker-conexant-microsemi-acuedge-matrix-creator-minidsp-950de8876fda
(and in the future maybe a dashcam too? ;)
Tested /Works (with repairs)
- Xiaomi Mi6 Android 8.0.0.0
- Raspberry pi 1 model B (26 + 8 GPIO) LG Smart TV
- Crankshaft-2018-04-01-1
First time boots flawlesly but when I connect the phone is detected but nothing shows up and the pi gets stucked.
You need to run raspi-config and set the video memory to 256 (64 is the default)
@fcox Great insight. I will look at the GPU mem config to see if that helps the issue of Pi getting stuck anymore. Awesome!
@htruong Nice. Maybe for better compatibility change the x11/rotate pinout to another (only if is possible)
Tested/working
Phone: OnePlus 5T running Oreo8.1
Raspberry Pi 2B
Everything works OOB. I had some USB connection issues with the phone where it would disconnect and reconnect multiple times per second, but I just switched ports to gain stability. Also, I'm getting a "pop" noise before every Google Assistant reply using the audio jack, but playing music/podcasts is fine. I can't remember if this was an issue with version <2018-04-01.
Thanks for this!
Hello everyone, this is a great project !
My use case: I have a car with no touch screen and not intending adding one more. How can I help to enable mouse support into crankshaft ? It seems to be a known issue with X11, my question has it been any workaround or solution available or is it X11 limitation which will never get solved.... Many thanks !
Tested/working
Xiaomi Redmi Note 4 (Snapdragon)
Raspberry Pi 3B, Official touchscreen
crankshaft 0.2.2 2018-04-07
-config.txt
max_usb_current=1 (to avoid Error 2 - Thats work for me)
Tested, and can confirm works:
- OnePlus 3T, Oreo 8.0.0.
- Raspberry Pi 3, Official touchscreen.
- Crankshaft 0.2.2.
Will keep this comment updated as I go along. Haven't experienced a single issue, and works with the audio options turned off. UK Crankshafters be advised that you might be at risk of violating the law (Penalties section, paragraph 2) if you mount this on your dash.
Tested / Works:
Note 8 SM-N950U1 Android 8.0
Raspberry Pi 3B+, Element 14 7" Pi Touchscreen LCD Display
Image 2018-04-07
worked right out of the box, no issues. i did the standard "lcd_rotate=2" to the config.txt file to flip the screen image 180
*note: my phone is in developer mode, android auto is not.
Pixel 1 XL Oreo
Pi 3B & Official 7in Touch Screen
Roccat Juke USB DAC for better sound quality.
Tested / Works:
- Nexus 5x
- HiFiBerry DAC+
- RPi3 / Official 7" Touchscreen
- MoPower UPS (great for a car enviornment! disabled power options in crankshaft)
- Panda PBU40 Bluetooth Adapter (A2DP and HFP working)
- aitesco USB Microphone
- Joycon EXR (steering wheel controls, replicates keyboard presses & EASY to program - plug&play)
(Note: Joycon PJexc or EXC would also likely work, I already had the older EXR.)
I used to have a Nexus 7 mounted in the car with a custom build (timur's kernel) for years. I already prefer the simplicity and ease of this. HiFiBerry sound quality is very good, less tinkering.
RP3 B
Samsung S7 edge (nougat)
Aliexpress 3.5inch touchscreen display (GPIO) https://www.aliexpress.com/item/NEW-Raspberry-Pi-3-Starter-Kit-Raspberry-Pi-3-Model-B-3-5-inch-Touchscreen-16G/32806241356.html?spm=a2g0s.9042311.0.0.YsdoFE
not working - only white screen on boot up
X11 did not change behavior
tried using my LG tv (HDMI) instead and see picture but won't display AA when connecting cell phone (phone indicates it is in auto mode)
Does anyone know how can I configure the config.txt file to enable my screen?
Thanks in advance guys!
Adding to my original post, I have figured out how to modify the official raspberry pi 7 inch touchscreen so that you can power it over HDMI. I used the Arducam CSI to HDMI cable extension module with 15 pin 60mm FPC cable. This way I was able to install the raspberry pi inside my armrest console and run an HDMI to the dash where I have the touchscreen mounted. I used the official raspberry pi touchscreen case, but cut the back off of it and was able to use a CD player mount tablet holder. You need to solder 1 wire from pin A on the extension module to 5V on the pi GPIO. At the touch screen side you solder 1 wire from pin a to 5V and 1 wire from Gnd to Gnd on the touchscreen.
@sensei221 the version of OpenAuto we're bundling with Crankshaft has had troubles projecting to the screen lately. I wish to release another version by this weekend to see if the situation improves.
Any test with a pi zero ?
@CorentinDy - Pi Zero should work, if you use a screen that works with it (official screen won't work), and pipe audio through Bluetooth.
Tested / Works:
-
Samsung S7 edge -
Justboom DAC -
RPi3 / 7" Waveshare Touchscreen
Tested/Working
RPi 3
Nokia 6 (8.0)
5'' Waveshare Touchscreen
Got this setup working thanks to reddit user elCaampi
Add this to the config:
max_usb_current=1
hdmi_group=2
hdmi_mode=87
hdmi_cvt 800 480 60 6 0 0 0
hdmi_drive=1
Then touchscreen drivers from waveshare: https://www.waveshare.com/w/upload/3/34/LCD-show-180331.tar.gz - Place on the boot partition. Enable Dev mode
Boot pi and enter:
tar xzvf /boot/LCD-show-*.tar.gz
cd LCD-show/
chmod +x LCD5-show
./LCD5-show
Remember to disable Dev once your done
Tested/Working
RPI 3 B+
Samsung Galaxy Note 8 SM-N950U (Sprint)
Android 8.0.0
7" Official Raspberry Pi Touch Screen
Looking to integrate some GPIO items but for now it works. Only issue I have is the phone seems to trickle drain. Going to be testing a USB Y splitter to see if I can inject added charging to Phone while communicating to device.
@Archer1632 is something like this a possibility? it's what i'm using
https://www.amazon.com/gp/product/B079L64V2N/ref=oh_aui_search_detailpage?ie=UTF8&psc=1
i'm not sure you'll be able to provide enough charge for the note 8 from the pi 3
@SmellsLikeMI negative... that was the first thing I tested, with my own wireless charger. The Note is "smart" enough to not charge and have the phone plugged in at the same time... Unless you know of a work around, since the phone has to be plugged into the Pi to communicate with Crankshaft.
Tested working:
HTC U11 Android 8.0
Raspberry Pi 3B+, Official touchscreen.
Image 2018-04-18.
Works like a charm, also including USB audio adapter.
But only stock USB-C cable works... So indeed cable sensitive.
@Archer1632 the Note 8 can wireless charge and and be plugged into the pi at the same time. I've been running mine like that for a month now. No special settings, workarounds or cables. It works with factory or aftermarket cables. Even micro-USB to USB-C converters.
@SmellsLikeMI I stand corrected... My initial test was performed incorrectly. I attempted to use wireless charging and had it plugged into the charger too. Note preferred the hard wire over the wireless. Obviously no options as to what USB connection was for. Thanks for the heads up on the wireless charger for car.
Tested / Works:
Google Pixel 1 XL, Android P Public Beta 2
Google Nexus 5X, Android Oreo 8.1 with May security patch
HTC 10, Android Oreo 8.0 with February security patch
HTC One M9, Android Nougat 7.1
Raspberry Pi 3B, Official touchscreen.
Image 18-05-2018
One slight problem with the setup is the navigation audio is sometimes janky and will pop on high frequency sound. The music is completely fine, and I have used two power cords to supply power to the Pi. This is present on two of the devices that I've tested and does not present on the HTC 10. This is a Raspberry Pi power delivery problem and can be solved by changing a power supply, I'm currently using this
By the way I used two cords, one for the display and one for the Pi
Tested / Works:
Google Moto X4 Android Oreo 8.0
Raspberry Pi 3B, Official touchscreen.
Image 2018-05-18.
Tested / DOES NOT WORK:
Google Moto X4 Android Oreo 8.1.0
Raspberry Pi 3B, Official touchscreen.
Image 2018-05-18.
Working:
Samsung Galaxy A5 (2017), Andriod 7.0
Raspberry Pi 1 B+
Image 2018-05-18
Hi,
Does it work with symbian belle car mode with mirrorlink?
There are some head units which support android & symbian at the same time like the following example
http://www3.jvckenwood.com/english/car/mirrorlink/
Phone: Nokia 8 8.1
Raspberry Pi version/hardware: Pi3 - Raspberry Pi Screen
Any customization done to the distro: None - 0.2.4 2018-05-18
Tested / Working:
- Samsung Galaxy S8 (Stock, Android 8)
- Raspberry Pi 3 B+
- Image 2018-05-18
Currently not working:
- First Gen Raspberry Pi B on AOC Q3279VWF 1440p Monitor
- Image 2018-05-18
Raspberry Pi boots from SD card and sits at Crankshaft splash screen, never get prompted to plug phone in. Happens in both display modes on the AOC Q3279VWF monitor
Edit to add: Works perfectly if OpenAuto is compiled from source, so it's a crankshaft-specific issue
Tested / Works:
- Samsung Galaxy S7 Oreo 8.0.0
- Raspberry Pi 3B
- Image 2018-05-18
- X11 Mode Enabled
- 6.5" 4 Wire Resistive Touchscreen Overlay
- Adafruit AR1100 Touchscreen Controller in USB Mouse mode
- HDMI Group 1, Mode 3 output
- Pi-Powered HDMI to Composite Converter
- Custom negative overscan to fit the screen
Occasional incompatibility error, but very rare
Not working, sadly
- Moto Z2 Play, Android 7.1.1
- Raspberry Pi 3B+, official Touchscreen
- Crankshaft Openauto 0.2.4 2018-05-18
- Crankshaft Openauto 0.2.2 2018-04-07
- Crankshaft Openauto 0.1.7 2018-03-10
I had this working 6 weeks ago, comes time to box this to put in the car, I flash 05-18 and have this problem:
- Crankshaft starts as expected.
- Android Auto tries to start and gets stuck on a grey page or gets me an error message. It does tell me I am connected to a car but that's it.
- Crankshaft screen does not change.
I have tried different images but get the same problem
I have turned on/off developer mode and USB debug modes
I have also tried different USB cables
I do not know how to compile and could not find straightforward instructions so have not tried that
Any input/suggestion is more than welcome
Galaxy S7 Edge not working
Phone says incompatible
Galaxy S7 Edge Oreo
crankshaft ALPHA 0.2.4
rpi 3 B
Geekpi 7 inch 1024x600 touch screen
https://www.amazon.com/GeeekPi-Screen-Display-Monitor-Raspberry/dp/B01L6YXZLY
X11 On
it appears my resolution had something to do with it?
I have forced my touchscreen to 800x480 and it seems happy.
Now if I can get my touchscreen to work with crankshaft I will be good (works fine with x)
I got the touchscreen working by using this as a reference
#64
@pat-ricochet Which software and hardware combo?
Tested / Works:
Moto X Play
Rpi 3 + Waveshare 5''
Crankshaft Openauto 0.2.4 2018-05-18
Plus:
Motion streaming from USB Grabber/USB camera and Omxplayer for AV Backup camera
Tested / Works:
Note 8 (unlocked) SM-N950U1 Android 8.0
Raspberry Pi 3B+, Element 14 7" Pi Touchscreen LCD Display
Image 2018-07-13
Working
HTC One M9
Android 7.0
Raspberry Pi 3 B+
Official 7" Screen
Image 2018-07-13
*Bluetooth not working
Partially works:
- Pixel, Android P
- Rpi 3 B+
- Waveshare 7inch HDMI LCD (B) (Rev 2.1, HID touch screen)
- Crankshaft 2018-07-13
Display does not correctly shut off when suspend timeout is reached.