Develop Bugs

Bluetooth does not pair with OBD-Adapter

dwmcqueen said:
Hello,
I just recently purchased this - http://www.amazon.com/gp/product/B0...tailpage_o04_s01?ie=UTF8&psc=1#productDetails
A couple of notes:
1. It appears to be another HuiFei model - specs all align with what is said in this thread (including the Developer password).
2. MCU says MTCB-GS-V1.91
3. I am having a real hard time having my ELM327 connect - scanning for new Bluetooth devices yields nothing.
4. There is no "Extra Settings" - so not sure where I go to map the physical buttons (I want the Navi button to map to Google Maps).
Other than that, seems to be working nicely.
Click to expand...
Click to collapse
I have the same unit its MCU 2.02 though but only certain BT ELM works.... I found on that works fine... I will include more info in my write up....

antiguangenius said:
I have the same unit its MCU 2.02 though but only certain BT ELM works.... I found on that works fine... I will include more info in my write up....
Click to expand...
Click to collapse
By default, these headunits only recognize and pair with BT OBD adapters that have the name "OBD". I've removed this limitation with the latest experimental release of the XposedMTC module.
makkan00 said:
Bit worrying. I have this unit hardly for 2 months and it has developed another fault.
When I hit speed bumps, it automatically changes to previous track / radio station.
Click to expand...
Click to collapse
It seems that the rotary encoders used for volume and tuning are sometimes susceptible to vibrations/bumps. I've had issues where the volume randomly goes up or down while driving. After spinning the knob up and down a few times it goes away.

agentdr8 said:
It seems that the rotary encoders used for volume and tuning are sometimes susceptible to vibrations/bumps. I've had issues where the volume randomly goes up or down while driving. After spinning the knob up and down a few times it goes away.
Click to expand...
Click to collapse
Thanks. I will try it.
With regards to obd, how do I take out the restriction on obd adapters which my unit can use?
Thanks.

makkan00 said:
Thanks. I will try it.
With regards to obd, how do I take out the restriction on obd adapters which my unit can use?
Thanks.
Click to expand...
Click to collapse
You can either decompile the MTCBluetooth3.apk and Settings.apk, modify the smali files to remove the restriction and recompile, or you can root your headunit (check out the first post), install the Xposed Framework, and install the XposedMTC module.

agentdr8 said:
You can either decompile the MTCBluetooth3.apk and Settings.apk, modify the smali files to remove the restriction and recompile, or you can root your headunit (check out the first post), install the Xposed Framework, and install the XposedMTC module.
Click to expand...
Click to collapse
I have xposed mtc and framework and this is a year later. It still does not see my bluetooth ODB as it is not named ODB. It is named CBT

Shagman68 said:
I have xposed mtc and framework and this is a year later. It still does not see my bluetooth ODB as it is not named ODB. It is named CBT
Click to expand...
Click to collapse
Compatibility also seems to depend on the version of the adapter; the generic ELM327 readers come in many versions. I haven't correlated which versions work and which ones don't, but my adapter, which also shows up as "CBT" is a v1.2, and the override within XMTC does work.
I'm assuming you've already set the XMTC preference to "CBT" and rebooted? Make sure the pairing pin in the stock BT app matches that of the OBD adapter (e.g. 0000, 1111, 1234), and try pairing from within the BT app.

agentdr8 said:
You can either decompile the MTCBluetooth3.apk and Settings.apk, modify the smali files to remove the restriction and recompile, or you can root your headunit (check out the first post), install the Xposed Framework, and install the XposedMTC module.
Click to expand...
Click to collapse
hey @agentdr8 , I've managed to install Xposed, but cannot install the module itself... tried several versions and it still not working on my 4.1.1 Head Unit.
can you help?

agentdr8 said:
By default, these headunits only recognize and pair with BT OBD adapters that have the name "OBD". I've removed this limitation with the latest experimental release of the XposedMTC module.
Click to expand...
Click to collapse
Man i tried that Xposed option and no luck..... its there something specific you need to do? i did the following
- Turned option on Typed Name of ODB adapter.... in my case "Carly Adapter"
- Turned option off
neither worked for me... am i doing something wrong? my HU has passcode set to 1234 which is the same for ODB adapter this one is specially made for BMWs

