yashsingh1/xdaforums huggingface dataset:
[MTCB Android Head Units Q&A] typos1:
I m not a buyer of it either, but have been avidly following this thread, the AN-21U one and the WD-8801 one for months, trying to decide which to buy, now that the bootloader is unlocked, this one seems to be edging ahead. Which is the other unit youre referring to, webdude ?
[MTCB Android Head Units Q&A] pakidermo5000:
ODB2 ? torque ? you mean?

yes, that is what I will do. Keep an original copy, so i can always get back. Anyway, recovery.img should also be that, but just for security I will save everything.

I know theres a CWM working for RK3066, but I also read somewhere that ROMs will not be able to be installed on RK chips via CWM (I think because of the kernel)

Wasn't TWRP working, according to webdude?

PS: there is not a lot of bloatware, just a couple of apps i will remove, and I will also include mine in there as well as update the ones that are there already.
[MTCB Android Head Units Q&A] Zaphod-Beeblebrox:
I think I may have found the first of these that are available on E-bay. I'm just not yet comfortable buying from Alibaba/express yet. While this is still coming from China, I feel a little better with E-bay protection policies

http://www.ebay.com/itm/251502162400?ssPageName=STRK:MEWAX:IT&_trksid=p3984.m1423.l2649

This one has a face-plate I've not seen before, and there are some inconsistencies in the screen shots, but I think this is a HuiFei unit.
[MTCB Android Head Units Q&A] nwskipro:
What unit is this? I'm guessing it is vehicle specific? Any other details?
[MTCB Android Head Units Q&A] nexgen10:
I think i'm going to order a lot from the mfg and list them on ebay. The MFG is telling me that HD screens will begin production in May.
[MTCB Android Head Units Q&A] webdude12:
TWRP loads, you just can't mount any of the partitions, so its basically worthless. I. E. Can't do backups, flash zips, etc. There is a 800x480 one floating around, and this is the one I took a picture of

---------- Post added at 10:36 PM ---------- Previous post was at 10:32 PM ----------

The unit I found, the y only have Audi, BMW, and supposily 1 universal unit (But I haven't seen it yet). I'm nor going to post links yet as you can buy it today with 4.1, I want to see if they hold true to 4.2.2 and proving key too unlock bootloader
[MTCB Android Head Units Q&A] nwskipro:
Cool cool - keeping an eye on this
[MTCB Android Head Units Q&A] agentdr8:
Mine does this too on occasion. Unfortunately I don't have a front miniUSB port, so I can't logcat the boot process. Factory reset doesn't seem to be a permanent solution. I've done a number of them, and it always comes back at some point.

If anyone with a front USB can grab a logcat during boot when the SystemUI error shows up, I might be able to figure out why it's doing it, and how to get rid of it. Try launching adb like so while the device boots up: adb wait-for-device logcat >> c:\temp\logcat.txt (or where ever you want to output it)
[MTCB Android Head Units Q&A] coppertop2000:
I found out that 1.86 was causing my system ui crashes after some time. I spent 2 days going to and from different versions... And the newer always ended up having problems after a while. I had to resort back to 1.77 for a more stable system.

Unfortunately I'm in Africa right now and won't be back home for another month to test out the new builds.
[MTCB Android Head Units Q&A] agentdr8:
Interesting observation. Will have to test out the 1.99 image once it's reuploaded and see if it too causes SystemUI to crash randomly. Thanks for the input.
[MTCB Android Head Units Q&A] MuttzNuttz:
Downloaded 1.99 disk size 117mb but wont extract here also.
[MTCB Android Head Units Q&A] idr3s:
I just installed my unit which is a KGL-8102 with mcu kgl4 v1.93.

I've got 2 issues that I wanted to ask about:

1)The button illumination on my unit stays on the whole time even when ny headlights are off.. anyway to fix that. (Note that my unit and car didnt need canbus so I need any other suggestions besides anything relating to Canbus)

