Database Info

KIA MTCE px5 unit... bluetooth issues

Just bought a unit specifically for my Kia.
Its an OctaCor PX5 MTCE unit [based in what I've read MTCE and MTCD are the same, right?]
Everything works well with the unit except bluetooth. It won't discover or connect to any device. The device name and password fields in the BT menu are blank. When I change those fields and add something, it doesn't make a difference. Its just constantly "searching"
I've explored all of the differenr BT optiona in factory settings menu and ive tried installing BT managers from the play store and they don't work either.
I can't seem to find anyone else having this problem.
No matter what phone or tablet I use, it doesn't discover it.
What could the problem be?
{
"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"
}
Sent from my SM-G925T using Tapatalk

j2gifted said:
Just bought a unit specifically for my Kia.
Its an OctaCor PX5 MTCE unit [based in what I've read MTCE and MTCD are the same, right?]
Everything works well with the unit except bluetooth. It won't discover or connect to any device. The device name and password fields in the BT menu are blank. When I change those fields and add something, it doesn't make a difference. Its just constantly "searching"
I've explored all of the differenr BT optiona in factory settings menu and ive tried installing BT managers from the play store and they don't work either.
I can't seem to find anyone else having this problem.
No matter what phone or tablet I use, it doesn't discover it.
What could the problem be?
View attachment 4384130View attachment 4384131View attachment 4384132
Sent from my SM-G925T using Tapatalk
Click to expand...
Click to collapse
The behaviour you describe is what I see if the wrong BT module is selected in the factory settings. If you have tried each BT module type, rebooted and then tried pairing via the BT app (not the BT settings) then its possible the BT module is faulty I guess?
Andy

ADB100 said:
The behaviour you describe is what I see if the wrong BT module is selected in the factory settings. If you have tried each BT module type, rebooted and then tried pairing via the BT app (not the BT settings) then its possible the BT module is faulty I guess?
Andy
Click to expand...
Click to collapse
+1

ADB100 said:
The behaviour you describe is what I see if the wrong BT module is selected in the factory settings. If you have tried each BT module type, rebooted and then tried pairing via the BT app (not the BT settings) then its possible the BT module is faulty I guess?
Andy
Click to expand...
Click to collapse
I'm going to go back and try each one again.
How can I find out which adapter is in the unit?
Also, are the BT modules easy to replace... OR is there an option to add a new one via USB input?
Sent from my SM-G925T using Tapatalk

j2gifted said:
I'm going to go back and try each one again.
How can I find out which adapter is in the unit?
Also, are the BT modules easy to replace... OR is there an option to add a new one via USB input?
Sent from my SM-G925T using Tapatalk
Click to expand...
Click to collapse
I am not sure if its something that can be replaced as its either directly on the MCU board or a module soldered to it. I am sure if you post some pictures of the internals someone will be able to identify it for you.
I would try each one in the factory settings followed by a reboot and then test with the BT app.
I think several people have tried USB BT modules without success. BT is a bit of an odd one as Android isn't natively aware of the BT module in these units like a phone or tablet is. The BT utilities are propietary to the hardware and aren't the built-in Android ones.
Andy

ADB100 said:
I am not sure if its something that can be replaced as its either directly on the MCU board or a module soldered to it. I am sure if you post some pictures of the internals someone will be able to identify it for you.
I would try each one in the factory settings followed by a reboot and then test with the BT app.
I think several people have tried USB BT modules without success. BT is a bit of an odd one as Android isn't natively aware of the BT module in these units like a phone or tablet is. The BT utilities are propietary to the hardware and aren't the built-in Android ones.
Andy
Click to expand...
Click to collapse
Figers crossed that going through the settings again works.
If not, I'll have to find the energy to pull the radio out and take pics of the inside
Sent from my SM-G925T using Tapatalk

This seems to be a Klyde (KLD) unit. I would put my bets on MD725 Bluetooth module type.
Do you remember what it was initially set to?
I guess you probably did the same mistake as most users do the first time. They try to pair Bluetooth devices using Android Bluetooth settings menu. This does NOT work with MTCD/MTCE units since Bluetooth is controlled by MCU. Neither do any of the Bluetooth management apps in Play store work.
You need to use the Bluetooth application which is installed on your head unit. It might be called "Bluetooth" or "Phone". On my KLD stock firmware it does have the green phone icon. Open the app and use it to pair your Bluetooth device (not only phones).
If it's not an MD725 my next bet would be SD968 Bluetooth module.

I've gone through every BT option in factory settings. The one thatbwas selected by default was the BC5 unless it was accidentally changed.
I'm using the stock bluetooth app to connect..
Still no luck..
Any other suggestions?

Stock bluetooth app
Sent from my SM-G925T using Tapatalk

Factory settings bluetooth options
Sent from my SM-G925T using Tapatalk

Bluetooth pairing screen constantly searching
Sent from my SM-G925T using Tapatalk

Here is the link to the radio I purchased..
If the listing is correct, the BT module is 7OC-MD-705... i think?
http://vi.raptor.ebaydesc.com/ws/eB...5&pm=1&ds=0&t=1514445690000&ver=0&cspheader=1
Sent from my SM-G925T using Tapatalk

I confirm you're in the right app.
Did you try selecting MD725 module in factory settings and rebooting the unit? Then try again.

I had a problem with pairing the bluetooth module SD968. I bought on aliexpress the USB device. I installed factory settings in the BT section type-MD725. I have connected the device COMFAST Bluetooth4.0 + wifi 150 Mbps Wi-Fi Dongle RTL8723BU to the USB input DASAITA. The device overloaded, bluetooth and Wi-Fi started to work perfectly.
---------- Post added at 20:42 ---------- Previous post was at 20:35 ----------
I shot the video in two parts: the first part, when Bluetooth is not included. This is the device status within 8 hours in sleep mode. The second part of the video as the bluetooth on the device after five hours, the device is in sleep mode.
This description of my problem, which I have given to the seller DASAITA : this is the first part of the video. Bluetooth is not working. The beginning of the video shooting is 7 hours and 8 minutes. After the last switch it took more than 5 hours. https://youtu.be/GOzM5bw9Z1E.
This is the second part of the video. Bluetooth working. Time is 19 hours and 46 minutes. After the last turn on the device, it took less than 5 hours. Turned on the device in 7 hours 04 minutes - Bluetooth not working. The device is switched on 11 hours 38 minutes-works bluetooth. The device is turned on 13 hours and 23 minutes-works bluetooth.
The device is switched on, in 16 hours 57 minutes-works bluetooth. The device is included in 19 hours 46 minutes-works bluetooth.
https://youtu.be/u47527OJYQg

Here are the pics of the inside of the unit... not sure where bluetooth adapter is
Sent from my SM-G925T using Tapatalk

SkyBeam2048 said:
I confirm you're in the right app.
Did you try selecting MD725 module in factory settings and rebooting the unit? Then try again.
Click to expand...
Click to collapse
Yes, I went through each selection and restarted everytime and nothing changed.
Sent from my SM-G925T using Tapatalk

j2gifted said:
Here are the pics of the inside of the unit... not sure where bluetooth adapter is
Click to expand...
Click to collapse
The bluetooth chip is right next to the point where the black cable (antenna) is soldered too. In fact there are two antenna soldering points there where your unit only has one antenna equipped. I can't read it on the chip but I think I can possibly spot the Realtek logo on it. Have a close look at the chip to the left of your PX5 SoM where the antenna is soldered to the board. I compared it to pictures I made from my one. The board layout of my KLD unit seems to be identical. However my Bluetooth chip is square, yours is rectangle shape. Take a close-up picture of the chip where the antenna is soldered to the board. It might be either Realtek RTL8723bu (which is MD725) or it's the SD-968 chip.
What I am not sure about is whether the module uses antenna diversity and/or which antenna is used for Bluetooth. My unit actually got antennas solered on both antenna connection points, yours only has one on the lower one. So perhaps it's an antenna issue which would explain why you don't get any connection.

KIgorM said:
I had a problem with pairing the bluetooth module SD968. I bought on aliexpress the . I installed factory settings in the BT section type-MD725. I have connected the device COMFAST Bluetooth4.0 + wifi 150 Mbps Wi-Fi Dongle RTL8723BU to the USB input DASAITA. The device overloaded, bluetooth and Wi-Fi started to work perfectly.
Click to expand...
Click to collapse
Excuse me KIgorM, can you tell me if with this adaptor you can pair other devices (not only phone, obd)? And wifi and bluetooth performances are better now than with internal chip?
Thank you in advance

jimbover said:
Excuse me KIgorM, can you tell me if with this adaptor you can pair other devices (not only phone, obd)? And wifi and bluetooth performances are better now than with internal chip?
Thank you in advance
Click to expand...
Click to collapse
Hi. I haven't tried other devices via Bluetooth and Wi-Fi to connect to the multimedia device. The voice quality when talking on the phone via bluetooth better than the module SD968.

SkyBeam2048 said:
The bluetooth chip is right next to the point where the black cable (antenna) is soldered too. In fact there are two antenna soldering points there where your unit only has one antenna equipped. I can't read it on the chip but I think I can possibly spot the Realtek logo on it. Have a close look at the chip to the left of your PX5 SoM where the antenna is soldered to the board. I compared it to pictures I made from my one. The board layout of my KLD unit seems to be identical. However my Bluetooth chip is square, yours is rectangle shape. Take a close-up picture of the chip where the antenna is soldered to the board. It might be either Realtek RTL8723bu (which is MD725) or it's the SD-968 chip.
What I am not sure about is whether the module uses antenna diversity and/or which antenna is used for Bluetooth. My unit actually got antennas solered on both antenna connection points, yours only has one on the lower one. So perhaps it's an antenna issue which would explain why you don't get any connection.
Click to expand...
Click to collapse
So I actually got it working. I noticed that the BT module appeard to be bent and loose. So i straightened it out and pushed the contact points bck in the board the best I could, and that did the trick.
Part of the board was chipped too in the same area.. i believe a screw or something may have hit it as it was right near a hole.
The only problem I have now is that sometime [every few days] the unit will appear to forget my steering wheel settings. When I open the key study, the selections are there but not working... so I have to set them again... why is that?
Sent from my SM-G925T using Tapatalk

Help Understanding Bluetooth MCU and Android Interaction

Hi,
So after having a bit of a read of the MTCD forums I have gathered that both bluetooth handsfree and bluetooth music playback are handled by the MCU but use Android companion apps to control what the MCU does. For OBD I am a little unsure but some are suggesting that the MCU looks for the "OBD" device name and forwards data to the MCU?
So what I have gathered from this is that because the MCU handles bluetooth, so this limits what you can do with bluetooth on these android HUs (so no bluetooth tethering ect...).
Or is it that android has full access to the bluetooth module but the developers of these units haven't implemented many profiles in their bluetooth stack? In this case, is the bluetooth module connected to both the MCU and the Android board?
Thanks!

zubin3333 said:
Hi,
So after having a bit of a read of the MTCD forums I have gathered that both bluetooth handsfree and bluetooth music playback are handled by the MCU but use Android companion apps to control what the MCU does. For OBD I am a little unsure but some are suggesting that the MCU looks for the "OBD" device name and forwards data to the MCU?
So what I have gathered from this is that because the MCU handles bluetooth, so this limits what you can do with bluetooth on these android HUs (so no bluetooth tethering ect...).
Or is it that android has full access to the bluetooth module but the developers of these units haven't implemented many profiles in their bluetooth stack? In this case, is the bluetooth module connected to both the MCU and the Android board?
Thanks!
Click to expand...
Click to collapse
The disadvantage that non Intel based headunits experience, is that the bluetooth module is hooked up via a serial link (hooked up to the MCU... So Android has to talk to the MCU, then the MCU talks to the Bluetooth module). On the intel units, like most Android phones, the Bluetooth is on the SoM (or wifi SoM) which interfaces in a differently, and more direct way. There is a shim between the Bluetooth module,mcu and Android, sending the commands via a serial link. It's messy because the developers have only slowly improved it.

gtxaspec said:
The disadvantage that non Intel based headunits experience, is that the bluetooth module is hooked up via a serial link (hooked up to the MCU... So Android has to talk to the MCU, then the MCU talks to the Bluetooth module). On the intel units, like most Android phones, the Bluetooth is on the SoM (or wifi SoM) which interfaces in a differently, and more direct way. There is a shim between the Bluetooth module,mcu and Android, sending the commands via a serial link. It's messy because the developers have only slowly improved it.
Click to expand...
Click to collapse
Ahh I see! I noticed some people on the forum have commented on plugging in a Comfast USB dongle into their unit and it ended up working. Would this have any advantages, or increase the feature set?
Thanks

gtxaspec said:
The disadvantage that non Intel based headunits experience, is that the bluetooth module is hooked up via a serial link (hooked up to the MCU... So Android has to talk to the MCU, then the MCU talks to the Bluetooth module). On the intel units, like most Android phones, the Bluetooth is on the SoM (or wifi SoM) which interfaces in a differently, and more direct way. There is a shim between the Bluetooth module,mcu and Android, sending the commands via a serial link. It's messy because the developers have only slowly improved it.
Click to expand...
Click to collapse
Um, actually... ALL bluetooth hooks up to the CPU using a serial link (including the one in your cell phone). This is absolutely normal. It looks weird to some people that its sitting on a different board than the CPU, and given how poorly they work, this weird look has been *blamed* for poor performance, but there is nothing more to it. In fact, bad bluetooth performance on all the chinese radios really just comes down to bluetooth being way too complicated for the feeble minded programmers that they hire.
Now some bluetooth devices also have i2s audio hooked up to the CPU. I don't think any of the chinese radios have this (even the ones with intel). The mtc's, if I remember correctly, actually have analog audio hooked from the bluetooth module to their BD37xx, which is where the MCU controls will kick in (because mtc has the BD37 control hooked to the MCU whereas the intel ones have the BD37 hooked up to the CPU). This is actually a lot *better* than the intel units for one reason -- the intel's don't have ANY audio lines hooked up to anything. Not analog, and not digital. They run their SCO over HCI (serial), which is why the SCO usually doesn't hook up on them at all. Not that SCO can't be run over HCI, but that Android doesn't have working code to do this, which means that they had to butcher the heck out of Android to get that to work, and you already know how bad they are at writing software.

luciusfox said:
Um, actually... ALL bluetooth hooks up to the CPU using a serial link (including the one in your cell phone).....
In fact, bad bluetooth performance on all the chinese radios really just comes down to bluetooth being way too complicated for the feeble minded programmers that they hire.
..... which means that they had to butcher the heck out of Android to get that to work, and you already know how bad they are at writing software.
Click to expand...
Click to collapse
Except for the MD725, which is actually an integrated BT and WIFI RTL8723BU chipset connected directly to the SOM via USB.
This would suggest, and agree with you, that the BT stack is butchered.
Similar inexperienced mistakes can be seen in the hardware, such as OTG switch (which doesn't because it's connected in parallel to the USB hub IC), parallel mic connection.
Fortunately, the PSU looks quite robust, perhaps directly from manufacturer design notes.
**Correction - 11/Mar/18 -. Appears that some manufacturers have corrected the USB switch issue as atleast one member has OTG without modification.

Handsfree
So I found what I think is the pinnout for the MD725 board in these HUs. I can see a PCM_IN and a PCM_OUT which I would believe would be for the handsfree microphone and the handsfree audio output respectively. And I think @luciusfox was suggesting that these audio signals are not touched by the CPU at all. And I guess there is no need for them to be either. I only wonder how the people that had success in plugging in an external USB MD725 dongle managed to get sound working if the headunit relies on the PCM lines for audio.
So do you guys think that the BT stack will be improved by someone or is the interest too low and or are there other large barriers for entry for this?
{
"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"
}

zubin3333 said:
So I found what I think is the pinnout for the MD725 board in these HUs. I can see a PCM_IN and a PCM_OUT which I would believe would be for the handsfree microphone and the handsfree audio output respectively. And I think @luciusfox was suggesting that these audio signals are not touched by the CPU at all. And I guess there is no need for them to be either. I only wonder how the people that had success in plugging in an external USB MD725 dongle managed to get sound working if the headunit relies on the PCM lines for audio.
So do you guys think that the BT stack will be improved by someone or is the interest too low and or are there other large barriers for entry for this?
Click to expand...
Click to collapse
This isnt the MD725 found in GS/MTCD units. MTCD Module has 7 Pins:
1 = +3.3v
2 = USB DM
3 = USB DP
4 = GND
5 = GND
6 = ANT
7 = ANT
As the USB Dongle tests and schematic indicate, no PCM lines, all over USB. Per my post, MD725 doesnt use MCU, all via Android.

External volume knob button mapping

Hi all! Recently got an Android 8.0 based GS (XTRONS) unit, the TE706PL.
The main issue that I have with the unit is that it does not have a physical volume knob. I was OK with this when I purchased it as I planned on adding in my own. I have used an Arduino and a rotary encoder to 'replicate' a HID volume knob.
This is able to adjust the volume on my computer as well as on my Oneplus 3T with an OTG adaptor. However, when connected to the head unit, it does not work. I also tried connecting a standard USB keyboard to the headunit and found that all the keys work, including media play/pause keys, except volume up, down and mute do not function.
On the head unit, I used this app: https://play.google.com/store/apps/details?id=innerlife.keyboard.multilanguagekeymapredefiner&hl=en to check, and found the inputs were correctly being read as 'MEDIA_VOLUME_UP' , etc.
I tried this on the stock GS Android 8.0 ROM as well as Malaysk's Android 8.0 PX5 ROM. Is there anything that can be done to allow this to control the volume?
Any help much appreciated!

kaise123 said:
Hi all! Recently got an Android 8.0 based GS (XTRONS) unit, the TE706PL.
The main issue that I have with the unit is that it does not have a physical volume knob. I was OK with this when I purchased it as I planned on adding in my own. I have used an Arduino and a rotary encoder to 'replicate' a HID volume knob.
This is able to adjust the volume on my computer as well as on my Oneplus 3T with an OTG adaptor. However, when connected to the head unit, it does not work. I also tried connecting a standard USB keyboard to the headunit and found that all the keys work, including media play/pause keys, except volume up, down and mute do not function.
On the head unit, I used this app: https://play.google.com/store/apps/details?id=innerlife.keyboard.multilanguagekeymapredefiner&hl=en to check, and found the inputs were correctly being read as 'MEDIA_VOLUME_UP' , etc.
I tried this on the stock GS Android 8.0 ROM as well as Malaysk's Android 8.0 PX5 ROM. Is there anything that can be done to allow this to control the volume?
Any help much appreciated!
Click to expand...
Click to collapse
Look for a thread of @bose123. He programmed his own
Enviado desde mi SM-G950F mediante Tapatalk

ikerg said:
Look for a thread of @bose123. He programmed his own
Enviado desde mi SM-G950F mediante Tapatalk
Click to expand...
Click to collapse
Thanks! Doesn't seem to be a valid XDA username though... Do you know where the thread was by any chance? I've done a fair bit of searching

kaise123 said:
Thanks! Doesn't seem to be a valid XDA username though... Do you know where the thread was by any chance? I've done a fair bit of searching
Click to expand...
Click to collapse
Sorry is @Bose321
That thread is for controlling radio from external remote control.....perhaps contacting him you can get the solution
https://forum.xda-developers.com/showthread.php?t=3625038
Enviado desde mi SM-G950F mediante Tapatalk

ikerg said:
Sorry is @Bose321
That thread is for controlling radio from external remote control.....perhaps contacting him you can get the solution
https://forum.xda-developers.com/showthread.php?t=3625038
Enviado desde mi SM-G950F mediante Tapatalk
Click to expand...
Click to collapse
Thanks for the suggestion, but unfortunately it's not quite what I'm looking for. His app allows you to control the built in microntek apps with a remote or media buttons. My media buttons are working fine, it's specifically Volume Up, Down and Mute which do not work (Android system seems to flat out ignore the input)
I was wondering if, as a potential workaround I could use an app to remap keyboard inputs to volume level inputs? I haven't been able to do this with Tasker so far.

kaise123 said:
Thanks for the suggestion, but unfortunately it's not quite what I'm looking for. His app allows you to control the built in microntek apps with a remote or media buttons. My media buttons are working fine, it's specifically Volume Up, Down and Mute which do not work (Android system seems to flat out ignore the input)
I was wondering if, as a potential workaround I could use an app to remap keyboard inputs to volume level inputs? I haven't been able to do this with Tasker so far.
Click to expand...
Click to collapse
Volume on our units is not controlled by normal media commands on android. Is controlled by the MCU and therefore by any microntek service.
Ask bose321 for support as he investigated this.
Enviado desde mi SM-G950F mediante Tapatalk

kaise123 said:
I was wondering if, as a potential workaround I could use an app to remap keyboard inputs to volume level inputs? I haven't been able to do this with Tasker so far.
Click to expand...
Click to collapse
Try this https://forum.xda-developers.com/showthread.php?p=76032481

aluver said:
Try this https://forum.xda-developers.com/showthread.php?p=76032481
Click to expand...
Click to collapse
Thanks, I did actually find that. I have given this a go manually through terminal emulator. When run as standard user, I get the following:
{
"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"
}
And when run with SU I get:
However nothing changes. I have tried this with a number of key codes that I found and none seem to have an effect. Am I running this incorrectly?
Any help definitely appreciated! I feel like I'm close here

kaise123 said:
Any help definitely appreciated! I feel like I'm close here
Click to expand...
Click to collapse
Try keycodes 273 (volumeUP) and 281 (volumeDOWN) from su.
If that works I can give you whole list
https://forum.xda-developers.com/showpost.php?p=67855471&postcount=17

aluver said:
Try keycodes 273 (volumeUP) and 281 (volumeDOWN) from su.
If that works I can give you whole list
https://forum.xda-developers.com/showpost.php?p=67855471&postcount=17
Click to expand...
Click to collapse
Thankyou!!! You saved me a lot of headscratching haha. My next step was trying to pull apart MTCManager to see what it could reveal....
Now... Tasker won't recognise my device is rooted, but that's a separate issue, may need to start a new thread at-least I know what I want to do is possible now.

Would it be possible to set this up using MTCD Tools? I'm very interested in figuring out how to configure this in mtcd tools.

kaise123 said:
The main issue that I have with the unit is that it does not have a physical volume knob. I was OK with this when I purchased it as I planned on adding in my own. I have used an Arduino and a rotary encoder to 'replicate' a HID volume knob.
Click to expand...
Click to collapse
I have a touch screen only (ISUDAR 7.1.2_GS PX3 2GB RAM) with no buttons at all and planned to do the same, so I'm interested in how this works out for you. My steering wheel does not have buttons, so I was going to replace it with one that does and see if it transmits on the CANbus because supposedly these ISUDAR units can adapt to it using the CANbus decoder box and app supplied with the head unit. If that didn't work on the vehicle harness my approach was to use Arduino to send CAN signals and read them with the CANbus decoder. I've not tried either yet, and am new to Arduino but seems possible. Do you have the CANbus decoder?
Also, does your unit have a SD card (or GPS) slot? Mine doesn't. If no, how/where did you place the flash files and start the system update to install the Malaysk ROM? I can't get much support from ISUDAR.

VigorPD said:
I have a touch screen only (ISUDAR 7.1.2_GS PX3 2GB RAM) with no buttons at all and planned to do the same, so I'm interested in how this works out for you. My steering wheel does not have buttons, so I was going to replace it with one that does and see if it transmits on the CANbus because supposedly these ISUDAR units can adapt to it using the CANbus decoder box and app supplied with the head unit. If that didn't work on the vehicle harness my approach was to use Arduino to send CAN signals and read them with the CANbus decoder. I've not tried either yet, and am new to Arduino but seems possible. Do you have the CANbus decoder?
Also, does your unit have a SD card (or GPS) slot? Mine doesn't. If no, how/where did you place the flash files and start the system update to install the Malaysk ROM? I can't get much support from ISUDAR.
Click to expand...
Click to collapse
ISUDAR are a seller AFAIK, your MCU will tell you what unit you have.
ALL MTCD/E units can use CAN Bus even if they are universal units - the data for all supported MTCD/E vehicles is in all MTCD/E MCUs, so you do not need anything other than a CAN Bus decoder for your car and a loom from your headunit manufacturerrto attach it to (or you could make one). Once you have these 2 things you just set the CAN Bus type in factory settings and your SWC should work.

VigorPD said:
I have a touch screen only (ISUDAR 7.1.2_GS PX3 2GB RAM) with no buttons at all and planned to do the same, so I'm interested in how this works out for you. My steering wheel does not have buttons, so I was going to replace it with one that does and see if it transmits on the CANbus because supposedly these ISUDAR units can adapt to it using the CANbus decoder box and app supplied with the head unit. If that didn't work on the vehicle harness my approach was to use Arduino to send CAN signals and read them with the CANbus decoder. I've not tried either yet, and am new to Arduino but seems possible. Do you have the CANbus decoder?
Also, does your unit have a SD card (or GPS) slot? Mine doesn't. If no, how/where did you place the flash files and start the system update to install the Malaysk ROM? I can't get much support from ISUDAR.
Click to expand...
Click to collapse
I don't have buttons on my steering wheel either. I also wanted to experiment with using CANBus signals to set the volume, but I was not able to find a reliable or well documented way to emulate canbus commands. In the end, I was able to get tasker to pick up the key inputs (Using AutoInput) and output the root command for changing the volume. I used an Arduino Pro Micro and the HID keyboard library to make an emulated keyboard input.
My device had a GPS slot only, but upon opening it I found that it had provision for an 'SD' slot. If you do not have a GPS slot there are other threads out there that might be able to help you, or if you are comfortable opening your device, see if it has the header to add one in yourself.

kaise123 said:
In the end, I was able to get tasker to pick up the key inputs (Using AutoInput) and output the root command for changing the volume. I used an Arduino Pro Micro and the HID keyboard library to make an emulated keyboard input.
Click to expand...
Click to collapse
I'm still not sure which direction I will take but am interested in more details on this solution if you would share. I'm a noob at everything you mentioned above. It gives me another idea to create a multi function knob like a simplified version all the new cars have for infotainment control. Rotate for volume, push for mute/power, forward for Home, back for Back, etc.
kaise123 said:
My device had a GPS slot only, but upon opening it I found that it had provision for an 'SD' slot. If you do not have a GPS slot there are other threads out there that might be able to help you, or if you are comfortable opening your device, see if it has the header to add one in yourself.
Click to expand...
Click to collapse
ISUDAR got back to me and said to load it on an empty USB stick instead. The rear of the case does have an open area marked for mounting a SD slot just no hardware populating it. I just had the unit opened up last week and added a homemade button to allow hitting the power button inside without needing a paper clip. If I open it up again what am I looking for with respect to a header?
I'm pretty keen to hack and customize more but struggle finding all the knowledge bits to connect the dots spanning software and hardware.

Did you manage to resolve this issue?
I've got the same head unit and the same issue, did you find a solution to the problem?
Thanks

kaise123 I have the Xtrons unit as well and need to do a similar solution to yours with a USB dial I have for volume and mute. It looks like you have root on this one. Can you direct me to instructions for rooting this unit?

frisbin said:
kaise123 I have the Xtrons unit as well and need to do a similar solution to yours with a USB dial I have for volume and mute. It looks like you have root on this one. Can you direct me to instructions for rooting this unit?
Click to expand...
Click to collapse
You need to be more specific, Xtrons are a seller not a manufacturer, there are no Xtrons units - units are identified by the MCU so you need to post that and the Andorid version youre running. There are also many guides to rooting.

typos1 said:
You need to be more specific, Xtrons are a seller not a manufacturer, there are no Xtrons units - units are identified by the MCU so you need to post that and the Andorid version youre running. There are also many guides to rooting.
Click to expand...
Click to collapse
Thanks for the instruction about that.
Like kaisel123, mine is labeled TE706PL (xtrons).
It shows Model px5, Android version 8.0.0, MCU version MTCE_GS_V2.78_3
Found some threads, reading through.

frisbin said:
Thanks for the instruction about that.
Like kaisel123, mine is labeled TE706PL (xtrons).
It shows Model px5, Android version 8.0.0, MCU version MTCE_GS_V2.78_3
Found some threads, reading through.
Click to expand...
Click to collapse
Right, you have a GS Oreo unit, theres a thread about rooting or Malaysk's ROM is rooted.

Mcu Problem / steeringwheel controls

Hi All
Thanks for any help you can give with this, i have been unable to find this problem mentioned elsewhere.
I have changed the mcu on my px3 1gb rk3188 head unit as i had been having trouble with the steering wheel controls being intermittent over the canbus.
I am sure my original was a kgl mcu but if i install that one and a few others i get a random beep every few seconds.
I have just tried the newest www and mx mcus and i also get the beep on these
The last mcu i had without the beep i think it was an mx one had no option for disabling the reversing camera
i was hoping to try hals nougat firmware however this requires a newish mcu.
Is there a fairly generic brand mcu which is likely to be a winner for me please or is there anything i can do to stop the random beeping please?
Also is there any way to make my steering wheel controls less intermittent please they will work fine for a while and then stop completely and same in the car diagnostics app so i assume it gets bored listening to the canbus and gives up.
it is a 2011 seat ibiza ecomotive.
Thanks
Kamcel

It could be the spring cable in the steering wheel if I understand correctly. My cable is going/intermittent but reprogrammed the buttons there are 2 sets for each button, I think it's a resistance issue, but it appears to be working for me.
Sent from my Z981 using Tapatalk

No external canbus decoder box on newer PX5 HUs?

Hi MTCD community.
Thanks to the time between the years (that's how we call December 27th to 31st in Germany), I had time to upgrade my HU. Up to now I had a RK3188 quad-A9 one (Erisin ES2508B, KGL) that had a proprietary power connector and a external canbus decoder box. (more information here: http://vi.vipr.ebaydesc.com/ws/eBay...descgauge=1&cspheader=1&oneClk=1&secureDesc=0 )
That external canbus decoder of the unit has a few dedicated output pins for illumination, reverse gear and a UART (?) style digital RX/TX connection to send wheel-button key commands. It's a perfect example for a Chinese product. This solution it easy and works - almost:
On Mercedes cars the wheel-buttons are used to steer the so called Kombi (KI). KI and HU are connected via canbus. Key commands are send in one specific can-message. The canbus decoder box is said being made specifically for Mercedes cars. While it correctly decodes button presses it fails to decode the current KI menu. As a result the HU will always interpret the "prev./next" buttons, even when you're not in the KI's Audio menu. As a result you either stop using your KI (bad option) or you disable some keys in the HU (that's what I did). The decoder box is also only reading the canbus and thus not able to send audio titles or the current radio frequency/station name to the KI.
Because of the decoder box sitting between HU and KI I never tried to enhance functionality because that would have ment either connecting another R/W canbus dongle to the HU or replacing the chinese decoder box and reverse engineering the RX/TX communication between decoder box and HU.
---
The newer PX5 unit that I now own (Erisin ES7689C, KGL?/LM?, http://www.ebay.co.uk/itm/Android-8...s-W203-W209-/123151147422?hash=item1cac61619e ) has a Quadlock connector (that's the correct name for the multi pin connector that became popular on HUs beginning in the early 2000th) and no external canbus decoder box (it is indeed perfectly plug'n'play). It is also able to identify itself to the KI as Radio which means it is also writing to the canbus. Compared to an original OEM HU, information is still extremely limited and it again fails to interpret only wheel-button commands send from the KI's Audio menu. - But, it is able to write to the canbus, so potentially this is a much better starting point for enhancements.
Now the key question: Does anyone know how the HU is communicating with the canbus? Is the decoder box just inside the HU's housing (and again being an extra translation module) or is it a proper canbus device controlled by an app or service from inside the HUs android?

Good piece of info mate. Thanks a lot
Unfortunately i am not able to answer the question due to limited knowledge.
I own a Mercedes w164 and have the same issues and i am keen to find a solution. Open a thread for that too here > https://forum.xda-developers.com/an...t/adapter-help-mercedes-t3903165#post79005544
My MTCD idetails are :
Unit: MTCD PX5
MCU: MTCE_GS_V3.00_3
ROM: Halk9 Mod 3.1 (Android 8)
Can Adapter : GS 10280514 / HW:V2 SW:V3
Can adapter Setting: 23 Benz_B200(simple)
On another thread more HW related you can find pleanty of info >
https://forum.xda-developers.com/an...elopment/mercedes-benz-class-comfort-t3680320
Also this guy did some work on canbus : http://honeysw.com/canproject.php
and here another piece of info : https://forum.xda-developers.com/an...-units-qa/how-bus-messages-make-unit-t3352343

Hi I also have a MB lol, a w203.
I have been through several head units of types makes etc, so know exactly what you mean. Although I never heard of 'ki' before.
My latest unit I have is def very good (best was a pioneer with separate car-pi can decoder) and that is also an erisin.
Great minds an all that eh!
The unit I have is a 4/32gb android 8. MTCE. It was working very well until I developed a problem with my reverse camera signal not getting picked up. Was switching OK but no image??
Anyway I bit the bullet and installed the custom rom by Malaysk which helps the camera but no steering control (for me) on 3rd party apps.
There is some talk about mtce files etc but I couldnt get anything to work until I installed a brilliant prog called mtcdtools (free from github).
Very techy to understand / use but with the info and help from others managed to replicate enough to get the two up/down left buttons working perfectly on all apps. It starts up by itself and stays in background. I'm very pleased with result and sure it could do much more if i only knew how. Def give it a go.
Also the up/downs only while in the audio sub menu and they operate whichever music app is running even while in the background if that makes sense. The right volume buttons always worked anyway, and with the phone.
I think the real challenge now will be getting info in the dash display to correspond with what ever app is on top. Currently mine just says audio off when using dab, but displays station number in radio and time elapsed from music player., but nothing from nav.