staticx1 said:
hey @agentdr8 , I've managed to install Xposed, but cannot install the module itself... tried several versions and it still not working on my 4.1.1 Head Unit.
can you help?
Click to expand...
Click to collapse
If you're using a Malaysk rom, the module comes preinstalled, and just has to be enabled in Xposed Installer->Modules. If not, make sure you're installing it to internal storage; some roms default to installing to sdcard and it won't work that way.
xterm305 said:
Man i tried that Xposed option and no luck..... its there something specific you need to do? i did the following
- Turned option on Typed Name of ODB adapter.... in my case "Carly Adapter"
- Turned option off
neither worked for me... am i doing something wrong? my HU has passcode set to 1234 which is the same for ODB adapter this one is specially made for BMWs
Click to expand...
Click to collapse
Try using just "Carly" as the name (it's a string comparison using a String.contains). Leave the option enabled, and then restart the headunit.

i left it as Carly Adapter it worked just needed to reboot after activation of xposed but sadly it soft brick my HU everytime so system enters recovery and erase everything to restore defaults.... this is using Stock pumpkin firmware. So i think i just gonna go ahead and install custom ROM instead

Hi, I', not able to connect to my OBD adapter. It's a Vgate 3 and the bluetooth name is V-LINK. I've the last Malaysk rom (April 2016), I've installed Xposed framework and Xposed bluetooth module. I've tried to set every combination of strings that could match V-LINK (rebooting) but nothing seems to work. I've also set the bluetooth pin to 1234 (matching my adapter pin). My unit is a Pumpkin 1024x600 quad core RK3188. Any help?

Lyhaku said:
Hi, I', not able to connect to my OBD adapter. It's a Vgate 3 and the bluetooth name is V-LINK. I've the last Malaysk rom (April 2016), I've installed Xposed framework and Xposed bluetooth module. I've tried to set every combination of strings that could match V-LINK (rebooting) but nothing seems to work. I've also set the bluetooth pin to 1234 (matching my adapter pin). My unit is a Pumpkin 1024x600 quad core RK3188. Any help?
Click to expand...
Click to collapse
Is your OBD adapter paired to your phone by any chance? If so, unpair it, and try again
Sent from my XT1575 using Tapatalk

brbarnyard said:
Is your OBD adapter paired to your phone by any chance? If so, unpair it, and try again
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Hi, thanks for the reply. I'll try, during my tests it was paired but If i remember well the phone bluetooth was off.

PX5 HA BT issue

I have HA head unit with 10 inch screen it is using HA_PX5_6.0(20171214) and MTCE_HA_V2.71
I have a problem connecting an OBD2 adapter, the adapter is called Response PP-2145.
Running a scan from the BT app in the head unit discovers the OBD2 adapter but it will not pair. This adapter cost quite a lot and was to replace a very cheap £3 one which works OK but does not find all available pids on the car.
If I search for the old (working) adapter it appears as an OBD symbol, a pairing attempt then asks for the password 1234 and it pairs OK.
The new adapter is found but has a mobile symbol and a pairing attempt does nothing at all. Yet pairing the new adapter to a Galaxy S6 works properly, there is no password asked for it just connects.
Edit forgot to say the factory setting for BT is set to SD-968, there are others but from memory trying to use MD725 (I think) results in no name or password in BT

Hi, known issue. Refer graser tool and information here

marchnz said:
Hi, known issue. Refer graser tool and information here
Click to expand...
Click to collapse
Thank you, I had read that thread but I assumed that the issue was different as it says "Bluetooth OBD devices that name does not start with "OBD" does not communicate with the OBD app, as the app does not detect the OBD device and wants to open the Bluetooth connection."
My unit does not even pair, do you think this is the same issue? as perhaps I have misunderstood but I read it as meaning that the OBD2 would pair but apps could not connect to it if the name was not OBD or OBDII my adapter appears in the BT scan list called OBDII the same as one that does work.
Please do not think that I am questioning what you have told me, I would like to check that you think this would fix my particular problem before I take the risk (I am not experienced with this) of installing Xposed etc Thanks again for your help.

JohnLynn said:
Thank you, I had read that thread but I assumed that the issue was different as it says "Bluetooth OBD devices that name does not start with "OBD" does not communicate with the OBD app, as the app does not detect the OBD device and wants to open the Bluetooth connection."
My unit does not even pair, do you think this is the same issue? as perhaps I have misunderstood but I read it as meaning that the OBD2 would pair but apps could not connect to it if the name was not OBD or OBDII my adapter appears in the BT scan list called OBDII the same as one that does work.
Please do not think that I am questioning what you have told me, I would like to check that you think this would fix my particular problem before I take the risk (I am not experienced with this) of installing Xposed etc Thanks again for your help.
Click to expand...
Click to collapse
It seems that your obd2 device is a low energy bt4.0 or above...
That devices don't need a pin number to pair...But I think the head unit is not prepared for that kind of obd2 devices...working normally with cheaper obd2 bt devices that need a pin to be paired (bt3.0 and lower)
Enviado desde mi SM-G950F mediante Tapatalk

ikerg said:
It seems that your obd2 device is a low energy bt4.0 or above...
That devices don't need a pin number to pair...But I think the head unit is not prepared for that kind of obd2 devices...working normally with cheaper obd2 bt devices that need a pin to be paired (bt3.0 and lower)
Click to expand...
Click to collapse
With Device name being "PP2145" (did you buy from Jaycar?) This device may only be installed with graser tool. Search discussion thread for instruction.

Sorry I have been a long while replying, yes the PP-2145 came from Jaycar and it does pair with a phone without asking for a password. The cheap one does ask for a password 1234
I will read the Graser tool thread and see if I have success, thank you for your continued efforts to help.

JohnLynn said:
Sorry I have been a long while replying, yes the PP-2145 came from Jaycar and it does pair with a phone without asking for a password. The cheap one does ask for a password 1234
I will read the Graser tool thread and see if I have success, thank you for your continued efforts to help.
Click to expand...
Click to collapse
I have a VGate iCar2 which reports itself as "V-LINK" and does not require a password either (although the manual says it should ask for 1234). With the stock ROMs of November and December it pairs and is recognised as OBDII adapter (blue icon in the notification bar) without the need of the Graser tool.
One thing that helped others is to change the passcode of the unit to 1234 (from presumably 0000 it is now?).

Yes I had tried changing the head unit to 1234 but unfortunately that didn't work either. The adapter instruction book says "to pair select the PP-2145" but the adapter does not appear as PP-2145 it shows up as OBDII which is exactly the same as the cheap one that does ask for a password and does pair. The only noticeable difference is that the working one appears in the list of available devices as OBD but the one that does not pair is shown as a mobile phone symbol.
Am I right in thinking that the Graser tool is to enable the head unit to accept a device named something other than OBD? this is why I am so confused as this adapter does show in the available devices as OBDII not PP-2145

abagos said:
I have a VGate iCar2 which reports itself as "V-LINK" and does not require a password either (although the manual says it should ask for 1234). With the stock ROMs of November and December it pairs and is recognised as OBDII adapter (blue icon in the notification bar) without the need of the Graser tool.
One thing that helped others is to change the passcode of the unit to 1234 (from presumably 0000 it is now?).
Click to expand...
Click to collapse
Even the Android system dos not show a dialog asking for a password, the password is required...for the VGATE 2 you need to set up the pin as 1234 or otherwise it will not pair...
the Graser tool helps to specific OBD2 devices to have the available port to transmit the data to MTCD units.....but i dont think it helps on pairing.
Before with my VGATE Icar3 I had to use Graser's tool to the android Torque app to recognize the paired OBD2 device, but the device was already paired. Now, as you pointed, Grasr's tool is no needed anymore as HCT removed the limitation of OBD2 devices to have a discovering name starting by "OBD" caharacters

ikerg said:
Even the Android system dos not show a dialog asking for a password, the password is required...for the VGATE 2 you need to set up the pin as 1234 or otherwise it will not pair...
the Graser tool helps to specific OBD2 devices to have the available port to transmit the data to MTCD units.....but i dont think it helps on pairing.
Before with my VGATE Icar3 I had to use Graser's tool to the android Torque app to recognize the paired OBD2 device, but the device was already paired. Now, as you pointed, Grasr's tool is no needed anymore as HCT removed the limitation of OBD2 devices to have a discovering name starting by "OBD" caharacters
Click to expand...
Click to collapse
My problem is that both Torque and DashCommand have trouble establishing a connection with the OBD. When they are started, the connection to my iPhone is lost, often I have to re-enter the OBD settings in DashCommand.
Probably it has to do with my OBD? It has the feature to auto power off after thirty minutes and I have to press a button to wake it up. After I re-start the application it connects and works fine.
The V-LINK shows up in the paired devices but never turns green (like the phone) and all options other than "Unpair" are grayed out.

abagos said:
My problem is that both Torque and DashCommand have trouble establishing a connection with the OBD. When they are started, the connection to my iPhone is lost, often I have to re-enter the OBD settings in DashCommand.
Probably it has to do with my OBD? It has the feature to auto power off after thirty minutes and I have to press a button to wake it up. After I re-start the application it connects and works fine.
The V-LINK shows up in the paired devices but never turns green (like the phone) and all options other than "Unpair" are grayed out.
Click to expand...
Click to collapse
in my case I have to unplug/plug again to Torque/DashCommand connects to the Device (I think due to the auto poweroff of the device), but you will see on the sattus bar how the OBD logo changes to BOLD when transmnitting to any app.
I have no issues of phone disconnection (Android Galaxy S8) when OBD devices connects

Would it be any use in my case with the not pairing issue trying an external BT adapter if there is a USB device that would work on these head units?

Today I was able to try my BT adapter in a friend's head unit which has the Malaysk rom. This of course has the Graser tool as standard.
Unfortunately the symptoms were identical, the unit recognises the BT adapter although shows a phone symbol and pressing pair results in absolutely nothing happening. This was from the BT app, if the same thing was tried from the settings/bluetooth then the adapter appeared named 1OBDII so we used the Glaser tool to add this name plus a few others such as PP-2145 but with no success.
I do not understand enough about the Glaser tool to try anything other than adding new names, there is a line above the name with "cv" written in it what is 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"
}
[/IMG][/IMG]
JohnLynn said:
I have HA head unit with 10 inch screen it is using HA_PX5_6.0(20171214) and MTCE_HA_V2.71
I have a problem connecting an OBD2 adapter, the adapter is called Response PP-2145.
Running a scan from the BT app in the head unit discovers the OBD2 adapter but it will not pair. This adapter cost quite a lot and was to replace a very cheap £3 one which works OK but does not find all available pids on the car.
If I search for the old (working) adapter it appears as an OBD symbol, a pairing attempt then asks for the password 1234 and it pairs OK.
The new adapter is found but has a mobile symbol and a pairing attempt does nothing at all. Yet pairing the new adapter to a Galaxy S6 works properly, there is no password asked for it just connects.
Edit forgot to say the factory setting for BT is set to SD-968, there are others but from memory trying to use MD725 (I think) results in no name or password in BT
Click to expand...
Click to collapse
Hi
I have exactly the same problem as you, my Audio Video Nav Unit is a MTCE_MX2_V2.75_1 - Android 6.0.1
I also have a costful OBD reader OBDLink LX that i like very much, the BT discovered it with the phone symbol BUT simply don't get paired. With a cheap ELM327 Obd it works fine, but these cheap readers not always work properly.
I've tried several things but still don't work, if you get a solution post here
I will continue to search...
Good luck

