I have a 2011 Mazda 3n
I tested all 4.4 and 5.1 ROMs, both factory and custom models. In all ROMs, I have a problem with the buttons on the steering wheel not working, and the radio program does not scan any channels.
In the program menu, I tried to manually introduce the buttons on the steering wheel, but unfortunately I did not succeed and it did not work
What can I do to fix this problem?
Car stereo model: mtcc rk3188 kld6 v3.06 s07 1024 * 600 ram 1gig
I should also mention that I did not have any problems with the previous ROM, which was the factory version 5.1.1. I had to change the ROM only because the ROM hung up and could no longer boot.
Could the problem be with the mcu version?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the previous profile:
sloved...
menu factory setting..
hu016865 said:
sloved...
menu factory setting..
Click to expand...
Click to collapse
I actually figured this out — and although technically what you did fixes it — it’s not the “answer” per se. The solution is to navigate to the CANBus selection area and pick the best suited canbus profile. There are tons on mine (15+?) that are designed for all different vehicles. There are a few Porsche options for my Porsche Cayenne so I just found one that worked the best.
If you don’t want to spend the time to find the best suited profile — you can just factory reset it like he said and it will probably give you a working version.
Related
Hey Guys,
I just tried to install Malaysk Rom on my Rk3188 MTCC Device.
Unfortunately I've chosen The wrong resolution.
I Installed The 800x480 instead of the 1024x600 version.
The device boots, but I online See a Black screen, with a home button and a menu Button, thats all.
I tried to just install The correct version but that doesn't seem to help. In recovery Mode I get the following different screens (one screen is some info about the factory version)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bnA87 said:
Hey Guys,
I just tried to install Malaysk Rom on my Rk3188 MTCC Device.
Unfortunately I've chosen The wrong resolution.
I Installed The 800x480 instead of the 1024x600 version.
The device boots, but I online See a Black screen, with a home button and a menu Button, thats all.
I tried to just install The correct version but that doesn't seem to help. In recovery Mode I get the following different screens (one screen is some info about the factory version)
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=69374440&postcount=869
Hi to all.
I have a problem with the Android radio for the Mercedes W220. Erisin company, motherboard KGL-6188-MAIN1-V8.2. The key backlight does not work.
The part that controls it is damaged. In the picture I have marked the red dot. Picture attached. Does anyone know what part this is? Only the DM inscription can be seen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DMB F7
Do any of you know what this element is? Pdf documentation for it?
elman2020 said:
Do any of you know what this element is? Pdf documentation for it?
Click to expand...
Click to collapse
Do you resolve thi problem?
Yes, I fixed the radio. I fixed it differently. I connected the backlight diodes directly to the 5V stabilizer through a resistor. Works well.
i have the same problem on fiat bravo car stereo. the key illumination transisor has blown. you no longer read the code but it should be dmb f7. I can't find it for sale
This is some Chinese transistor, I also did not find a replacement, the marking says nothing. Do as I do, the solution is above.
Same situation here on a KLG-6188-MAIN1-V8.1 mainboard. I cleaned up all around burned area, a lot of components are missing. I am looking for the schema of the main board. Perhaps on russian forum I would find.
@elman2020 , could you post a picture of your fix or a schema please? thank you.
Hi,
I posted this in the Android Auto General yesterday - but that might have been the wrong forum. Please forgive me for the doublepost.
I´m having issues with an old Eonon GA8166A unit in a BMW X5 E53 where the Bluetooth is very unstable (does not work when the unit is cold and only intermittent after multiple restarts when the unit is warm).
Since the unit is discontinued and out of warranty I´m wondering if it is possible to replace the motherboard and/or bluetooth module on this unit? I believe it is a px3 board with android 7.1.2 and MTCD KBT 2.61.
Maybe it is possible to upgrade to a newer board with better cpu/ram (maybe a PX6?) while still maintaining the integration with car system (canbus).
From other threads it appears a new firmware (MTCE KBT 3.3) is recommended before changing the board. I cant´t seem to find newer KBT firmwares though. I have browsed the Yandex disk but can´t find the KBT version.
Any help or suggestions for boards that will work for my unit would be greatly appreciated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi,
I have BT issues with an old PX3 unit running Android 7.1.2 with SD-968 BT adapter. The unit is an Eonon GA8166A installed in a BMW X5 E53.
When the unit is cold BT is not working. I have entered factory settings and set the BT adapter to WQ_BC8 according to instructions from Eonon. This works for a while after multiple resets if the unit is warm (after driving 10-15 minutes). However after leaving the car overnight the WQ_BC8 setting will reverted to the original settings and BT no longer works. Setting the BT adapter back to WQ_BC8 will not work again until the unit is warm. The list of paired BT devices is blank and the unit will not discover any nearby BT devices.
I have tried flashing the unit with a file provided by Eonon (Eonon_kbt2_PX3_7.1(20170830).rar) but that did not make any difference.
Other users have tried upgrading the PX3 to a PX5 but that did not make a difference. This seems to be temperature related - but I do not know which board or module to replace. After searching the forum I have not found any solution to this problem - despite the fact that many users seem to face the same issues.
Attached you will find photos of the board and software setup.
Any suggestions would be greatly appreciated. Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok, so I’ve had this unit for maybe a year or so but contacted wondefoo because I found that my car battery was draining from constant power to the head unit. It’s difficult with the language barrier, but they told me to cut the red cable (this is my photo with their markup).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I cut it, the unit doesn’t power up now. They said it was the canbus so I ordered another one of those…that hasn’t fixed it.
I’m not great at this stuff but any assistance would be appreciated.
They sent me this today. Neither of them look like my wiring loom and and it’s really grainy…I’m confused.
Check that (+12 always) and (acc) are actually correct in your head unit harness. They are likely swapped and incorrect.
Do you use canbus interface.
Also, details of headunit post Android system unit including mcu version.
Thanks for your response.
I asked a bunch of questions to the seller and they just said they’re going to send a new harness - I wonder if they can see that the one I got is not correct…
I’m using a canbus interface.
I don’t have the pin out for the canbus interface or the head unit so I can’t tell which wire is supposed to be where.
It’s running android 10. Seller: Wondefoo (AliExpress).
I’ll grab the version shortly.