yashsingh1/xdaforums huggingface dataset:
[MTCD Android Head Units General] makes2068@gmail.com:
Back on LM 2.44 and it seems to work. Very strange.

Conclusion:

There must be a setting resposible for the function in factory settings.

MCU´s are not really cross compatible.

To good to be true: not working.

Sleep only for about 10 seconds. Longer ignition off time, and radio boots from deep.
[MTCD Android Head Units General] ozzyboy:
hi, it works in px3?
[MTCD Android Head Units General] marchnz:
Have you considered you have a problem which you havent yet identified, not excluding proper configuration of factory settings? I cant follow the changes you have made, steps or if/where you have followed the advice of others to conclude it is a mcu problem. Your issue seems to indicate configuration of factory settings, to me anyway.

---------- Post added at 08:17 AM ---------- Previous post was at 08:16 AM ----------

After you tried it, let us know!
[MTCD Android Head Units General] makes2068:
It looks like there is a problem with px5 board and my erisin 3015 with included can bus.

With px3 the delay of two hours works.

The px5 board handles the power management in a different way.

Actually I use kld 2.57 mcu. All settings done New. No restore from other mcu.

Since now, no hint of a specific setting in the factory settings.

Send from D6603 with Tapatalk
[MTCD Android Head Units General] ozzyboy:
ok, i'll try to update with 2.55 mcu and dupdate.img of 5.1.1
[MTCD Android Head Units General] meuhmeuh51:
I did not find the link for duptade.img.

I found that to update the mcu. You have a link for rom?
[MTCD Android Head Units General] nadkp:
If you mean the ACC Option to set the deep sleep after a chosen time, it is not in the factory settings. It is in the extra settings
[MTCD Android Head Units General] makes2068:
No, the settings did not do anything. So I ask for a one in factory settings.

Send from D6603 with Tapatalk
[MTCD Android Head Units General] nadkp:
When I remember correctly, than there is no such setting in the factory settings. But I do know an option which has an "on/off" switch for a shutdown, but I can't remember where to find it.

Later today I can take a look, but now I am at work, so you have to be patient or someone else can help in the meantime
[MTCD Android Head Units General] makes2068@gmail.com:
Thank you for your help.

Like i wrote: with PX3 board the shutdown delay was working.

Now with PX5 and a different power handling it doesn´t .

Wrong wiring is impossible cause original plug from car is attached to the unit. The unit itself got a two way can bus integrated.

Yesterday i stopped with the car at the supermarket to by bread. Took only two minutes. Than further to pick up my daughter. After that I drove home.

