yashsingh1/xdaforums huggingface dataset:
[MTCB Android Head Units General] treibstoff:
http://huifei.fs-fileserver.de/cont.../KLD 4.4.4/1024x600/KLD1024x600 20160502 DSA/

this one is the one i use because for me 5.1.1 is not running well. the volume control is not smooth with the volume knob and system Performance stuttering sometimes. feels like ram is not enough. 4.4.4 works perfect here....
[MTCB Android Head Units General] tariqkhan.co.uk:
I installed KLD9 2.98 yesterday...

Didn't notice anything different. I saved some radio stations and then booted into recovery, didn't make any changes and simply restarted, radio stations gone (did not save).

I'll stick to this MCU version as it is newer and will let you know if I spot anything different at a later date.
[MTCB Android Head Units General] typos1:
Did you make sure the radio tuner was set to the correct type after the update ?
[MTCB Android Head Units General] tariqkhan.co.uk:
Yes, but if it was not on the correct type, would I even be able to pick up stations?

Just wondering if there was a post/wiki that detailed the default settings for all the various units around?

I have a Eonon Klyde system and took pictures before an upgrade of the MCU. But, when I first got the system over a year ago, I may have updated or altered the settings without noting down what they were.
[MTCB Android Head Units General] typos1:
Stations can be picked up if its on the incorrect type, at least I have experienced it several times.

If youve checked and its correct, then it doesnt work for you for some reason, I just made that suggestion in case you hadnt checked.
[MTCB Android Head Units General] tariqkhan.co.uk:
Thanks, I did check, but would be curious as to what the defaults are so that I can crosscheck to ensure they are correct:

Eonon Klyde System

--------------------------

APPLICATION:

- BT = WQ_BC6

- TV = NO

- DVD = NO

- IPOD = YES

- CanBus = 05 GM(Raised)

- Radio = TDA7786

RADIO BAND:

- Europe

CAR LOGO:

- Not listing

AUDIO

- TV = 20

- AV in = 20

- DVD = 20

- Radio = 9

- IPOD = 20

- BT = 20

- Sys = 5

OTHER:

- Model = S07

- RDS = TICK

- Front camera = Untick

- Wheel3 = Untick

- RGB LED = RGB

- Rudder = Tick

- Disable app install = Untick

- key light = Untick = Untick

- No wheelstudy = Untick

- Keymap option = Option 1

- Touchmap option = Option 1

- Reversing bri... = 0

- swap canbus next prev = Untick

Maybe this might get others posting their settings, which may be handy to many who have lost or are curious as to what the defaults are?
[MTCB Android Head Units General] typos1:
The defaults are specific to each unit, depending on what car its for and the spec (tuner type, BT module type etc). There are too many units to make a list, just best to save settings before updating MCU
[MTCB Android Head Units General] chichi87:
Hello

I have a radio with mtcb kld 2.77 version

now i updated from original rom to the lollipop rom with mcu kld1 2.55 i can't find the 2.77 one.

lollipop now is working fine but the radio is mute no sound from all the apps and system.

can i use the kld2 2.77 version or is this not working?

what should i do?

thks
[MTCB Android Head Units General] typos1:
What you need is the very latest MCU.

On the fileserver in my signature go to firmware/MCUs/KLD, first try MTCC KLD9 v2.98, if that does not work properly, then try MTCC KLD6 v2.97, then MTCC KLD6 v2.96, MTCC KLD6 v2..91, MTCC KLD6 v2.86, MTCC KLD6 v2.85, then try MTCC KLD5 v2.97. If none of those work then try MTCB KLD6 v2.86, then MTCB KLD6 v2.85, then MTCB v2.83.

With a bit of luck one of the MTCC ones will work and you will have upgraded your unit to an MTCC one !
[MTCB Android Head Units General] Wolf Hamburg:
And remember ... If you have a MCU flashed in the factory settings the right type radio, BT, etc adjust. Otherwise, your radio will be mute ;)
[MTCB Android Head Units General] chichi87:
thks man i have a mtcc now

