yashsingh1/xdaforums huggingface dataset:
[MTCD Android Head Units General] Phredeee:
Absolutely true. In my previous professional life I designed HMI panels for large automated industrial equipment. Part of the process in getting a good panel for the application is determining the proper blend of hard buttons and knobs vs soft ones on the screens. A lot can be said for tactile feedback.

BTW, thanks Typos1 for all your input here. It has helped me tremendously. I tolerated aggravating issues for a long time and after reading your comments in a few threads I upgraded my Joying MTCD with HA 2.59 MCU (Yes it is compatible and helped the BT phone audio a lot with now both speakers!) and Malaysk 12.6 w/MicroG. It made a big improvement and solved some bugs. Enough that I think this PX5 upgrade will be just what I need.

Not to hijack this thread..... In doing my upgrades to fix problems it either caused some minor ones or didn't fix some. There may be fixes for these, I'm still working on it.

I can not connect to my phone's mobile hot spot only if WPA2 is enabled. The phone is Nougat and works fine if open, so I'm currently using MAC filter for security. Maybe a Marshmallow HU will work better?

The RGB dash lights around the hard knobs are no longer color or brightness tunable (MCU?) but I can select R G or B and the red is close to the orange I want to match the other dash lights (Small issue)

I am looking for a DVR or setting for the existing one, for my dash cam that will auto start on power on every time.

A method to have a separate EQ automatically for different sources would be great. My music and my phone need different EQ and FX.

Maybe Tasker or IFTTT is the answer for some of these? On of my winter wish list items is develop a method to have my garage door automatically open when I approach. With the PX5 a background Geofence to trigger my already opening app may be possible?? I love Android head units!
[MTCD Android Head Units General] typos1:
I ve worked at companies where touch screens have been rejected for some applications because of the lack of haptic feedback and the slower speed of input.

Glad I ve helped. :)

I would guess that the RGB issue is to do with the fact that you've changed from a JY MCU (which is Joyous BTW - Joying are a retailer, not a manufacturer) to an HA one, I would check [MENTION=4974080]marchnz[/MENTION]'s thread about changing MCU types for info on how to sort that.
[MTCD Android Head Units General] Wout2426:
I hope that I can get some advice.

I upgraded my joyous from px3 to px5, and want to put malaysk on it.

In the malaysk thread I read something about realtek / atreos drivers for wifi and bt.

Anybody here has flashed malaysk after the upgrade ?

Problems with wifi and bt not working ?
[MTCD Android Head Units General] techo91:
I’ve done it and I have no issues like that. MTCD_KSP.
[MTCD Android Head Units General] dude-nl:
I've upgraded my ox3 to px5 and installed Malaysk.

Now I can't watch video through Youtube or my IPTV anymore (through browser, perfect player, Kodi etc). The sound is good but the video stands still or give green screen.

When I open the same youtube or channel I on my tablet or mobile everything run's fine.

Looks like it has problems with HD video... Sounds familiar to someone?
[MTCD Android Head Units General] arshish1612:
Hi,

I currently have the new version PX3 2GB Android 7.1.2 with MTCD_MX_V2.56b_1. Bluetooth unit is SD-XXX. My problem is that there is no way I can root this unit. If I buy this board will it work for my HU? It will downgrade me to Android 6 with a PX5 which is fine. The can I use Malaysk's PX5 ROM to get route?

Would the WIFI / BT / AUTOSLEEP would work?
[MTCD Android Head Units General] typos1:
You cant use a ROM for RK3368/PX5 units on an RK3188/PX3 unit.
[MTCD Android Head Units General] thecos77:
MTCD_LM upgrade

Hi, I have an older MTCD_LM unit with Android 5.1.1 and I am trying to figure out the following:

1. Is this generation of units now refered to as PX3 or is PX3 newer than what I have?

2. Can my unit be upgraded with the PX5 board?

3. Where is the best place to buy the PX5 upgrade if it can be used on my unit?

Any info would help me catch up and be appreciated. Thanks
[MTCD Android Head Units General] typos1:
The newer RK3188/PX3 units have a slightly modified SoM but its fully compatible with any MTCD motherboard, so yes your unit can be upgraded, SoMs are available on Aliepxress, as are teh RK3368/PX5 octacore SoMs.
[MTCD Android Head Units General] thecos77:
Yes! thank you.

I'm looking to order the Witson PX5 board from aliexpress (https://www.aliexpress.com/store/pr...32814450733.html?spm=2114.12010615.0.0.FjpmNC)

Would this be the best (bang for your buck) upgrade available for my unit at this time? I'm out of the loop as I havent even updated my units firmware in over a year.