The whole time no music cause radio always boots up... ;-(
[MTCD Android Head Units General] ozzyboy:
MCU update for MX

MX 2.51.1 for px3 with android 5.1.1
[MTCD Android Head Units General] markmorto:
Thanks for posting this. I have a XRC 2.41b MCU in my Hizpo Android 7.1 head unit. Do you know if this update fixes Bluetooth connectivity to allow passwords to connect to Bluetooth devices?
[MTCD Android Head Units General] marchnz:
Yet you've posted on another thread a question related to wiring! The problem isn't the MCU. Go back to stock firmware and properly confirm wiring. Suggest taking to a professional auto electrician to validate wiring is correct - specifically the ACC wire - if you're not able to make these checks yourself.
[MTCD Android Head Units General] makes2068@gmail.com:
Try to deconnect the pin16 cable.

But... with PX3 everything worked! So wiring should be o.k.

What are the differences in power handling between PX3 and PX5 board?
[MTCD Android Head Units General] ikerg:
By pass the canbus and check if delay works without can-bus.

Enviado desde mi D6603 mediante Tapatalk
[MTCD Android Head Units General] makes2068@gmail.com:
Can do this with a dip switch on the back of the unit.

Unit didn´ t start with ignition anymore. Only switch on and off manually. But it seems to go into autosleep.

But tht is not a solution to me ;-(

...and did not test long enough what happens to battery.
[MTCD Android Head Units General] makes2068:
Changed ignition and acc. Used only one cable in both pin places.

Nothing.

It looks like the setting autosleep wasn't transfered from the rom to the unit.

Changed and tested several mcu.

Now I got the one for my LM unit. LM 2.52.

No auto sleep.

Send from D6603 with Tapatalk
[MTCD Android Head Units General] Solovei2:
Latest PX5 MCU for GS?
[MTCD Android Head Units General] nadkp:
I doublechecked my settings. Just to be sure: my radio goes off when I pull the key and starts immediately after I put the key back in and turn it without starting the car.

My MCU: MTCD_GS_V2.51_1

My factory settings -> other -> "default power status" = OFF

My Extra-settings: ACC delay = auto sleep

There are no more settings for the auto sleep function.

When I change the extra settings ACC delay to 30 seconds or 5 minutes or some other option, my radio needs about 20 seconds to start and I can see my car logo in the meantime

If those settings don't work for your head unit, it might be damaged

---------- Post added at 08:11 PM ---------- Previous post was at 08:10 PM ----------

Should be 2.51 like my radio has
[MTCD Android Head Units General] makes2068:
If set default power status to off, unit did not start.

Power status is off then...

Tested this and I have to flash a different mcu from recovery to reanimate. Maybe a combination of this setting and the wiring.

Why should unit be damaged? Everything else works great.

Are you on stock Rom?

Send from D6603 with Tapatalk
[MTCD Android Head Units General] makes2068@gmail.com:
Got the issue!

I depends on the can bus. Set can bus to "none" in factory settings and auto sleep works. Only the delay from the rom settings did not work.

And i got no can bus information ;-(

Now i have to find out how to handle both and save batteries life ;)
[MTCD Android Head Units General] marchnz:
Hoorah! See really wasnt the MCU issue ;)

See mcu cross compatability thread - attach a pic of the sleep settings you have.
[MTCD Android Head Units General] makes2068@gmail.com:
At the moment i´am on LM_2.52.

No changes if i use MX_2.51 or HA_2.56. Tested both. You mean there are other mcu´s offering other can bus settings? Car is an VW Touran 2007

Can bus is integrated in the unit so an update isn´t possible. I think i had to change the behaviour there ;-(

This unit will fit the following car model:

VW PASSAT CC (2008 to 2013), PASSAT (2005 to 2013), Golf 5 (09/2003 to 2013), Golf 6 (08/2008 to 2013),

Tiguan (2007 to 2013), Touran (2003 to 2013), EOS (2006 to 2013), Jetta (2005 to 2013),

Caddy (2003 to 2013), Sharan (2010 to 2013), Amarok (2010 to 2013), Scirocco (2008 to 2013),

Polo V 6R (2009 to 2013), Multivan T5 (2010 to 2013), New Bettle 2 (2011 to 2013).

SEAT Altea (From 05/2004), Leon (From 09/2005), Toledo (From 12/2004), Altea XL (From 04/2007)

Note: This unit has front panel size 220mm(Top width)*130mm(High)*210mm(Bottom width),

please check your dashboard size before bid to avoid mistake!

- 8 Inch super wide Screen, our unique design, the most VW car dvd player just has 7" screen size

- Built-in Dual Channel CanBus Decoder incl. support display Car OPS/Radar, A/C Control and Backing Track Line

Sleep settings?: Auto sleep

But the settings there did not work. In any case.

Can bus = none = always auto sleep

Can bus = 01 VW = always boot up

Tested other can bus settings without success.
[MTCD Android Head Units General] nadkp:
Yes, I am still on stock rom, since Malaysks rom isn't exactly working for some users
[MTCD Android Head Units General] makes2068@gmail.com:
Malaysk V2 working great without issues to me.

Only my autosleep problem.

But there could be a reason. Found this:

...I read on a post that these units reboot from cold when an app draws more energy than expected during sleep

Using a wlan hotspot at usb port. (loading while in standby) So could this be the reason?
[MTCD Android Head Units General] nadkp:
I guess not, because I am using a wifi hotspot as well. It's connected to the usb port in my glove compartment and has a lte sim card in it. Works like a charm, but needs 5-10 seconds after waking up from stand by to completely do its work. It is a ZTE MF79 Wifi Hotspot USB Stick
[MTCD Android Head Units General] makes2068@gmail.com:
You´re right. Tested and still not working.

I think my internal can bus isn´t compatible with the malaysk rom. Or with any rom!?

Settings there where not transferred.

Next option is to test a stock rom. But this took a long time... ;-(
[MTCD Android Head Units General] ikerg:
Can you take a photo to the canbus information that it is printed into the canbus box?

Enviado desde mi D6603 mediante Tapatalk
[MTCD Android Head Units General] makes2068@gmail.com:
Got no canbus box ;) See bold text in my posting

...attached photo of units back.
[MTCD Android Head Units General] makes2068@gmail.com:
Installed an old mcu 2.30. Sleep delay was completely removed in extra settings. Not only the auto sleep function. Strange.
[MTCD Android Head Units General] ikerg:
Ia the first time is see that can-bus is integrated....

Enviado desde mi D6603 mediante Tapatalk
[MTCD Android Head Units General] makes2068:
There are a lot of units out...

Send from D6603 with Tapatalk
[MTCD Android Head Units General] stanley 00:
I was not aware of a bluetooth issue. I can connect my phone. the head unit gives a code like ( 0000 or 1234) then you enter it in your phone and it's done.

For other device like Bluetooth ODBII, i dont know.
[MTCD Android Head Units General] makes2068:
Could someone offer me a mcu from a stock erisin unit with stock px5 board?

My last idea to get auto sleep working.

Thanks a lot!

Send from D6603 with Tapatalk
[MTCD Android Head Units General] typos1:
Look on the fileservers in my signature, you cant get an MCU off of a unit.
[MTCD Android Head Units General] makes2068:
Thanks, but nothing there that would help.

It has to be a LM mcu with auto sleep.

Got one 2.52 but did not work cause it is not from a px5 unit.

Send from D6603 with Tapatalk
[MTCD Android Head Units General] typos1:
MCUs are the same for ALL MTCD units !!
[MTCD Android Head Units General] makes2068:
I know but they are all not working. So my last hope was a tiny difference to the or one.

Send from D6603 with Tapatalk
[MTCD Android Head Units General] makes2068@gmail.com:
Could someone xplain the version n umbers behind the mcu files? These are available in the factory settings "version"

2.52_01

2.52_02

Some are up to 5 versions inside one mcu
[MTCD Android Head Units General] typos1:
It may refer to the "customer version" in factory settings or it may be different versions of the same MCU - on MTCB/C units there are "KLD", "KLD2", "KLD6" etc which denote different MCU versions some of which are cross compatible between manufacturer versions (KLD in this case - for instance KLD can often be flashed to KLD6). I ve not read anything about this re MCD units.
[MTCD Android Head Units General] BENI2345:
I have auto-sleep with MCU 2.47, if you device is Erisin RK3188 KGL.
[MTCD Android Head Units General] makes2068@gmail.com:
Mine is an erisin LM.

Have you got the witson board too? Autosleep only works with PX5 board and thats an RK3368 not an RK3188.

You are still on PX3? (RK3188) so can´t have autosleep!?

---------- Post added at 12:54 PM ---------- Previous post was at 12:52 PM ----------

Thank you, but my question was: What does the 01 and 02 mean? Where are the differences? What are the doing? Where is a description?

Only find in a mtcb thread some information. But thats not relevant to a mtcd unit ;-(
[MTCD Android Head Units General] typos1:
I was just using MTCB/C units as an example, so cant understand why youd look in the MTCB/C forums.

As I said earlier it MAY be different MCU versions of the same number - a la MTCB/C units - or it MAY relate to the "customer version" in factory settings.

There are no MCU changelogs.

Why not try changing the customer version and seeing what happens ??
[MTCD Android Head Units General] makes2068@gmail.com:
So there is no info about that.

A simple: "I don´t know, too" would be easier to understand for me.

No matter, thank you for your help.
[MTCD Android Head Units General] typos1:
There are 2 possibilities, which I have explained TWICE, try both MCUs and try both with different customer versions, easy, simple.
[MTCD Android Head Units General] makes2068@gmail.com:
You have explained twice? Sorry...

01 = version for/with...???

02 = version for/with...???

Maybe i understand it this way ;)

Try and error isn´t a decsription. "Maybe it will do this or that" also not.
[MTCD Android Head Units General] nadkp:
It seems to be the only way to do a try and error test.

It also seems that you are the only one who has these problems. I've read about guys who "updated" their headunits with the witson board, but I haven't read about anyone who had an auto-sleep problem like you have. Maybe there is no solution, maybe you just have to return it or buy a new head unit
[MTCD Android Head Units General] typos1:
Maybe you think this is a paid support site where all knowledge is known ?

It is not, we have to find things out sometimes by trial and error - there are no MCU changelogs or instructions from the manufacturer, I have given you two possibilities and in the time youve taken to moan at me that my free advice is not good enough, you could have found out for yourself by simply flashing both MCUs and changing the customer version in factory settings to see if it makes a difference.

---------- Post added at 02:35 PM ---------- Previous post was at 02:31 PM ----------

Actually, there is one other guy.

But as you say it is trial and error, another solution is to try an MCU from a different manufacturer's MCU - [MENTION=4974080]marchnz[/MENTION] has opened a thread about this - it is actually possible but it also involves some trial and error, so I dont think [MENTION=6850592]makes2068@gmail.com[/MENTION] would like that either.

EDIT: actually the other guy is [MENTION=2661844]makes2068[/MENTION], so I guess it just one guy with two similarly named accounts, or a massive coincidence !!

Why dont you spend your time finding out what "LM" is an abbreviation of and then contact the manufacturer [MENTION=2661844]makes2068[/MENTION] [MENTION=6850592]makes2068@gmail.com[/MENTION] ?
[MTCD Android Head Units General] makes2068@gmail.com:
It´s me, both times.

Sometime i post via Tapatalk and there is another name, sorry.

O.K. so there is no solution in my case.
[MTCD Android Head Units General] typos1:
Oh god, try what I suggested before you decide that there is no solution.
[MTCD Android Head Units General] makes2068@gmail.com:
What i tried:

Malysk ROM V2 and V3 with mcu´s LM 2.30, LM 2.44, LM 2.52, GS 2.51, HA 2.56, KLD 2.57

Stock ROM HA Dasaita with mcu´s LM 2.30, LM 2.44, LM 2.52, GS 2.51, HA 2.56, KLD 2.57 = no success

Re-wired both VW power cords ACC and B+. Both connected, only one connected, both connected in reversed modus. = no success

De-activated canbus via dip switch on the back of the unit. = works but no infos then and not shure if battery drain

De-activated canbus in factory settings. = sometimes it works like via dip switch, sometimes not.

Enough?

Now i ordered an adapter to attach a external canbus and set internal one via dip switch to "off".

With PX3 board and mcu LM 2.44 everything works as exspected.
[MTCD Android Head Units General] stefcio007:
I think _1 and _2 just relates to what canbus you have chosen in Factory Settings. I have mine set to RAISE 05 for canbus and so it states my MCU with _5 at the end. I don't think it's related to versions at all, but I could be wrong. Can anyone else check?
[MTCD Android Head Units General] typos1:
Lol, I love the way its not even your problem and youve had a go, yet the guy whos problem it is wont bother.

I ll have a go on mine later if I can.

If it was me I would have tried everything before I posted. :)
[MTCD Android Head Units General] makes2068@gmail.com:
Thank you for the first, maybe helpful, post ;)

