yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] RMac6.0:
OBDII Bluetooth Now Connected

Thanks for the reply!

I already had the bluetooth OBDII because I previously used Torque displayed on my phone. Maybe I was a bit close minded since I had one but everything I read here seemed to really point to using the bluetooth type connection.

After a little research I found this link on ft86club.com/forums/showthread.php?p=1388518 website where post #15 walked me through it. It was a little confusing as the steps did not match words on the screen exactly. After deleting the file you suggested I was able to select bluetooth connection in Torque and now it works like it should.

Side Note:

Another handy link I found - (http) ://brady.thtech.net/tag/torque/
[Android Head-Units] jakejm79:
Yeah it's kinda an either or with OBDII you can either force USB but then BT wont work or you can have BT but then USB wont work (deleting/installing the file mentioned will toggle this). I understand that you already had all the stuff, but I think a USB dongle can be had for about $10 and you don't have to worry about configuring with BT quick settings, just plug it in and it works.
[Android Head-Units] sciallo:
been meaning to ask out of curiosity: would renaming that file have the same effect (keeping it easier to switch)?
[Android Head-Units] donaldta:
Yes. It's a Torque thing that checks if the file exists. Changing the filename will hide it from Torque, so that it will use the Bluetooth datalink.
[Android Head-Units] daveaus:
This was working for me but now for some reason when I exit the music app all audio is muted and it won't unmute unless I open the music app (even trying to turn the volume up doesnt work). Any ideas before I do a factory reset?
[Android Head-Units] MrGreenPants:
I think this might do the trick:

Try the following: Check the '3rd party application priority' tickbox in Settings->Sounds

I believe that this is what this checkbox is for - but then again things could have been lost in translation.

Let us know if it works (or doesn't)
[Android Head-Units] daveaus:
I thought you might be onto something there but no luck. It was already ticked, I tried unticking it.. no good.. I reticked it again still the same.

Its strange when the device is in mute and you adjust the volume it comes out of mute but the mode my device seems to be in when the music app isn't running doesn't work that way. You can adjust the volume but the speaker icon on the volume change popup is crossed out.

Looks like I will have to factory reset, failing that I will just put a folder with a silent mp3 in it and use that when I want to listen to Pandora.
[Android Head-Units] sleep_debt:
has anyone else had this problem? i havent heard of this before, via this forum or video reviews (where ive seen people use pandora alongside the oem app).
[Android Head-Units] sciallo:
I remember that happening, it's not the same "mute" as if you mute it with the button, it just tells you all native apps are muted... Have you tried to see if an android app is muted too? (poweramp or whatever) it might just not be...
[Android Head-Units] tin2001:
Can anyone tell me what the newest HAL9K ROM is?

I vaguely remember a post saying there was a newer one than the rooted image I posted in October, and I'm intending to reflash/reformat my unit some time soon so if there's a newer/better ROM, I'd like to go that way.
[Android Head-Units] sciallo:
Post # 2108 :)
[Android Head-Units] sleep_debt:
finally had my unit installed; used this exact usb hub but my wifi usb adapter and obd-to-usb arent reading. do i need to installed drivers for these?

EDIT: my root didnt take, thats probably why...

can someone please post a guide to rooting so i know if im missing a step?
[Android Head-Units] sciallo:
http://xdaforums.com/wiki/Generic_Android_Head_Unit#Rooting
[Android Head-Units] sleep_debt:
ah, thanks! couldnt find it from my phone.
[Android Head-Units] typos1:
Sorry if this has been covered already, but can anyone tell me if these units have a page on xda yet or are mentioned in this thread ?

http://www.ebay.co.uk/itm/261339315591?ssPageName=STRK:MEWAX:IT&_trksid=p3984.m1423.l2649

I have searched the forums and cant find anything, to save me searching through 200 pages ( :-o ) hopefully some one can tell me :)

The wiki page says the Ouku ones are similar, but this one supposedly is dual core Freesscale I.MX535D, not an MST786 Dual Core, cant find any mention of dualcore versions of the I.MX535D on freesscale's website though.
[Android Head-Units] jakejm79:
A similar specced unit has a thread here: http://xdaforums.com/showthread.php?t=2528349 it is has a different faceplate and isn't confirmed that it is the same as the unit you linked to, but it appears to have the same dual core processor and android version.

