yashsingh1/xdaforums huggingface dataset:
[MTCD Android Head Units General] makes2068:
Thanks for the links.

The mcu zip file contains only one img file.

Version 1.90 contains three files.

Is this correct? Any risk flashing this on Erisin 3015?

Getapped and getalked with 6603
[MTCD Android Head Units General] dortmundez:
das ist richtig.
[MTCD Android Head Units General] dongali:
Added to the OP! Thanks [MENTION=5182670]PhopsonNY[/MENTION] for providing the MCU!
[MTCD Android Head Units General] makes2068:
Maybe you can add the 1.90 on the first page, too?
[MTCD Android Head Units General] dongali:
I have already added LM 1.98. The provided links to 1.90 are dead.
[MTCD Android Head Units General] makes2068:
Any experiances with this mcu on Erisin 3015?

Don´t want to brick my unit ;)

EDIT:

Could someone please update first page with the common update information:

After updating mcu, all radio station presets are gone. Canbus-Setting is gone. Hardkey-Mapping is gone.

All has to be done again, so please notice your settings befor updating mcu.
[MTCD Android Head Units General] guimolle:
Hello everybody,

Is that someone could help me to create a new account for 4PA.RU because i don't read Russian !

Thank you very much !

My mail in PM.
[MTCD Android Head Units General] makes2068:
Translate the site with google chrome.
[MTCD Android Head Units General] guimolle:
Yes but the captcha is write in Russian but is a captcha and google translate don't work :(
[MTCD Android Head Units General] sodiumspain:
dont be afraid. i update mcu and rom yesterday and its works.
[MTCD Android Head Units General] emarcin:
The new version dmcu 1.96a_1 for GS

http://www.mediafire.com/file/9omsiwwzkgj9vh7/dmcu.img

https://yadi.sk/d/N6C99Uk933dze3

https://mega.nz/#!OMdWSCAI!RqCobndwzCr7Z5_kAM1Fwqa7bQcCy0akWgCmhAzROh4

My screenshot of the software Malaysk
[MTCD Android Head Units General] typos1:
Make note of what everything is set to, then apply the settings your self. You can also read the Cross Compatible MCU thread which tells you how to set other things.
[MTCD Android Head Units General] Xorit:
Just FYI the MX2.91 MCU seems to break the pull down menue.

Some guys in HAL9ks ROM thread figured that out and it was confirmed by others inkl me, that downgrade to 2.90 fixes it.

---------- Post added at 11:42 ---------- Previous post was at 11:42 ----------

Just FYI the MX2.91 MCU seems to break the pull down menue.

Some guys in HAL9ks ROM thread figured that out and it was confirmed by others inkl me, that downgrade to 2.90 fixes it.
[MTCD Android Head Units General] jorisvervuurt:
For those who are looking for updates for their MX/MX2 MCU:

Attached is a new MCU update (MTCE_MX_V2.94)! :D

This update seems to have fixed the 'automatically' closing pull-down menu. :cool:

As always: use at your own risk!
[MTCD Android Head Units General] woozie.2007:
For the LM nothing new?
[MTCD Android Head Units General] TT_Vert:
Curious was your been every 10 seconds? How did you resolve this?

Dave
[MTCD Android Head Units General] ursel666:
hello, I have a Tristan Auron Android 8.0 car radio,whit the MTCE_LM_V.2.75_2..vom ​​dec.6.2017.. there is a newer version ..? the search has so far not found suitable.
[MTCD Android Head Units General] typos1:
Yes, theres version 2.88 in [MENTION=9297693]cs-x(RU)[/MENTION]'s sound mod thread, it has enhanced audio.
[MTCD Android Head Units General] ursel666:
sorry, I can not find the said file .. did you have a direct link for me ..?
[MTCD Android Head Units General] typos1:
https://xdaforums.com/android-auto/...ent/mod-cs-x-mod-mtcd-e-mcu-firmware-t3816042
[MTCD Android Head Units General] ursel666:
ohh command back, I have a typo inside drinne .. I mean the file, MTCE_LM_V.2.75_2..vom ​​dec.6.2017..but for the gibs probably no new update .. ??
[MTCD Android Head Units General] typos1:
Sorry I dont really understand any of that.
[MTCD Android Head Units General] ikerg:
Check the thread...2.88

Enviado desde mi SM-G950F mediante Tapatalk
[MTCD Android Head Units General] ursel666:
So I had in my first post this stated..MTCE_IM_V.2.75_2..but I have had MTCE_LM_V.2.75_2, version on it .. instead of the I I meant the L..have found the right MTCE_LM _. .and works great ..

