yashsingh1/xdaforums huggingface dataset:
[MTCD Android Head Units General] cogano:
[MENTION=4974080]marchnz[/MENTION]: how did you initially compare the MCU images? I tried

$ xxd JY_V2.06_2.dmcu.img > JY_V2.06_2.dmcu.img.hex

$ xxd KD_V2.06_2..dmcu.img > KD_V2.06_2..dmcu.img.hex

$ diff -Naur JY_V2.06_2.dmcu.img.hex KD_V2.06_2.dmcu.img.hex | grep -v "^ "

and while at the beginning of the image files the differences are just very subtle (and only a few of them), significant blocks are different from address 000f880 to the end of file (at 00027b50) . The total size of the diff file is 897 kB...
[MTCD Android Head Units General] 1-2-Hak:
If you dont apply the dmcu.cfg you get the error. If you apply it it goes away until you go back in factory settings. Then the error comes back
[MTCD Android Head Units General] marchnz:
Interesting, have you tried stock / HA android firmware? Perhaps we are seeing some models are not compatible, thanks for your feedback.
[MTCD Android Head Units General] 1-2-Hak:
Havent tried stock but error is specific that the HA is not compatible so dont think it would make a difference
[MTCD Android Head Units General] marchnz:
I compared using a diff tool on windows. Note files appear encrypted.
[MTCD Android Head Units General] syk02jcb@hotmail.com:
Installed newest HA mcu on xtrons PB76FSFAP, confirming it works. Had to change knob mode in factory settings to make the volume knob turn work, and if course all panel key settings.

I hoped the acc off delay would make a change of the turn off when opening front door, but this remain the same.

One major difference is the sound level, it is now really loud, I now use volume setting 4 to 5 (of 30). On the GS mcu I used 16-19...
[MTCD Android Head Units General] marchnz:
Hi, thanks for posting your experience. Did you trim your volume levels in factory settings? I found I had to trim the radio volume down to match the relative levels of system, video, BT etc.

Sorry to hear the latest HA MCU didnt resolve the door opening turn off.

- M
[MTCD Android Head Units General] syk02jcb@hotmail.com:
Hadn't trimmed the voice settings no, did this and audio is back to normal. Thanks!
[MTCD Android Head Units General] marchnz:
You're welcome. Thrilled to see others getting the same enjoyment out of upgrading their old units and also others where the sellers arent providing mcu updates.
[MTCD Android Head Units General] Bose321:
Updated my GS 2.43 to HA 2.52. Got that unmatch error, but flashed the backed up .cfg file and now it seems to work fine. Can I make changes in the factory settings or would that cause the error again?
[MTCD Android Head Units General] 1-2-Hak:
It did for me but give it a shot and see. Just have to reflash cfg if it does.
[MTCD Android Head Units General] bluemask69:
i have the same GS 2.43 and want to update to HA 2.52. Where is the mcu config to save? Thanks
[MTCD Android Head Units General] dark_lord86:
I got unmatched error to, on gs.

How you flash backup cfg?

Edit: sort it!
[MTCD Android Head Units General] bluemask69:
how you solved the problem?
[MTCD Android Head Units General] leonkernan:
Just converted my old Xtrons TD618AS PX3 to HA 2.52

Easily done, proof that the MLT type MCU is compatible as well.

Only trick was dmcu.ext needs screen:4 for the 6.2 inch 800x480 screen in this unit.

All of the touch buttons were correctly supported without any configuration required.
[MTCD Android Head Units General] norekm:
Thank you, it suffices me.
[MTCD Android Head Units General] akslow:
Could you upload somewhere that MCU 2.72 GS version?
[MTCD Android Head Units General] Danno1975:
Audio tech direct are apparently sending me a link to an update on Monday which they reckon sorts the google instability. Will remain to be seen what they send. If it’s worthwhile I’ll share it.