2)I want to play music using Aux and I have connected my phone to aux but I dont know how to play from it. Is there some aux app on the unit.
[MTCB Android Head Units Q&A] agentdr8:
The illumination wire on your headunit is connected to the wrong wire on the vehicle side. It's on a switched or constant 12V, instead of one that's tied to your headlight/parking light circuit.

There's an app called AVIN.
[MTCB Android Head Units Q&A] idr3s:
Will this require any cutting of wires to connect to the illumination.. or is it some sort of PnP .. (got the connection done from a shop so not sure what happened there)

Can you also tell me how can I find the illumination wire?

Also ive got one more issue.. regarding obd2..ive got a usb obd2 and im using the torque that comes with the unit... at first it was asking for car profile or something..then I checked fast obd2 connection and set baud rate to somewhere around 30000.. it worked for almost a sec then it doesnt anymore...

Now it does say connection to ECU ok but shows nothing on the gauges... any clue?
[MTCB Android Head Units Q&A] coyttl:
Depends entirely on your car. If someone else here has the same car as you, they may chime in if you post what you're driving. Otherwise, you only have one way to figure it out - take it out and look. :D (Or, I guess, take it back to the shop and have them fix..?)
[MTCB Android Head Units Q&A] ProfessorKnox:
7-tips trick doesn't enable development options menu

Hi all friends and fans of HuiFei radios and their derivates.

I'm new to this thread and have read the first 80 posts as well as the last 50 ones.

Great work of all participants.

I'd like to participate my experience too.

