yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] p64imp:
Take donaldta's reply and follow the schematics in his previous post for the relay. Pulling the u jumper = isolation of the power from the front posts. Connecting this to the relay using the schematics donaldta provided in his previous post will get you going.

I bought this relay and connected it exactly as it showed and it fired up perfectly the first time on ignition.

Note that the relay you purchase will have 5 posts (only 4 are connected in the schematic). THis was marginally confusing to me at first, but if you look closely the spade for that 5th post is there, just not connected.
[Android Head-Units] tdt038:
Guys who bought this unit, can you upload stock apps from unit - radio, music player, еqualizer and phone? Just looks niser than from AN-21. Also, maybe you have firmware?
[Android Head-Units] mad212:
I got it all hooked up this weekend and everything works great. Didn't use a relay just hooked up to cig lighter fuse and it shuts off with ignition. So far loving the head unit just need to figure out how to get Spotify and Rdio cache to usb or microsd. Anyone figure that out yet?
[Android Head-Units] booba5185:
Hey everyone,

I have my AN 21 U installed and working great, except for my SWC. I'm confused. I open the radio app with a song playing, the song pauses and the radio starts. I hold back like the F.A.Q.'s say to, and when I hit Play on my steering wheel, the paused song resumes. That is the only button that works. After that, I open the steering wheel controls app and hit start the Volume Up, both buttons turn yellow on the screen, and nothing else happens. Ever. I push up Volume up on my SWC, and nothing happens. What am I doing wrong?

I'm also getting ready to dig into Torque. I have a USB OBD II ELM adapter that's a cheapie off ebay, and it doesn't work at all. Torque is set to USB, but no device is seen.
[Android Head-Units] jonalowe:
Does the OBD adapter work with a PC or another Android device? That's the first thing I'd check. Most of the adapters come with a PC program.
[Android Head-Units] booba5185:
I don'y have anything else to check it with at the moment, but I will shortly. I'm mainly wanting to get the SWC working right now.
[Android Head-Units] djblaze852002:
Music2SD has tricked my spotify a few times

I have used Music2SD to get Google Music to save to the external SD slot. It requires the Xposed Famework.

I noticed however on a few occasions if I installed Music2SD

then

installed spotify, somehow it would trick spotify into saving to the external SD card too. I have only gotten it to do it a few times... In my case, I do not want spotify saving to my external SD as I rarely use it and I want to reserve all the space for google music. I have also experienced some crashes when using Music2SD, I'm still trying to figure out what is causing them. A quick reboot fixes the issue...

Has anyone else had any experience with Music2SD?
[Android Head-Units] ohsobrown:
no audio coming from unit

Hey there! So my audio stopped coming from my unit. it still plays the songs or video, but the audio crapped out. i tried restarting it and the volume came back for a few seconds, but went away right after that.

i tried resetting it to factory settings, but it didnt help. the same problem occurs.

what can i do to get it back?

can you help me please?
[Android Head-Units] ionutlup:
Audio problem.

I push rst(reset) and restored the audio.Try!
[Android Head-Units] booba5185:
This SWC stuff is frustrating! What should I be doing differently? My car only has the single wire setup, and the play button works, but I can't get anything else to work!
[Android Head-Units] ohsobrown:
Audio stopped working

Okay so my audio stopped working all in general. No sound is coming from the radio either. I turned up the volume while listening to some wu-tang, and the sound died off.

I tried restarting the unit, and it came back for a few seconds with the volume turned down, but then stopped working again.

After resetting it to the factory settings, the problem has not gone away.

Can you help me? I have no idea as to what I should do.

Thanks!
[Android Head-Units] mad212:
I tried music2sd and I was getting force closes of Play Music so I disabled it.
[Android Head-Units] booba5185:
Well after HOURS of searching, the only information I could find said to:

1.) Connect Key 1 to the car's SWC wire (there is only 1, it's a 2000 Grand Prix)

2.) Hit start then the function I want the button to perform on the Head Unit (turning start and the function yellow)

3.) Hold the button on the steering wheel itslef

4.) Touch the Key 2 wire to ground