I'd suggest posting in that thread since it is a much better match than the single core Android 2.3.X units discussed in this thread.
[Android Head-Units] typos1:
Thanks, already seen that thread, but posted in this one as I thought that it was a general thread for all android headunits, I ll ask in that one :)
[Android Head-Units] kartun83:
Success

I've been able to flash and root my head unit device, layout of device could be seen on images.

The only difference is the flashing process - mine was entering flashing mode with simultaneous press of volume knob and menu button.

Here is my small research about "Prev/next" buttons:

seems like services radio and music player are catching the key presses, so if I kill apps and services, I was able to catch key presses with other programs, but, at the same time even if this services were killed PowerAmp didn't handle it :crying:

At the current moment I'm almost happy with device, except amount of available modules ... I hope there would be some modules for modern wifi cards and 3G dongles. As I can't find any suitable 3g dongle for the existing modules.
[Android Head-Units] Kartun:
Could someone share list of tested 3g/4g dongles ?
[Android Head-Units] jakejm79:
Has anyone tried a JoyCon EXR with this device, the website states that only Android 3.1 and above is supported, but I just plugged a USB keyboard into my unit and was able to use it (albeit with a few interesting discoveries, detailed below), so I assume it should work, since as far as the head unit is concerned it will just see the JoyCon EXR has a standard USB Keyboard.

Anyway here is a few things I found interesting.

The volume keys on my USB keyboard (Fn + F5, etc) did work, but they only appear to control the Android volume (which doesn't actually change the physical volume, even if an Android source is playing, i.e. Pandora, but the OSD volume display does change).

End appears to shut off the display

Esc appear to simulate Back (but I suspect this is common of all external keyboard Android devices)

Home appears to simulate Home (same as above)

The search button (FN+F3) does launch the search (also context menu button (windows specific keyboards) does the same).

Lastly the top row of letters (Q through P) appear to be used to skip to a certain spot in a track (at least with the AOSP GB music player), i.e. Q will to the start, W to 10%, E to 20% and so on.

Anyway it appears the native apps don't support controls from OS (i.e. the USB keyboard) so my plan is as follows:

My system is a resistive system with just on wire connected to Key1, I plan to leave that connected so I can map the volume buttons and track prev/next buttons in the menu for steering wheel controls, so the built in apps can still use them and it controls the global volume.

But then also connect the JoyCon EXR to that one wire and just program the next/prev buttons (so they will also work in Android apps, but I shouldn't have any conflicts since I wont be listening to the radio and an Android sounds source (i.e. Pandora) at the same time). And then just map my remaining to buttons to Home and Play/Pause.

Anybody see any problems with this?
[Android Head-Units] donaldta:
The reason why it says that it only supports Android 3.1 is because that's when Google released the USB API. However, Linux has supported USB HID keyboard forever and its the underlying OS of Android. Since, the JoyCon is a programmable so you can set as simple Linux Scancodes. Of course, you can also create a custom keylayout file to match those Linux Scancodes to Android key events that are available at whatever API level you're using (use the API dropdown in the leftside to hide the events that are incompatible).
[Android Head-Units] jakejm79:
Yeah I figured that was the case and since my physical USB keyboard worked I see no reason why it shouldn't. My only real problem now is that I don't have enough physical buttons to map everything I want, and then remembering what I have mapped to long press and short press.
[Android Head-Units] tin2001:
Could those wishing to answer the above question please also add it to the USB devices section on the wiki page? That way we will all have quick access to the info :)
[Android Head-Units] cyberpapa3:
CAN TX and CAN RX wires

Hello again,

I've searched most of this tread and the Web in hopes of finding where the CAN TX and CAN RX wires connect to the vehicle. I've installed a Capacitive Android 4.1 6.2" Dual Din 3G-Wifi Car GPS Nav DVD Player BT IPOD RDS #141122491537 in my 2006 Civic EX along with the AXXess ASWC-1 steering wheel controller. Everything works great, but I'm wondering where these 2 wires connect. I suspect they connect to the OBD2 connector, but how?

I want to run the TORQUE APP on this unit. Ive tried a BT OBD2 device paired with my ASUS NEXUS 7 with success, but I think theOBD2 device died. I'll have to get a better one.

Any help is appreciated!
[Android Head-Units] KID52:
It would perhaps be wise to post in the thread that relates to your unit.

http://xdaforums.com/showthread.php?t=2528349

The CAN wires are for CANBUS, which the Civic does not have (at least not in the UK), so they connect to nothing in your car.
[Android Head-Units] cyberpapa3:
my unit is an Ouku. It looks like the AN-21 U. I think most of these unit are made by just a few different manufacturers in China. They even similar to name brand units like Pioneer. From what I've read, most new cars after 2006 use CANBUS. for example if your DRL goes out, the notification goes over the CANBUS to the DRL light on the dashboard. I was thinking, maybe incorrectly, that the CANBUS can be accessed via the OBD2 connector.

Merry Christmas to Y'all in the UK!

here's the link to my unit. It is the Pure Android, not the dual core.

http://rover.ebay.com/rover/0/e1105...em=141122491537&ssPageName=ADME:X:RTQ:US:1123
[Android Head-Units] KID52:
Did you not just state "Capacitive Android 4.1 6.2" Dual Din"? If so, my post is valid.

Having looked at your eBay item # too, this is the wrong thread. The one I linked to is correct.

This thread is for 2.3 units.
[Android Head-Units] cyberpapa3:
Please see reply to my post above. This image varification is giving me fits!
[Android Head-Units] KID52:
Single core? Your link states "CPU: Dual Core CORTEX A9,1.2GHz frequency ".

The hardware is that of the AN-21 U.

The software is that of the AN-21 U.

Again, this is the wrong thread for your unit if you purchased the one in your link, or in fact any dual core A9 4.1 pure Android unit that is available for sale at this time, as far as I know.
[Android Head-Units] cyberpapa3:
Well excuse me!!! I saw that this thread is for

http://xdaforums.com/showthread.php?p=48822595#post48822595 so thought my unit would fit. I saw nothing in the title for 2.3 only!

Didn't think people would be so picky about the Android version. Any case the CAN wire connections should be the same regardless of unit.
[Android Head-Units] KID52:
The software and hardware are different, so things that apply to one unit, may not apply to another, hence the two threads.

I believe I answered your question regarding CAN wiring, as far as I know, the Civic does not have such capabilities.

One way that usually shows if you have it or not, is if your car tells you when a bulb is not working, or fluid is low. Does your car do this? My Civic does not.
[Android Head-Units] cyberpapa3:
yes my Civic does tell me when a DRL light is out, and when to change the oil etc. My trim package doesn't include tire pressure monitoring, but EX-L does. Also I think y'all have a Civic CTS, which I like the looks of, and we don't. I think the CTS might be similar to our Fit.

I'll try the other thread although it says in the title "rooted" in the title. Thanks for your input.
[Android Head-Units] KID52:
It says rooted because the unit has been rooted :)