i flashed the kld9 v2.98 its working now with much better soundquality than stock kld1v2.77 no disturbs on the audio signal.

only thing fm radio dont work anymore but its not tragic for me.

i noticed also a flackering of the lcd on white icons or bars in apps its a known problem? is it possible to resolve?
[MTCB Android Head Units General] tariqkhan.co.uk:
I don't get any "flackering" or flickering lol

Radio would be because you have not set the settings correctly as I got the same.
[MTCB Android Head Units General] typos1:
Oops, yeah, sorry, I should have said, go into factory settings and try all tuner types and make sure its set to the right area of the world.
[MTCB Android Head Units General] Johny DJ:
I also noticed flickering on white colours and some others, but on the begining I bought the unit that was not happening...

I don't know why and when this happend, but probably because of poor screen quality.
[MTCB Android Head Units General] Valfox:
Mcu_mtcb-zd-v2.85 03/03/2016

MCU for Eonon GA5162F / GA5161F

I do not know with other models!
[MTCB Android Head Units General] typos1:
Thanks I will add it to the fileserver.

BTW there is no sucj thing as a Eonon GA5162F/GA5161F - there are made up by Eonon, they are simply ZD MTCB head units, the MCU should work on all ZD MTCB headunits.
[MTCB Android Head Units General] efrasjourney:
Hey guys, my current MCU is KLD v2.30. Just to be sure, I can upgrade my MCU to v2.78 without breaking anything?

thanks!
[MTCB Android Head Units General] typos1:
No guarantee you wont break anything, but whatever "breaks" will be fixable.

Go into factory settings and take screen shots of all screens, then after updating make sure everything is set correctly.

Try the KLD9 one first then KLD6, then KLD5 etc, finally if none work properly try KLD v2.78.

See here also for MCUs :

https://mega.nz/#F!zRRkVThb!DYBC0LRK-o34ZxDObQo73Q!XNwCna7S
[MTCB Android Head Units General] efrasjourney:
Thanks for the info. As long I'm flashing MCU's that are KLD it could work, right? I'm a little bit nervous about upgrading this b/c my MCU us working fine, the only thing that I want is the sleep mode because every time I shut down the car the HU completely shuts down and I saw somebody writing that upgrading the MCU fixed that. Am I wrong?

Cheers!
[MTCB Android Head Units General] typos1:
Dont be nervous - there are enough MCUs available to downgrade. Yes, later MCUs have a shutdown timer, as I say, try the latest first and work backwards if you have problems.

BTW earlier when I said try KLD9 and KLD6, try the MTCC versions first, hopefully theyll work and if they do youve upgraded your unit to an MTCC one !
[MTCB Android Head Units General] efrasjourney:
Awesome!!! Will try it, thanks!!!!
[MTCB Android Head Units General] celiocalves:
Whats the difference between KLD, KLD1, KLD2, KLD6, etc ? I saw so many versions... :/

I currently have a pumpkin HU with MTCB KLD2 v2.77 and i'm thinking to upgrade, expecting some improvements, but I don't know which is the best MCU.

It's a good idea or not?

Thanks
[MTCB Android Head Units General] typos1:
Slightly different software thats all.

You dont have a "Pumpkin" unit, you have a Klyde unit, Pumpkin are no more than sellers. Follow the instructions I gave previously, try MTCC KLD9 and MTCC KLD6, start with the latest version and work backwards. If all else fails you can use the last version of MTCB KLD2, but try to upgrade to MTCC first and take screen shot of factory settings so you can set everything correctly after the update.
[MTCB Android Head Units General] celiocalves:
So you think upgrading to MTCC first, rather than MTCB is better?

Im running Malaysk ROMs Android 4.4.4, it will work? Malaysk refers "only MTCB"...

I'm undecided between Malaysk latest 5.1.1 and 4.4.4. Which is you advice?

