[jkont]

Originally Posted by Kri

Unfortunately moving the Controler down`is not "keypad-down" by default, a mcu update will also not change this behavior as it is intention to (not) work this way by the engineers.

Kri

Originally Posted by Kri

Unfortunately moving the Controler down`is not "keypad-down" by default, a mcu update will also not change this behavior as it is intention to (not) work this way by the engineers.

Kri

Why they did this ?
They should change it. The "up" works , why not the "down" movement ?
I cant' figure out their thought.

[Kri]

Originally Posted by jkont

Why they did this ?
They should change it. The "up" works , why not the "down" movement ?
I cant' figure out their thought.

We also can`t figure out their thoughts, its just how it is ever since

Kri

[Kri]

Hello guys, good news

It has been found out by the amazing guy`s at discord, that you can connect other (non phone) Bluetooth devices at some Headunit via a workaround !

PLEASE READ THE ENTIRE GUIDE CAREFULLY BEFORE APPLYING !

It seems that the Bluetooth module is not blocked at Beginning by KSW_BT, this does happen as soon as some KSW App does want to access the Bluetooth modul.
So you need to hurry a little bit, because when you take too long KSW_BT will block the device again, this will also happen even when "BT" at Factory settings is disabled.

Please note that it also does seem that this procedure does not work on every headunit.
For example i can connect BT devices on my 4/64 1920p Headunit, but not on my 2/32 1280p Headunit, both running 2.1.0.
Its also not known at the moment if this workaround was already functional since ever or since a specified build version.

• First of all you need to disable "BT" at Factory Settings , therefore it is not possible to use KSW Bluetooth and Full-Bluetooth at the same time !
  
• Then ensure that BT App does not autostart anymore when starting the headunit.
  To do for example start music or video player, and then do a reboot at Factory-Settings "Profile import", it should then autostart that payer.
  

so lets start:

1. Go to settings Menu and select "Connected devices"
   
   
   
2. Click on the Search icon
   
   
   
3. Search for "rec", wait a little bit until "Files received via Bluetooth" does appear, click on it
   
   
   
4. click on Bluetooth
   
   
   
5. Bluetooth is now disabled
   
   
   
6. Enable bluetooth and wait until the Device name "QCOM-BTD" does appear !
   If the device will not show up, then either your "BT" Setting at factory setting is not disabled, or you have not been fast enough and KSW_BT has taken over control, then you have to reboot your device and start from beginning.
   Now enable Bluetooth pairing of your desired device!
   If the Device has been found click on "Pair new devices"
   
   
   
7. Let the device find (in my case TouchAI Mouse/KB) and click on it.
   If your device will connect then the menu should jump back to the View which is shown on Picture 6.
   If it will stuck at "Pairing" or will stay at this page after some then unfortunately pairing does not work for your device, please check Point 9
   
   
   
8. You can now see the connected devices at Picture 2 "connected devices" , please note that also a small Bluetooth icon does appear at the taskbar.
   
   
   
9. When you have tried it please post your results in the following form:
   
   
   • Headunit MCU Version:
   • Android Version installed:
   • System Memory config.:
   • Device tried to connect:
   • Bluetooth Connection successful:
   • Comment:
   
   For example my results:
   
   Headunit MCU Version: 105245dLS-CIC-GTL-DC-200722
   Android Version installed: Android 10 2.1.0
   System Memory config.: 4GB / 64GB
   Device tried to connect: TouchAI Ai01 , BMW Performance Analyser
   Bluetooth Connection successful: yes
   Comment: BMW Performance Analyser only running ODB2 Data, no G-Sensors.
   
   Headunit MCU Version: 023052dGS-CIC-GTL-191127-B18
   Android Version installed: Android 10 2.1.0
   System Memory config.: 2GB / 32GB
   Device tried to connect:TouchAI Ai01
   Bluetooth Connection successful: no
   Comment: does find the device and start "pairing" but does not connect
   

Please also do the last number and post your results, so we maybe can find out any hints why it does work on some units and why not !


And here an example of the TouchAi working:

View post on imgur.com

Kri

[mbonus]

Headunit MCU Version: 023055dGS-NBT-GTH-DC1-200709
Android Version installed:Android 10 v2.0.9
System Memory config.: 4GB / 64GB
Device tried to connect: BAFX OBDII
Bluetooth Connection successful: Yes
Comment:

[Frankly30]

Headunit MCU Version: 023055dGS-NBT-GTH-DC-200702A
Android Version installed:Android 10 v2.1.0
System Memory config: 4GB / 64GB
Device tried to connect: EXZA HHOBD
Bluetooth Connection successful: Yes
Comment: Bluetooth device shows up in the list. However it refuses to pair. After having entered the pin nothing happens. Turning on and off bluetooth and trying to pair again it just does nothing. Bluetooth icon does not show up on the topbar.
EDIT: It doesn't say it's connected, but opening any OBD analyser app shows my OBD Bluetooth on the list. It does work just doesn't say it's connected in the settings app!

[Kri]

mbonus Frankly30 , i have added the Line "System Memory config" , would appreciate if you could update your informations with that line

Sincerely Kri

[Ericokta]

Originally Posted by Kri

.rar is a file archive, you need to unpack the file using winrar to get the ksw_mcu.bin, thats the file that has to be put on the thumbdrive.

Here you have the latests File for your system:

Attachment 2419345

