yashsingh1/xdaforums huggingface dataset:
[MTCD Android Head Units General] xbenjiiman:
I'm using Malaysk's ROM, with the normal play store.

I don't seem to have the auto power off anymore which was in the "extra settings", it seems it's always in low power mode now with the engine off and I'm worried it's going to drain my battery.

Edit: Nevermind, updated the MCU and all is well.
[MTCD Android Head Units General] semcoinc:
Thanks for the insight typos1.

I will have a 4Gb RAM SoM so I should be in good shape to run Gapps. :good:

Mike
[MTCD Android Head Units General] Phlom:
Hello! Which MCU did you use for the upgrade? What version you had?
[MTCD Android Head Units General] xbenjiiman:
I had KLD 1.92, updated it to 2.44.
[MTCD Android Head Units General] Phlom:
Thank you, mate.
[MTCD Android Head Units General] ruipedro2a:
Hello i bought this head unit for the fiat tipo Egea 2016, and i want to know if upgrade is possible..

bought it from this.. https://www.aliexpress.com/item/7-HD-1024x600-Pure-Android-Autoradio-For-Fiat-Tipo-Egea-2015-2016-2017-DVD-GPS-Navigation/32816025031.html

it has a PX3, 2G or ram and 16ROM

is it possible to upgrade the board to this one ?

https://pt.aliexpress.com/item/WITSON-Octa-Core-2GB-RAM-32GB-Flash-Coreboard-For-Android-DVD-Android-5-1-A5XXX-upgrade/32814725689.html

I know it upgrades to android 6.0 and i have 7.1.2 but that is not the problem, i don't care to go back on android...

as the PX5 is faster than this px3..

[IMG="head unit description"]https://i.imgur.com/oemC81S.jpg[/IMG]

[IMG="description 2"]https://i.imgur.com/1CFOwN3.jpg[/IMG]

[IMG="Description 3"]https://i.imgur.com/9iqORZz.jpg[/IMG]
[MTCD Android Head Units General] typos1:
Yes you can update.

But you may want to try this ROM before you do (its much faster) :

https://xdaforums.com/android-auto/...-2-mtcd-mtce-head-units-t3741583#post75359774
[MTCD Android Head Units General] ruipedro2a:
thank you, i will give this a try.

But anyways i think i will upgrade the board, so what this board also do, is downgrade to the android 6, is that it ?
[MTCD Android Head Units General] bm449:
Salut à tous,

Je suis a la recherche de la rom android et du mcu d'origine svp

https://xdaforums.com/android-auto/mtcd-android-head-units-general/mise-jour-erisin-es3061b-t3741695

-=-=-

mod edit

translation added
[MTCD Android Head Units General] ruipedro2a:
regarde mon post juste au dessus, je crois qu'elle est compatible avec ton poste.
[MTCD Android Head Units General] stefcio007:
I have a DVD drive above my PX3 board. How tall is the PX5 heatsink? It seems like a PX5 board won't fit for me.
[MTCD Android Head Units General] typos1:
It doesnt have a heat sink.
[MTCD Android Head Units General] stefcio007:
What about the metal plate that covers it? If it's only like 1mm thick then that's fine. My PX3 has a piece of card attached on the top to prevent it touching the DVD drive above.
[MTCD Android Head Units General] typos1:
Yes, its no higher than the RK3188/PX3.
[MTCD Android Head Units General] tiago_mix:
hello, I need help, I have the central Eonon 8153

eonon.com/Android-Car-GPS/Vehicle-Specific-GPS/Volkswagen-SEAT-SKODA-8-Inch-Car-Audio-2GB-RAM-Quad-Core-GPS-Navigation-System-Touchscreen.html

she says to be px3 on the rom,

I would like to know if I can trade

aliexpress.com/item/WITSON-Octa-Core-2GB-RAM-32GB-Flash-Coreboard-For-Android-DVD-Android-5-1-A5XXX-upgrade/32814725689.html