Not holding me breath though :)
[MTCD Android Head Units General] ZeligPC:
https://www.dropbox.com/s/rhrxeocosdbn4ii/dmcu.img?dl=0
[MTCD Android Head Units General] wobbletop:
Has anyone with a KGL 800x480 unit been able to update beyond KGL 2.54? How about anyone with any 800x480 unit?
[MTCD Android Head Units General] typos1:
The screen resolution has nothing to do with the MCU - MCUs are the same for ALL screen resolutions.
[MTCD Android Head Units General] wobbletop:
Do you have a 800x480 unit?
[MTCD Android Head Units General] marchnz:
Read Page 1 OP. Done.
[MTCD Android Head Units General] wobbletop:
JHC, if you don't have an 800x480 unit, don't bother responding. You think I don't know about the dmcu.ext file? I was one of the first to figure that out for these units.

I would just like to know if someone else was successful. Isn't that what this thread is for?
[MTCD Android Head Units General] marchnz:
MCU cross compatibility, did you have anything else you wanted to contribute to the thread subject.
[MTCD Android Head Units General] solmer:
Hi ZeligPC, any improvements with the new 7.2 MCU?

Thanks in advance.
[MTCD Android Head Units General] freaksamael:
Have a Winca Top Road S190 platform (px3 800x480) with MCU version MTCD_ZH_V2.60a_1 Is there any known compatibility or a newer version? Thanks!

From support I have this download link https://mega.nz/#!12QilTYD!GxQbtB2wc8_C1H4WUmxWcVdlCxo4odldvMTHMAR6Omk for MCU. Never tried to flash the unit so please be aware and carefull.
[MTCD Android Head Units General] typos1:
You dont have a Winca, you have a ZH unit. Dont think anyone has tried a ZH MCU yet, you ll have to try it yourself.

---------- Post added at 06:03 PM ---------- Previous post was at 05:58 PM ----------

Oops, sorry, my mistake.

Done, lol.
[MTCD Android Head Units General] ZeligPC:
Absolutely nothing.

To be honest, I'm tired of wasting my time installing updates (both MCU and ROM), that - despite of changelogs - are always the same since months: all the same bugs are still there, no new functions, no visible changes at all...
[MTCD Android Head Units General] typos1:
There are no MCU changelogs. Its always best to update to the latest MCU if available, even if you dont always notice any difference, its not a waste of time.
[MTCD Android Head Units General] joules33:
Two differences i saw cosmetic and unit can work with both obd and phone by Bluetooth that's all for rom and absolutely nothing for mcu
[MTCD Android Head Units General] marchnz:
I have seen some minor improvements and Bluetooth handsfree improvements. I would agree that some updates appear purely cosmetic.
[MTCD Android Head Units General] zhafranabqory:
also updated to MTCE 2.71

i got problem on steering wheel setting.

Actual setting of steering wheel different with selected icons . how to solve this problems?

thanks
[MTCD Android Head Units General] ZeligPC:
My BT phone and OBD are working (bad...) exactly the same as before: they connect at the same time, but OBD apps like Torque have problems to connect to OBD (I have to retry connection many times before success, then it works fine) and phone sometimes didn't connect at all on startup and I have to reboot the unit to have it working again... :eek:

And... I think we are a bit OT discussing about that in this thread... :o
[MTCD Android Head Units General] typos1:
What unit have you got ?
[MTCD Android Head Units General] ZeligPC:
KGL PX5 (this one)
[MTCD Android Head Units General] typos1:
Ok, some units have a dual wifi/BT chip but only one antenna (even though there are 2 antenna points on the board), soldering another antenna on may help.
[MTCD Android Head Units General] Kayhan 17#:
My PX3 just died while flashing GS2.72, what can i do now?

All black, no response :\

Open the case and hope for an USB slot?
[MTCD Android Head Units General] marchnz:
Wrong thread, not a q&a.
[MTCD Android Head Units General] Scipy10:
this is the last update rom+mcu send me from Erisin

https://xdaforums.com/showpost.php?p=74758105&postcount=291
[MTCD Android Head Units General] abagos:
Hello,

I can confirm that the MCU from HA (2.61) is compatible with a MTCD_KBT unit (branded Eonon GA2155, and upgraded with a PX5 board).

The update went smoothly although it needed a second attempt without the mcu image to load the cfg and ext files.

HA was chosen because it was reported to enable the shutdown menu in the extra settings, before that the unit would wake up with no touch and panel buttons.