I own a ES9401 (e.g. ebay article #131250029868) and use it in SKODA Supberb 2011 3T5.

SW Details:

- MCU-Version MCTB-KGL-V1.77 / May 14 2014 17:49:13

- Kernel-Version 3.0.36+ Wed May 14 03:45:57 PDT 2014

- Build-Number rk30sdk-eng4.2.2 20140514.19:44:15

I have rooted device successfully according the description in this thread.

BUT I have a big problem. Enabling the hidden development options menu by 7times tipping onto build number doesn't work at all.

I tried it multiple times and also more than 7 taps - no chance.

Does someone know an alternative way to enable that menu, e.g. by inserting xml files at the right locations or modifing some config files?

Every help and support VERY appreciated.

BR Tommy
[MTCB Android Head Units Q&A] Stank0:
I'd like to know that one too.

I worked around this problem once before on one of my many phones in the past. I installed an app which required USB debugging and it just took me there even without it being available in options.

The problem is, I don't remember what app it was. I'm pretty sure it was one of them tethering apps like PDANet and EasyTether.

Hope that helps at least as a temporary solution.
[MTCB Android Head Units Q&A] 1-2-Hak:
My apologies - must have crashed through uplod last nite.

Will re upload this morning.

** Should be good now
[MTCB Android Head Units Q&A] krebs8:
[MENTION=5990523]ProfessorKnox[/MENTION]:

Hallo,

habe das exakt gleiche Gerät mit genau diesen Softwareversionen in meinem Golf 6 (2010), aber einen dumpfen Radioempfang.

Wie ist der Klang bei Dir, welchen DIN-DoppelFakra-Adapter hast Du und wie sind die Radioeinstellungen in den Werkeinstellungen ? Danke.
[MTCB Android Head Units Q&A] ProfessorKnox:
I searched google using "This app requires usb debugging enabled" and found a dinky app called 'USB Debug' by tatibana.

Even though it's already past 11:00pm in Germany I couldn't wait for going to my car and give it a try immediately.

Abd it does the right thing: It shows the hidden Development Options menu - to be clear it doesn't enable it but only gives access through the app -but that's just perfect!!!

@Stank0: THANKS A LOT. You made it happen, to find this app after initiating my search for 'PDANet' and 'EasyTether'!
[MTCB Android Head Units Q&A] ProfessorKnox:
Hi,

is it possible for you to write in English - this would allow the international HuiFei fans to follow our discussion. For the time being I'm gladly willing to answer in Geman as well as in English.

Hallo, ist es möglich in Englisch zu schreiben - das würde den internationalen HuiFei-Fans erlauben unserer Diskussion zu folgen. Für den Moment bin ich gerne bereit in Deutsch und in Englisch zu antworten.

DE:

Ich habe das Gerät gerade erst ca. 3 Wochen. Vom (Radio-)Ton scheint es ok. zu sein. Andere Quellen habe ich bisher noch nicht probiert. Ich hatte in der Zeit eher das Problem mit miserablem Empfang zu tun und diesen zu beheben. Habe dafür einiges für Versuche investiert: Antenne direkt angeschlossen -> negativ. Aktiver "Diversity"-Adapter mit Phantomspeisung -> negativ. Separate UKW-Aktiv-Antenne -> negativ. Habe heute einen simplen Single-Phantomspeiseadapter erhalten - und der scheint den Empfang um Dimensionen zu den vorherigen Versuchen zu verbessern - muss ihn aber erst noch unter dynamischen Verhältnissen (Autofahrt) testen - aber die Chancen stehen gut.

PS: Hatte vorher ein KRAEMER KR-G6+ inkl. internem DAB+ - Empfänger - der macht aber beim Einschalten der Radios bei schlechten Empfangsverhältnissen - und die gibt es unweigerlich immer wieder - einen Senderscan und überschreibt damit alle zuvor gespeicherten Sender - oder wenn kein Empfang möglich ist resultiert das im Löschen der gespeicherten Sender.

EN:

I have the unit just for about 3 weeks. (Radio-)Sound seems to be ok. I haven't tested other sources yet. During that time I'd rather had problems with lousy reception and to solve this. Have invested considerably for that. Antenna connected directly -> negative. Active "Diversity" adapter with phantom powering -> negative. Separate active VHF antenna -> negative. Received today a simple single phantom powering adapter - and this one seems to enhance reception by dimensions compared to the previous attempts - but still must test it under dynamic conditions (driving) - but chances are high.

BTW. Had a KRAEMER KR-G6+ incl. internal DAB+ receiver previously - but it performs at switch on of the radio and bad reception conditions -which always is inevitably possible - a transmitter scan and by that overwrites all previously stored stations - or if no reception is possible this results in clearing of the stored stations.
[MTCB Android Head Units Q&A] Skitals:
Audio quality problems

The more I've used my unit the more I've noticed slight audio quality issues. I don't know if they are hardware issues with my unit, software, or some type of grounding issue. I have no factory amp, running stock speakers, but I do have an aftermarket mono amp and sub hooked up to the headunit via front l/r preamp out. I have ZERO issues with the sub/amp, no popping or funny business from the sub/amp. But my regular car speakers DO get sporadic popping/clipping noises.

I initially thought it was encoding issues with particular MP3 files, but there is definitely something wrong here. On certain songs at certain frequencies I'm getting popping noise coming from my speakers. For instance, what should be a nice clean bass hit will clip and create an irritating pop.

This morning I was using the Waze navigation app with Poweramp playing in the background. When an audio prompt plays in Waze, it automatically lowers the volume of the song playing, and then raises it back up when the prompt is finished. Every time the voice prompt ends and it raises the volume back up, there is an audio pop.

The Radio is worst of all, which I don't know if it's related. Despite trying multiple antenna adapters (amplified diversity antenna in my car), the reception isn't great. But even when I've got a solid lock on a station, I get worse clipping/popping then any mp3. It is NOT am/fm static... the audio otherwise sounds very good until it clips out, pops, etc.

This is all rather subtle and would probably be difficult to impossible to document via a recording. I'm just looking for suggestions. Do you think I could have some type of short or bad ground inside my unit? Would adding an external ground help? Should I redirect the ground wire in the wiring harness to a solid chassis ground?

I am also somewhat willing to add an external 4 channel amp if it would help. But I reckon it's possibly not a hardware problem at all and code the MCU software sending funny signals for whatever reason.

Please help! I've got a GS unit running GS-V1.90.
[MTCB Android Head Units Q&A] idr3s:
So my unit started giving me these problems now:

1) Wifi's stuck on 'Turning on Wi-fi...' screen and it doesn't turn on..Though it did work in the beginning once.. Dont know what happened. Already tried turning it on and off..