5.) The buttons on the screen of the head unit should turn grey, and I should follow steps from there.

Does it sound like I missed anything? I have to pull my dash all apart to do this, so I dunno if it'll be coming apart today or not.
[Android Head-Units] TOMMYX2:
you need only the Key-1 wire,if your Car have a digital Can Bus you need a seperate Can Bus Adapter for your Car;)

i hope they release a better Firmware for the Unit or something make a Rom for better Support and Overclocking.
[Android Head-Units] booba5185:
I just finished trying and no dice, I hit start and Vol (-) on the head unit and they turn yellow, then I hold the Volume (-) on the steering wheel. The instant I ground Key 2, the button turns grey on the head unit. I hit end and close out of the steering control app, and the button does nothing. If I ground Key 2 it'll turn the volume down though. I also tried the same procedure with the key1 and key 2 wires swapped, with the same results. I know my car is not Canbus. I think I am going to us my old PAC SWI infared interface I have from my old head unit and use it. Does anyone know a way to remap the remote keys or make the remote keys work in Poweramp?

Edit: nevermind, I need a USB remote setup for the remote to work. Awesome. I guess it's back to trying to fix the steering wheel controls. What am I doing wrong?
[Android Head-Units] mcskeezy:
Setting default permissions for peripherals

Wow, what a monster thread. I've gone through about 100 pages of it and haven't found an answer to my question, so I guess I'll go ahead and ask.

I've got an WIRED ELM327 OBDII adapter plugged directly into the USB port on the back of the unit. It's recognized fine, and displays metrics from my car in a fabulous manner. The only hiccup is that every time the app is launched, Android asks me if I would like to associate this peripheral by default with the application. Seems simple enough, but Android doesn't seem to remember my selection. To confound the problem, under android's settings, I don't see the options for setting and choosing default applications. I do have the unit rooted, and I'm currently out of ideas. I'll post a photo of the error message below.

htt ps://ww w.dropbox.com/s/hlnuqmcv3gqs7ul/2014-03-04%2019.17.34.jpg

Any help would be greatly appreciated.

Quick Edit: This problem has already been solved. A solution is posted in post number 2052 in this thread. I had to enable root explorer BEFORE trying to backup the Torque APK. Now that annoying popup is gone for good!!! Hope this helps anyone with the same problem.
[Android Head-Units] booba5185:
Do you have a link to the unit you bought? I bought one off of ebay and it doesn't work at all. I have it connected to a powered hub (tried connected directly) and only the red light comes on. The other turn on when I first plug it in, but soon after that they are all off. the head unit never does anything.
[Android Head-Units] p64imp:
Hi,

I'm wondering if somebody can please help me. I've been trying to get my unit to start up the way i'd like it but i'm having a lot of issues.

First, i noticed that applications dont work right unless i have the aux in app from the MCU started and closed out. Other apps tend to cause issues such as sound stealing from other apps (music/radio/dvd), etc. so i just have aux in the default app to boot on.

The issue here is whenever i start my unit, it takes about 10 seconds to boot up and enter aux in, then i have to wait another 15 or so seconds before i'm able to hit home to finally get to the android home screen. Then i have to wait yet another 10 or so seconds for the system to fully load before i can start an application. This is a HUGE pain in the butt as i'd like for it to simply start up at the home screen when i hop in my car. Should not be a chore every time.

I spent hours playing with tasker. I set device_boot properties to wait 15 seconds, force close aux in, and go to the home screen. Nothing. I read some places that some devices load tasker after the device_boot hits, so i'm guessing tasker is missing the trigger. From there i set a task on aux in open to close the app (not preferred, but frustrated at this point) and go to the home screen. This also does not work as aux in is getting loaded again before tasker.

I gave up on tasker and the many additional variations i tried and went with startup manager. I purchased pro so i can get in to the advanced options, and in both basic and advanced aux in does not appear at all.

At this point i have no idea what to try next and am preparing to just deal with the ass way it likes to boot.

Anyone else have luck getting this dang thing to boot straight to the home screen, or even better an application such as wayze or pandora?

Tired of trying new things at this point... hoping somebody can help!
[Android Head-Units] mcskeezy:
Getting device to boot into specific app

