yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] KID52:
It depends on the player.

All file explorer applications such as ES File Explorer, and Astro, have no issues seeing the files. In fact, if you choose an MP3 file and select the player of your choice to open the file, it will indeed open and play, however it does not show up in the list of available songs.

One example of a player than can see the files is Poweramp.

"/mnt/sdcard" is already linked to "/sdcard", but this is the internal USB storage, not external. Perhaps it can be unlinked, and the MicroSD card, "mnt/usb/mmcblk1p1" linked there instead.
[Android Head-Units] KID52:
Best to keep discussion for the 4.1 unit in this thread now.

My keyboard is not Bluetooth, it has a small receiver that is probably 2.4GHz, and it works fine.

Unfortunately there is no Bluetooth menu on the device. However, there are a few interesting quirks with the unit, one being that the security menu is disabled, however, if you try to enable something (I forget what, maybe storing location data or something), it tells you that a lock code must be set, so you press okay, and what opens? The security menu...

I will try installing Torque at some point, as on my phone it requests to turn on Bluetooth, so maybe it will access the menu on the unit. I don't have much hope for this working though.

Perhaps the USB device will work, but I do not have one, and do not intend on buying one at that price.

Yes, I've tried a couple that I had lying around.

If you can recommend a specific one that isn't too expensive I may trying buying to see if it works.
[Android Head-Units] sciallo:
KEEP IN MIND ALL MY EXPERIENCE IS WITH THE 2.3 OUKU but this might help:

Usb Keyboard is natively supported on all of them, if it's wireless with its own dongle (not bluetooth) that's just all it is, a usb keyboard.

