Related
dwmcqueen said:
Hello,
I just recently purchased this - http://www.amazon.com/gp/product/B0...tailpage_o04_s01?ie=UTF8&psc=1#productDetails
A couple of notes:
1. It appears to be another HuiFei model - specs all align with what is said in this thread (including the Developer password).
2. MCU says MTCB-GS-V1.91
3. I am having a real hard time having my ELM327 connect - scanning for new Bluetooth devices yields nothing.
4. There is no "Extra Settings" - so not sure where I go to map the physical buttons (I want the Navi button to map to Google Maps).
Other than that, seems to be working nicely.
Click to expand...
Click to collapse
I have the same unit its MCU 2.02 though but only certain BT ELM works.... I found on that works fine... I will include more info in my write up....
antiguangenius said:
I have the same unit its MCU 2.02 though but only certain BT ELM works.... I found on that works fine... I will include more info in my write up....
Click to expand...
Click to collapse
By default, these headunits only recognize and pair with BT OBD adapters that have the name "OBD". I've removed this limitation with the latest experimental release of the XposedMTC module.
makkan00 said:
Bit worrying. I have this unit hardly for 2 months and it has developed another fault.
When I hit speed bumps, it automatically changes to previous track / radio station.
Click to expand...
Click to collapse
It seems that the rotary encoders used for volume and tuning are sometimes susceptible to vibrations/bumps. I've had issues where the volume randomly goes up or down while driving. After spinning the knob up and down a few times it goes away.
agentdr8 said:
It seems that the rotary encoders used for volume and tuning are sometimes susceptible to vibrations/bumps. I've had issues where the volume randomly goes up or down while driving. After spinning the knob up and down a few times it goes away.
Click to expand...
Click to collapse
Thanks. I will try it.
With regards to obd, how do I take out the restriction on obd adapters which my unit can use?
Thanks.
makkan00 said:
Thanks. I will try it.
With regards to obd, how do I take out the restriction on obd adapters which my unit can use?
Thanks.
Click to expand...
Click to collapse
You can either decompile the MTCBluetooth3.apk and Settings.apk, modify the smali files to remove the restriction and recompile, or you can root your headunit (check out the first post), install the Xposed Framework, and install the XposedMTC module.
agentdr8 said:
You can either decompile the MTCBluetooth3.apk and Settings.apk, modify the smali files to remove the restriction and recompile, or you can root your headunit (check out the first post), install the Xposed Framework, and install the XposedMTC module.
Click to expand...
Click to collapse
I have xposed mtc and framework and this is a year later. It still does not see my bluetooth ODB as it is not named ODB. It is named CBT
Shagman68 said:
I have xposed mtc and framework and this is a year later. It still does not see my bluetooth ODB as it is not named ODB. It is named CBT
Click to expand...
Click to collapse
Compatibility also seems to depend on the version of the adapter; the generic ELM327 readers come in many versions. I haven't correlated which versions work and which ones don't, but my adapter, which also shows up as "CBT" is a v1.2, and the override within XMTC does work.
I'm assuming you've already set the XMTC preference to "CBT" and rebooted? Make sure the pairing pin in the stock BT app matches that of the OBD adapter (e.g. 0000, 1111, 1234), and try pairing from within the BT app.
agentdr8 said:
You can either decompile the MTCBluetooth3.apk and Settings.apk, modify the smali files to remove the restriction and recompile, or you can root your headunit (check out the first post), install the Xposed Framework, and install the XposedMTC module.
Click to expand...
Click to collapse
hey @agentdr8 , I've managed to install Xposed, but cannot install the module itself... tried several versions and it still not working on my 4.1.1 Head Unit.
can you help?
agentdr8 said:
By default, these headunits only recognize and pair with BT OBD adapters that have the name "OBD". I've removed this limitation with the latest experimental release of the XposedMTC module.
Click to expand...
Click to collapse
Man i tried that Xposed option and no luck..... its there something specific you need to do? i did the following
- Turned option on Typed Name of ODB adapter.... in my case "Carly Adapter"
- Turned option off
neither worked for me... am i doing something wrong? my HU has passcode set to 1234 which is the same for ODB adapter this one is specially made for BMWs
staticx1 said:
hey @agentdr8 , I've managed to install Xposed, but cannot install the module itself... tried several versions and it still not working on my 4.1.1 Head Unit.
can you help?
Click to expand...
Click to collapse
If you're using a Malaysk rom, the module comes preinstalled, and just has to be enabled in Xposed Installer->Modules. If not, make sure you're installing it to internal storage; some roms default to installing to sdcard and it won't work that way.
xterm305 said:
Man i tried that Xposed option and no luck..... its there something specific you need to do? i did the following
- Turned option on Typed Name of ODB adapter.... in my case "Carly Adapter"
- Turned option off
neither worked for me... am i doing something wrong? my HU has passcode set to 1234 which is the same for ODB adapter this one is specially made for BMWs
Click to expand...
Click to collapse
Try using just "Carly" as the name (it's a string comparison using a String.contains). Leave the option enabled, and then restart the headunit.
i left it as Carly Adapter it worked just needed to reboot after activation of xposed but sadly it soft brick my HU everytime so system enters recovery and erase everything to restore defaults.... this is using Stock pumpkin firmware. So i think i just gonna go ahead and install custom ROM instead
Hi, I', not able to connect to my OBD adapter. It's a Vgate 3 and the bluetooth name is V-LINK. I've the last Malaysk rom (April 2016), I've installed Xposed framework and Xposed bluetooth module. I've tried to set every combination of strings that could match V-LINK (rebooting) but nothing seems to work. I've also set the bluetooth pin to 1234 (matching my adapter pin). My unit is a Pumpkin 1024x600 quad core RK3188. Any help?
Lyhaku said:
Hi, I', not able to connect to my OBD adapter. It's a Vgate 3 and the bluetooth name is V-LINK. I've the last Malaysk rom (April 2016), I've installed Xposed framework and Xposed bluetooth module. I've tried to set every combination of strings that could match V-LINK (rebooting) but nothing seems to work. I've also set the bluetooth pin to 1234 (matching my adapter pin). My unit is a Pumpkin 1024x600 quad core RK3188. Any help?
Click to expand...
Click to collapse
Is your OBD adapter paired to your phone by any chance? If so, unpair it, and try again
Sent from my XT1575 using Tapatalk
brbarnyard said:
Is your OBD adapter paired to your phone by any chance? If so, unpair it, and try again
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Hi, thanks for the reply. I'll try, during my tests it was paired but If i remember well the phone bluetooth was off.
Enyone suceeded in enabling Internet via Bluetooth? (enable BT theathering on phone, pairing HU with phone and enabling HU to use phone Internet connection - that way no need for USB modem in HU if you have internet on phone and you take your phone with you in car as we do most of the time).
I was trying to enable that with my LG G3 phone but it doesn't work.
(I'm using Malaysk ROM, KGL unit type)
Any hints appreciated.
Hi, I just switched on "hotspot" in my Moto G menu then switched on WiFi on Headunit then they just paired up, hope this helps.
Bill.
bilnick said:
Hi, I just switched on "hotspot" in my Moto G menu then switched on WiFi on Headunit then they just paired up, hope this helps.
Bill.
Click to expand...
Click to collapse
Thank you but that is different thing. I wish to use BT specifically.
pa.ko said:
I wish to use BT specifically.
Click to expand...
Click to collapse
Try this app (there is a trial version to test with):
https://play.google.com/store/apps/details?id=com.bluedunx
I haven't tested that app myself as I use a USB 3G dongle.
themissionimpossible said:
Try this app (there is a trial version to test with):
https://play.google.com/store/apps/details?id=com.bluedunx
I haven't tested that app myself as I use a USB 3G dongle.
Click to expand...
Click to collapse
Not working
I searched around and it looks like bug in Android 4.4.4 preventing BT theathering to work (in fact it works but apps cannot use that connection).
Anyone found workaround?
Hi everyone, I have a joying rk3188 1024x600 head unit and recently flashed the most recent malaysk rom. Before the flash, obd dongle would pair fine. Now I cannot get out to connect. I can connect my phone to the headunit, can connect my phone to the obd dongle, but cannot connect the obd dongle to my headunit whatsoever. It shows up in "available devices" and can be clicked then click "yes" to connect, but it doesn't connect.
I've tried to play around with xposedmtc but no luck.
Anyone have any ideas?
Thanks!
did you click enable xposedmtc in xposed?
TRY disable xposed-bt or manager in xposed
and roboot will be done
Yes, all are activated in xposed. And tw0119, I will give that a try.
Malaysk‘s rom Dec.2015 on my JY-HU clould pair fine ,but Feb.2016&Jan.2016 roms could not.
So i try disalbe all Xposed modules ONLY enable Xposed mtc ,OBD dongle works after roboot
Tw0119, perfect, works now. Did you go back and reactivate the modules again or no?
Thank you so much btw!
dannyboy223 said:
Tw0119, perfect, works now. Did you go back and reactivate the modules again or no?
Thank you so much btw!
Click to expand...
Click to collapse
NO,if you reactive the XposedManager module it would be down.
So i think somethings wrong with the Framework,maybe Malaysk could TEST for it
tw0119 said:
NO,if you reactive the XposedManager module it would be down.
So i think somethings wrong with the Framework,maybe Malaysk could TEST for it
Click to expand...
Click to collapse
No XposedBT whit OBD.
Prob is that there are number of overlapping Xposed modules, conflicting with each other and even underlying ROM features.
Until Malaysk and module devs coordinate their activities you have to experiment and make compromises. In order to get something you have to drop something.
I had the same problem: my bluetooth OBD2 / OBD adapter were being detected, but I could not pair them. My OBD2 adapter has a pin number and I was never asked for the pin to pair. Also, the device was being scanned and shown with the phone icon instead of the OBD icon. Had this problem with March and January 2016 versions of Malaysk ROM (which is awesome, btw!). How I solved the problem:
1. Opened the stock bluetooth app, removed the device which already appeared paired
2. Set the default pairing PIN to the PIN of my device
3. Disabled XposedMTC and XposedBT in the Xposed module manager
4. Rebooted
5. Scanned for the device, checked that it appears as OBD (icon) and paired again. No pin was requested, but it paired correctly and it works.
Hope this helps! Cheers,
C.
i have 2 adapters and neither will work for me. one will not pair no matter what combination of things i choose in xposed but works great with my phone. the other adapter works so good i don't even have to put in the pass code when using my deck, but it will not communicate with my 2001 fords ecu.
Hi
Not working bluetooth. Not scaning anything
Which BT chip sellected? WQ BC5 ,WQ BC6, IvtBt,Sd bt, WQ BC6B. My sytem rk3066 arm vortex 1.6 dual core .
April 2016 malaysk rom.
I tryed xposed disable combination but not working bluetooth
Help pls
Sytem starting i see pop-up bt connecting,version2
OBD adapter
Unfortunately I have the same problem with the OBD adapter are connected may not apply to find and get information...
The machine is KLD2-RK3188 1024x600 machine with the latest of Rom Malaysk 21/1/2017 (21 version)
I have tried all the above solutions but still not the OBD program works.
OBD connection Joying
Can somebody tell me where to get to "Xposed module manager" in Joying system please? For OBD bluetooth issue
i had same problem but solved it.
Don't use the bluetooth menu in system settings but use the bluetooth app instead (which came with the rom (android 6)).
Using the bluetooth app search here and here pairing worked without any problems for me, after pairing it worked as normal again.
cheatman said:
I had the same problem: my bluetooth OBD2 / OBD adapter were being detected, but I could not pair them. My OBD2 adapter has a pin number and I was never asked for the pin to pair. Also, the device was being scanned and shown with the phone icon instead of the OBD icon. Had this problem with March and January 2016 versions of Malaysk ROM (which is awesome, btw!). How I solved the problem:
1. Opened the stock bluetooth app, removed the device which already appeared paired
2. Set the default pairing PIN to the PIN of my device
3. Disabled XposedMTC and XposedBT in the Xposed module manager
4. Rebooted
5. Scanned for the device, checked that it appears as OBD (icon) and paired again. No pin was requested, but it paired correctly and it works.
Hope this helps! Cheers,
C.
Click to expand...
Click to collapse
That worked for me. But found also additional tips are needed to check:
1. If adapter name is not OBDII per default then in BT app settings (last tab) set exact name. This option is available in modded BT apps in Malaysk ROM (4.4.4), dunno for other ROMs. So there is no need for any exposed modules, just change adapter name in app.
2. Adapter with correct name can pair even if pin code is incorrect! Looks like paired but will not work in apps. So check that pin code in BT app settings is correct for your adapter.
3. In Torque, if you had any other adapter used before, clean all app data (in Android app info). Also noticed that even after app data cleaning, old Mac address is shown instead of new one paired in BT app. Looks like MCU somehow wrongly saves and provides old, even removed from BT app, adapter Mac address. But new paired adapter is working. So there is some mess with MCU and BT and Torque... Not sure where is the issue, but noticed that latest Torque ver listed something about 'improved listing of BT devices'. So it may be known issue on Torque side....
I had the same problem (obd bluetooth not working) using Pumpkin Android 7.1.2 with malaysk ROM 4.1 and found the following solution:
Go to app settings, select "show system apps" an delete data+cache of all (4 in my case) apps regarding bluetooth.
Then connect your devices again. Enjoy
So i deiced to get the 10" Joying rx3188 unit with android 5.1.1 that recently came on the market. So far I rooted it and got it set mostly how i want, but I discovered an issue with bluetooth. Basic phone pairing and functionality works properly and ive also paired my OBD2link MX unit with it as well for the torque app, which works fine as well. the issue i'm having is that other apps that would use bluetooth, think that bluetooth is disabled on the unit. when i try to have them use bluetooth, they ask if they can turn bluetooth on. Selecting yes hangs the app and i have to force end the app to stop it. Even if i go in to torque, it reads bluetooth as disabled even tough the app itself works fine otherwise.
It seems as if the OS is not properly flagging to apps that bluetooth is turned on as far as i can tell. Is there a workaround for this, or something i can do to signal to apps installed that bluetooth is indeed enabled on the HU?
whitetigerlgt said:
ive also paired my OBD2link MX unit with it as well for the torque app, which works fine as well.
Click to expand...
Click to collapse
whitetigerlgt said:
Even if i go in to torque, it reads bluetooth as disabled even tough the app itself works fine otherwise.
Click to expand...
Click to collapse
Sorry i don't understand, Torque is working for you or not?
But, what's the "bluetooth name" of your device? Because to work properly i think it must be "OBD" or "OBD2", otherwise you have to search an Xposed module that can help you.
I'm having the exact same problem with the same unit also on Lollipop. I've notified the developer in the Forum post below and he is looking into it. This now makes a total of 3 people with the same problem.
http://forum.carjoying.com/thread-52.html
whitetigerlgt said:
the issue i'm having is that other apps that would use bluetooth
Click to expand...
Click to collapse
what apps are you having problems with?
also, what car did you put it in? How does it look? 10 inch screen sounds awesome
I'm having two problems right now. The first is that I am unable to pair my Logitech k810 keyboard, and I am unable to connect to a Bluetooth dongle that is used by my radar detector / laser Jammer with an application called Alp connect. I've found quite a few bugs with this head unit and I'm reporting them all to the developer. It works okay my main concern is that it is quite sluggish and I think that is due to the one gigabyte of RAM and lollipop. I installed it in a 2011 Subaru Impreza
sterod said:
The first is that I am unable to pair my Logitech k810 keyboarda
Click to expand...
Click to collapse
I'm fully on board with the concept "your money your car, do what you want" but what do you use a keyboard for in the car?
Quite often I'm too lazy to unpack my laptop when I have to compose a lengthy email on the go so I prefer to do it with a keyboard rather than try to use the touch screen to bash out a couple paragraphs.
popeye70 said:
Sorry i don't understand, Torque is working for you or not?
But, what's the "bluetooth name" of your device? Because to work properly i think it must be "OBD" or "OBD2", otherwise you have to search an Xposed module that can help you.
Click to expand...
Click to collapse
Torque is working, but if you go to adapter status in torque i shows BT not enabled. And thats the issue, the BT status is off when apps check it. For torque, it does not try to turn on BT to function. other apps do, and when they do, they hang.
I need to somehow flag BT as on for other apps so they dont say they need to turn on BT to work.
CadillacMike said:
what apps are you having problems with?
also, what car did you put it in? How does it look? 10 inch screen sounds awesome
Click to expand...
Click to collapse
apps like tablet talk, or obdlink or solostorm. all think BT is off, and try to turn it on when you want to use the BT obd2 adapter.
its in a Mazda MX-5.
sterod said:
Quite often I'm too lazy to unpack my laptop when I have to compose a lengthy email on the go so I prefer to do it with a keyboard rather than try to use the touch screen to bash out a couple paragraphs.
Click to expand...
Click to collapse
If your objective is to solve the problem get a usb keyboard. They work. If your objective is to get bluetooth keyboards working you might have to wait a long time.
Well, I hope you are wrong as my previous NewsMy NU3001 head unit worked perfectly with it. I'm aware I can use a USB keyboard. In any case I'm happy the developer is willing to try and fix it. What is your source for claiming it will be a long time for it to be fixed?
Also to add to this, im also unable to pair my qstarx 10hz BT gps unit.
It may be helpful to post your Bluetooth concerns in the same thread as mine on the Joying Forum I linked to above so that the developer is aware it's not just me and may encourage him to work on this more quickly.
Just popped my head in over there. I was hoping that peeps here would know of a trick or flag for the OS to make all apps think BT is on. then they could get past the check and just access BT, kinda like what the torque app does.
Yeah if someone finds a way to do that I'd be interested to know how as well. Slightly off-topic did you try installing a custom recovery or the Xposed framework on this unit? I have tried and failed many different types of attempts to do it on this unit.
sterod said:
Well, I hope you are wrong as my previous NewsMy NU3001 head unit worked perfectly with it. I'm aware I can use a USB keyboard. In any case I'm happy the developer is willing to try and fix it. What is your source for claiming it will be a long time for it to be fixed?
Click to expand...
Click to collapse
My source? Joying didn't write the software.
And what relevance does that have to the speed at which the issue can be resolved? It seems that you are just being defeating for no purpose. The developer is willing to help and he has expressed that desire in many Communications I've had with him so far. I prefer to be optimistic and that he has the right people to contact to resolve the issue
sterod said:
Yeah if someone finds a way to do that I'd be interested to know how as well. Slightly off-topic did you try installing a custom recovery or the Xposed framework on this unit? I have tried and failed many different types of attempts to do it on this unit.
Click to expand...
Click to collapse
no. i just have it rooted so far with supersu installed. what feature in xposed could be used to help here?
None that I can think of I was just curious if you had been able to install Xposed. I am curious as to how you were able to install SuperSU, as I was only able to install King root.
sterod said:
And what relevance does that have to the speed at which the issue can be resolved? It seems that you are just being defeating for no purpose. The developer is willing to help and he has expressed that desire in many Communications I've had with him so far. I prefer to be optimistic and that he has the right people to contact to resolve the issue
Click to expand...
Click to collapse
http://forum.xda-developers.com/wiki/Generic_Android_Head_Unit/MCU_Explained
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?