pauloroxa said:
[/IMG][/IMG]
Hi
I have exactly the same problem as you, my Audio Video Nav Unit is a MTCE_MX2_V2.75_1 - Android 6.0.1
I also have a costful OBD reader OBDLink LX that i like very much, the BT discovered it with the phone symbol BUT simply don't get paired. With a cheap ELM327 Obd it works fine, but these cheap readers not always work properly.
I've tried several things but still don't work, if you get a solution post here
I will continue to search...
Good luck
Click to expand...
Click to collapse
There are multiple posts on this issue. Set pin code in BT app to 1234. Push button on Odblink then scan on headunit. Await for discovery to complete then press on Odblink in app to pair. You might need to push pair button on Odblink a second time.

Well i've tried almost everything...result: nothing. It continues to Discover and identify the OBDLink LX, but DON'T PAIR. I even reset the px5 MTCE to factory settings to clear All caches and start All the process ...nothing.
Is There anybody here from Scantool.net to gimme a reply?

Yes I am afraid that I have run out of things to try, setting pine code to 1234 as suggested above in my case does nothing as my unit does not have a pin. It would be good to know why our head units recognise the OBD unit as a phone?

JohnLynn said:
Yes I am afraid that I have run out of things to try, setting pine code to 1234 as suggested above in my case does nothing as my unit does not have a pin. It would be good to know why our head units recognise the OBD unit as a phone?
Click to expand...
Click to collapse
Hi John
well, i'm like you very sad not to set this up because the OBDLink LX is the best BT scan tool i ever used, cheap obd elm 327 have no comparison with LX, my cheap Obd already gave me ABS errors on the dash can you imagine and cut transmission very often, its useless.
the only thing their good is Pairing right away
But i didn''t gave up from LX yet...
I discover that our OBDLink LX firmware is STN 1155 V.4.3.0 identifying ELM327 V.1.3a and the cheap chinese ELM327 is V2.1, i think the problem is here... we need an older firmware
Keep in touch if you know something
Good luck