I like to have my device boot straight into the Torque App. To do this I've used a program called AutoStart by Guro Labs. You simply choose the apps you want to start on boot and voila. I had tried 3-4 other startup apps and none of them worked, but this one seems to be just what you need. I've had no luck with tasker on these units, but it sure does work great on my phone. There's still a 5-10 second delay before everything loads up but hey, we're talking about cold booting into android, it's going to take ~20 seconds. I just deal with it.
[Android Head-Units] booba5185:
I have tasker opening Poweramp and playing a song when I boot up, works like a charm. That's weird. Have you tried opening the Disc app (without a disc inserted)? It'll close itself and then the unit is "free" from the stock apps, unless you open one again. If you open one again, just go open Disc again and it'll close itself.
[Android Head-Units] sciallo:
Wiki page

For those who don't know, a wiki page was started about all of these units. As of yet it's still rough, and it's a single page for all the head units...

Special thanks to [MENTION=1915855]KID52[/MENTION] [MENTION=5192090]G2k0[/MENTION] [MENTION=255685]tin2001[/MENTION] [MENTION=220275]tbd@immigrantsong.de[/MENTION] for the contributions.

I plan on moving most "series" (ie. OUKU, S150, AN-21 U etc.) details on their own pages linked from there and keeping the main page as a list with identification and topics common to all units. I will also add subpages such as how-tos etc from there. These threads tend to get lengthy and confusing really quickly, it will be nice to have some of these hacks/fixes/suggestions organized and readly accessible... I know more is coming, root was just the beginning: now that we have that, we'll have all kinds of how to's popping up (google framework/gapps, market/playstore fixes, gmail sync) we should start a to-do list... I'm sure a lot of what was done for the ouku probably applies just the same (for example the cache fix for large apps in this post by no other than [MENTION=2322651]jakejm79[/MENTION]...

[MENTION=1915855]KID52[/MENTION] nice job on the specs, where did you get such details as what sound processing chip is in there etc.? (Interesting by the way I was looking at the spec sheet for it, and it confirms what I was talking about in this post and others. Communication with the eq app is I2C)

On that note....

It's not confirmed but you should also be able to display aux in. At least that gives a few more options, with the right connector/adapter you could stream/play movies from your phone for the kids in the back...

That feature is another adeed feature that is really part of the "non android" side of these things. (see the post i mentioned if I lost you). Android itself has no way of outputing a specific app or anything for that matter to a separate video out... technically it should be able to mirror what you see on one screen to others but I don't think there is an android unit set up that way AFAIK... What unit did you see those instructions for? got a link to that video?
[Android Head-Units] donaldta:
Btw, it still depends on the ROM not necessarily whether or not it is running Gingerbread (API - 10). The stock Asteroid Smart is running Android 2.3.7 and works just fine CL230x and PL2303 ODB2 adapters "out of the box". I suppose it is a unique situation since coincidently the GPS unit for this unit is a Telnit GPS inside of external USB to Serial (CL203x) dongle which apps communicate to it over /dev/ttyUSB1 devlink.
[Android Head-Units] sciallo:
Guys, OTG is simply the abilty of a USB port to switch from Host to Device and vice versa on demand. In fact in some cases a device can charge or be charged on the same port depending on what state it's in.

That does not handle any of the kernel crap, it just allows phone "charge" and "device" plugs to also act as "host" plugs. In our case WE HAVE TWO HOST PLUGS!! (hence no usb ADB) OTG does absolutely nothing 3.2 or 4.1 same thing our 3.2 units don't need OTG because they have 2 dedicated USB host plugs...

For any program to communicate with anything on that port there needs to be a driver that bridges between harware and userspace/system software. Not just USB... ALL HARDWARE! That is the kernel's main job. Some of it is "just handeled", it's become so standard and unified it's just part of the kernel, built into it. (example USB mass storage or USB keyboards). but most of it needs to be compiled specifically (actually I'm wrong, if the developers of the firmware wanted to be mean they could have compiled the kernel for this rom without USB keyboard for example) or added as a loadable module...

