yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Orisai:
I think the chinese are well aware of what we're trying to do, judging by what some people accomplished with the previous gingerbread models, and thus blocked every function that could let us break through, and root the device. I hope they didn't patch their source against exploits used by Cydia Impactor or Kingo ROOT.

Too bad I don't have a headunit yet, as I'm waiting for one made for the 2013 Hyundai Santa Fe (i45). I'll try anything I can once I get one.
[Android Head-Units] sciallo:
yeah, god forbid we "break in" and fix each and every little quirk and issue we can like it was done with the gingerbread units... It would be a shame, they might have to produce too many to keep up with demand...

I don't get it.
[Android Head-Units] KID52:
Sorry, I mentioned it in my review, and I think in a post in the other thread, but of course that would have been lost. I'll add this bit of information to the main post.

I'm willing to test stuff out on my unit if there is a possibility it will work, hopefully no harm in trying...

Yes, I have asked many times for root and USB debugging password, but apparently the firmware is their "technical secret" and they cannot reveal it. They do seem to have spent some time blocking access to every part of the unit possible.

Exactly, why should we not be allowed to do this? It is even possible with all the larger manufactures...
[Android Head-Units] Orisai:
They want us to pay more money for "optional" features which today are standard in car stereos and should be included in the base headunit in the first place. OBD2/CAN bus scanning among them.

Even Kenwood's Android stereos, which are way more restrictive, include CAN bus reading as a base feature.
[Android Head-Units] Defender666:
Is the FM reception ok ? Most chinese radios have crappy reception?

Can DVB-T stick be used?

especially this: http://feilen-stolz.de/wavesink_android.php

what is the manufacturer website?
[Android Head-Units] bmj67:
bluebox results

I ran bluebox on my unit and it says unpatched and vulnerable to bug 8219321 and 9695860. Though usb debugging is locked by password. If we could get the password it would open some options
[Android Head-Units] Orisai:
You should try this app...

https://play.google.com/store/apps/details?id=com.sherdle.adbwireless

Although unstable, It claims to allow ADB access through wifi without root and doesn't mention enabling debug mode at all. If it really works, it might let you drop the su binary into /system/xbin/su then take full control by installing either SuperSU or Superuser.
[Android Head-Units] Defender666:
Anyone can tell something about radio FM quality?
[Android Head-Units] Orisai:
It depends on your car's antenna. I haven't tested one of these headunits yet, but I've installed plenty of different ones from major brands and the car's antenna really makes the difference.

If your car doesn't have an external (aerial) antenna, then you can add one that's installed on top of the windshield, inside the car.
[Android Head-Units] chris.r.r:
I did some research on the tuner component they used for the 4.1 unit:

It's a NXP TEF6624 (Philips) which is ok, it's actually a tradeoff between component costs and performance.

NXP states in their product description (NXP description)

Therefore, I assume that the FM reception - even if there is a good antenna - will be only OK but probably not as good as with some of the manufacturer radios (e.g., dual tuner, better noise reduction)...
[Android Head-Units] Defender666:
The car has an excellent antenna on the roof, the problem is that most chinese CAR Stereo Units have very bad FM reception.

I investigated some of the so called China-RNS devices and most had improper grounding on the FM part. In china they don't test it while driving, most of the manufacturer don't have the proper cars to test, they only play around with the devices on the desk.

BTW can anyone state what manufacturer company is this device from. Do they have a website. Most guys arround ebay and ali are only reseller. However someone here stated he has contact with the manufacturer.
[Android Head-Units] Orisai:
No one knows for sure who builds them, probably because headunit manufacturers don't speak English at all. The only contact [MENTION=1915855]KID52[/MENTION] and I have, is their sales representative or reseller Peter Chan, through skype (pumpkin_cool).

There are two chinese car stereo manufacturers? who have websites:

RoadRover (www.roadrover.cn/e) and Isudar (www.isudar.com).

No idea where they sell their products, as both of them doesn't have an e-commerce platform built in their websites, or ebay/aliexpress links to their stores.
[Android Head-Units] sciallo:
Would be interesting to see if that could work.

- have you tried https://play.google.com/store/apps/details?id=me.tennkia.apr&hl=en to enable debugging?

