yashsingh1/xdaforums huggingface dataset:
[Connected Car] marcjero:
Yes look there : http://raspberrypi.stackexchange.com/questions/23094/calibrate-overscan-settings

Basically you can customize config.txt the way you want... (it's located on the first partition of the sd card)

Do you have any error message when starting rpiauto ? (before connecting the phone)
[Connected Car] Paladin0:
feedback

Sorry i should have remembered that i did that on the weekend...facepalm

Ok all good with that side. I login. run rpiauto, plug the phone in.

last error is Message overflows buffer

But nothing is coming up on the screen
[Connected Car] ceqface:
Buffer Overflow

I too am getting the buffer overflow with a Moto X G2 on Lolliop 5.1/RPi 1. App aborts to a command prompt.

I have been dreaming for this app. Keep up the awesome work.
[Connected Car] terrorgen:
Tested the latest image.

Three scenarios:

1. Buffer overflow

2. Buffer doesn't overflow, but no android auto video on HDMI output (tested composite output as well, nothing there)

3. rpiauto failed to put device into accessory mode.
[Connected Car] marcjero:
Ok if everyone is getting buffer overflow that's good sign : all devices behave the same....

I think that you get overflow because of broken decoder. Could you try to enter this command before running rpiauto ?

export LD_PRELOAD="/usr/lib/libEGL.so /usr/lib/libGLESv2.so"

Another tip : after a test, kill the rpiauto process (CTRL-C) then restart it again.

UPDATE : I uploaded a new image (https://drive.google.com/open?id=0B4clr3Un0RJTcGJSRlpVNmxaOVk) that includes a rpiauto.sh startup script. The script sets the LD_PRELOAD variable for you so you just have to run rpiauto.sh instead of rpiauto.
[Connected Car] terrorgen:
marcjero,

Just an idea:

make rpiauto quit on USB disconnect.

edit /etc/inittab and use 'respawn' to have Raspberry Pi auto launch rpiauto after startup and relaunch after it quits.

This way you won't have to deal with rpiauto 'works only the first time since launch' if you know what I mean.

Also, you don't need to deal with the login shell and root access can be disabled.
[Connected Car] marcjero:
This is a temporary issue and it will be fixed in the code itself. But as the code may change a lot until we get it fully working I didn't spend time to clean everything. I kept login shell for debugging purposes.

What is important for now : first display a picture and then capture input events.
[Connected Car] terrorgen:
Agreed. Like I said, just an idea :)
[Connected Car] marcjero:
Yes and it will be useful for the final release :)

What would really help a lot is to find a sample code of mouse/touch screen management in Raspberry PI (based on dIspmanx or eg, not xorg)l. I think I know how to get mouse events but I need to draw a pointer on top of the AA display.

Keep in mind that the pointer could be used if you install a trackball in your car. So it's not just for testing. Of course if you have a touch screen the cursor will be disabled.
[Connected Car] terrorgen:
I know QT has some libraries that draws directly to the framebuffer and would not need X in order to function. Raspberry Pi is supported as well.

If you are familiar with python I suggest that you give pygame a try. Pygame draws directly to the framebuffer as well. http://www.pygame.org/docs/ref/mouse.html
[Connected Car] ceqface:
Just loaded it and gave it a go - getting a MESSAGE BUFFER OVERFLOW error but it does open an android auto screen for a few seconds. Anything I can to do help log or debug?
[Connected Car] marcjero:
Do you mean you get the android auto welcome screen on the RPI ? I think you only get the screen on your phone correct ?
[Connected Car] ceqface:
Android auto opens on the phone, I get the initial android auto screen with the controls at the bottom, all black, then it dies. Never gets past that. But that is further then the last build!
[Connected Car] marcjero:
ok I got it... I think I have to go back to real time kernel to make the usb transport reliable again. What a mess !

I will do a new build tomorrow.
[Connected Car] Paladin0:
Input dev

cgit.freedesktop.org/~whot/evtest/tree/evtest.c

That link should have everything you need in terms of examples for using /dev/event

EDIT:

cursor can be drawn as a sprite using dispmanx’s hardware compositor, this has an example of drawing sprites onto a background layerhttps://github.com/AndrewFromMelbourne/raspidmx/blob/master/spriteview/spriteview.c
[Connected Car] terrorgen:
Just did this... still the same... see picture.
[Connected Car] marcjero:
I uploaded a new version with 1000hz kernel scheduler : https://drive.google.com/open?id=0B4clr3Un0RJTcGJSRlpVNmxaOVk