Just DRL, or all lights? Usually CANBUS will indicate a fault with all external lights. Oil is also normal, what about washer fluid?

I wouldn't have thought the US and European Civic spec would be too different, despite being a sedan and hatchback respectively. It seems quite a drastic difference to add CANBUS to the US model, but not to the European model.
[Android Head-Units] cyberpapa3:
According to this link http://www.auterraweb.com/aboutcan.html 2006 Civics sold in the US do have CANBUS. All vehicles sold in the US since 2008 have to have CANBUS.
[Android Head-Units] the_tesseract:
Alright guys! Just got some time to root this baby so it will be done tomorrow!

A few more questions.

So bluetooth sucks on this thing. For real. Playing music through bluetooth is dodgy at best, sometimes it will be good (not excellent) sometimes it is just plain bad (makes my music sound like crap) and this is a major feature for me. Is there a way to make this better after root? If yes is there an app for this?

Same goes for bluetooth calling, no one can hear me. I have to scream, is there something that can be done?

I threw in a 32gb card in there that i filled up with music, the darn thing doesnt detect the music unless i copy it to inand folder... Is there something special I have to do?

A part from navigation (which is excellent) this unit in its stock form is pretty bad up until now because advertised features work more or less!
[Android Head-Units] tin2001:
Only for the diagnostics and engine stuff (which operates on a different network to user level stuff like displays and lights and such).

My understanding is the CANBUS these units is only for steering wheel controls and is read by the same service as the resistive steering wheel control inputs... Not 100% sure, but that's what I took it as.

