Related
After mainly lurking on the forums for a while, I decided to embark on a Nexus 7 Installation as I wanted to have to same features found in newer vehicles in my 2000 Mazda Protege. The only problem is I didn't want a permanent installation and didn't find previous posts to be complete enough other than to get some ideas from. I didn't like the fixed installation because the screen in most setups doesn't face the driver and doesn't appear to be useful. In addition, I wanted to be able to remove it especially in the summer when conditions in the car may be dangerous to the device itself.
The goal of this post is to give very detailed account of the setup up, how it works, and what my future plans for improvement are. I would also like to try and answer as many questions as possible for people considering doing the same with their own devices.
Video
First off, we'll start with a quick video of the installation in action. It may seem a little low in volume in the video but all of the sounds and music are playing through the car's speakers. As such, you can make it as loud as anyone could possible want.
Pictures
First up is the view from about where the driver would see. In reality, the steering wheel does not obstruct the screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Next is where the hub is currently placed. I don't yet want it completely hidden because the signal strength is displayed on the freedompop stick. It can be pushed down and out of sight from here.
And the hub in all its glory.
This is the view from the back where you can see the fish eye lens protruding from the trunk lid.
And now with the lens removed. Its still unfinished but I wanted to get a working prototype. I just need to sand down and seal the opening to prevent rust.
The MIMO antenna for data connection is just attached to the passenger's headrest for now. The wires are pretty short so it may end up staying here for now.
The FM antenna is currently placed in the back by the rear window. I live pretty far from the station so I needed something bigger for a clean signal.
A view of the power inverter. The hub takes up the plug while the Nexus is powered via the USB port.
And finally, a diagram showing the buttons of the bluetooth remote and what they do.
Hardware
Here is a complete list of all of the main hardware used.
Nexus 7 1st Gen
PAC Ground Loop Isolator
VicTsing Magnetic Detachable Fish-Eye Lens
RTL-SDR, FM+DAB, DVB-T USB Stick Set with RTL2832U & R820T
Satechi ST-TP01 Car Holder Mount for 5" - 10" Smartphones & Tablets
AmazonBasics USB 2.0 A-Male to A-Female Extension Cable (9.8 Feet/3.0 Meters)
ScanTool 426101 OBDLink MX Bluetooth/OBD-II Scan Tool Interface
DVB-T TV Turner to RF TV Antenna Coaxial Cable Adapter
Satechi Bluetooth Multi-Media Remote
NETGEAR 6000450 MIMO Antenna with 2 TS-9 Connectors
Freedom Stick Bolt 4G USB Modem
Logitech HD Webcam with Fluid Crystal Technology, C270
AmazonBasics USB 2.0 4-Port Ultra Mini Hub (NOT CURRENTLY USED)
PowerGen 4.2Amps / 20W Dual USB Car charger (NOT CURRENTLY USED)
Schumacher XI14 Power Inverter
Rosewill RHUB-300 USB 2.0 Hub 7-Port HUB With Power Adapter
Amplified AM/FM Antenna
GE Passive Antenna
European-TV Adapter
Micro USB Host OTG Cable + USB power
Software
Here is the complete list of the major software components used in this installation.
USB ROM for Nexus 7 with Timur’s Kernel
Webcam Hotswapping by redeyedjedi
SDR Touch
Torque Pro
Backup Cam (Mirror)
Tasker
Spotify
iHeartRadio
External Keyboard Helper Pro
Assistant Event for Tasker
Hardware Set Up
The Nexus 7 is mounted on the dash with the tablet mount, facing the driver. Its placement allows for easy viewing while not obstructing vision. From there, a 3.5mm audio cable runs for the headphone jack out into a PAC Ground Loop Isolator to eliminate the alternate whine and other electrical interference. This finally plugs into the AUX input of a cheap aftermarket radio I installed to replace the stock.
Coming out of the micro usb port is a Micro USB OTG Cable with power which connects to a powered USB Hub. The hub and device are powered by a 12V Power inverter. Everything should be able to be powered just through the OTG cable but I was having some charging issues early on which I rectified by disabling some apps from logging and constantly using the GPS but I kept the setup as it worked well.
On the hub are the Freedompop Bolt, RTL2832U dongle, and USB extension. The Freedompop Bolt I got a deal on over the summer which gives me a gig of free data every month which the Nexus used for its primary data connection. The signal strength can vary pretty dramatically out in NC where I am so I also installed a MIMO Antenna to improve reception and also have cell tethering as a backup in a pinch. The RTL2832U dongle is connected to the passive antenna for better FM reception which required some adapters listed in the Hardware Section. The USB extension cable runs from the dash, under the seats into the trunk where it connects to the USB webcam mounted in the trunk lid. I drilled a hole through which a fisheye lens attached to give me the backup cam.
Connected to underneath the dash is the bluetooth OBDII adapter which feeds realtime data to the Nexus and is displayed on Torque Pro. I enjoy knowing as much as possible about the car and actually end up using this display over the instrument cluster.
The final piece of hardware is the bluetooth remote mounted on the steering wheel. The buttons are remapped to various apps allowing complete control of the Nexus just using the left hand. It only took about a day to completely memorize everything which allows it to be operated without taking my eyes off the road.
Software Set Up
On the software side, The Nexus is running USB ROM with Timur's kernel which provides a fantastic base to start from when it comes to car installations. In addition, redeyedjedi's mod was installed which allows for hotswapping of the webcam as long as it was plugged in at boot. This means once everything is set up correctly, I can remove the tablet for whatever reason and when I plug in the USB again, everything works like it did before without any reboot needed.
Torque Pro is used to read and display all of the realtime information as mentioned before. SDR Touch taps into the RTL2832U dongle to give me live FM radio which is controlled via the bluetooth remote. I have the mainstays of Spotify and iHeartRadio for music in case I have poor reception of radio or just feel like something different.
Getting the webcam to work was tricky because most apps have the display rotated 90 degrees are have too low a refresh rate such that the feed to too choppy to be useful. I ended up installing Mirror because it gives me the correct orientation of the image and has a high enough refresh rate.
Like any good setup up, the Nexus is used for Navigation which is quite nice on the large, 7'' screen compared to my HTC One which I used to use. Google Now can be launched via the bluetooth remote allowing for voice commands to be given to set the location. Having all of the media run through the Nexus means that when navigation is speaking, the other sounds are muted and the directions can be heard clearly. This eliminated the problem of having the GPS drowned out by the radio which happened all too often with my old setup. It should be noted that I cannot yet get SDR Touch to muted or lower its volume when Navigation is speaking yet so that can be a problem sometimes.
Anyways, this is meant for people to follow along if they would like, get some inspiration for their own projects, as well as get some feedback on my own and how it can be improved. As of right now, I'm not looking to completely hide everything because it's all still being tested. I am, however, looking for some thing which can be added on to possibly make it even better. Some things I have already considered are putting a bunch of music on a flash drive for another source of music in case of poor FM and data reception.
Awesome work, i'll try to follow it. thanks for this guide
Is the dash mount sturdy enough to reduce vibrations/shakiness from driving?
jml215 said:
Is the dash mount sturdy enough to reduce vibrations/shakiness from driving?
Click to expand...
Click to collapse
Yep! I love this mount. It is solidly stuck to the dash and the Nexus doesn't move at all even when you hit a pothole or something.
Also, if you are using this guide as a reference, I am testing a new radio antenna setup. The dipole I was using was too directionally dependent and I would lose signal depending on the car's orientation. I'm testing a set up where I splice into the car's antenna and so far it seems to be working well. Once I finalize the setup, I'll update the OP.
This is awesome. In the back of my mind I've been thinking about doing similar, it's so awesome to see it in action. Good work!
aviola7x7 said:
Getting the webcam to work was tricky because most apps have the display rotated 90 degrees are have too low a refresh rate such that the feed to too choppy to be useful. I ended up installing Mirror because it gives me the correct orientation of the image and has a high enough refresh rate.
Click to expand...
Click to collapse
Interesting setup with all the extra antennas!
Question about the cam...
You mentioned refresh rates and all. What about lag or delay? Is there a delay in the video when it hits your screen?
Or was that fixed with the Mirror app?
Nice setup. I have a question about your FreedomPop dongle. When your Nexus comes out of sleep mode, does it automatically reconnect to the dongle/4G? I have one as well, and it worked fine when I tested it on my bench but once installed it doesn't seem to want to work.
Backup Cam (Mirror)
Can you please post a link to the Backup Camera App you have used... After much searching I still cannot find it...
This is the ugliest car install I've seen, obviously aesthetics aren't an important factor for you.
Poi25 said:
This is the ugliest car install I've seen, obviously aesthetics aren't an important factor for you.
Click to expand...
Click to collapse
That's the ugliest comment I've seen. Obviously, reading the post wasn't important to you. There's no reason to hide it and make it look good if it's still in a testing phase for different items.
Great post aviola, interesting choices in parts and a very good breakdown for people to gain ideas from. Very good point about keeping it removable, because summer car heat can really obliterate pieces/devices that are out unprotected.
:good:
thanks so much for this guide. :good:
Sorry for the delayed responses. With the semester finishing up, I keep forgetting to come back to this thread
natesjk said:
Interesting setup with all the extra antennas!
Question about the cam...
You mentioned refresh rates and all. What about lag or delay? Is there a delay in the video when it hits your screen?
Or was that fixed with the Mirror app?
Click to expand...
Click to collapse
I have no real issues when it comes to lag. Initially, when I was using camera applications, there was a good 1 second delay between what the camera saw and what the screen showed. Installing the mirror app reduced the lag to a point I don't notice it anymore.
delphi.actual said:
Can you please post a link to the Backup Camera App you have used... After much searching I still cannot find it...
Click to expand...
Click to collapse
Here is the link for the Mirror app I have been using:
https://play.google.com/store/apps/details?id=com.yuvalluzon.mirror
In terms of updates, I have successfully tied the tuner into my car antenna for the best reception. I installed a splitter so that the car radio and usb tuner can be connected simultaneously. SDR is good but doesn't do as well with poor reception and there are some times I would rather just use the radio rather than the whole setup.
I'm still having power issues where the the screen on max and GPS navigation use more power than the tablet gets. I'll probably do some testing with a multimeter to see how much power is actually getting to the tablet but for now I have to take the Nexus in about once a week for a full charge up.
Aesthetically, I don't have any plans as of yet to hide all of the wires. I'm constantly swapping stuff in and out and don't want the hassle of dealing with running them through the dash or anything. As the majority of people have correctly observed, this is a proof concept rather than a formal installation. My objective in posting this was not to provide a complete step by step guide for people to follow as there are already several excellent threads devoted to this. This was meant for people to get ideas from so they could build their own installations with their own equipment.
Thanks everyone for all of the positive feedback. For anyone with questions, feel free to continue to ask and I will do my best to be more timely about answering them. If you need more in depth or specific information, that's really what this thread is all about. I anticipate changes to my setup will come slowly but I'll try and update this with the ones that have been proven to work.
I am looking to get a b+ to set up as a mini computer on the cheap.
What do you guys use your pi for?
Torrent downloader + media player
desde Tapatalk móvil
Routinely sits in front of the TV as a media player too (OpenElec), but after a quick change of SD card has a second identity for the kids with Minecraft, Scratch and beginning to edge towards Python and some similar coding and basic I/O learning via the GPIO.
The Pi is OK as a cheap computer, as long as you don't expect too much from it in terms of processing power. If what you want to do could broadly be done on a smartphone or similar device (or a mid-spec tablet) then you should be ok, but if you want to replace a true PC then you may struggle depending on exactly what it is you plan. It'll certainly handle day-to-day stuff like email and web browsing though (if you're not so concerned about flash and that kind of stuff, as with mobiles too).
Currently using my Pi as a web server. It does well for keeping it up and running but there is a problem regarding power. I'm using a Bluetooth and WiFi adapter (as I have no way of connecting it to Ethernet), the power issue is that the poly fuses kind of blow up after a few days or hours and therefore either one or both of the USB ports don't have any power, I have to disconnect the power and then plug it in after a few hours/minutes and then it works again (self-repair). Really annoying so I may need keep it for local hosting while an other product that I'm hoping to receive shouldn't have issues with it and should be more powerful so that I can make it public and run it with no issues.
The Pi tries to use less power as possible by boosting the power to the USB ports (consider the fact that the Pi takes around 5v of power, same for a single USB port) so if you need to use USB devices which are doing to be a little intensive with power then expect the USB devices to get a power cut off.
If the Pi is going to be used for something that isn't so power hungry then it should do for certain things.
You can boost the Pi's power (talking about literal energy, not performance) but that means more parts.
You may also partially get around that by using a powered hub to take some of the strain. But there again you are adding additional parts and power requirements. There are cases available with built-in hubs and more chunky power supplies to drive both the hub and the Pi which at least partially get around some of that, but it's more investment.
The other alternative is to minimise such power-hungry items and consider things like ethernet-by-powerline for the network if a direct cable would be inconvenient or impossible (but again at the cost of extra bits of hardware and further set-up).
DarrenHill said:
The Pi is OK as a cheap computer, as long as you don't expect too much from it in terms of processing power.
Click to expand...
Click to collapse
Yeah, this will not replace my pc, rather just be a little fun project, as it will be more unique than a tablet, and serve the same purpose.
Media center and APRS digi, another is my marine reef tank controller
Portable (battery powered) Mp3 player/Internet radio streamer.
Chris J said:
Portable (battery powered) Mp3 player/Internet radio streamer.
Click to expand...
Click to collapse
Where do you get a suitable battery pack from?
I bought it with a whole host of wonderful ideas of what to use it for, and never got round to anything.
Very occasionally it gets used as a media player (with OpenELEC), with an external HD, but since I've had a Chromecast it's pretty much been gathering dust!
One day I'll get round to doing this: http://www.raspberrypi.org/ambilight-alike/
Jesse72 said:
Where do you get a suitable battery pack from?
Click to expand...
Click to collapse
Amazon; 2600 mAh cellphone charger. It only cost around five dollars and provides stable output while charging, so you don't have to bother with switching it when the charger is plugged in.
---------- Post added at 09:01 AM ---------- Previous post was at 08:29 AM ----------
I also have one connected to a 1TB hard disk I use as a file/print server. It doesn't actually see much use, but it consumes so little power that there's no harm leaving it on.
house automation
I use mine as a server for house automation using FHEM.
Jesse72 said:
Where do you get a suitable battery pack from?
Click to expand...
Click to collapse
Just normal portable battery is ok.
Mine makes me hungry
Mine is a honeypot
(always work in progress)
http://nowhere.purificato.org:65000/
As server,for play music+films and for learning,but most for crying,lol.
GREETZ FROM TEAM-OPTIMA!!!
All sorts!
I've used mine as a web server, a bluetooth portable speaker, a wifi point (when my wifi access point went bang) and now it sits and controls the lighting in my computer and cupboard-under-the-stairs!! (where me and my computer live!!)
I'm gonna get some arduino stuff and adafruit stuff to do the lighting soon then I'll figure out another use for it.
Probably going to buy a B+ board and retire my current one to my son so he can do his school Scratch projects on it.
Probably the best thing ive bought for its versatility.
Not much as of yet
I haven't been using my raspberry pi for a few months now due to my hectic work schedule, however the only use I had for it was media center purposes. I ran both RasPlex and Raspbmc (with the latter being the preferred OS).
I'm hoping that with the new year almost upon us that I'll be able to look into other uses. I'm mainly interested in either home automation or home security. Although I have a friend who is working on making an arcade cabinet using i-pac equipment and pimame as an OS which has piqued my interests severely.
Torrent + Network Attached Storage
MY PI
I generally use my Raspberry for the night when i turn the pc off. In the day I use it As A Universal Remote Control for Nearly everything that's it how i use my PI...
"Headunit": The First, Best, and Only Headunit app for Android Auto, Now Open Source & Free !
Turn an Android tablet into an Android Auto compatible Headunit ! (With several limitations at this early time of course...)
Android N developer preview: http://forum.xda-developers.com/showpost.php?p=65749262&postcount=1165
If you purchased Headunit on Play before Google removed it: http://forum.xda-developers.com/gen...droid-auto-t3125252/post65015637#post65015637
160117 January 17: New Self mode & Car mode fix: http://forum.xda-developers.com/gen...droid-auto-t3125252/post64844560#post64844560
151224 December 24: 1280x720 and X86 support: http://forum.xda-developers.com/showpost.php?p=64466237&postcount=943
151128 November 28: Voice Input + Audio Output: http://forum.xda-developers.com/showpost.php?p=64045807&postcount=903
August 28 & 5 Voice Input etc: http://forum.xda-developers.com/showpost.php?p=62548380&postcount=724
USB OTG Y cables I've had success with: http://forum.xda-developers.com/showpost.php?p=62745966&postcount=792
Comments welcome: Proposal for a Private Website / Forum for the Headunit app and Automotive Android: http://forum.xda-developers.com/showpost.php?p=62207324&postcount=587
July 24 APK Immersive mode: http://forum.xda-developers.com/showpost.php?p=62014837&postcount=519
July 14b APK Standalone mode: http://forum.xda-developers.com/gen...oid-4-1-headunit-android-auto-t3125252/page43
July 11 APK: http://forum.xda-developers.com/gen...oid-4-1-headunit-android-auto-t3125252/page39
Quick summary of Google Play bans and final responses; I fixed each time & Google gave a different excuse each time: http://forum.xda-developers.com/gen...droid-auto-t3125252/post61632463#post61632463
Nexus 9 OTG charging w/ M developer preview & Nexus 7 2013 w/ Timur kernel/mods: http://forum.xda-developers.com/showpost.php?p=61632651&postcount=312
Nexus 7 2013 OTG charging while running Headunit w/ ElementalX kernel: http://forum.xda-developers.com/showpost.php?p=61593874&postcount=290
Now Open Source and Free ! http://forum.xda-developers.com/gen...droid-auto-t3125252/post61440441#post61440441
June 16 Release #5 APK: http://forum.xda-developers.com/showpost.php?p=61422602&postcount=163
Release #2 APK and instructions: http://forum.xda-developers.com/showpost.php?p=60894402&postcount=94
Thank you "All About Android" for covering the Headunit app in episode 218 ! http://forum.xda-developers.com/showpost.php?p=61412309&postcount=152
Android Auto over WiFi Direct is coming: http://forum.xda-developers.com/gen...oid-4-1-headunit-android-auto-t3125252/page16
June 16 APK: http://forum.xda-developers.com/gen...oid-4-1-headunit-android-auto-t3125252/page15
June 12 APK Auto-Start: http://forum.xda-developers.com/showpost.php?p=61321219&postcount=107
June 11 APK: http://forum.xda-developers.com/gen...unit-android-auto-t3125252/page8#post61287292
June 9 APK: http://forum.xda-developers.com/gen...roid-4-1-headunit-android-auto-t3125252/page5
Android Auto is Google's latest and greatest effort to provide automotive navigation, music, phone and other features in an environment that minimizes distraction.
The Headunit app is intended for 7 inch /17 cm or larger tablets.
A $100-200 Nexus 7 tablet mounted in the car is MUCH cheaper than $700-$1400 Pioneer devices.
A $300+ 10 inch/25+ cm tablet provides a much larger & nicer screen than 6 inch double-din units.
Original XDA Thread: http://forum.xda-developers.com/android-auto/android-auto-general/developer-mode-aa-t3059481
These are early, experimental releases. They should only be used for testing at this time.
Please note that Google has NOT released Android Auto specifications required to build a Headunit app such as this, except to headunit and auto OEMs who have paid fees and signed NDAs.
This app required over 500 hundred hours of painstaking reverse engineering (and many more to come), and another 500 or so as of mid July to build and test the app so far.
If you wish for apps like this that are professionally engineered, supported and updated, your financial support via Paypal donations is required, especially since Google will not allow Headunit apps on Play.
Help keep an independent developer working full-time++ on this cool new stuff.
Thanks for your support !
Mike.
What the heck is Android Auto, and why would I want it ?: http://forum.xda-developers.com/showpost.php?p=61114397&postcount=2
What devices and ROMs are supported ?: http://forum.xda-developers.com/showpost.php?p=61114397&postcount=3
How do I use the Headunit app?: http://forum.xda-developers.com/showpost.php?p=61114419&postcount=4
Troubleshooting: http://forum.xda-developers.com/showpost.php?p=61114437&postcount=5
Supported Phones running Android Auto: http://forum.xda-developers.com/showpost.php?p=61114468&postcount=6
Business Issues: Open Source & Pricing: http://forum.xda-developers.com/showpost.php?p=61114482&postcount=7
Feature Requests: http://forum.xda-developers.com/showpost.php?p=61114494&postcount=8
Coming Features: http://forum.xda-developers.com/showpost.php?p=61114500&postcount=9
Future of Android Auto: http://forum.xda-developers.com/showpost.php?p=61114532&postcount=10
What the heck is Android Auto, and why would I want it ?
Introduction / Different approaches:
There are many different approaches to running apps in a car, and they each have advantages and disadvantages.
Many people are happy to just install an Android tablet or Android based headunit and run apps much like they do outside of the car.
Others may mount their phone on the dash and use Android as they always do. They may plug it in to charge and might pair the phone's Bluetooth with their existing in-car audio system.
If you are using approaches like these, and you are happy with them, that's great ! I'm not a mission to convince you otherwise if you have decided these methods are best for you.
Android Auto:
Android Auto (AA) is Google's latest and greatest effort to provide automotive navigation, music, phone and other features in an environment that minimizes distraction.
AA was announced in 2014, and it's "app" first publicly released March 19, 2015, after Pioneer starting selling their AA compatible 4100/7100/8100-NEX headunits. Google did not seem ready to launch AA at that point, but Pioneer's early release of headunits seems to have forced this.
Apple has it's own rough equivalent to AA called Apple Car Play. Many who have seen both prefer AA, but iOS users also appreciate having more or less the same iOS UI they already know in their car.
How AA works (basic):
AA is not a mirroring solution like MirrorLink, Miracast or Apple Airplay. Mirroring solutions simply send phone screen video to an external, larger screen and return touch events. Thus the in-car screen is simply a blown-up version of the phone screen.
Mirroring solutions generally work with all existing apps. AA on the other hand, requires Android apps to have special AA compatible extensions added. Clearly this can be a disadvantage of AA. Few music and messaging apps can be used with AA, and the only mapping/navigation app supported is Google's.
With AA, Google mostly controls the User Interface (UI) as implemented in their AA "companion app". AA compatible apps CAN modify some of the color scheme and some related minor UI features, but the look and feel are largely Google designed and controlled.
Google has done this to minimize distraction. Although many of us will not be happy with Google's decisions. we should consider that the last things Google wants are: (1) laws against Android Auto, (2) bad publicity from distracted driving incidents, and (3) expensive lawsuits. Note that Google, Apple and the auto OEMs are reportedly negotiating who takes how much responsibility for the inevitable lawsuits, particularly in the US where multi-million dollar settlements regularly occur.
Google AA supports two types of AA compatible apps at present, with more (eg maps/navigation ?) coming in future: (1) Audio/music and (2) messaging. For the most part, audio/music AA extensions provide functions for starting/stopping/nexting/etc of the audio as well as functions to determine the music navigation hierarchy. Messaging AA extensions include sending a message to AA to be converted to speech as well as handling spoken replies.
Video and gaming apps will likely never be supported for the drivers position, at least while driving, for obvious reasons.
Many app developers are hesitating at this time to add AA extensions. At this time, there is very little revenue to be made by supporting AA (and the same has been seen for watch and TV apps). This should improve as more cars have AA installed, via OEM systems or aftermarket headunits.
So why would I want AA ?:
If you need access to ANY Android app, and not just the limited selection of AA compatible apps, then mirroring solutions will work better for you.
AA is more for people who want a solution that "just works" (although there are still many wrinkles to iron out), is well integrated, and has a common Google specified UI.
Less technically minded people will appreciate AA or Apple CarPlay, while Android power users may be happier with mounting a tablet or using an Android based (usually Chinese) HU.
An Android based HU which can run my Headunit app, may offer the best of both worlds. You can run any Android app when you need to, or run my HU app to get AA features. (At present nobody has reported success running my Headunit app on an Android based HU. I hope/presume I'll figure that out.)
I am personally convinced that AA will be very important for Google going forward. Controlling and getting the treasure-trove of data from connected cars is important to Google. We may not be far from the day when Google will get a commission when it successfully convinces us to pull over for specific fast food or auto maintenance. Want fries with your oil change ?
Because AA is important to Google, I feel confident it will not be abandoned, and will only get better as the years tick by, bugs are fixed, apps are AA enabled, etc.
Getting AA working:
Please, always do your best to drive responsibly and with a safe minimum of distraction. You assume all liability for following any of these or any other instructions.
First, your phone (or tablet) needs the AA companion app installed. US residents can install the Android Auto app from Play: https://play.google.com/store/apps/details?id=com.google.android.projection.gearhead and those outside the US can find APKs here: http://www.apkmirror.com/apk/google-inc/android-auto/ .
Next, you need an AA compatible aftermarket or auto OEM headunit. Auto OEM AA headunits (HUs) are just starting to come out for a limited selection of 2016 models. Aftermarket HUs like the Pioneer 4100/7100/8100-NEX devices are a good alternative. If a $500-700 HU is too expensive for you, that's where my Headunit app for tablets comes in, but there are some inherent disadvantages to such an app and a tablet is just one of the costs. More on this further below.
Ensure that your mobile device running the Google AA companion app is setup with a Google account. Make sure the Google apps are up-to-date, including the AA app, Google Play Services, Google Maps, and Google Play Music.
Now plug your mobile device USB into the HU. If all goes well you should see a series of prompts and screens on the HU and mobile device. If something complains that it's not safe to configure at this time, ensure your car is in the Park gear (or neutral for manual), that the emergency/parking brake is fully engaged, and press down on the brake pedal. My 4100-NEX is setup for testing, outside of a car, and I simply connect the green wire to ground or 12 volt negative line. I'm not sure that this will work well if your HU is installed such that the green wire is connected to other things.
Hopefully you will now see the main AA Intro/Google Now Screen. Select functions from the "rail" at bottom of screen: In order: Maps/navigation, Phone, Google Now, Music, and "Other/OEM".
Your mobile device should show a mostly black AA screen indicating the device is in AA/car mode. You CAN escape this and run other apps, but it is not recommended.
While your mobile device is connected via USB, it should charge. Turn the device screen off to maximize charging and minimize heat build up. Using Maps/Navigation will use the device GPS (unless the HU provides it) and this contributes to heating of the device and minimizes charging.
How AA works (technical):
Basically, the AA app creates a special environment in which it draws to a virtual screen instead of the real screen. The resulting video is encoded as an H.264 stream and sent via USB to the HU. The HU responds with touch-screen events which the AA app interprets similarly to normal Android app operation.
AA compatible audio apps contain AA audio extensions, which can provide control of audio app playback and provide information about which audio streams or files can be played. The audio app uses it's normal Android audio APIs, which the AA "app" hooks in order to send the audio to the HU, over USB or Bluetooth. I refer to the AA "app" with parentheses, because it has many hooks into Android internals which normal apps do not have access to. Thus, much of the AA "app" is really system level code, though there is a minor UI for some basic configuration and to provide access to AA developer mode functions.
The AA USB protocol also includes functions for accessing sensors, including parking brake status, gear position, fuel tank level, road speed, engine speed and many more. Only a few sensor functions are fully implemented at this time however, such as parking brake status to determine if it is safe to do configuration.
Google has referred to AA HU's as "dumb terminals". But IMO a true "dumb terminal" would simply be a touchscreen with a DVI/HDMI like interface. AA HUs DO need to have some "smarts", such as H.264 video decoding, Bluetooth and sensor signal processing.
Hardware HUs also generally provide many other functions that work standalone with no mobile device, such as AM/FM/HD radio, CD player and vendor specific apps that run on the HU.
Why would I want your Headunit app ?:
- For the customization opportunities.
I haven't seen any 10 inch / 25 cm screens on auto OEM or aftermarket HUs. Large tablets however are readily available with many choices for screens and other hardware.
- To use or experiment with Android Auto without buying a new car or a $500+ hardware headunit.
Note however that besides the tablet, you may also need a USB OTG Y cable and a powered USB hub in order to properly charge the mobile device, and tablet, without running down the tablet battery.
Some devices (for tablets, mostly non-Samsung) may need special kernels in order to charge while acting as a USB host.
Why can't we just run our phone in an AA standalone mode, without tablet or Headunit ?:
Mostly because Google does not want that. They consider screens under 7 inches / 17 cm to be distracting. Google seems to eventually want "Android in the car", so Google may be working on something like a standalone mode (for what would essentially be an Android tablet in the car), but this is nothing but rumours so far.
I know a LOT of people would REALLY like a standalone mode, so I am likely to explore the feasibility of this in the near future. I am sure that Google would disapprove of this and would eventually take measures to sabotage such a thing, so it's a tricky prospect.
I think an AA standalone mode "app" (more like system mods than an app, same as AA "app" itself) would require a rooted device. It likely would also require Xposed (or similar) to hook and modify various system functions.
Add it all up and it turns into a very difficult venture with limited returns on time invested.
A Headunit app running on a 2nd device/tablet is more feasible as Google can not just change the AA protocol overnight, and it does not require root on the tablet (except for charging of non-Samsung tablets, sigh...)
Are there any other AA compatible Headunit apps ?
At this time no, my Headunit app is the first and only of it's kind.
Google has not publicly released documentation or code to build a Headunit app, and may never do so.
It has so far taken me over 600 hours of work to reverse engineer the AA protocol and build this app. With open docs/code it might have taken only 100-200 hours at most.
I've read a report that Google must certify AA HU implementations before they are "allowed". This is likely part of the agreement and NDAs that auto and HU OEMs must sign to join Googles "Open Auto" alliance, beyond whatever fees are charged.
GENIVI appears to have plans to "open source" an AA client implementation. But AFAICT, GENIVI "open source" is not entirely public and open. I suspect Google would want to ensure that any users of such source code adhere to their requirements.
Pioneer HUs run Android. Their AA client implementation is a binary, so it's somewhat similar to an HU app. But it's specific to their hardware and will not work on general purpose Android tablets or phones.
There may be other Headunit apps to come, but I have not heard of any, beyond one persons desire to create an open source app in the long term.
What devices and ROMs are supported ?
Root is NOT required. (But root and a custom kernel may be needed on non-Samsung tablets in order to allow the tablet to charge while it's in USB host mode.)
Most Android 4.1+ ROMs should be able to work.
ICS 4.0 and earlier devices/ROMs do not have the needed video decoder and can never work. (Except by building my own decoder with FFMPeg or whatever, which is way too much work for too little return.)
A working H.264 video decoder is required, but most quality Android 4.1+ devices should have this. (Chinese/budget devices may use slow and/or buggy implementations.)
Only devices that support USB host mode are physically capable of working. Many or most tablets released in the last 2 years should support USB host mode.
Full, official support is limited to devices I own. With sufficient demand for a new device, I may purchase that device and add official support, if possible.
These are the tablets that I own and test:
Nexus 7 2012 stock.
Nexus 7 2013 stock.
Nexus 9 2014 stock.
Xperia Z2 Tablet stock. CM12 tested OK too.
Many other devices will work and I will do my best to support them.
Phones can work as a headunit, but tablets of 7 inches/17 cm or greater are recommended. Smaller screens are more distracting and can risk your safety.
How do I use the Headunit app?
At this time I can't recommend this for use while driving. It's ONLY for testing within the safety of a home or office... If you can't understand that this Headunit app is still VERY experimental and potentially very distracting while driving, then please don't run it. It's not my fault in any respect or measure if you hit a tree or kill people; it's ALL on you... You assume all responsibility for collisions, injury or the advent of Skynet...
App requires Android 4.1 ICS or higher, but I've mostly tested on Android 4.4 KK, 5.0 and 5.1 Lollipop..
I tested successfully on these, for the Headunit/Tablet side running my app:
Tablets are recommended for a decent size screen in a vehicle:
Xperia Z2 Tablet - CM12 - This 10" screen is wonderful compared to the 7 inch/17 cm 800x480 Pioneer 4100-NEX screen, despite that the video is still only 800x480 at this time.
Nexus 9 - stock - This looks pretty nice too and the CPU power helps make it look good and pretty lag free.
Nexus 7 2013 - stock
Nexus 7 2012 - stock
Phones can also work, but small screens are less safe so I can only recommend these for testing:
HTC One M8 - stock
HTC One M7 - CM12
HTC One XL - CM12
Xperia Z - Lollipop
Xperia Z1 - CM12/FXP
Moto G - CM12
GT-N7100 Note 2 - CM11, but with some video issues.
These phones have major issues or did not work for me:
GT-I9300 GS3 - CM12 unofficial
GT-N7000 Note1 - CM11
GT-I9100 - Android 5.1 ROM
GT-I9000 - Android 5.1 ROM
Note that Headunit/Tablet side issues are largely separate from Phone/Mobile Device side issues. Phones that do not work with Pioneer or other AA head units will not work with this app either, and only Google and the phone OEMs can fix that. This includes MANY very popular Samsung devices. I note that my older Samsung devices also have issues on the Headunit side, and this may be related to general USB issues on Samsungs. (?)
The Headunit/Tablet side running the Headunit app needs to connect to the phone running AA with a USB OTG cable. The OTG cable small micro-USB side needs to plug into the Headunit side.
Many devices can do USB Host for the Headunit side, but can't supply any power to the phone. For these devices a powered USB hub is required, and is recommended for all devices anyway, or the Tablet/Headunit device will quickly lose power to running the phone device.
The phone running AA plugs into the USB hub output side, and should be the only device so plugged in (or the device my app connects to will be random-ish, with HTCs having highest priority.)
When they are all plugged, be patient and wait at least 6 seconds after plugging the USB before starting my app. Most likely the Gallery app will open on the Headunit side. This is annoying, but at least it confirms the connection is good. You may have to wait, then hit Back to exit Gallery. If you get any popups, hit Back or Cancel; you might get several.
Latest AA companion apps to run on the phone side are here: http://www.apkmirror.com/apk/google-inc/android-auto/ This requires Android 5.0 Lollipop+ on the phone side as per Googles' decision, and also requires Google Mobile/Play services to be installed and an account set up.
Now you can start the Headunit. You should be prompted to allow access to USB twice. Select OK both times. Don't bother to check the "Remember" box because it never works and it's a silly Google thing. Better solutions are possible, especially if rooted.
If you have never connected the phone with AA to a headunit before, you will be prompted to do a bunch of stuff on the phone side. If you are outside the US you must manually update to the latest AA app from APKMirror etc. You may have to download Maps and Play Music if you don't have yet, and say Yes or "Standard" etc, to various prompts.
After all this, hopefully you will see video on the Headunit screen. You will likely see a safety warning prompt etc. Read it and understand it, and select OK if you dare.
Hopefully you will now come to the main/home/Overview/Now screen of AA. On some devices, video may be imperfect. Select different functions on the "rail" at bottom to help clear it up.
Touch works, but not Multi-touch yet.
Audio output was through the phone last I looked, but microphone does not work.
If you hit Back while in the app, it should exit and the AA connection is broken.
To open a new AA connection/restart the app you MUST disconnect and reconnect the USB, at any point in the chain.
It generally seems possible to turn the screen off and return to it after powering it back on, but if the orientation changes from landscape this may not work. Same for leaving the app with the Home or Recents button; if it switches to portrait, you can't get the video back and must stop the app, reconnect USB and restart the app.
I'm finding that quite a few of my phones running custom ROMs will not run AA on the phone side properly. In some cases a custom DPI really messes up the video dimensions and you can't even select the startup OK button. I see this on my One M7 with CM12 and many people see the same on other phones w/ custom ROMs, whether using a Pioneer headunit or this app.
Enjoy responsibly.
Troubleshooting:
Nothing more disheartening than trying a cool new app, and.... it doesn't work.
Public Enemy #1: Cheap/Bad USB OTG cables.
I got 3 cheap OTG cables and 2 straight and 2 right angle adapters a few months ago. The cables seemed OK in the beginning and now they're all flaky. The adapters didn't last as long and some were flaky new. 7 cables and adapters and they're all garbage.
I've been happy for a few weeks at least with these $10 Y cables that can power/charge both devices. I'll see if they're still good in the next few months: http://www.amazon.com/Micro-Cable-Power-Samsung-AtomicMarket/dp/B009YPYORM
But even with the best cables, your phone and tablet micro-USB ports can be a factor too. Car mounting, with constant vibrations and bumps adds to the challenge.
When I get Android Auto over Wifi working better, I hope USB will just become a backup connection. But wifi has it's own issues too.
Cheap or Chinese devices and hardware HUs are a "crap-shoot": So far I don't think I've had a single success report for Chinese devices. The ROMs and video decoding are often bad or VERY slow and USB is questionable. Some devices do not support USB Host mode or have a bad software implementation.
I recommend Nexus or good quality tablets from Sony or maybe Samsung. All tablets that I own work and are officially supported, including: Nexus 7 2012, Nexus 7 2013, Nexus 9 and Sony Xperia Z2 tablet.
July 24 or later releases recommended for testing: http://forum.xda-developers.com/showpost.php?p=62014837&postcount=519http://forum.xda-developers.com/gen...oid-4-1-headunit-android-auto-t3125252/page39
July 24 has a bottom "Test" button to test H.264 video decoder (some phone/ROM decoders are bad or VERY slow.)
Also has a bottom "SUsb" button for devices with USB Host Mode supporting kernels even without Android support.
Also allows manual USB device selection when automatic doesn't work.
MANY possible fixes:
- You must have 2 devices for the Headunit app, so try reversing them to see if that works. This requires the Android Auto app and Google app, Google Play Music, Google Now and Google Maps to be installed on both devices of course.
- You usually need 2 cables: The micro-USB side of an OTG cable to the Headunit app device/tablet, and the full-size USB connection to a "normal" phone/USB cable connected to the Android Auto device/phone.
At least one person reversed the cables, without reversing HU and AA devices and it worked. USB can be funny; there are MANY possible jumper, resistors, wires etc combinations, especially with specialty high current charging cables.
- With some devices, an OTG Y cable MUST be powered, with others it MUST NOT be powered, and for some it doesn't matter and power can even be stopped and started with no effect.
- "Fast Charge" should be disabled if it's a kernel setting. Saw this with Elemental-X kernel on Nexus 7 2013. This kernel also has a setting to allow charging in USB Host mode.
- Sometimes enabling USB Debugging helps, sometimes disabling, sometimes turning it off, then back on. Do this at both ends: Headunit app device and Android Auto device.
- Unplug and replug cables, at both ends and in between. Ensure they are firmly pushed together. July 11 release allows you to see devices disappearing and re-appearing if cable connections are flaky and moved.
- Before starting Headunit app, plug all cables together. If Camera Importer or Gallery, or other apps pop up, hit Cancel or Back to deal with them first. Then after a few seconds of no more popups, NOW start the Headunit app. Plugging/unplugging while the app is running may work but is less successful than starting the app after plugging.
- Some devices/ROMs have various USB settings to try, such as "Charge Only", MTP, etc.
- Use the Exit button or Back key to terminate the Headunit app and try again. It kills it's own process for an extra fresh start next time.
- Use Recents button to return to the Headunit app if Android Auto covers it.
- Avoid screen switching to Portrait mode for best chances of success. Home-screens that force portrait mode can create problems, as can lock-screens.
- Self or SUsb modes require SU/root access. Sometimes the SU prompt is covered and not visible. In such cases manual SU configuration, or setting SU default to "Grant" can help.
Supported Phones running Android Auto:
Any phone that works with hardware headunits, such as Pioneer 4100/7100/8100-NEX, should also work with this Headunit app.
Note: This list is for devices running Android Auto. It is NOT for connected devices running the Headunit app, except for Self standalone mode where one device runs both.
Devices that I tested OK:
Galaxy S3 GT-I9300 CM12.
HTC One M7 stock & CM12.
HTC One M8 stock & CM12.
Xperia Z stock & CM11.
Xperia Z1 stock & CM11.
Xperia Z2 stock & CM11.
Moto G stock & CM12.
EDIT: I wrote this page before Google banned Headunit from Play and before I made it free and open source, but please feel free to read my thoughts written before that below.
Soliciting donations sucks. Thanks much to those that have and those that will. But VERY few people do. At some point I will likely have to return to a commercial model.
Those who donated, or bought Headunit on Play before the ban will become most honoured customers retroactively.
Business Issues:
Yes, I am (attempting) to run a business here. I hope I don't have to explain or apologize for trying to make a minimal income to help support my wife, kids, cats, pay for a house, cars, and all the usual basic accoutrements of life like food, electric, fuel, etc, etc...
I have been working 60-70 hour weeks for over 4 years now on my apps, mostly the Spirit FM apps: Spirit1, Spirit2, Spirit Transmit. I have no other income except my apps.
I am somewhat disappointed that I've been making a small fraction of what I made for decades doing contract or salaried work for a plethora of tech companies.
I have seen my Spirit FM income dropping for the last few years, and have entered into the connected car apps space in an effort to make a better income.
I hope to serve your app desires and appreciate the financial support of everyone who can afford at least roughly the price of a meal at McDonalds, or there-abouts.
Open Source:
Yes, I know EVERYONE wants free and open source software... I LOVE open source; my career has been built mostly on Linux (and Android) since 1997.
But NONE of the 20-odd companies I've done contract or salaried work for in those 18 years has open sourced their code.
Very, VERY few companies turn a profit with open source. How many app devs can you show me that make a decent living exclusively or primarily with open source ? Over 99.9% are based on closed source.
Kickstarter / IndieGogo etc ? LOL. Show me a lone app dev who has done well with that route.
If someone were to sponsor me with a decent income I'd be happy to open source everything. But that's not too likely and I'm not seeking that.
Google is keeping their AA code secret and unpublished, and they do the same with their premium apps like GMail, while the AOSP apps like EMail languish.
Pricing:
Pricing software is a funny thing. If no technical support or packaging are provided (and there are no advertising costs), the incremental cost of 1 more copy of an app is zero.
And yet if you hire people (or yourself) and pay a decent, competitive rate, the R&D costs for the 1st copy can be in the $millions for many modern apps.
There is no such thing as a "fair price"* for an app. Many think apps must be $0.99 for something simpler, or up to $10 for something more complex, and in rarer cases, $20-40-100 or much more.
(*Fair Price: If we talk about technical support, a "fair price" becomes more feasible. If my time is worth $60 per hour (and it should be much more in this field for very short term work), then 10 minutes of total time spent to support someone is worth $10. But that ignores ALL the time it takes to build and test apps.)
The number of people who will buy an app at some given price are a major determinant for a developer trying to make a decent living.
A popular non-root app for "Joe Average" that millions of people might use might be $0.99 or free with ads.
An app only for Android enthusiasts who root, ROM and install Xposed on the other hand will have a very limited market, and price must be high for a chance to make a decent living.
I've noted that there are several examples of specialist Automotive apps that sell in the $20-40 range. Then there are apps like Torque that may sell for $3-5 but have a much bigger market, and the income allows people to be hired, above and beyond supporting a single independent developer.
At this time, I've put this Headunit app for sale at less than $9 US or 8 Euro (after 20% VAT Euro prices are under 10 Euro, but I get none of that).
Note that Google takes 30% (42% markup !) so I only get about $6 US per app. That hardly buys a Big Mac these days...
My desire is to license this Headunit app on a per device basis, though Google doesn't provide any easy method to do so. So if you use this app in 2 cars, but with only one Play store purchase, I'd appreciate consideration via Paypal. There is NO DRM in this app and I REALLY hope not to use any form of copy protection. DRM is mostly trouble.
I reserve the right to change price at any time. As the app becomes more fully featured, I may raise the price as needed to get sufficient income to work on this full time.
Without sufficient financial support, I'll just have to spend more time on other app opportunities. So if you use and like this app (or just want to support such) please support me so I can support you.
And please help spread the word about this app. I'd rather spend time working on wonderful new features and fixing bugs (LOL) than spending time doing marketing stuff, or spending/wasting money on advertising.
Thanks !
Mike.
Feature Requests:
I'm always happy to hear what you want.... Speak up !
Coming Features:
(Originally written in June. Amended August.)
Features I guarantee I will try to added in the relatively short term of 1-3 months:
- Automatic start at plugin.
- Bypass USB permissions with root. (July 24 "SUsb" button)
- Multitouch support (pinch zoom GMaps)
- Resolution increase & switching, if possible. 800x480 at present, 1280x720, 1920x1080. (July 24 still does not seem possible. No hardware HUs higher than 800x480 so Google hasn't enabled ?)
Future of Android Auto:
Built-in, Brought in, Beamed in.
Android in the car
Self driving cars
Flying cars
Skynet^H^H^H^H^H^H
"Headunit" - Build an AA Headunit with a $165 tablet...
As I posted on the original thread:
240 downloads of the Free APK now... http://forum.xda-developers.com/showpost.php?p=60894402&postcount=94
"Headunit" is the app name I've settled on. Short & sweet.
Want to see this Headunit app fixed and improved on a regular basis ?
Then I need your help...
First need is some IMO well deserved publicity. There is no other app like this and I think there is a need...
I saw LOTS of excitement on Android enthusiast sites about Android Auto. And a LOT of excitement dissipated hearing that a $700 Headunit or new car was required.
So wouldn't turning a $165 Nexus 7 2013 tablet into a basic AA Headunit with an app restore some excitement ?
I've been busy on the tech side, but to keep this project moving, people need to find out about it.
I've started a new thread here for all further discussion about my Headunit app: http://forum.xda-developers.com/general/paid-software/android-4-1-headunit-android-auto-t3125252
If it seems worthy to you, please consider clicking on "Submit Thread as News Tip" at top right of that thread.
Most Android news and discussion sites have similar functions to submit news tips. If it comes from people like you, I'd think it has more weight than me trying to promote my new app.
XDA is kinda, sorta, not supposed to be used to SELL things (and that's kinda vague & fuzzy, and there IS a section for paid apps, where my new thread is), and I understand and respect that...
But truth is that my second, and perhaps most important need, in order to support YOU, is for some "little bits" of support from you... See my new thread or sig for the new paid APK on Play.
There are other, Android Auto/Connected Car app ideas I have, should this one garner insufficient support. Feel free to comment:
- Use any media player (or messenging) with AA, where it does not have AA extensions.
- App to connect sensors, + via ODB and maybe Torque like functionality.
- Standalone mode for AA running on a phone. Will likely require root and Xposed and LOTS of work and workaround when Google sabotages it.
- Customization of Android Auto via root/Xposed app; Change anything from backgrounds to color to rules that AA imposes in the name of safety and anything else that needs a mod.
Thanks !
Mike ( [email protected] )
Hi!
I've just purchased your headunit app. I've attempted to connect it, but am unable to get it working. I'm really excited to see something like this, and can probably help you debug it if needed.
My devices:
- Nexus 7 (2012 Wifi), running stock Android 5.1.1, stock recovery, rooted with Nexus Root Toolkit
- Nexus 4, running stock Android 5.1.1, custom recovery, rooted with Nexus Root Toolkit
Cables:
- USB OTG cable, purchased some time ago, but known to be functional -- I've used it on my Nexus 4 to connect a microSD reader.
- Micro USB (male) connector from USB OTG cable plugged into Nexus 7.
- Charging cable plugged into micro USB connector (female) on USB OTG cable.
- Standard micro USB connected from Nexus 4 to USB A (female) port on USB OTG cable.
- Both devices show as charging.
Problem:
- When starting Headunit app, the screen stays black (with only standard on-screen controls, and never prompts me on either device for anything).
- I have also tested this in reverse, by sideloading the Headunit APK onto my Nexus 4 (Google Play Store said incompatible, but what do they know? ), and sideloading the Android Auto app onto my Nexus 7. I reversed the cabling, so that the USB OTG cable is plugged into the Nexus 4 as the host device. Same results.
- I've tried various combinations of unplugging and replugging, force closing and restarting apps, etc.
What's the next step in debugging this setup?
jpreston84 said:
Hi!
I've just purchased your headunit app. I've attempted to connect it, but am unable to get it working. I'm really excited to see something like this, and can probably help you debug it if needed.
My devices:
- Nexus 7 (2012 Wifi), running stock Android 5.1.1, stock recovery, rooted with Nexus Root Toolkit
- Nexus 4, running stock Android 5.1.1, custom recovery, rooted with Nexus Root Toolkit
Cables:
- USB OTG cable, purchased some time ago, but known to be functional -- I've used it on my Nexus 4 to connect a microSD reader.
- Micro USB (male) connector from USB OTG cable plugged into Nexus 7.
- Charging cable plugged into micro USB connector (female) on USB OTG cable.
- Standard micro USB connected from Nexus 4 to USB A (female) port on USB OTG cable.
- Both devices show as charging.
Problem:
- When starting Headunit app, the screen stays black (with only standard on-screen controls, and never prompts me on either device for anything).
- I have also tested this in reverse, by sideloading the Headunit APK onto my Nexus 4 (Google Play Store said incompatible, but what do they know? ), and sideloading the Android Auto app onto my Nexus 7. I reversed the cabling, so that the USB OTG cable is plugged into the Nexus 4 as the host device. Same results.
- I've tried various combinations of unplugging and replugging, force closing and restarting apps, etc.
What's the next step in debugging this setup?
Click to expand...
Click to collapse
Hi, Thanks for your support.
Send me an email at [email protected] and I'll send you a debug release. Or I'll PM you a link when I get one built in a few hours. Are you able to capture a logcat or should I add an easy "Send logcat" button ?
Some quick googling tells me the stock Nexus 4 does not support USB OTG (ie running the headunit app). But some kernels enable this and this is the first thread I saw about that: http://forum.xda-developers.com/nex...g-externally-powered-usb-otg-t2181820/page154
The app specifies that USB OTG is required, and I thought that was a great way to prevent people from purchasing on incompatible devices. But now that I see Nexus 4 (and I'm sure many other devices) can do OTG with a custom kernel, I guess I should remove that as a hard requirement. A popup warning would be better.
I have that same Nexus 7 2012 with the latest Android 5.1.1 (unrooted even) and pretty much stock, and all released versions of the Headunit app work on it. So I feel confident that the hardware and software work OK together.
And AFAIK, Android Auto runs fine on stock Nexus 4.
If you aren't getting prompted for USB permissions on the Headunit app side, that seems to indicate a connection problem.
Can you stop charging the Nexus 7 and reboot it to see if that helps ? My understanding is that Nexus devices can't do USB host mode and charge at the same time. Custom kernels are needed to allow this.
If you have a plain OTG cable without a charging connection please try that also. Ensure that the regular USB cable supports data tranfer. Some are for charging only.
My test setup is:
- 1 regular USB cable: large male (plugged into OTG large female) to micro-USB male (plugged into Android Auto phone).
- 1 OTG cable: large femaie (plugged into regular large male) to micro-USB male (plugged into Headunit device).
Sometimes between the 2 cables I insert a powered USB hub, but a straight connection seems to work for both Nexus 7's, Nexus 9 and Xperia Z2 tablet, though it does drain the Headunit device battery to charge the Android Auto device.
A good sign that the cabling is working is seeing the Gallery app opening on the Headunit device when they are plugged. Android Auto device pictures and videos are shown via USB MTP I guess.
I'm going to add a startup screen that shows connected USB devices and that can be used for trouble-shooting.
This thread needs to be woken up...
If you have ANY questions or comments, please post !
I'm encouraged to see the Headunit app on Play has had 2 confirmed sales in the last 2 days; there are also 9 cancels (boo !) and 3 unconfirmed....
Pretty Good I think for the first few days of a new app.... Could be more if I remove the strict USB host requirement, but probably more disappointed cancellers too.
I appreciate Google Play reviews from anyone who has purchased and/or cancelled.
Right now I have two 1 star reviews on Play to deal with; thankfully Google lets us reply to reviews now.
Here's what I just added to the Play Store description:
No risk/full refund within 90 days. Just email 15 digit order ID or email of purchase to [email protected] . But "be warned" that I WILL do my best to get this app working for you and make you happy, or at least explain why your device may be incompatible...
Click to expand...
Click to collapse
Message to app reviewers on Play:
The Reviews section of Google Play has a 350 letter maximum. It is impossible to provide good technical support with that limit.
Please email me [email protected] for private support.
But I prefer to discuss publicly for everyone's benefit if you are registered or don't mind registering at XDA Developers Forum. Headunit Thread: http://forum.xda-developers.com/general/paid-software/android-4-1-headunit-android-auto-t3125252
If Headunit is working well for you, Great !
For problems, please read on:
I updated the Play Store description with this:
NOTE: Requires 2 devices ! Needs an Android 4.1+ tablet (that supports USB Host mode) running this Headunit app connected to an Android 5.0+ phone running Android Auto. Connection requires 1 standard phone USB cable and a special USB OTG cable connected to the Headunit app device.
No risk/full refund within 90 days. Just email 15 digit order ID or email of purchase to [email protected] . But "be warned" that I WILL do my best to get this app working for you and make you happy, or at least explain why your device may be incompatible...
Click to expand...
Click to collapse
I hope you understand this is the first release of a new type of app, and that I'm still calling it "experimental".
I will do my best to support as many devices as I can. But some devices will never work, particularly those that can not support "USB Host Mode".
The most common problem will be USB cable connection problems. Generally, you will need at least 2 cables:
1 USB OTG cable connected to tablet or other device running the Headunit app.
1 Regular USB cable connected to phone running Android Auto.
The cables are connected together of course, directly or though a hub. Sometimes you may need to insert a powered USB hub between the cables, with the powered side going to the Android Auto phone.
Sometimes connections may be loose. Ensure that (at least) all 3 connections are securely made. Gently try to push the plugs in just a little deeper to see if it goes farther. This has fixed it for me more than once.
I will put some better debugging and logging options in the next release of this app.
There is a LOT more information about how to get the Headunit app working, and some trouble-shooting hints in the First 10 posts of thread: http://forum.xda-developers.com/general/paid-software/android-4-1-headunit-android-auto-t3125252
Hi, good work on getting this started. For me the deal breaker feature down the line would be car integration, namely:
Bluetooth calls take place over car mic and speakers
Steering wheel controls (volume, answer, next track, etc.)
I imagine some support for the pioneer adapter that allows this would be feasible.
Any plans or knowledge about that?
ok, seems to be working ok (although slowly) on a nexus 7 2012 (as headunit). does not work at all on a nexus 7 2013 (as headunit), just a black screen without any notices.
I would really like to try this, but the USB port of my N7 2012 is broken, and I still haven't fixed it :/
Sent using my nexus⁴ running Euphoria 1.1 with Xposed and hells-Core B78
Maxr1998 said:
I would really like to try this, but the USB port of my N7 2012 is broken, and I still haven't fixed it :/
Click to expand...
Click to collapse
I really hope that Google can enable Android Auto over WiFi soon. If not, I will consider mods that would allow this. But it would require root on both sides; an AA standalone mode (that only needs one rooted device) may be desirable to more people.
Android Auto over Wifi would solve USB specific connection problems, like the need for USB Host mode on the Headunit and the associated "charging while in USB host mode" problems that usually requite a custom kernel.
ldti said:
ok, seems to be working ok (although slowly) on a nexus 7 2012 (as headunit). does not work at all on a nexus 7 2013 (as headunit), just a black screen without any notices.
Click to expand...
Click to collapse
Good start...
My N7 2012 seems to have good video speed, but I only use it for testing so I have very few apps and they aren't doing many background tasks.
Does the video have defects or does it look accurate ? I have seen slowness and defects together, but mostly on my older, slower phones.
The release I'm working on now has better debbuging capabilities. I'll try to post a new version within the next 12 hours.
Can I presume both Nexus 7's are stock ? Root and recovery shouldn't matter, but a custom kernel (or ROM) could make a big difference.
Hello guys, I'm planning to build my first carputer. 2 years ago I have modified a tablet, Asus zenpad 8, very similar to Nexus 7 in my opinion. Now I want something more.
What I want:
Fully automated pc that works exactly like an android head unit but much better and more flexibility when it comes to external devices like an external DAC with optical output. Actually this is the main reason for not buying an android head unit, didn't find one that works very well with an external DAC. Some other things that I want from this carputer: the compatibility with steering wheel controls, backup camera, fm or even DAB radio, gps, phone calls( via bluetooth), 4G internet and so on. Many of those things are pretty simple to integrate, will talk about them later.
The components:
1. The pc - didn't think about it yet because there are loads of mini pc on the market for good prices. The only problem I'm thinking is the start up on ignition. First I wanted to go for a Remix mini pc but I don't know how could I make it start on ignition and after that automatically play the last song. If I would go for a normal PC, I found a smart PSU which has the possibility of ignition start and stop and puts the computer in sleep mode. That way I will avoid the waiting time for the boot, in fact the computer will be permanently turned on. The only problem I can think of, is the compatibility of this PSU with the android Remix OS. Is it possible?
I've tested the Remix OS and I like it, very quiq, easy to use in car with a touch screen, support all the external devices( wifi, 4g, fm and DAB, external DAC with optical output) and the launcher can be changed. I know I can opt for Windows OS and that way I will be sure that the PSU works but in my opinion windows is not so "mobile friendly", not so easy to use in car.
2. The screen: not so many to talk about, found on ebay some 9" tft touch screens, very good resolution, hdmi connectivity and USB for touch. The best thing with these screens is the AV2 input for the backup camera. The screen automatically switch to this input, has guidance lines, and this way I solved the problem with the camera. And also is quite cheap.
3. Steering wheel controls. Found on ebay the Joycon steering wheel adapter that is compatible with Android. I just have to make an initial configuration and that's it, nothing more, simply works through USB.
4. The other external devices: all of them can be found on ebay for good prices. The only thing that worries me is the bluetooth compatibility. I remember when I built that Asus zenpad tablet, I couldn't find a solution for this. Now my question is, what type of bluetooth adapter should I buy and how do I integrate this in the carputer. And I'm not talking about physical connection, I think I will need some kind of software, app, that knows what to do with this bluetooth adapter.
So, in the end, I would need some help regarding the ignition start, just the hardware part of it, all the other automatic things (launch the app and play the song) can be made with tasker very easy. Also I would need some help with the bluetooth phone calls.
Hope I didn't miss any important thing and I will appreciate any help. Thanks.
yoiedi said:
Hello guys, I'm planning to build my first carputer. 2 years ago I have modified a tablet, Asus zenpad 8, very similar to Nexus 7 in my opinion. Now I want something more.
What I want:
Fully automated pc that works exactly like an android head unit but much better and more flexibility when it comes to external devices like an external DAC with optical output. Actually this is the main reason for not buying an android head unit, didn't find one that works very well with an external DAC. Some other things that I want from this carputer: the compatibility with steering wheel controls, backup camera, fm or even DAB radio, gps, phone calls( via bluetooth), 4G internet and so on. Many of those things are pretty simple to integrate, will talk about them later.
The components:
1. The pc - didn't think about it yet because there are loads of mini pc on the market for good prices. The only problem I'm thinking is the start up on ignition. First I wanted to go for a Remix mini pc but I don't know how could I make it start on ignition and after that automatically play the last song. If I would go for a normal PC, I found a smart PSU which has the possibility of ignition start and stop and puts the computer in sleep mode. That way I will avoid the waiting time for the boot, in fact the computer will be permanently turned on. The only problem I can think of, is the compatibility of this PSU with the android Remix OS. Is it possible?
I've tested the Remix OS and I like it, very quiq, easy to use in car with a touch screen, support all the external devices( wifi, 4g, fm and DAB, external DAC with optical output) and the launcher can be changed. I know I can opt for Windows OS and that way I will be sure that the PSU works but in my opinion windows is not so "mobile friendly", not so easy to use in car.
2. The screen: not so many to talk about, found on ebay some 9" tft touch screens, very good resolution, hdmi connectivity and USB for touch. The best thing with these screens is the AV2 input for the backup camera. The screen automatically switch to this input, has guidance lines, and this way I solved the problem with the camera. And also is quite cheap.
3. Steering wheel controls. Found on ebay the Joycon steering wheel adapter that is compatible with Android. I just have to make an initial configuration and that's it, nothing more, simply works through USB.
4. The other external devices: all of them can be found on ebay for good prices. The only thing that worries me is the bluetooth compatibility. I remember when I built that Asus zenpad tablet, I couldn't find a solution for this. Now my question is, what type of bluetooth adapter should I buy and how do I integrate this in the carputer. And I'm not talking about physical connection, I think I will need some kind of software, app, that knows what to do with this bluetooth adapter.
So, in the end, I would need some help regarding the ignition start, just the hardware part of it, all the other automatic things (launch the app and play the song) can be made with tasker very easy. Also I would need some help with the bluetooth phone calls.
Hope I didn't miss any important thing and I will appreciate any help. Thanks.
Click to expand...
Click to collapse
Have you thought about using a rock 64 single board computer like a Raspberry Pi that Android is really supported something like that could work really well as it has gpio outputs for various functions USB inputs for audio dacs and DAB radio and can work with touch screens or even projectors for heads up.
The truth is I know nothing about raspberry pi, heard about them but nothing more. Can you please explain a bit more? Is it possible to make it automatically turn on/off on ignition? How? Apparently that's the hardest part of the job. I've read on the internet that Remix OS doesn't work very well with stand-by function and if I'll make it to shut down completely, I'm afraid that will take too long to boot back. I was thinking about Remix mini pc and a controller that simulates pressing of the on/off button simultaneously with the ignition but it has to be tested.
So, quickly searched on google about raspberry pi and banana pi possibilities, there are some power supplies for in car use, basically they simulate a shut down from the button with a delay. That looks very good, very easy to do and also very cheap. But, how fast can boot a raspberry or banana pi running Remix OS? Does anyone know?
yoiedi said:
The truth is I know nothing about raspberry pi, heard about them but nothing more. Can you please explain a bit more? Is it possible to make it automatically turn on/off on ignition? How? Apparently that's the hardest part of the job. I've read on the internet that Remix OS doesn't work very well with stand-by function and if I'll make it to shut down completely, I'm afraid that will take too long to boot back. I was thinking about Remix mini pc and a controller that simulates pressing of the on/off button simultaneously with the ignition but it has to be tested.
Click to expand...
Click to collapse
To make it turn off and on with the ignition, just plug it into a 12v line that is powered when ignition is on. Generally the 12v line to your head unit fits that criteria. If you want constant power to keep the device in standby mode, you can connect a relay to an a wire that is powered when the car is powered, then use the relay to short the pins of the standby button.
For boot time, you can achieve quite a bit of improvement by getting the fastest sdcard you can buy.
Thanks for advice. I've searched on youtube how android works with raspberry pi and in my opinion they don't do it very well, I mean it struggles even on youtube playing videos. So, I bought an ssd hdd, 32gb and made some tests on my pc. Found a version of android 7 special made for in car use and I'm quite happy with it until now. This android has a "special" feature, when the power button is pressed the pc shut down without displaying any confirmation message on screen. That means it will work perfectly with an intelligent power supply like m2-atx, m3-atx etc. In the next few days I'll get a new pc, micro atx mainboard so I'll begin the tests on that. Until now I've got a boot time around 30-40 seconds. Is not a bad time but I'll try to remove the unnecessary apps from startup and see what happens then. I'll post some pictures or even videos when I'll have good results. Any advice is welcome. Thanks.
yoiedi said:
Thanks for advice. I've searched on youtube how android works with raspberry pi and in my opinion they don't do it very well, I mean it struggles even on youtube playing videos. So, I bought an ssd hdd, 32gb and made some tests on my pc. Found a version of android 7 special made for in car use and I'm quite happy with it until now. This android has a "special" feature, when the power button is pressed the pc shut down without displaying any confirmation message on screen. That means it will work perfectly with an intelligent power supply like m2-atx, m3-atx etc. In the next few days I'll get a new pc, micro atx mainboard so I'll begin the tests on that. Until now I've got a boot time around 30-40 seconds. Is not a bad time but I'll try to remove the unnecessary apps from startup and see what happens then. I'll post some pictures or even videos when I'll have good results. Any advice is welcome. Thanks.
Click to expand...
Click to collapse
Check these out http://www.hardkernel.com/main/main.php
yoiedi said:
Thanks for advice. I've searched on youtube how android works with raspberry pi and in my opinion they don't do it very well, I mean it struggles even on youtube playing videos. So, I bought an ssd hdd, 32gb and made some tests on my pc. Found a version of android 7 special made for in car use and I'm quite happy with it until now. This android has a "special" feature, when the power button is pressed the pc shut down without displaying any confirmation message on screen. That means it will work perfectly with an intelligent power supply like m2-atx, m3-atx etc. In the next few days I'll get a new pc, micro atx mainboard so I'll begin the tests on that. Until now I've got a boot time around 30-40 seconds. Is not a bad time but I'll try to remove the unnecessary apps from startup and see what happens then. I'll post some pictures or even videos when I'll have good results. Any advice is welcome. Thanks.
Click to expand...
Click to collapse
Why don't you get an android head unit?
gtxaspec said:
Why don't you get an android head unit?
Click to expand...
Click to collapse
I think you didn't read, I couldn't find any that works with an external sound card(DAC). My audio system is quite expensive, made for sound quality, and of course I want the head unit to be as good as possible. An external sound card with optical output I think is the best you can get.
Google search "raspberry pi alternative" theres lots of these little gadgets now adays, raspberry pi 3B is one of the most popular ( and cheapest) but there are more out there that are more powerful & better hardware.. The ASUS Tinkerboard is becoming popular as well I think I may be getting one for a streaming machine.
I've already purchased the PC and ordered the PSU. The price for all those components(+ a 30gb ssd) was under 100£ so not very expensive. Why I went for a pc instead of a single board pc? I don't know, maybe because I have no previous experience with them. Yes is true that is way much bigger than a raspberry alternative and the power consumption as well but I don't mind, maybe in the future when I'll get bored again I will try one of those pc's.
So, I've tried to install the Android X86 64bit (there is one version on internet with a patch that removes the confirmation message when you want to shut it down) on this pc with no success, all I've got was a black screen or a continuous reboot. Found out that Android X86 64bit is not so friendly with AMD cpu's. Should've search for that before buying it. Anyway, tried the 32bit version so that one works very well but I didn't find any with that patch installed. How can I remove that confirmation message when the power button is pressed?
Thanks.
first tests, quite happy with it, still lot of work to do.
https://youtu.be/lNJmRjXG81A
Odroid C2 with android + kodi
For anyone that still uses a Note 5, and misses the IR Blaster from their Note 4 or S6, I purchased one of those 3.5mm IR adapters from eBay for $5.00 that works great.
The description of some of these 3.5mm adapters was pretty clear: Does not work with Android! iPhone only! etc. well, it works great with my Note 5. I don't know about other Android or Galaxy phones, but it works with mine. I don't know if the Note 5 supplies more power to its ports because it has to support the S-Pen or something of that sort, but the LED on the 3.5mm ir adapter lights up like a Christmas tree on mine (blue light.)
Practically every thread I've looked up on this forum, states that these don't work; however, based on my results so far, from about 10 feet out the adapter works flawlessly. From up to 14 feet out it's so-so. After 14 feet it's a hit or miss, leaning towards the miss most of the time.
I chose the smaller adapter because I use a case, and can barely see it sticking out; definitely what a was looking for. There are other adapters on eBay that look huge; I'm sure they have better range but at the cost of portability and cosmetics. To activate the adapter you have to do a half turn to the right/left (it doesn't matter which way you turn it, once the LED lights up, it means it's being powered) and download "Remote ZaZa-Universal Remote" app from the Play Store. The Samsung peel remote app didn't work, or maybe I didn't know how to set it up; however, with ZaZa I was able to set up my TV and Set-Top-Box in no time.
Since the 3.5mm headphone jack is at the bottom, ZaZa has an option to rotate the app on start-up to save you the hassle of having to do it every time the app is opened. Again, make sure the adapter lights up. Mine lights up blue every time I rotate it to the right or left. If it doesn't, it might be defective. Also, remember to turn the volume all the way up on the ZaZa settings options, since I believe that gives the device more amperage for better range.
Can you share the sellers name or info on the IR so I can find it?
I would like to look into this can you share the ebay link
Please can you share the link.
I reverse image searched the pictures and found an ebay post in Germany but it looks like the guy has stopped selling them. (I can't post the link due to too few posts)
Thanks :good: