yashsingh1/xdaforums huggingface dataset:
[MTCD Android Head Units General] OldRon:
Which Room do you use, Malaysk?

At the moment I'm running da_anton since it is slim... Malaysk is a bit to "fancy" for me ;)

I'm asking because I got my upgrade unit a few days ago and will change it after this weekend..
[MTCD Android Head Units General] ZeligPC:
I agree about Malaysk ROM... :D

I'm on august 3 stock ROM (and waiting to try august 18 one).
[MTCD Android Head Units General] OldRon:
Can you give me a link to the ROM and MCU?

And if it is a KGL, which brand ist your unit? Mine is an Erisin...
[MTCD Android Head Units General] typos1:
The brand is irrelevant - the only thing that matters is the manufacturer, in this case Kai Ge Le.
[MTCD Android Head Units General] OldRon:
I know... It was just out of curiosity :)
[MTCD Android Head Units General] typos1:
Ah, ok. :)
[MTCD Android Head Units General] fatyus:
Hi there. My car is Ford Focus 2. The MCU version of my multimedia device is called MTCD_VHZ. What is the MCU update file? Thank you.
[MTCD Android Head Units General] msb111:
Hi,

Has anyone tried using the HA MCU on a MX player? I have MX ver 2.55 and Google Maps keeps hanging if I have "Navigation Monitoring" option ON. I think it's an MCU problem that I'm hoping to fix.
[MTCD Android Head Units General] typos1:
Any VHZ MCU, unless of course you want to try an MCU from another manufacturer in which case read the thread which contains all the info you need to try and maybe the results of anyone else who has tried using another manufacturer's MCU on their VHZ unit.
[MTCD Android Head Units General] ZeligPC:
I think you should take your time ad read all the main threads in this forum, you'll find all you need and a lot of useful knowledge about those head units... ;)

Anyway, look here and you'll find ROMs and MCUs links for download.

About the brand, I bought it from one of the many unknown sellers on Aliexpress (Dicola is the name) but, as someone else already suggested, the seller name is irrelevant.

And, BTW, we're going a bit off-topic here... :)
[MTCD Android Head Units General] dark_lord86:
Hi.

Some time ago I installed ha on xtron

I fixed error "version unmatched" with flash of dmcu .config

Now I was flashed last gs dmcu but I got "version unmatched" and I can't get rid of it.

Any help?
[MTCD Android Head Units General] iscaryot:
Theres a thread for mcus in mtcb/c. They got higher versions of mcus then we have here. And it should be compatible with rk3188. So why do we bother with these lower versions here.
[MTCD Android Head Units General] luciancaramlau:
I also have the same troublesome display problem. The phenomenon is due to the return to an older dmc version.

Install dmcu v.2.58 and no "unmatch version" will be displayed.

https://www.sendspace.com/pro/dl/2laeqs
[MTCD Android Head Units General] OnkelDeffe:
I installed an GS 2.56 mcu file on my xtrons TD101AS, which had a "HZC" mcu version installed at first. This worked OK, but since a few days I could not pair my phone with BT anymore AND sending the contacts from my phone did'nt work as expected: there was no space between name and surname, so mtcdialer did'nt work.

In another thread I was told that the contacts problem was solved using another android rom version - (HA 2.59) - I installed it, but BT did not work at all. Then I found an original HZC mcu file 2.58 and installed it - worked ok so far but now ends with the "version unmatched" message at the bottom of the screen. Everything seems to work (and a new BT connection was build up immediately after mcu update) - so it seems that it is NOT a problem with "wrong" mcu file for my hardware BUT: during installing the new mcu file I saw a message that 4 android apps are changed too - so I thing this "version unmatched" message could be a hint that the "bridge" between the android rom software and the mcu firmware does not work as expected - what do you think about it?

So for now I am looking for the android rom version which was "bundled" with the "HCZ" 2.58 mcu file or the latest combination of GS android rom and mcu file (2.58 or 2.59 I think) or the "HA" mcu version 2.59 (hoping it will work on my device)

Uhh - forgot it: should I install the mcu file first or the android file? As I said: during install of the mcu file 4 android apps where updated so it maybe important to install the android rom first?!

Thanks in advance
[MTCD Android Head Units General] dark_lord86:
I tried that, it ok until I flash the cfg file. Without flashing cfg file I can't use my volume knob.

Any ideeas?
[MTCD Android Head Units General] marchnz:
Set knob in factory settings as described in this thread.
[MTCD Android Head Units General] dark_lord86:
Unfortunately, it is the only one that I cannot set.
[MTCD Android Head Units General] basmand:
Hi