Also, CANBUS doesn't operate as TX and RX like the wires are labelled. Again, I'm not certain, but I think the wires are meant to connect to an external adapter of some sort. Happy for someone with more knowledge to correct me of course.
[Android Head-Units] cyberpapa3:
This unit already has wires labeled KEY 1 and KEY 2 which are used for steering wheel controls. That's why I was curious about the CAN wires. I've sent e-mail to the seller asking for clarification on these wire. He's waiting for a reply from his technician and will notify me of the results.

I am hoping this is something new on this unit to hardwire connect somehow to the CANBUS, as I have just purchased it earlier this month. I'll post again when I hear from them.
[Android Head-Units] tin2001:
Same on mine. I checked voltages with the multimeter, watched the data byte counts for serial lines, etc trying to figure out if the CAN wires were any use. In the end, I couldn't confirm one way or the other, so I did the safe thing and left them alone. My car has CANBUS pins on the OEM head unit wiring, so I had good reason to want it to be real CANBUS :p

Well that'll answer whether I guessed right or not... :)
[Android Head-Units] cyberpapa3:
I checked the audio connector pinouts on the Civic's harness and found nothing labeled CAN, but I did see a "K" line, and I have no idea what it does. When it warms up today I'll finish hiding my GPS antenna and Wi-Fi dongle under the top of the dash and button everything up. I can always take it apart again. LOL
[Android Head-Units] sciallo:
Incidentally that has been recently discussed at length on the thread mentioned for 4.1 units, worth a read. If your car uses canbus for the steering wheel buttons you would use the canbus wires (not sure if you would need an adapter), the key1 and key2 wires are used for resistive type SWC some cars have. Ways to measure with a multimeter for resistive or voltage differential are on that thread as well...

Also, some of the more car specific units of the 4.1 version shipped with some apps for AC controls and more canbus related stuff. That's all I know about it as I don't have canbus (or SWC for that matter)

I will join [MENTION=1915855]KID52[/MENTION] and say, you should bring this up there (maybe after searching the thread first).
[Android Head-Units] cyberpapa3:
As suggested, I have started reading the AN-21U thread from the beginning. I'm up to page 30 at the moment. Very interesting and helpful info there, and I appreciate all the hard work y'all have done.

I believe my SWC controls are resistive. They partially worked on my old unit, based on WinCE 5.0. I tried to get the SWC to work on this new unit, but couldn't. Ended up buying the AXXess ASWC-1 and it works perfectly. I hope to get a reply from Ivy, the LIteinthebox reseller, later today, and will happily share the info, good or bad. My new unit is Generic, not vehicle specific. When I bought it I didn't pay much attention to the vehicle specific units because I liked the looks of this unit better, and I already had a 2 DIN facia/ Bezel. I had no idea there were apps to control AC. That's a great idea, and I'll have to research that option more, later on.
[Android Head-Units] sciallo:
Good, keep on reading... Just recently, in the past 5 pages or so, the whole resistive SWC was discussed in depth. You should not have a problem using it without a converter, it's just a matter of identifying it right and connecting the right wires. (usually just one of the two "key" wires and ground... but make sure there isn't vltage on the wires - or too high voltage... in other words, do read on first)
[Android Head-Units] jakejm79:
There are a lot of vehicles that use resistive style circuit at the actual steering wheel controls, but later something (be it the ECU, DICE unit, or something similar) in the car converts those signals to be sent over a bus (be it CANBUS or something vehicle specific) to the factory headunit.

If you can intercept the signal prior to being converted you should be able to connect it directly to key1 (and possibly key2 if your steering wheel controls work on two separate circuits, i.e. buttons on the left are one circuit and right another). If you can't then you will either need a CANBUS adapter that would be vehicle specific and connect to the CANBUS Tx/Rx wires or to use an aftermarket adapter (PAC SWI-RC) and then hook that up to the key1 (and possibly key2) wire(s). As best as I can tell the CANBUS Tx/Rx wires are not meant to be connected directly to any vehicles CANBUS system but rather to an adapter that would then be connected to the vehicles CANBUS system. It seems that the VW specific units are supplied with this adapter (which will support radio frequency, etc output to the MID and possibly info about the climate control system depending upon the vehicle).
[Android Head-Units] cyberpapa3:
Thanks. At the moment I have my dash all back together and every thing works, except I have to read more on how to Get TORQUE to work on this unit. Since the SWC works with the ASWC-1, I'll leave it in the dash. I have an Android friendly Bluetooth OBD 2 dongle that works great with my Asus Nexus 7, so hopefully it won't be too difficult to get it to work on this unit.