If they figured out a way to add a module from torque that's great, but not the most efficient and bug-proof. This would run in userspace and have lower priority. I'm not knoledgeable enough to say wether it would even be a kernel module or a userspace program that manages to get that serial connection going, but I'm curious to know (well, somewhat, low on the list I wanna learn)

I feel that regardless it would be a better way to have the right kernel module installed. And just the one I need at that... no need to waste resouce and space (and boot time?) for something I don't need (probably part reason why developers of the stock rom kept it so skimpy...)

Am I wrong in any of this? I am just learning, I don't mean to sound lecturing but re-reading this it kind of does :rolleyes:
[Android Head-Units] jakejm79:
I believe the answer is none, at least the for Ouku it was, Hal9K added one module and Brady compiled another which I added to the most recent firmware. It might be different for the An-21U, but I doubt it, though I do think it would be a good idea to find out. Yes I have no doubt there are plenty of issues with 'natively' supported devices (probably reason for why live data was freezing for the other user in this forum).

---------- Post added at 01:25 AM ---------- Previous post was at 01:21 AM ----------

Not if the Asteroid came with the correct kernel modules included out of the box, from what I have read/experienced the Chinese manufactures have little interest in supporting additional features (like OBDII), they rely on the low price to sell them. The Asteroid and Ca-Fi devices support these additional features and command a premium in doing so.

I don't know about the Asteroid Smart, but I do know the Ca-Fi device has a specific flag set to 'force' Torque Pro to connect via USB, this is the same flag that is needed on the GB Ouku unit.
[Android Head-Units] patrickoneal:
Maybe a dumb question...

Since root and wireless adb access have been achieved, has anyone rebooted into recovery? Just curious if anything interesting is there.
[Android Head-Units] jakejm79:
Torque Pro relies on a OS that supports OTG to use its native support for Serial to USB adapter chips, this is only present in the AN21U, if you own one of the Torque Pro 'natively' supported USB dongles then it should work (though probably in a less than perfect way) with no need for a kernel module. If your dongle is not one of the supported ones then you would need a specific kernel module for it.

If OTG support isn't present in the OS (i.e. GB) then Torque Pro's 'native' support wont work, we need to rely on a kernel module, despite the ports being host they still only support the kernel modules that are available included in the ROM not any 3rd party apps, hence why we couldn't use Torque Pro's 'native' support with GB (i.e. original Ouku) units.
[Android Head-Units] jinny81:
i been a member for years, change email once and cant post links, apparently im still new.

youtube.com/watch?v=p1ycUuUSs-Q

not sure id ever use this dual zone picture in picture function as per the video, the screen is pretty small already, but it would be handy to know all the ins and outs of the unit for that one time...

Having said that, is it just me or the remote control is utterly useless? Does the unit even have an IR sensor? looking at the remote it has the standard IR bulb thing at the front, while theres nothing obvious on the unit, and i saw nothing like a usb IR sensor dongle included in the box.

Bashing around on the remote buttons does nothing.
[Android Head-Units] Defender666:
Wow, just away for 1 day and your guys root the AN-21.

What version of firmware can I use the new for root? I see there is a new 2.62.

If I upgrade to 2.62 don't I loose my TV Tuner app?
[Android Head-Units] donaldta:
Well, you're both right and sort of wrong contextually.

As sciallo pointed out, OTG is simply the ability to switch the USB between a Client and Host port. This is facilitated by a special USB cable which has the sense pin shirted to ground on the MicroUSB cable. Its purpose is to signal the Android device that it needs to be a USB Host in order to communicate with the device on the other end. This is important for devices which do not have native host ports available on them, like Smartphones. So, in this case sciallo is correct.

​

For these Android automotive head units, jakejm79 is wrong because in Torque Pro does not depend on OTG. Rather, it relies on the USB Host API which was introduced Android 3.1 (Honeycomb - API Level 12). This is because these particular Android devices come with dedicated USB host ports as sciallo pointed out and does not need to be switched by an OTG cable. Although, the ports on these head units have various level of integration with the underlying Linux OS and Android sub-systems depending on its ROM.

