yashsingh1/xdaforums huggingface dataset:
[MTCD Android Head Units General] excessdivide:
Per [MENTION=4974080]marchnz[/MENTION] suggestion I am moving this discussion here from its original posting (https://xdaforums.com/showpost.php?p=74187608&postcount=2125)

Hello everyone,

Big thanks to the heavy hitters here that are making these units actually usable!

I received my Dasaita HA5217-V600 two weeks ago and thanks to having previously scoured these forums, I was able to install it, in my 2016 Toyota Corolla, with relative ease. Everything worked better than expected, and I had great bluetooth sound, strong WiFi connections, my door and A/C controls appeared on screen, my SWC all matched and decent FM reception. My bluetooth OBDII adapter is arriving this week so I'll have to report back on that.

I have been perplexed by my inability to use my A2DP stream anywhere other than the very generic A2DP widget included in the ROM. After a week of toying with it I became bold enough to attempt Makaysk's ROM and the install went beautifully. (Thanks Malaysk!) I was still limited to that widget however. So I when I saw the new MCTE 2.65f MCU update I gave that a try also. Except I goofed up. I somehow, (really not sure how I did this) downloaded and installed a GS MCU update instead of the HA update. As has been previously documented the update worked, but I lost the use of my capactive panel buttons. They no longer react to touch though the option to control their lighting still appeared in the settings menu and they did still light up on headlight activation which proves that the unit could still control them. The panel button reset screen in factory settings is now blank and does not list any keys at all. Once I caught my mistake I quickly updated to the correct HA MCTE 2.65f MCU update. However my panel buttons are still dead to the touch, and now they don't even light up or have the option to change their LED control mapping in the setting menu and the panel reset screen in the factory settings is still blank.

I actually tried to go back to HA MCU 2.60 which what shipped on my unit. The same issue persists. Upgraded back to MCTE HA MCU 2.65f and nothing has changed.

It's so frustrating that one MCU so easily changed the setting and now the original can't seem to restore it.

I have attached pics of the original software and the updated software, as well as the blank panel reset screen.

Any help in getting my panel buttons back would be much appreciated!

Thanks gang!

Updated MCU:

https://1drv.ms/i/s!AsfQ9pSp8e6FrUtCFUB80zQpFXJa

Original MCU:

https://1drv.ms/i/s!AsfQ9pSp8e6FrUrVnLzROkXFqMUv

Blank Panel Reset screen:

https://1drv.ms/i/s!AsfQ9pSp8e6FrUx08tiRzB_CBZJR
[MTCD Android Head Units General] viniciusdasilva:
Hi, marchnz.

The painel buttons configuration screen is like the steering wheel screen. There, press any button of painel to configurate its function.
[MTCD Android Head Units General] excessdivide:
Except the screen does not list Any buttons. That is why I am asking for advice. See the last picture included in OP.
[MTCD Android Head Units General] viniciusdasilva:
That's normal. I saw the picture.

That's already happen to me and I also didn't know how to solve because the list didn't appear.

Only press the physical or capacitive buttons, then will appear the list of commands to choose.

Only after buttons configured they will appear in the list of your last image.

I hope you understood. If not you can call me here again.
[MTCD Android Head Units General] excessdivide:
Thank you. I appreciate you trying to help. Even if I touch the physical capacitive buttons in the Panel button reset screen under factory settings nothing happens. The buttons no longer light up either and the option to control their Led color, or when they light up is also missing which makes me believe that the firmware isn't configured to see them.
[MTCD Android Head Units General] viniciusdasilva:
I see. That's very strange. When I tryed to chance my MCU to a HA version on my GS head unit I also had problems, including the panel lights were off. I didn't remember if I tryed other things, but I remeber that I turned back to GS MCU and changed the light options on factory settings, but it's not works at the first time. Only after I rebooted the HU it works again. Try this or install the stock MCU again. Try to install the stock rom too.

---------- Post added at 05:00 PM ---------- Previous post was at 04:31 PM ----------

excessdivide,

my bad. Sorry. I tryed right now to simulate the configuration on my HU and remembered why I had problems. Instead to press in touch key study instead in pannel key study. Will ask to press on the corners to configurate the screen, then will ask to press the capacitive buttons and to choose each function.
[MTCD Android Head Units General] excessdivide:
Wow! That's was beyond what I expected anyone else to do! Thank you so much!

Sadly, after I configured the touch screen. It simple took me back to the key study main screen.

But really, thank you for your efforts!
[MTCD Android Head Units General] chris4507:
Please delete this post
[MTCD Android Head Units General] excessdivide:
I got it to work! I started incrementally installing Stock ROMS in descending order until I found one that worked.

I had to go back to this MCU/ROM:

-V2.56 --> https://www.sendspace.com/pro/dl/tjnkwj

Then after resetting the touch panel it did take me to the option to remap the panel buttons, and now their LED controls also appear again!

Thanks you soooooo much! that was driving me crazy!!

These units have their quirks but if you can work through them, it is well worth it!
[MTCD Android Head Units General] ZeroZorro:
Thanks, wil try this and hope it will solve some issues I have like device leds on when lights off and visa versa. Also canbus signals are not all read (reverse camera works when shifted into reverse but no alarm sounds when reversing).

Fingers crossed!
[MTCD Android Head Units General] marchnz:
Great to hear. Can you clarify, was Touch panel [RESET] tested in each MCU test, or only when v2.56 was applied? Also which manufacturer MCU v2.56 was applied?
[MTCD Android Head Units General] excessdivide:
I was incrementally working my way through the HA MCU's. I did test the panel reset buttons after each MCU update. Interestingly enough, after I had reprogrammed them, it took 2 reboots to get the Element light option to appear in the factory settings. But everything seems to be working fine now.

I am still annoyed by how restricted the a2dp stream is. I had expected to be able to see and control a2dp stream from anywhere in the system. Alas, I am limited to that a2dp widget which is really bare.

Thanks again gang!
[MTCD Android Head Units General] typos1:
Yes the same applies to MTCB/C units when switching to RGB LEDs in factory settings they need several reboots for Element to show up.
[MTCD Android Head Units General] faria:
some info about MTCE MCU

The new mtce mcus are from the new Rockchip PX3 Cortex A9, 4-core 1.6GHz updated boards running android 7.1.

One of the manufactures using it is WITSON .

Here is an example of my unit : mcu MTCE_MX_V2.65.1 (Please note that THE ABOVE also shows up as an MTCD_MX mcu depending on android version.

The same unit with the old board (Rockchip 64bit RK3368 Octa-core ARM Cortex-A53) Would have have an mcu version : MTCD_MX_V.x.x.x
[MTCD Android Head Units General] csitkiri:
Hy!

Which one would go up in this direction?

A media auto 1024X600

Android: 6.0.1

2016.06.01

SF3GR_M-26-3_cpeg_rk-r2p_bc2-20160629_111639

Kernel:3.14.0+

chun@hctr930#15

Build:sofia3gr_car_64-userdebug 6.0.1 MMB29M eng.hct.20170705.123915 release key

MCU:

MTCD_LM_V2.55_1

Jun 23 2017 13:42:21

HCT2000022096

Thank you!
[MTCD Android Head Units General] bettuccio:
Very interesting. I would try the MCU MTCE MX 2.65.1 that you have. I have a PX5 with MCU MX MTCD native. Where can I find it? Currently I am with a MTCE HA 2.65.
[MTCD Android Head Units General] typos1:
No, the MCU has nothing to do with the processor board - the Intel Sofia units use the same MCUs, the MCU and processor are entirely separate - I have a 2Gb ERAM Nougat RK3188/PX3 unit with an MTCD MCU, indeed most of the units with these boards started out with MTCD MCUs.

ALL MTCD units, using ANY processor can be upgraded to MTCE MCUs.

Witson ARE NOT manufactures, they are sellers.
[MTCD Android Head Units General] arti777:
Mtcd_kld_v2.57

I confirm my MTCD_kld V2.57 to (MTCE mcu kld 2.65d)

PX5 rk3066 octa core A53@1.5G 2GB Honda Accord dual air, Steering wheel working super, nothing changed about my doors still I not see on my android screen just the small screen left for me under the counters (cloks)

I just reset the steering wheel and everything works fine. There is only a problem with Poweramp graphic equalizer - if I do turn it on instead of giving it a louder, on the radio playing normally.
[MTCD Android Head Units General] Oberbergler:
After some time with the HA MTCE MCU on my GS unit I recommend to any GS user to NOT install any HA MCU. My unit started yesterday to have some trouble with the HA MCU. First it didn`t boot anymore, it took about 10 secs to switch to the reversing camera, there was no more boot logo and all MCU settings were gone. The screen was reversed by the x-axis. When I tried to install the GS MCU and restore the GS cfg the unit hang up and didn`t do anything anymore. The screen was on from midday until I came back at the evening and my cars battery was totally empty. I had to unplug the unit and reinstall the GS MCU. Now everything is working but I am not able anymore to let disappear the MCU version unmatch error, even with the original MCU.
[MTCD Android Head Units General] faria:
I dont have to share, its in the unit, i'm waiting for the seller to send the Rom/mcu.

No playing with it until i have a backup rom:D
[MTCD Android Head Units General] typos1:
There are plenty of back up ROMs available on here, you dont need to wait.
[MTCD Android Head Units General] bettuccio:
When you're in possession, please post it. Thank you.

you can back up the MCU configurations. As Typos1 has said, there are many firmware and MCUs to be able to restore.
[MTCD Android Head Units General] MrWaloo:
Since I have sound problem with my (Erisin ES3715V) PX3 MTCD_LM_V2.55_1 with the radio, does this mean that I can update to any MTCE_????
[MTCD Android Head Units General] pedroof:
Just sharing the attached updated MCU from Witson (for MX units) -

Version is MTCE_MX_V2.65
[MTCD Android Head Units General] typos1:
You can update to an MTCE MCU from your manufacturer, if you cant find any then check the "Cross Compatible MUCs" thread. It may fix your sound problem, it may not.
[MTCD Android Head Units General] gomylle:
I stumbled by accident on GS 2.65_3 MCU

http://www.fast-files.com/getfile.aspx?file=148174

I tried it on my GS unit and it works :)

Hmmm. seems like a shady upload host i found. Let me know if there is a better place and I will upload it again

Here is where I found it originally:

https://yadi.sk/d/umCvHqCDzHccr/All dmcu for PX3, PX5, Intel Sofia3g/GS/dmcu
[MTCD Android Head Units General] xxfOxx:
Version Unmatch

Who know how to fix "Version Unmatch" error :( ?

From start I have unit with KLD 2.59_1 and I update it with Android HA (20170901 as I remember) + HA MCU ( so now I get error Version Unmatch at any firmware + KLD mcu. Error gone away when I update unit with HA mcu but in this case I get non-working FM radio

Can anybody help me ?
[MTCD Android Head Units General] luciancaramlau:
You have to go back to the last MCU with which the device was running. After installation, restart the device.
[MTCD Android Head Units General] Kayhan 17#:
I have a 7.1.2 Nougat Radio from Erisin ES4798V, it has a PX3 chip and 2GB Ram according to what i could see in the System Information.

I had previously the MTCD_KGL_V2.60_4 file installed and did an Update to the MTCD_HA_V2.65f_1, then tried installing GS version and back again to the HA version(my android version is now the recent from malaysk).

I have the problem with the "Version Unmatch" message appearing, i must admit that i didnt do any backups of my previous settings but could access a second head unit after i know the factory settings =).

Anyway, does anyone also have an idea where i could find the Stock 7.1.2 Rom which was installed previously or how i could dump it, so in case i want to revert?

Kind Regards
[MTCD Android Head Units General] typos1:
The ROM has nothing to do with the MCU, they are entirely separate so it wont make any difference to your MCU problem. Have you read the entire thread and tried all the methods to remove the version unmatch error ? Have you tried other MTCE MCUs ?
[MTCD Android Head Units General] Kayhan 17#:
i know that the MCU and ROM are different, altough i still would want to know how to revert as the style/Theme of malaysk is not that of my taste

i also read a lot of threads and lost the overview =)
[MTCD Android Head Units General] marchnz:
Resolve is in this thread

Version unmatch

see this post
[MTCD Android Head Units General] marchnz:
Version unmatch

see this post
[MTCD Android Head Units General] Oberbergler:
No, it worked one week with this method.

Now I have the version unmatch error and the only solution to let it disappear is to install the HA MCU but with the HA MCU the head unit is hanging up once a week. So I have now the same problem how xxfOxx and I think that there is no solution as I´ve tried everything to reset, reininstall, different other MCU versions, older, newer.... There is no solution :/
[MTCD Android Head Units General] chris4507:
Hi I have kld and I had unmatched issue and couldn't resolve the only way for me was to use maleskys room but flash a kld mcu now works perfect there's a kld mtce I uploaded to mega and shared link search and you will find also typo1 has some kld in his signature hopefully he has updated with the kld mtce
[MTCD Android Head Units General] typos1:
Ok, so try MCUs from other manufacturers ?
[MTCD Android Head Units General] Oberbergler:
Already tried. Didn´t work :(
[MTCD Android Head Units General] typos1:
If youve tried EVERY MCU from EVERY manufacturer then, I guess yours is one of the few that cant be changed.
[MTCD Android Head Units General] Oberbergler:
Every MCU is working but sometimes the HU is hanging up. My problem is that with the original GS MCU I get the version unmatch error since I have installed the HA MCU and with the HA MCU i don´t get the error bu the unit hangs up sometimes
[MTCD Android Head Units General] marchnz:
What options have you tried setting in factory settings? Customer Version? Following the update to HA or GS, did you power through unit off fully by disconnecting from battery for up to 30 minutes?
[MTCD Android Head Units General] Oberbergler:
I've tried to install the original dmcu.cfg and all customer versions (HA has 2 and GS has 3). The unit was powered off by disconnecting it from the battery. Without success.
[MTCD Android Head Units General] Kayhan 17#:
Hey mate,

i somehow had it gone, maybe with the dmcu.cfg which i put from another machine(first wipe cache, factory, flash MCU with dmcu.cfg), i still would want to know how i could get the ROM dumped and flash to STOCK ROM as i didnt like Malaysk ROM :\

Unfortunately *#hct#root# doesnt works, i could get access on the device via WIFI and ADB, any idea?
[MTCD Android Head Units General] typos1:
This thread is about cross compatible MCUs, there are plenty of other threads about ROMs and quick searhc will tell you all you need to know.
[MTCD Android Head Units General] ZeligPC:
Just upgraded from KGL 2.54 to MX 2.71 (MTCE), without any problem! :cool:

Just had to reprogam function keys on panel and steering wheel.

At first sight, I can't see any improvemnt... :rolleyes:
[MTCD Android Head Units General] Kayhan 17#:
i could find my stock rom now, and flashed KGL_V2.54, with that one everything is ok, when i flash HA_V2.71 it gets me the version unmatch error.

My HeadUnit came with MTCD_KGL_V2.60_4, when i only could get the latest KGL version somewhere :(:confused:
[MTCD Android Head Units General] marchnz:
Search thread.
[MTCD Android Head Units General] :
The last available KGL mcu version is 2.54, for the latest you can ask to your headunit reseller.
[MTCD Android Head Units General] Kayhan 17#:
Look at my screenshot, i made this before i started playing around with the software of the device
[MTCD Android Head Units General] typos1:
No need for that, just get a later one from xda, there are loads of links.
[MTCD Android Head Units General] bjt2:
That's a shame you didn't make a copy (If that's even possible?) I haven't been able to find the official 2.60 for KGL anywhere.. It isn't anywhere on this site.
[MTCD Android Head Units General] Kayhan 17#:
I found the Stock Rom, i am right now updating my linux virtual machine and will try to do some Android Kitchen stuff to root that thing, afterwards put in on my colleagues Radio and check how i can dump that MCU.
[MTCD Android Head Units General] typos1:
Why do you specifically want that version ? Seems strange, just use a later updated MTCE one.
[MTCD Android Head Units General] :
I never said it not exist newer KGL version, i said just the last available to download.

I think is need some sort of recovery to extract the mcu image, not just a rooted system.
[MTCD Android Head Units General] typos1:
Ok, it doesnt matter that you cant find 2.6 because newer versions are available.

As I ve already said you CANNOT make a backup of an MCU, rooted or not. the MCU has NOTHING to do with Android.
[MTCD Android Head Units General] bjt2:
I'm looking for an official KGL MCU as many people seem to be having issues with version errors after upgrading.
[MTCD Android Head Units General] Petesky:
A few posts back someone went from KGL 2.54 to MX 2.71 (MTCE) without any problem but I'd backup settings first so you can flash them back

Or you can download the KGL 2.54 from here

https://yadi.sk/d/umCvHqCDzHccr/All dmcu for PX3, PX5, Intel Sofia3g/KGL/dmcu

it looks like thats the latest one
[MTCD Android Head Units General] g.mariano85:
Hi guys, I have an autoradio Android 7.1.2 px3 with mcu mtcd chs v2.56 and i would like to know if there are updates or if there are some compatible mcu without risking the breaking of the stereo
[MTCD Android Head Units General] marchnz:
Hi,

You would like to know if there is an MCU update available for [CHS]? Read the post describing that the MCU file is validated by recovery before it is applied? A quick search of this thread suggests other have tried and received version mismatch.

What did you discover before posting this question?

Others have successfully got passed version mismatch OK, others haven't, ostensibly having documented & exporting their factory settings before upgrading, resetting factory settings after upgrading MCU and/or factory resetting android or flashing MCU vendor android.

Given you don't appear to have found references to CHS in this thread outling the process; testing another vendor MCU might be too risky for you.

Please contribute in a helpful way.
[MTCD Android Head Units General] typos1:
Yeah, but why bother to search threads when you can try and get others to do it for you ? ! :)
[MTCD Android Head Units General] marchnz:
Don't know about you but seems the number of new member posts which don't observe the forum rules or bother to search/help themselves/learn seems to be on the rise.

Granted, a wiki needs to be created for MTCD, but almost need an autoresponder for new member posts/repeat questions for questions already asked.
[MTCD Android Head Units General] Sylvan151:
Google Play not working after DUPDATE 09082017

Hi everyone.. been a while since i am back here. Here we go.

I updated my Radio from MTCD HA 2.51 to MTCE HA 2.71. It is successful.

But one thing which did not work fine!!! Google Play.

Please help.
[MTCD Android Head Units General] Sylvan151:
Fixed it!!!!!

I just reinstall the DUPDATE.img and Google Play works fine!!!!!
[MTCD Android Head Units General] typos1:
I could mod the MTCB/C wiki and turn it into an MTC wiki covering B/C and D/E units with a section for each.
[MTCD Android Head Units General] marchnz:
Sounds like a good plan. I'll contribute as well.
[MTCD Android Head Units General] Danno1975:
I’m having trouble searching to find the latest MTCD/E MCU updates for my KGL current v2.54_5. tried searching in all the relevant threads by KGL and just get post re people saying search as there’s loads on links?.

The links on the first post of the MCU thread all seem like older versions?
[MTCD Android Head Units General] ZeligPC:
I have recently updated my KGL unit to 2.72 GS MCU (MTCE) and latest 7th november ROM.

You find both in the 7th november ROM download in this thread : https://xdaforums.com/android-auto/...opment/mtcd-px5-headunits-repository-t3619906

Please note, that's not a KGL MCU, it's a GS MCU, but it works fine on my device, jut have to reprogram phisical buttons on panel and steering wheel.

Of course you can install MCU update only and then any other ROM you like, like Malaysk if you prefer.
[MTCD Android Head Units General] Danno1975:
Thanks, might have a go, appreciate the heads up.

Did check again and as far as official KGL goes the June V2.54_5 seems the latest.

As I’m not an IT dude and am an android and android HU newbie I think I’ll wait for a proper KGL update this time till I’m up to speed [emoji1360].

Though I can see changing buttons and such is straight forward.

Will do it for sure when the Oreo Rom is ready.
[MTCD Android Head Units General] wobbletop:
I also have a KGL with 2.54 and I'm having trouble updating it. My unit is a 800x480 type and when I update the MCU, the updates I've tried all get the resolution wrong even though I have the proper dmcu.ext file that works with my KGL 2.54 dmcu image.

Could it be that other MCU updates do not recognize the dmcu.ext file? I've tried a couple of the later MCU images (MX 2.71, HA 2.61) and they have the issue.

I haven't tried playing with the settings inside dmcu.ext yet.

Could it be that those that have successfully updated their units all have the 1024x600 sizes?
[MTCD Android Head Units General] Overmann:
KSP MTCD to HA 2.7.1 MTCE seems to work. Exported config before, reapplied settings after.
[MTCD Android Head Units General] superlesio:
Compatibility MTCD <–> MTCE and px3 <–> px5

Hi Guys,

I’m little bit confused about the MCU type compatibilities.

Could you confirm that I’m right ?

My Device px3 2GB RAM has been delivered with the MCU version: MTCD_MX_V2.59_1

Can I make update to the version: MTCE_MX_V2.71 for px5 device ?

Is the MCU from the same manufacturer are compatible (MTCD <–> MTCE and px3 <–> px5)

:confused:
[MTCD Android Head Units General] norekm:
Hello everyone, this is my first post, so please be understanding, also for weak English.

Can you post if the KGL on the Mtce GS 2.72 still has an echo when connecting via handsfree?
[MTCD Android Head Units General] typos1:
MTCE is an update to MTCD, so yes go ahead and flash it. MCUs are the same regardless of processor - there are no "PX5 MCUs".
[MTCD Android Head Units General] superlesio:
Thx for your answer. It works :)
[MTCD Android Head Units General] ZeligPC:
Echo problem is not MCU related, it's ROM related.

Anyway, not tested yet (I make very few calls, sorry).
[MTCD Android Head Units General] marchnz:
Use factory android firmware and dont apply dmcu.cfg, instead manually set your factory options.
[MTCD Android Head Units General] michLQ:
Has someone tested to flash the HA 2.52 MCU on a PX3 HU with an LM 2.41 MCU?
[MTCD Android Head Units General] Knightbird68:
That's great, but where did you get them from? I can't find any download links??
[MTCD Android Head Units General] screwey:
The HA MCU code is here:

https://xdaforums.com/android-auto/...asaita-mcu-updates-rockchip-px5-octa-t3575155
[MTCD Android Head Units General] Knightbird68:
Thank you!!!:good::good::good::good: