Heres my situation
I have a 2001 BMW 740i e38. I would like to keep the original display, but integrate a Raspberry Pi as the brains. I found a website that sells an interface that seems to take car of most of my needs.. http://pibus.info/index.html
Heres the question
Is there a way connect with my android via USB for music player, google maps, etc?
This is my first time trying a project of this magnitude, but I have been flashing devices since the HD2, so I do have the ability to at least follow step by step instructions with some mild trouble shooting.
Any help greatly appreciated.
PS
I also have an unused ATT Note II that would be really great to integrate into the system as a touch screen interface, maybe built into the armrest.
Thanks
Hello,
I have downloaded Android 5.1 lollipop image and installed on my raspberry pi2 board.
I have installed gapps, google play store etc. on it.
I want to test one application which requires camera, bluetooth and audio out.
I installed CameraFi app for testing my Logitech webcam but it didn't work out. Audio out is also not working. I have not tested bluetooth yet.
I did some changes in boot/config.txt like
#start_x Enable the camera module.
start_x=1
But after that board doesn't boot.
Is there any way or work around to enable Webcam on Raspberry Pi2 using Android OS.
Please help.
Thanks in advance.
Hallo,
I'm using a Raspberry PI in my 2001 BMW. I can connect my phone (S7 EDGE) via Bluetooth to stream music to the PI and listen in my car.
The PI also shows content played in KODI server on the NAV screen in the dash.
I'd like to use the raspberry in the future to run the headunit app and control the S7 directly.
So far I was able to install QT5.8 on the PI and to compile the 0.94 version from this source:
github.com/gartnera/headunit/
It is designed for Mazda cars but also has an Ubuntu Folder. When I start the compiled file, it gives me some errors.
Did anybody ever try to compile this for use with a Raspberry ?
Some update:
I was able to compile the version 0.94 and also headunit-master from the source i already gave.
Errors:
With 0.94 the app starts in the X Session but i get a data stream error from gstreamer.
With headunit-master version the X Session suddenly closes with error segmentation fault.
Did anyone else try to make it run on a Pi?
Hello,
I would like to announce my newest project called OpenAuto.
Donate
What is OpenAuto?
OpenAuto is an open source AndroidAuto(tm) headunit emulator application based on aasdk library and Qt libraries. Main goal is to run AndroidAuto(tm) on the RaspberryPI 3 board computer smoothly.
Demo video: https://www.youtube.com/watch?v=k9tKRqIkQs8
Status
Project is currently under beta testing.
Links and open source code
https://github.com/f1xpl/openauto
Features
480p, 720p and 1080p with 30 or 60 FPS
RaspberryPI 3 hardware acceleration support to decode video stream (video stream up to [email protected])
Audio playback from all audio channels (Media, System and Speech)
Audio input for voice commands
Touchscreen and buttons input
Bluetooth
Automatic launch after device hotplug
User-friendly settings
Supported platforms
Linux
RaspberryPI 3
Windows
Before you start using OpenAuto please read Readme and wiki page. Also check OpenAuto Pro.
Whoa, nice work. Would this also have a audio EQ/Crossover interface for the Pi?
Can you post a Windows binary build please? Thanks
Daved+ said:
Can you post a Windows binary build please? Thanks
Click to expand...
Click to collapse
Is this at least possible OP? Noobs here, Thanks in advance.
Will this work as standalone or does it need the app?
"Do not use while driving" Well where is the fun in that?
look like someone may able create Open AA instead and resolve blocking issue by google..i guess
Time to give my ride a sweet upgrade
Will raspberry survive high or low temperatures?
I'm trying to compile it, but I got a bit rusty in building under linux.
Code:
[ 6%] Building CXX object CMakeFiles/autoapp.dir/src/autoapp/Main.cpp.o
In file included repos/android-auto/openauto/src/autoapp/Main.cpp:19:0:
repos/android-auto/openauto/include/f1x/openauto/autoapp/USB/USBMain.hpp:22:40: fatal error: f1x/aasdk/USB/USBWrapper.hpp: No such file or directory
#include <f1x/aasdk/USB/USBWrapper.hpp>
Did I forget something when configuring with cmake?
f1x said:
Hello,
I would like to announce my newest project called OpenAuto.
Donate
What is OpenAuto?
OpenAuto is an open source AndroidAuto(tm) headunit emulator application based on aasdk library and Qt libraries. Main goal is to run AndroidAuto(tm) on the RaspberryPI 3 board computer smoothly.
Demo video: https://www.youtube.com/watch?v=k9tKRqIkQs8
Status
Project is currently under beta testing.
Links and open source code
https://github.com/f1xpl/openauto
Features
480p, 720p and 1080p with 30 or 60 FPS
RaspberryPI 3 hardware acceleration support to decode video stream (video stream up to [email protected])
Audio playback from all audio channels (Media, System and Speech)
Audio input for voice commands
Touchscreen and buttons input
Bluetooth
Automatic launch after device hotplug
User-friendly settings
Supported platforms
Linux
RaspberryPI 3
Windows
Before you start using OpenAuto please read Readme and wiki page.
Click to expand...
Click to collapse
Hi! First of all, thank you for bring us this post! Amazing I've the same question as another guy here, Could you post the Windows binaries or link to the step by step to get it running under windows?
Thanks a lot in advance!
Seriously impressive, great work.
Works perfectly on my Pixel 2/PI3.
Do you think it would be possible to get Android Auto Wireless functionality at a later point? Or does this require some specific wireless/bluetooth protocol that Google hasn't released just yet?
bluethoot
What can you do with the bluethoot feature ?
xbenjiiman said:
Seriously impressive, great work.
Works perfectly on my Pixel 2/PI3.
Click to expand...
Click to collapse
Thanks for your feedback. Great to see it working .
Zaf9670 said:
Do you think it would be possible to get Android Auto Wireless functionality at a later point? Or does this require some specific wireless/bluetooth protocol that Google hasn't released just yet?
Click to expand...
Click to collapse
I think it will be possible but needs some time and effort to implement it. OpenAuto is a hobbyist project and I cannot promise the exact deadline but this feature is on the TODO list.
brett1996 said:
What can you do with the bluethoot feature ?
Click to expand...
Click to collapse
What do you mean?
f1x said:
I think it will be possible but needs some time and effort to implement it. OpenAuto is a hobbyist project and I cannot promise the exact deadline but this feature is on the TODO list.
Click to expand...
Click to collapse
I wasn't sure how much of Android Auto is "open" to use. I haven't invested too much time looking into these forks like Auto and Wear but I know they're not quite as public as standard Android. At least that is the take I have gotten over the past few years.
Hopefully it's something that won't require some sort of specific hardware. Best of luck! I hope to test this out on my Pi 3 in a few weeks myself. I'll be sure to keep tabs on the project!
I promise I'm not one of those XDA ETA/update zombies.
Woohoo!! Thank you for this effort!
I'm curious which hardware, aside from the Pi, has been used successfully so far? Is that the Raspberry Pi Foundation touch display? Any HATs?
Thanks again!
-Chad
MasterCLC said:
Woohoo!! Thank you for this effort!
I'm curious which hardware, aside from the Pi, has been used successfully so far? Is that the Raspberry Pi Foundation touch display? Any HATs?
Thanks again!
-Chad
Click to expand...
Click to collapse
Only Raspberry PI 3 has been tested so far in case of embedded platforms. Code itself is portable for any Linux-based or Windows platforms. If hardware acceleration of video decoding is supported by underlying backend used in Qt multimedia library (GStreamer for Linux and DirectShow for Windows) then OpenAuto will run smoothly without additional effort. If hardware acceleration is not supported by underlying backends then it must be implemented in OpenAuto (like in case of Raspberry PI 3).
I apologize, I meant in addition to the Pi, not alternative platforms. Things like which screen is it that you've used, any HATs on your Pi, etc. ?
Thank you!
MasterCLC said:
I apologize, I meant in addition to the Pi, not alternative platforms. Things like which screen is it that you've used, any HATs on your Pi, etc. ?
Thank you!
Click to expand...
Click to collapse
Screen is the official one from PI Foundation (7''). Basically any screen should be suitable to run OpenAuto (as long as it is supported by the OS that hosts OpenAuto). The same for other hardware.
Dude! You're my hero, I've been playing around with so many ways to get this working, yours seems to be the perfect solution, I'll take it for a test drive tomorrow
Hi,
I'm currently building a Raspberry Pi (3) Android Auto project for my 55 year old Land Rover. I'm using Openauto installed on Raspbian (rather than using Crankshaft) so I can also add reversing cameras, ultrasonic sensors and so on, more easily.
Anyway, I the system so far:
RPi 3b running Raspbian Stretch
7" Touchscreen
USB soundcard with mic input.
It took a while but I finally configured the audio and it's working, at least Google Assistant and I think Navigation prompts (but it's difficult to assess that, the system isn't installed yet so it isn't going anywhere). The problem I am having is I can't get music at all. The music apps work, and I can use BBC iPlayer Radio no problem. I just can't get either Google Play Music or Pulsar working with locally stored files - There isn't any sound output at all. Mike input works, I tested the soundcard in Raspbian and it outputs audio now (after finding a guide and editing configs, it didn't work at first out of the box)
I'm not an expert on Linux or Android, I'm following guides so consider me a beginner if you would please! Also, if this has been covered before, I do apologise for bringing it up again, any and all help is very much appreciated. I also apologise if it is forum etiquette to introduce oneself before asking questions, I don't mean to be rude.
And here I was thinking the most difficult step would be figuring out how to mount/fit everything into the old bus...
Many thanks,
Ste