Jakejm79 is correct in saying that the kernel modules are not necessary for Torque Pro to work, but this is only true if the Android device supports USB Host API. This is because this API provides apps with the option of raw communication with the USB endpoint. In this case, it allows Torque Pro to use its own FTDI and Prolific drivers to communicate through the USB endpoint.

I believe that you might have missed bmj67's post where he listed the modules on the ROM of his AN-21 U head unit. Among the many modules, "usbserial" is found in the list which according to the documentation supports a fair amount of USB to Serial modules including the Prolific PL2303.
[Android Head-Units] slinkydonkey:
I am thinking about getting this device but I want to be able to display my mobiles screen on the display...I wish it supported Miracast for my Google Nexus 4 hint hint haha the next best solution for me would be to use a slimsline adaptor to HDMI but clearly this unit does not support HDMI I was thinking of getting this unit as it supports HDMI http://www.ebay.co.uk/itm/Capacitiv...S_In_Car_Audio_Players_PP&hash=item2333169ec5 it says its Andriod but is it Pure Andriod do you think?
[Android Head-Units] sciallo:
It is not pure and it's known to have problems with the docking connector. It doesn't last too long. These units do have aux audio video in (rca) maybe an adaptor? but I don't see the point too much, why not use it, touchscreen and all rather than just displaying your phone's screen?
[Android Head-Units] slinkydonkey:
Yeah good point I think ill get the PURE one do you how easy it is to install ? currently im using a Pioneer with a Pioneer cables?
[Android Head-Units] donaldta:
You can always run VMLite VNC Server on your Nexus 4 then run vnc view app on the AN-21 U to duplicate the Nexus 4's display. If you want the audio from your phone to also go over your car's speaks then you'd just need to connect audio via bluetooth.

No, that is not a pure Android unit, its a dual OS with WinCE/Android on it. The tablet part is Android but the Car Stereo "Dock" runs Windows CE. When you mount the tablet on the dock then the video switches between the two operating systems depending on function. It's actually pretty much garbage from the reviews I've seen and read. I am not even sure it supports HDMI while it is connected to the car radio since its a HDMI output not input.
[Android Head-Units] sciallo:
I'm assuming you're getting a universal 2din? (there is car specific ones and those come with adapters ready to plug in)

You can buy an adapter and splice that in, but it sounds like you already have one :) just cut that out from the pioneer one and splice the wires from the ISO harness that come with the unit according to the diagrams. the unit comes with wiring diagram, I'm sure you can find yor car wiring reference by googling it. I suggest soldering and heatshrink, but crimp on butt splices would do too.
[Android Head-Units] principino1984:
hey guys do you know if the vw units have the same fw of the universal one?
[Android Head-Units] sciallo:
None of that is confirmed as of yet, heck the 2din generic with 2 dials and more buttons aren't confirmed yet, but they are believed to if they have the same specs.

That seems the way the chinese are doing it... same guts different faces...

---------- Post added at 05:51 AM ---------- Previous post was at 05:50 AM ----------

do you have a link to a specific one you're thinking of?
[Android Head-Units] principino1984:
yes, that's what I thought... what shoud I ask to pumpkin guy to be sure it's the same hardware with a different face? thanks

Marco
[Android Head-Units] slinkydonkey:
Ok I was hoping not to do any soldering im rubbish at it can you just buy an adapter to plug it in? I have a Kia Ceed
[Android Head-Units] sciallo:
Find a kid in the neighbourhood that will do it for a skateboard :)

I don't believe there would be an adaptor with both your car plug and the plug this unit uses... you'd still have to connect it. Crimp them with barrel connectors (or like I plan on doing, with male/female spade and bullet connectors so I can always take it out and wire it to my tabletop psu) crimpers are cheap :)
[Android Head-Units] cchrisv:
How?

Can you post your settings for tasker. I would like mine to do the same.

---------- Post added at 02:53 AM ---------- Previous post was at 02:48 AM ----------

Can you share your system_ui.apk. I would love to get rid of the soft buttons.
[Android Head-Units] ackyo:
FYI, i installed an inclinometer app for when i am offroad - Inclinometer Pro, works great on my phone but unfortunately these units do not appear to have any sensors that the app can use