What is the latest original MCU file for GS units, I am on GS 2.56_1.

If there is an update to that version, please provide download link

Regards Basmand
[MTCD Android Head Units General] dark_lord86:
Sort it out! The volume knob setting was unde the "other" tab.
[MTCD Android Head Units General] Bose321:
2.58 right now I believe. Search it, there are plenty of links.
[MTCD Android Head Units General] typos1:
The MCU has NOTHING to do with the processor, they are TOTALLY separate.

MTCB/C and MTCD MCUs ARE NOT compatible with each other.

MTCB/C and MTCD have different MCUs, some apps that communicate with MCU work on both devices, but YOU CANNOT flash MTCB/C MCUs onto a MTCD unit or vice versa, this is why people bother with "the lower versions here".

The version number is lower on MTCD units because they are newer.
[MTCD Android Head Units General] iscaryot:
Thanks for the clarification, i should have know that.
[MTCD Android Head Units General] ArtfulCodger:
Not sure if this is the correct thread but here goes....Customer version is an option in factory settings (from memory) but what does it actually do, I changed it on my PX5 GS unit and it didn't seem to do anything but I didn't do a cold reboot. So anyone found what the different 'versions' offer?
[MTCD Android Head Units General] marchnz:
From what Ive read, can sometimes contain settings such as lower res displays - but nothing documented.
[MTCD Android Head Units General] bjt2:
I experimented with this a while back, I changed the version number to see what would happen and all my hardware buttons changed function. So one of its functions is how many buttons you have and the mapping of the buttons layout. Probably does other things also.
[MTCD Android Head Units General] ArtfulCodger:
Ummm ok thanks I think for the lay person (me) best to leave it alone till someone finds some benefit from playing with it.
[MTCD Android Head Units General] Tabs78:
i have mtcd kgl 1024x600, which mcu i can install?and which do you suggest?
[MTCD Android Head Units General] Petesky:
Dont know what the latest version is but HA v2.56 Has been shown to work with KGL , as in the opening post in this thread
[MTCD Android Head Units General] OldRon:
I can confirm this for my Erisin KGL unit.

I upgraded last weekend from PX3 to PX5 and installed the latest HA stock image and MCU... runny like a charm :)
[MTCD Android Head Units General] RazGame:
Successful install today HA 2.59 on my KD 2.40. After install, I only changed HU front buttons.
[MTCD Android Head Units General] marchnz:
[MENTION=4018808]RazGame[/MENTION] - thanks for sharing your experience. The consensus seems to be that switching to a differing manufacturer MTCD MCU requires factory settings such as buslttons remapped, BT module defined, volume levels set up. Appears that there is some manufacturer specific config baked into MCU code, which is readily resettable through factory settings.
[MTCD Android Head Units General] Guerreiro_BR:
How did you upgrade PX3 to PX5?
[MTCD Android Head Units General] screwey:
Its a physical CPU board upgrade inside the unit.

Here's the physical description. Look for my other posts to review how I set the screen resolutions, and updated the MCU, etc. Hope this helps:

https://xdaforums.com/android-auto/...1-1-to-px5-t3581741/post72734493#post72734493
[MTCD Android Head Units General] zapedge:
hello do your sdcards still work after the change?
[MTCD Android Head Units General] OldRon:
Yes, both SD-slots work perfectly fine...
[MTCD Android Head Units General] nickw909:
Noob post, be gentle with me... ;)

I have a Px5 KGL unit, on v2.47_2.

I have a problem with the front SD slots. SD card with mp3 tracks, music player plays first few seconds of a track then moves to the next track.

Reboot will fix the problem for a while.

If I move the SD card to a card reader in one of the USB ports then it works ok.

Am I correct in thinking the firmware that controls the SD slots will be within the MCU?

Therefore trying HA v2.61 for example might fix my problem?

Thanks?

Nick.
[MTCD Android Head Units General] maniac2k:
Can anyone confirm KLD is also cross compatible? My MCU info is:

MTCD_KLD_V2.58_1

Also, How does one Export/Restore the MCU settings?
[MTCD Android Head Units General] typos1:
If you press the "export" button in factory settings it will add an mcu.cfg (MCU config) file to your sd card which it will then flash along with the MCU, restoring all your original settings.
[MTCD Android Head Units General] SkyBeam2048:
I know. I think my cfg was still on the USB stick I upgraded from. So either it was lost or incompatible and discarded. I don't mind at all as I am able to configure all those settings in 5 minutes. Also I am happy the upgrade seems to have solved my Bluetooth/WiFi coexistence issue. Perhaps it was also good to reset the settings to factory and start over.