Thanks
[MTCB Android Head Units General] typos1:
You could try 4.4.4 with an MTCC MCU but there may be issues. I d use 5.1.1 and MTCC personally.
[MTCB Android Head Units General] celiocalves:
Ok thank you ;)
[MTCB Android Head Units General] dhmsjs:
From studying actual the MCU code itself, what I am seeing is _very_ little difference functionally -- even from MTCB to MTCC. Most changes are cleaning up the (messy) code, perhaps to open up some extra space. Haven't yet found the reason that the radio stops working for some users with MTCC KLD9 v2.98. Notably, when I have asked Pumpkin for a specific version, they pointed me to a more recent rev.

Some have reported that KLD9 V2.98 saves radio presets; haven't found the reason for that yet either. (It is not obvious.) The meaning of KLD9 vs KLD6 vs KLD2 is not obvious either since they often seem to be interchangable.

Just be aware that you cannot "upload" your current MCU image; you can only send a new one to the MCU. So it's a good idea to make sure that at least you know what you received from the factory before you change it. If the version you received from the factory is not available here, you may not be able to go back.

And if you do find a functional difference between versions be sure to report it here!
[MTCB Android Head Units General] typos1:
Its not so much "some users" who experience radio problems, its ONLY non numbered MTCB KLD MCUs, units with KLD1 - KLD9 MCUs can all be upgraded to MTCC MCUs with no loss of functionality. Why it only effects MTCB KLD MCUs without numbers is a mystery.

We have enough MCU versions on the fileserver, this MCU thread and the Mega site for ALL USERS to be able to upgrade their MCUs without worrying about not being able to downgrade if there are problems, if we dont have the exact version one a few numbers above and below will be ok - no one has yet experienced a problem in 3 years.

There are too many people to list who have experienced functional differences [MENTION=6906599]dhmsjs[/MENTION] - just read this thread and the "Lollipop for MTCB/C . . ." thread to see.
[MTCB Android Head Units General] dhmsjs:
Of course -- except perhaps for those who do worry or care about such things.

Not dismissing any of that nor interested in a debate. Just sharing what I see.
[MTCB Android Head Units General] typos1:
I wasnt trying to start a debate - I was simply informing you of the facts as you seem to be the MCU guy - its only KLD non numbered MCUs that have this problem with the MTCC update and no one (except perhaps people with ZD units as we dont have many ZD MCUs) should worry about updating their MCUs because we have enough copies of almost all the MCU versions available should anything go wrong.

If you could use your skills to sort that, many users would be grateful (I can use MTCC MCUs, so I m asking for others, not myself).
[MTCB Android Head Units General] dhmsjs:
Just for a quick summary of where I'm coming from:

My base image has been MTCB-KLD2-V2.77 just because that is the one that I started with, and one that works with my HU -- so I could test changes with it were I to get to that point.

I haven't myself upgraded the ROM to 5.1.1 or MCU to MTCC (yet). Not a priority for me. When MTCC came out I grabbed the MTCC-KLD6-V2.91 image to compare. Because [MENTION=6041319]dsa8310[/MENTION] reported strange behavior with front panel LEDs and a broken radio, I focused on those areas. When you pointed to the MTCC-KLD9-V2.98 image as being the only one with those problems, I disassembled that for comparison as well.

Of course just because I haven't yet found a smoking gun in the code doesn't mean there are not significant differences between these images. Why would the original developers bother to release new versions if there were not?

But what I have seen, and what I can say is that the vast majority of all changes I see are what I would call "housekeeping" more than functional differences. And there is a lot of housekeeping to be done.

Just for example, I've now studied the front panel LED code fairly carefully since dsa8310 reported his experience. Yes there are some minor changes, but algorithmically I have yet to find

any

difference at all between the three images as far as the front panel LEDs are concerned.

That doesn't mean I am trying to say that no differences exist. But it does strongly suggest that the differences are very subtle, and may be related more to how the Android ROM interacts with the MCU than with the MCU image itself. Of course I could be wrong on that, but that is what I see.