- Question remains do we have a valid USB port or are all the wired ports HOST only and useless as ADB like it was on the other units? It looks like the app/software do need a USB connection the first time to configure the whole thing...
[Android Head-Units] donaldta:
Bluebox gives false reports. It is better to check with SRT AppScanner. Saurik, had posted in his blog how to manually exploit these bugs on his blog but without ADB debugging access (USB or WiFi), you'll need someone who can translate his instructions using a local copy of busybox and telnet running on the unit. I had asked [MENTION=1915855]KID52[/MENTION] to give it a try but he never got back to me.
[Android Head-Units] bmj67:
Srt app scanner says the same thing and adds 9950697 bug .
[Android Head-Units] donaldta:
That's good news. Though I have bad news. I was in the middle of rewriting the instructions then I came up on two commands which cannot be translated, "adb jwdp" and "adb forward". So back to the drawing board of getting the debugging password or maybe find some way around it. Has anyone tried, "Cobaaja08x" or "Cobaja08x"? I know this is a far stretch but its the one used for the Andromax U2 (Hisense EG98).
[Android Head-Units] sciallo:
Please help me understand the "password" thing... does it ask for a password to go to the developer menu? Or when you try to enable debugging?

I already asked and I'll ask again. Has anyone tried https://play.google.com/store/apps/details?id=me.tennkia.apr&hl=en ?
[Android Head-Units] bmj67:
Passwords you suggested do not work. As far as usb debug app from link it just takes you into developer options page. Developer options are unlocked the password is needed to enable usb debugging. When you hit the checkbox it wants a password.
[Android Head-Units] donaldta:
If it is like the Andromax U2, it prompts for a password when they try to enable debugging.
[Android Head-Units] PsychoMcSatan:
Mine was part of the breakout cables. There's was one plug that broke out to mostly the bare wire leads, another that was mostly RCAs for audio and video out, and a third that has iPhone plug, AUX in (left and right audio and video), as well as this female 3.5mm. I've used it with phone calls but nothing else.
[Android Head-Units] sciallo:
Pics would be awesome.... if you feel like it, also of the inside, where is that hooked up?

I believe that's part of that lingering market issue we should figure out...
[Android Head-Units] Orisai:
Anyone having market issues, such as "incompatible with your device" apps, should try Market Helper.

I'm running a Genymotion Android 4.1 x86 image, and some apps won't install on a virtual machine, so I gave it a try and it worked.

Of course, use it at your own risk. I'm not sure if Google is capable of detecting this kind of spoofing.
[Android Head-Units] sciallo:
I am pretty sure that was the solution for the OUKU too...
[Android Head-Units] jakejm79:
I found sound hound to work on my Ouku with an external mic. Voice Search also works with it as does many voice memo/recording apps.

I can get Shazam to work once after restoring a backup, but after that it fails saying it can't connect to the server, but for purposes of working with the mic it does work.
[Android Head-Units] kmtk:
Ordered the unit from newdealestore2012, can't wait to root and start tinkering. Was wondering what's the colour of the LEDs? Here's a link to the specific unit.

www[dot]ebay.ca/itm/111233072287?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1439.l2649
[Android Head-Units] KID52:
Yea after posting I downloaded Sound Hound apk and that seemed to work. Although I think the microphone I purchased is not very sensitive as I had to place it quite close to the speaker for it to get a hit on the song.

Blue lights, cannot choose anything else for this style. Unless you change them yourself of course.
[Android Head-Units] KID52:
So it appears you can use a USB webcam...

I guess if you find an app that can record from this, you could use a webcam as a DVR. However, trying to find a webcam with a wide angle lens, and then the bulk of the webcam itself, plus the price, you're probably better off using a dedicated DVR anyway.

I tried the "Dashcam" app, which displays my webcam image, but was unable to record. This could be down to the 99p webcam, I don't know.

In other news, I downloaded "Freezer" which works to disable the stock apps - they are easy to tell, the icon is displayed and they are titled what they are, so "Music" "Radio" etc. This stops them from trying to open, but still the steering wheel controls don't work, so it's not ideal if you use navigation, and want to change songs.

