Related
I've searched all over for this and I haven't found a solution. I've even decompiled APKs and deodexed the bluetooth odex searching for some clue on any way to change this, but I haven't found anything.
I've actually found a workaround in my particular case, but I'm still curious as to why this is happening and how no one has noticed...
So my Galaxy S3 will not pair with a bluetooth SPP device that has no passcode. I've paired with devices that support SSP without a passcode, but I can't pair with insecure devices. The reason I am trying to do this is because I need to stream GNSS data to a GPS receiver. The receiver is a Navcom SF-3040. For anyone searching, the workaround was to change to the PIN on the device to something other than "no pin". It was a pain in the ass though considering I can't find any 64 bit driver for this receiver and had to find a 32 bit Windows PC to use.
But my question still remains and I'm curious if anyone knows anything about this. After I successfully paired my phone with the receiver, I deleted the profile off my phone and I deleted the PIN from the receiver again just to reset it and see if it would work, but it didn't. The phone would still ask me for a PIN even when the device didn't have one, and there's no option to continue without inputting a PIN. Inputting any standard PIN like "0000" or "1234" didn't work. The only way to pair my phone with the receiver was to set a PIN for it.
So I have an Eonon GA1312 Single din (RK3188).
I have been having two bluetooth issues. All have been troubleshot by disabling and enabling/deleteing data/cache of Bluetooth app, different settings and "off" in factory settings for bluetooth tab and a reload of malasyk rom after a factory reset.
Bluetooth will always show every device it sees. I have 6 Devices under "available devices". 2 I know of (game pad and OBD). 4 were because things were in range when scanning. They persist through everything. It's so weird.
Secondly, the ODB, while off is "available", but once conmected it jumps to "paired" devices and connects no problem. My game pad (nes30 pro to test the viability of bluetooth media control without buying one) is there whether in range, on, or not, and if I try to connect, I tap it, I am asked if I want to connect, and it does nothing.
My cellphones connect fine.
I read all over about some bluetooth limitations but found nothing documented on tje wiki or in the forum.
Any help? Sorry if repost, I thought I made a thread but it says it isn't there and I have no move/deleted notices.
Bump for justice.
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 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?
The problem is to connect Bluetooth on a Moto Z Play Android 7.1.1 patchlevel 2/2018 (current in reteu, was same result with Android 6.0.1 12/2016) with a Volvo XC40 car.
The first pairing with Bluetooth succeeds for a second. Then, nearly immediately, both displays (car and mobile) show reconnecting for about 10 seconds. It has a connect for a fraction of a second, and then is reconnecting and so on.
Trying flight mode and then only Bluetooth enabled on the mobile did not help. IIRC it showed some message about "My Volvo Carnull not bonded" (the name of the car for Bluetooth is "My Volvo Car" and some message with typo, something like "conecnting not successful". After that I rebooted, result was the state before with reconnecting.
Did try this several times. Also did try to reduce the amount of Bluetooth access types the car tries. There are 4 connected: phone, audio, internet, contacts. Did also not help.
Has anyone an idea how to get a successful connection or what the cause of the problem is? Did search for similar problems with Bluetooth in cars, but could not find anything (except for that hint with flight mode which did not help).
What I tried by now:
- Flight mode, only Bluetooth (as already mentioned). No change
- Remove all bluetooth connections. Pair new. No change
- Delete data for sytem app "Bluetooth Freigabe". No change
All other bluetooth connections are working fine. Another Moto Z Play using Android 7.0 (01/2017) is working flawlessly with that car. Strange for me is that it didn't work on 6.0.1 in the same way it does now fail on 7.1.1, but the other Moto Z Play using 7.0 is connecting stable.
Still the question: Does anyone have an idea how to get the connection working?
Factory reset?
I see that you deleted all bt connection but do you have some apps that are using bt? Like for smartwatch, headphones...?
I have Amazfit and watch must be connected to be able to pair a new device. Drow me crazy first time when I had that problem. I thought that car audio is broken, then phone... After pairing, watch doesn't have to be connected to reconnect.
Sent from my KFSUWI using Tapatalk
Zeljko1234 said:
Factory reset?
Click to expand...
Click to collapse
I was afraid this reply could come. When doing a factory reset, I do following: Pack /data/media somewhere because Nandroid omits this. Backup all partitions using twrp. Backup all apk using adb. Export SMS. Export contacts. Screenshots of the launcher screens. All this takes about 2-3 hours. Then I struggle a week until my device behaves like before. I'd be willing to do it if I saw a reason why it could help.
Zeljko1234 said:
I see that you deleted all bt connection but do you have some apps that are using bt? Like for smartwatch, headphones...?
Click to expand...
Click to collapse
Headphone, yes, there is August EP650 configuration tool that is not necessary. Thank you for the hint, will try it. Also I read somewhere it may help to delete cache partition, that's also worth a try before doing factory reset. Maybe I'll wait for Oreo before trying factory reset, could be they fixed some bug there.
Edit: BatOn which shows Bluetooth battery for external devices could also be the culprit.
Zeljko1234 said:
I have Amazfit and watch must be connected to be able to pair a new device. Drow me crazy first time when I had that problem. I thought that car audio is broken, then phone... After pairing, watch doesn't have to be connected to reconnect.
Click to expand...
Click to collapse
That's a strange behavior indeed. Amazfit seems to do something wrong.
It doesn't get any better if you upgrade to Oreo, I've been having problems with my Moto Z play disconnecting and reconnecting to the radio in my Corolla constantly ever since I went up to nougat. To be honest I just bought a good pair of headphones and stopped using the radio. Good luck though, if someone finds something that helps let me know.
I'm using bt with car audio, headphones, smartwatch... No problems at all, except one with Amazfit. And that is related to their bt implementation, not Moto fault.
Sent from my KFSUWI using Tapatalk
Seems the last action to remove Bluetooth related apps was the right one . There were two apps installed:
1. BatOn showing the state of battery of connected Bluetooth device
2. August configuration app for August EP650 headset
Removed both as they are usually not needed and it seems to work now. Will see later if it only worked for the short test I did today (currently I try to avoid driving because of an injury) or if it keeps stable.
Good, you didn't have to factory reset after all
Sent from my XT1635-02 using Tapatalk