Develop Bugs

Bluetooth OBD Adapter not connecting after malaysk rom

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

Car kit Bluetooth problem, help pls :(

Hi everyone,
So I bought my HTC 10 a month ago.
Yesterday I took one of my cars, which I haven't driven for a long time, and tried to pair my phone with the car kit. For the record, I have a Parrot Mki9200 installed, since the car's kit did not have BT.
Now the weird part:
- I search the device - OK
- I pair the devices - everything still OK
-after that, it is supposed to instantly connect with the unit and then download my contacts. Long story short, it cannot connect, no matter what. I tried many times but all that happens is I keep waiting until I get an error from the phone " unable to connect" and then something like "make sure that your devices are one, etc".
I could really use some help on this. I even made a factory reset on the Bluetooth unit just to eliminate any conflicts. I called the authorized service in my country and they told me it should be a problem with the phone.
The weird thing is that my M8 connects flawlessly (on Android 6.0), so does a Huawei P9 lite on Marshmallow, so do all the other devices.
Any help?? The last thing I want is to make a factory reset on the phone and make no difference whatsoever.
Is there any way to reset the BT settings on the phone without factory reset? Any other way to fix it or even find the cause?
FYI, on 1.90 firmware currently, no root.
Any help will be highly appreciated, since I cannot imagine what else I can do with a new phone and no option to connect it in my car.
Thanks in advance,
Cheers,
Thanos
Sent from my HTC 10 using Tapatalk

Nobody???
This is what I am getting btw
{
"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"
}
Sent from my HTC 10 using Tapatalk

I had the same problem with pairing the device with my sony srs-x5 bt speaker.Got no luck,tried cleaning dat and cache,didn't help;and did a factory reset.Taht fixed it.This happened to me once on stock rom,now I am on custom without any connection problems.

Did you pair it without problem but was not able to connect??
Thnx
Sent from my HTC 10 using Tapatalk

thanito said:
Did you pair it without problem but was not able to connect??
Thnx
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
Yes,it was paired but not connected.I got the same error message.

ordeniz said:
Yes,it was paired but not connected.I got the same error message.
Click to expand...
Click to collapse
A few hours ago I finally found the culprit of the problem, just to let anyone know if they have the same issue.
When you are requested to enter the pairing PIN, a bit below there is an option to allow the BT unit to download the contacts, which is selected by default as always.
All phones never have a problem with that.
Anyhow, this time I deselected this option and guess what, it instantly connected!
Afterwards I selected again this option in settings and now everything works like a charm, it connects instantly every time and the contacts are properly synced.
Best regards,
T.
Sent from my HTC 10 using Tapatalk

Hi thanito,
Thanks for the hint ! I had the same problem, your comment was very helpful, I could connect my phone. Although phone works fine and contact are correctly synced, I'm not able to connect the device in Media Audio mode.
The Bluetooth in the car shows "Audio connected". In the device I see only Phone Audio and Contact Sharing. I unpaired and paired it again unsuccessfully.
Do you have an idea how to correct the problem?
Thanks for your help
Fred

Do you have the same car kit unit? Did you try to enter the settings of the paired device and select media audio?
Sent from my HTC 10 using Tapatalk

thanito said:
Do you have the same car kit unit? Did you try to enter the settings of the paired device and select media audio?
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
Hi, yes is the same car kit. It went suddenly wrong, I didn't change any settings. I tried to unpair and pair it many times.
When I'm pairing the device I can't select media audio. I'm only asked if I agreed to sync the contacts.
Something strange: when I get a call whatsapp, Soma or Google Duo, I can hear it trough the car Bluetooth for few second then it cuts.
I don't see how to add the Media Audio to a paired device.
Moreover, I don't have Media Audi problem when I connect the HTC10 to the MINI Bose Bluetooth. It works perfectly
Car kit works properly with my Samsung S6 Edge: Phone Audio, Audio Media & Contact sync.

FredMD11 said:
Hi, yes is the same car kit. It went suddenly wrong, I didn't change any settings. I tried to unpair and pair it many times.
When I'm pairing the device I can't select media audio. I'm only asked if I agreed to sync the contacts.
Something strange: when I get a call whatsapp, Soma or Google Duo, I can hear it trough the car Bluetooth for few second then it cuts.
I don't see how to add the Media Audio to a paired device.
Moreover, I don't have Media Audi problem when I connect the HTC10 to the MINI Bose Bluetooth. It works perfectly
Car kit works properly with my Samsung S6 Edge: Phone Audio, Audio Media & Contact sync.
Click to expand...
Click to collapse
Check the photo attachments to see the option in settings ?
Sent from my HTC 10 using Tapatalk

thanito said:
Check the photo attachments to see the option in settings
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
Hi,
See my picture: Audi... = Car Kit, MINI Bose = Music Bluetooth player.
In the options for the paired Audi, I don't have Media Audio and can't select this option. few weeks ago it was ok and suddenly, the Media Audio option disappeared. I can't set it again.

FredMD11 said:
Hi,
See my picture: Audi... = Car Kit, MINI Bose = Music Bluetooth player.
In the options for the paired Audi, I don't have Media Audio and can't select this option. few weeks ago it was ok and suddenly, the Media Audio option disappeared. I can't set it again.
View attachment 3866658
Click to expand...
Click to collapse
I see..
Did you try unpairing/deleting stored device from both devices?
Usually in factory car kits you get the option to delete the paired device from the memory.
When done, try to find again the phone from the car kit or the car kit from the phone, uncheck the option for the contacts, then recheck it and hope that you are asked to allow media audio access, contact access, etc. I remember that I am prompted for these every time I pair the phone with a new BT device
Sent from my HTC 10 using Tapatalk

thanito said:
I see..
Did you try unpairing/deleting stored device from both devices?
Usually in factory car kits you get the option to delete the paired device from the memory.
When done, try to find again the phone from the car kit or the car kit from the phone, uncheck the option for the contacts, then recheck it and hope that you are asked to allow media audio access, contact access, etc. I remember that I am prompted for these every time I pair the phone with a new BT device
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
Hi, I tried all options, pairing/unpairing/deleting devices, etc... no way.
I finally decided to reset (factory) my phone HTC10...
Now it works fine, Phone Audio, Media Audio & Contacts Sync options are visible and connected successfully...
Many thanks for your support

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.

Help me with my Dasaita PX5 MTCE 8.0 Unit

Hi XDA Gurus,
Recently purchased a Dasaita MTCE PX5 unit running Oreo 8.0. Upgraded to the latest MCU and software package straight away.
I just have a few issues and some advice that I was hoping to get from you guys.
Issues that I have..
1. Radio app or easy connection auto launches when I boot up my head unit - Is there anyway I can disable this.. searched and found a thread that mentions downloading startup manager and disabling it from there.
2. When both my OBDLink MX device and iPhone is paired to my headunit via Bluetooth, sound crackles and sometimes my OBD monitoring apps have intermittent disconnection to my OBD. Is this a common issue when 2 devices are paired.
3. Dashcommand app needs to be closed via task killer along with torque before it connects and works properly. Could this also be related to an app like torque auto starting in the background..
Need your recommendations..
1. Should I root my device via kingoroot? What’s the advantages.
2. Should I install Malaysk rom, what are the advantages. If my issues above can be resolved without custom rom I probably don’t need to buy if installing malaysk rom is beneficial then I will go for it.
3. How do I get more control over my device, I feel the settings are too basic for advanced functions.
Appreciate any feedback you guys can give me because I really like my carwebguru interface that I created and if 2 Bluetooth devices paired doesn’t play nice together then I’m happy using the CarPlay dongle that I should be receiving soon.
{
"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"
}
Thanks

KidCastro said:
Hi XDA Gurus,
Recently purchased a Dasaita MTCE PX5 unit running Oreo 8.0. Upgraded to the latest MCU and software package straight away.
I just have a few issues and some advice that I was hoping to get from you guys.
Issues that I have..
1. Radio app or easy connection auto launches when I boot up my head unit - Is there anyway I can disable this.. searched and found a thread that mentions downloading startup manager and disabling it from there.
2. When both my OBDLink MX device and iPhone is paired to my headunit via Bluetooth, sound crackles and sometimes my OBD monitoring apps have intermittent disconnection to my OBD. Is this a common issue when 2 devices are paired.
3. Dashcommand app needs to be closed via task killer along with torque before it connects and works properly. Could this also be related to an app like torque auto starting in the background..
Need your recommendations..
1. Should I root my device via kingoroot? What’s the advantages.
2. Should I install Malaysk rom, what are the advantages. If my issues above can be resolved without custom rom I probably don’t need to buy if installing malaysk rom is beneficial then I will go for it.
3. How do I get more control over my device, I feel the settings are too basic for advanced functions.
Appreciate any feedback you guys can give me because I really like my carwebguru interface that I created and if 2 Bluetooth devices paired doesn’t play nice together then I’m happy using the CarPlay dongle that I should be receiving soon.
Thanks
Click to expand...
Click to collapse
Don't run Dash command and Torque at the same time. This may be causing your Bluetooth problem with the crackling noise. So choose one or the other. I prefer Torque over any other OBD software.
As for the unit running easy connection at startup, once it's started go into the option menu on easy connection and disable the option for auto start.
I'm using a PX5 unit on 8.1 without said problems.
Hope this helps fella.
Sent from my LYA-L29 using Tapatalk

Tbizzness said:
Don't run Dash command and Torque at the same time. This may be causing your Bluetooth problem with the crackling noise. So choose one or the other. I prefer Torque over any other OBD software.
As for the unit running easy connection at startup, once it's started go into the option menu on easy connection and disable the option for auto start.
I'm using a PX5 unit on 8.1 without said problems.
Hope this helps fella.
Sent from my LYA-L29 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply... I’m running them independently, never at the same time... that causes issues for me too.
When I run torque + phone at the same time I get crackling.
Easy connection doesn’t have an option within the app settings to stop it running at startup. Do you mean within App Info in android settings?
Sent from my iPhone using Tapatalk

KidCastro said:
Thanks for the reply... I’m running them independently, never at the same time... that causes issues for me too.
When I run torque + phone at the same time I get crackling.
Easy connection doesn’t have an option within the app settings to stop it running at startup. Do you mean within App Info in android settings?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Hi
It's in the app itself. I will double check later on mine and post exactly what to do. But being it's only 6.10am and -5 degrees it's too cold to be looking now [emoji3587][emoji3587]
Sent from my LYA-L29 using Tapatalk

Sorry for you, the Dasaita , has audio problems caused by hardware (sound crackles) a lot of us have the same problem (looks like it has a shielding problem on the hardware)
*Wifi had (hiss sounds when downloading from the internet), I solved It changing the horrible wifi antenna.
*Some other has sound crackles when the unit is reading from the usb devices (usb dongles, cameras and other things).
*Some other has blank sound when they are calling from the bluetooth.
*Some other has blank sound and static when playing music.
Till now Dasaitia does nothing to resolve this problems. Almost all PX5 units from diferent brands has the same problem.
Do not try to root, it will kill your device (Dasaitia says that this thing is not rooteable)
Inside the option menu you can turn off the autostart.