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.
XTRONS TD702A
mcu version mtcb-gs-v2.73
android 4.4.4_26082015
build rk3188-eng4.4.4 26082015.16:09:23
800x480 as per product webpage spec sheet
http://xtrons.com/td702a-android-4-...itor-with-screen-mirroring-function-obd2.html
i would like to flash Malaysk ROM. i believe i'm compatible but would like some reassurance before i screw something up. do i use update_4_4_4_FUSE_800X480_RK3188_12_MAL_13_02_2016. there is also a file Launcher2mtc3_JY.apk in the directory with update_4_4_4_FUSE_800X480_RK3188_12_MAL_13_02_2016, should i install that or is the stock launcher better?
i also see discussion about updating mcu. what does mcu mean and do i need to update mine with MCU_GS_2.55_Sleep_Musik or is my current mcu more up to date?
i assume there is no twrp for android decks?
thanks in advance for anything yall can teach me about my devise.
Hi,
I buy a Android car radio with version 6.0, but I don't found any information about this.
I want root my radio for can install Apps like ViperForAndroid.
someone can help me to found info about my radio? I found threads like this: https://forum.xda-developers.com/showthread.php?t=3246386 but I don't found my radio version.
My radio:
http://imgur.com/a/MuMxV
http://imgur.com/a/8yZ5Q
Thanks and sorry for my english
Hey!
My english is not good enough (... as I speak spanish...)
I have seen your photos and I have a doubt about the radio app.
Can you store your preferred stations in the order yo want or the system stores the stations it founds in the order it decides?
I have an android 5.1.1 heat unit and my app stores the radio stations in the order it decides. I can not change them or just select those I like.
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 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