I've also added a matte screen protector (little tip here, ones for Wii U controllers are a perfect fit ;)), which although I have not tried it in the sun, from past experience of matte screens, I think it will work better. For me, I also prefer the touch compared to a standard screen or protector. Of course the tradeoff is that the screen doesn't look as clear, but given you aren't going to be sat there reading a book in size 10 font, I don't think it's an issue.
[Android Head-Units] sciallo:
That's good news... Doesn't torque have a dashcam recording feature that also overlays gauges on the video?

Does skype see it? LOL, skype while driving...

What camera are you using, what module does it use?
[Android Head-Units] KID52:
I have no idea. But the app has to specifically use a USB camera. I tried Skype, but it does not work with USB cameras apparently. That is what I read from a quick Google search.

The camera is just a generic one, don't know any details.
[Android Head-Units] KID52:
Does anyone know how I would go about monitoring for the steering wheel control inputs (via software, don't want a hardware solution), and then eventually assigning them to perhaps a keystroke? (I assume this would allow for best compatibility between music apps).
[Android Head-Units] jakejm79:
If you had (or wrote) a tasker plugin that monitor for the inputs, you could have it change a parameter to a specific integer depending upon the button pressed, then another task that would perform a simulated media button press (or anything else you wanted) when said parameter was changed to a certain integer.
[Android Head-Units] KID52:
Sounds relatively simple... But... I wouldn't really know where to begin on attempting to monitor for the inputs, I have no idea how they are handled, or where to find out.
[Android Head-Units] sciallo:
I think this was tested with the ouku, and the hardware buttons and steering wheel buttons didn't show up as keystrokes in android. I hope they do trigger something in android but they could be part of the non-android hardware, it would communicate with android through the I2C those boards communicate through...

Perhaps This app could help... I was planning on trying that once I got mine. See if it gives any clue...
[Android Head-Units] bmj67:
Do you have the buttons wired up correctly. Wiring diagram shows 2 wires for steering wheel controls. I'm assuming they are + control wire and the 2nd wire says only connect when the car has 2 + signal wires. And did you set them in extra settings.
[Android Head-Units] KID52:
Buttons do not seem to send any intents that the app can pick up.

You appear to be correct, a the settings for the buttons are set in the extras menu, however upon factory reset these are saved, suggesting they are not part of Android, but of the other hardware. Again, using an app to test for keycodes, they show nothing when pressed.

Of course I have. The controls work fine with default apps, I am trying to get them to work with other apps, eg Poweramp.

Now we have root and can disable stock apps, it makes using your own music app extremely viable, except the non-functioning steering wheel controls which are fairly important if you want to change tracks.

Volume works fine as that is a general Android function, as does any other such functions, back, home, etc. But stock-app seemingly-specific functions, such as next, previous, fast forward etc, do not work with anything but stock apps.
[Android Head-Units] jakejm79:
You can map the home, back, menu buttons to the steering wheel controls so android must be able to see them. I believe there is an apk that handles the steering wheel controls, though I'm not sure if that is just for configuring them or for parsing the inputs too.
[Android Head-Units] KID52:
Hmm yes, Android must be able to see them otherwise they wouldn't be able to do any function right? But it cannot see them in the sense of a basic keyboard keypress.

There must be something proprietary that is handling the hardware input and giving the desired function in Android, maybe an APK as you say, or maybe something deeper in the system.

Now, taking the example of the "next" button, is a global message being sent, and the individual apps such as music picking this message up and acting upon it, or is the controller more advanced, and is able to tell which application to send the message to specifically?

I've been taking a look through the system apk files, but can't find much. Only thing I noticed was an app (com.tw.service_a5a4.apk) that appeared to contain things related to CANBUS, eg aircon control and parking sensor display.

Anyone that wants a copy of the 2.6.62 system apps folder can download it from here.
[Android Head-Units] sciallo:
Someone suggested looking at the sbd app a few pages back, but no, android doesn't necessarily have to see anything about those keypresses I'm afraid... It can all be handled by the underlying hardware and it's own firmware... The same firmware that works the same on < $200 units without android... Those have buttons and steering weel controls too... The android apps simply display the status of those and offer additional on-screen "buttons". Not saying that is how it is for sure, but it might be...
[Android Head-Units] KID52:
I can't find that app, from what I read, he said that it contained all of the stock apps? Whereas I found these to be split up into different APK files.

I see what you are saying, so it is possible that Android never sees some of the presses (surely it has to see at least home, and back presses though). But it could be possible that the other functions, next and previous, are handled elsewhere.

Really need someone who knows what they are talking to give some input :)