Thanks, friends ... went great ..
[MTCD Android Head Units General] amershi:
I install MTCE-ksp_v2.89 the device file was mtce_ksp_v.2.80_1

now the screen touch is Upside down so that you press left when you need to open the right icon

When you click the Settings icon opens Googleplay.

What must i do

Thanks

---------- Post added at 02:01 PM ---------- Previous post was at 01:48 PM ----------

this link is not working

MTCE-KSP-2.80sp
[MTCD Android Head Units General] jorisvervuurt:
For those who are looking for updates for their MX/MX2 MCU:

Attached is a new MCU update (V2.96)! :D

As always: use at your own risk!
[MTCD Android Head Units General] meuhmeuh51:
hello, the link does not work mtce_mx_v2,96.zip. I have an error.

Édit: the link is working again. thank you
[MTCD Android Head Units General] cs-x(RU):
please, download all MCU firmwares from the thread
[MTCD Android Head Units General] tkay564:
Hey, I have an Eonon GA 9153a in my Passat B7 with Dynaudio. Everything else works quite well except for the EQ and balance/fader settings of the device. Those do not work at all.

I am sure that the problem is not with hardware (Eonon sent me a new device to replace the first one) but more like a mcu-file issue. I already had one mcu-file that made the eq and balance settings work ok but there was a version unmatch and an irritating beep.

Eonon has sent me a couple of mcu-files that do not have the unmatch errors but then the eq and balance do not work. Would someone here know what to do to fix the issue? Thanks!
[MTCD Android Head Units General] typos1:
Eonon are sellers, not manufacturers, "GA 9153a" is a name made up by them, please quote your MCU to identify your unit.

There should be no mismatch errors if youve flashed an MCU with the correct one, you ll only get those errors if you flash one from another manufacturer.
[MTCD Android Head Units General] tkay564:
Oh, sorry. These are the ones Eonon provided me to try with: MTCE_HT_V2.84 (all works except eq and balance) and MTCE_WWW_V2.85d (all works but a version unmatch).
[MTCD Android Head Units General] typos1:
Theyve provided you with 2 different MCUs from 2 different manufacturers, thats why you have the problem.

Eonon usually sell Klyde units (KLD MCU) WWW MCUs are also made by klye, m guessing yours was WWW origianlly ?
[MTCD Android Head Units General] tkay564:
No, the oem was the HT version (no eq/bal, otherwise ok). Support sent me the WWW file that works otherwise but gives a nag of version mismatch.
[MTCD Android Head Units General] typos1:
Ok, but its still the same problem - youre getting the mismatch error cos you flashed a WWW MCU on an HT unit, basically you flashed the incorrect MCU.

See the "Cross Compatible MCU" thread for how to stop the error.
[MTCD Android Head Units General] tkay564:
Yep, i understand how to get rid of the error, but how to get rid of the eq/balance problem?
[MTCD Android Head Units General] m184:
Hi, what is diffirent mx vs mx2 ?
[MTCD Android Head Units General] typos1:
Dunno, HT is a new make so there arent any other versions around to try.

I d suggest using the WWW MCU and getting rid of the error then.

---------- Post added at 05:11 PM ---------- Previous post was at 05:02 PM ----------

Slightly different versions from the same manufacturer, think theyre interchangeable though, but export your settings before trying.
[MTCD Android Head Units General] geowiwi:
MX2 is without logos.
[MTCD Android Head Units General] jorisvervuurt:
They should be fully compatible (from MX to MX2 and the other way around). The only difference I know of is that the MX2 version does not include the car brand logos (the one you see when the head unit is booting). I’d just install the MX version. ;)
[MTCD Android Head Units General] iwl:
Flashing wrong MCU what happens worst?

Can I brick device or always flash another?
[MTCD Android Head Units General] typos1:
Depends which wrong MCU, one from a different MCTE/E manufacturer than your device, it should be recoverable, one from a totally different device, it may brick it. Its easier to NOT flash an incorrect MCU unless you know what youre doing and have read the "Cross Compatible" thread.
[MTCD Android Head Units General] gforums:
You know what has been added or optimized?
[MTCD Android Head Units General] iwl:
HA (Hotaudio?) seems to be biggest maker with most updates.

I was considering trying their MCTE MCU on my MTCD LM (what is LM?).
[MTCD Android Head Units General] jtrosky:
From my experience, you usually don't notice anything different with updated MCU's. Only benefit is if you have some known bug with the MCU - otherwise, I'd stick with the MCU code that is designed for your unit. It's not like they are adding new features to the MCU. I've tried many different versions of MCUs and have never really noticed any difference at all. Now I just stick with what the unit came with...
[MTCD Android Head Units General] typos1:
HA isnt the biggest maker, they do update on here though. No point changing to another manufacturer's version unless you have a specific prblem you cant get round, see the Cross Compatible MCU thread before trying, in fact best off discussing it there as thats what its for.