For the bluetooth menu install Quick Bluetooth Lite from Market. I was lucky enough one of the dongles I had lying around worked (one didn't) mine sais "KINIVO" on it.

There is a similar app on the market to use bluetooth keyboards.

...but with both of the above it all depends on the ability to add a BT dongle, the internal one is not visible to android as I understand it (and as it was with the other units OUKU, winCE etc.

I have that exact ODBII reader mainly because I wanted a reliable one that could get the most codes... off topic here, but there is differences. Torque forums are a good resource. I haven't tried USB with it yet. There is cheap usb only out there, but I guess there is two different kinds of usb-to-serial chips... you MIGHT have one of the two installed if they included it....

Bottom line, it doesn't matter what Android supports. What matters is what modules the chinese manufacturer compiled in the kernel or included as a loadable module...

You could get a hint looking at the /home/rick/OUKU/stock/4.1/test/lib/modules/ folder...
[Android Head-Units] KID52:
Yes, exactly my thoughts.

Thank you for the advice, I will try it out soon, see what happens.

The info you have regarding the OUKU unit may well be relevant to this new one too.
[Android Head-Units] Orisai:
No, you don't have to buy such devices just for testing purposes. I have plans on buying one for my Santa Fe i45, because USB OBD2 scanners are faster and way more reliable that BT ones, and I'll need it to plug directly into my laptop or the OTG adapter in my SGS4.

Try to plug them when your stereo is turned off. I recall someone saying that you have to plug in WiFi and 3G dongles with the headunit turned off, so they get detected by Android when it boots up. Perhaps this is the case with BT dongles too.
[Android Head-Units] KID52:
Hmm, I said that. I put it in the main post too. Maybe someone said it about OUKU too, I don't know.

But yes, I do usually turn off the stereo and plug the device in before booting.
[Android Head-Units] Orisai:
Then it must be like sciallo said, kernel has to be compiled with the required modules to make bluetooth dongles work, much like Hal9k's firmware.
[Android Head-Units] donaldta:
Might want to get a terminal for android, like Android Terminal Emulator. Then you can check to see what sort of linux modules/drivers are pre-installed. For example:

$ lsmod
lsmod
blackberry 1084 0 - Live 0xbf10a000
cdc_acm 15311 0 - Live 0xbf100000
sierra 9201 0 - Live 0xbf0f7000
option 13120 0 - Live 0xbf0ea000
usb_wwan 8010 1 option, Live 0xbf0e2000
hso 29290 0 - Live 0xbf0d3000
tnx_mxt_ts 15886 0 - Live 0xbf0c9000
cp210x 10931 2 - Live 0xbf0c0000
pl2303 10925 0 - Live 0xbf0b7000
usbserial 26415 8 blackberry,sierra,option,usb_wwan,cp210x,pl2303, Live 0xbf0a8000
88w8688_wlan 362475 1 - Live 0xbf041000
tun 13189 2 - Live 0xbf037000
omap3_isp 97716 0 - Live 0xbf014000
omap_hsmmc 14041 0 - Live 0xbf000000
$

This will give you an example of modules installed. In the above example is from the Parrot Asteroid Smart. The output gives you an idea of the sort of devices that you'll be able to use with the unit. For example, there are the cp210x and pl2303 drivers for Serial UART to USB devices. So, for example one could use a USB ODB2 cable as long as they use either a Prolific or Silcon Labs UART.

Something that is not well known is that Torque Pro supports USB ODB2 cables. The product linked earlier from Amazon is an ODB2 scanner by Scantool which is a professional model. (Analagous to buying a Fluke Multimeter vs an Innova) They do have another model that costs a little bit more and supports USB and Bluetooth or even WiFi if you prefer. But, there are some less expensive knock offs that you can get for less a fraction of the price. So, if you know the AN-21 U supports a particular Serial to USB driver then you might be able to use one with Torque Pro. The nice thing about USB ODB2 cables over Bluetooth ones is that the data stream is closer to real time and has less lag than a BT ODB2 adapter around the same price.

Some places hide various menus from the settings control panel, but you can often them bring them up using intents through Activity Manager. However, finding the available intents sometimes requires root but you do not need to be root to execute them. For example:

$ su
su
# dumpsys package com.android.settings | grep BluetoothSettings
dumpsys package com.android.settings | grep BluetoothSettings
4068b7e0 com.android.settings/.bluetooth.BluetoothSettings filter 4068bc48
4068b7e0 com.android.settings/.bluetooth.BluetoothSettings filter 4068ba78
4068b7e0 com.android.settings/.bluetooth.BluetoothSettings filter 4068ba78
# exit
exit
$ am start -n com.android.settings/.bluetooth.BluetoothSettings
am start -n com.android.settings/.bluetooth.BluetoothSettings
Starting: Intent { cmp=com.android.settings/.bluetooth.BluetoothSettings }
$

However, not all Bluetooth software conforms to the Android standards and will force close if it doesn't. In most cases if a Bluetooth driver is installed then a good app to get is Bluetooth Auto-Pair. It allows the manual settings to pair various devices even if the manufacturer implements an artificial limitation on the devices that they will support.
[Android Head-Units] KID52:
You definitely seem to know your stuff!

That is an extremely informative post, thank you.

I'll take another read tomorrow and do some tests on the unit, see what I can find out.
[Android Head-Units] donaldta:
This is actually a pretty bad blanket statement. It actually depends on the Linux modules included with the Android device. And in fact, I played with an Android TV device that had fuse.ko modules installed and supported NTFS partitions. The best way to tell what sort of filesystem that your Android device supports is through "/proc/filesystems".

$ cat /proc/filesystems
cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev sockfs
nodev usbfs
nodev pipefs
nodev anon_inodefs
nodev devpts
cramfs
squashfs
nodev ramfs
vfat
msdos
nodev mqueue
nodev mtd_inodefs
nodev oprofilefs
nodev ubifs
$

The first column signifies whether or not the filesystem is currently present on your android device and the second column shows all the various types that it supports.

---------- Post added at 11:06 PM ---------- Previous post was at 10:49 PM ----------

While you're at it, you might consider installing SRT AppScanner. If the device is vulnerable to Master Key either exploit bug 8219321 and/or 9695860 then there's a good chance that Cydia Impactor can root your device.
[Android Head-Units] KID52:
I thought you needed to connect your device to a PC to use Cydia Impactor? Also, not sure if it would be required, but USB debugging is password protected.
[Android Head-Units] donaldta:
Well, technically you don't have too. It works off of Android Debug Bridge and can work over WiFi or USB. However, it does need debugging to be enabled. I missed the part that it is password protected. However, the masterkey scripts might still be able to help gain access to root if it hasn't been patched on the device.
[Android Head-Units] bmj67:
1.3 Works We Have ROOT

Thanks WonderEkin

also deleting /data/local.build fixes the lag issue

Now all we need is a usb bluetooth module so that we can use a usb bluetooth stick to run our obd2 scan tools and torque
[Android Head-Units] donaldta:
Why not use a USB to ODB2 adapter? The response is faster and it is more secure, less expensive and won't run down your battery while the ignition is off. According to usbserial (which was listed in your /sys/module directory) documentation, it should have compatibility with the Prolific PL2303 Driver.
[Android Head-Units] chris.r.r:
Great work, guys! Thanks a lot! :good:

Now it's time to get one, I'm really looking forward to mod the UI. :D
[Android Head-Units] JohnnyTightlips:
Awesome, looks like I will be getting one too. I know we can make this device so much cooler with root.
[Android Head-Units] KID52:
This is great news to wake up to, thanks again :)

I'll be testing this out and updating the main thread with this guide.

What system version was used to make this? I'm assuming it shouldn't matter too much?
[Android Head-Units] WonderEkin:
Any version should be fine, it won't let you to install the apk if the master key is not match.
[Android Head-Units] donaldta:
To be precise, isn't really that the RootMyAN21U.1.3.apk will not install if its keystore signature is different from the SettingsProvider.apk on the destination device? I know this exploit is known as the "masterkey" but there's no actual master key involved. Rather, the process disguises alternate content behind the appropriate keystore signatures of the original APK (that bmj67 provided) to run modified code with a privilege id, system, on a particular ROM. So, your apk is more like the Trojan Horse with modified files (ala Greeks hiding inside) so the code can run inside the system (like the Walls of Troy).
[Android Head-Units] KID52:
Got mine rooted, but wasn't as smooth as it could be.

First issue is that the icons and menus were black so I couldn't open the application again for step 2.

Managed to reset to factory and install again, this time put an icon on home screen, ran app step 1, rebooted, opened app, no step 2 option?

Connected via ADB fine so pushed su to the device as suggested if step 2 fails, and ran the ADB commands then installed SuperUser app on the device.

Couldn't find local.build, but there was local.prop which I deleted and that took the device back to normal speed and no black icons.
[Android Head-Units] bmj67:
The black screen is what mine did earlier. For some odd reason though if I open the TV app and then hit home it would go to normal screen. So I just found to open the TV app first then run the root apk then restart. The unit would restart into TV because it was last app. I would just hit home a few times and screen would be normal.

Also local.prop is what I deleted as well.

At any rate a few little bugs are worth root for me.

[MENTION=5389783]donaldta[/MENTION]

I have both Usb and bluetooth obd2 tools. They are the cheap ebay specials but the do their job.

Bluetooth is secure as you must have the ignition to On position to make the device connect

As far as power concerns, there are a few on ebay that have power buttons or sleep mode.
[Android Head-Units] KID52:
Makes sense, before when I tried it I had the AUX app open and experienced a similar scenario, this time after factory reset it was the radio. I will try it again later.

Agreed, it's a small amount of hassle to get root access.
[Android Head-Units] patrickoneal:
Great work on the root WonderEkin, KID52, and bmj67, and anyone else I may have left out.

I just ordered one without the TV tuner, it was down to $299 on ebay:

http://www.ebay.com/itm/Android-4-1...eo-Radio-GPS-WiFi-3G-CAPACITIVE-/111230514418

When it gets here, I'll confirm that the CPU is actually 1.2ghz.

What are you guys using to run these on the bench? I've never invested in a good bench top power supply, but I don't want to spend a lot.

I plan on disconnecting the internal microphone and adding a connector for an external mic, and changing the front LEDs to match my dash. I'll try to take pictures of the process if anyone is interested.

I'll also look around on the mainboard, there might be a debugging port or pads for one. I don't really see needing it now, but I'm curious.
[Android Head-Units] KID52:
Will be interesting to know about the CPU.

I'm using a variable desktop power supply from Maplin. Haven't seen the device use much more than 3A, and that was with the speakers turned up. As it sits now, it's around 1.5A. So basically any 12v up to 14v or so power supply that can handle 5A or should be fine.

Would be interested in pictures of your progress, I'm also going to be adding an external microphone, but leaving the LEDs.
[Android Head-Units] JohnnyTightlips:
I just mod an old computer power supply to do all my testing of other head units. I would also be very interested in seeing different color led's and the external mic. Hands free is not good if the mic stinks.
[Android Head-Units] KID52:
This is a good cheap (maybe free) alternative if you don't want to purchase an actual bench supply.
[Android Head-Units] sciallo:
Great job guys! hopefully just in the nick of time for me. I'll try to see if I can get a 4.1 unit as a replacement for the one I returned :fingers-crossed: ...hopefully it's not too late.

I'm also curious to know about different models, is the same firmware going to work on 1.0ghz and 1.2 ghz units? is this one the same?

http://www.ebay.com/itm/Android-4-1...yer-BT-Stereo-Radio-Ipod-RDS-NEW/251391153474

I'll ask more later about this as I'm working on the wiki pages...

I use an old computer power supply, on the hard drive plugs, black wire is negative, YELLOW is 12V. and red is 5V (I use that to power up a powered usb hub). To get the PSU tu turn on just make a little jumper with wire or a paper clip between the green wire and any black on the motherboard plug. Some say you are supposed to have a load on the psu at all times, I never really concerned myself with it but I don't really keep it turned on without it powering something anyway. For more, just google it :)

Wether I get the 2.3 or the 4.1 I also plan on a few hardware hacks including led and ext. mic. ...More involved hacks later once I get into it with IOIO. What car are you putting this in? what color? Getting confused with color and options in LED choices (forward voltage current and luminos intensity...

For ADB, I ran into something that could be interesting (not sure if it applies to our units, but it might be worth a try...)

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

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

http://hackaday.com/2013/11/17/getting-a-shell-on-any-android-device/

I haven't yet read much about it, so forgive me if it's far-fetched, just thought I'd share thoughts.
[Android Head-Units] donaldta:
You must have had better luck than I have had, I've purchased and returned almost a half of a dozen of these cheap Bluetooth adapters from eBay. Most cars' ODB2 port is powered by 12v constant and not 12v switched. So, in the ones I have tried, the Bluetooth pairing required no physical access to the unit itself and remained pairable regardless of the ignition setting.

If you don't want to spend any money and have a spare computer lying around you can use its power supply. I've used old 20-pin AT & 24-pin ATX PC power supplies to power up car radios before. The yellow wires from the accessory leads provide 12V DC. All you need is to jump the Green - Power Supply On (pin #16 on ATX or pin #14 on AT) with Black - Ground (pin #15 on ATX or pin #13) to have it power up.
[Android Head-Units] jakejm79:
In my experience with BT OBDII dongles they do remain powered on with the ignition off but it is such a small draw that I have had no problem leaving one permently connected and letting the car it sit for days.

Regarding security (again in my experince) you are unable to connect to one unless the car is providing the dongle with an active canbus signal and that only happens with the key in the car.
[Android Head-Units] KID52:
That has been my experience with the cheap ELM327 clone I have; not able to connect when the key isn't in slot 1 or 2. Any obvious signs of life, eg LEDs, are off when the car is off. I don't know if the car is providing a constant 12v to the OBD socket, but the diagram donaldta suggests that it does.
[Android Head-Units] donaldta:
That is certainly interesting perhaps the reason they remained pairable on my cars is because they don't use CAN-bus but PWM. Which I guess could be active regardless of ignition key depending on the car model/manufacturer. I guess this can be a condition where your mileage my vary (YMMV).
[Android Head-Units] jakejm79:
I agree this is something that would vary based on car manufacturer, I doubt it would be hard to wire in a relay for the constant +12V to the OBDII port that was closed via the ignition +12V source, if it is something you are really concerned about. That being said I much prefer my USB OBDII dongle.
[Android Head-Units] mcskeezy:
Will rooting affect the stock radio app?

I've got a very similar unit, which I started to review on the thread below.

http://xdaforums.com/showthread.php?p=50072764

I would like to root my device using the method that KID52 provided, however I noticed that his stock radio app is different than mine.

http://www.aliexpress.com/snapshot/306445356.html

If I root the device using the method he provided, will I still retain my radio app, or will it be downgraded to look like the one in KID52's post?
[Android Head-Units] KID52:
See reply in the other thread.
[Android Head-Units] donaldta:
Nope. Because unlike some of the other methods of accessing root on other devices which often requires a full re-write of the system image, the method of rooting the AN-21U with the RootMyAN21U.apk is exploiting a security hole known as "Masterkey exploit". This allows the /system/xbin/su binary to be copied onto the unit without altering anything else on the system.

Still again, this is something that you could have brought up in the this thread without resurrecting the other one.

P.s., the rooting method was provided by WonderEkin not KID52.
[Android Head-Units] sciallo:
Thanks [MENTION=5389783]donaldta[/MENTION] that answers most of it and it's all correct.

I did get in touch with someone at Tonghai create, through qq, a chat program very popular in china, i guess. And I also asked about a board to OUR_STYLE, Part of the issue is shipping the unit back costs about $80, If I can get a replacement board for about as much, i would rather do that, and I can keep the old board to mess with :) If one of the two should decide i should get it as a warranty part that would be nice too...
[Android Head-Units] gpmg762:
Tapatalk 4.1.4.3 is okay, after that the search is broken.
[Android Head-Units] tdt038:
Allison is a woman, she also known as Denver:

xttp://www.aliexpress.com/store/415121
[Android Head-Units] jpapadami:
:laugh:Thanks for the clarification and for the link to the store.

Just made the correlation between the email name and the store name in Aliexpress.
[Android Head-Units] vmontagut:
Hello.

I am hesitating in buying these two machines:

w w w.aliexpress.com/store/product/2014-Newest-Pure-Android-4-1-Car-Dvd-Gps-For-Toyota-Kia-Nissan-Tiida-Qashqai-Sunny/203819_1580396624.html

w w w.aliexpress.com/store/product/2014-Newest-2-Din-100-Pure-Android-4-1-Universal-Car-Dvd-Player-Pc-Gps-Navigation/203819_1580294879.html

The only differences I see are visual, because the features are the same. I like the 2nd machine, since they have more buttons and there you need not go changing on the screen. On one hand, I like more the 2nd machine, but on the other hand, I prefer to have firmware updates.

But I do not know if the firmware of this post are valid.

How do you see?

Thanks You.
[Android Head-Units] Prdie:
Hello I need help as well. I'm trying to find a replacement for my OUKU and my key attributes are now - capacitive screen, volume button and green illumination. I was persuaded that only S150 and old WINCE units have changeable illumination colors (at least 2.3 OUKU have not), but I found today this :

http://www.ebay.com/itm/161171651999?_trksid=p2055119.m1438.l2649&ssPageName=STRK:MEBIDX:IT

It seems to me that it's and AN-21 but this seller is advertising changeable illumination. Is this AN-21 ? And do all other AN-21 have changeable illumination ?

Thank you all for the help
[Android Head-Units] mcskeezy:
Can't get TorquePro to launch on boot

Thanks donaldta, I went ahead and rooted it, whole thing went very smoothly.

My reason for rooting, was that I hoped it would allow me to set default permissions for apps, something I am currently not able to do with this unit.

My ultimate goal is to have the TorquePro app launch on boot, and get rid of an annoying "Do you want to use this USB OBDII adapter by default?" popup that comes up every time I launch the app.

I've tried automating the process with Tasker, but I can't seem to even get Tasker to launch on boot, I always have to load it manually once the device has booted.

Anyone got any ideas? Or had any success getting apps to launch automatically on boot?
[Android Head-Units] typos1:
This has all been covered before - search the thread
[Android Head-Units] mcskeezy:
Launch App on Boot

In case anyone is having the same problem, Tasker still doesn't work, but an app called "Autostart - No Root" seems to accomplish the task of launching an app on boot, unfortunately, the app launches in focus and not in the background (which would probably be preferable for a logging app like TorquePro).

This being said, I still haven't found a way to set default permissions and have them remain after the device is rebooted.
[Android Head-Units] donaldta:
Interesting. Care to share on your epiphany?

As far as I can tell by the specifications they are both the AN-21U. This means that the same system board is inside both models. The only difference is the faceplate is different between the two Universal variants.

I think they are supposed to but compatibility with the color change depends on the LEDs inside the faceplate and if the MCU has the correct firmware update. This is basically what led [MENTION=3081576]sciallo[/MENTION] to try and find the correct MPU update to get it to work but ended up frying the MPU.

Are you sure that is the syntax? Mind grabbing a screenshot? Are you sure it isn't "Which app you would like to start for this USB device?"

I have had plenty success getting Tasker to load upon boot. You just need a profile that checks for "Event: System: Device Boot" then link it to an task to "App: Load App: Tasker". After you created it, make sure both the task and profile are enabled. This profile should now be called when the boot complete broadcast is sent after Android has completed loading.

To test it, use the following command in a terminal app or adb shell, "am broadcast -a android.intent.action.BOOT_COMPLETED". This will simulate the "boot completed" broadcast and all the apps that should respond to will react appropriately. This includes your Tasker profile.