Please let me know if it solves the usb issues.
[Connected Car] terrorgen:
Loaded this new version just now.

I would say 60% of the times I got the buffer overflow error, which doesn't make sense to me since the packet received is smaller than the ones before it but the buffer doesn't like it.

35% of the time it loads the home screen of AA. Of course at this time I can't do anything with it yet.

5% of the time the program just stalled and I have to kill it by hitting Ctrl-C.

Sorry about the blurry and upside-down pictures!
[Connected Car] marcjero:
Hi, thank you for the feedback. I detect the overflow when the header I receive is incorrect. This means that some packets were drop somewhere... Nice pictures anyway :good:

Would you say that it works better with the 1000hz kernel ?

If yes I will rebuild the kernel with Real time patch + 1000hz scheduler..
[Connected Car] terrorgen:
Yes! I have never got this far before, so it is definitely beneficial.
[Connected Car] ceqface:
Goes about as far as the last build for me - I do see something get rendered and then the buffer overflow message. (Moto X Gen 2)
[Connected Car] marcjero:
Nice to know. It seems that things may change depending of phone hardware.

New image with RT PATCH and 1000 hz scheduler : https://drive.google.com/open?id=0B4clr3Un0RJTcGJSRlpVNmxaOVk

If you still have issues please try with your phone battery fully charged. We could have power issues here. Be sure that your PI power supply is ok.
[Connected Car] ceqface:
It goes about as far for me as the last image.. Still no go past a black screen with the 3 icons..
[Connected Car] ExTREmE99:
wow this is an awesome project. please do keep updating, as i'd love to get this working on the pi!!
[Connected Car] sandman01:
first attempt to get the prebuild image working with my Sony Xperia Z2 (latest Cyanogenmod)

set up config.txt to have hw decoding working (each attempt without it did not work)

need to get Android Auto apk manually because Google Playstore do not show it directly (AA version

login with pw: root

sh /usr/bin/rpiauto.sh > /dev/null

connect my mobile phone the usb autodetect displays a few lines about the usb device detected ==> seems ok to me

However the latest line semms to be from AA

usbfs: process 0 did not claim interface 0 before use
Segmentation Fault
#

tried it a few times also with different USB cables because it seems that the fist one has little connection problems when bent to much.

Anything else I can provide help here finding the issue

thanks so far for that amazing fast image that looks extremely interesting to me. :)

best regards

Mario
[Connected Car] marcjero:
Hi,

I'm nit sure to understand what the issue is. If you have failure during a test it's safer to reboot the PI to get a clean system again. Do you have an AA screen on the PI ?
[Connected Car] sandman01:
I'm on the same page :)

when start normally to see all the screen output I saw that a Android Auto GUI was displayed extremely short. (only a little flash on the screen)

also there is so much display output that I can not find if there is an error also, will try to redirect the output into a file to analyse it further

Android auto is starting automatically on my mobile phone but on the HDMI interface of the pi not really
[Connected Car] marcjero:
could you please try without any redirect ? I always got worse results with that.
[Connected Car] link3d:
same for me on Nexus 4.

I run rpiauto.sh and Android Auto GUI was displayed extremely short and nothing after. same for rpiauto wihout sh
[Connected Car] sandman01:
after a few attemps without redirect the output I saw the error message that is allready stated a few posts before:

RPI Auto : USB Message received with status 0
RPI Auto : !!!!!MESSAGE OVERFLOW BUFFER!!!!!!!
RPI Auto : AA message (channel = 15, flags=227, message_length=52431, total_length=-1) received

The looks really like a buffer overflow (-1), maybe in the receive buffer of the RPi

Takes some time because a new behaviour occured the last approaches.

Every time I try to start the binary and connect the device the RPi restarts.

At the beginning I thoungt it is because my phone was on 68% batterie, but now also on 100% it reboots a few times.

regards

Mario
[Connected Car] marcjero:
I think your power supply isn't powerful enough. This can make the RPI very unstable. And in our configuration the USB port is charging the phone so you really need a 2A power supply for this configuration.

---------- Post added at 08:43 PM ---------- Previous post was at 08:40 PM ----------