---------- Post added at 01:21 PM ---------- Previous post was at 01:12 PM ----------

Sounds like they did things right with the VW head unit. What you say about the CANBUS wire needing an adapter makes sense. Maybe they will come out with a "generic" adapter for the universal head units soon. The Key-1 wire was the only one I used with the ASWC-1 on my Civic. Don't know if this works for non US models or not.
[Android Head-Units] tin2001:
Been fiddling with my unit some more with the aim to actually put the glove box back in soon (been out for months now :p). Here's some more random brain dumps.

USB port voltages: We plugged just the WiFi adapter supplied with the unit into a bus powered hub and measured the 5v line on another port. During initial bootup, it was a steady 5v. But once the WiFi enabled and connected, it dropped first to 4.8v (not too bad) then down to around 4.6v. To confirm it was dropping due to load, we stuck in a 3G stick and it dropped to about 3.5v. Certainly explains why the USB stuff breaks with bus powered hubs - it can barely run a low power USB device.

3G sticks: Still having a lot of trouble getting the 3G to show up a signal. Tried 2 different Huawei devices (E122 and E160E) and 2 different SIM cards. Both sticks work fine in Linux, and both have their SD card slot and fake CD drive disabled. They show up in dmesg as being connected and enabled at /dev/ttyUSB0, ttyUSB1 and ttyUSB2, and no random USB errors appear in dmesg. Planning to try and interact with the serial port itself to see if it responds to AT commands, but haven't done so yet.

Anyone got any ideas here? What 3G sticks work out of the box?

Date and Time: These units should keep the time, right? Mine's been losing it on reboot - even if the car power is still on. It corrects itself by GPS once I'm out on the road but this can take a few minutes, by which time I'm often almost at my destination. I factory reset tonight, and it seems to have fixed it, but I won't call it a success until it keeps it overnight.

Latest ROM: As part of my mucking around, I figured I would update to the ROM from post 47999537... Startup time is about the same, but damn it shuts down quick. Also seems a little smoother swiping the launcher screens (both in the supplied launcher and ADW). Compared with my root-hacked ROM, that is.
[Android Head-Units] jakejm79:
JoyCon EXR

So I just wired up my JoyCon EXR to try and get steering wheel controls with any Android app, and while it kinda works, it isn't really very functional. I think the problem is that this device is Android ver. 2.3.7 and while USB keyboards are kinda supported the extended functions (i.e. media controls aren't).

For example I can map track next to a button and when I go to use it nothing happens, if I map the letter A to the same button, it will allow me to type A by pressing the button, so I know the hardware is working correctly. Just seems that media functions (play/pause/track next/prev/etc) don't work.

I assume this is because of the earlier Android version and that full functioning USB input wasn't incorporated until 3.0?

Anybody have any idea on a solution? I'm thinking either a media player that supports customized keyboard input for playing tracks, i.e. I could map P to play, N to next, etc, or is there a way to do this globally within Android, i.e. make P always play for every app.
[Android Head-Units] KID52:
A solution?

Send it to me so I can use it on my 4.1 unit? :D
[Android Head-Units] jakejm79:
I'm not sure you would want it, I think on later Android devices that officially support USB input devices that you can only have one keyboard at a time active and the EXR counts as a keyboard meaning you would have to toggle the input method between that and the on screen keyboard.
[Android Head-Units] KID52:
Actually I think you are correct.

When I have my wireless keyboard plugged in, it disables the on-screen one, and I have not found a way to enable it without disabling the wireless keyboard.

For an actual solution, is it not possible to change the key mapping? I know on the 4.1 unit there are some key map files. By default, it even has ones for the Logitech G25 racing wheel.
[Android Head-Units] tin2001:
Does the answer on this page help?:

http://android.stackexchange.com/qu...keyboard-when-bluetooth-keyboard-is-connected

I was thinking the same... Has anyone tried a plain old regular wired USB multimedia keyboard on these units?