Everything is working, the unit is also much faster and responsive with the new board.

The seller has also sent me an updated MCU (2.41, my unit had 1.98) but I didn't use it, I had already updated to HA_2.61.

Attached for reference.

Thanks for all the help and information,

Alex.
[MTCD Android Head Units General] wobbletop:
Can you explain more on this part?

Do you mean the first time to updated MCU, the display resolution was wrong and keys weren't mapped? And then you removed the dmcu.img, and reapplied the update, and then the resolution and key mapping was correct? That's a very important detail if correct.
[MTCD Android Head Units General] abagos:
Yes, when the MCU was updated, the unit came up with a wrong resolution and key mapping (as indicated in the beginning of this thread, so I wasn't too scared). I removed the image and repeated the process (took some careful touching on the screen to get the right menus) and then it came up correct.

Observations:

1. If I make any change in the factory settings and apply, it comes up wrong again after the reboot and I have to redo the second procedure (is that common?). Please note that I also have upgraded the board to a PX5 so I am not sure how it would behave with the original PX3 (I wouldn't bother upgrading the MCU in that case however).

2. RDS does not work on the radio app, no matter what.

3. (not sure if this is related to the MCU, the android firmware or both) Applications with sound only play on the left speakers. NOT the radio though (so the cabling is fine). I have tried Spotify and youtube over the Internet app. Has anyone else experienced this?

Alex.
[MTCD Android Head Units General] abagos:
I think I know now how it should be done properly:

a) When you apply the MCU for the first time, put the dmcu.ext file together with the image. That will fix the resolution and (in my case) made the unit usable meaning that the touch screen was not too "off".

b) DO NOT include the dmcu.cfg file. That seems to have confused and complicated things and created all sorts of problems (version unmatch, inability to save factory settings, etc.)

c) Go into factory settings and apply what is appropriate for your device.

After that problems #1 and #2 are gone. Haven't tested #3 yet.

Alex.
[MTCD Android Head Units General] Doublecc1:
ES5060PB

I updatet the erisin es5060pb MCU from version MTCD LM 2.55 to 2.62.

Is there another compatible update to MTCE?
[MTCD Android Head Units General] aLkRicha:
hello, what latest MCU is compatible with MTCD KD head unit?
[MTCD Android Head Units General] marchnz:
See post #1. FYI HA is reference MCU as produce regular updates in the forums.
[MTCD Android Head Units General] aLkRicha:
So, you say, i could install latest HA mcu on my KD unit?
[MTCD Android Head Units General] typos1:
Erroneous post.
[MTCD Android Head Units General] akviberg:
I have tried Ha, Gs an KGL on my xrc unit, they are a no go.
[MTCD Android Head Units General] akviberg:
So, i som how managed to convert my XRC unit to a HA unit, installed Malays rom and HA mcu (along with a XRC dmcu.cfg) it worked.

Then i Downgraded to a Stock rom, got a message "unmatched version HA" tried the XRC one, same there "unmatched version XRC".

After this i installd the HA (with XRC dmcu.cfg) again and it worked.
[MTCD Android Head Units General] vttland:
Hello I have a little problems whith my mx mcu.

I have put wrong setting in factory setting, now if android start i have no backlight.

Have you dmcu.cfg? for restore my dmcu ? Or dmcu.ext is need?

I note I have acces to recovery but not to android.

Thanks for your help

I have succeful restore my unit i put wrong dmcu.cfg and after i restore the good parameters

here for people has need dmcu.cfg for c4l

https://yadi.sk/d/BPs9Q5wO3QoM4V

is MX mcu
[MTCD Android Head Units General] ali20042004:
MCU KLD 2.01_1

px5

please
[MTCD Android Head Units General] typos1:
You already have that MCU why do you want it again ? Plus its very old.
[MTCD Android Head Units General] ali20042004:
becuse when I flash may head unite to new firmware , do I need to update mcu to new version or not?
[MTCD Android Head Units General] typos1:
You dont need to no.

