Develop Bugs

Weird BT issue

I have an Eonon GA2114 - rk3188, 800*480, KLD2 2.77 MCU, BC6B BT board
With the original Eonon ROM bluetooth is unusable. There is no default device name or PIN. If I type in these, they disappear after reboot. It does not detect either phones or OBD, nor is it detected by phones.
With other KLD ROMs bluetooth is active, can be paired to both phones and OBD but all sound is muted during calls (both ways)
With Joying ROMs, including Malaysk, BT works as it should.
This is clearly a software issue, anyone has any clues about where should I start looking? Are these manufacturers using different BT stack implementations maybe?
Anybody can provide a working rk3188 800*480 Eonon ROM? Not the October 19 ROM also available on this forum, that one has the issue described above.

Hi,
I'm facing the same issue, I have an GA5153V device and contacted Eonon about that but hey keep sending me wrong MCU version and ROM. Can You please tell me which MCU version do You have?
It would be great if someone posts working version of Eonon ROM.

Sn00k said:
Hi,
I'm facing the same issue, I have an GA5153V device and contacted Eonon about that but hey keep sending me wrong MCU version and ROM. Can You please tell me which MCU version do You have?
It would be great if someone posts working version of Eonon ROM.
Click to expand...
Click to collapse
My MCU is a KLD2.
I have requested Eonon to send a compatible ROM, even older, but they say it's the only one available. The ROM they are sending id the one available on this forum in the Factory ROM thread. Eonon appear to just brand generic units and have no technical personnel. I gave up getting a competent answer from them. For now I am on Booroondook's ROM, waiting for Joying to release a Lollipop version.

m00n61 said:
waiting for Joying to release a Lollipop version.
Click to expand...
Click to collapse
At present there is no need to have a bugged (and unfixed by Google) Lollipop 5.0.x on these units, Kitkat 4.4.4 is still the best IMHO.
We'll see in the future what will happen with Marshmellow...

m00n61 said:
My MCU is a KLD2.
I have requested Eonon to send a compatible ROM, even older, but they say it's the only one available. The ROM they are sending id the one available on this forum in the Factory ROM thread. Eonon appear to just brand generic units and have no technical personnel. I gave up getting a competent answer from them. For now I am on Booroondook's ROM, waiting for Joying to release a Lollipop version.
Click to expand...
Click to collapse
Since Eonon is keep sending me KLD2 based mcu even I have KLD(MTCB-KLD-v2.78) by default I cannot use this version because FM radio is not working. I said that to them but again they sent me KLD2, the I gave up on them and now trying to fing some solution to make bluetooth to work.
Can You please tell me where did You download current ROM that You are using?
thx!

Sn00k said:
Since Eonon is keep sending me KLD2 based mcu even I have KLD(MTCB-KLD-v2.78) by default I cannot use this version because FM radio is not working. I said that to them but again they sent me KLD2, the I gave up on them and now trying to fing some solution to make bluetooth to work.
Can You please tell me where did You download current ROM that You are using?
thx!
Click to expand...
Click to collapse
MCU and OS ROM image are independent, even if the Chinese keep sending both you can burn only the Android ROM and leave the MCU untouched.
Anyway, I am currently using this ROM. A more detailed installation procedure is in the first post of the thread.

Go to factory settings and adjust the bt module there. Code is 126.
I was seeing the same thing when I found that option and began playing around.

Klyde Unit What to do ?

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.

please help me, I installed the wrong MCU

Hello ,
I have updated the MCU incorrectly because of cross compatibility.
This is the original version of my device in the pictures.
now my device changed to screen 1024x600
please help me, how do I get to the 800x480 version

Your pics show MTCD, try MTCD section, see cross-compatibility thread which details how to resolve for 800x600.

Restore MCU: MTCD_KGL

Please I need your help, I am extremely worried trying to return my DVD CAR to its initial state.
My unit originally had the following data:
MCU: MTCD_KGL_V1.40_1
Android 5.1.1
rk3188-userdebug 09032016
Then, looking for improvements, update the firmware to the version
[ROM] [PX3] [RK3188] [Nougat] [7.1.2] Hal9k ROM 2 for ALL RK3188 / PX3 MTCD / E.
Instead of improving my equipment, it became very slow, play store services do not work for me and almost all applications give me an error.
Please I am not criticizing this version, I am sure the errors that I mention are due to an incorrect installation of my part.
The biggest problem of all is that I can not find a way to return to my old installation with Android 5.1.
Please I'm going crazy looking for a way to restore my equipment but for more I read the different posts every time it gets more complicated "
1- What should be the proper firmware to install
2- Where is the rom stock that I must download, etc etc
I would eternally thank whoever can help me out and give me some advice.
I hope your help