Canbus 01_VW low/raise

Factory settings 01 and 02. So this could be the switch between 01 = low and 02 = raise.

But: Got the canbus setting 01 vw and installed a KLD mcu that got 5 versions inside. So it not really depends on the canbus settings.

No one can explain the correct "working" together between all parts of software and settings, so...
[MTCD Android Head Units General] typos1:
No. CAN Bus settings to switch between CAN Bus types (Raise, Simple etc) is under CAN Bus settings.

He says he thinks the MCU number on the end might change depending on which CAN Bus type you have set.

Most of the correct working is known, its just this one point.

Again you seem to think this is a paid support forum, people have taken their time to help you for free and you should be grateful even if the help dosent work, that is if you even bothered to try what is suggested.

You can always trace LM and ask them . . . you can legitimately moan at them if youre not happy as they made your unit.
[MTCD Android Head Units General] typos1:
Just for general info :

Many later MCUs are also posted in this RK3368/PX5 thread :

https://xdaforums.com/android-auto/...opment/mtcd-px5-headunits-repository-t3619906

This is the MCU post :

https://xdaforums.com/showpost.php?p=72622240&postcount=2

But there may be MCUs is other posts too.

As MTCD MCUs work on the motherboard whatever processor you have, RK3188/PX3 1 or 2Gb RAM, RK3368/PX5 or Intel Sofia, people with RK3188/PX3s and Intel Sofias might not look there, so check it out for newer MCUs.
[MTCD Android Head Units General] marchnz:
Get this: there is no information, only what people chose to share here. Try and contribute by posting your findings.
[MTCD Android Head Units General] makes2068@gmail.com:
Found an mx mcu 2.55 in the signature from a user here in this post ;)