But new firmware or old its best to update to the latest MCU you can find.
[MTCD Android Head Units General] amel:
Happy new year! If anyone wants to do radiochim 6686, it is necessary a certain mcu, suitable KLD, I have HA mcu is not working. Constantly preinitialization, it was clear from the log (in terminal "dmesg")
[MTCD Android Head Units General] marchnz:
Youve changed the radio module, do I understand correctly?

If so the HA mcu is fine, just change radio type in factory settings. Yes, ive done this mod on JY and HA MCU and while it worked, in my experience there was no gain/improvement. The 6686 being 'significantly better' is a myth.

My radio module thread here
[MTCD Android Head Units General] subixt:
I have the same head unit as you stated above. Can point me to where you find the MTCD MCU ypu are referring. Thank you!
[MTCD Android Head Units General] typos1:
You dont need this thread its for cross compatible MCUs ie for units that have no support any more or that lack certain features, KLD units are still supported with all features, try the normal MCU thread, there is no need for you to change your MCU to another manufacturer's.
[MTCD Android Head Units General] SkyBeam2048:
This was also not fully clear to me. I thought this thread is about findings regarding cross-compatiblity of any MCU. Here about cross-compatiblity of KLD and HA MCUs.

So what I can confirm regarding this is:

HA MCU works on KLD unit

HA MCU either by general or on KLD unit breaks screen-blanking functionality

HA MCU does not seem to be better/worse in any other aspect (at least to me)

Settings are not cross-compatible

The last item needs some explanation perhaps...

I just made is that when switching MCUs between different vendor flavors your exported settings might not be applied correctly. I could verify this now as I exported my dmcu.cfg to all locations (internal, external sd and USB) so it was located everywhere. After changing my MCU to HA the head unit booted with default settings. So I lost a couple of settings:

Beep volume

DVD, iPod etc. settings

Bootup logo (reverted to default "Android")

Radio region selection

RDS enable/disable

HW type and button illumination settings

AMP attenuation

SWC resistor configuration

So basically when you switch between different vendor MCU you might not have your settings preserved, even if you exported them. I believe this is due to some binary-format of the dmcu.cfg which is slightly different and not universal among manufacturers.

And no, I dont' believe I did anything wrong as when I reverted to MTCE KLD 2.65 the settings were immediately re-imported properly. Just switching to HA MCU seemed to fail importing the dmcu.cfg so settings are reverted to default. Anyway it's quite pointless providing an export button in factory settings but missing an import button which could also point out if there is an importing-issue.

But there is little hope manufacturers are going to release the tools and sources to improve such things in the future.

So the best recommendation I can provide is to create screenshots of every settings page before an MCU upgrade is performed. Especially if you're unexperienced and you don't know what the settings are used for.

However I agree that discussing a specific head unit might be out of scope here but the findings I made are (if not known already) perhaps of value for someone looking forward to install a 3rd party MCU on his unit.
[MTCD Android Head Units General] typos1:
The thread is about the findings of the cross compatibility of MTCD/E MCUs, but the guy I replied to just wanted the latest KLD MCU, hence I directed him to a normal MCU thread as there is no need to use another MCU if you have a Klyde, although advanced users could try if they wanted.
[MTCD Android Head Units General] subixt:
Thank you for taking the time Explaining your findings this helps allot.
[MTCD Android Head Units General] typos1:
But none of that post is relevant to you - as I said you dont need to use another MCU as your KLD unit is fully supported.
[MTCD Android Head Units General] subixt:
I am very grateful for everyone help. However, My question still stands. Where can I find the latest version of a KLD MCU or an MCU that is compatible?
[MTCD Android Head Units General] SkyBeam2048:
Not sure if you read completely my first answer to you (admittedly I have edited it later). I have included a link to MTCE KLD 2.65d on the very last word of the response:

I also recommend you to stick to the official KLD MCU due to the reasons I already explained in previous posts. So no need to look for cross-compatible MCU at the moment. Even though I can confirm HA MCU works on KLD with some limitations explained before.
[MTCD Android Head Units General] subixt:
My apologies. I saw the link to the MCU file. For some reason, my head uni MCU Version is MTCE_KLD_v2.70_1 . But I do not have a copy of this MCU. I should have been more precise.
[MTCD Android Head Units General] mum1989:
is coika product are MTCD/MTCE and MCU compatible ? https://fr.aliexpress.com/store/all...ml?spm=a2g0w.12010108.100004.3.1698c4a73PLEGA