-worried I won't be able to root the device without any network connection

2) The Avin app is not working either.. just shows an exclamation mark and nothing playing

Anyone have any input on this?

Back to the shop it is! the guy did say if I don't find anything in settings to fix this ..he'll just run the wires with the parking/headlights wire when I come back ..

Any clue with the other issues above? ^
[MTCB Android Head Units Q&A] krebs8:
[MENTION=5990523]ProfessorKnox[/MENTION]:

Please test radio sound compared e.g. to mp3 sound and tell my the results.

Which "simple single phantom powering adapter" did you buy ?

I will be glad to here for your test while driving.
[MTCB Android Head Units Q&A] sprfly:
They offered a 50$ refund and I had already used a 35$ coupon on it so thats 85$ savings; total with shipping $265. I would still have to figure out how to mount it as the old brackets do not work. I would also have to source my own maps. What I cant change are the buttons on the front of the unit. I think I am still going to send it back and get what i wanted. :confused:
[MTCB Android Head Units Q&A] typos1:
Hmm, having thought about it some more, I would push for a further discount (maybe $100 ?) and ask them to send the actual buttons you ordered.

Or contact another supplier and try and see if they can supply you with those buttons (your front is used by hundreds of Chinese stereo companies, for Android units, WinCE units and all sorts of other more basic units, so shouldnt be hard to find someone who ll supply them).

Then fit them yourself - it should be quite simple as its only the plastic cover of the button , the rubber pad and LED wont be changed.

Then using advice for people on here (1-2 Hak, agentdr8, Dark Ales, etc) re-map the buttons.

Hey presto, just what you wanted for $$s less !
[MTCB Android Head Units Q&A] Stank0:
I've purchased right angle adaptor for USB bud ended up not using it because I couldn't find a reason for having USB in the first place. (don't have anything to plug into it)

The GPS antenna was a little bit bigger deal but I absolutely hate to cut anything in my car, especially make holes into HVAC airbox.

As a temporary solution I just pushed it in hard enough to bend the GPS connector (and not break it). It worked just fine.

I'm planning to get the right angle adaptor for GPS as a permanent solution.
[MTCB Android Head Units Q&A] sir sniffalot:
I also have a GS unit (running on V1.85)

I am not happy with the sound quality either. I have tried poweramp and viper4android and I can't get a set up that gives me a nice sound. Bass sounds flat and at times too loud (even if I turn bass frequencies really low). If I find a reasonable setting for one mp3 track it sounds terrible on another. I even find that some frequencies are 'missing' - the hand claps in House of the King (Focus) just aren't there. I'm using some fairly decent JBL speakers which gave a nice rich full sound with my old bog standard Ford stereo with one bass/treble setting that worked for everything from ABBA to acid techno :silly:

I also get pops from time to time and sometimes the volume reduces for a second or two for no apparent reason.

Any help for setting up sound settings would be greatly appreciated.
[MTCB Android Head Units Q&A] lamjanus:
Ok, i see in the txt from the uploaded 1.99 version that the "4" is for a slide down screen unit type. A lot of different MCU versions from now on?
[MTCB Android Head Units Q&A] RmXsTyLe:
My KGL comes with V1.77 and it says "MTCB-KGL-V.177". with upgrade to 1.86 i take the mcu from MTCB-KGL so i got

"MTCB-KGL-V1.86". Upgrading only the MCU to 1.95 i finally got "MTCB-KGL4-V1.95".

now i flashed full V1.99 with MTCB-KGL5 and my unit says "MTCB-KGL5-V1.99" but my buttons on the unit dont do, what they've done before.

if i press volume up or down, the bluetooth menu starts, now i try to flash with KGL1 and will report. my unit is ErisinES9401

http://i00.i.aliimg.com/photo/v0/1857386668/ES9401A_8_Android_4_2_2_Car.jpg
[MTCB Android Head Units Q&A] zorantoma:
I have the same unit,so please report if you found the right MCU version :)
[MTCB Android Head Units Q&A] Navall2:
STOP!