When I change this processor, will I have to change the ROM?
[MTCD Android Head Units General] morgish:
Also interested
[MTCD Android Head Units General] skezza:
So yes, this will work on any?
[MTCD Android Head Units General] janusz12561@gmail.com:
Also interested:)
[MTCD Android Head Units General] Sylvan151:
Interested to the group buy of the board. Count me in! ?
[MTCD Android Head Units General] martrobgray:
+1, I'm also interested in the PX5 upgrade.
[MTCD Android Head Units General] barehill:
me too

also interested if price closer to $40
[MTCD Android Head Units General] typos1:
Lol, it aint gonna be that cheap is it.
[MTCD Android Head Units General] PhantomXP:
Is possible for Erisin MTCD KGL RK3188?
[MTCD Android Head Units General] typos1:
Its not an Erisin KGL MTCD its just a KGL MTCD and yes, the thread clearly says MTCD units can be upgraded.
[MTCD Android Head Units General] Skrallex:
Sent them an email and got the following reply this morning:

So, hopefully we can looking at getting these in the next couple of months. Looking at a price point of around $100 USD, postage probably depending on where to.
[MTCD Android Head Units General] dongali:
Do they know we have an entire community devoted to this. I'm very confident this "upgrade" can easily done by anyone who knows how to use a screwdriver and has a MTCD RK3188
[MTCD Android Head Units General] leonkernan:
From some of the posts i've seen here over the last year or two I wouldn't be so confident.
[MTCD Android Head Units General] Kalti94:
100$ would be ok for me, so i can enjoy everyday a more responsive Unit. Where do i have to ask for the board?

Thanks Michael
[MTCD Android Head Units General] Skrallex:
I linked them to this forum, as well as the video HotAudio posted on here on how to swap them. I *think* they realise that a lot of people on HERE could do it without issue, the problem is people buying it without doing all the fact checking, ie. making 100% sure that it's going to be compatible with their unit. Plus the absolute pain it must be to receive hundreds of "will this work with my XYZ headunit" considering how many people don't realise the difference between sellers and manufacturers, etc. I think their best option is going to be to say "Only compatible with HA PX3 head units" and then let anyone in the know determine if it will be compatible with their head unit from another manufacturer.

Not to mention the issue of voiding warranties...
[MTCD Android Head Units General] Sylvan151:
I don't mind spending USD$100+ for this.
[MTCD Android Head Units General] leonkernan:
Put it this way:

If you're Mr HotAudio or Winston are you going to sell someone a part for say $100 and then have to deal with replacements / repairs / warranty issues when they screw it up?

Personally i'd just tell them if they want to upgrade they should buy a new unit.
[MTCD Android Head Units General] Skrallex:
You're not wrong, but I'd say there's likely more money in this for them by selling the modules than what they would make if we all purchased new units. I would imagine the markup on the modules could/would be higher than that on the whole unit. Plus, it's an easier sale, one that likely wouldn't be going through Aliexpress from the sounds of it (which means Ali takes no cut). Also, HA aren't actually sellers, so if they sell it directly then obviously they aren't having the sellers mark it up to make a profit. All this results in a higher margin by allowing us to purchase the modules. Whether or not it will translate to us actually being able to purchase it, only time will tell :)
[MTCD Android Head Units General] typos1:
Yes and some sellers and manufacturers DID sell RK3188 SoMs to MTCB/C owners with RK3066 SoMs, so its likely that some will also sell these while others will refuse to.
[MTCD Android Head Units General] chaps:
I have bought a PX5 upgrade board from Witson, who made my head unit (MCU is MX). Price to the UK is 110 usd plus 6% paypal surcharge, including delivery. Works out at about 94 GBP.

Bob from Witson seemed reluctant, citing the high cost of the part as a reason for me not to purchase. Just waiting to receive it now.
[MTCD Android Head Units General] javiermi:
Hi chaps