MCU vs Firmware Cross Compatibility

Hi,
This might sound a weird question but can anyone clarify the following
I got a unit which has MTCE_CZ_V3.17_2 MCU (Wondefoo)
Can I for example flash it with MTCE_MX_V3.41 with HCT4_PX5_9.0_ota(20191125) MX/WITSON Firmware?
Or the best is to remain with original MCU?
Can I stay with original MCU and flash with other brand Firmware like HCT4_PX5_9.0_ota(20191125) MX/WITSON?
In short: can I cross upgrade with "X" MCU and "Y" Firmware or the MCU and Firmware has to be always the same "X" version?
What is the best option / combo? The MCU should always remain the original and can upgrade with other brand firmware or can change both?
Thanks

cgentil said:
Hi,
This might sound a weird question but can anyone clarify the following
I got a unit which has MTCE_CZ_V3.17_2 MCU (Wondefoo)
Can I for example flash it with MTCE_MX_V3.41 with HCT4_PX5_9.0_ota(20191125) MX/WITSON Firmware?
Or the best is to remain with original MCU?
Can I stay with original MCU and flash with other brand Firmware like HCT4_PX5_9.0_ota(20191125) MX/WITSON?
In short: can I cross upgrade with "X" MCU and "Y" Firmware or the MCU and Firmware has to be always the same "X" version?
What is the best option / combo? The MCU should always remain the original and can upgrade with other brand firmware or can change both?
Thanks
Click to expand...
Click to collapse
Take a look at wiki in my sig.

MCU and Android updates are completely independent. I'd recommend using the latest CZ update (3.4.1, per 4pda), exporting your settings to your USB/SD before updating, and then installing whatever Android build you want (based on launcher, newness, etc). Will work just fine as long as it's for a MTC MCU device and same SoC (ie, PX6), and has same base version (ie, 9.0).

Thanks for your reply @Matt Devo
Could you please send me 4PDA link?
If I install the latest FIRMWARE and MCU with option wipe cache and delete data, all installed apps which came from factory at initial boot, will stay there or not?
I want that all apps which came remain

Another question about MCU and CANBUS.
If I get same radio from different sellers, for example one has CHS MCU and other CZ MCU.
CHS MCU on factory settings page (126) on CANBUS shows BAGOO ALFA ROMEO, and all works, shows doors open and all.
CZ MCU on factory settings page (126) on CANBUS shows NO and all works but not showing doors open, but if I set BAGOO ALFA ROMEO, S.W.C. stops working and keeps not showing doors open.
Any idea?
That's strange

cgentil said:
Thanks for your reply @Matt Devo
Could you please send me 4PDA link?
If I install the latest FIRMWARE and MCU with option wipe cache and delete data, all installed apps which came from factory at initial boot, will stay there or not?
I want that all apps which came remain
Click to expand...
Click to collapse
https://4pda.ru/forum/index.php?showtopic=959688&view=findpost&p=87174444
if you load one of the Android updates found here and wipe data/cache, you will lose any of the addtional apps your reseller preloads. Recommend to root the device and back those up first.
cgentil said:
Another question about MCU and CANBUS.
If I get same radio from different sellers, for example one has CHS MCU and other CZ MCU.
CHS MCU on factory settings page (126) on CANBUS shows BAGOO ALFA ROMEO, and all works, shows doors open and all.
CZ MCU on factory settings page (126) on CANBUS shows NO and all works but not showing doors open, but if I set BAGOO ALFA ROMEO, S.W.C. stops working and keeps not showing doors open.
Any idea?
That's strange
Click to expand...
Click to collapse
are the canbus modules the same for both units? what MCU version loaded for each?

Matt Devo said:
https://4pda.ru/forum/index.php?showtopic=959688&view=findpost&p=87174444
if you load one of the Android updates found here and wipe data/cache, you will lose any of the addtional apps your reseller preloads. Recommend to root the device and back those up first.
are the canbus modules the same for both units? what MCU version loaded for each?
Click to expand...
Click to collapse
Thanks.
Canbus modules are Bagoo for each, the one shows doors info is CHS and the other which not is CZ.

cgentil said:
Canbus modules are Bagoo for each, the one shows doors info is CHS and the other which not is CZ.
Click to expand...
Click to collapse
again, which MCU version is loaded for each?

Version MCU CHS V3.15, CZ V3.17

Can someone please provide me a link where can i download MTCE_MX_V3.41 ? I had tried on 4pda forum but i can't download anything, probably because i don't have account. I tried to make an account there but can't read the captcha codes in russian so i can register. Many thanks