You are installing MCU FIRMware that is not compatible with your unit.

The MCU and the program in it is comparable (not the same) to BIOS input/output system. If you load the wrong mcu.img file it will not be able to talk to Android (which is the operating system).

It is like a PC which have a motherboard, and on that is a peripheral card like a graphics card or TV card or ....

Windows will "talk" to the TV card (or whatever card you have installed) through a driver that knows what to ask for and where to get it in the TV card. But if you insert another TV card you need another driver or it won't work.

You could say that the MCU is a "TV card" and you are installing the wrong driver.

You need to go back to your original image file (mcu.img v. 1.77) and get the EXACT name of your KGL file from the menu.

Then find the corresponding mcu.img file.

NOTE:

KGL is NOT the same as KGL1, KGL4 or KGL5 or similar.

Good luck on your endeavour.
[MTCB Android Head Units Q&A] RmXsTyLe:
[MENTION=5990140]Navall2[/MENTION]

Thx for your post, but i think u are wrong.

My unit comes with 1.77 KGL, and in upgrade from 1.77 to 1.86 i used KGL as well, because in first post of this thread is said:

"MTCB-KGL1 --> This is the mcu for BMW and Mercedes

MTCB-KGL --> This is the mcu for the other car makers"

and though i got a Skoda Octavia i dont own a bmw and used KGL, BUT! the gps key didnt work. so i upgraded with 1.95 MCU,img (usind 1.86 update.img because i cant reach recovery with the steps in post #1 and nobody helps me) named KGL4 and everything worked fine.

so even if my unit comes with 1.77KGL the update to 1.86 and update to 1.95 MCU only with KGL4 MCU works fine! so my unit says MTCB-KGL4 1.95 and everything fine

now for the 1.99 full upgrade, you got 6 different KGL files and it says:

"МТСB-KGL1-В1.99 --- With return button on panel

МТСB-KGL2-В1.99 --- For BMW with return button on panel

МТСB-KGL3-В1.99 --- Only for Jeep with button on panel

МТСB-KGL4-В1.99 --- For slide down screen unit

МТСB-KGL5-В1.99 --- For unit without return button on panel

МТСB-KGL-V1.99 --- For BMW without return button on panel."

as u can see, i dont own a bmw and dont own a jeep and down own a slide down screen unit.

so i can only use KGL5 or KGL1. i cant use KGL as u wish, because KGL is for BMW.

i dont have any return button on my panel so i used KGL5 MCU.
[MTCB Android Head Units Q&A] optx:
Buttons dont work for me,when KGL1 or 5 is flashed. Anyone else getting this Problem ?

Will flash now 1.95mcu, since this one worked perfect.
[MTCB Android Head Units Q&A] Navall2:
I think you read my answer wrong - I did not mean you should use KGL - I meant you should install the ORIGINAL image and CHECK what version that is, and find a similar one. If the original was KGL4, then you should obviously use that.

Hope that clarifies it.
[MTCB Android Head Units Q&A] RmXsTyLe:
no no, i understood you, and i wrote, that my unit comes originally with MTCB-KGL-V1.77, so ORIGINAL IMAGE is KGL-V1.77.

BUT! when i upgraded to KGL-V1.86 my GPS button dont work, even with this right KGL MCU.

BUT! after i upgraded to KGL4(!!)-V1.95 (mcu only) my buttons all worked like in KGL-V1.77.

in your opinion my unit couldnt work with KGL4 if it is an original KGL. but why does it work, and why does is work better with KGL4 1.95 than KGL 1.86 ?? so that is the point where i think u are wrong.

KGL only says, that i got an KGL Device, but the number after is only for different cars or different key layout in the KGL units.

i hope THAT clarifies ;)
[MTCB Android Head Units Q&A] Navall2:
I am confused. Not by your answer, but the fact that I have a KGL1 (BMW) image - that works with all current KGL1 updates. And if what you say is true (and I do believe you) the KGLX (number) is no longer to be trusted and we are up the creek wihtout a paddle.:confused:
[MTCB Android Head Units Q&A] 1-2-Hak:
I can ask keylo what the answer is but I think the numbers are just slight variation of configs to match inputs on the MCU for the different models.

