yashsingh1/xdaforums huggingface dataset:
[MTCD Android Head Units General] makes2068:
Maybe in the factory settings?

This mode depends on the mcu I think

Send from D6603 with Tapatalk
[MTCD Android Head Units General] OnkelDeffe:
I did not find any shutdown time value neither in the normal settings nor in the factory settings?!

Unfortunately I have a very seldom used MCU (MTCD_HZC_V1_75_1) and I can't find any information about it ...

EDIT: I've got a problem: on android 5 / px3 under "Settings" - "Car" - "Extra Settings" I could select shutdown timer after ACC off (from 30 seconds up to 2 hours). Now under android 6 / px5 this entry does not exist any more! So it is no MCU problem I think?! Any ideas?
[MTCD Android Head Units General] makes2068:
I think the mcu is to old for that. Try to find a newer one.

Send from D6603 with Tapatalk
[MTCD Android Head Units General] marchnz:
refer / read this thread.
[MTCD Android Head Units General] OnkelDeffe:
Thank you for this link - very interesting!
[MTCD Android Head Units General] internest:
What was the problem that makes you to drill the hole for the third screw?

I have installed mine today and it has been working for 20 minutes, then the radio shutted down unexpectedly. Do you have the same problem?

Thanks in advance.
[MTCD Android Head Units General] OnkelDeffe:
The original PX3 board was fitted with 3 screws on the mainboard and so there are 3 placeholders on the mainboard for them. At the position of the 3d (middle) screw on the new PX5 board is a screw at the bottom for the cooler board. This screw will press against the 3d placeholder and so the contacts of the px5 board won't fit correctly. In my case the radio did'nt started up at all. I removed this 3d screw at the bottom, but this didn't help. So I removed the cooler plate and drilled a hole at this middle position so that I can fix the board with the original screw in the middle position.

So yes, I recommend to remove the 3d cooler board screw and drill a hole at this position so that you can fix the board near the connectors to have good contact at all.

Greetings

Detlev
[MTCD Android Head Units General] internest:
I have found the problem. My heat sink is making some type of contact... If I remove it, it works, but when it gets hot the unit stops. I'll try to use a chipset heat sink instead of original.

Thanks all!
[MTCD Android Head Units General] Dantical:
in case anyone wants to know : get 3x m2,5x6mm bolts ;) they´ll fit with the cooling plate!!

the original rk3188 screws are m2,5x3,5 :)

just take the heatshield of and drill the hole for the middle screw ( mine had no middle screw attached ) up to 2,5 mm and wiggle a bit so it is a bit wider then 2,5mm, ( be care full, to drill upside down from underneath to the top, so no metal gets on the heatsink or clean all and put new heatsink on ) then put the headshield on with 2 screws, and put the board in. 3x m2,5x6 screws and your done! wohoooo

this way it still uses 3 bolts to attach right and sits flat!
[MTCD Android Head Units General] internest:
It was not the problem. Sometimes boot, sometimes not boot...

My radio is an XTRONS (GS). Is there anyone with the same radio?

thanks in advance.
[MTCD Android Head Units General] typos1:
Yes, EVERYONE in the forum ! - theyre all pretty much the same, with some very minor exceptions (ie ones with no buttons, maybe a slightly different radio tuner), so what applies to one pretty much applies to them all (most of the time).

It sounds like a loose connection, have checked them all ?
[MTCD Android Head Units General] internest:
A lot of times. I can disassemble it with my eyes closed.

when it boots, the screen turns black passed few minutes and music stops. This was the reason that makes me to thought that it was a heat problem.

when it doesn't boots, the screen remains in black. I can't see the "audi logo".

:crying:

thanks!
[MTCD Android Head Units General] randeez:
I've had mine do it only once, thought it was heat issue though as well. Black screen with frequent flash I could hear it was working, button pushing feedback noise. My unit has a reset on the front, hit that and haven't seen it since
[MTCD Android Head Units General] karadas87:
Mtcc kld6 px3 I want to install my multimedia device with 1 gb ram, px5 card with 2 gb ram. where can I find
[MTCD Android Head Units General] typos1:
Not possible, the upgrade is only for MTCD units.

We are working on trying to make N work on MTCB/C RK3188/PX3 devices, there are also rumours of a RK3188/PX3 SoM with 2Gb RAM and N being available at some point.
[MTCD Android Head Units General] makes2068@gmail.com:
Updated my PX3 Erisin 3015 with this board. No problem and easy doing.

Main reason was the auto-sleep function, so unit came up fast ever time.