Let me know how it goes with the upgrade, I'm also from UK so may be interested if goes well
[MTCD Android Head Units General] typos1:
If you have an MTCD/E unit yo can upgrade your board.

Of course, the SoM will come with a ROM pre-installed.

BTW Eonon are a seller, there are no Eonon units, the letters afet "MTCD" or "MTCE" will tell you what unit you have.
[MTCD Android Head Units General] tiago_mix:
my eonon says EONON_PX3_7.1_KLDMTCD_V2.62

this preinstalled ROM can I swap for a 7.1 px from the correct forum?

thanks
[MTCD Android Head Units General] typos1:
You have a Klyde (KLD) unit.

No, there is only Android 6.0 for RK3368/PX5.
[MTCD Android Head Units General] tiago_mix:
Can the KLD switch to the px5 chip I mentioned?
[MTCD Android Head Units General] typos1:
Yes, ANY MTCD/E unit can be upgraded.
[MTCD Android Head Units General] semcoinc:
Hi All,

I currently have a PX5 configuration per the below pic

Is there a good choice MCU update available for my KBT unit?

And does an MCU update completely erase all the current apps and data in my machine?

Thanks for any help available.

Mike
[MTCD Android Head Units General] typos1:
An MCU wont affect the Android side of things at all.

KBT is quite a rare MCU, try googling it or asking the seller you got your unit form.
[MTCD Android Head Units General] semcoinc:
Thanks Typos1 :good:

That may explain the red circuit board rarity as well.

The seller sent me that V2.42 MCU update when I initially complained about very slow cold boot issues with their 1GB PX3 SoM.

Not much else out there in Google that I can find.

Will keep looking.

Thanks again.

Mike
[MTCD Android Head Units General] typos1:
You could try [MENTION=4974080]marchnz[/MENTION]'s Cross Compatible MCU thread and use one from another manufacturer.
[MTCD Android Head Units General] semcoinc:
Yes, thanks Typos1. I was just headed there shortly after my last post.

Mike
[MTCD Android Head Units General] abagos:
I have upgraded my Eonon KBT unit to the latest HA MCU (2.75). It worked fine and enabled the Auto Sleep function. You may want to record your factory settings to make sure you have them in case they are lost.
[MTCD Android Head Units General] typos1:
Cool did you post your results in the Cross Compatible MCU thread ?
[MTCD Android Head Units General] semcoinc:
Thanks abagos.

That is great info. I will find the HA 2.75 file and put it into my KBT unit. As advised, I will save my factory settings from the .cfg file when I do the flash.

I will now look to find the HA 2.75 MCU.

Update: I have found the HA 2.75 MCU file here listed under MTCE

https://xdaforums.com/android-auto/mtcd-android-head-units-general/dasaita-mcu-updates-rockchip-px5-octa-t3575155

Thanks again abagos.

Mike
[MTCD Android Head Units General] abagos:
Yes I have, all the information is in the thread
[MTCD Android Head Units General] semcoinc:
I just uploaded the HA 2.75 MCU update to my MTCD KBT unit with a Witson PX5 4GB SoM.

I placed my saved .cfg file onto the GPS card with the dmcu.img file and flashed the update. The unit accepted the update and flashed some terminal information on the screen that update was in progress, then the screen went blank and the button lights began flashing and flashing and flashing and flashing.

I let this button light flashing continue for about 10-12 minutes and then I hit my reset button.

The unit booted but here is what I found:

1. all buttons on left and right of head unit are deactivated

2. FM radio completely inactive.

3. most configuration settings are not in place.

I went through the machine settings with pictures of the screens I had made before and changed them to what I had before. I also manually set up the head unit side buttons.

I will now try to flash the .cfg file separately to see if that will bring back my FM reception (yes, I have selected America frequency like in previously working settings)

BT quality appears to be good, without any reported echo. Sound appears improved especially in bass levels and I now have an assured shutdown after 1 hour available in Extra Settings.

