Related
This thread is to document MCUs found to be cross-compatible between MTCD units, which includes PX3 and PX5 variants, which share identical mainboard hardware and MCU Chip STM32F091.
The following MTCD & MTCE (as of v2.56) MCUs have been validated as cross compatible on 1024x600 units:
- MLT - 01/07/17 - caution - has resulted in issues for some @leonkernan
- JY
- KBT - 08/12/2017 - thanks @abagos
- KD (v2.40_2 - enables bluetooth hands free in both front speakers)
- KGL
- KSP thanks @Overmann
- GS - Note "version unmatch" error and fix below No issue experienced on MTCE going from JY 2.80 to GS 2.78 and back to HA 2.80 - March 2018
- GS compatible on MX (see post #513)
- HA (v2.56 06/07/17 - note v2.52 on enables "shutdown delay when acc off" menu) HA MTCE (30/09/17) V2.65 https://www.sendspace.com/pro/dl/ufie8k
See this thread for pics where MCU HA and KD has been applied on JY. https://forum.xda-developers.com/showpost.php?p=72737797&postcount=640
I initially upgraded to KD 2.40, then HA v2.52 after first exporting the MCU settings.
Note that I had to reapply MCU settings in [factory sertings] to configure radio, LED, bluetooth, hardware keys, volume levels between radio, bluetooth, system etc.
MCUs were previously thought to be manufacturer specific - e.g. HA, JY, GS, KD, however I have found that they are compatible and of interest where there is either a specific issue with your MCU (e.g. bluetooth out of one speaker, to enable PX5 sleep mode control) or the vendor has long ceased to support & release updates - such as JY.
MCU cross-compatibility became of interest to me when I upgraded my JY [MCU v2.06_2] PX3 with a HCT PX5 SOM and wanted to enable the MCU specific menu item [shutdown delay when ACC off] to control sleep as found on HA/Dasaita.
I first noted that from an XDA post listing JY an KD v2.06_2 being identical and on that assumption, upgraded to KDv2.40_2, which successfully applied - but had to reconfigure factory settings.
Following on, I found a post which has an image of a GS board & MCU chip - noted it was identical to the MTCD JY MCU chip [STM32F091] - then came across a post where a user had inadvertently applied a MTCD GS MCU to a MTCD JY without bricking it.
I then started comparing same version number firmware files from various manufacturer MCUs with a text compare tool. From this work, I had enough info to compare the latest HA v2.52 and conclude it 'should' be compatible. Indeed it is.
As always, check first (suggest confirming MTCD, MCU Chip part number, view/compare the fw files, ensure you have original MCU FW, backup MCU settings or document the settings to ensure your hardware controls, volume control, bluetooth, radio, canbus etc are setup correctly). Apply at your own risk.
Please post your results and I will update this thread.
Updates:
UPDATE: 26/06/2017 Users of 800x480 Users must also apply file[dmcu.ext], a text file containing:
For PX3 --> screen:3
For PX5 --> screen:1
01/07/17 - MLT
06/07/17 - KGL confirmed and new HA v2.56
30/09/17 - MTCE MCU confimed compatible
08/03/18 - MTCE JY/GS/HA compatible - No issue experienced on MTCE going from JY 2.80 to GS 2.78 and back to HA 2.80
GS Specific Notes:
Oberbergler said:
For all those with a GS: Our unit is compatible with the MTCE MCU but you have to restore your settings and maybe to manually reconfigure your touchscreen and buttons. There is a simple function to do this in the factory settings (126) which is called key study. My touchscreen was also swapped by the x axis. I had to go with the swapped touchscreen into the settings, configure it, reboot the unit and everything was fine. For the buttons you have also the possibility to use short press and long press buttons, which is great because our units (at least mine) has only five buttons and no return button. So I use now the power off button as return in short press mode and power off in long press
Click to expand...
Click to collapse
Version unmatch see this post where user resolved by reapplying MCU AND Software APK Fix Here
- Attached Version Unmatch APK fix to this post, thanks @Wadzio
GS Configuration Settings file:
Bose321 said:
Here it is: https://gerbenbol.com/android/dmcu.cfg.
Click to expand...
Click to collapse
Do not dilute this thread by posting "how-to" questions such as - how do I update the MCU, what unit do I have, can I do it, how do I find factory settings, etc. This thread is to document cross-compatible MCUs and the fixes they apply.
Hi! Confirmed, I've upgraded to PX5 (JY UL135). Flashed KD2.40 over JY 2.06_2 then flashed HA 2.52 and everything is working as it should be. Thanks for your work.
I can confirm a cross compatibility as well.
My Unit is a xtrons device with die MCU firmware GS 2.43 and yesterday i did flash the HA 2.52. But be sure to save your mcu config first. Otherwise the hardware buttons won't do what they were supposed to do. But after flashing the firmware and restoring the config, everything is back to normal.
To make it easier to re-apply the settings, you can use the mcu.cfg function and flash it with the MCU, just in case anyone didnt know.
Some time ago I tried to investigate what actually those abbrevations mean. In my understanding GS, JY, HA is related to the canbus profiles, not directly to the reseller. It seems to be reasonable because MCU has really tiny flash capacity and add all canbus configurations to one chip would be impossible.
f1x said:
Some time ago I tried to investigate what actually those abbrevations mean. In my understanding GS, JY, HA is related to the canbus profiles, not directly to the reseller. It seems to be reasonable because MCU has really tiny flash capacity and add all canbus configurations to one chip would be impossible.
Click to expand...
Click to collapse
No, you are wrong there - the letters very definitely relate to the manufacturer, NOT the CAN Bus profiles KLD = "Klyde" KGL, = "Kai Ge Le", JY = "Joyous" etc, this has been established for years.
The seller has NOTHING to do with the software at all.
The CAN Bus profiles are named in factory settings
On MTCB/C headunits there was a slight difference in the code between MCU types so they were not interchangeable (apart from BN and HA), it would seem that on MTCD units there is no such variation in the code.
Does this also apply to LM_ (Erisin) MCUs?
I have a Erisin 5048 HU with MCU 2.41_1. Does anyone have any experience in flashing a different MCU to a LM_ type MCU? I´m worried to brick my HU if a flash a higher HA_ version.
Any info would be highly appreciated.
Greetings
Speedycarv
SpeedyCarv said:
I have a Erisin 5048 HU with MCU 2.41_1. Does anyone have any experience in flashing a different MCU to a LM_ type MCU? I´m worried to brick my HU if a flash a higher HA_ version.
Any info would be highly appreciated.
Greetings
Speedycarv
Click to expand...
Click to collapse
There are no "Erisin" MCUs - Erisin are a seller only, they sell units made by several manufacturers. You have an "LM" unit.
I would stick to what @marchnz has tested already, although having said that, on the MTCB/C units if you flash the wrong MCU you can simply flash the correct MCU to correct it, cant say if its the same for MTCD units, up to you if you want to risk it.
typos1 said:
There are no "Erisin" MCUs - Erisin are a seller only, they sell units made by several manufacturers. You have an "LM" unit.
I would stick to what @marchnz has tested already, although having said that, on the MTCB/C units if you flash the wrong MCU you can simply flash the correct MCU to correct it, cant say if its the same for MTCD units, up to you if you want to risk it.
Click to expand...
Click to collapse
My level of knowledge has not grown in any way after reading your post.
Thank you anyway..
SpeedyCarv said:
My level of knowledge has not grown in any way after reading your post.
Thank you anyway..
Click to expand...
Click to collapse
Maybe read it again ?
Basically, you could risk trying it - MTCB/C units can be restored if the wrong MCU is flashed, maybe MTCD units could be restored if the wrong MCU is flashed also ? But maybe not, so that is your decision whether to try or not.
Otherwise stick to what @marchnz has said and do not try it.
And your unit is NOT an "Erisin" unit, they are sellers and sell units from many manufacturers, you have an LM MTCD unit.
Cant make it any clearer than that.
typos1 said:
Maybe read it again ?
And your unit is NOT an "Erisin" unit, they are sellers and sell units from many manufacturers, you have an LM MTCD unit.
Click to expand...
Click to collapse
Not necessary to read again. I already knew that. That's what i tried to express in typing "my level of knowledge has not grown" Sorry if i write misunderstandable, i'm not a native speaker (German).
Thank you again for your time and patience
typos1 said:
To make it easier to re-apply the settings, you can use the mcu.cfg function and flash it with the MCU, just in case anyone didnt know.
Click to expand...
Click to collapse
Can you explain me how ? Do I put the mcu.cfg file with the new mcu in the root of gps SD ?
In factory settings I see only the option to export, not to import. Or did I miss something ?
Wout2426 said:
Can you explain me how ? Do I put the mcu.cfg file with the new mcu in the root of gps SD ?
In factory settings I see only the option to export, not to import. Or did I miss something ?
Click to expand...
Click to collapse
Thats correct, just put the mcu.cfg file on the SD card with the mcu.img.
typos1 said:
Thats correct, just put the mcu.cfg file on the SD card with the mcu.img.
Click to expand...
Click to collapse
Or, once mcu has been upgraded, you can remove the mcu update (.img) from the root of the gps card and apply the config (.cfg) on the root of the gps card separately - by running the 'upgrade MCU', it will see .cfg file and apply it.
Update for 800x480 users who update to the latest MCU - you must also apply a dmcu.ext
DMCU.EXT details
DMCU.EXT & screen resolution setting/howto/details
dmcu.ext details for PX5 800x480
That said - why is anyone purchasing a PX5 unit with 800x480?!?!
KD --> HA for 800x480 Screen
I have had quite an experience over the weekend, but am able to report successfully updating a PX3 MTCD_KD unit to a PX5 with the HA2.52 MCU Code.
For those of us with 800x480 screen sizes, as now noted in the main thread, we need to create the dmcu.ext file with the appropriate screen size to be flashed with the dmcu.img file.
Just a note that if you run across the issue of not having the appropriate resolution; don't freak out.
One interesting note I hadn't mentioned before is that after the PX5 started thinking it was 1024, I replaced it with the PX3. The PX3 booted thinking it was 1024 also. After reverting the PX3 to 800 (flashing with screen:3), I replaced the PX5. The PX5 however, did not revert back to 800, but remained at 1024. The PX5 did not revert back to 800 until after I reflashed the MCU, specifically stating it was to be 800 (screen:1).
So I tried HA 2.52 on Xtrons TB706APL
I get the following error on reboot.
After I update from dmcu.cfg it goes away but if you go into factory settings and change anything it comes back.
I also didnt see the option for the shutdown that this mcu is supposed to have.
typos1 said:
Thats correct, just put the mcu.cfg file on the SD card with the mcu.img.
Click to expand...
Click to collapse
I assume you mean "dmcu.img" and "dmcu.cfg"? That's how my downloaded img and backup cfg are called.
Bose321 said:
I assume you mean "dmcu.img" and "dmcu.cfg"? That's how my downloaded img and backup cfg are called.
Click to expand...
Click to collapse
Yeah, thats right - the "d" is just there to show its an MTCD MCU not an MTCB or MTCC one.
1-2-Hak said:
So I tried HA 2.52 on Xtrons TB706APL
I get the following error on reboot.
After I update from dmcu.cfg it goes away but if you go into factory settings and change anything it comes back.
I also didnt see the option for the shutdown that this mcu is supposed to have.
Click to expand...
Click to collapse
The shutdown option is under System Settings --> extra settings. You wont find it in the factory settings. Just FYI.
Which dmcu.cfg did you use? I might be wrong, but it seems to me it might be dangerous to use different dmcu.cfg files with different versions of the MCU Code.
Please help me. I bought a navi and would like to do an update. Can you tell me what rom I can install? I searched the entire forum and found no reply.
MCU Version
2017-03-21 11:20:39 RUL_(NOR)_90_C9_685x5009_CAN_ALL_Newlap_AMP
CPU Info
Intel Atom 4QuadCore, GPU4D Mail-450 MP4
Android 5.1.1
seller SinoSmart
https://pl.aliexpress.com/store/pro...2684489095.html?spm=a2g17.12010612.0.0.rGfFBr
Regards
AFAIK there are no ROMs for any Intel based units.
This thread is intended on collect the information about Android 8 (Oreo) over the Android units that features:
PX5 Platform Core Board
MTCD/MTCE MCU Type
The information below is a copy of the same thread for Android 6 by @aarick
Post 2: Firmware
Post 3: Tips, Tricks and Fixes - Rooting instruction here
Post 4: Bugs/Issues
Post 5: Useful apps
Post 6: Useful links
For those not familiar with the PX5 Head unit, the specs are below:
OS: Android 8.0 Oreo
CPU: Rockchip PX5 A53 Octa-Core
RAM: 2GB or 4GB DDR3
ROM: 32GB
Audio output: 4*45W
Features:
Built-in Radio Tuner (RDS Enabled) (18 FM and 12 AM stations Preset)
Built-in USB & SD Slot
Region Free DVD Player
Screen Mirroring
Steering wheel controls (SWC) and Canbus interface
Optional compatible accessories:
DAB+ USB Tuner
TPMS
4G/3G Dongle
OBD02 Module
Camera
DVR
External Mic
The head unit comprises of two parts:
a MicroController Unit(MCU) board, which controls physical buttons and A/V inputs/outputs to/from the headunit. This board interacts with Android OS.
ANDROID part. The main Operating System.
Both MCU and Android ROM interact together to achieve the functionality of the head unit.
MCU
MCU type discussed here is MTCD or MTCE (if your unit has not MTCD/MTCE type MCU this thread is not for your unit)
MTCE is a software upgrade for MTCD, so they are identical in terms of hardware
Manufacturers.
The Manufacturer is identified by the XXX when consulting the MCU information under "device information" [MTCE_XXX_Version]. Take into accout that you should always refer the MANUFACTURER name (not the seller) on the forums for help/assistance. Giving the name for the Seller does not give any information but confusion.
e.g: MTCD_HA_1.93_1 (MTCD Unit with MCU for HotAudio under 1.93_1 version)
e.g: MTCE_GS_2.75 (MTCE Unit with MCU for GESHI manufacturer under 2.75 version)
Known manufacturers for MTCD/E PX5 are:
______________ _____________
GS = GE_SHI (ShenZhen GESHI Electronics And Technology CO.,LTD. Brands: KA JUN DA. Website: http://www.szgeshi.com )
KD = KU_DUO (Shenzhen Kuduo Electronic Technology Co. Ltd.)
HA = (Guangzhou Huge Circle Electronic Technology Co., Ltd. Brands: HOTAUDIO/DASAITA. webSite: http://www.hot-audio.com)
JY = JIE_YOU (Shenzhen Jieyou Electronic. Brands: JIE YOU J)
LM = LEI_MA (Lei Electronics Inc)
MX = MAI_XIN (Shenzhen Mai Xin Da Technology Co. Ltd)
ZH = ZHI_HANG (Guangzhou Zhihang Electronics Technology CO., LTD. Brands: WINCA/ROADNAV/STQ) http://www.roadnav.com.cn)
HZC = HANG_ZHI_CHEN (Same as ZH??)
HXD = HE_XIN_DA
KGL = KAI_GE_LE (Shenzhen Kaigele Electronics Co., Ltd Brands: HUIFEI. Website: http://www.kaigele.com/enus/)
KLD = KE_LAI_DE
KSP = KA_SI_PU (Kasi Pu Technology Co., Ltd. Shenzhen)
XRC = XIN_RUI_CHANG (Xinrui Electronic Technology Co. Ltd)
HLA = (Shenzhen Hualingan Electronic Co. Ltd. Brands:HUALINGAN. Website: http://www.dvdplayer.com.cn/)
(this list will be updated according to users report new manufacturers)
Some information I found on the CPU:
Rockchip PX5 Press Release
Firmware Post
MCU Upgrades Repository:
https://forum.xda-developers.com/showpost.php?p=72622240&postcount=2
ANDROID 8 (Oreo) stock Update List:
All the stock and custom PX5 MTCD/MTCE firmwares are valid for all PX5 MTCD/E units independently of manufacturer/seller/amount of RAM/amount of ROM
December 19th 2017. Source Dasaita. Thanks @hotaudio --> https://www.sendspace.com/pro/dl/kc1azp
January 8th 2018. Source HCT. Thanks @hotaudio --> https://www.sendspace.com/pro/dl/empate
January 18th 2018. Source GS. Thanks @kumarai --> https://yadi.sk/d/umCvHqCDzHccr/RockChip PX5 Android 8.0/GS
February 28th 2018. Source HCT. --> https://yadi.sk/d/umCvHqCDzHccr/RockChip PX5 Android 8.0/HCT
March 5th 2018. Source Dasaita. Thanks @hotaudio --> https://www.sendspace.com/pro/dl/v7cuby
March 13th 2018. Source Xtrons (GS). Thanks @catelusii --> https://1drv.ms/u/s!AjrY0uqbW_kBhCr0zB8pj-rIig_U
April 13th 2018. Source Dasaita (HA). Thanks @hotaudio https://www.sendspace.com/pro/dl/7smety
May 16th 2018. Source Dasaita (HA). Thanks @hotaudio
https://www.sendspace.com/pro/dl/q9mr31
June 11th 2018. Source Dasaita (HA). Thanks @hotaudio
https://www.sendspace.com/pro/dl/np2t2w
June 27th 2018. Source HCT. Thanks @fastebp
https://www.sendspace.com/pro/dl/nkez0x
July 5th 2018. Source Dasaita (HA). Thanks @hotaudio
https://www.sendspace.com/pro/dl/2l056f
July 17th 2018. Source Dasaita (HA). Thanks @hotaudio
https://www.sendspace.com/pro/lo8ztf
ANDROID 6.0 -> ANDROID 8 UPGRADE WARNING
Due to change in partition system and upgrade in recovery system, update can't be performed using the OTA Android 8 files over Android 6.0 as usual method (direct or Recovery) as it will result in an error (or could get a bricked device...)
The only available methods are:
1) Upgrade by using SDCARD slot:
Thanks to @marchnz for the Oreo ROM Dumping, to @kumarai for the recovery change procedure, to @SkyBeam2048 for the compiled solutions for Upgrading/Downgrading (and the comprehensive instructions)
The following Procedure can be used :
https://forum.xda-developers.com/showthread.php?t=3736950
Note1. Your unit MUST have a SDCARD slot with direct access to recovery (Not all SDCARD slots on all units can - some sdcard slots have been reported to be another usb port extension [USB3] and they will not work for upgrading)
Note2. USB port is not able to upgrade the recovery as required.
Click to expand...
Click to collapse
2) Upgrade by extracting the SOM and connecting a homemade OTG USB cable:
Instructions for making the OTG cable:
https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892
For upgrading via OTG cable it is recommended to use Rockchip Tools for the Android 6 to 8 upgrade from a PC (to put the unit into "loader Mode" and then flash the supplied firmware)
Custom Oreo Firmwares:
@Malaysk has been released a prerooted Android 8 image with several improvements and modifications:
https://forum.xda-developers.com/an...-malaysk-roms-px5-2-4-gb-8-0-android-t3762724
Tips, Tricks and Fixes
Root for stock ROMs.
[*] Method 1: SDCard & Flashing Update File
Android 8 ROM Root requires to boot.img to be modified and loaded during the Flasing process. @kumarai has been released a first Oreo Root files based on GS ROM from January.
This information is extracted from:
https://forum.xda-developers.com/showpost.php?p=75741195&postcount=519
ROOT rights for Oreo based on GS firmware from 20180118
Receiving the root only through the loading card. The load map contains a modified recovery, and the update.zip update is modified by the boot.
Download archive
Yandex - https://yadi.sk/d/pFSNkK4_3SwNx5
Google - https://drive.google.com/file/d/1xpz...GmaEPfsjd/view
The archive contains the following folders:
Androud-8-sdupdateROOT
CreateCD
SD Formatter
UpdateZIP-patch-root
- In the CreateCD folder, create a bootable card using SD_Firmware_Tool (the program is configured, no checkboxes are set)
- Image to create a map from the folder Androud-8-sdupdateROOT
- After creating the boot card, delete sdupdate.img from the card
- Copy from the UpdateZIP-patch-root folder to the root of the card's SD update.zip
We insert the card into the recorder, reboot, install the update from the SD Card
Remove the card and reboot the radio.
Map formatted with the program from the folder SD Formatter
The root system / app script writes to MagiskManager-v5.6.1.apk
Click to expand...
Click to collapse
[*] Method 2: Injecting supersu via ADB
Originally Posted by Copycat228
Hello!
Use the following instruction to receive permanent root on Android 8 using adb without flashing device:
On Head Unit, install terminal emulator on device and run two following commands and reboot device. This will open ADB witj root permissions on the port 5555
Code:
setprop persist.adb.tcp.port 5555
setprop sys.rkadb.root 1
On your PC, download latest "SuperSu" zip archive from official site, extract su binary from arm64 directory inside the archive
On your PC, create new file called "rooting.rc" with following content:
Code:
service rooting /system/bin/su --daemon
class main
priority 10
user root
oneshot
seclabel u:object_r:system_file:s0
From your PC run:
Code:
# adb connect "device_ip"
# adb root
# adb connect "device_ip"
# adb remount
# adb shell setenforce 0
# adb push su /system/xbin/su
# adb push su /system/bin/su
# adb shell chmod 06755 /system/bin/su
# adb shell chmod 06755 /system/xbin/su
# adb shell /system/bin/su --install
# adb shell /system/bin/su --daemon&
# adb push rooting.rc /system/etc/init/rooting.rc
On Head Unit, install SuperSu from PlayMarket and ask "NO" when application ask to update the module
Click to expand...
Click to collapse
Reboot and enjoy!
https://youtu.be/4v9s89fYIZ4
Bugs/Issues
Q&A
1. I have a MTCD RK3188 unit. Can I use the firmware updates here published?
No. All the stuff here published is for RK3368 (PX5) MTCD/E units. Only the MCU files could be used for your unit (if it is really a MTCD/E)
2. How do I know if my unit is a MTCD/E?
Go to Settings> Device Information and check the MCU version. it MUST be:
MTCD_XXXXX_yyyyy.
MTCE_XXXXX_yyyyy.
Where XXXXX is the acronym for the manufacturer and yyyy is the version for the MCU file
3. I cant find MTCDs MCU updates, but MTCE. Can I update a MTCE over a MTCD?
HCT developers, starting from MCU version 2.65, has been renamed the MCTD as MTCE. It is reported to be a major software update and it is fully compatible with MTCD MCU. Therefore, you can upgrade to MTCE from MTCD safely.
4. My MCU is XXX and i can't find new updates from manufacturer for a long time. Can I update from other Brand MCU?
Not all the MTCD MCUs are the same, but quite similar between them. There is a thread that is collecting all the MCU cross compatibility based on user experiences.
https://forum.xda-developers.com/an.../mtcd-verified-cross-compatible-mcus-t3624724
5. How Do I enter into recovery menu?
Depending on the HeadUnit, the entering into recovery process could vary.
Reset Button Procedure (You need a needle to access that button inside the Reset hole)
Applicable to:
[*] HeadUnits with no physical buttons on Headunit (just capacitive buttons) [Brands: Dasaita]
1. Press Reset and hold until button light blinks (15-20secs)
2. Release Reset and press again. Hold it until you see the Marshmallow logo
3. Release Reset and wait for the Recovery menu to appear
[*] Power Button Procedure [Brands: Dasaita]
Applicable to:
[*] HeadUnits with physical power button on Headunit [Brands: Dasaita]
[*]When none of the above procedures worked:
1. Disconnected all power from the unit... ACC & BAT disconnected
2. Prepared 12V power supply with on negative and two positive connectors
3. Connected negative to GND & one positive to BAT
4. Connected USB keyboard
5. Press right ALT (ALT GR on some keyboards) and PrintScreen
6. Connected the other positive lead to ACC (unit does not work if both BAT and ACC are not connected)
6a. Start pressing repeatedly on E (not holding E pressed, but press...release... press... release..... rapidly)
7. The boot logo shows (MarshMallow...etc) and after a few seconds the unit reboots itself
8. Release right CTRL & PrintScreen and continue to repeatedly press on E.
9. The Recovery shows on screen.
6. I have a complete Bricked Unit with a continuous loop. What can I do?
First of all, you have to try to reload the firmware into the unit. As you are not loaded into Android system, you must reload the firmware by using the recovery menu. To enter into recovery menu read the FAQ#5.
Most of the times, reloading the Android firmware solve the issue. Try with different firmwares if you can't succeed at first time. When, even having tried to update your firmware from recovery, but it did not succeed, you probably have corrupted your NAND. In that case a more complex solution is available (desoldering/soldering is required) to come the unit back to life. Thanks @marchnz for the detailed description on the following thread:
https://forum.xda-developers.com/an...tions-development/px5-stuck-bootloop-t3635412
7. My HeaadUnit never shuts off and, even several days, after switching engine on the Headunit starts in a few secons....Can I kill my car battery?
These units are designed to enter into deep sleep state detecting ACC off, in order to avoid each time you connect the car, you had to wait a full cold boot (20secs) and they just wake up in 2seconds. During This sleep state, the Headunit consumes a small current (just 100-150mA). Such current can't drain your battery.
Some manufacturers (like Dasaita (HA)) have implemented a menu in which, apart of Auto-Sleep you select at which time you want to HeadUnit shuts off completely, useful for long car unused periods.
8. My apps are killed during Sleep and they don't start again after waking up
These HeadUnits kills background processes (except specific ones) during deep sleep state (see Q&A#6). The killing process is managed by MTCManager.apk file. A developer (@graser) has been released a tool that is based on adding apps/services to a whitelist to pevent the unit killed them during sleep. You need root & Xposed Framework. Currently only working on Android 6. wait for a Android 8 upgrade
9.How can I root my unit?
PX5 devices under MM can be rooted easily by means of using kingoroot app (not kingroot), but Android 8 is more complicated (see Post#2)
10.My Bluetooth is not Working. What can I do?
Some specific implementations for MD725 bluetooth device are lack of necessary Blueooth SDK file into Android image. Currently no solution has been found apart from waiting HCT (software developers) to release an Android 8 upgrade with the required SDK included.
Useful apps
Tool Unpack Repack system.new.dat system.img For Windows v3
Current Oreo update file is based on a "update.zip" file (not classic .img file). When decompressing a file system.new.dat contains all the system information and apks. This tool can unpack and repack these kind of files:
https://forum.xda-developers.com/an...tool-tool-unpack-repack-dat-img-v2-0-t3284806
Useful links
Reserved
---------------
Interesting... Hoping for someone to release an upgrade method....
emre33 said:
ANDROID 6.0 -> ANDROID 8 UPGRADE WARNING
Bootable SDCard to GPS slot??? boot.img, uboot.img
Click to expand...
Click to collapse
What's that mean then?
Sent from my [device_name] using XDA-Developers Legacy app
Reverse camera interrupts head unit sound, is this a software limitation or hardware?
Reverse volume in settings
Sent from my [device_name] using XDA-Developers Legacy app
Hi,what is rar password?
jtheg said:
Reverse volume in settings
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Will take a look tonight. Thanks
zeyret said:
Hi,what is rar password?
Click to expand...
Click to collapse
No password
Hi,
I have GS px5 HU how can I install it? Please help Thanks!
kispako89 said:
Hi,
I have GS px5 HU how can I install it? Please help Thanks!
Click to expand...
Click to collapse
YES!
Why don't we all jump in and ask that question without reading at least the first page
Hi, just bought my unit recently. Was very happy with the RK3188 version, just a little slow. This one is much faster, only the display is a big disappointment in my eyes. The colores are not really rich in contrast. Grey font on white background is not really readable. Is this the same issue for you too?
dboff said:
Hi, just bought my unit recently. Was very happy with the RK3188 version, just a little slow. This one is much faster, only the display is a big disappointment in my eyes. The colores are not really rich in contrast. Grey font on white background is not really readable. Is this the same issue for you too?
Click to expand...
Click to collapse
I don't know which specific model you have, but I have experienced some of the same. Grey on white is hard to see. I think it helps to view the screen from a more direct angle. I am also experimenting with a sun blocker for when the sunlight angle is very shallow. I may possibly try substituting a 10" screen from a 4gb Marshmallow model. And finally I've ordered a model with a 9" display which is not for my car but I believe it will fit, to see if the screen is any better. I think the 10" Intel Joyings had the best screen, incident light reflects off the pixels instead of the faceplate. Having said all that, the Oreo model I have seems useable, although I haven't taken it on what I would call a road trip yet.
As I still have not opened my Unit, looks like OTG USB is possible only on board modify at least according to https://forum.xda-developers.com/showpost.php?p=73057218&postcount=3 and based on provided schematics in https://forum.xda-developers.com/an...id-head-units-general/mtcd-schematic-t3637816 wonder if there is a way to simplify the process.
I'll have my new GS 8.0 PX5 4.0GB ram unit next week, I'll do a small comparison between my current GS 6.0 PX5 2.0GB unit.
Cheers
Mat
Hello everybody,
I´ve got a Klyde Car Specific Head Unint for my Car now i want a custom Rom or a Android Update or maybe a MCU Update
I´ve readed now many Posts about it but I dont found a thread about my Headunit.
When i understood all in the other Threads is the MCU the Chip that Control everything, is it possible that my System will
boot faster when i do a MCU Update ? My MCU Version is : MTCD_KLD_V254e_1
The next question is about the DAB APP ive got the Version 1.0 sometimes when i start my Car i dont find the Channel i have than to close the App
and restart again is there a fix ?
My Build Number is px5.userdebug 6.0.1 MXC89L maybe somebody got the same Device and can help me.
Sorry for my bad English im From germany
dear greatings
Juergen
jecker1 said:
Hello everybody,
I´ve got a Klyde Car Specific Head Unint for my Car now i want a custom Rom or a Android Update or maybe a MCU Update
I´ve readed now many Posts about it but I dont found a thread about my Headunit.
When i understood all in the other Threads is the MCU the Chip that Control everything, is it possible that my System will
boot faster when i do a MCU Update ? My MCU Version is : MTCD_KLD_V254e_1
The next question is about the DAB APP ive got the Version 1.0 sometimes when i start my Car i dont find the Channel i have than to close the App
and restart again is there a fix ?
My Build Number is px5.userdebug 6.0.1 MXC89L maybe somebody got the same Device and can help me.
Sorry for my bad English im From germany
dear greatings
Juergen
Click to expand...
Click to collapse
All Klyde MTCD/E headunits are the same inside, they only differ outside, therefore the only thing that is important is the make (KLD), the platform (MTCD/E) and the processor (RK3188 (PX3) or RK3368 (PX5) ), so you dot need to look for your specific unit, you need any Klyde MTCD/E MCU and for the ROM any MTCD/E ROM for your processor type - because all PX3 and PX5 MTCD/E units use the same board, you dont have to use a Klyde ROM, you can use ROMs from other MTCD/E manufacturers (a long as they match your processor type).
So, in summary, find the latest KLD MTCE MCU and use that and you can use any MTCD/E RK3368/PX5 Android 6 or Android 8 ROM.
BTW youve posted i the MTCB/C forum and you have an MTCD/E unit, I ll get the thread moved.
This thread is intended on collect the information about Android 9 (Pie) over the Android units that features:
PX5 Platform Core Board
MTCD/MTCE MCU Type
The information below is a copy of the same thread for Android 6 by @aarick and my own thread for Android 8
Post 2: Firmware
Post 3: Tips, Tricks and Fixes - Rooting instruction here
Post 4: Bugs/Issues
Post 5: Useful apps
Post 6: Useful links
For those not familiar with the PX5 Head unit, the specs are below:
OS: Android 8.0 Oreo
CPU: Rockchip PX5 A53 Octa-Core
RAM: 2GB or 4GB DDR3
ROM: 32GB
Audio output: 4*45W
Features:
Built-in Radio Tuner (RDS Enabled) (18 FM and 12 AM stations Preset)
Built-in USB & SD Slot
Region Free DVD Player
Screen Mirroring
Steering wheel controls (SWC) and Canbus interface
Optional compatible accessories:
DAB+ USB Tuner
TPMS
4G/3G Dongle
OBD2 Module
Camera
DVR
External Mic
The head unit comprises of two parts:
a MicroController Unit(MCU) board, which controls physical buttons and A/V inputs/outputs to/from the headunit. This board interacts with Android OS.
ANDROID part. The main Operating System.
Both MCU and Android ROM interact together to achieve the functionality of the head unit.
MCU
MCU type discussed here is MTCD or MTCE (if your unit has not MTCD/MTCE type MCU this thread is not for your unit)
MTCE is a software upgrade for MTCD, so they are identical in terms of hardware
Manufacturers.
The Manufacturer is identified by the XXX when consulting the MCU information under "device information" [MTCE_XXX_Version]. Take into accout that you should always refer the MANUFACTURER name (not the seller) on the forums for help/assistance. Giving the name for the Seller does not give any information but confusion.
e.g: MTCD_HA_1.93_1 (MTCD Unit with MCU for HotAudio under 1.93_1 version)
e.g: MTCE_GS_2.75 (MTCE Unit with MCU for GESHI manufacturer under 2.75 version)
Known manufacturers for MTCD/E PX5 are:
______________ _____________
GS = GE_SHI (ShenZhen GESHI Electronics And Technology CO.,LTD. Brands: KA JUN DA. Website: http://www.szgeshi.com )
KD = KU_DUO (Shenzhen Kuduo Electronic Technology Co. Ltd.)
HA = (Guangzhou Huge Circle Electronic Technology Co., Ltd. Brands: HOTAUDIO/DASAITA. webSite: http://www.hot-audio.com)
JY = JIE_YOU (Shenzhen Jieyou Electronic. Brands: JIE YOU J)
LM = LEI_MA (Lei Electronics Inc)
MX = MAI_XIN (Shenzhen Mai Xin Da Technology Co. Ltd)
ZH = ZHI_HANG (Guangzhou Zhihang Electronics Technology CO., LTD. Brands: WINCA/ROADNAV/STQ) http://www.roadnav.com.cn)
HZC = HANG_ZHI_CHEN (Same as ZH??)
HXD = HE_XIN_DA
KGL = KAI_GE_LE (Shenzhen Kaigele Electronics Co., Ltd Brands: HUIFEI. Website: http://www.kaigele.com/enus/)
KLD = KE_LAI_DE
KSP = KA_SI_PU (Kasi Pu Technology Co., Ltd. Shenzhen)
XRC = XIN_RUI_CHANG (Xinrui Electronic Technology Co. Ltd)
HLA = (Shenzhen Hualingan Electronic Co. Ltd. Brands:HUALINGAN. Website: http://www.dvdplayer.com.cn/)
(this list will be updated according to users report new manufacturers)
Some information I found on the CPU:
Rockchip PX5 Press Release
Firmware
Current PX5 Android 9 firmware development:
Stock
Date: March 22th 2019. Source: HCT. New UI --> https://yadi.sk/d/umCvHqCDzHccr/RockChip PX5 Android 9
Date: April 15th 2019. Source: Dasaita. Classic Blue UI from Dasaita --> https://www.sendspace.com/pro/dl/so9wg2
Date: May 3th 2019. Source: Unknown. --> https://yadi.sk/d/tyLXd4E-xXeylQ
Date: May 5th 2019. Source: MX. --> https://yadi.sk/d/DyLTKQsIQOx7Vg
Date: May 21th 2019. Source: Dasaita. --> https://www.sendspace.com/pro/dl/uv1jkf
Date: May 28th 2019. Source: Dasaita. --> https://www.sendspace.com/pro/dl/tso1eg
Date: May 31th 2019. Source: Dasaita. --> https://www.sendspace.com/pro/dl/yzg5we
Date: Jun 12th 2019. Source: MX. --> https://yadi.sk/d/nsQpvo_4yLv5BA
Date: Jul 31th 2019. Source: Dasaita. -->
https://www.sendspace.com/pro/dl/xj0pve
Date: Aug 13th 2019. Source: MX. -->
https://dosya.co/dpm1tyyojqxu/HCT4_PX5_9.0_Ota(20190813).7z.html
Custom
No custom firmwares have been released yet
Installation:
When upgrading from already Android 9:
Just copy the update.zip extracted from the downloaded OTA firmware downloaded into a root folder of a USB storage.
Upgrade system from Recovery or just update for the specific menu in settings
When upgrading from Android 6 or Android 8 (instructions taken from Hal9K thread)
a) If you have a sdcard slot:
Download Hal9k_Mod_3.x_upgrade_to_Android_9.0.rar
Uncompress it on PC
insert a recently FAT32 formatted micro SDcard into PC (by means of USB adaptor) --> It is recommended 8Gb or lower capacity for this purpose (max working 16Gb)
execute the SD_Firmware_Tool.exe file
Select the Drive which the sdcard is detected by your PC as target
Check that only the option "Update Firmware" is marked
on Firmware select the provided file: bootcard.img on Parent folder
Press "Create"
Wait for the bootable SDcard is created
Go to the Sdcard and replace the file sdupdate.img with the one provided on Parent Folder
in the HeadUnit:
insert micro sdcard on the slot marked as GPS/sdcard
reboot Unit -> Settings > Factory Settings: Password--> hctreboot
the recovery will be automatically upgraded and loaded into display
Use the USB with the upate.zip file in root folder and plug into the USB port
select on recovery: Upgrade system > From USB storage
The Android 9 image will be loaded into the headunit.
You can follow this video as well : https://www.youtube.com/watch?reload=9&v=EhEdeD5RICk
b) if you dont have a sdcard slot or previous metod does not work for you as your sdcard slot is just an USB extension
b1) By means of ModInstaller apk made by Hal9k
This is the easiest way for those who don't have sdcard slot.
Instructions here --> http://hal9k.ru/?page_id=207
b2) By means of OTG Cable
This procedure requires some kind of soldering knowledge and Android knowledge.
You must need a OTG USB cable (build your own) as per the following post:
https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892
Download Hal9k_Mod_3.x_upgrade_to_Android_9.0.rar and look for sdupdate.img file
Download BatchTool_1.7 or AndroidTool 2.39 from this post and download Drivers from this URL
Install the corresponding Drivers (select x86 or x64 depedning on your Windows version)
Open your Headunit and extract the PX5 SOM from the Motherboard
Connect the OTG USB cable into the PX5 SOM as per the previous thread and to the PC
Execute BatchTool.exe or AndroidTool.exe. In AndroidTool go to the Firmware Updte tab
The app will inform you that a USB is detected .
Load the sdupdate.img file on Firmware (FW) option
Press Upgrade button
When Upgraded...plug again the SOM into the Headunit...
Start unit and ente into recovery...you will find a 9.x.x recovery version
Proceed with the system upgrade as previous section from a USB storage
Note: if the app does not detect any device, check the drivers are installed
If the device is detected as mass storage, press oer the switch button to change the mode to a loader (the mode for the device to receive a flash file)
Reserved
Issues and Bugs
features:
Split screen --> Only on MX ROM
Issues found:
The clock is not updated when waking up from sleep --> Corrected from May updates
Not compatible Apps
Car Launcher Pro --> When trying to add a shortcut of an app, the list of selectable apps is blank
Useful Apps
Useful Apps for PX5 Android 9
MTCDialer 1.2.3 --> New Version for this app supporting for Android 9. Thanks @f1x & @scorillo_ro
https://github.com/scorillo/MtcDialer/releases/download/1.2.3/com.f1x.mtcdialer-1.2.3.apk
This app allows to Use Google Voice Assistant to Dial to your Contacts stored in your HeadUnit
To make a call just say a name of the contact stored in your PhoneBook, e.g. "Mom" or "Britney Spears" (if you have one ) or say some digits, e.g. "One One One Seven Six Five Four Two Zero"
No Internet Connection is required.
Reserved (6)
Great, but you should maybe change “ the information about Android 8 (Pie) over the Android units that features” to Android 9 (Pie)!
Done...the risk of the copy/paste
Enviado desde mi SM-G950F mediante Tapatalk
Hi everyone
I also switched to Android 9,
problems: clock not running from autosleep and missing TTS voice, I installed google speech synthesizer but it doesn't feel good.
does anyone have solutions?
Hi,
This update work for PX5 - MTCE_HXD?
Does it add the "Split Screen" feature that is missing from my head Unit?
Can someone tell me how to add this feature?
I have Android 9 but my builder has not enabled this option.
Thanks for your answer....
zimass said:
Hi,
This update work for PX5 - MTCE_HXD?
Does it add the "Split Screen" feature that is missing from my head Unit?
Can someone tell me how to add this feature?
I have Android 9 but my builder has not enabled this option.
Thanks for your answer....
Click to expand...
Click to collapse
sure you can as you have a MTCE unit
I have not tried the split screen, but i will
ikerg said:
sure you can as you have a MTCE unit
I have not tried the split screen, but i will
Click to expand...
Click to collapse
ok thank you, so I'll wait before updating.
I contacted the manufacturer who tells me that Android 9 does not support Spilt Screen on this head unit.
It's curious because Android 8 integrates this feature well
So I've the Android 9 May update on my Dasaita HU. It's really stable and the clock shows the correct time now. The only thing missing is the split screen but i guess it's s well known and discussed issue.
My question now is, I've seen a few videos and pics of Android 9 with white and dark interface (depending on the time of day), i can't see any setting in Dasaita PX5 HU to get this. Is there any compatable Android 9 Rom i can download to get this UI?
Sent from my SM-N950F using Tapatalk
That's possible to downgrade an PX5 MTCD Android 9 to Android 8 with Split screen option ?
naira1 said:
So I've the Android 9 May update on my Dasaita HU. It's really stable and the clock shows the correct time now. The only thing missing is the split screen but i guess it's s well known and discussed issue.
My question now is, I've seen a few videos and pics of Android 9 with white and dark interface (depending on the time of day), i can't see any setting in Dasaita PX5 HU to get this. Is there any compatable Android 9 Rom i can download to get this UI?
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
That rom was the first one distributed by hct (I think) which published the own hal9k.
The rest of roms are based on different manufacturers. I dont know if the mx version is similar to the hct one or we need wait for new release of that specific version.
EDIT:
According to this video, the Last MX version has the ui you want and split is working as well
https://youtu.be/iht_nFyXo1I
Download it from second post
Remember that any rom for mtcd unit px5 is compatible to your unit...not only dasaita ones
Enviado desde mi SM-G950F mediante Tapatalk
zimass said:
That's possible to downgrade an PX5 MTCD Android 9 to Android 8 with Split screen option ?
Click to expand...
Click to collapse
It is possible
Enviado desde mi SM-G950F mediante Tapatalk
sorry but I'm a newbie with this type of update.
My head unit doesn't have SD card support.
But I have 2 USB ports.
When I put the update file at the root of the USB key the specific menu does not start the update.
How to update from the Recovery mode?
ps : the MX update link is broken ... Someone would know where to find the file?
---------- Post added at 05:04 PM ---------- Previous post was at 04:20 PM ----------
ikerg said:
It is possible
Enviado desde mi SM-G950F mediante Tapatalk
Click to expand...
Click to collapse
How to do ?
zimass said:
sorry but I'm a newbie with this type of update.
My head unit doesn't have SD card support.
But I have 2 USB ports.
When I put the update file at the root of the USB key the specific menu does not start the update.
How to update from the Recovery mode?
ps : the MX update link is broken ... Someone would know where to find the file?
---------- Post added at 05:04 PM ---------- Previous post was at 04:20 PM ----------
How to do ?
Click to expand...
Click to collapse
Read the post #2: SDCARD or OTG Cable that you must make by your own.
ikerg said:
Read the post #2: SDCARD or OTG Cable that you must make by your own.
Click to expand...
Click to collapse
By recovery mode
Update by USB it's not possible?
MX-link is broken. I would appreciate if you could create a new link.
Thanks