(it's PX5, Android 8.0 etc... same GUI I think )

thanks
[MTCD Android Head Units General] subixt:
I want to thank everyone for being so responsive. I decided to do more thorough analysis. I decided to hook up my old head unit to rule out any issue with the existing hardware and to my surprise find out that my old head unit has the same problem. Long story short. I checked all fuses (they were ok), and I narrow than the culprit to the Harman Kardon Amp that came with the car. For some reason, the rear channel is the only functional one. I am buying a new amp and hopefull, ythis fixes the issues.

The ROM is working correctly. Thank you all once again.
[MTCD Android Head Units General] typos1:
My original reply to you in another thread told you to try the MCU thread, that help still stands - please look in that thread for MCUs in future, this thread is for cross compatible MCUs.

Its not a Coika product, they are sellers, from the look of it its a GS unit. Its not so much "MTCD/MTCE compatible" it IS an MTCD/E unit.
[MTCD Android Head Units General] mum1989:
mmm so, I can probably install Malaysk rom ?

thanks
[MTCD Android Head Units General] SkyBeam2048:
Not sure about this. It's a PX5 unit (likely with 4GB RAM) but as I can read it comes with Android 8.0. Android 8 seems to have different partition scheme. Most of us here are waiting for Android 8 release for their PX5/2GB units but we have been told installation is not just like a ROM update and there are some missing tools or even hardware modifications required to upgrade it. So there was no ROM image and instructions released yet as of my knowledge.

The same issue might apply if you want to downgrade from Android 8 PX5/4GB unit to Android 6 Malaysk ROM. I personally don't think this will just work out of the box. You might end up with a non-bootable system and due to missing publicly available Android 8 ROM you cannot even restore it from recovery. So I recommend you not to try downgrading to any Android 6 ROM if you own an Android 8 based PX5 board.

However this does not affect MCU, you can always upgrade the MCU. As of my knowledge the MCUs are the same for those Android 8 PX5 units. So to be clear, the MCU is for the base board where the SoM (PX5 board) is connected to. The ROM is the software which runs on the PX5 board. So upgrading MCU is safe, but changing Android 6 to 8 or vice versa is currently not tested or supported. Tools might be released in the future though or Malaysk might release an Android 8 based ROM later.

So my recommendation to you is to keep patience and do not try to install Malaysk for your own safety.
[MTCD Android Head Units General] mum1989:
Ok thanks a lot for this long post.

I will wait Malaysk Android 8.0 ROM.

if you want I can dump my new device.
[MTCD Android Head Units General] rs3754:
Hello, I have a problem and it is that the volume button does not work and when I put a mcu of the thread if everything goes but I get some red letters, the steering wheel controls have never worked well but I guess it is the car
[MTCD Android Head Units General] typos1:
Just updated an MLT unit to the latest HA and everything works but not the radio, guess Ill have to try other manufacturer's MCUs.
[MTCD Android Head Units General] serbanowen:
Hi guys,

I did a stupid thing and by mistake I updated the mcu of my MTCD-KGL 1.87 android lollipop 5.1.1 to MCU_JY_v2.86_MTCB.

I have a Mazda 3 2008. Now the headunit does not turn on and the original LCD of the screen says Power off.

I tried the reset buton but nothing changes it just power on the leds for 1 second after I release the reset button.

I also tried MENU+POWER buttons together and the leds flash for 2-3 seconds and then they go off.

Can I enter I recovery mode somehow?

Please help!

Thank you in advance.
[MTCD Android Head Units General] j2gifted:
Just purchase a KLD a53 MTCE unit, and the bluetooth isn't working... I've been searching for other threads but can't find any info.

The bluetooth menu comes up but device name and password are both blank. When you select the search/refresh option, it just searches but nothing comes up in the results.

Attached are the system specs
[MTCD Android Head Units General] :
Try to change the BT module in factory settings to MD725. Most of PX5 use this BT module.