Its best practise to update your MCU if a new one is available.
[MTCD Android Head Units General] jtrosky:
That is your opinion.

My opinion is that if it aint broke, don't fix it. I've never seen a radio manufacturer recommend updating MCU or firmware unless there is a specific issue you are experiencing that the update fixes. In fact, in my experience, they usually recommend that you do NOT update unless you are having an issue becuase it could introduce issues that you didn't have before.

Just becuase something is newer, doesn't mean that it's better.

Obviously, if you are having some issue, then it's worth a shot updating it - otherwise, it's just not necessary.
[MTCD Android Head Units General] typos1:
No, its not my opinion, its established advice given by the majority of users of MTCB/C/D/E headunits on here for the last 5 years, its your opinion that this advice is incorrect, your opinion, which you are entitled to, goes against the established advice.

Youve never seen a radio manufacturer recommend updating an MCU because, Hotaudio accepted, there are no MTC radio manufacturers on xda, or indeed publishing advice on the internet. There are, however, many MTC headunit retailers (Pumpkin, Eonon, Xtrons etc) telling people not to update MCUs, but this is cos they are retailers only, who know very little about the products they sell. And if you read Hotaudio's thread you will see that they do recommend you update.

I totally agree that newer is not always better, but in this case, newer is better and in almost all cases its better to update to the latest MCU if one is available.

Indeed, NOT updating can actually cause problems especially when Android is updated.

Sometimes uploaders also publish the MCU changelog as well and if you read one you ll see there are many minor bugs that are fixed, some you were probably not even aware of, and many other minor improvements in how Android and the MCU interact with each other.

So, to recap, the established advice over the last 5 years is to update your MCU if there a newer one available and this is what most people do.

Your opinion, which you are entitled to, goes against the established advice.
[MTCD Android Head Units General] jtrosky:
Official source?

User advice or a thread on XDA is not a valid manufacturer source or reason to update something that is working fine. Please show me a link to MCU updates from a MTCD/E head-unit manufacturer website? Surely, if they want you to constantly update the MCU, they will make the updates readily available, right? Hell, if that were the case, they would make it so you can download and install MCU updates right from the head-unit (on-line updates). They certainly wouldnn't put the options behind password-protected menus.

In the end, the *seller* of the unit is who sells the item and honors the warranty - and they recommend that you do NOT update the MCU - *especially* if you aren't having any issues. Why? Because it makes no sense and causes nothing but grief for them when people update for no reason. If it just made things better (which means less complaints) and easier for them, they would *gladly* provide MCU updates from the manufacturer and recommend that you install them. Regardless of who actually makes the unit, the seller is the one that you go to for support and warranty. It's no different than any other product - you *always* go to the company that puts their name on the product for support and warranty - regardless of who actually manufacturers the unit or the parts inside the unit.

If the *manufacturer* really wanted you to keep the MCU updated, they would offer dynamic, on-line updates that you could easily download and install right from the head-unit. Truth is - they don't want people messing with the MCU if you are not having any issues - becuase it can only hurt if you don't have any issues or complaints to begin with. If there is an issue that doesn't affect you or cause any issues, then it's really not an issue you need to address - and it makes no sense to fix what isn't broken.

Everytime you go to update the MCU, there is risk involved. Corrupted files, wrong files, losing power during the update, introducing new bugs that didn't exist before, etc, etc, etc - all of which provides no benefit if you weren't having any issues to begin with.

Anyway, I'll wait for the manufactrer source (official site) that says you should update your MCU even if you are not having any issues...