Don`t forget to unzip it !

Kri

Thank you Kri

I will try later

[F20_M135i]

Hello Kri, great discovery

And if we tried to "freeze" the application KSW_BT ??

I am on Android 9 and root, I can try via TitaniumBackUp (mcu from 2019 ALS for me)

[RedErik]

Headunit MCU Version: 415187dLZH-CCC-GTL-200617-B18
Android Version installed: Android 9 v3.9.8
System Memory config: 4GB / 64GB
Device tried to connect: PIXEL 4XL
Bluetooth Connection successful: No
Comment: No Bluetooth settings at all on Android 9.

Headunit MCU Version: 415187dLZH-CCC-GTL-200617-B18
Android Version installed: Android 10 v1.2.0
System Memory config: 4GB / 64GB
Device tried to connect: PIXEL 4XL
Bluetooth Connection successful: No
Comment: Phone manged to find HU and vice versa, but BT was always disconnected 1sec after pairing PIN code popup.

Headunit MCU Version: 415187dLZH-CCC-GTL-200617-B18
Android Version installed: Android 10 v2.1.0
System Memory config: 4GB / 64GB
Device tried to connect: PIXEL 4XL
Bluetooth Connection successful: No
Comment: Phone manged to find HU and vice versa and both devices seemed to accept PIN code. Phone displays HU as saved device. Connection doesn't last longer than 1sec.

[rao83]

hi all,

Need help to patch my mcu file. bought this android player from mekede but very poor response from them. I read earlier post that the MCU need to be patch so that it can be used in OEM menu.

Idrive is not working in oem screen but it does in android menu.

MCU ver: 023052dGS-CCC-GTL-191127-B18

https://mega.nz/file/Z6xWXTYC#ncDlUt...Ae3JqTJVVSs_SU

[rao83]

but for e60 the idrive in oem still doesn't work. "flap" originally set to not active.

Originally Posted by Girder82

Good point. Sadly the buttons on the wheel are configured via iDrive in the OEM Screen as well.
Really think we need an MCU Upgrade for all those Flap Display Owners.

Thx
Girder

[RedErik]

A small update on my testing:

Headunit MCU Version: 415187dLZH-CCC-GTL-200617-B18
Android Version installed: Android 10 v2.1.0
System Memory config: 4GB / 64GB
Device tried to connect: XBOX Bluetooth controller
Bluetooth Connection successful: YES
Comment: It just works... guess I'm ready to play some GAMES! Xbox pass or whatever it's called might be an option here

[EvntHrzn]

Headunit MCU Version: 023055dGS-NBT-GTH-DC1-200709
Android Version installed: Android 10 2.1.0
System Memory config.: 4GB / 64GB
Device tried to connect: Xbox Controller (just first device I had on hand)
Bluetooth Connection successful: YES

Comment: While the connection was successful and functioned to control even the android menus, it rendered my carplay external dongle (sold by Avin) unstable and unusable (known as AutoPlayBox, aka "Carlink Autokit", and internally to the system as "cn.manstep.phonemirrorBox").
The dongle constantly lost connection to the phone, whether it was plugged in or via wireless carplay.

[fredy3330]

Headunit MCU Version: 023052dGS-CIC-GTL-191127-B18
Android Version installed: Android 10 V 2.1.0
System Memory config: 4GB / 64GB
Device tried to connect: VGATE ICAR PRO OBD BLUETOOTH 3.0
Bluetooth Connection successful:YES
Comment:CONNECTED AND STAYING CONNECTED AFTER EVERY REBOOT!!!
At the begining didn't work. When typing "rec" nothing happened.
Changed the language to english and the "Files received via
Bluetooth" appeared. Thank you

[F20_M135i]

Hello,
I allow myself a warning about the BT connection:
Even if you manage to connect a bluetooth adapter, ESPECIALLY DO NOT PROGRAM YOUR ECUs with it! You could brick your system (the end "reset" for erasing errors is a real risk)
Opinion of an encoder

[mike78]

Anyone with navifly android10 and dvr adas camera?

[fredy3330]

Originally Posted by F20_M135i

Hello,
I allow myself a warning about the BT connection:
Even if you manage to connect a bluetooth adapter, ESPECIALLY DO NOT PROGRAM YOUR ECUs with it! You could brick your system (the end "reset" for erasing errors is a real risk)
Opinion of an encoder

Hi,I just use this app with Bluetooth for monitoring. For anything more I use ista with laptop and wired connection. Thank you.

[F20_M135i]

Hello my friend !

I do the same thing to display the temperature gauges for example, but as some of these software also offer the deletion of "fault codes", I preferred to warn everyone



HAVE A GOOD DAY !

[haibn92]

Originally Posted by Kri

Hello guys, good news

It has been found out by the amazing guy`s at discord, that you can connect other (non phone) Bluetooth devices at some Headunit via a workaround !

Kri

Hello Kri,

Thank you for your finding. BT is always a weakness for this kind of HU.

Following your instruction, I can understand that the pre-condition is to disable BT in factory-settings right ? It means for Android 8 & 9, it'll not working as there is not a switch for enable/disable BT ?

[steslatt]

So I tried to update chrome through the play store and it wouldn't update, clicking update did nothing. I uninstalled and tried reinstalling but it won't reinstall now either. Any ideas how to get it back? Can I push the app with ADB? If so what's the target location or better yet if someone knows the full command?

EDIT: Never mind, it came back after a reboot. Still can't be updated via the play store though, is this normal?

[EvntHrzn]

Originally Posted by haibn92

Hello Kri,

Thank you for your finding. BT is always a weakness for this kind of HU.

Following your instruction, I can understand that the pre-condition is to disable BT in factory-settings right ? It means for Android 8 & 9, it'll not working as there is not a switch for enable/disable BT ?

Not answering for Kri, but when I posted my findings I forgot to mention that toggling BT in the factory settings had no bearing on my ability to follow Kri's instructions to connect devices via Bluetooth.

I can leave it checked or unchecked, and I'm still able to connect the Xbox controller. I don't know if this is unique to only some headunits such as mine.

[Wireless]

Originally Posted by mike78

Anyone with navifly android10 and dvr adas camera?

I'm