Stay tuned.

Mike
[MTCD Android Head Units General] semcoinc:
So, I flashed the unit again with the .cfg file through the MCU updates button (My "Updates" screen in About Device does not open up) and that took me back to a safer place. A previous reboot with my old .cfg file gave a "Version Mismatch" error on the screen and that really freaked me out.

So I did the .cfg through the MCU updates button and got the Version Mismatch eliminated and went back into the button configuration to set up my side buttons.

I properly ejected the GPS card and rebooted. All booted properly (still no Radio reception) and all apps and sound was fine. I have the 1 hour shut down option and then I went back into the Factory Settings screen to set up my front panel buttons which had become inoperative, and exported the .cfg into the Flash as well as onto my now clean GPS card (to save it for later use if needed.

Still no Radio, and I will keep searching for others with this problem and how they solved it.

I still have the 6.0 20180201 .img update but I'm a little leery about doing it until I get this radio thing sorted out.

Anyone else experienced this loss of radio functionality when using the HA 2.75 MCU update?

Quite the journey.......
[MTCD Android Head Units General] abagos:
Did you take pictures of your factory settings? Applying the cfg file didn't work for me either so I applied all settings manually. There is a "Radio On/Off" option in the first page of the settings, maybe that's why your radio's not working. I also re-configured the buttons and screen calibration. I have the pictures I took, let me know if you'd need them.

Alex.
[MTCD Android Head Units General] semcoinc:
Yes, fortunately I had pictures of my factory settings pages and was able to reset everything back to where it was manually. I checked the Radio ON/OFF setting and it is ON.

Mike
[MTCD Android Head Units General] typos1:
Its strange considering that other people got the radio working.

I think we discuss it in the Cross Compatible thread because we are more likely to get help with the problem there than here, particularly from [MENTION=4974080]marchnz[/MENTION] who has the most experience with changing MCUs.
[MTCD Android Head Units General] semcoinc:
That sounds good [MENTION=456516]typos1[/MENTION]

I am considering my next move this morning to restore the radio function. I have a dmcu.img file from the reseller which has a date of: 20170327 for the PX3/Lollipop. This is the MCU that was in use for my PX3 system and when the PX5 SoM was put in and with it the radio worked. So maybe I will roll back to that MCU. Or I am also considering a roll back to HA V2.71 or HA V2.65.

I will choose soon and report back my results.

Mike

See my results here

https://xdaforums.com/showpost.php?p=75518947&postcount=463
[MTCD Android Head Units General] abagos:
Mike, instead of trying to restore your settings with the cfg file, use the factory settings menu to set everything up from scratch by hand. In my case, that solved the "Version Mismatch" error. You will be able to select the BMW logo there too. The shutdown menu should come up also with the 2.41 MCU from KBT, but it lacks the option to Auto Sleep, that's enabled by the HA MCU. Probably you could try an older version, the lowest that enables this option (look in the thread). Again, forget the cfg file and do everything manually in the factory settings.

It's really strange that your radio does not work, the MCU 2.41 for KBT was the last on sent to me by Eonon so I wonder if our motherboards are different.

Alex.
[MTCD Android Head Units General] typos1:
Unfortuantely you cant set up the radio manually other than on or off - you coudl pick the tuner type in MTCB/C units, but not MTCD/E for some reason.

I flashed an MLT unit with an HA MCU, but the radio did not work either - one person in this thread reported that it did work and another that it did not, seems a bit random.

There may be something we could do on the Android side to make it work - [MENTION=4974080]marchnz[/MENTION] has a thread about changing the radio IC and there was some way to see the radio tuner type via Android so may be threes away to change it this way ?
[MTCD Android Head Units General] semcoinc:
Hi Alex,

Thankfully, I was able to bring my radio function back by going back to the KBT V2.42_1 MCU and I had to reload my .cfg file to get my BMW logo back during boot up and all button settings restored. Still no joy on getting a shutdown menu.

The KBT MCU with the PX3 SoM (Android 5.1) has a maximum 2 hour shutdown

BUT, the PX3 system is a [MENTION=5092263]Hal9k_[/MENTION] V1.2 ROM, so maybe the [MENTION=5092263]Hal9k_[/MENTION] ROM is enabling the shutdown menu option. I just realized his framework option is there as well (I was using microG on the 1GB PX3 SoM).

The KBT MCU with the PX5 SoM installed has no shutdown option at all.......

I have to believe that the SoM and/or Android version has some interplay with the shutdown menu, because if it was solely reliant on the MCU, the MCU would deliver a shutdown menu in each SoM. Is my logic flawed?

:confused: :confused:

[MENTION=3590033]Malaysk[/MENTION] is coming out with a V7.0 ROM for the PX5 and that looks really good. I will likely give that a try when he finalizes it. Here is his video:

https://youtu.be/YD31zLeNrXc

Mike
[MTCD Android Head Units General] typos1:
I guess, this is a bug that has affected RK3368/PX5 units, although later MCUs sorted it and some people say different ROMs did too.
[MTCD Android Head Units General] semcoinc:
Hi typos1

More and more I'm thinking the ROM has a key role in whether a shutdown menu exists. Since my PX3 system was a [MENTION=5092263]Hal9k_[/MENTION] V1.2 ROM and had a shutdown menu while inserting the PX5 SoM and it's stock standard 6.0 ROM did not have a shutdown menu.

Mike
[MTCD Android Head Units General] typos1:
Yes, its done by the MCU but I guess there has to be something in the ROM to enable it, the HA PX5 thread has many posts about it.

If I were you I d try a couple of different MCUs, seeing as youre now a bit of an expert at it ! :)
[MTCD Android Head Units General] abagos:
Hi Mike,