At this point I've spent about a year of my spare time studying the v2.77 code (and simultaneously working on a re-write which is perhaps about 1/2 done at this point). If anyone else has ever tried reverse engineering at the machine language level, they will probably agree that it is painfully slow going. These images are particularly difficult because the code is not well-structured (from my perspective anyway). Many of the changes I see in the MCU versions I've studied seem to be addressing this more than adding new features or capabilities.

Given how much time and effort it takes to study and compare images, If someone really does want me to investigate some specific difference in behavior between any given MCU image and any other, then step one will be to identify EXACTLY which MCU versions they want compared. Sorry but I'm not going to monitor every single XDA thread looking for relevant posts. Step two will be to have

a lot

of patience. You might join in the fun too, if you are so inclined.

Finally, I'll note that much of my efforts may be wasted if the market moves away from MTCB/MTCC to MTCD. At this point I am guessing that it won't be a total waste though, since the chances are pretty good that the developers ported the much of the MCU code from the MTCB/MTCC (8051 core) device to the newer (ARM core) MTCD device. Only time will tell on that one.
[MTCB Android Head Units General] typos1:
Thanks for your reply, I ve been following what youve been doing since youve been posting about it, I appreciate your efforts.

You have a lot of knowledge about the MCU software and I have a fair bit about what upgrades work on which MCU versions, so I was just trying to make you aware that the strange behaviour dsa reported ONLY happens on non numbered KLDs when upgrading to MTCC - all other MTCB KLD1-9 MCUs work ok with MTCC and can be upgraded and work with improvements.

I dont remember saying that KLD9 was the only one with these problems though - AFAIK all numbered MTCC KLD MCU firmware has these or similar problems when flashed on units that originally had a non numbered KLD MCU.

It does seem strange how only the non numbered ones dont work, especially as there are no discernible differences.

You could always flash a copy of an MTCC MCU on yours to see the results, pretty sure we have an MTCB KLD2 v2.77 if you want to go back I ve flashed lots of different MCUs.
[MTCB Android Head Units General] GREATXDADEV:
This kgl is for mtcd compatible???

]

Hy ...excuse me can i use the kgl v.2.83 for any mtc"x" .....or i find the kgl for only mtcd unit???? Please thank you
[MTCB Android Head Units General] GREATXDADEV:
compatible mtcd

but this mcu is for mtcd unit compatible?? hovewer if i have mtcd kgl v1.92 can i upgrade with this yours file kgl v2.83
[MTCB Android Head Units General] typos1:
This thread is for MTCB and MTCC devices only, check out the MTCD section for MTCD MCUs, you say you have "2.83" what 2.83 do you mean MTCB KGL 2.83 if so then yes . . .

and please reduce the size of your quote - it unnecessarily takes up a whole page !!!!
[MTCB Android Head Units General] GREATXDADEV:
Thank you....and excuse me for my terrible english..........i dont find the mcus list for mtcd....you can give me the link......i have just find the mtcd rom link (malaysk).....thank you.....
[MTCB Android Head Units General] typos1:
PLEASE REMOVE OR REDUCE THE SIZE YOUR FIRST QUOTE !!

Look in the MTCD section for MTCD units, this is the MTCB/C section !
[MTCB Android Head Units General] GREATXDADEV:
Done ok!!!
[MTCB Android Head Units General] ravenrocha:
Hi,

does any one knows where I can find an update for my MTCB-ZD MCU? My version is 2.83. Its for a Mazda 3 car.

Thanks!
[MTCB Android Head Units General] typos1:
The only ZD MCU update we know of is the one on the fileserver in my signature.
[MTCB Android Head Units General] ravenrocha:
Thanks so much for your quick reply and for letting me know of that new version. Mine is MTCB-ZD 2.83 from Dec 2015 and now this 2.85 is new and from March 2016. For updating is just to put on a PEN a make the update from recovery? Is like the ROM update? I never update the MCTB. Its safe to do it?