I made some old-school screenshots on the original settings of all screens when I got the stock unit. So I know the default settings.

One more thing I forgot: My car does NOT have any CANBUS. I read something that some MCU might be identical but differ in CANBUS configuration and therefore using an incompatible MCU firmware could create CANBUS issues. As my car does not have CANBUS I did not test this regarding KLD -> HA MTCD MCU conversion. Use at your own risk.
[MTCD Android Head Units General] typos1:
What you read is incorrect - each MCU contains ALL the CAN Bus settings for all the cars the unit is compatible with and also a no CAN Bus setting.
[MTCD Android Head Units General] SkyBeam2048:
This is very good. Thanks for clarification. As written I don't have any CAN bus so I cannot prove it so also I can't test whether the CAN bus works fine with this MCU version on my device. But it's good to know that all implementations are included, always.

I guess what I read is the mainly a summary of issues I read where in most cases likely the user misconfigured the CAN bus settings not to match the car. So I guess in most cases it's just about finding the right settings and not about correct MCU then.

Thanks again for clarification.
[MTCD Android Head Units General] typos1:
Its ok, no proof is needed, that just how it works - the CAN Bus settings are the same for all MCUs. :)
[MTCD Android Head Units General] Cid6.7:
What is the password to get into factory settings ?

Cheers
[MTCD Android Head Units General] carlos.forero.56:
126

Enviado desde mi SM-N910V mediante Tapatalk
[MTCD Android Head Units General] Cid6.7:
That was the pw I had before I installed the MTCD HA 2.61 MCU

Its now been changed :eek:

EDIT: Found it its m12345 :)
[MTCD Android Head Units General] Oberbergler:
Has anyone already tested the new MTCE MCU? https://xdaforums.com/android-auto/...asaita-mcu-updates-rockchip-px5-octa-t3575155

I am curious to know if it can be installed without any problem on a GS unit :)
[MTCD Android Head Units General] typos1:
Pretty certain it can, I will be trying it later. I think its for HA MCU units, so to try it, I would flash an HA MCU using [MENTION=4974080]marchnz[/MENTION]'s Cross Compatible MCU thread as a guide, then flash the HA MTCE MCU. Thats how I will try it.
[MTCD Android Head Units General] marchnz:
Applied today - on my originally JY MTCD - after a brief compare against an earlier HA in a hex editor.

Indeed after applying HA MCU MTCE 2.65f the MCU reports [MTCE 2.65f].

Inital finding - anecdotally BT handsfree audio is improved. I don't notice any audible clicks or pops. Havent tried a2dp or google maps, Gmaps hang was intermittent for me anyway.
[MTCD Android Head Units General] Oberbergler:
I`ve now installed the MTCE MCU and first I`ve got the "Version unmatch" error, but after reinstalling the GS MCU and then switch another time to the HA MTCE let it disappear.

Everything is working, for me bluetooth hands free audio is like before (maybe because I have another chip: SD-968; but never had problems), the A2DP sound quality is highly improved and RDS works better :)
[MTCD Android Head Units General] marchnz:
Thanks for posting - great to read another GS success story and a clear method for installing MCUs on GS.
[MTCD Android Head Units General] Cid6.7:
Has anyone tried the MTCE on a Sofia MTCD_HXD ? Currently on 2.15

Or could a nice person much smarter than I stick it in a hexeditor for comparison..? ;);)

I havent been seeing any HXD's just me & 1 other.

TY
[MTCD Android Head Units General] typos1:
Its been verified by [MENTION=4974080]marchnz[/MENTION] and [MENTION=744370]ikerg[/MENTION], so no need to verify it again, as all MTCD/E MCUs are the same regardless of processor, go ahead and flash it.
[MTCD Android Head Units General] inde_pkv:
I have just flashed it (MTCE 2.65f) on my MTCD KSP and it worked. Nothing improved i noticed yet. Keep checking if it fixs my bluetooth problem.
[MTCD Android Head Units General] roly01:
Ive also applied the MTCE 2.65 to a PX5 hotaudio unit but have seen no improvements regards the bluetooth streaming issues
[MTCD Android Head Units General] bettuccio:
Can I install it on my PX5 MTCD MX too? I never changed MCU because I think it is not interchangeable. With this "MTCE" can I do it? Has anyone already tried it?
[MTCD Android Head Units General] typos1:
Are you serious ?? You thought it is not interchangeable and you say that in a thread specifically about interchanging MCUs ?? !!
[MTCD Android Head Units General] Cid6.7:
Also flashed it dont notice anything yet sound or bt quality wise, but I just noticed my main SD card used for the maps wont mount. The one beside it is working fine..
[MTCD Android Head Units General] typos1:
Youre still using an SD card for maps ? Surely theres enough space on the ROM for them ? (Not that it would solve your problem). AFAIK the MCU shouldnt affect the SD card mounting.
[MTCD Android Head Units General] Cid6.7:
Haha idk its just still in there from when I bought it..

