Hi All,
I've got a KGL unit for the E46 BMW.
It originally came with MTCB-KGL-V2.55 - on which version everything worked fine (as far as I could tell).
Unfortunately I updated before reading not to update unless you have problems(!).
Now, I'm using KGL-V2.83, and for the most part, things are working fine, but no matter what I set the "keylight" option to in Factory Settings, the button lights are always on.
If I flash back to KGL-V2.55 (with sleep and soundmod from darkleo - only V2.55 I can find), when the keylight option is unchecked, the button lights come on only with the car headlights as they should, but the button map is incorrect, the sound is odd - clicks instead of beeps, and bootup is a pain - it won't boot normally, I have to boot into recovery first then reboot into system.
What I'm after, then, is a MCU version which boots properly, abides by the keylight option, and has working sound - ideally, the original V2.55 MCU version.
Does anyone know anything about this, where I can find the older version, or indeed, if I can get the keylight option working correctly on V2.83?
Cheers
Nick
Did you take a look here? link
Yes, I did - that's where I got the V2.55 darkleo version from. Unfortunately the unit doesn't boot properly.
I've since found a mega.nz dump with loads and loads of MCU versions and have found the original V2.55 and tested - still doesn't function as it should though - specifically the keylight remaining on at all times no matter what the factory setting is and the status of the light switch.
Recently some users including me are having issues with BT Connection, device search, setting device name and making changes persistent.
BT MODULES THAT IT WAS TEST ON:
SD-968 - [HA] [MCU MTCE 2.75] Firmware 20180201 and few earlier = WORKS
MD725 - [??] [MCU ???] Oreo Firmware = DO NOT WORK (According to feedback) LogCat needed to see if Firmware communicate with BT Module at all.
METHOD 1 (SHORTER):
1. Force Stop BT app
2. Clear DATA and CACHE for BT app
METHOD 2 (LONGER):
Here are the steps I've done to make it work.
1. Boot device (restart if it was not in deep sleep)
2. Directly go to system BT settings (drop notification and tap on BT)
3. Set Device name and PIN
4. Press refresh
5. Go to Home Screen (Home Button)
6. Open BT App -> Configuration
7. Name and PIN should be entered now
8. Disable/enable Auto Connect and exit app
9. reenter app and configuration to enable Auto connect
10. Make sure that all previous BT profiles for HU are deleted on phone and that phone is visible for all devices (usually when BT configuration is open device is visible)
11. Try to search for devices. It should fail (it failed for me)
12. Go to factory settings
13. Change BT Device even it is wrong one (I have SD-968 I changed to MD725)
14. Tap Apply -> Exit -> CANCEL on reboot prompt (without doing step 13 there will be no scheduled restart)
15. Reenter Factory settings and set correct BT Module (I have SET SD-968) Tap Apply -> Exit -> and Confirm REBOOT
16. After Reboot Go to BT App and try to search for phone it should be found (make sure it is visible like in step 10)
17. If all is OK you should see the phone and you should be able to use it normally (it worked for me)
Attached pictures of some steps for METHOD 2.
NOTE: I'm ATM at HA 6.0.1 Firmware from 20180201 and issue happened after upgrade. Also from what I see Users have same issue with and after Oreo update. Hope I helped
Thanks for the info. Have you tried this method also for oreo rom as well ?
A step that worked for me was to clear data and cache for bluetooth app..
julien_blanche said:
Thanks for the info. Have you tried this method also for oreo rom as well ?
Click to expand...
Click to collapse
Haven't updated to Oreo yet.
Phycopat said:
A step that worked for me was to clear data and cache for bluetooth app..
Click to expand...
Click to collapse
Good point it didn't worked for me but, it can also help. Added to main post.
You can trigger a reboot with "hctreboot" in factory settings. Does that work instead of doing steps 12-15?
I definitely have the BT issue. I have an Xtrons(GS) MTCD/E PX5 Oreo and an Xtrons brand OBDII. They won't talk or disconnect. I'll try this tomorrow morn and report back.
jdisco1 said:
You can trigger a reboot with "hctreboot" in factory settings. Does that work instead of doing steps 12-15?
I definitely have the BT issue. I have an Xtrons(GS) MTCD/E PX5 Oreo and an Xtrons brand OBDII. They won't talk or disconnect. I'll try this tomorrow morn and report back.
Click to expand...
Click to collapse
I have same GS MTCE 2.75 PX5 OREO but an old OBD2, give HU same password as OBD2 adapter..
jdisco1 said:
You can trigger a reboot with "hctreboot" in factory settings. Does that work instead of doing steps 12-15?
Click to expand...
Click to collapse
Point of 12-15 is that HU re init Module itself along with software. Not sure if it works that way on MTCD/E but usually it works on modular systems.
Tried with PX5 oreo installed with no luck. Both methods are not working for me.
PekeMM said:
Haven't updated to Oreo yet.
Click to expand...
Click to collapse
What???(I thought that this was a trick for oreo)
In my unit BT(MD725) works without any tricks for MM.
I tried your trick with 2 kinds of oreoROM(HA and GS) but BT did not work.
Thanks anyway
I'm sorry, but as I wrote I have SD-968 BT module not MD725. I'll update main thread with so far know to work devices.
Any news?
JonatanP said:
Any news?
Click to expand...
Click to collapse
Not that I know, I'll be back from Trip on Sunday, so I hope I'll finally finish the tests and upgrade to Oreo in April.
seems to be the same
The solution is to go back to android 6, the problem is that it is not as fluid in my case as android 8.
Hi, same problem here....
I can not use my ODB2 connector on my Android 8 radio either.
Is there an adapter that works?
Is there a trick to make it work?
Greetings and thank you!!
Hi..any update on how to get the bluetooth working on android 8..
Mtcd ksp px5
warata said:
What???(I thought that this was a trick for oreo)
In my unit BT(MD725) works without any tricks for MM.
I tried your trick with 2 kinds of oreoROM(HA and GS) but BT did not work.
Thanks anyway
Click to expand...
Click to collapse
if you still have android 8 installed, try going to factory setting and change the BT Device even it is wrong one (anything other then MD725) tap apply and exit and reboot.
after reboot change the BT device back to the original one (MD725) tap apply and exit and reboot.
after reboot go to the system BT and try to search if the phone name appears let me know.
i still didn't try the above method on android 8, but if anyone with MD725 module is still using android 8 please try and update us.
thanks
i was having problem with bt too...
here you can read my post https://forum.xda-developers.com/showpost.php?p=77525417&postcount=791
now i have Oreo Rom in a px5 board (32+4) with MD725 BT module working well
macoloco said:
i was having problem with bt too...
here you can read my post https://forum.xda-developers.com/showpost.php?p=77525417&postcount=791
now i have Oreo Rom in a px5 board (32+4) with MD725 BT module working well
Click to expand...
Click to collapse
Thanks, you said in that thread ".i have found a directory where all manufactures update.zip where listed
Go there , pickup last LM version" could you say where this directory is? Once there what do you do with that file?
bjt2 said:
Thanks, you said in that thread ".i have found a directory where all manufactures update.zip where listed
Go there , pickup last LM version" could you say where this directory is? Once there what do you do with that file?
Click to expand...
Click to collapse
i wrote all my procedure here
https://forum.xda-developers.com/showpost.php?p=77525417&postcount=791
and here
https://forum.xda-developers.com/showpost.php?p=77538182&postcount=796
Dasaita MMCNP - BT connection problem
Hi, I have Dasaita HA2106-V840-8 a problem with Bluetooth connectivity. First time I managed to connect my phone to Dasaita MMCP (car_kit), but after a few days the devices failed to connect. I guess my device has embedded SD968 BT chip, in accordance with the description.
When I enter the name of the device and new PIN in BT settings, and then turn on finding the device, they are not visible to each other. I tried this other day too, but when I turned MMCP, entered settings was gone (not memorized). No name, no PIN, but also there is no connection. Search doesn't have results. At the end I tried to unpair devices and pair them again, but I get a message on my phone "Unable to communicate with CAR_KIT".
When I entered in settings for BT (settings/car/factory setting/application-choose...) it was set to WQ_BC6. And then I tried to set up SD_BC6, reboot, search BT, nothing was found again. Then I returned to WQ_BC6, reboot, search BT, without success. In the end, I tried to set up SD968, but it's not worth it anyway, MMCP does not see a mobile phone. I also tried several phone models without success. I also went to the BT application and clear data and cache, but always the same thing - BT devices do not see each other. I'm not even sure BT is ON because it doesn't have a special slider to move On/Off.
What should I do? Please help me!
Hi everyone,
I have a problem with my HU... the knob volume and knob seeking not working in rotation ways. Working only if it's pushed(mute and back). I read almost everything on this forum related with this. Also I already posted the problem here and today I had some time to spent and I tried to solve this issue but without any luck. What I have done? I tried to reset button panel from key study, I tried to reflash with old mcu.img, new mcu.img, patched mcu.img, to flash with an empty mcu.cfg (0bytes), also I've tried with another rom(rooted one) to insert command manually to assign keys code ( am broadcast -a com.microntek.irkeyDown --ei keyCode XXX )... nothing changed.
After all these attempts I came up with an idea, to flash my mcu with a mcu.cfg from you. Maybe will work...
So, here is my requires, to helping me with this cfg file, saved by you from your good working HU. also I'll need mcu.img to flash same versions as your HU on mine. Or at least to tell me your version of mcu and I'll search it.
Now, my HU it's a MTCD MX with physical buttons (for VW car). So I need your exported dmcu.cfg from your mtcd mx HU.
!!!An advice for you, those who want to helping me, Do not ever ever choose "hardware key study" and assign one, just for play or curiosity, if you pushed, just go back. Don't "save and exit"!Because in this way you will lose the settings for all physical buttons... and you have to assign manually, but the knob rotations can't be assigned anymore. Like this I lost the knobs functions. That's it!
Thanks a lot my friends!
Solved
Finally solved! How?!...
In factory settings > other settings > knob mode it was a wrong setup "IO ports". I entered here and I saw there are few types of settings. And because i don't know what they means, I've tested "2 10k/20k ADC" and BINGO...both knobs works again.
Most likely was my fault for that wrong setup from knob mode... I don't remember when I've changed but doesn't matter now... new setup solve my issue!
Hi There, I'm about to update my HU and wanted to know how to export my current settings. Is there an APP you install?
Never mind I found it in the car setting under "Factory Settings" my password was m123456, I'm running a MTCE_HT. I've seen where another password could be 212121.
ozzyboy said:
Finally solved! How?!...
In factory settings > other settings > knob mode it was a wrong setup "IO ports". I entered here and I saw there are few types of settings. And because i don't know what they means, I've tested "2 10k/20k ADC" and BINGO...both knobs works again.
Most likely was my fault for that wrong setup from knob mode... I don't remember when I've changed but doesn't matter now... new setup solve my issue!
Click to expand...
Click to collapse
thanks , your solution saved me! :good:
Hello all,
After finally updating my PX5 to the latest MCU and firmware (according to Hall9k) using his mod application, I am now experiencing low volume on everything (radio on max is pretty low volume when you're on the highway) and bluetooth settings always reset to empty settings and will not find my phone and my phone will not find the PX5.
I've tried resetting wifi and bluetooth settings, no luck. I've tried resetting the unit back to factory settings, erasing all data, no luck. I found a post regarding the bt issue and followed all his steps (changing the bt device and reverting back to it, etc.) but no luck. I found a post which said the device somehow needed to be an other one than previously set, so I've tried all the devices in the list, but no luck. Only at the parrot device, the bt settings were automatically reverted back to factory default (Car... something), but it wouldn't connect. Normally my device was on SD-968 I believe (not currently in my car).
So, that's my main issue now. How can I get BT to connect, without rolling back to Android 6.0.1? Because on 6 it worked.
And second, how can I get the volume louder? Again, after updating the volume somehow seems limited.
I don't want to go back to 6, if there's an other way, because 6 had its own problems...
I'm really lost here and have spend many hours in the car, trying everything I could find online (even manually clearing cash and storage of the bt settings, etc). There must be a way this should be fixed.
My Android 9 fw is from November (Hal9k send that one to me)
My MCU is MTCE_GS_V3.17bd_3
Ever since i had this unit, i have updated the MCU from LM 2.7x to HA 3.x to current HA 3.40.
I also changed the system software from LM to HA with the latest OTA updates to.
No matter what i do, for the DAB+ and TPMS devices, everytime I restart i have to re-select "Use by default" per the screens attached.
The apps do have system access allowed permissions.
gwaitsi said:
Ever since i had this unit, i have updated the MCU from LM 2.7x to HA 3.x to current HA 3.40.
I also changed the system software from LM to HA with the latest OTA updates to.
No matter what i do, for the DAB+ and TPMS devices, everytime I restart i have to re-select "Use by default" per the screens attached.
The apps do have system access allowed permissions.
Click to expand...
Click to collapse
i never did get this sorted. anyone have any ideas