Will try this cause the px5 board is from witson ;)
[MTCD Android Head Units General] typos1:
You mean the fileservers in my signature ?

ALL RK3368/PX5 boards are made by HCT, who you bought it from is not relevant, Witson is a seller, they dont make the SoM board, or the motherboard and the MCU is on the motherboard and is totally separate from the MCU.
[MTCD Android Head Units General] makes2068@gmail.com:
So the mcu should be the one fitting the motherboard?

I know that there are no or only very small differences between the mcu´s. But it´s my only hope of fixing my issue ;)

Why are there a lot of mcu´s around if only one (the hct one) is needed?
[MTCD Android Head Units General] typos1:
Again you are not reading correctly - the SoMs are the same and made by HCT, the MCU software is different and its the MCU software that you are looking for - "GS 2.56" for example is MCU software.
[MTCD Android Head Units General] makes2068@gmail.com:
Sorry, my fault.

No i´am looking for "The thing" that controlls the SoM.

Everything works, only after replacing board from PX3 to PX5.

So the reason for my problem must be the different power management of these both boards. My only solution possibilities are the mcu´s ... :(
[MTCD Android Head Units General] typos1:
Yes, we know all this.
[MTCD Android Head Units General] ikerg:
I think that your only solution ia to select the correct can-bus .

What canbus option did you have when you were on rk3188? Is the same option selected on px5?

Enviado desde mi D6603 mediante Tapatalk
[MTCD Android Head Units General] makes2068@gmail.com:
Yes: Can bus setting 01 VW low/raise

It´s the only setting that works with "door open" and "car status".

Tried others, but not all...
[MTCD Android Head Units General] typos1:
Well the manufacturer of your built in CAN Bus decoder must be Raise then.
[MTCD Android Head Units General] makes2068@gmail.com:
Really? I thought only "low"?

Tested other low variant. Now i can test other raise ones... ;)