Ok TY I'll see maybe somethings funky with the card or slot
[MTCD Android Head Units General] bettuccio:
in fact I did not hear anyone switching one MCU MTCD MX with another. I've never been certain. In this case if you confirm this, it means that MTCE is probably the same way. I prefer to be sure about this I asked.
[MTCD Android Head Units General] typos1:
If you read the thread youll see that its no problem to switch back if it doesnt work.
[MTCD Android Head Units General] bettuccio:
yes, I read a long time ago. I already have MCU MX backup setup. I just wanted to know someone who had already tried to change with great success.
[MTCD Android Head Units General] flaix66:
Hi all

i ve got an Xtrons PB96MTVPL

The original MCU was MTCD GS V2.43_1

I try to flash to newest MTCE 2.65

and unfortunately after flashing it i ve got some troubles

tactil commands are reversed and the steering wheel buttons and front buttons didn t work anymore

Any idea ?

Fred
[MTCD Android Head Units General] typos1:
Did you export your settings before flashing ?
[MTCD Android Head Units General] flaix66:
unfortunately not :/

i ve got Xtrons PB96MTVPL

any idea of how to recover the functions ?

you already heard about this ? reversing the tactil ?
[MTCD Android Head Units General] typos1:
You dont have an "Xtrons", theres no such thing, Xtrons are a seller only, you have a GS unit.

You will have to read the thread to find out have to reset your settings.
[MTCD Android Head Units General] flaix66:
i understand what do u mean

i flash with MTCE after read about cross compatible MCU

and i explain what kind of problem i have making this

it could be usefull for somebody else

i read the last 4 hours the whole last thread of the forum to find someone who had the same pblem :)
[MTCD Android Head Units General] typos1:
I think the problem is related to cross flashing an MCU from a different manufacturer rather than the fact that you flashed an MTCE MCU, I think it can be corrected, wait til [MENTION=4974080]marchnz[/MENTION] reads your posts, I m sure he ll be able to help.
[MTCD Android Head Units General] marchnz:
Hi

From OP:

As always, check first (suggest confirming MTCD, MCU Chip part number, view/compare the fw files, ensure you have original MCU FW,

backup MCU settings or document the settings to ensure your hardware controls, volume control, bluetooth, radio, canbus etc are setup correctly)

. Apply at your own risk.

Options might be for you to create a new thread, or ask in Q&A for someone who has a GS that may share their factory settings. Did you try reapplying original GS MCU?

Good luck.
[MTCD Android Head Units General] flaix66:
I read on a post a little higher that it was fully functional

that the newest MTCE 2.65 was ok for GS headunit

i re flash with MCU GS V2.43_1 as it was before but the x axis (horizontal) of the touchscreen stay swapped

i read all your post .. i try to find advanced options by entering the factory settings with password m123456 that does more options than 126

no chance
[MTCD Android Head Units General] trap63:
Me too...

I Installed a PX5 dasaita MCU v2.59 on my GS....'cause I read too late description in this thread (it's a bit misleading) https://xdaforums.com/android-auto/...asaita-mcu-updates-rockchip-px5-octa-t3575155 . Now GS starts but out of range for display settings and out of frequency, unable to switch between any menu, I tried to install GS MCU 2.56 with success but still boot up this way. I tried to recovery and flash again and updating system...no results. I tried FW 2.43, same results.

Are there any option to restore as original one? mine is 800 GS PB76HGTAP (Xtrons) flat.

I tried to insert dmcu.ext with :1 and :4 line , no success
[MTCD Android Head Units General] trap63:
Hi mate, I am on trouble same HW. Can you save for me your .cfg? I am not able to return to previous settings after flashing to HA on GS, thanks
[MTCD Android Head Units General] Bose321:
Sure. I have one backed up on a USB at home, so when I get home I'll send it to you.
[MTCD Android Head Units General] flaix66:
cool :)