Thanks again.

Regards,

Hugo
[MTCB Android Head Units General] nFKT:
fwiw the attached version is 2.72
[MTCB Android Head Units General] typos1:
Ah, ok, well thats still later than the previous verison posted.
[MTCB Android Head Units General] nFKT:
Indeed, there isn't a later version posted here or 4pda, and fwiw the latest dark leo KLD2 MCU didn't work on my KLD2 unit anyway.
[MTCB Android Head Units General] typos1:
Hmm, ok 2.53 works fine on my KLD, though, so did the previous versions.
[MTCB Android Head Units General] m4f1050:
Haven't flashed this, but it's supposed to be KGL v2.83, courtesy of AUTOTOP.

EDIT: Confirmed KGL v2.83 dated Nov. 26 2015
[MTCB Android Head Units General] Zeinynet:
I have the installed 2.68 .....Build RK3066......?
[MTCB Android Head Units General] Tryden:
Is it possible to save the original MCU?

I got an Erisin Unit and with other MCU's the Key Mapping is wrong and other maps doesnt change it to the original mapping. So I would like to save the original version from a friends unit.

Gesendet von iPhone mit Tapatalk
[MTCB Android Head Units General] typos1:
No, not possible.

Erisin is a seller, to find out what unit you have look in settings/about.
[MTCB Android Head Units General] Oberbergler:
Mcu

Hello,

does anyone know where I can get the MTCB-KLD6-V2.81 Mcu?

Thank you
[MTCB Android Head Units General] igorski:
mine says MTCB-ZD-V2.83 Dec 02 2015 17:37:36

I have a MCU file that says in windows, modified Dec 02 2015 10:42

Is this the same one?
[MTCB Android Head Units General] m4f1050:
Do not flash any MCU

Make sure its the right one or you have the same model. (i.e. ZD v2.80)
[MTCB Android Head Units General] igorski:
I'm not about to do it, but I just wanted to ask if this could be the same as I have. I got this from a thread on this forum, but since the date don't match exactly I'm not sure it's the same.

It was more that if this should be added to the list. ZD isn't mentioned. It's a Eonon GA5153F unit.
[MTCB Android Head Units General] m4f1050:
I would just flash the update.img and leave your mcu.img alone...
[MTCB Android Head Units General] c1bear:
HI and good day, I hope someone can help me here, I just picked up a Eonon GA2114

MCU

MTCB- KLD V2.79 I dont see that one in the list above.

looking to flash rom but need a back up just incase something should go wrong any help, My main issues with this unit is ipod it connects what it want to, and if i have a song playing on my ipod then connect it to the unit i can control music files and folders from my ipod craziest thing ive ever seen, Sorry if i post this in wrong place just trying to get some help with advice thanks in advance
[MTCB Android Head Units General] typos1:
Flashing the ROM and MCU are ENTIRELY separate - flashing the ROM WILL NOT change the MCU, this thread is for MCU only.

Try searching the Q&A section.
[MTCB Android Head Units General] c1bear:
Thanks sorry about post in wrong place
[MTCB Android Head Units General] :
MCU v2.81

Hello,

where can i find the MCU v2.81 for KDL6

I updatet my MCU to the v2.83 from this post. But after the update my buttons of the wheel steering control and the Touchbuttons on the devices aren't working anymore.

Hope someone can help me

Thanks a lot
[MTCB Android Head Units General] m4f1050:
The "KLD6" has to match, you can't flash plain KLD or any other KLD other than KLD6, that is very important. Hopefully you can still access sdcard or USB to reflash to right one.
[MTCB Android Head Units General] :
Thanks for your fast answer :good:

I used the right one. first i had a KLD6 too. but the 2.81 (Screenshot was before i updatet to 2.83)

then i updatet to the KLD6 v2.83 from here

and now the buttons of the wheel steering control and the touchbuttons doesnt work

But i cant find the original 2.81 now :(

I found a 2.81 here

https://mega.nz/#F!KMZnXTJC!zDFMlP4qgxEE6vQxt8rrrw!LQhDQCQT

But its named KLD2B-V2.81

Can i use this one?
[MTCB Android Head Units General] m4f1050:
So the mcu is kld6 v2.81 but named different? Interesting. I wouldnt but you already dont have buttons workin so not sure if it will mess it up more than what it is. Maybe you have the chance to get buttons back, but I would look for right name mcu.img just un case... What does the About say the new MCU is, KGL6 v2.83 and didnt work? I know I had same situation and could never get the buttons to work again, so I put it on my F150 that had steering wheel controls (but the radio was vw and when installed on F150 you cant see the buttons) im sure thats not your case, but I would be very careful with MCU flashing. I learned my lesson and now I just leave the MCU aline and just flash UPDATE.IMG...
[MTCB Android Head Units General] typos1:
Yes either go into recovery or if you have a later L ROM you can go into "updates" from settings/about device.
[MTCB Android Head Units General] EagleSoldier:
Hi Forum, Hi Typos,

my unit (MTCB) is runing the DSA Rom with kld2 2.81 MCU.

Everything is working perfect....

Can I change the unit to MTCC?

When yes, wich should I use?

I have read that u can change from MTCB to MTCC

Best regards from Austria :)

EDIT: I found a answer from typos 2 pages befor.... best regards
[MTCB Android Head Units General] typos1:
Cool start with MTCC KLD9 v2.98, it should work if not try MTCC KLD6 v2.97 etc, let us know the results :)
[MTCB Android Head Units General] EagleSoldier:
Hi,

will try and report.

Thanks typos :)
[MTCB Android Head Units General] Oldpapa49:
Don't forget to take pictures of your factory settings 1st. Factory settings code is 126. Make sure you do this before, otherwise if it does change, you have a start point to settings
[MTCB Android Head Units General] EagleSoldier:
Thanks for that Info Oldpapa49 :)

I will report tomorrow morning.

Best regards
[MTCB Android Head Units General] typos1:
Good point
[MTCB Android Head Units General] EagleSoldier:
I installed the MCU KLD9 v2.98

Everything is working perfect....

See picture atteched

Thanks guys for your help :)
[MTCB Android Head Units General] typos1:
Cool, you should now be able to save radio presets and have them remembered !
[MTCB Android Head Units General] EdwardV:
Hello,

I have a G2110 that won't boot. I have not done any modding to it.

Is there any other way to find the MCU version? The only thing on the unit is G2110-NK0499.

Thanks
[MTCB Android Head Units General] typos1:
A what ? That sounds like a made up name by one of the sellers. Pics of the link where you bought it and /or of the outside and inside would help us identify it.
[MTCB Android Head Units General] typos1:
No, Eonon is not a brand its just a seller, from the pics it looks like a JY (Joyous) unit.

Youve got it booting now then ?
[MTCB Android Head Units General] EdwardV:
Thanks. After the initial message in the first picture the screen stays black, no android logo loading as it used to. Hence I don't know what MCU i should be trying to load onto it or what image I can run the recovery to.
[MTCB Android Head Units General] typos1:
Have you recently updated it ?
[MTCB Android Head Units General] EdwardV:
No, nothing has been done. Never been updated, just decided to stop working :(
[MTCB Android Head Units General] typos1:
Ok, strange.

You can use any MTCB/C image (but not later MTCC KLD factory images) as long as it matches your screen res and processor type (dual - RK3066 or quad - RK31888 core, 800x480 or 1024x600).
[MTCB Android Head Units General] efrasjourney:
Hey guys, finally updated my MCU to MTCC KLD6 V2.97, thanks to typos1 for the encouragement. Happy with the results. The only thing that it's bugging me and it's not a deal breaker is that every time I turn on the car lights the screen goes blank, but I found out if I activate an app or force the HU to change screens it goes back on. Like I said, no deal breaker, I can live with that :D