pauloroxa said:
Hi John
well, i'm like you very sad not to set this up because the OBDLink LX is the best BT scan tool i ever used, cheap obd elm 327 have no comparison with LX, my cheap Obd already gave me ABS errors on the dash can you imagine and cut transmission very often, its useless.
the only thing their good is Pairing right away
But i didn''t gave up from LX yet...
I discover that our OBDLink LX firmware is STN 1155 V.4.3.0 identifying ELM327 V.1.3a and the cheap chinese ELM327 is V2.1, i think the problem is here... we need an older firmware
Keep in touch if you know something
Good luck
Click to expand...
Click to collapse
It doesn't matter the version of elm chip....(in fact I think odblink lx is not an elm)...the point here is the version of Bluetooth of the obd2 device....your device is low energy bt 4.1...and head unit recognizes it as phone...
Enviado desde mi SM-G950F mediante Tapatalk

ikerg said:
It doesn't matter the version of elm chip....(in fact I think odblink lx is not an elm)...the point here is the version of Bluetooth of the obd2 device....your device is low energy bt 4.1...and head unit recognizes it as phone...
Enviado desde mi SM-G950F mediante Tapatalk
Click to expand...
Click to collapse
Thanks Ikerg for your time.
And why doesn't pair even being recognize as a phone? If the head unit treats it like a phone, at least it might paired like one...
I think the problem also is the 6 digit code that OBD LX requires, but the head unit never received that request besides have 4 digit space 0000 or 1234
i even dispaired all my devices in head unit and nothing.
Is there any app or firmware that we can install on HU android that runs on low energy devices?