post it in a public space
[MTCD Android Head Units General] Bose321:
Sure, will do.
[MTCD Android Head Units General] trap63:
and...not able to return on GS to 800x400 , I tried to insert dmcu.ext line:1; 3 and 4....any suggestions?
[MTCD Android Head Units General] Cid6.7:
I have a HXD unit on 5.1.1 and had the option to change BT settings under factory settings, but since upgrading the MCU from 2.15 to all these latest MCU's from 2.61 2.56 HA etc I am unable to get these settings back I am no longer able to select a different BT option. Can someone with a 5.1.1 unit with the ability to select these options let me know which MCU your on please :) I have tried reverting back to default reflashing 5.1.1 & 2.05 MCU

EDIT: I can confirm that these settings are controlled by the OS Version on INTEL ONLY, I just installed 6.0 & now have the ability to change them, I did not update the MCU wich is still at V2.05 I'll update & see what changes are made.
[MTCD Android Head Units General] typos1:
You have an Intel unit dont you ? I think it only applies to them because AFAIK on all the Rockchip ones its controlled by the MCU.
[MTCD Android Head Units General] Cid6.7:
I do yep ;)
[MTCD Android Head Units General] typos1:
Thought so, that means your previous post ONLY applies to Intel units.
[MTCD Android Head Units General] Cid6.7:
Yes it does :) Now I just have to figure out how to root the dang thing.. Never used adb before :fingers-crossed:

---------- Post added at 04:35 PM ---------- Previous post was at 03:48 PM ----------

MCU MTCE 2.65f https://www.sendspace.com/pro/dl/ufie8k IS NOT COMPATIBLE WITH INTEL SOFIA RUNNING 6.0

You'll have the unmatch error in red and all sorts of other weird stuff going on. Right now my unit is blinking at me in recovery mode then entire screen just keeps flashing & eventually it'll reboot on its own, then it'll boot up & do it all over again.

And you wont be able to downgrade it ! You will get MCU Version unmatch errors & it'll fail.

I've tried my HXD dmcu.img & currently trying more to see if I can get back running normal.
[MTCD Android Head Units General] Oberbergler:
For all those with a GS: Our unit is compatible with the MTCE MCU but you have to restore your settings and maybe to manually reconfigure your touchscreen and buttons. There is a simple function to do this in the factory settings (126) which is called key study. My touchscreen was also swapped by the x axis. I had to go with the swapped touchscreen into the settings, configure it, reboot the unit and everything was fine. For the buttons you have also the possibility to use short press and long press buttons, which is great because our units (at least mine) has only five buttons and no return button. So I use now the power off button as return in short press mode and power off in long press :)
[MTCD Android Head Units General] Bose321:
Here it is: https://gerbenbol.com/android/dmcu.cfg

For others, this is my GS config. Use at own risk.
[MTCD Android Head Units General] flaix66:
thanks dude

work fine
[MTCD Android Head Units General] sadaghiani:
Can I use the update HA MTCE 2.65 (MTCE_HA_V2.65f) for mtcd kld mcu ?

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

https://yadi.sk/d/umCvHqCDzHccr/All dmcu for PX3, PX5, Intel Sofia3g/HA/dmcu
[MTCD Android Head Units General] TOMMYX2:
looking for my Original MTCD KLD V2.59 Mcu Image,because with other Mcus i get always Version Unmatch Error.

And with my Mcu Config File from 2.59 its all working ok,but after a full Reset its the Unmatch Error back and all my Mcu Settings are lost:confused:.

My Radio is Pumpkin:

http://www.autopumpkin.de/pumpkin-7-zoll-double-din-android-6-0-universal-autoradio-multimedia-player-mit-gps-navigation-unsterstutzt-bluetooth-octa-core-ram-2gb-rom-32gb.html
[MTCD Android Head Units General] typos1:
Pumpkin are sellers only, your radio is a Klyde unit, hence the "KLD" in the MCU, have you read the whole thread ?
[MTCD Android Head Units General] TOMMYX2:
yes and have you read my post?I get Unmatched Error.

I have found now KLD V2.50 here in the Forum,and all working again.

i Have test it with HA MCUS,LM and othe Mcus for MTCD Unit and i get always a Unmatched Error,thats not cross Compatible:crying:
[MTCD Android Head Units General] chris4507:
Please can you point me in the direction of the kld mcu as i screwed up i flashed ha mtce and says virsion unmatch in red on screen so i flashed ha mtcd still the same so i need kld to go back normal
[MTCD Android Head Units General] TOMMYX2:
you have PM;)
[MTCD Android Head Units General] chris4507:
Yes got it thank you gunna flash it later do u know what differnces from mtcd and mtce as i know kld do a mtce just wondering what benerfit of the update would of been?