I'm just having a bit of a waffle...
[Android Head-Units] VMontreal:
Firmware 2.7.26

Anyone tried this firmware 2.7.26 from the Russian forum (4pda - topic 522762, st=800)?

Thanks.

-v
[Android Head-Units] juninyo:
Hi, I tried with another sd, I've formatted, I downloaded the update again. I can not update. That does not happen, sooner if I could upgrade. Since I put the version 2.7.9 update not let me. One thing I've seen that has changed is the path where is located the sd, was previously more or less on the route sdcard/mnt/usb/mmcblk1p1 and now he is on the route. mnt/storage/extsd1, Can this be the reason?, How can I change it back?
[Android Head-Units] Skratchuk:
Great info Miwer it makes me wonder if my device had the wrong MCU which was 4.2.13-1-10-2101 in the first place.

Can anyone help me identify this model please or the correct mcu.
[Android Head-Units] Miwer:
I would assume that too... That is, after all, the rule that Model Choose function lives by ;)

I think they are just binary - there are many different BCD systems, but I don't think java/dalvik uses any that would cause the nibbles to be "flipped around" - So 21 = binary 0010 0001 = RDS and Color

I would recommend that too. As an example: 4.2.15-1-10-2101 you should at least make sure you use firmwares that matches your original firmware on the numbers marked with red.

Not really - sure some of them I can guess upon (like RDS, Sleep, Color and the 1din/2din), but I don't know what effect they might have, if any.

For example my MCU has the Color feature, and I have the color app, but it doesn't do anything. The hardware buttons LEDs in my unit are green, and they do not change color :confused:
[Android Head-Units] Skratchuk:
Can/has anyone got or recommend a cover for the 2 din unit to put over it when not in use.
[Android Head-Units] proenergy:
Hi,

is the AN-21 U the same one like this (see attached Foto). Can I update the System Version 2.7.11

Thx
[Android Head-Units] Skratchuk:
Yes you can upgrade both system & MCU versions on your unit.
[Android Head-Units] m00n13:
2.7.26

I used it to update from 2.7.4 which was the stock system for my unit.

I have a Witson W2-9000A which is just another AN-21U variant. Funniest thing is that the HW info on the manufacturer's site is wrong, they claim it's a i.mx535D unit :)

Anyway, update went flawless. I now have the new radio interface and the new launcher. I managed to root using Baidu, Root_My_AN did not work for me.

Now, if only I could figure out why TomTom does not see satellites...Sygic, Igo and Google maps all work flawlessly.
[Android Head-Units] Cebulon48:
Can someone please post a link to the Baidu root apk .

Maybe this works, trying to root my T7019a ;)

Thanks

Oliver

Gesendet von meinem GT-I9100 mit Tapatalk
[Android Head-Units] VMontreal:
So, you were able to first update then root... In my case (I only updated from 2.6.70 to 2.7.11), I had to root first then the update worked. Without rooting, the system update showed "Update start" followed immediately by "Update end" and acted like it did not see the files on my MicroSD.

Just checking... was your TomTom working in 2.7.4 ?

Thx.
[Android Head-Units] cat2115:
Thanks for the info. I would like to get my hand on this experiment but I don't understand. Please write guide if you have time.

I think, is this what you mean.

- Flash system 2.7.11 to the unit then root for root access

- Go to system/etc/mcu and look for zip file: Question: What zip file should I look for since there are a lot in it? My stock unit came with MCU 4.2.6.1-7-10-6501. I have 2002 Honda Accord EX

Or i need to open the unit and actually look at the chip on the board to identify the real mcu? I will open mine this wkend since i had to replace the screen.
[Android Head-Units] proenergy:
Which MCU and Sytem version is the most current for that unit
[Android Head-Units] MFKinSINY:
If your unit came stock with 4.2.6.1-7-10-6501 you're in trouble (joking) because there are one too many digits in the software version number.

I am going to assume that you meant 4.2.6-7-10-6501

Depending on which firmware version you most recently updated to, find the highest software version

(the numbers BEFORE the first dash i.e. 4.2.13- or 4.2.15- or..... you get it?)