Frankly I don't know what exactly can be different. In my case, there was a shutdown menu with both SoMs, PX3 and PX5. The difference was the additional option with the PX5 SoM to "Auto Sleep". This is very useful IMHO because there is zero delay when you start your car, the radio comes up instantly. I tried different ROMs too so I would assume that the stock Android 6 ROM supports it (when enabled by the MCU). Having the option to start instantly, I don't care for the logo any more, when I reboot for whatever reason, the Ford logo I use is shown. I am currently using the SVA ROM.

In my case there were problems when the original configuration of the PX3 SoM was used while the PX5 SoM was installed. I solved that by going through the configuration manually in the factory settings (I had to re-calibrate and assign the buttons again). Having said that, my radio never stopped working.

Probably you could try upgrading your PX5 ROM too to the latest stock ROM.

Alex.
[MTCD Android Head Units General] semcoinc:
Hi Alex,

Yes, I do like the instant start feature, but like others, am concerned about the current drain over long periods of inactivity and the assured shutdown is essential in my view. I use a battery maintainer every night while in my garage but on rare occasions the vehicle is parked in a public place for an extended period of time with no access to electricity and that would be my worry (think airline business trip).

I have an updated HA PX5 6.0 ROM (20180201) for the PX5 but I'm afraid to use it because I don't have

a 6.0 ROM image for the Witson SoM to go back to if it fails. The HA MCU killed my radio and I'm reluctant to go with another HA file.

I'm going to conserve my time and live with the system as is for now. It is working quite well (other than no complete power shutdown option) and when [MENTION=3590033]Malaysk[/MENTION] gets his V7.0 launched for the PX5, I'll give that a go.

Mike
[MTCD Android Head Units General] marchnz:
Fyi - Going from OEM px3 unit upgrading to pX5. Px3 had shutdown menu, pX5 did not. That lead to my upgrading MCU to HA, which resulted in shutdown menu both px3 and pX5 SOM. In both scenarios stock latest android ROM applied.

The MCU is the key, with supporting ROM.

---------- Post added at 07:36 AM ---------- Previous post was at 07:30 AM ----------

