Develop Bugs

MCU issues - keylight / sound / button map - need KGL V2.55...

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.

Broken screen and digitizer, enable cast to chromecast with USB keyboard

Hi guys,
I'm in trouble with my OP3T and would really appreciate your help here.
I dropped the phone to the ground and broke the screen and digitizer
I would like to cast the screen to my chromecast to recover my files and maybe later repurpose the phone as a media player through a displaylink adapter.
I have connected a USB keyboard and mouse and can interact with the phone.
Can someone guide me through the steps (keypresses) to enable the cast to my chromecast?

bronderb said:
I'd just buy a new screen on Amazon and install it
Click to expand...
Click to collapse
+1
Just login into your One+ account , demand an RMA, follow the instructions and for around 120 euro you will be all good within 2 weeks with a fully functional phone.

Yeah sure I thought about that but I've been a fool and bought the phone on gearbest, hoping to save a little bit at that time...
As the phone was not bought on the oneplus website, it's a bit tricky for the warranty.
Furthermore, I wasn't aware that it was a model made for the Chinese market so the 4G reception has always been horrible here in Europe.
The local repair shops are asking 160€ or more to replace the screen, it's not worth it especially knowing about the non-existent 4G.

Ok I managed to cast another phone to my chromecast using only the usb keyboard/mouse... but I guess the menu structure is not the same on the OP3T as that doesn't work.
Here is what I have thus far:
- Unlock the phone with fingerprint
- Open the app panel with the mouse (move to the bottom of the screen then drag it up)
- Type "param" > this will filter the list, only the parameters app will remain
- Press TAB twice to highlight the parameters app
- Press ENTER
The next part is tricky but doable:
- Move the cursor at the top right of the screen
- Move the cursor slightly down and left and click on the search icon (you have to fish for it a little bit, but you can hear a "click" once you've succeeded)
- Type "cast"
- Press TAB
- Press ENTER (that brings you to the display menu)
- Go at the bottom (Press the down arrow until you stop hearing click sounds)
- Press ENTER to select the cast menu
- Press TAB to select the chromecast device (only one in my case)
- Press ENTER to start casting
I would be very grateful if someone could try on his OP3T and tell me what differs and what key sequence I should press :good:

Hi bronderb,
Yes stock rom (rooted).
Unlocked bootloader and TWRP if that matters.

ced-2k said:
Hi bronderb,
Yes stock rom (rooted).
Unlocked bootloader and TWRP if that matters.
Click to expand...
Click to collapse
If your version of TWRP has USB-OTG enabled, then you can boot into recovery and use your mouse to take a full backup.
TWRP also enables MTP and you can retrieve the backup to your laptop.

rk2612 said:
If your version of TWRP has USB-OTG enabled, then you can boot into recovery and use your mouse to take a full backup.
TWRP also enables MTP and you can retrieve the backup to your laptop.
Click to expand...
Click to collapse
Except I can't really use the mouse to create a backup in TWRP as I don't see the screen :laugh:
I did recover some files with using ADB while in recovery mode, but I didn't manage to do a full backup.
And that won't help me in re-purposing the phone to play prime video and local media files through a displaylink adapter

ced-2k said:
Except I can't really use the mouse to create a backup in TWRP as I don't see the screen :laugh:
....but I didn't manage to do a full backup.
Click to expand...
Click to collapse
For a full backup, you can create an openrecoveryscript which is recognized by TWRP and upon boot into recovery, TWRP will automatically make a backup as specified in the script and you can pull that over MTP.
Refer: https://twrp.me/faq/openrecoveryscript.html

rk2612 said:
For a full backup, you can create an openrecoveryscript which is recognized by TWRP and upon boot into recovery, TWRP will automatically make a backup as specified in the script and you can pull that over MTP.
Refer: https://twrp.me/faq/openrecoveryscript.html
Click to expand...
Click to collapse
I managed to backup all my data, thanks a lot for your help!

kvanlier said:
+1
Just login into your One+ account , demand an RMA, follow the instructions and for around 120 euro you will be all good within 2 weeks with a fully functional phone.
Click to expand...
Click to collapse
It's cheaper than that. To be more precise it costs 88 EUR. Just sent mine last week

I still would like to reuse the phone as a media center.
If someone can guide me to enable chrome cast or setup a display link adapter without replacing the screen...

[MTCD/E] [PX5] BT Search and connection issues with device name and pin

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!

[Request] mcu.cfg file

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:

i have a zoyoskii tesla android 10, and i need reinstall mcu and android

Hello i have zoyoskii tesla andrid 10 4gb+64rom, for ford mondeo 2007-2010 , the tactil screen fail, I press a button and it recognizes it below or above , inicial it work good, but Android auto dont work well and i went to menu "more", when you see the android options, and i restore to factory, this option was enabled but developer option and the menu factory have password) . When it restore the screen dont know well when you push, or the token its not calibrates, i test with apks and dont work. then i went to menu information, and push in mcu update. The unit dowload a new , but the ac now dont job, the original module ac is behind radio . the firm android is actually.
How i can solve this?

Is it an MTCD/E device?
Post MCU version.
FYI - these units are NOT Android Auto.