The red number -7- is the HARDWARE version. THIS should never change (unless you swap the mainboard or some other significant component inside and the HW version is newer or older)

The -10- is the make/model of your vehicle. I don't know for sure the significance, maybe graphics (wallpapers, boot animations specific to the make/model of your vehicle), and can bus protocol possibly. 10 is for Volkswagen. Being that you own a Honda, you "MAY" prefer -20- (but PLEASE DO NOT trust entirely in my statement)

The LAST FOUR DIGITS -6501 are specific to features & processing chips inside your unit. I strongly suggest you DO NOT stray from those very significant numbers, especially the last two (01) for the two chips, otherwise you might lose audio and/or radio or have affected audio quality etc. etc.

According to the bitmasking scheme provided by Miwer, and how he explained it to me in post #3984 the "65" is 0110 0101 so your "features" include:

(bit 0) RDS, (bit 2) AD, (bit 5) COLOR, (bit 6) BC6

All this being said, you "should" be ok with 4.2.13-7-10-6501, 4.2.15-7-10-6501, 4.2.13-7-20-6501, 4.2.15-7-20-6501

BLUE is the software version. RED is the hardware version. GREEN is the make/model of vehicle.

Maybe you can help me?!?

Can you identify what exactly is AD, and what is BC6?

I'm pretty sure you might have an app for these features. When I changed from -0101 to -2101 I got a new app for adjusting color of the LED's and it wasn't there before.

Good Luck
[Android Head-Units] ionutlup:
Baidu root

Baidu root works great on our system.

Run and install Super SU from GooglE Play

https://www.dropbox.com/s/72b1jj5nnritn9q/BaiduRoot_2001_EN.apk
[Android Head-Units] m00n13:
tomtom

That's right, update worked without root.

TomTom did not work on 2.7.4 either. It is worth mentioning that I was unable to install TomTom from Google Play (licensed copy), it said this unit is incompatible. I had to use a downloaded APK. Install had no issues but it's just not working. According to TomTom website it uses Android location services and should get a more or less accurate position from WIFI only. I am going to try older 1.3 versions, see if it helps.
[Android Head-Units] PsychoMcSatan:
Awesome work!

I've got a couple observations to add as I've struggled with multiple MCUs trying to troubleshoot bluetooth and knob issues.

My unit came with 2.6.1-7-10-2501-1. It showed up with that extra "-1", but such an MCU was never included with any system version. I went with one that did not have the "-1" and it caused my knobs to work reversed, but otherwise perfect. That would be fine since they recently introduced the option to reverse the knob direction, however, they stopped including "-7-10-2501" and an updated MCU is required to allow that knob reversing function.

I tried "-7-10-6501" which was a perfect fit except for bluetooth not working. Knobs were reversed, but they could be switched. Since bluetooth is a must have, I had to go with "-10-10-2501". Bluetooth works, but knobs aren't just reversed, but crazy wonky so they are unusable.

My binary expertise is a bit off so I'm not sure which bit is switched when 'cc' changes from 65 to 25, but it seems like bluetooth. And 'a' clearly helps map knob, and perhaps button, functionality.
[Android Head-Units] Miwer:
That does seem odd indeed. The way the code works is that it divides the filename into groups divided by "-", and works on them from there. I could see the code using the four first groups. I did not see any reference to a 5th group, so I don't know where that extra -1 is coming from in your case. It could be some special tweak from the factory for your model, that they may wanted to somehow show in the version number, without it having any significance to the updating logic. Don't take my word for it though, I'm purely guessing here, lol :silly:

65 = 0110 0101 = RDS, AD, Color, BC6

25 = 0010 0101 = RDS, AD, Color

Are you saying that your bluetooth works with 25, but not with 65?

Maybe BC6 is some special variant of bluetooth chip (maybe even the one supporting OBD)?

I don't have BC6 in my mcu feature list, but I do have bluetooth working, although not the one supporting OBD. I'm too cheap to pay additonal $50 for that feature. :o

Can we have someone with OBD supporting bluetooth to verify this, by posting their MCU versions?

/Miwer
[Android Head-Units] Skratchuk:
I have read that buttons can be re mapped in extra settings I have tried to do this but it doesn't change anyone know how to change preset buttons?