This will not work ;-( Updated mcu to 2.52 without succes.

What can i do?
[MTCD Android Head Units General] Nomader0:
Update your rom as well to malaysks v.2 or v.3
[MTCD Android Head Units General] makes2068@gmail.com:
Sorry, i forgot: Malaysk V3 ==> not working.

Maybe it depends on the car or CAN bus settings? (VW Touran 2007)

EDIT: With the witson board my unit is now MX instead of LM?
[MTCD Android Head Units General] internest:
Hi all,

Not all mtcd units are compatible with the upgrade. Be carefull. I have to go back to my old px3-1gb.

I have seen that there is another upgrade to px3 with 2gb RAM and Android 7.1.1 and when I ask to my seller, he said that is not compatible with my mtcd unit.

My unit is this: pf75aa3a xtrons 5.1.1 px3 1gb

Enviado desde mi ONE A2003 mediante Tapatalk
[MTCD Android Head Units General] typos1:
What MCU is yours ? Why did you have to go back ?
[MTCD Android Head Units General] internest:
Here you have the details.

I had to go back because PX5 uphrade doesn't works. It started first time, I setted up my google account and install some standard software, and whe I go to try GPS performance, the units shutsdown unexpectedly and remains off. It starts 2 or 3 times after that, but always past some minutes the unit stops.

I thougt that was heat problems, I install a chipset heatsink, but it doesn't works.

Enviado desde mi ONE A2003 mediante Tapatalk
[MTCD Android Head Units General] typos1:
Did you update your MCU ? It looks like quite an old one.

This sounds like a problem with the SoM, it doesnt mean that the PX5 isnt compatible with all MTCD units - ALL MTCD units can take RK3188/PX3, RK3368/PX5 and Intel Sofia SoMs, because the motherboard is the same for all of them.

I also noticed that in a yourube video of your unit, it has a Klyde back plate (clearly says "K" oon it) but a GS MCU, does yours have a "K" on the back ?
[MTCD Android Head Units General] internest:
Can you post the video to see what do you mean about "k"?

I update the mcu to 2.40 (I thought), but nothing happens.

Thanks in advance.

Enviado desde mi ONE A2003 mediante Tapatalk
[MTCD Android Head Units General] typos1:
A later MCU would be better but as the GPS is on the SoM on MTCD units, so its most likely a problem with your new SoM I think.

Have you checked your antenna connection at the SoM ?

This is the video :

https://www.youtube.com/watch?v=P65ZyO3J0QE
[MTCD Android Head Units General] gangs73r:
Hello, i just received the px5 board, and everything works flawless, no lag what o ever bether that i`ve imagined. My only issues are the power on/off when shutdown the car that I understand that that is how it operates and is nothing that can be done about it and the other thing is that it seems that i don`t have any application for vehicle info, the one that shows battery voltage, fuel, I just can`t find it, is it something that i can do to install or something ?

thank you in advance

I updated the mcu to 2.43 from 1.52
[MTCD Android Head Units General] internest:
My unit is exactly the same with the K in the back.

Enviado desde mi ONE A2003 mediante Tapatalk
[MTCD Android Head Units General] typos1:
Right, well that is weird - you have a Klyde unit (hence the K and the Klyde back - no other manufacturer has this style back plate) but a GS MCU, your MCU should be KLD as well.

I would flash a KLD MCU on it, as its clearly a Klyde unit but check this thread as well just in case there is a problem, I cant see there being but you never know :

https://xdaforums.com/android-auto/.../mtcd-verified-cross-compatible-mcus-t3624724
[MTCD Android Head Units General] internest:
I am looking for a kld mcu and I can't find for mtcd. Kld is only mtcc or mtcb?

Enviado desde mi ONE A2003 mediante Tapatalk
[MTCD Android Head Units General] typos1:
No, Klyde is MTCB, MTCC (the only MTCC MCUs are KLD) and MTCD, I found the latest KLD MTCD MCU (2,54) in this thread a few pages back.

The latest KLD MTCD MCU is here :

https://onedrive.live.com/?authkey=...59&parId=3E65BF84DE43F2EE!11758&action=locate

It says "PX5 MCU" ignore this - it can be used on ANY KLD MTCD unit, RK3188/PX3, RK3368/PX5 or Intel Sofia.
[MTCD Android Head Units General] internest:
Thank you very much! I'll try it today. :)
[MTCD Android Head Units General] makes2068@gmail.com:
Who can confirm that auto sleep is working? Updated old PX3 unit with PX5 board!

I think this did not work when unit isn´t PX5 out of the box.

Is it possible to work only with newer Can bus as my simple one from a Touran 2007?
[MTCD Android Head Units General] Maly_P_kow:
Where can I buy the RK3368 / PX5?
[MTCD Android Head Units General] typos1:
The link has been posted umpteen times in this thread, try the first post and search from there . . .
[MTCD Android Head Units General] makes2068:
Guys I give up.

No auto sleep. No way.

At start I have to be patient. But then, the upgrade is worth it's price.

Fast, responsable, functional.

Thanks to all for supporting me with my problem.

Send from D6603 with Tapatalk
[MTCD Android Head Units General] Nomader0:
Mate this is very strange.. I have nothing to propose..

But though I have autosleep, I have it set to 30 seconds anyway, as I prefer my unit to clean restart every time..
[MTCD Android Head Units General] makes2068:
Thanks for your nice words.

My unit needs between 35 and 65 seconds to boot. Don't know why?

Maybe I downgrade to V2...

Send from D6603 with Tapatalk
[MTCD Android Head Units General] typos1:
I think if you just have some patience that some software update will come along and fix it at some point, I suspect an interaction with the MCU and Android on some units (maybe the ones where the manufacturer havent released octacore version yet ?) is causing the problem, but c'mon, its not THAT bad a problem really, is it ? I mean its not like its taking 5 mins to boot or something. :)
[MTCD Android Head Units General] makes2068:
You are right.

Tested a bit without knowing what I am doing.

There is a dip switch on the units back.

Acc change.. Or similar.

With this, ignition power is off and unit has to be switched on by power button.

And the unit stays in sleep and came up fast.

Don't know if I should use this mode or my battery get drained.

Send from D6603 with Tapatalk
[MTCD Android Head Units General] typos1:
I would give it a try and see. The dip switch is on the unit or the CAN Bus decoder ?
[MTCD Android Head Units General] makes2068:
Both, it´s a special VW unit. CanBus decoder is integrated inside the unit.
[MTCD Android Head Units General] typos1:
Oh, not come across those before, any pics ?
[MTCD Android Head Units General] makes2068:
Just search on eBay or the Web for Erisin 3015.

The newer one is called 5015.

Send from D6603 with Tapatalk
[MTCD Android Head Units General] Apostrofix:
I am sorry but I cannot find the link. The link from the first post seems to be dead. Any ideas what I should search for?
[MTCD Android Head Units General] typos1:
Dunno, I ve seen the links and opened them but I did not memorise what pages they were on so in order to find it I would have to go through every page of this thread for you, I m not gonna do that so your ll have to. :)
[MTCD Android Head Units General] colostro:
Here It Is the link: WITSON Octa-Core 2 GB RAM 32 GB Flash Coreboard Per Android DVD (Android 5.1 A5XXX eseguire l'aggiornamento a Android 6.0 B5XXX direttamente)

http://s.aliexpress.com/2YJBvyIn

Inviato dal mio Redmi Note 3 utilizzando Tapatalk
[MTCD Android Head Units General] stefcio007:
Check my signature, it links to WITSON store and from there the first product is the PX5 board. My link should always work even if the product listing changes.
[MTCD Android Head Units General] ptclabs:
jy 10.1 with 8 cores lines and color problems

I know this has already been discussed but this units connectors does not seem to be long enough to make proper contact with this board. I already lowered the three stakes to make it so the board is level, but while that fixed the lines, I still get a redish tint sometimes when I first start the unit as the connection is bad. I may sand down the new boards connector a little to see if that makes them go in far enough.
[MTCD Android Head Units General] typos1:
Hey, [MENTION=6005745]ptclabs[/MENTION], was it you that a few years back tried to get the screen lock function working on one of these units ?
[MTCD Android Head Units General] makes2068@gmail.com:
Another question for my problem, unit not auto sleeping ;)

Picture from my quadlock wire vw: See plug 15 an 16

Picture from Radio: See plug 14 an 16

Could this be my problem? How to release the cable and pin to another Number?

Do i have to change the both cables?
[MTCD Android Head Units General] d-panja3:
I just upgraded my joying unit with the new board. Works perfectly! I have installed HA 2.56 MCU and 20170706 HA system.
[MTCD Android Head Units General] internest:
It could be my problem too. The board sometimes works and sometimes not. In some cases I had faulty image. How do you try to fix it? I am thinking about install a connector between the MCU and the board to make sure that all pins are connected.

like that:

http://www.ebay.es/itm/like/251528429986?chn=ps

I had this type of connectors, but the holes are too much separate to connect directly. I'll try to use a protoboard or something to make sure that it works. Now... I need to find some time to do it.
[MTCD Android Head Units General] martrobgray:
The pins are quite stiff to push the core board on to. I experienced initial problems at first, with fuzzy resolution and colour issues (blacks were green!). One day the unit just wouldn't turn on and had been working perfectly. After inspection the core board wasn't contacting the pins properly. I had to apply more pressure than I was comfortable with but it did move down on to the pins. I haven't experienced any problems since.

Just make sure there are no bent pins and you get the connector aligned correctly, apply pressure progressively making sure its even. It can be quite tight!
[MTCD Android Head Units General] ptclabs:
I have found more problems with the 10.1 and this upgrade. The right 1.5cm of the touch screen does not work either. No matter what i tried I cannot get rid of the lines sometimes. It goes away after about 2 minutes.
[MTCD Android Head Units General] makes2068:
On stock HA Rom at the moment to test.

No auto sleep!!

I give up...
[MTCD Android Head Units General] makes2068:
It looks like that the can bus sees that the radio took a few power and cut the power.

Ignition power wire cut cause not necessary if can bus is in use. Behaviour stays equal.

It's driving me nuts.

With px3 everything works.

Send from D6603 with Tapatalk
[MTCD Android Head Units General] typos1:
Put up with it until a software update fixes it ?

Or sell the RK3368/PX5 SoM and buy an RK3188/PX3 2Gb Nougat SoM ?
[MTCD Android Head Units General] OnkelDeffe:
You said that your unit has an built-in can bus controller - and that auto sleep works, when you disable it. So why not trying an external can bus adaptor? If this external one tries to cut power too you could make a direct connection of battery power and ignition power without using the can bus and everything should work ... or you ask the maker of your hardware board (which MCU was it originally?) for a mcu firmware update (is your unit (or a similar one) with px5 board available?)
[MTCD Android Head Units General] makes2068:
That's not that easy cause there are no adapter from quad lock to quad lock with an external can bus between.

Got one with quad lock and external can bus, but with Iso connectors. And they did not fit the quad lock input at head unit.

Send from D6603 with Tapatalk

---------- Post added at 12:18 PM ---------- Previous post was at 12:15 PM ----------

Software has nothing to do with the problem.

Canbus always cut power whatever I connect to.

Send from D6603 with Tapatalk
[MTCD Android Head Units General] typos1:
Ok, reckon its the CAN Bus decoder, but if it didnt hppane with the RK3188/PX3 SoM, I thought it was somethign to do with the MM ROM on the RK3368/PX5 SoM.

You easily cut the wires and join them with bullet connectors, or move the wires on the ISO, or even remove the quadlock - it doesnt matter what connector you use, as long as all the right wires are connected.
[MTCD Android Head Units General] makes2068:
You don't understand my problem.

The unit has a quad lock socket.

There are no adapter available to connect to this one.

Only the same as at the unit and this did not fit.

Sorry, but I can't describe better.

Got this. But the Iso connectors in the middle should be a quad lock socket to attach to unit.

Only, very difficult way is to dispatch all pins and connect to a quad lock socket.

Send from D6603 with Tapatalk
[MTCD Android Head Units General] typos1:
I do understand your problem - just cut the wires and remove the quadlock, or move the wires in the quadlock (just insert something thin between the pins to release the tabs remove them), or replace the quadlock with an ISO, it doesnt matter, you could even not have an ISO or a quadlock and just join all the wires with bullet connectors, as long as the right wires get the right wires that all that matters.
[MTCD Android Head Units General] makes2068:
I do not cut the original car quad lock. Sorry.

Will order the quad lock socket and try to change all the pins.

Found this...

Ordered and will try if all fits behind the unit.

Send from D6603 with Tapatalk
[MTCD Android Head Units General] michLQ:
Try this one

http://www.ebay.de/itm/252087021279
[MTCD Android Head Units General] makes2068:
This will not work cause it´s only a extension.
[MTCD Android Head Units General] michLQ:
Okay, I thought you need it to change the connectors.
[MTCD Android Head Units General] hmotwr:
After installation everything seemed to work fine, until I tried to use the WiFi. It isn't working. Doesn't turn on at all. Anybody had this issue?
[MTCD Android Head Units General] typos1:
Have you tried updating the MCU ?
[MTCD Android Head Units General] ptclabs:
yeah it works just add a user and switch user on start with init.d. works fine.

---------- Post added at 09:48 AM ---------- Previous post was at 09:46 AM ----------

i think there is a way to switch which chip it is using in some of the mcus in factory options. i had to change the radio it was using, amp is was using before also.
[MTCD Android Head Units General] typos1:
Right, I thought that you couldnt get it to work back then. I asked because [MENTION=5092263]Hal9k_[/MENTION]'s MTCD ROM has it enabled, he says he just added the original Android code back and it works as on any other Android device.

On MTCB/C units there is a drop down list in factory settings to choose the radio chip, but on MTCD units I ve only ever seen "yes" and "no" options under radio.
[MTCD Android Head Units General] makes2068@gmail.com:
Is this the "version" thing you can choose in some mcu´s via factory settings?
[MTCD Android Head Units General] typos1:
No, I m talking about "radio" in factory settings which on MTCB/C units lists the all radio tuner types, but which just have "yes" or "no" on all the MTCD units I ve seen.
[MTCD Android Head Units General] hmotwr:
Thanks for your reply.

I currently have HXD 2.15_2

Which version would you recommend?

BR
[MTCD Android Head Units General] typos1:
The latest version you can find, but I havent seen any HXD MCUs anywhere, there is [MENTION=4974080]marchnz[/MENTION]'s Cross compatible MCU thread.
[MTCD Android Head Units General] hmotwr:
Thanks.

Will risk trying and report back.
[MTCD Android Head Units General] typos1:
Its best read the entire thread and then try !
[MTCD Android Head Units General] hmotwr:
I've been reading a lot at that thread already. Looks like HA will work. I'll post results in an hour or so.
[MTCD Android Head Units General] hmotwr:
So far so good

I have installed HA_2.56_1 on a MTCD_HXD unit

With RK3188 Android 5.1.1

I'll replace the PX3 Board with the new PX5 and report later.

https://photos.app.goo.gl/sd5jrNpIlqaE54ow1

Edit: The config file didn't work or was not compatible, so I had to edit manually to have the panel keys working.
[MTCD Android Head Units General] typos1:
Cool !
[MTCD Android Head Units General] hmotwr:
Well, it didn't work on wifi. Everything else works but wifi after upgrading to px5 board. I have MCU HA 2.56

Will revert to 2.52 and see

Edit: No success. I've tried several MCU versions and ROMs and no success. Seems like I have to choose between a laggy HU with WiFi or a fast one without WiFi.
[MTCD Android Head Units General] audisean:
i got a bricked (cause unknown - radio off as usual and never woke up)

px3 mtcd so just ordered the px5 - hopefully this will bring it back to life and improve a few things....

might add a cooling fan mod when i get part - done it with other devices - just depends on room for one
[MTCD Android Head Units General] internest:
I have the same problem. My wifi options are not showing mac aaddress, and bluetooth doesn't works too.

Enviado desde mi ONE A2003 mediante Tapatalk
[MTCD Android Head Units General] typos1:
Did you try changing the BT type in factory settings ? Some MCUs only have the option of 2 BT types, but others have a lot more. My KLD MTCD nit has an rtl8723bu combined wifi/BT module, but there is space for the BC6 BT only module (used on MTCB/C units) and lots of options for BT in factory settings, maybe the problem is to do with one of these settings ? - if its on a setting for a combined wifi/BT chip and you have separate BT and wifi chips this could be the problem ?

Why dont you try and unbrick it using SD firmware tool ?
[MTCD Android Head Units General] marchnz:
Exactly. Those upgrading MCU without documenting factory settings are likely to experience issues. To give up so easily and blame "MCU" makes no sense.
[MTCD Android Head Units General] audisean:
I did try SD unbrick - nothing - power is getting to PX3 chip but nothing comes out - 4 USB ports on back of unit are dead too - got a rework station on way (lol even one I already had died too) so maybe i'll try to reflow chip
[MTCD Android Head Units General] makes2068:
Today I tested external can bus Box.

No auto sleep possible. No way. No chance..

I surrender. Unit works perfectly and fast.

Only, ignition off = reboot.

Send from D6603 with Tapatalk
[MTCD Android Head Units General] typos1:
Hmm, I wonder if the MCU is fried, pity you havent got another unit to test the SoM in.
[MTCD Android Head Units General] weevil_:
I think the best way to achieve the same thing is with a soldering iron. Heat up the iron and then just touch the middle placeholder with it for a minute or so. This melts the glue and the placeholder falls right off the mainboard.

Removing it however has not gotten rid the lines from my screen at startup. Grrr. Everything else perfect.

---------- Post added at 03:16 PM ---------- Previous post was at 03:15 PM ----------

How did you lower them???
[MTCD Android Head Units General] ptclabs:
took them out and put them on the flat bed sander. It helped the lines for a day or so but they came back. It is something on this board that is not right. I may try the betty crocker solution if he will not replace it. I still need to come up with some 1gig chips for my wifes car also or upgrade it to a mtcd. Any ideas what temp to bake it at?

I thought about sanding down the connector on the new soc a little to see if it helps, but i think it is just a bad connection on this board somewhere. The old one is too consistent.