Develop Bugs

bluetooth gps receiver problem

I purchased marbella GB-6205 V2.2 for my dopod900 but pairing problem is encountered.There shows ? in the icon. I'm running out of tips. ROM 1.30.230WWE. Somebody got any advice

Dont really have a tip i just wanted to see what people came up with. I am haveing the same problem with my Gsat 359. My issue is with the 8525 and Wayfinder. im on VP3gs offical wm6. Also having issues with some of the menus looking like half circules but that is more an issue with the software.

For both posts, I think that you have to be more specific, not being able to pair a device might have lots of causes, in example:
- Are you sure that your devices are indeed in pairing mode, having them to enter in pairing mode can be tricky sometimes
- Usually any device in pairing mode within range will be detected by the PDA/phone.
- Sometimes the keyboard applet appears just above the passkey request window not permitting to see it (happens sometimes with my universal), also there are at least two "common" paskeys used for bluetooth devices (this doesn't mean that some more could exist), usually "0000" and "8888".
- Are you sure that both (PDA/phone and bluetooth device) devices work? Try to pair another bluetooth device with your PDA/phone and try to pair your BT device with another PDA/phone; defective items are always a possibility.
- You might even have had success to pair your devices, the problem might be the software, see all the post that To_mT_om have generated because of problems with third parties BT GPSs, verify your software and a very practical way of being sure that everything went ok with the pairing is to install the app that usually all BT GPSs have included, normally a very simple app that displays geodesic coordinates or even raw NMEA info.
- Some PDAs/OSs might have the need to "create" another serial port for the new BT GPS in order to be accessed by the software, also see the other posts for this information.
Do you need more info?
Verify all the possibilities, perform all the test mentioned and then be very specific about the exact problem, most of the best gurus (and I'm not talking about me!) ask for a tough research of the forum's posts before asking for something that might have been already answered, I understand them when they say that it is not funny to answer to the same question (in various flavors) several times.
One last thing, it's holidays time, many people could be missing in these days.
Good luck

got mine up and runnning. My problem was software related. Downloaded software from handango and i just wasnt working right. Went to the manufacture website...wayfinder.com and the new software found my gps with no problem.

We've tended to find that simultaneously restarting the BT GPS and PDA at the same time (and often with a battery removal on the GPS) can solve issues where the GPS simply doesn't want to complete pairing.
When this fails, it's usually software related or a corrupted Bluetooth stack / registry settings on the PDA..
Worst case, hard reset the PDA..
Good luck
Andy
www.pressdigital.com.au
Press Digital Support Team

Nexus 5X and Skoda Superb Bluetooth Pairing Problems

I've got a Skoda Superb with Columbus head unit. I've paired half a dozen phones (Nexus One, Galaxy Nexus, Nexus 4, iPhone 5, 2 x Z5 Compact) with it successfully until I got my Nexus 5X.
The procedure is to use the car's multi-functional display to search for a nearby device with the phone at the Bluetooth settings screen and with Bluetooth on. The car displays a 16 digit code made of 4 sets of consecutive numbers, e.g. 3333 4444 5555 6666 which is then entered as a PIN in the handset.
After a little handshaking that's usually the end of it. But the Nexus 5X then wants another PIN entered, but the car continues to give a 'connecting...' message with no PIN displayed. After much trial and error I've found that if I supply the same number again quickly enough it'll sometimes accept it. The car then flashes the PIN - if a different PIN is shown then the phone fails to connect.
Assuming a connection is made the car then prompts to name the device and create a user profile, appears to download contacts etc. I've not yet had time to test fully what functions are and aren't available at this point.
In any event the phone won't reconnect when I leave the car and come back. The car immediately displays a PIN to enter, but it doesn't appear to be attempting to connect as the phone never displays the PIN entry dialogue.
Additionally I get a permanent notification on the Nexus 5X showing the Bluetooth icon titled 'Bluetooth SIM access' and the message 'Request client to disconnect?'. There's a disconnect button on the notification which doesn't appear to do anything, and I can't clear the notification without restarting the phone.
{
"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"
}
I've tried resetting the car's Bluetooth to factory settings, removing it from the phone and trying again.
Any other suggestions please?

Unpairing problems
Hi huntajc,
I had similar problems pairing/connecting to my Audi MMI system. After many attempt, MMI reboots, clearing contacts, removing all BT paired devices, etc. it worked. Don’t ask me what the trick was. But… the doesn’t unpair. I also get the same message in my N5X when leaving and turning off the car. In the top left (!) corner a BT sign appears also with the message 'Request client to disconnect?'. The disconnect button on the notification doesn't appear to do anything. When using the car again the N5X won’t connect. However when turning off and on the BT on the N5X, the `Request client to disconnect?` disappears and the phone pairs again with the MMI system. No idea how to set the N5X such that it unpairs automatically.
Greetings,
Materie62
huntajc said:
I've got a Skoda Superb with Columbus head unit. I've paired half a dozen phones (Nexus One, Galaxy Nexus, Nexus 4, iPhone 5, 2 x Z5 Compact) with it successfully until I got my Nexus 5X.
The procedure is to use the car's multi-functional display to search for a nearby device with the phone at the Bluetooth settings screen and with Bluetooth on. The car displays a 16 digit code made of 4 sets of consecutive numbers, e.g. 3333 4444 5555 6666 which is then entered as a PIN in the handset.
After a little handshaking that's usually the end of it. But the Nexus 5X then wants another PIN entered, but the car continues to give a 'connecting...' message with no PIN displayed. After much trial and error I've found that if I supply the same number again quickly enough it'll sometimes accept it. The car then flashes the PIN - if a different PIN is shown then the phone fails to connect.
Assuming a connection is made the car then prompts to name the device and create a user profile, appears to download contacts etc. I've not yet had time to test fully what functions are and aren't available at this point.
In any event the phone won't reconnect when I leave the car and come back. The car immediately displays a PIN to enter, but it doesn't appear to be attempting to connect as the phone never displays the PIN entry dialogue.
Additionally I get a permanent notification on the Nexus 5X showing the Bluetooth icon titled 'Bluetooth SIM access' and the message 'Request client to disconnect?'. There's a disconnect button on the notification which doesn't appear to do anything, and I can't clear the notification without restarting the phone.
I've tried resetting the car's Bluetooth to factory settings, removing it from the phone and trying again.
Any other suggestions please?
Click to expand...
Click to collapse

huntajc said:
I've tried resetting the car's Bluetooth to factory settings, removing it from the phone and trying again.
Any other suggestions please?
Click to expand...
Click to collapse
I own a Superb myself and had also problems with pairing the device. It prompt everytime to pair the phone..
After i unchecked 'contact sharing', the phone connects without any problems. I hope this will fix your problem too.

Hi, is there anyone else having the same issue? I have got it since I bought this phone on November 2015. It was never resolved by any security update, nor Nougat.
I can make through the paring cycle just by guessing what PIN will BT unit require. It is then paired and will connect automatically, but the connection everytime takes maybe 45 seconds instead of just seconds like with any other phone. Could this be reason to ask for warranty repair?
The other issue that could be caused by the same bad BT is that when I am using Waze on the phone, its voice commands are supposed to go through the Columbus unit's audio. This unfortunately only works when there is and ongoing call. If no call, the command is just lost.

capo56 said:
Hi, is there anyone else having the same issue? I have got it since I bought this phone on November 2015. It was never resolved by any security update, nor Nougat.
I can make through the paring cycle just by guessing what PIN will BT unit require. It is then paired and will connect automatically, but the connection everytime takes maybe 45 seconds instead of just seconds like with any other phone. Could this be reason to ask for warranty repair?
The other issue that could be caused by the same bad BT is that when I am using Waze on the phone, its voice commands are supposed to go through the Columbus unit's audio. This unfortunately only works when there is and ongoing call. If no call, the command is just lost.
Click to expand...
Click to collapse
Yes, I have a similar problem with the Superb's Columbus headset and my Nexus 6P. They pair successfully but cut the mobile data connection so there is a 'no network' message. Sometimes phone calls or texts get through but are not logged on the phone.
I now rarely the use the Bluetooth but use the phone's speakers. Time for a change.
Any help would be most welcome.
Sent from my Nexus 6P using Tapatalk

Android Wear 6.0 and Vehicle bluetooth

So, i have 2 different vehicles that have Bluetooth calling. When i get in my car, the vehicle connects to my phone and i can make and receive calls through the car and the sound goes through the speakers. Now that my watch is connected as a calling device with the new speaker activated, my vehicles will not connect to my phone. The only i can think of around this is to disable the Bluetooth or enable airplane mode on the watch which is a real pain every time i get it my car. Anyone else have this issue and a solution?

Same here, the car will connect to the phone but will then disconnect. This keeps repeating. If I turn watch off, car connects to phone OK.
Sent from my SM-G928F using Tapatalk

Oh, that's bad! But it's somehow also logical. The phone can only be connected to one handsfree/handset device at a time. Even so the car audio is the better choice, the phone does not know this, and will just stay connected to the watch.
Have you tried to connect to the car audio by the BT menu on the smartphone? You car audio is listed under paired devices and you can connect to it manually.
Maybe it will also remember this decision.
---------- Post added at 08:26 PM ---------- Previous post was at 08:16 PM ----------
Just searched a bit on the internet. The problem is not new, as people with headsets and a BT car stereo experienced the same problems in the past, so maybe there is already a solution for this. I quickly searched and found a potential solution by apps, that manage the BT connection and offer prioritization, like this one claims to be capable of: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
Maybe this is also something you may investigate into.
I'm very interested on a solution, because I drive a lot of rental cars and I usually connect my phone to the car stereo (if available).
Completely disconnecting the watch is not an option for me, as one reason for buying the watch was to get quick notifications also when I'm in the car.

foo said:
Oh, that's bad! But it's somehow also logical. The phone can only be connected to one handsfree/handset device at a time. Even so the car audio is the better choice, the phone does not know this, and will just stay connected to the watch.
Have you tried to connect to the car audio by the BT menu on the smartphone? You car audio is listed under paired devices and you can connect to it manually.
Maybe it will also remember this decision.
---------- Post added at 08:26 PM ---------- Previous post was at 08:16 PM ----------
Just searched a bit on the internet. The problem is not new, as people with headsets and a BT car stereo experienced the same problems in the past, so maybe there is already a solution for this. I quickly searched and found a potential solution by apps, that manage the BT connection and offer prioritization, like this one claims to be capable of: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
Maybe this is also something you may investigate into.
I'm very interested on a solution, because I drive a lot of rental cars and I usually connect my phone to the car stereo (if available).
Completely disconnecting the watch is not an option for me, as one reason for buying the watch was to get quick notifications also when I'm in the car.
Click to expand...
Click to collapse
just disable in the bluetooth settings of the watch on the phone the "phone audio" and it works fine again.
Had the same problem that my car connected to my phone and played music, but the calls were still connected with my watch
{
"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"
}

Yeah, but if you disable on the watch, you can't use the speaker that was just activated on the watch to make calls.
I actually found a program called triggers that will disconnect the watch and allow the car to connect.

same issue with bt headphones. Kinda annoying.

Motawa88 said:
same issue with bt headphones. Kinda annoying.
Click to expand...
Click to collapse
Kinda annoying? This should have never left Google like this.

Maybe this googled answer will help: http://superuser.com/questions/3979...tooth-connection-priority-for-various-devices

Scott said:
Maybe this googled answer will help: http://superuser.com/questions/3979...tooth-connection-priority-for-various-devices
Click to expand...
Click to collapse
I tried that. Doesn't help if you are already connected to the watch and get in your car.

Apple watch doesn't have this problem. Google really need to fix this.
Sent from my SM-G928F using Tapatalk

Yes, I have this problem too. I will try to play with BT priority, maybe it will help.

So I tried using triggers and it worked to activate my car bluetooth. However, the sound does not go through my car stereo. I went in and had to disable phone calling on the watch bluetooth in my phone to get my car to work correctly. It sucks to have a speaker on a watch and you can't even use it to make calls because it interferes with other devices. I think the basic fix for this is to have a widget or shortcut on the Watch to enable airplane mode when you get into your car. Right now you have to go into settings and scroll through to get to airplane mode.

All I have to do is pull down the quick settings and choose my cars Bluetooth instead of the watch and it switches just fine

yes, priority do not work.

mgorman said:
All I have to do is pull down the quick settings and choose my cars Bluetooth instead of the watch and it switches just fine
Click to expand...
Click to collapse
This works for me also. For those having the issue here is one option. Use tasker and secure settings plugin. Create a profile in tasker to monitor BT near. Choose your cars BT. Create a task that uses secure setting plugin to connect to cars Bluetooth. Once done whenever your phone sees the cars BT it will connect. Rooting is not necessary.
Sent from my Nexus 6 using Tapatalk

crawrj said:
This works for me also. For those having the issue here is one option. Use tasker and secure settings plugin. Create a profile in tasker to monitor BT near. Choose your cars BT. Create a task that uses secure setting plugin to connect to cars Bluetooth. Once done whenever your phone sees the cars BT it will connect. Rooting is not necessary.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I used tasker and triggers to get my car to connect to my phone. The problem is, as long as bluetooth is enabled for the watch, i don't get sound through my car. I have to actually disable the watch to get sound to work.

dschachm said:
I used tasker and triggers to get my car to connect to my phone. The problem is, as long as bluetooth is enabled for the watch, i don't get sound through my car. I have to actually disable the watch to get sound to work.
Click to expand...
Click to collapse
I'm not having that problem. Might try with secure settings to see if you get a different result. If not it must be a phone or car head unit thing.
Sent from my Nexus 6 using Tapatalk

crawrj said:
This works for me also. For those having the issue here is one option. Use tasker and secure settings plugin. Create a profile in tasker to monitor BT near. Choose your cars BT. Create a task that uses secure setting plugin to connect to cars Bluetooth. Once done whenever your phone sees the cars BT it will connect. Rooting is not necessary.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
dschachm said:
I used tasker and triggers to get my car to connect to my phone. The problem is, as long as bluetooth is enabled for the watch, i don't get sound through my car. I have to actually disable the watch to get sound to work.
Click to expand...
Click to collapse
It seems that bluetooth near is actually working. I never even knew that existed. Hope it continues. Thanks

Can anyone give me a newbies guide to what you're talking about with triggers and tasker and how to configure?
I'm aware of tasker and have used it a long time ago when I used to root my Android devices, but I'm not entirely sure about the config nowadays especially for this kind of thing.

thisispete said:
Can anyone give me a newbies guide to what you're talking about with triggers and tasker and how to configure?
Click to expand...
Click to collapse
+1
Sent from my SGH-I747M using XDA Free mobile app

PX5 HA BT issue

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

Hi, known issue. Refer graser tool and information here

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

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

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

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

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

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

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

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

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

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

Today I was able to try my BT adapter in a friend's head unit which has the Malaysk rom. This of course has the Graser tool as standard.
Unfortunately the symptoms were identical, the unit recognises the BT adapter although shows a phone symbol and pressing pair results in absolutely nothing happening. This was from the BT app, if the same thing was tried from the settings/bluetooth then the adapter appeared named 1OBDII so we used the Glaser tool to add this name plus a few others such as PP-2145 but with no success.
I do not understand enough about the Glaser tool to try anything other than adding new names, there is a line above the name with "cv" written in it what is this?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG][/IMG]
JohnLynn said:
I have HA head unit with 10 inch screen it is using HA_PX5_6.0(20171214) and MTCE_HA_V2.71
I have a problem connecting an OBD2 adapter, the adapter is called Response PP-2145.
Running a scan from the BT app in the head unit discovers the OBD2 adapter but it will not pair. This adapter cost quite a lot and was to replace a very cheap £3 one which works OK but does not find all available pids on the car.
If I search for the old (working) adapter it appears as an OBD symbol, a pairing attempt then asks for the password 1234 and it pairs OK.
The new adapter is found but has a mobile symbol and a pairing attempt does nothing at all. Yet pairing the new adapter to a Galaxy S6 works properly, there is no password asked for it just connects.
Edit forgot to say the factory setting for BT is set to SD-968, there are others but from memory trying to use MD725 (I think) results in no name or password in BT
Click to expand...
Click to collapse
Hi
I have exactly the same problem as you, my Audio Video Nav Unit is a MTCE_MX2_V2.75_1 - Android 6.0.1
I also have a costful OBD reader OBDLink LX that i like very much, the BT discovered it with the phone symbol BUT simply don't get paired. With a cheap ELM327 Obd it works fine, but these cheap readers not always work properly.
I've tried several things but still don't work, if you get a solution post here
I will continue to search...
Good luck

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

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

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

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

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

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

In the market for a new phone and have a Bluetooth question

Hi all, I'm in the market for a new phone, though, that's not what I want to ask. I'm interested in the bluetooth functionality.
What I'd like to know is for all you Xiaomi Mi 6 owners out there - Are you able to have multiple bluetooth devices connected at the same time, just like the S8+? And I'm not talking about dual audio.
To elaborate on the question. I have the leeco le pro 3 and normally have my bluetooth headset everyday. When I jump in my car, the phone connected to the bluetooth car which is expected, however, the phone completely disconnects the bluetooth headset. I just tested out a friends galaxy s8+ and was able to have both bluetooth devices connected at the same time, and "hot swap" between the 2. I'm not sure if this is the result of Apt X technology, android OS version or even the mfr's ROM config.
Can the Mi 6 do that?

Yep, I can do that on my Mi6 - AICP 13.1
The phone is contently connected to my watch (Amazfit pace).
and it connects to my headphones seamlessly.
although i haven't tested 2 BT headset at the same time.
I can test it tonight if it helps

Thank you, yes can you please test it with 2 audio and/or phone channels. In my case, I have a bluetooth car receiver and a bluetooth headset that I want to have connected at the same time, so I can switch between them. I have an old phone that doesn't allow 2 of the same type (phone/audio) channel streams to be connected at the same time. I know that most phones can't stream to 2 at the same time, but I want them to stay connected so I can hot swap.
Below is how my Bluetooth looks when I connect to 2 devices of the same channel. I can't have both phone and audio on both bluetooth devices *connected* at the same time.
{
"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"
}
Below is how my friends Bluetooth settings looks on his s8+ when connected to 2 devices of the same channel. He can have both phone and audio on both bluetooth devices *connected* at the same time

Well, I've played with it a little....
As you can see in the attached picture, I have my Amazfit Pace Smartwatch connected.
JBL BT headset for music
And Sena for calls.
You have to set profiles for each one; you can have two BT connections for music or calls, you have to pick what goes where.
But at a click of a button I can switch between them (is this what you call "hot swap"?)
As far as I know, both the Samsung and the Xiaomi have BT 5.0
So I don't think it's a hardware limitation.
It's also worth mentioning that I'm using a custom rom:
AICP 13.1, stable build, ver 21.05.18, based on LOS 8.1
Sent from my MI 6 using Tapatalk
update:
Hey @R0ttenB4ndit
Just now saw your edit
well, I've done some digging and.... not good
With Android Oreo (I use ver 8.1) I now have the ability to set the AVRCP version to 1.6 (insted of 1.4)
I can also select a variety of Audio Codecs, but no matter what I choose (eg. aptX HD) it wouldn't stick, only SBC works for now.
It's 100% software limitation, just like I said earlier
both SGS8+ and the MI6 have BT 5.0 (and the Pixel2 and OPO5 and others)
but so far, only Samsung has used Android Oreo BT5 abilities
I guess it's a matter of time and ambition from our devs.
BTW, if it help, android P should bring us the ability to connect to 5 devices!
https://www.androidpolice.com/2018/...cted-simultaneously-via-new-developer-option/
Edit2:
well, I stand corrected, it's not a software thing,
https://www.youtube.com/watch?v=T-CPobBQi6E
Samsung did something differently, that is why they can do it while others can't.
sucks....
BTW, ZTE did it too with the AXON M

SM26 said:
Well, I've played with it a little....
As you can see in the attached picture, I have my Amazfit Pace Smartwatch connected.
JBL BT headset for music
And Sena for calls.
You have to set profiles for each one; you can have two BT connections for music or calls, you have to pick what goes where.
But at a click of a button I can switch between them (is this what you call "hot swap"?)
As far as I know, both the Samsung and the Xiaomi have BT 5.0
So I don't think it's a hardware limitation.
It's also worth mentioning that I'm using a custom rom:
AICP 13.1, stable build, ver 21.05.18, based on LOS 8.1View attachment 4506515
Sent from my MI 6 using Tapatalk
update:
Hey @R0ttenB4ndit
Just now saw your edit
well, I've done some digging and.... not good
With Android Oreo (I use ver 8.1) I now have the ability to set the AVRCP version to 1.6 (insted of 1.4)
I can also select a variety of Audio Codecs, but no matter what I choose (eg. aptX HD) it wouldn't stick, only SBC works for now.
It's 100% software limitation, just like I said earlier
both SGS8+ and the MI6 have BT 5.0 (and the Pixel2 and OPO5 and others)
but so far, only Samsung has used Android Oreo BT5 abilities
I guess it's a matter of time and ambition from our devs.
BTW, if it help, android P should bring us the ability to connect to 5 devices!
https://www.androidpolice.com/2018/...cted-simultaneously-via-new-developer-option/
Edit2:
well, I stand corrected, it's not a software thing,
https://www.youtube.com/watch?v=T-CPobBQi6E
Samsung did something differently, that is why they can do it while others can't.
sucks....
BTW, ZTE did it too with the AXON M
Click to expand...
Click to collapse
[*]You have to set profiles for each one; you can have two BT connections for music or calls, you have to pick what goes where.
Yeah that's what I have to do now, because when I connect the second device... the previous device will get completely disconnected from the phone. I have to go in an manually choose which profile goes on what device to have both connected, but that doesn't help me since I can't push (for instance) the answer button and have the bluetooth transfer the call or media over to the specified BT device.
[*]But at a click of a button I can switch between them (is this what you call "hot swap"?)
Do you mean the click of a physical button?? Yes ! that's what I mean as hot swap. When I press a button on one headset, I want the active call or media to be transferred to it automatically. Instead of now I am having to go in and switch profiles, or even disconnect one of the two devices.
[*]So I don't think it's a hardware limitation.
Yeah I am starting to think it's software implemented like you said. Do you think otherwise now?
[*]With Android Oreo (I use ver 8.1) I now have the ability to set the AVRCP version to 1.6 (insted of 1.4)
Not sure what AVRCP is, but does it change anything for you with using 2 bluetooth devices though?
[*]BTW, if it help, android P should bring us the ability to connect to 5 devices!
https://www.androidpolice.com/2018/...cted-simultaneously-via-new-developer-option/
Good to know ! but I can't even connect to 2 devices at the same time ! Does android P do this?
[*]well, I stand corrected, it's not a software thing,
https://www.youtube.com/watch?v=T-CPobBQi6E
Ah, so wait? It is a hardware limitation then???
Thanks so much for your help

R0ttenB4ndit said:
[*]You have to set profiles for each one; you can have two BT connections for music or calls, you have to pick what goes where.
Yeah that's what I have to do now, because when I connect the second device... the previous device will get completely disconnected from the phone. I have to go in an manually choose which profile goes on what device to have both connected, but that doesn't help me since I can't push (for instance) the answer button and have the bluetooth transfer the call or media over to the specified BT device.
[*]But at a click of a button I can switch between them (is this what you call "hot swap"?)
Do you mean the click of a physical button?? Yes ! that's what I mean as hot swap. When I press a button on one headset, I want the active call or media to be transferred to it automatically. Instead of now I am having to go in and switch profiles, or even disconnect one of the two devices.
[*]So I don't think it's a hardware limitation.
Yeah I am starting to think it's software implemented like you said. Do you think otherwise now?
[*]With Android Oreo (I use ver 8.1) I now have the ability to set the AVRCP version to 1.6 (insted of 1.4)
Not sure what AVRCP is, but does it change anything for you with using 2 bluetooth devices though?
[*]BTW, if it help, android P should bring us the ability to connect to 5 devices!
https://www.androidpolice.com/2018/...cted-simultaneously-via-new-developer-option/
Good to know ! but I can't even connect to 2 devices at the same time ! Does android P do this?
[*]well, I stand corrected, it's not a software thing,
https://www.youtube.com/watch?v=T-CPobBQi6E
Ah, so wait? It is a hardware limitation then???
Thanks so much for your help
Click to expand...
Click to collapse
It has been a mini rollercoaster.
To make a long story short:
Right now, with Android 8.1
The mi6 operates just like your 'old' phone.
Not like the s8.
Why is this like this? Is it hardware? Is it software?
I have no idea.
As of right now, I found that a ZTE axon m is supposed the have the same "dual audio" as the s8.
If it's really the case, then it should be a matter of software.
I've downloaded the axon m kernel and in the few days will poke around when I'll have a time away from work.
I've also heard that the LG v30 have dual audio, but haven't looked into it.
If you need to buy a new phone NOW, and you MUST have that ability, then the MI6 is a no go.
This could be a nice project, but like everything here on XDA...I can't give an ETA.
Sent from my MI 6 using Tapatalk

SM26 said:
It has been a mini rollercoaster.
To make a long story short:
Right now, with Android 8.1
The mi6 operates just like your 'old' phone.
Not like the s8.
Why is this like this? Is it hardware? Is it software?
I have no idea.
As of right now, I found that a ZTE axon m is supposed the have the same "dual audio" as the s8.
If it's really the case, then it should be a matter of software.
I've downloaded the axon m kernel and in the few days will poke around when I'll have a time away from work.
I've also heard that the LG v30 have dual audio, but haven't looked into it.
If you need to buy a new phone NOW, and you MUST have that ability, then the MI6 is a no go.
This could be a nice project, but like everything here on XDA...I can't give an ETA.
Sent from my MI 6 using Tapatalk
Click to expand...
Click to collapse
Thanks for the help! For the sake of being clear.... "dual audio" is not the same thing as having multiple Bluetooth devices *connected* simultaneously. "Dual audio" is what Samsung named the feature which streams audio to 2 devices simultaneously. I'm not sure if this is a Samsung thing or not. hopefully you understood what I meant earlier, which it seemed like you did . I don't need audio played on both. I just want to swap between the 2 with the push of a button on the device itself.
The Dual Audio feature has been released with the Samsung Galaxy S8, S8+ & Note8. When two devices are connected via Bluetooth at the same time, the Dual audio feature allows the user to play sound on both devices.
Click to expand...
Click to collapse
I planned on buying the new Xiaomi Mi 7 when it comes out, but the rumored specs show that it has the exact something Bluetooth features as the previous gen which is why I asked here
Thanks again.