If people want to update the MCU, that is perfectly fine - but I've never seen a manufacturer recommend it if you aren't having any issues (in fact I've always seen the exact opposite).
[MTCD Android Head Units General] jtrosky:
All of that typing, and still no source from a manufacturer where they say it's "best practice" to constantly update your MCU even if you are not having any issues...

That's what I thought.

We'll have to agree to disagree.
[MTCD Android Head Units General] typos1:
I ve covered your point in "all that typing" which you obviously havent read fully, Hotaudio accepted, youll read nothing about updates from any MTC manufacturer, anywhere, they only have websites designed for wholesale buyers.

And even if you could, the advice would probably be the same as it is about sellers, ie dont take too much notice of what they say, they dont know very much about what they make - I spoke to Shenzhen Klyde a few years back about putting 2Gb RAM on the SoMs of MTCB/C units and they just couldnt understand how it could be done, when all that was needed was to fit 2x1Gb modules, instead of 2x512Mb modules. We gave up talking to the manufacturers and people on here (and 4pda.ru) retro fitted 2x1Gb modules themselves.

No one "constantly" updates their MCU, most people update their MCU when a new one becomes available.
[MTCD Android Head Units General] xLeviNx:
Can someone repost the MTCE_HA_2.95? The link to the one that is in sendspace seems to be corrupted on all sources (including the russian website)
[MTCD Android Head Units General] jorisvervuurt:
Unfortunately, there is no changelog for these types of updates.
[MTCD Android Head Units General] dgcruzing:
+1..

Actually I would advise not to update if your system is running fine with the setup you have got going.

My advice comes from my own experience.

While typos1 has been around about offering some good advice. I would also disagree with the lastest 'you should always'... maybe it should read.. caveat "if you have a problem it is best too" or if you upgrade your version of Android then it might "pay too"..

In my case on the Joying which I got direct from Shenzhen on a trip using Chinese contacts.. once I had settle on the big M's rom and MCU.. it went fine for all I wanted it to do..

Thus no added benifits to upgrading..

Just drive the car and enjoy the hands-free experience..

But.. as we can see..

Plenty of people gravitate to these forums due to getting that 1 of of 1,000 piece of equipment that has a fault and thus have to resort to experimentation of upgrading and down grading bits and pieces..

So in the nature of good debate in a open forum.. typos1 don't take this as a gang up on your opinion but as a open discussion with others that are sharing thier experiences .

There is plenty of devices littering the council dumps due to the manufacturers of all shapes and sizes (nations) that can't quiet make that holy grail piece of equipment..thus.. there is open for both sides of this thought..

One of the reasons I took so long to upgrade and buy a unit was to wade through these forums and work out which seems to be the most stable..

Kinda reminds me of the android tv box's..same theory and plenty of consumers screwed over via inferior product being pushed to market..

Carry on gentleman.. lol..

Just like to add..

As always ... due diligence on any flashing..

Bricking things can be painful...
[MTCD Android Head Units General] jogobelo:
My radio is ISUDAR Android 8 PX5 MTCE_GS_V2.94_2 and these updates are sent to me by ISUDAR, for repair of LCD strips. Maybe someone is using it.
[MTCD Android Head Units General] bisy:
Did this update fit for MTCD or MTCE PX3 7.1.2 HU OR only for PX5 HU

Where I can find latest update for XRC PX3 HU?

https://docviewer.yandex.ru/view/0/...mcmFtZSI6ZmFsc2UsInRzIjoxNTQyNzQ3NDY0NTY3fQ==
[MTCD Android Head Units General] typos1:
There are changelogs for MCUs, bu they often get overlooked by the time theyre uploaded here.

You say "in your experience" but you dont say of any problems youve had when updating, so surely you mean your opinion.

And didnt you have an MTCB unit years back ? When there was a period when updating MCUs could cause problems ?

We now have unbrick tools for STMicroelectronics 32bit MCUs so bricking isnt really a problem, not that I ve ever heard of any MCU bricking on an MTCD/E unit.
[MTCD Android Head Units General] dgcruzing:
Just to set the record strieght..

You are correct on the first unit..

And yes .. only flashed 1x MCU upgrade..

The beast is still going as went with the car and new owner is happy..

So.. from my experience..which then shapes my opinion.. which is also shaped from flashing kernels and ROMs since 2008..

If the equipment is running to the users expectations. And there is not a need to upgrade to the newest version of software and or there is no hardware anomalies..

Then why advise that it is in the best interest of said user to go screwing up a good thing..

So..as previous poster has stated..

Agree to disagree and leave it at that .

I agree with the opposing experience and thus..

Happy to put forward this experience for others to make up thier own mind on which way they may want to go..
[MTCD Android Head Units General] typos1:
As I said, there was a time a few years back with the MTCB/C units (that use a related but 16bit MCU) that when updating an MCU could cause a few problems, on those different units and only for a short period, this has never been the case with MCTD/E units - almost everyone updates regularly and there has never been similar problems with MCTD/E units.

So I can see why you have formed that opinion, but as I ve said, its best practise to update the MCU if a new one is available and thats what most people do.

And as I also said, if you update Android, you deffo need to update your MCU as well.

I have never advised "that it is in the best interest of said user to go screwing up a good thing", because updating the MCU does not "screw up" anything, as 1000s of posts in this thread prove, myself and others would not advice to update the MCU if a new one is available, if it did "screw things up".

Your "opposing experience" is not relevant as it was with a different type of unit.

Youre entitled to your opinion, but its neither the best thing to do, or what most people do.
[MTCD Android Head Units General] wifi75:
what are the features in this version?
[MTCD Android Head Units General] jorisvervuurt:
Unfortunately, these updates do not come with a change log.
[MTCD Android Head Units General] typos1:
Yes they do, but not all original uploaders bother to upload them.
[MTCD Android Head Units General] slidefriday:
somebody here have leads to MTCE_CSN supports? thank you!!!
[MTCD Android Head Units General] stefcio007:
I have to agree with dgcruzing.

I'm still running a PX3 unit with 1GB RAM Android 5.1.1, very old right? Well, everything works fine, not perfect but works.

Nothing has really enticed me to upgrade to a newer unit. Manufacturers are still using the same screens as they did back then and that's the main part I would want to upgrade. Until then, happy driving.
[MTCD Android Head Units General] typos1:
Yes, but it may very well run better if you updated the MCU, but you ll never know cos youve not tried.
[MTCD Android Head Units General] ikerg:
Not right.

Manufacturers have improved the displays.

Now they are IPS....same resolution...but better displays

Enviado desde mi SM-G950F mediante Tapatalk
[MTCD Android Head Units General] jtrosky:
There may be some that have IPS displays, but I'd say that most still have TN displays. I bought two PX5 units and both had TN displays (even though one advertised as having an IPS display!).
[MTCD Android Head Units General] shida:
Hello,

I tried to search in this thread to avoid another question about which mcu i have, but seems not possible to know that, at least for a newbie like me, please help me to point me where i can get a update for my mcu, im keen to use a subwoofer additon in the equalizer apk

This is what i have: 2018-01-23 10:56:39 JY_(R68)_26_C26_6026_CAN

Px5 android 8
[MTCD Android Head Units General] typos1:
I m sorry, but I dont see how its hard to work out, newbie or not - you dont have "MTCD" or "MTCE" in front of your MCU number so you dont have an MTCD.E unit, youre in the wrong thread, try looking in the Android Headunits general forum.
[MTCD Android Head Units General] Eventer_:
Hi,

what is the latest Firmware for android6 mtcd hu?
[MTCD Android Head Units General] typos1:
For the MCU, it depends what MCU version you have now.
[MTCD Android Head Units General] meazz1:
I bought a Eonon system, PX5 And 8.0.0.

MCU: MTCE_www_V2_85d_1.

how can I findout if there's a newer MCU out there?
[MTCD Android Head Units General] karimh sanchez:
help

Can someone help me with passing me the mtcd kgl v.2.56

RK3188
[MTCD Android Head Units General] Eventer_:
Hi,

I have MTCE_GS_V2.83_1 (it's a GS HU)

My 6.0.1 FW is from 20180201.
[MTCD Android Head Units General] gigaforce1111:
Hi,

I have Eonon GA9151B with MTCE_HT.

I have a serious problem with the wifi. It Disconnects after a few seconds.

I thought of updating the dmcu.

Does anyone know where can I find HT mcu file?

Does it compatible with other type of mcu files?

Thanks.
[MTCD Android Head Units General] zeyret:
MTCE_MX_V3.00

https://ufile.io/n0w70
[MTCD Android Head Units General] digitalcan:
At last this version fixes my bluetooth interferance issue with radio app. And sound is better now. Thanks!!
[MTCD Android Head Units General] jorisvervuurt:
For those who are looking for updates for their MX/MX2 MCU:

Attached is a new MCU update (V3.00)! :D

MX includes car brand logos (shown while the head unit is booting), MX2 doesn't include those logos.

As always: use at your own risk!
[MTCD Android Head Units General] locum:
Hello,

I have a new car that came with this Head Unit. (A-MEDIA AUTO 1024x600 S)

MCU：MTCD_KSP_V2.09_1 Dec 22 2016 19:42:38

Android：5.1.1

Kernel：3.0.101+rocky@hctr930 #39 Fri Dec 2 15:38:02 CST 2016

Compilation：rk3188-userdebug 17122016.11:21:07

RAM : 1GB

CPU: ARM CORTEX-A9 @ 1.6 Ghz

I am looking for guidance on updating it to newer MCU and Android version if possible.

BTW I already tried to email cusp without luck
[MTCD Android Head Units General] typos1:
The best ROM is here (use the microG set up) :

https://xdaforums.com/android-auto/...rom-hal9k-mod-mtcd-head-units-t3623982/page28

Attached is the latest MCU.