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?
Related
Hello,
i’ve bought one elm327 bluetooth adapter from Ebay, my problem seems to be that i should pair it to my HTC Desire using no code at all(blank code), this seems not to be possible since the ‘ok’ button is greyed out if i do no enter any code. I’ve tried enter ‘spacebar’ and ‘spacebar + backspace’ with no result, first one complains about wrong password, second one just gives me an error when it tries to pair.
The device i am using shows up as ‘CHX’, and the manual states i should use code ’5678′ which does not work at all.
I tried to pair to my macbook and pairing seem to work if i choose to not use any code at all, but i can’t test to see if it actually works because i can’t find any sw for os x.
Anyone have a clue what to do?
TIA
[Edit]
*Solved*
Just for the record if anyone come across the same problem with a device that identifies itself as 'CHX' the pairing code for my unit were not what the documentation stated, but instead 6789.
Discovered this after trying all logical codes i could think of.
Thank you!!!
The same 6789 worked for me!
Thanks!
Thanks! My bluetooth dongle got here today and I tried it out and couldn't get it paired for the life of me, but 6789 did the trick. Going to have to write that puppy down.
RoosterX said:
Just for the record if anyone come across the same problem with a device that identifies itself as 'CHX' the pairing code for my unit were not what the documentation stated, but instead 6789.
Discovered this after trying all logical codes i could think of.
Click to expand...
Click to collapse
Thank´s for the tip, i was beginning to think my new unit was defective.
You have just saved my day.
yeah the more we get this info out there the less people will be like us, thinking we got a defective unit from ebay!!
6789 worked a treat for me too...
ufff strugled to find it in my car just few minutes ago...
tnx to xda dev everything solved...
you rock guys...
Bah, I got mine today but 6789 does not work
nor does 0000, 1234 and about a million others I have tried.
got mine from here
http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&item=160550008686&ssPageName=STRK:MEWNX:IT
Try 6789 or 7890
Sent from my HTC Desire [Redux 1.2]
And if you're got it paired but still can't "connect" - some cars need to be fired up and not just key turned to accessory mode.
BMW - Year 2000.
Well 6789 worked after about the 300th attempt.
Doing my head in. Eventually gave me some error message about not connecting properly and resorting to default something...any it worked.
I had tried my old HTC Hero but that simply does not even see the device.
I don't think these things are at all well made but it was cheap.
Hi!
I bought Elm327 a few days ago.
When I try to find it with Htc Desire bluetooth, it doesn't apper in the list.
And so I can't pair these two
However, when I used it with my computer it was fine!
Any idea why this happens?
Hi, I have same problem like lina_k I can pair ELM327 with LG P500 (android), with Mio A501 (windows mobile 5.0), but with T5388i - HTC Touch Diamond 2 clone (windows mobile 6.5) I can't see ELM327 device. Bluetooth is ok, because I use bluetooth handsfree. Can anyone help? Thanks.
i'd love to buy one, somehow my car isn't supported.
vw golf mk5 tdi (CAN BUS),
thanks to this thread for letting me know the 6789 passcode for my cheap ebay obdII reader.
bobzero said:
thanks to this thread for letting me know the 6789 passcode for my cheap ebay obdII reader.
Click to expand...
Click to collapse
It's nice to know that it works for you.
6789 worked for me too, just got in from work to find the dongle waiting, now to charge phone up and put some fuel in the car lol
I got the same unit as you from ebay.. The pairing code appears to be 1234, but running on a mac, so far, I have not gotten it to work. It ID's as an ODBII bluetooth device and functions as an additional serial port. I am trying software from h t t p://w w w.yhasi . com called movi, but am about to give up and switch to windows mode to make sure it really functions.
(Since i am a new poster, i cant post the url correctly)
This thread saved me as well. I tried 0000 and 1234 while repeatedly telling my friend how no device ever uses codes other than those. Thanks!
Thank you! Cd that came with the dongle was broken, and 0000 or 1234 which.usually have worked with other devices, didn't work with this one.
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
So this is yet another thread asking for advice on paring an ODB2 device with the HU. I've searched through this forum and haven't found a resolution.
I've recently purchased a Hondash (http://www.hondash.net), it works perfectly when connected to my mobile phone so I know the device works. The HU can see it but won't pair with it. It sees the device as "HONDASH".
I have Xposed-MTC-Manager installed and the OBD workaround didn't work. In settings.ini, I've tried both:
obd_device=HONDASH
(as suggested here on XDA), and
obd_device = HONDASH
(with spaces as suggested on 4pda.ru)
Neither got it to work.
I've tried pairing through the Bluetooth app and Settings.
I've also tried the workaround using XposedMTC to no avail (I also disabled Xposed-MTC-Manager so there was no clash between the two Xposed modules).
It seems most OBD apps do not like the bluetooth on our headunits as when starting them, they ask to enable bluetooth then when you press Allow, they stop on a message saying something like "turning on bluetooth".
So, is there anything else I could try? Is there a way I can force the HU to pair? Are there any terminal emulator commands which force bluetooth pairing? Are there any modified bluetooth apps which fix?
Did you try to set HU bluetooth security code to match OBD? Default is 0000 and I had to change mine to 1234.
Yes, tried exactly that and still not working. I'm wondering if it's a Bluetooth hardware incompatibility or a ROM issue (currently running Booroondook's 5.1.1 ROM).
CARRisma said:
Yes, tried exactly that and still not working. I'm wondering if it's a Bluetooth hardware incompatibility or a ROM issue (currently running Booroondook's 5.1.1 ROM).
Click to expand...
Click to collapse
I have similar issue like on video: https://www.youtube.com/watch?v=wxI2LqHQrAk.
I have 2 pcs OBDII BT adapter. These work with my 4.4.2. android Samsung mobile. And these have worked 2 years ago with only 4.2.2 OS on the headunit.
I'm using malayk's rom (4_4_4_800X480_RK3066_23_MAL_02_12_2015) now. The BT's is OK, because my mobile phone paired with HU, and the HU works like a headset.
I can't find the pairing process. The HU has found the OBD device, but does't appear the pairing.
It's either a ROM or MCU issue. Xposed-MTC-Manager is supposed to work around this however the module is designed for 4.4.4 not 5.1.1. Replacing mtcmanager.apk with an older version gets some features of Xposed-MTC-Manager to work but unfortunately the Bluetooth work around still doesn't work. I suspect that another file other than mtcmanager.apk needs to be replaced in order for Xposed-MTC-Manager to do it's thing correctly. Currently Xposed-MTC-Manager is trying to patch some code that has changed from what it expects.
CARRisma said:
It's either a ROM or MCU issue. Xposed-MTC-Manager is supposed to work around this however the module is designed for 4.4.4 not 5.1.1. Replacing mtcmanager.apk with an older version gets some features of Xposed-MTC-Manager to work but unfortunately the Bluetooth work around still doesn't work. I suspect that another file other than mtcmanager.apk needs to be replaced in order for Xposed-MTC-Manager to do it's thing correctly. Currently Xposed-MTC-Manager is trying to patch some code that has changed from what it expects.
Click to expand...
Click to collapse
My HU worked well OBD2 BT reader with JY v2.07 MCU and JY Android OS 4.2.2 10102014. I willl try MCU downgrade.
CARRisma said:
Yes, tried exactly that and still not working. I'm wondering if it's a Bluetooth hardware incompatibility or a ROM issue (currently running Booroondook's 5.1.1 ROM).
Click to expand...
Click to collapse
I have done this solution:
If they're not pairing and it's not the adapter name issue, disable all Xposed modules and try pairing. After pairing, you can enable the Xposed modules. Many thanks for Core-Lokt!!!
Now my BT OBDII device was paired with HU. I'm using Malaysk ROM. And Torque Pro works well.
CARRisma said:
So this is yet another thread asking for advice on paring an ODB2 device with the HU. I've searched through this forum and haven't found a resolution.
I've recently purchased a Hondash (http://www.hondash.net), it works perfectly when connected to my mobile phone so I know the device works. The HU can see it but won't pair with it. It sees the device as "HONDASH".
I have Xposed-MTC-Manager installed and the OBD workaround didn't work. In settings.ini, I've tried both:
obd_device=HONDASH
(as suggested here on XDA), and
obd_device = HONDASH
(with spaces as suggested on 4pda.ru)
Neither got it to work.
I've tried pairing through the Bluetooth app and Settings.
I've also tried the workaround using XposedMTC to no avail (I also disabled Xposed-MTC-Manager so there was no clash between the two Xposed modules).
It seems most OBD apps do not like the bluetooth on our headunits as when starting them, they ask to enable bluetooth then when you press Allow, they stop on a message saying something like "turning on bluetooth".
So, is there anything else I could try? Is there a way I can force the HU to pair? Are there any terminal emulator commands which force bluetooth pairing? Are there any modified bluetooth apps which fix?
Click to expand...
Click to collapse
I have the Hondash as well and same scenario as yours it won't pair properly to the headunit but works fine on phones. Headunit sees it as "OBD".
I have another OBD adaptor for another vehicle thats shows up as "OBDII" on the headunit and works fine with Torque.
Have you managed to solve this problem? still trying to get mine rooted Allwinner T3 P2 android 4.4.2.
DROIDLG said:
I have the Hondash as well and same scenario as yours it won't pair properly to the headunit but works fine on phones. Headunit sees it as "OBD".
I have another OBD adaptor for another vehicle thats shows up as "OBDII" on the headunit and works fine with Torque.
Have you managed to solve this problem? still trying to get mine rooted Allwinner T3 P2 android 4.4.2.
Click to expand...
Click to collapse
Hi, sorry for delay, haven't been here since before Christmas. Yes, I got it to work eventually. I sent to Hondash dongle thingy back to the developer and he reprogrammed it so the Bluetooth ID was something that would allow the headunit to pair with it. The default is 'HONDASH' which our headunits do not recognise. As it was so long ago, I can't remember exactly, but I think our headunits only like to pair with devices that have 'ODB' in thier ID? He reprogrammed the it and now it pairs with the headunit.
CARRisma said:
Hi, sorry for delay, haven't been here since before Christmas. Yes, I got it to work eventually. I sent to Hondash dongle thingy back to the developer and he reprogrammed it so the Bluetooth ID was something that would allow the headunit to pair with it. The default is 'HONDASH' which our headunits do not recognise. As it was so long ago, I can't remember exactly, but I think our headunits only like to pair with devices that have 'ODB' in thier ID? He reprogrammed the it and now it pairs with the headunit.
Click to expand...
Click to collapse
Hi mind sharing photo/video of the head unit functioning with hondash? If really the case I'll have to contact the developer to reprogram the dongle.
DROIDLG said:
Hi mind sharing photo/video of the head unit functioning with hondash? If really the case I'll have to contact the developer to reprogram the dongle.
Click to expand...
Click to collapse
Well after all that faffing, I decided having Hondash installed on my headunit is not for me because it's too much out of my line of sight. So It's no longer installed on my headunit. I'm now using Hondash on my previously retired mobile phone which is by the dashboard so more in my line of sight. I've rooted the phone, installed Tasker and setup some fantastic Tasker routines to automate things. If you're interested in doing that, let me know.
CARRisma said:
Well after all that faffing, I decided having Hondash installed on my headunit is not for me because it's too much out of my line of sight. So It's no longer installed on my headunit. I'm now using Hondash on my previously retired mobile phone which is by the dashboard so more in my line of sight. I've rooted the phone, installed Tasker and setup some fantastic Tasker routines to automate things. If you're interested in doing that, let me know.
Click to expand...
Click to collapse
Can you screenshot the hondash on your phone confirming that the name has been changed?
DROIDLG said:
Can you screenshot the hondash on your phone confirming that the name has been changed?
Click to expand...
Click to collapse
Here you go.
{
"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"
}
Try the MyMTCService app from Play Store. That has the Bluetooth ID workaround, maybe it works better than the Xposed modules.
Still in process, this may not work for every remote, especially those will lost pairing after reboot, and I found some remote will disconnect after a few hours and need pairing again, dunno this is bug of shield or anything else
Tested on Sheid TV 16gb 2017, firmware 5.01 (developer)
1. side load this app to your shield: "nRF Connect for Mobile", or any BLE scanner/connect app
2.a scan the remote and press connect
{
"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"
}
2.b when connected, shield tv will ask for pairing
2.c paired and connected but it still not work
3.a adb pull /data/misc/bluedroid
3.b you will see a list of paired device in bt_config.conf, include the 3rd party remote but it will lack most info
Code:
[XX:XX:XX:XX:XX:XX]
Name = 小米蓝牙遥控器
DevClass = 1344
DevType = 2
AddrType = 0
Timestamp = 1486758640
LE_KEY_PENC = a27d02fb2083ba5847f1e4734XXXXXXXXXXXXXXX
LE_KEY_PID = 1731754feb64c60edcd09XXXXXXXXXXXXXXXXXX
LE_KEY_PCSRK = 00000000db21e99ab6XXXXXXXXXXXXXXXXXX
LE_KEY_LENC = ef8ac21724e8fc31837XXXXXXXXXXXXXXXXXX
LE_KEY_LCSRK = 00000000842e019dd2caXXXXXXXXXXXXXXXXXXX
LE_KEY_LID =
Service = 00001812-0000-1000-8000-00805f9b34fb
HidReport = 4d2a0101222e4d2a020122324d2a030122364d2a0002223a4d2ae00322454d2ae10322484d2ae203224b4d2ae303224e4d2ae40322514d2ae50322544d2ae60322574d2ae703225a4d2ae803225d4d2ae90322604d2aea0322634d2aeb032266
HidAttrMask = 0
HidSubClass = 0
HidAppId = 255
HidVendorId = 10007
HidProductId = 12800
HidVersion = 273
HidCountryCode = 0
HidSSRMaxLatency = 0
HidSSRMinTimeout = 0
HidDescriptor = 05010906a1018502050719e029e71500250175019508810295017508810195057501050819012905910295017503910195067508152825fe0507192829fe8100c0
[XX:XX:XX:XX:XX:XX]
Name = 小米蓝牙遥控器
DevClass = 7936
DevType = 2
AddrType = 0
Timestamp = 1486758704
LE_KEY_PENC = fe426d85f40053734a9eXXXXXXXXXXXXXXXXXXXXXXXXX
LE_KEY_LID =
Service = 00001812-0000-1000-8000-00805f9b34fb
3.c
now fill in the miss part, mainly the "Service", and HID part which you can omit some of them, and never change those key nor add any missing key. For service most of them will be "00001812-0000-1000-8000-00805f9b34fb "
It is suggest to copy these info from another device, I copy them from my HTC 10
beware of the order of those line, wrong order may will refuse to work
suggest to use some text editor support unix format (LF for new line) such as pspad
4. after modify push back to shield tv, reboot (I didn't try if turning on/off bt will work or not)
5. refer to this post for key mapping https://forum.xda-developers.com/shield-tv/general/change-3rd-party-remote-key-layout-root-t3548871
for china version of xiaomi box bt remote, 1st version bt remote which use CR2032 will need repairing after reboot and also will disconnect after about 1 day, but it can pair by shield tv, it will say cannot pair for 1st try, just don't touch the remote and let shield pair it again, it will pair mostly in 2~3 try
2nd version of this bt remote without voice (just $4 usd) , which us 2xaaa battery can be pair using the above method, sheild tv cannot search for it, it will not disconnect after shield tv reboot/power off, I am still testing it, hope it will not disconnect after a few hours of using.
Tmall bt voice remote same as xiaomi 1st version bt remote, and the power button is IR, voice will not work
Edit
Sorry, rereading your post, i see were not discussing the same issue, my apologies
Edit2
Although you may have giving me some places i could look into, like the config file locations, reviewing them before pairing, after pairing, and after loss of pairing, so thanks for that
Im having this similar issue on marshmellow full android
Im having no problems with seing and pairing devices, but the shield forgets the pairing when i turn off, then turn on the bluetooth, making me have to repair again, which when you have so many devices to pair becomes a pain.
Ive not tested extensively, but the pairing seems to stick, at least in the first instance of turning bluetooth on and off, as long as the bluetooth device was connected when i turn off the bluetooth
I can test this a bit more, like pair more then one device(ive only been pairing/testing one device at a time), keep one device connected, turn off the bluetooth, and see if the shield remembers all the pairings, or just the one that was still connected, when i turned off the bluetooth
I do hope a solution becomes available, as i rely quite extensively on the shields bluetooth
Researching up on it, seems theres a little issue with marshmallow and bluetoth but not this exact problem, so im stumped, this post, and another on zulus marshmellow thread are the only places ive seen mention of this particular pairing problem, the forgetting your pairings issue
http://www.videomap.it/forum/viewto...d=01cc9900293e5b3a59e3dba77a43f876&start=1000
Lukecastle
'hi zulu,
I was wondering why everytime I turn on the shield from a shutdown. I'd always have to pair my bluetooth devices. For some reason it doesnt remember the already paired devices. Thanks'
Tried to signup to that site to add to lukecastles post, but it wont let me, im a spambot apparently
banderos101 said:
I was wondering why everytime I turn on the shield from a shutdown. I'd always have to pair my bluetooth devices. For some reason it doesnt remember the already paired devices. Thanks'
Tried to signup to that site to add to lukecastles post, but it wont let me, im a spambot apparently
Click to expand...
Click to collapse
Your problem actually the same as some of my bt device and I don't have a solution, it may be a mix of the bt device firmware problem and the Shield bt, every time it happen I saw a GATT disconnect then device refuse to connect again. What I know is some of my device is fixed after a firmware update(the bt device).
Edit:
Saw some similar bug on nexus, may be they are related, need time to keep digging
DummyPLUG said:
Your problem actually the same as some of my bt device and I don't have a solution, it may be a mix of the bt device firmware problem and the Shield bt, every time it happen I saw a GATT disconnect then device refuse to connect again. What I know is some of my device is fixed after a firmware update(the bt device).
Edit:
Saw some similar bug on nexus, may be they are related, need time to keep digging
Click to expand...
Click to collapse
Dont know if this will be any help in your search, but theres a floating/popup/overlay logcat on the playstore called 'logcat extreme' that might be usefull, maybe give you some clues you may understand better then me.
I tend to pause the log, clear it, then unpause right before an action, in this case
1. Turning on bluetooth(with nothing paired) (pause, then save log)
2. Clear log, unpause, pair device, pause, save log
3. Clear log, unpause, turn off bluetooth, pause, save log
4. Clear log, unpause, turn on bluetooth(testing the pairing), pause, save log
Ill probably go over this again more thoroughly if more information comes out that helps me look out for something specific, perhaps this "GATT disconnect " that you speak off
The fact that this issue is happening on the nexus, as you say, seems to indicate that this is an issue with android itself, so im hoping, once xposed comes out for nouget, that this issue will be resolved when i update, which will be fun, seing as my adb/fastboot is not working........hoping flashfire app will do the job in this case, aswell as, hopefully, fix the adb/fastboot, but i digress
Edit
I have a very strong feeling that im gonna turn my device into a door stop when i eventually test/hope/hail mary with flashfire, a new shield purchase may be in my future just hope their still selling the 2015 model when/if i do
banderos101 said:
Dont know if this will be any help in your search, but theres a floating/popup/overlay logcat on the playstore called 'logcat extreme' that might be usefull, maybe give you some clues you may understand better then me.
I tend to pause the log, clear it, then unpause right before an action, in this case
1. Turning on bluetooth(with nothing paired) (pause, then save log)
2. Clear log, unpause, pair device, pause, save log
3. Clear log, unpause, turn off bluetooth, pause, save log
4. Clear log, unpause, turn on bluetooth(testing the pairing), pause, save log
Ill probably go over this again more thoroughly if more information comes out that helps me look out for something specific, perhaps this "GATT disconnect " that you speak off
The fact that this issue is happening on the nexus, as you say, seems to indicate that this is an issue with android itself, so im hoping, once xposed comes out for nouget, that this issue will be resolved when i update, which will be fun, seing as my adb/fastboot is not working........hoping flashfire app will do the job in this case, aswell as, hopefully, fix the adb/fastboot, but i digress
Edit
I have a very strong feeling that im gonna turn my device into a door stop when i eventually test/hope/hail mary with flashfire, a new shield purchase may be in my future just hope their still selling the 2015 model when/if i do
Click to expand...
Click to collapse
Thanks for the app, really helpful. Beside logcat you can also take a look of HCI bluetooth snoop.
a little bit off topic:
When try to stop the shield being discoverable I found that even it stop being discoverable by default bt_addr it will become discoverable by a different bt_addr if you scan for it long enough (about 1~3mins), and there are at least two different bt_addr.
you can try yourself by change the scan mode in bt_config.conf, there also an app call bluetooth settings (by4a.bluetoothsettings) can do that for you, just need to restart after install that app or the setting may not stick
Notes
I tested with another device, bluetooth mouse(which i believed to have a higher bluetooth version then the bluetooth keyboard version i was testing previously), ive been making an assumption, that under bluetooths settings "paired devices", if it comes up empty, then the pairing/s was/were forgotten, but clicking on the bluetooth mouse buttons, to auto connect, brought up a "enter pin popup"(shows up everytime i connect, so its not "fixed"), which connects ok after entering pin, so the pairing was still there, just not showing up in bluetooth settings
So at least i know its not deleted of the system
Search goes on
Edit
Bluetooth keyboard still cant auto connect(needs repairing), unlike the bluetooth mouse(which needs the pin entered every auto connect, which was not previous behaviour)
Although mouse works, the bluetooth "paired devices" sections is still empty, untill i press buttons on the mouse to auto connect
Hopefully someone finds this usefull, i sure hope im not jacking your thread dummyplug
banderos101 said:
Notes
I tested with another device, bluetooth mouse(which i believed to have a higher bluetooth version then the bluetooth keyboard version i was testing previously), ive been making an assumption, that under bluetooths settings "paired devices", if it comes up empty, then the pairing/s was/were forgotten, but clicking on the bluetooth mouse buttons, to auto connect, brought up a "enter pin popup"(shows up everytime i connect, so its not "fixed"), which connects ok after entering pin, so the pairing was still there, just not showing up in bluetooth settings
So at least i know its not deleted of the system
Search goes on
Edit
Bluetooth keyboard still cant auto connect(needs repairing), unlike the bluetooth mouse(which needs the pin entered every auto connect, which was not previous behaviour)
Although mouse works, the bluetooth "paired devices" sections is still empty, untill i press buttons on the mouse to auto connect
Hopefully someone finds this usefull, i sure hope im not jacking your thread dummyplug
Click to expand...
Click to collapse
Enter pin is actually an old pairing method before bt auto pairing. Anyway seems the bluetooth is quite buggy on shield, let hope it will be better for future firmware.
DummyPLUG said:
Enter pin is actually an old pairing method before bt auto pairing. Anyway seems the bluetooth is quite buggy on shield, let hope it will be better for future firmware.
Click to expand...
Click to collapse
Yeah, thats what im counting on when i have the opportunity to upgrade to nouget, hopefully the stock OTA download/OTA flash method works and fixes bluetooth and all my other various issues.
Also, for informations sake, i dont remember that particular bluetooth mouse of mine needing to enter a pin before i started having bluetooth issues, come to think of it, i realise the the initial pairing of my mouse auto pairs still, only after every auto connect does the pin show up
Ive encountered the blutooth/pin code popup many'ya times in the past and, well, quite recently i guess, i had assumed, that it was based on the bluetooth device you were pairing that dictated whether a popup pin would occur, and not so much android, different bluetooth peripherals having different bluetooth versions, some having or not having support for any particular bluetooth authorisation method introduced in higher/lower bluetooth standards.
Maybe part of the problem for me specifically is that my shield is not able to identify/communicate correctly with my devices
Its like you said, buggy ......and weird.......heres to hoping the ota fixes it
So does this remote - http://www.gearbest.com/smart-home-controls/pp_257680.html stay paired after reboot using this method?
GalaxyWhy said:
So does this remote - http://www.gearbest.com/smart-home-controls/pp_257680.html stay paired after reboot using this method?
Click to expand...
Click to collapse
I use the older one which don't have voice and take 2*aaa battery, beware the firmware may different, I had 4 of them and out of 2 behave a little bit different but still stay pair after reboot and don't affect usage
I have this exact remote and It has never even worked for me, does not make a beeping sound and pressing home + back any ideas why this remote wouldnt turn on at all?
hxxp://xxx.ebay.com/itm/HOT-Original-Xiaomi-Mi-remote-control-Apply-to-xiaomi-TV-and-Mi-tv-box-Pro-Cool/311829970277?_trksid=p2047675.c100005.m1851&_trkparms=aid%3D222007%26algo%3DSIM.MBE%26ao%3D2%26asc%3D41375%26meid%3D2cd664f8927e4787a3a56bf779251134%26pid%3D100005%26rk%3D5%26rkt%3D6%26sd%3D222539565729
As I know only the old one will beep, and it should be "home + menu"
my 1st xiaomi remote which using cr2032 will not work very well with shield, may be mine got a outdate firmware
(@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.