Related
Hi everyone, I have a joying rk3188 1024x600 head unit and recently flashed the most recent malaysk rom. Before the flash, obd dongle would pair fine. Now I cannot get out to connect. I can connect my phone to the headunit, can connect my phone to the obd dongle, but cannot connect the obd dongle to my headunit whatsoever. It shows up in "available devices" and can be clicked then click "yes" to connect, but it doesn't connect.
I've tried to play around with xposedmtc but no luck.
Anyone have any ideas?
Thanks!
did you click enable xposedmtc in xposed?
TRY disable xposed-bt or manager in xposed
and roboot will be done
Yes, all are activated in xposed. And tw0119, I will give that a try.
Malayskâs rom Dec.2015 on my JY-HU clould pair fine ,but Feb.2016&Jan.2016 roms could not.
So i try disalbe all Xposed modules ONLY enable Xposed mtc ,OBD dongle works after roboot
Tw0119, perfect, works now. Did you go back and reactivate the modules again or no?
Thank you so much btw!
dannyboy223 said:
Tw0119, perfect, works now. Did you go back and reactivate the modules again or no?
Thank you so much btw!
Click to expand...
Click to collapse
NO,if you reactive the XposedManager module it would be down.
So i think somethings wrong with the Framework,maybe Malaysk could TEST for it
tw0119 said:
NO,if you reactive the XposedManager module it would be down.
So i think somethings wrong with the Framework,maybe Malaysk could TEST for it
Click to expand...
Click to collapse
No XposedBT whit OBD.
Prob is that there are number of overlapping Xposed modules, conflicting with each other and even underlying ROM features.
Until Malaysk and module devs coordinate their activities you have to experiment and make compromises. In order to get something you have to drop something.
I had the same problem: my bluetooth OBD2 / OBD adapter were being detected, but I could not pair them. My OBD2 adapter has a pin number and I was never asked for the pin to pair. Also, the device was being scanned and shown with the phone icon instead of the OBD icon. Had this problem with March and January 2016 versions of Malaysk ROM (which is awesome, btw!). How I solved the problem:
1. Opened the stock bluetooth app, removed the device which already appeared paired
2. Set the default pairing PIN to the PIN of my device
3. Disabled XposedMTC and XposedBT in the Xposed module manager
4. Rebooted
5. Scanned for the device, checked that it appears as OBD (icon) and paired again. No pin was requested, but it paired correctly and it works.
Hope this helps! Cheers,
C.
i have 2 adapters and neither will work for me. one will not pair no matter what combination of things i choose in xposed but works great with my phone. the other adapter works so good i don't even have to put in the pass code when using my deck, but it will not communicate with my 2001 fords ecu.
Hi
Not working bluetooth. Not scaning anything
Which BT chip sellected? WQ BC5 ,WQ BC6, IvtBt,Sd bt, WQ BC6B. My sytem rk3066 arm vortex 1.6 dual core .
April 2016 malaysk rom.
I tryed xposed disable combination but not working bluetooth
Help pls
Sytem starting i see pop-up bt connecting,version2
OBD adapter
Unfortunately I have the same problem with the OBD adapter are connected may not apply to find and get information...
The machine is KLD2-RK3188 1024x600 machine with the latest of Rom Malaysk 21/1/2017 (21 version)
I have tried all the above solutions but still not the OBD program works.
OBD connection Joying
Can somebody tell me where to get to "Xposed module manager" in Joying system please? For OBD bluetooth issue
i had same problem but solved it.
Don't use the bluetooth menu in system settings but use the bluetooth app instead (which came with the rom (android 6)).
Using the bluetooth app search here and here pairing worked without any problems for me, after pairing it worked as normal again.
cheatman said:
I had the same problem: my bluetooth OBD2 / OBD adapter were being detected, but I could not pair them. My OBD2 adapter has a pin number and I was never asked for the pin to pair. Also, the device was being scanned and shown with the phone icon instead of the OBD icon. Had this problem with March and January 2016 versions of Malaysk ROM (which is awesome, btw!). How I solved the problem:
1. Opened the stock bluetooth app, removed the device which already appeared paired
2. Set the default pairing PIN to the PIN of my device
3. Disabled XposedMTC and XposedBT in the Xposed module manager
4. Rebooted
5. Scanned for the device, checked that it appears as OBD (icon) and paired again. No pin was requested, but it paired correctly and it works.
Hope this helps! Cheers,
C.
Click to expand...
Click to collapse
That worked for me. But found also additional tips are needed to check:
1. If adapter name is not OBDII per default then in BT app settings (last tab) set exact name. This option is available in modded BT apps in Malaysk ROM (4.4.4), dunno for other ROMs. So there is no need for any exposed modules, just change adapter name in app.
2. Adapter with correct name can pair even if pin code is incorrect! Looks like paired but will not work in apps. So check that pin code in BT app settings is correct for your adapter.
3. In Torque, if you had any other adapter used before, clean all app data (in Android app info). Also noticed that even after app data cleaning, old Mac address is shown instead of new one paired in BT app. Looks like MCU somehow wrongly saves and provides old, even removed from BT app, adapter Mac address. But new paired adapter is working. So there is some mess with MCU and BT and Torque... Not sure where is the issue, but noticed that latest Torque ver listed something about 'improved listing of BT devices'. So it may be known issue on Torque side....
I had the same problem (obd bluetooth not working) using Pumpkin Android 7.1.2 with malaysk ROM 4.1 and found the following solution:
Go to app settings, select "show system apps" an delete data+cache of all (4 in my case) apps regarding bluetooth.
Then connect your devices again. Enjoy
I've searched and looked, and I can't seem to find a complete answer to exactly how the bluetooth works on these things.
As far as I can tell; there is the native bluetooth manager that's built into Android, and then a Bluetooth app. Seems like the app is used to make calls and stream from the phone?
I've also read that there cannot be an OBD2 sensor and a phone connected at the same time? I remember reading somewhere that's because Android doesn't actually handle the bluetooth itself, so if I were to get a bluetooth dongle, would that fix this?
FYI, I have a joying headunit and I have been using the Torque app w/ a Bluetooth ODBII adapter and received calls while both are connected. But yes the Bluetooth profiles that come with these units are very limited and basic.
bsavoir22 said:
FYI, I have a joying headunit and I have been using the Torque app w/ a Bluetooth ODBII adapter and received calls while both are connected. But yes the Bluetooth profiles that come with these units are very limited and basic.
Click to expand...
Click to collapse
What is your process in getting them to work together?
Sent from my Nexus 6P using Tapatalk
I remembered that I had another BT OBD2 adapter. I was using this one and couldn't get it to work, https://www.amazon.com/dp/B011NSX27A/ref=cm_sw_r_other_apa_F0mqxbPZDQSQ5
I then pulled out my old one, (not this exact one, but looks identical) https://www.amazon.com/dp/B00EQ57BE8/ref=cm_sw_r_other_apa_b8mqxbA6SEVRV and now they both are working together.
Sent from my Nexus 6P using Tapatalk
Is it possible to get DashCommand working on these units? I like it better than torque.
Sent from my Nexus 6P using Tapatalk
Sure no problem, and what I did is just buy a self powered USB hub and stick an additional Bluetooth dongle in there (android compatible, costs about $4) and pair with both.
Never had a problem with any of them
Hello,
The BT module in these devices are not an internal device, rather an external BT chip. There is no direct data line between device and BT chip. Basically they send commands and share metadata over serial port. Thats all about so dont consider it is a native bluetooth device.
Hello everyone, I was wondering if this has happened to anyone else.
I updated my rom to "Johny DJ" MicroG apps 5.1.1, everything is working except bluetooth seems a bit strange, on the Bluetooth app I cannot see any connected devices, or I cannot search for any devices, but I can connect to it from my phone, if I make a call I can hear it though the car, but the app still does not see the phone, so I cannot search for any contacts.
Additionally it also means I cannot connect a OBD2 because I cannot see it through the unit.
The only Bluetooth that work is the WQ_BC5, can it be an issue with the bluetooth manager.apk and that specific module?
Had anyone else had this issue?
Thanks
I have the octa-core PX5 MTCD/E under the brand Eonon P/N GA9150B running the stock ROM and I'm trying to add a Gyro/Magnetometer (for a compass, navigation, roll/pitch/yaw, etc) and having a hell of a time.
I purchased a Bluetooth WitMotion BWT901CL and did the initial setup on my Galaxy S7 (Android 7) using their apk with no issues. When I connect the device over Bluetooth to the PX5, it shows up as an OBD scanner. I attempted to install the apk on the PX5 but it crashes upon startup.
I then decided to attempt using a USB connection and purchased a USB to TTL cable and ended up with nearly the same results. When I plug the WitMotion in, I get a "Which app do you want to use this device" message, either iBus (BMW app) or Torque. Neither which are going to help me.
Regardless of USB or Bluetooth, when I open a compass app, it tells me there is no Magnetometer in my device and closes. Same for Google Maps, Waze, etc.
Has anyone successfully installed something like this? I found this tread, but with no solutions
Nobody?
Bump for justice
Interesting! I was looking for something like this as well. Still no luck I guess?
(@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.