They are designed for the KGL MCU just offer different config. the buttons will either work or not - it shouldnt brick the device.

I will confirm this with keylo

** I have asked - she will check and get back next week (friday night)
[MTCB Android Head Units Q&A] Navall2:
Android image 1.99 vs. 1.86

@1-2-Hack:

Could you also ask him to explain why the Android image files (update.img) differ?

The 1.86 update.img file is 596 MB, but the 1.99 is only 563 MB.

That is quite a lot of data "missing".

I haven't done a comparison, so I can't tell where the differences are.

BTW, do you know if I can patch the update.img file in the text areas?

I would like to try and replace some of the build.prop parameters to make it Play compatible without rooting.

Obviously without exceeding the current number of characters in the field.:fingers-crossed:
[MTCB Android Head Units Q&A] Stank0:
Your problems aside 'coz I can't help, did you notice any difference or changes with the new firmware?

I'm looking for reasons for update since everything works just fine with 1.86 for me.
[MTCB Android Head Units Q&A] 1-2-Hak:
Keylo is a She :)

She is not technical - just sales. I have asked her to check the MCU with her engineer.

I will do a quick compare if I get time.

There are lots of ways of editing the build.prop without rooting but must ask the question why no root? Always can root then unroot.
[MTCB Android Head Units Q&A] Blaze Falconburger:
Bug report:

- Override Mode - when enabled and I don't select anything else - the menu claims Music & Radio are standard, but I can't ever select Radio

Feature Request

- Add more apps to the list, for example I use Tune-In Radio and would be great if I could select this on the Mode button

- PowerAmpp - can you override the Tune knob to scroll up/down the folder list? Currently it skips a track, but this is not necessary with the physical next/prev hardware buttons

Keep up the good work this is becoming a good module!
[MTCB Android Head Units Q&A] Navall2:
I have tried rooting on 1.77 using Rootmaster 2.1.1, but how do I un-root?? I don't wan't to leave it open to possible vira, malware or the like.
[MTCB Android Head Units Q&A] optx:
If you have installed Superuser, there is a menu to unroot the device ;)
[MTCB Android Head Units Q&A] 1-2-Hak:
You can always flash TWRP via the bootloader.

Then boot into recovery.

Do whatever you want to do to the rom via adb

- modify build.prop

- add su to root (no rootmaster risk)

- delete bloat

- mod system apk
[MTCB Android Head Units Q&A] 1-2-Hak:
These are the 1.86 - 199 Rom differences

Anyone who has loaded confirm these widgets are missing?
[MTCB Android Head Units Q&A] RmXsTyLe:
I now used upgrade V1.99 with KGL4 MCU File. Originally i came from v1.77 KGL. But now all buttons on the unit work as before.

And i got a new function, the unit now displays me if a door is open.

but also i got a new problem, my swc now is fully mad:

- track up button leads to 3 steps track down

- track down button leads to 3 steps track up

so direction is wrong an 2 titles were jumped

and advice ?

[MENTION=1059814]Stank0[/MENTION]

i think boot time is faster, but not much. everything is fine except SWC and as i mentioned i got new function for display open doors :)

if i see other things new, i will post them