chinese android head unit problem Play Store and Bluetooth

hello everyone,
I just installed a SEICANE chinese android head unit in my Fiat Ducato from 2017.
I connected the ISO port directly to the 2 connectors from the car, I've first tried to use a power harness including the CanBus decoder, but then the HU is dead. Without harness , the HU works (I guess the car already has a CanBus built in?).
The radio works very well. Also Wifi works well, I can surf on the Internet. But some apps I can not download (using Play Store). For example when I try to download TomTom GO, the HU tells me that there is no Wifi (although there actually IS Wifi!). Other apps are no problem to download (I've "fixed" this problem by installing Sygic i.o. TomTom).
I paired my Samsung XCover3 via Bluetooth and also problems: when I try to make a phone call, sometimes it goes to handsfree (like it should), but sometimes it does not (although the phone display opens on the HU). I did the pairing 10 times , but no difference. I also tried to make an Internet connection using Hotspot or tethering, but that also does not work.
I resetted the HU, but no improvement.
Does somebody knows these problems (and has sollutions to it)?
Regards,
Peter

Seicane T3 K2001N Android 7.1.1 - no bluetooth aplication and shortcut to pair ELM327

I am new here so Hello first to everyone.
I just bought and installed a seicane Android 7.1.1 quad T3 K2001N 1GB 16G.
The seller does not answer my questions.
I am asking you guys for help "How to made bluetooth pairing with ELM327?"
There is no bluetooth icons:
- in apps list,
- in upper shortcut bar
- in android settings.
Only bluetooth aplication is "BT MUSIC" and its working perfect with Android smartphone.
How to made bluetooth pairing with ELM327 when there is no posibility to pair it in Android?
It is not possible to connect to the TORQUE program without pairing in android menu first.
Help please

Try to connect to it through the tool cabinet app then look for odb match

Ivanow100 said:
I am new here so Hello first to everyone.
I just bought and installed a seicane Android 7.1.1 quad T3 K2001N 1GB 16G.
The seller does not answer my questions.
I am asking you guys for help "How to made bluetooth pairing with ELM327?"
There is no bluetooth icons:
- in apps list,
- in upper shortcut bar
- in android settings.
Only bluetooth aplication is "BT MUSIC" and its working perfect with Android smartphone.
How to made bluetooth pairing with ELM327 when there is no posibility to pair it in Android?
It is not possible to connect to the TORQUE program without pairing in android menu first.
Help please
Click to expand...
Click to collapse
I have got a WiFi enabled ELM327 and it works without any glitch on this same unit.
Have you tried setting up the Bluetooth using the phone menu settings? Do not keep phone connected to unit while searching for OBD2 unit

I have the same problem.. I tried buying the bluetooth and the wifi dongle with 0 results.

emmandiet said:
I have the same problem.. I tried buying the bluetooth and the wifi dongle with 0 results.
Click to expand...
Click to collapse
Are you trying to run Torque (pro)?
Torque Pro works best with a USB connection
https://www.amazon.com/ScanTool-OBDLink-USB-Professional-Diagnostics/dp/B005ZWM0R4

FYI: Not MTCD, post in wrong forum.

Alternate BT that can connect to XGPS160? [Rockchip PX5 A53 | Android 9.0 | 4GB RAM]

(@Admins I think this is the correct forum to post this in, but please feel free to move it if I've chosen the wrong forum. I'm still figuring out exactly what category my device is in)
TL;DR - Trying to figure out if it's possible to get an external USB Bluetooth dongle working on my radio instead of the built-in one, so I can connect to all types of bluetooth devices, not just streaming audio
Hi all,
I'm searching for a possible solution that would allow me to connect my Android radio (AUTOPUMPKIN AA0495B, using a PX5, MCU CSN2_06252019_163051) to a Dual XGPS160 device. I installed this stereo in my track car for the purpose of running Harry's Lap Timer; currently the app is running perfectly, with a wired OBDLink EX in use for OBDII data and also connecting to a GoPro via WiFi to control the camera. The last piece of the puzzle is I want to get an XGPS160 connected for better GPS data capture (10Hz vs 1Hz of the radio's GPS). After hours spent trying to get it to pair and connect to the device, I emailed AUTOPUMPKIN support and they confirmed that this radio cannot connect to such devices, as the Bluetooth module in the radio is essentially a glorified bluetooth headset and can only connect for streaming audio (I haven't been able to determine the model number of the bluetooth module it uses). My hope is there is a USB Bluetooth dongle that I could plug into the radio and then have the radio use that instead, which would then allow it to connect to the XGPS160 (and any other type of bluetooth device).
When I go into the Car Settings on the radio, it has the following options available for bluetooth:
IVT i140
IVT i145
FC6000TN
GOC_BC5
KD6
KD6 is what is selected from the factory. Please correct me if I'm wrong, but my understanding is this list is basically the different bluetooth hardware models the radio has driver support for? If I'm correct on that, then I'm also guessing if I were to plug in a bluetooth dongle using one of the other models and change this setting, the radio would use that instead of the built-in bluetooth? I don't use the bluetooth audio streaming or phone tethering feature, so I don't care if I lose those features if it allows me to connect the radio to the XGPS160. As long as the WiFi keeps working I'm ok with it.
Sorry if I'm asking any stupid questions; I'm a programmer by background, but even after hours of reading this forum my knowledge about the hardware in these Android radio units is still very limited. That being said, I'm not opposed to modifying config files to get this working. I have Android Developer mode enabled and I can connect to the radio via ADB; I spent some time looking at the file structure and various config files so modifying those if needed shouldn't be a problem for me.
thanks!

There was another (lengthy) thread on the subject of bluetooth dongles around here somewhere. You will have to do a search for it. If I remember correctly you had to open your head unit and physically disconnect your original bt module... and even with that there was limited success in getting the thing to actually work....and of those who claimed they did get it to work also said they couldn't get anything more to connect to the dongle than what the original BT could handle
It's too bad too. I have a sound processor on my system which uses an app through BT on my phone to make adjustments and I was HOPING it would connect to the head unit. It won't
BTW... your obdlink ex usb will also work with Torque (Pro). I use it with torque and it's blazing fast and reliable.... a lot more than a BT connection!

deja100 said:
(@Admins I think this is the correct forum to post this in, but please feel free to move it if I've chosen the wrong forum. I'm still figuring out exactly what category my device is in)
TL;DR - Trying to figure out if it's possible to get an external USB Bluetooth dongle working on my radio instead of the built-in one, so I can connect to all types of bluetooth devices, not just streaming audio
Hi all,
I'm searching for a possible solution that would allow me to connect my Android radio (AUTOPUMPKIN AA0495B, using a PX5, MCU CSN2_06252019_163051) to a Dual XGPS160 device. I installed this stereo in my track car for the purpose of running Harry's Lap Timer; currently the app is running perfectly, with a wired OBDLink EX in use for OBDII data and also connecting to a GoPro via WiFi to control the camera. The last piece of the puzzle is I want to get an XGPS160 connected for better GPS data capture (10Hz vs 1Hz of the radio's GPS). After hours spent trying to get it to pair and connect to the device, I emailed AUTOPUMPKIN support and they confirmed that this radio cannot connect to such devices, as the Bluetooth module in the radio is essentially a glorified bluetooth headset and can only connect for streaming audio (I haven't been able to determine the model number of the bluetooth module it uses). My hope is there is a USB Bluetooth dongle that I could plug into the radio and then have the radio use that instead, which would then allow it to connect to the XGPS160 (and any other type of bluetooth device).
When I go into the Car Settings on the radio, it has the following options available for bluetooth:
IVT i140
IVT i145
FC6000TN
GOC_BC5
KD6
KD6 is what is selected from the factory. Please correct me if I'm wrong, but my understanding is this list is basically the different bluetooth hardware models the radio has driver support for? If I'm correct on that, then I'm also guessing if I were to plug in a bluetooth dongle using one of the other models and change this setting, the radio would use that instead of the built-in bluetooth? I don't use the bluetooth audio streaming or phone tethering feature, so I don't care if I lose those features if it allows me to connect the radio to the XGPS160. As long as the WiFi keeps working I'm ok with it.
Sorry if I'm asking any stupid questions; I'm a programmer by background, but even after hours of reading this forum my knowledge about the hardware in these Android radio units is still very limited. That being said, I'm not opposed to modifying config files to get this working. I have Android Developer mode enabled and I can connect to the radio via ADB; I spent some time looking at the file structure and various config files so modifying those if needed shouldn't be a problem for me.
thanks!
Click to expand...
Click to collapse
No; it must be a specific BT type MD725 realtek device. No, you cant connect all manner of devices due to the hacked BT implementation.

Bob_Sanders said:
There was another (lengthy) thread on the subject of bluetooth dongles around here somewhere. You will have to do a search for it. If I remember correctly you had to open your head unit and physically disconnect your original bt module... and even with that there was limited success in getting the thing to actually work....and of those who claimed they did get it to work also said they couldn't get anything more to connect to the dongle than what the original BT could handle
It's too bad too. I have a sound processor on my system which uses an app through BT on my phone to make adjustments and I was HOPING it would connect to the head unit. It won't
BTW... your obdlink ex usb will also work with Torque (Pro). I use it with torque and it's blazing fast and reliable.... a lot more than a BT connection!
Click to expand...
Click to collapse
Yeh I found that threat in my searches, but no one in there quite mentioned this specific scenario (Selecting one of the other options in the Bluetooth settings) so I wasn't sure. And I'm definitely not opening up the unit and cutting on the hardware; hacking config files I can do all day long, but I have no skills when it comes to soldering so I'd probably just destroy the radio in the process of trying to cut that module :laugh:
Yeh I've run the OBDLink EX with Torque as well for data logging temps on track and it worked flawlessly for that as well. BT is definitely more convenient, especially since most are running apps from their phones, but if you have a dedicated radio like these then it's a no-brainer to permanently wire up a USB device.

marchnz said:
No; it must be a specific BT type MD725 realtek device. No, you cant connect all manner of devices due to the hacked BT implementation.
Click to expand...
Click to collapse
When you say "hacked BT implementation" I'm assuming you mean they don't use the standard Bluetooth stack built into the Android OS? That would make sense, as when I try to do anything with bluetooth from the standard Bluetooth settings menu, it doesn't do anything, doesn't see any devices available for pairing, or anything else. You can only see other devices and pair to them from the PUMPKIN Bluetooth app; the funny thing is it will go through the first steps and show the XGPS160 as being paired, but none of the apps that use the GPS actually see it as a paired device (my OBD dongle shows up, but not the GPS).
I don't understand why they didn't just use standard bluetooth that's already part of the OS, rather than use some hacky custom solution

Quick update since the last post. Spent some time tonight on google looking up the information I could find on those other bluetooth modules in the list of options on my stereo. Based on technical manuals and FCC documents, it appears the FC6000TN and BC5 are audio-only bluetooth chips that only support A2DP profile (basically the same as what I have now with the KD6); Now the IVT i140 and IVT i145 on the other hand appear to be full fledged bluetooth chips, and do support the SPP (Serial Port Protocol) that is needed by the XGPS160 (and many other bluetooth profiles) so in theory that would work. Unfortunately after searching for both of those, all I can find are ones in bare module form (i145 and i140) that would have to be soldered onto the board (assuming the pins are even compatible) and there are no USB versions of them that I could just plug in to my radio's free USB-A slot. The only thing even remotely close that comes up in Google in USB form is this adapter and I'm pretty sure it's not based on the i140 or i145.
Given that my soldering skills are non-existent, it seems I'm pretty much out of luck on getting this to work. Disappointing for sure, as I would gladly have paid more $ for the unit to come with a fully functional bluetooth module instead of this hacked audio only junk they put in it :/

deja100 said:
Quick update since the last post. Spent some time tonight on google looking up the information I could find on those other bluetooth modules in the list of options on my stereo. Based on technical manuals and FCC documents, it appears the FC6000TN and BC5 are audio-only bluetooth chips that only support A2DP profile (basically the same as what I have now with the KD6); Now the IVT i140 and IVT i145 on the other hand appear to be full fledged bluetooth chips, and do support the SPP (Serial Port Protocol) that is needed by the XGPS160 (and many other bluetooth profiles) so in theory that would work. Unfortunately after searching for both of those, all I can find are ones in bare module form (i145 and i140) that would have to be soldered onto the board (assuming the pins are even compatible) and there are no USB versions of them that I could just plug in to my radio's free USB-A slot. The only thing even remotely close that comes up in Google in USB form is this adapter and I'm pretty sure it's not based on the i140 or i145.
Given that my soldering skills are non-existent, it seems I'm pretty much out of luck on getting this to work. Disappointing for sure, as I would gladly have paid more $ for the unit to come with a fully functional bluetooth module instead of this hacked audio only junk they put in it :/
Click to expand...
Click to collapse
Unfortunately, It wouldn't matter which BT you use from the supported BT types, BT implementation is non-standard to do stuff like act as a BT hands-free.

marchnz said:
Unfortunately, It wouldn't matter which BT you use from the supported BT types, BT implementation is non-standard to do stuff like act as a BT hands-free.
Click to expand...
Click to collapse
Yeh, that's extremely disappointing Does anyone know of any Android based radio units that have full working bluetooth? I don't mind buying a new unit for the car if I know it will work with everything.

The old intel sofia units (mtcd as well) had the bluetooth & wifi ibtegrated into the soc...and they had a standard (or at least more profiles) implemented
Enviado desde mi SM-G975F mediante Tapatalk

ikerg said:
The old intel sofia units (mtcd as well) had the bluetooth & wifi ibtegrated into the soc...and they had a standard (or at least more profiles) implemented
Enviado desde mi SM-G975F mediante Tapatalk
Click to expand...
Click to collapse
Bummer they don't make those units anymore :/ Then again, they may not have been powerful enough to run my track timer apps anyway.