Current consumption in sleep is less than. 15mA. From this, it would take months to deplete your car battery.

If your car battery is not holding a charge and you continually need to float charge it, the car battery is bad - replace it.

Please don't perpetuate a non-existent issue, using sleep is fine.

Using a float charge with vehicles that aren't used very often is a good practice as will help to maintain battery life and prevent sulphation.
[MTCD Android Head Units General] semcoinc:
Thanks for your insight [MENTION=4974080]marchnz[/MENTION]

Given your experience, would you have an MCU file to recommend that I try next to get a match to the Witson PX5/6.0 SoM?

On the car battery, thanks for confirming the sleep drain value of <15mA. I was unaware of what the value was for sleep condition before you cited it. I agree, this is a very low value and is now not a worry for me. My battery is in excellent shape, a fairly new AGM technology battery with roughly 90Ah so no worries for me in the battery condition department.

Thanks again for your insight.

Mike
[MTCD Android Head Units General] marchnz:
Hi,

What is your current MCU? Have you read my cross comparability thread?
[MTCD Android Head Units General] semcoinc:
Hi Marchnz,

My current MCU is KBT V2.42_1

Yes, I have read all of your cross compatibility thread and this is where I learned of a success by [MENTION=8603573]abagos[/MENTION] with the HA V2.75 MCU in his KBT unit with PX5 SoM. So, I gave that a go and lost my radio function.

Then I went back to the KBT MCU

Mike
[MTCD Android Head Units General] typos1:
Mike - changing MCU to one from a different manufacturer can be a tricky business,as you know.

But changing ROMs is not, its a totally different kettle of fish - you can flash ANY RK3368/PX5 ROM you like, they are all compatible and if you dont like it you can flash a different one.

Whilst MCUs are the same basic chip on all units, have different software (which may or may not be compatible) and they are all on different motherboards.

But SoMs are identical, so you really dont have to worry about having problems like you did trying another MCU.
[MTCD Android Head Units General] semcoinc:
Thanks typos1. This is a very helpful assurance and will help to reduce my PTSD fears of another function loss disaster like I experienced with the MCU change..

I feel better now about a potential ROM upgrade.

Would your thoughts also apply to the HA PX5 Android 6.0 upgrade dated 20180201?

Please let me know.

Thanks,

Mike
[MTCD Android Head Units General] typos1:
I am still running the ROM that my RK3368/PX5 came with, so I cant commet on that update, all I can say is that you can flash any without fear, apart maybe form Oreo - thats a tricky process at the moment and not for the faint hearted ! (Although I should add that there is always a slight risk when flashing new software on anything).

PS: is the update youre talking about deffo 6 not 8 ?
[MTCD Android Head Units General] semcoinc:
The 6.0 PX5 Android update I have downloaded and might consider upgrading to is here at the beginning of this thread

Dasaita - Latest MCU and Updates for Rockchip PX5 Octa-Core 2G RAM 32GB

https://xdaforums.com/android-auto/mtcd-android-head-units-general/dasaita-mcu-updates-rockchip-px5-octa-t3575155

What do you think of it's viability to my Witson sourced PX5 SoM?

Thanks,

Mike
[MTCD Android Head Units General] typos1:
I see - as I said - ALL RK3368/PX5s SoMs can run any RK3368/PX5 ROM - all RK SoMs are made by HCT, where ever theyre bought from, so flash away !
[MTCD Android Head Units General] semcoinc:
Thanks typos1

I am getting a bit more comfortable with the idea of a ROM flash. I may be giving the HA 6.0 upgrade a go this coming weekend and will report back my results.

Mike
[MTCD Android Head Units General] abagos:
Hi Mike, about the sleep feature I can only confirm the facts by [MENTION=4974080]marchnz[/MENTION] .

As for the upgrade I can only repeat the advice to keep your cfg file only as backup and try to configure manually.

Hope I've helped,

Alex.