Thanks for these feedbacks. I didn't have a lot of time to work on it these days. I have to do more testings on my side. But USB seems to be very unstable that's very annoying. I think you really need to use a good quality usb cable and a good power supply to get a chance to have a reliable communication.
[Connected Car] sandman01:
thx for the hint, but I allready use 2A power supplies.

also tried 2 different ones.

but I'm able to test it also with a more powefull supply 5V/60A :D

only need to test if its stable enough in terms of the voltage ripple.
[Connected Car] Paladin0:
update

Any word on this project?
[Connected Car] Paladin0:
?

anything guys? im keen to help develop this
[Connected Car] mikereidis:
Nobody working on it AFAIK.

Can RasPi decode H.264 at 30 fps for 800x480 ?
[Connected Car] terrorgen:
mike,

Yes RPi can decode. I have run your test video on RPi and it works.
[Connected Car] mikereidis:
Then it's possible I guess.

I just re-noticed that this is a 9 page thread now. OP created this thread to "brainstorm" but AFAIR nobody has committed to do this and I don't want to spend time re-reading the thread to check.

I'd like to say that it's just a matter of someone porting my Headunit app code (but it is not).

It shouldn't be too hard to port/adapt my C code where most of the logic is, as well as interfaces to libssl, libusb and TCP sockets.