VWGolf7 raise did not work.
[MTCD Android Head Units General] typos1:
Dunno about that, maybe "low" is a CAN Bus manufacturer that uses the same protocol as Raise, but "CAN high" and "CAN low" are terms used to donate the input and output lines on the CAN Bus network so I always assumed that "low" was referring to that.
[MTCD Android Head Units General] GREATXDADEV:
Ok....but in the first page of post there is only 1.92! Is possible there are 2 kind of kgl?

Thanks
[MTCD Android Head Units General] ZeroZorro:
I have a related question...is there a way (or app) that will provide this information cause a thorough Google search didn't help me finding the manufacturer/built of my CAN Bus Decoder...

(Peugeot Expert Van 2014).

I am hoping to get auto switch display to reverse camera image working.... and if possible also (beep) warning sounds when car is in Reverse...
[MTCD Android Head Units General] typos1:
Try the fileservers in my signature.

I d just try all the Peugeot CAN Bus settings then.
[MTCD Android Head Units General] ZeroZorro:
Yup, but all i could find is number 50 at the Canbus settings in Factory Settings (which is mispelled but i think they mean peugeot). I also read somewhere that nr.51 could work but nope for me.

So far no luck so i hoped someone had experience with this combination car/px5...
[MTCD Android Head Units General] typos1:
Have you also tried Fiat CAN Bus settings ?