Thanks again.
[MTCD Android Head Units General] typos1:
I guess, it is I have both the quadcore RK3188 2Gb N unit and an octacore RK3368 2Gb MM unit and I cant tell much difference in the performance, but theyre the same price so its just down to whether you want Nougat or MM.
[MTCD Android Head Units General] puffobro:
Hello

I'm selling it for a new, purchased, purchased px3 2gb core. for those who are interested contact me.

thank you

---------- Post added at 05:34 PM ---------- Previous post was at 05:33 PM ----------

Ciao,

lo sto vendendo per un nuovo core acquistato, acquistato, px3 2gb. per coloro che sono interessati mi contatti.

grazie
[MTCD Android Head Units General] thecos77:
Which board are you selling? Price?
[MTCD Android Head Units General] pedracca:
Hello, my px5 board finally arrived today. I have an XTrons unit (PF75ATTAR), which I think may have given some trouble upgrading to others, but I thought it was worth trying (recently it's becoming painfully slow).

I have a question though, regarding if it is worth updating the firmware right away. What do you think? Sorry if it's been asked already, information in this thread is overwhelming. I've already gone through most of the pages and couldn't see the answer.

I'm asking because I'd like to avoid the system degrading performance over time, and maybe the Malaysk rom can help on this.

Thank you in advance.
[MTCD Android Head Units General] typos1:
You dont have an "Xtrons" unit, Xtrons are a seller only, go to settings/about device - the 2 or 3 letters after "MTCD" will tell you what unit you have.

Its certainly best to update the MCU to the latest version, probably best to update the ROM also.
[MTCD Android Head Units General] pedracca:
Thank you for your answer. The unit is a GS (MTCD_GS_V1.61_1).

Does this mean that the correct MCU file to flash would be: Comprehensive Updated MCU List for MTCD Head Units (current latest GS_12-17-2016_2.04_1_dmcu.img - version2.04_1)

And latest ROM from this thread: [ROM][PX5][HD] Malaysk ROMs for any yet known MTCD-Device (currently September 7th, 2017, Firmware No. 5.0)

?

Thank you again.
[MTCD Android Head Units General] puffobro:
Hello

I sent you a private message
[MTCD Android Head Units General] typos1:
The correct MCU is ANY MTCD GS MCU.

The correct ROM is ANY MTCD RK3368/PX5 ROM.
[MTCD Android Head Units General] arima0k:
Hello, my unid is hotaudio RK3188, can i install this coreboard on it? it is compatible?
[MTCD Android Head Units General] typos1:
Dunno, you havent given us enough ifno to tell - MTCB/C units use RK3188 processors too, what MCU have you got ? Does it say "MTCB", "MTCC" or "MTCD" in settings/about device?
[MTCD Android Head Units General] arima0k:
MTCD
[MTCD Android Head Units General] pedracca:
Hello, I'm a bit desperate after hours fighting with my new px5. Would really appreciate some help.

- System is a GS sold by Xtrons. It originally had a px3 with stock android (06072016FW) and v1.61 GS MCU, everything working, though very slow.

I've fitted the px5 board and updated to latest GS MCU (2.58) and Malaysk 5. Very fast, but... can't get the Realtek chipset to work (rtl873bu), so no BT nor Wifi, which renders the HU useless for my needs.

Here is what I've tried so far:

Updating MCU, tryed

- GS 2.58

- HA 2.61

- HA 2.65f (MTCE version)

- Downgrading to previous versions from GS and HA, but Recovery rejects them

Flashing stock firmware (as of 20170901).

Using PX3 drivers, as suggested here and here.

Renaming gocsdk and sdsdk process as described here

Tryed every BT setting in Factory Settings.

Reseated the board several times

None of these helped in any way.

I'm out of ideas, I've tried to unpack a px3 stock rom so I could try more driver files if I found them, but Rockchip tools didn't work with my Ubuntu, even though I've followed the instructions it won't unpack the rom for me.

Again, would really appreciate some help. Thank you.
[MTCD Android Head Units General] typos1:
You could try the custom ROM builder here :

https://xdaforums.com/android-auto/...ns-development/tool-mtcd-rom-builder-t3475444

I ve used it to unpack ROMs for RK3188/PX3 MTCB/C units and MTCD/E RK3188/PX3 1Gb units and I use Ubuntu too. Cant say if it will work with RK3368/PX5 ROMs, I think I may have read it doesnt, but worth a try.
[MTCD Android Head Units General] pedracca:
Thank you typos1, will try this one once at home with my laptop.

Meanwhile, does this driver thing make any sense to you? (px5 packing drivers for Atheros instead of Realtek, as I've read in the forum).

I'm in doubt because the files I'm substituting in /system/lib are named the same, and the name of the files seem to refer to the Realtek chipset (/system/lib/rtl8723bu_wlan.ko).

Is downgrading MCU not possible to some extent, or is it a matter of trial and error (I've read in the forum someone that had to try several times before being able to flash)? I can go from 2.65 to 2.58 but not anything below.

Does it make any sense trying to downgrade? I mean, with v1.61 GS MCU + PX3 board it worked, but is there any relevant piece of firmware in the MCU regarding the BT/Wifi chipset?

I'm trying to focus the efforts towards one direction, discarding the MCU or the android system would help a lot.

Thank you!
[MTCD Android Head Units General] typos1:
You can up or downgrade the MCU at any time, so flashing an older version is worth trying.

Stupidly and confusingly, there are 4 or 5 RK3368/PX5 threads in this forum (they really need to be merged), so its not easy to track problems - do you subscribe to all of them ? You should if you dont.

Anyway I ve read a bit about similar problems, cant remember which one but one there was talk of an RF shield near the corner of the SoM that was missing causing wifi/BT problems. Also theres the antenna problem I mentioned earlier. Have you taken the lid off the unit ?
[MTCD Android Head Units General] pedracca:
I think I'm aware of the threads that could potentially contain some relevant info, most of them are 100+ pages so I'm searching "wifi" in them and looking for ideas, but indeed, they are overwhelming.

My unit is in the workbench and fully opened. The PX3 had no issues with the antennas, maybe this can get worse in PX5 but the behaviour when activating wifi clearly indicates there is a software issue. After pressing wifi toggle nothing happens, it doesn't even scan for networks (the same action with the PX3 had the correct behaviour, it scanned for networks).

Any sequence downgrading MCU which you think would work best? Any firmware I've tried below 2.58 is rejected because invalid signature or sort of that (can't remember exact message).
[MTCD Android Head Units General] typos1:
Apologies - yes it cant really be the wifi antenna issue.

But the RF shielding issue, I m not so sure, having thought a little more, maybe it only applies to units that came with the RK3368/PX5 processor in the first place, I cant remember, but maybe, due to the different layout of components on the RK3368/PX5 SoM or some similar reason, there is interference causing the chip not to work ? I think it could be worth you finding the posts related to the subject to at least eliminate it from your enquiries.
[MTCD Android Head Units General] marchnz:
Did you document your factory settings before MCU upgrade and validate the factory settings were correct after the MCU upgrade?

In particular and critical to your described issue, is the factory setting for [Bluetooth]

correct? What was BT set before and after upgrade?
[MTCD Android Head Units General] pedracca:
I've attached a photo of the antenna connection. It only has one antenna connected, the other spot doesn't have anything soldered. Maybe not the best layout, but again, knowing it worked on the px3 it leans me towards a software issue.

I made an export of a working dmcu.cfg, updating with it didn't help, though this was after upgrading to GS 2.58. I've tried every BT option in the list, they are: "MD725", "WQ_BC5", "WQ_BC6", "WQ_BC8", "Parrot_FC6000T", and "SD-968". As far as I know, correct setting is "MD725". Original setting was "WQ_MD725", wich no longer shows up after upgrading from mcu GS 1.61, but I'm guessing it is the one that shows up as "MD725" now.

I've also tried selecting "NO" to test wifi.

None of these helped. No BT nor wifi after all.

Thank you all for your answers.
[MTCD Android Head Units General] marchnz:
Can you attach a better image of the main board and detailed image of th WIFI/BT chip? Should be RTL8723 as I would think all MTCD are.

Also, recommend connecting an additional antenna if that WIFI/BT chip is a , you could repurpose the antenna, socket, cable etc, from an old Wireless router. The GS board I have is identical and has a second antenna "wire" soldered.

Note that I own a JY, the GS board (both RTL8723)I have is a spare part, used as a JIG for NAND recovery.
[MTCD Android Head Units General] pedracca:
I think it is, last digit is a bit blurry but it seems so. Soldering an additional antenna is something I have in mind, but first I should be able to make it work.

I'm attaching some more pics.

I've spent a few hours today too and I'm starting to think there is no way. Even as stubborn as I am.

I've finally been able to unpack a px3 rom and extract every file in system partition with the "RTL" string in its name + wlan.ko + wb.ko (with the link that typos1 provided, TY), and copied/substituted in a Malaysk5, but didn't work. I can't do the same in a stock rom because I can't root them, kingoroot wants to connect to internet and obviously there is no connection, so it fails and can't try the substitution in any other rom.

I've also tried system images from different dates from these vendors: GS, HA, KGL (haven't found stock roms from other vendors listed as compatible with GS), but it didn't work.

I'm a sad PX5 owner :crying:

PD: I now see that the glue in the wifi antenna is in the middle, but the cable is correctly soldered.
[MTCD Android Head Units General] marchnz:
Hi,

You have the standard MTCD RTL8723 BT/WIFI. It should work out of the box. Suggest checking for connection/bend pin to the SOM. Also, remove that glue on the WIFI antenna. Just confirming, is WIFI an issue for your PX3 module?

Cheers
[MTCD Android Head Units General] pedracca:
Wifi/BT worked fine with px3, even when switching back from the px5 with newer MCU, so I'd narrow it down to the android firmware.

I don't have the HU here right now, but I'm confident I didn't bent it, I was really careful while replacing the board. Anyway, as I'm giving up, will see when I switch back to PX3. I even modified the heat sink (drilled a bigger hole) to enable the center hole to use the third screw next to the pins, just to make sure it was properly seated.

Too sad it didn't work, not only for the 100$, but for the improvements in speed I won't have, it would really have helped with waze, which I use everyday.

Maybe in the future if someone succeeds I'll try again, I will pay attention to the forum but for now, it is over, too many hours spent.

Thank you all, very much!
[MTCD Android Head Units General] typos1:
You didnt try the antenna shielding then ?
[MTCD Android Head Units General] pedracca:
Not really necessary, wifi is working well with px3, and even if it would help, it is not the real problem with the px5 board. Maybe in the future.

Forgot to mention (I posted at 4 am, this thing was driving me nuts) that you can really tell if the Wifi could work even without switching it on, as the "advanced" menu from Wifi config shows an invalid MAC address. I'll post pictures when I get home.
[MTCD Android Head Units General] typos1:
As I said, this has fixed a similar problem in the past - some sort of interference was causing the wifi not to work with the RK3368/PX5 SoM, so its worth trying.
[MTCD Android Head Units General] pedracca:
I'm sorry but I can't find references in the forum, this is the only I've found. Is this what you are suggesting? I mean, using RF shielded tape? I haven't used it never before, but I suppose I could buy some and try. I suppose it is non-conductive, but how, or more specifically, where is applied?

Thank you.
[MTCD Android Head Units General] typos1:
Yes, looks like I was slightly wrong in that it wasnt wifi/bt that was not working on that unit (it was 2 months ago, thats my excuse !).

Still, its so simple its worth trying to see if it helps your wifi/bt problem.
[MTCD Android Head Units General] wirethin:
Do give up yet. I had the same problem as you but I managed to fixed the problem after try and error for a week just like you did.

I have a JY-135 with PX3 MCU2.0.6(JY) and Malasky 11.6. After upgraded to PX5 board, with MCU2.0.6(JY) and ROM come with the board, everything worked fine including WiFi & BT. I exported dmcu.cfg and upgraded MCU to HA2.59 and ROM to Malasky 5. I found WiFi and BT stopped working. So I upgraded MCU to MTCE 2.65f hoping issue would be fixed and still nothing. Searched web found no solution. Only one post mentioned WiFi and BT problem after upgrade. I downgraded to MCU2.59, MCU 2.52, MCU2.40 with no success. I can not downgrade back to JY MCU because of error "Version mismatch". I guess it is because of now MCU is HA not JY anymore. As last try, I put PX3 back, boot up HU, found WiFi and BT still worked with MCU2.40 and Malasky 11.6. With PX3 board, I exported dmcu.cfg again and upgraded MCU to MCTE 2.65f. Rebooted HU and found WiFi & BT still worked with MCU2.65f. Powered off HU, replaced PX3 with PX5 and found WiFi & BT worked now. So now I have PX5 with MCU2.65f & Malasky 5 working. Couldn't be more happier. Based on my experience, I think the steps that brought HU back was upgraded MCU with PX3 board first and then switched to PX5 board not the other way around. Hope this can help you or someone else in the same boat.
[MTCD Android Head Units General] typos1:
Ah, that sounds promising, lets hope it works for him . . .
[MTCD Android Head Units General] pedracca:
Cant' wait to try it when I get home. Thank you so much!
[MTCD Android Head Units General] marchnz:
Fantastic contribution, thanks for sharing!
[MTCD Android Head Units General] pedracca:
Well, finally tried, no luck :crying:

I am not sure I backed up the correct dmcu.cfg in the first place, though. I installed the mcu update right away when I installed the new board and can't remember if I did it before or after the first MCU update.

Maybe this should work if done right, don't know. Anyway, I've asked a fellow who has the same unit (Xtrons PF75ATTAR) if he could export the MCU configuration (afaik he hasn't ever updated). I'll try again if I can get it.

At least I was able to reproduce the issue in the PX3 board. This could look like something bad, but I think is good: There's simply a combination of drivers/configuration that will work, others won't.

Tomorrow I'll be looking at some more logs, maybe I can find anything of interest.
[MTCD Android Head Units General] wirethin:
Sorry to hear you are still having trouble. Recall my recover steps, I think the most important sign is WiFi & BT worked again after PX3 board was put back. As long as WiFi & BT works under PX3 board, it should work.

I don't think the dmcu.cfg exported under PX5 matters. When I recovered mine, I did not used the dmuc.cfg that was exported under px5. When I put px3 board back, I found WiFi & BT worked, that was when I exported dmcu.cfg and used in the following MCU upgrade steps.

From your description I could not tell if WiFi & BT worked after you put PX3 board back.
[MTCD Android Head Units General] Overmann:
Just purchased and installed a Witson PX5 coreboard into my KSP PX3 MTCD unit. It did indeed work. Now to get custom firmware. No offense, Witson, but I need root until I can construct the dimmer adapter for my car.
[MTCD Android Head Units General] typos1:
TBH you dont really seem to be fully persevering with the "ideas" that others have suggested, you seem to be sticking to your own "ideas" about solving it which arent working.

If I were you I d try anything, however unlikely it seems that it would help.
[MTCD Android Head Units General] pedracca:
I am willing to try the RF shield thing, but I haven't found anyone that has posted how to nor pictures.

I haven't worked before with this, so I don't know what to apply, nor how, even where.

If you can help me out giving some advice on what, where and how to apply I'd do it without hesitation.

Thank you.
[MTCD Android Head Units General] typos1:
I have not either, from what I recall its just a case of some metal or foil tape (insulated of course) on one corner of the SoM.

But also I think you havent fully tried [MENTION=8040039]wirethin[/MENTION]'s suggestions either.
[MTCD Android Head Units General] pedracca:
I can guarantee I did, and variations of what he described. I said I can't reproduce it 100% because I think I don't have the very first dmcu.cfg, because I didn't export it. That was my fault but I didn't know I would need it. Anyway, as far as I can tell dmcu.cfg makes no difference at all, same file works / doesn't work depending on the board (I've binary compared the cfg files).
[MTCD Android Head Units General] typos1:
It does make a difference - it saves the mcu settings.
[MTCD Android Head Units General] JohnnyTightlips:
I have this unit http://www.eonon.com/Android-Car-GPS/Vehicle-Specific-GPS/GA6151.html Will this work as an upgrade for me? What else do I need to flash or install? I tried searching but there is just so much information I was not able to easily peace together the latest way to do it all.

Is this the correct board?

https://www.aliexpress.com/item/WIT...VD-Android-5-1-A5XXX-upgrade/32814725689.html
[MTCD Android Head Units General] typos1:
Yes it will work. you dont need to flash or install anything other than the actual SoM.
[MTCD Android Head Units General] JohnnyTightlips:
Is there any specific updates or install you would recommend to get the most out of the faster chip? What are most people running for the rom?
[MTCD Android Head Units General] typos1:
No, just the latest, there is also [MENTION=3590033]Malaysk[/MENTION]'s ROM.
[MTCD Android Head Units General] dh2010:
Mtcd upgrade

Is this upgrade

https://m.aliexpress.com/s/item/32814725689.html?spm=a2g0n.search-cache.0.0.bc91bfcJpW2ka#autostay

Can work in mtcd_kd 800*600 resolution
[MTCD Android Head Units General] typos1:
It can work in any MTCD/E unit.
[MTCD Android Head Units General] makes2068@gmail.com:
Info from Witson via AliExpress message center to my problem "no autosleep" with PX5 board in my VW Touran:

very strange...
[MTCD Android Head Units General] aLkRicha:
what coreboard to choose?

Hey, could somebody (who knows) tell me what coreboard i could use for update my head unit (MTCD_KD), i attachments photos of coreboard what i have now.

Thanks.
[MTCD Android Head Units General] typos1:
Any MTCD SoM - all the motherboards can take any of the 3 processor types - RK3368/PX5, RK3188/PX3 in 2Gb N configuration or Intel Sofia.
[MTCD Android Head Units General] aLkRicha:
RK3368/PX5 - the best choice?
[MTCD Android Head Units General] typos1:
The 2Gb RK3188/PX3 is perfectly good, but the RK3368/PX5 is more modern, has more cores so its probably the best one to go for.