But my Android Java code would take some work to adapt (I would do this completely in C on a RPi). The main need here is APIs to the H.264 decoder and touchscreen input. Using Android makes this reasonably easy but I have no idea how hard it would be on RPi (except that touchscreen input is usually done via USB and shouldn't be too hard).

If there are no volunteers to do this, then there are no volunteers, and I only have plans for Android tablet support.

I'll add that the interest in Android Auto seems muted at this time. I've been away from this project for a few months and while there is some continued interest, it has been underwhelming.
[Connected Car] terrorgen:
I saw that some people are able to run Android Auto on an i.MX platform which Mazda's headunit is based on.

I have a vision of how the 'things' around the car would be centralized in this headunit, through wifi. I.e. the headunit will be a wireless router/bridge of sorts. The phone will be providing a means of accessing the outside world.
[Connected Car] mikereidis:
Wifi is NEVER* as good as wires, especially in the RF noisy environment of a car.

That's one reason our cars are filled with miles of cable.

It's also why Android Auto does not (yet ??) support Wifi. Apple announced wifi for CarPlay but I haven't heard that it's supported yet:

https://www.reddit.com/r/apple/comments/3qoch1/wireless_carplay/ ; I guess no hardware HUs support CarPlay Wifi yet.

(*NEVER: except for user convenience, it's only advantage.)
[Connected Car] terrorgen:
within a few meters I think it is still feasible. I set it up so wifi tethering on my phone is automatically turned on when I start my car. So far there aren't any complains...

If wifi is not working the major auto companies won't be cutting throats for in car wifi.
[Connected Car] nookbully:
In car WiFi has so many potential uses, it's practically inevitable that it will be in every car someday. Coupled with the coming 60GHz Wi-Fi speeds which will be 5 to 9 times faster than gigabit WiFi, and it makes even more sense.
[Connected Car] rewen:
There's a new board that might work better than the pi for this. I am going to back the project in hopes to one day use it in an Android Auto head unit.

https://www.kickstarter.com/projects/pine64/pine-a64-first-15-64-bit-single-board-super-comput

The + model would be the obvious candidate as it's got more RAM and built-in LCD and touch connectors.

Specs attached:
[Connected Car] mikereidis:
And that's the one they recommend for Android.

If it runs Android 5+ (5.1 for this board), supports USB host mode and can decode H.264, then it should run my Headunit app.
[Connected Car] sandman01:
Very interesssting.

However the the advantage would be that we could use the headunit app from xda when android runns directly.

I would also like to dig deeper into the code if someone could upload it.

Also I'm in search how a headunit shall work in detail (design requirements for the interface) but didn't find much information so far.

regards
[Connected Car] mikereidis:
https://github.com/mikereidis/headunit

If you're talking about Android Auto specs/docs all that stuff is secret, and only available to the "Tier 1" OEMs that are part of the so called "Open Automotive Alliance".
[Connected Car] sandman01:
Yes thats exactely what I mean.

I'm only a guy that want to understand how things are working together but reverse engineering is extremely complicated.

So where did you get all the infos to make your app.

Buy the way I allready fetched your github project, but didn't find the time to analyse it in more detail. :)

I'm currently working on many different projects in my spare time :D

regards

Mario
[Connected Car] mikereidis:
Painstakingly long reverse engineering.

Same way I made my FM apps; pretty much all of the information needed is locked away in documents that are almost impossible to obtain.
[Connected Car] sdra:
Brief summary

Apparently things started the good way by marcjero. He got a prototype working and shared a RPI image

which people could test. After the 25/10/2015 he disappeared and the conversation started from scratch like

no work was done at all. Probably cause nobody wants to read 9 pages of fruitful discussion... or cause THE guy

just disappeared and never come back.

Please take this into account when continuing this thread ;)
[Connected Car] joexner:
Motorcycle head-unit

I'm starting in on a project to build a rpi2-based headunit for my Honda Goldwing motorcycle, and just found this thread. The hardware details are here: https://redd.it/3ysqjs

I was thinking I'd just run the developer DHU app ( https://developer.android.com/training/auto/start/index.html#test-it-dhu ) on Linux on the pi, but maybe I'll try running Android and headunit!

P.S.: Sorry, XDA won't let me post real links because I'm new here.
[Connected Car] mikereidis:
For the DHU app on Linux, as you wrote on reddit, "it's pretty clunky".

I looked at it, and it seemed pretty slow, even on my x86 development PC, with a good deal more horsepower than Android devices. My guess is that Google wants it to be too slow to actually use in a car, while being just fast enough to allow app developers who can't afford/justify buying a $500 HU to use it for HU emulation.

Another issue is that it supports mouse, but not a touch-screen.

And, you have to start the HU server manually, then forward tcp ports via ADB.
[Connected Car] RocketChef:
I googled for rpi and android auto, found this thread and I'm sorry to see [MENTION=483738]marcjero[/MENTION] to disappear on this. I like the idea of an AA "client" for the pi because you can easily attach a CAN Bus adaptor to capture steering wheel controls. I would like to build a little setup to get this into my BMW CIC head unit using the rca out of the pi going to the rear view camera input and the iDrive controller for input (captured via CAN). Has anybody considered that there must be som kind of non-touch control for AA? Audi is using a similar controller for their head unit: https://www.youtube.com/watch?v=yxq7yJEnt-s so there would be no need for a real touch input.
[Connected Car] Y_Yan_C:
try this

guys, i have no knowledge on coding, but i hope this might help, its like pine64 but with a touch lcd attached

https://www.kickstarter.com/project...ouch-a-raspberry-pi-touch-stand?ref=discovery
[Connected Car] mikereidis:
Yes. Android Auto supports what they call "Rotary Controllers" and keyboard type input can be done this way as well. No traditional touch input is mandatory.
[Connected Car] rewen:
Interesting find. It's only a case, though. Not sure it will be applicable unless someone wants to mount one on top of their dash rather than in it.
[Connected Car] nintendo1889:
What about mounting a tablet with GPS support (samsung galaxy does). I've been wondering this for awhile, what's the cheapest tablet with GPS support? I know that there are gps units with bluetooth support, but I think they only are for sending contacts.

There's also a few different apps on the play store with bluetooth gps support.

Sorry, I didn't mean to hijack this thread.
[Connected Car] mikereidis:
IMO cheapest DECENT tablet is always Nexus 7, preferably 2013. $130-150 new now, cheaper used. Runs stock Marshmallow, easy root, tons of ROMs, and tons of experience installing and using in cars and Timur's kernel etc. works well in auto use, for stock 5.1 at least.

Anything cheaper is only possibly worth it if your time is worth less than $1-3 dollars an hour.
[Connected Car] sdra:
Btw, ODroid from Hardkernel boards look like they can fit the purpose as they run Android smoothly.

ODROID-C1+ (Raspberry like board) plus (7" multi touch screen) is a total of 92$.

Gps shouldn't be needed as would come from the phone in accessory mode.

Unfortunately bit out of the scope as this thread is supposed to talk about AA on Raspberry PI.
[Connected Car] youpie44:
Would be nice to have a multimedia central with Waze running... Hope it gets popular fast
[Connected Car] mikereidis:
Waze is claimed to be coming for Android Auto, but with no time estimates: http://xdaforums.com/android-auto/android-auto-general/waze-twitter-mentioned-android-auto-t3252801

Integration with Android Auto could be better than standalone usage.
[Connected Car] aisagi:
do you have this working for raspberry pi 3?
[Connected Car] marcjero:
nope I gave up to implement this on the PI because the usb hardware is not stable enough.
[Connected Car] a7x6kse6:
Could you post your source code so that we could try to continue your great work?
[Connected Car] mbt28:
Hi marcjero,

But is it smooth with normal X86 desktop computer?

Thanks
[Connected Car] arusiasotto:
Well, seeing this got me excited, as I had just bought a Raspberry Pi 3... Suppose I can put nougat on it and try Headunit..
[Connected Car] SaSa1983:
You could just use a Display, connect Rapsberry Pi to your AUX Input and install Android Auto 2.0.

It allows standalone usage.
[Connected Car] rewen:
This is a great step in the right direction. I hope they allow you to link your phone to another Android device running Auto 2.0 so that your calls can go through to it. Right now it's kind of gimped.
[Connected Car] bardzogrozny:
Hey,

I'd love to see this story going on. Here is a success story that maybe is usefull. Isn´t this project exactly what we´re talking about here?

https://www.raspberrypi.org/blog/the-carputer/

https://abartben.wordpress.com/2016/12/10/steering-wheel-commands-on-my-carputer/

check this out.

Cheers!
[Connected Car] HobbyCollector:
I don't think this is quite what most of us are looking for. Android head units have been available for a minute already but straight android head units don't have android auto capabilities which is the slick integration that at least I know I'm looking for
[Connected Car] Sabcoll:
I'll be going for a odroid c2.

It's higher in price, but completely supported of android 6.01 Marshmallow.

I like the RPI, i got 1 RPI B+, 1 RPI2 and 1 RPI Zero. But it's not practical for some ideas like a NAS or Car PC. There are better devices out there to use.
[Connected Car] spadival:
Hi. Has anyone tried compiling my version or A Gartners Ubuntu version of the code for rpi.

https://github.com/gartnera/headunit/tree/master/ubuntu

https://github.com/spadival/headunit/tree/master/ubuntu

Maybe I will buy an Rpi and try this. Any recommendations on the board and touchscreen? Should be cheaper than a decent 7 inch tablet.
[Connected Car] kryptur:
Hi, I just tried to compile this on an RPi3-B (1GB).

It's a bit complicated - There were several dependency issues and now I stuck with hundrets of "undefined reference to `google::protobuf::internal::XXXXX`" errors and the build fails.

Any suggestions on how to fix this?
[Connected Car] Android0032:
Hi guys, maybe a little off topic regarding the current development but still related to the goal.

What if you install Marshmallow on the RP, install and run Android Auto, connect it to a Android Auto compatible car via USB so you can use the in-car display, feed your RP with your mobile wifi tethering data ... if working you have "Android Auto Wireless", no ?

Then you just keep the PI permanently in the car and the mobile can stay in your pocket.
[Connected Car] f1x:
I see that topic is quite old but maybe you are still interested in how to run AndroidAuto on the Raspberry PI. I am developing a project called OpenAuto. OpenAuto is AndroidAuto head unit emulator capable to run Android Auto projection even at 1080p@60 on the Raspberry PI 3 Hardware. Features like voice command or bluetooth work as well. Here is the link to the project on GitHub. At the project wiki you can find instructions how to build OpenAuto for the Raspberry PI 3.
[Connected Car] marcjero:
Hi f1x,

congrats for your impressive job ! I'm glad someone was able to achieve this. Did you have any issue with usb ? I was not able to get reliable usb messaging with RPI 1. RPI 3 is probably a much better choice..

Cheers
[Connected Car] f1x:
Hi,

thank you. Actually I did not try to run OpenAuto on the RPI 1. In theory it should be possible but may require some adjustments of OMX video streaming. Also it could be an issue with compiling OpenAuto directly on the RPI due to less amount of RAM memory - some toolchain setup for cross compiling would be needed in this case. I think RPI 3 is the best choice (among RPIs) to run OpenAuto.
[Connected Car] benjamimgois:
Impressive work man ! Congratulations. Is it possible to run it on a rpi2 ? I have a couple rpi2 laying around and would love to use it for openauto.
[LG G Watch R] haribolman:
Hi,

I've been using my watch well since I bought it late last year.

The latest software update was installed 2 days ago and I am no longer able to get the watch to respond to ANY screen touch at all! It will only respond to the crown button!

I am unable to do anything other than turn it on or off!

I let the battery run flat and then recharged it, but it remains the same!

Any ideas?