Also try Citroen, PSA and Dongfeng ones.
[MTCD Android Head Units General] ZeroZorro:
Thanks, no, i will do that and report back!
[MTCD Android Head Units General] gbarrenalesslan:
MCU CHS

Hi I have this MCU and I flash with other version, now Version Unmatch.

where can I localize this MCU:

I need: MTCD_CHS_V2.51_1

I have brick my radio.

Thanks
[MTCD Android Head Units General] typos1:
Read the Cross Compatible MCU thread.
[MTCD Android Head Units General] gbarrenalesslan:
yes I read but I dont know how is the correct one.

I have try a lot of MCUs and all say Invalid match -01 in red
[MTCD Android Head Units General] pb40:
hello,

do you want update MX on 20/10/2016 ?
[MTCD Android Head Units General] meuhmeuh51:
@ pb40 thank you for your reply. if you have a link for the update, I will.
[MTCD Android Head Units General] Musicman1973:
Is there a new DMCU for the LM Unit available ?
[MTCD Android Head Units General] pb40:
A link for MX https:...//1fichier.com/?ax3mwwu1xw

and for dmcu https:...//1fichier.com/?oxr1dhzc1s (remove the ... and mx before update:) )

I dont' try this update because I have a KD.

---------- Post added at 01:08 PM ---------- Previous post was at 12:46 PM ----------

The last is V1.82b-1 for me .
[MTCD Android Head Units General] Octochris:
New KGL is available

Hello,

a new KGL V1.92a_4 is available, see post http://xdaforums.com/showpost.php?p=69487562&postcount=527

I have it installed on my headunit, everything is ok.
[MTCD Android Head Units General] meuhmeuh51:
[MENTION=7499099]pb40[/MENTION]

Thanks for links.

I try to install them, but after rebooting, it still registers the same version (mx 1.71-1). I do not understand anything.

I have a version wilson MX 1.71-1 though.

If someone knows why the version of the mcu does not change after installation of the update, I am taker.

thank you
[MTCD Android Head Units General] fifthelement:
copy the update file into internal memory by a file manager and then try to update. my update was failing from a USB drive.
[MTCD Android Head Units General] trvbone:
anything for Xtrons guys?
[MTCD Android Head Units General] DudeInMyrtleBeach:
I have no idea what changes there were. I simply emailed them with a question about my HU (10.2 MTCD) and they emailed me back and said 'try this fix' lol.

Latest Hot Audio ( HA ) version 1.93 :

MCU version：

MTCD_HA_V1.93_1

Oct 17 2016 15:32:59

Android version：

5.1.1

Kernel version：

3.0.101+

chun@hctr930 #188

Thu Oct 20 17:06:17 CST 2016

Build number：

rk3188-userdebug 20102016.20:05:12

Link:

https://mega.nz/#!zh5mBK5I!zD3Dgc0NR6t5_XQqXq965HO_aMKOqM3OIlM3JUXqvWM
[MTCD Android Head Units General] masri1987:
GS?
[MTCD Android Head Units General] Sehmee:
Xtrons is GS. I am also looking for a newer version than 1.93
[MTCD Android Head Units General] masri1987:
I think that's the latest, I haven't seen ANY MCU later than 1.93 yet