Hi all,
i am runing my trinity with WM6 and AX3l's rom. my issue is that i cant connect to my car stereo which is a pioneer DEH-P55. My trinity see's the stereo and gives the option for hands free but the stereo cant detect the trinity. my device is visible to others but the stereo wont pick it up. Any suggestions for a fix on this would be appreciated.
thanks
corm
maybe you have to push a button on your radio to activate first time pairing, that was the solution for my bluetooth headset.
(pairing from both sides)
just a suggestion, maybe it helps.
Try the Jetware bluetooth extension it has a 30 day trial and worked for my Alpine headunit its at http://www.jetwaremobile.com/
Thanks for the replies, but still no luck. I can pair other phones to the stereo but not this. Are there any settings that i may need to activate on the device that i am missing? its abit infuriating as i need to get this up and running as soon as.
rgds
Corm
activated "receive all incoming beams" ? its in settings/connections/beam
its already activated stormyb but thanks again for helping.
I always had problems using bt and irda...
I never succeed send/receive any file using my pc (my pc irda always worked fine with others devices). Beam enabled on commManager and on settings "receive all incoming beams".
When I try to connect (pair) using (htc) BT I get this error: the connection failed or the passcode is incorrect...
---
One time I tried to send a file to a nokia phone and I needed 30 min to succeed: restart phone, restart BT, restart beam, restart phone, restart nokia, restart BT, restart, restart, ....
Now I'm using the radio 1.46.00.11, rom eLiAs2.11wwe (before I was radio 1.38 and udk rom) and when I pair from htc, on pc I don't receive the pin request. If I pair from pc, I see the request for pin no htc but when I type it: "the connection failed or the passcode is incorrect".
Only one time I was succeed pair (and saved on device list), I typed 3 times the pin code, but after I can't transfer files...
From pc, I see the htc on the device list, if I try the ftp service, htc ask me: "xxx wants to connect with your device using bluetooth. Do you want to add XXX to your device list?" I answer yes but when I insert the pin, the pc give to me this error: "error establishing the connection"
If i try the voice gateway, after type the pin on htc I get this error on pc:
"the remote device closed the connection"
Using this last rom, when I try beam a file, I can't see my pc irda (using the udk rom I can to see but without success), I only see my pc BT but always "failed" the connection.
Nobody has the same problem?!
What bluetooth comms are you using, windows or Widcomm's?
I installed widcomm onto my laptop as I was suffering the same problems as you mention and I couild not get a bluetooth serial port setup either, once installed and restarted the pc then I just powered up both BT's and set the phone to visable and the laptop found it straight away with all the services and could setup the serial port.
I seem to recall there are numerous problems with most BT's when using the default windows drivers etc..
HTH's
hi, I'm using widcomm...
I didn't test again a bt headphone, but I have problems trying to connect to a nokia phone for example (n95, n73).
The irda never works... I tried too with a nokia phone and a remote control software for wm6... nothing...
All ok using headset BT...
I installed blueSoleil BT driver and now it is ok.
same ppc, same rom, same problem with my bt bury in the car and with other ppl's triyng to bt connect to my ppc. i can "see" them they can "see" me but there is no transmission TO me. I can send.
i am using the bt phone (bury) but onlt when I initiate the connection. i think it's a rom bug.
I just bought a Holux M-241 Bluetooth GPS reciever to work in conjunction with my Vogue (CDMA HTC touch), I've tried to follow the instructions provided to create a device relationship, but the instructions were written to connect to a WM5 device whereas my touch is WM6 and I keep on getting hung up when it asks me to enter a passcode.
This is the first time I've tried to use bluetooth with my touch and it doesn't mention anything about passcodes in the GPS setup instructions. I've tried entering both the P/N and the S/N numbers written on a sticker on the back of the M-241, as well as my device password, but it always tells me that "the passcode is incorrect" and then it drops the bluetooth connection from both the system tray and the M-241.
I must be doing something wrong, I would really appreciate if someone has any advice on this situation.
- Sam
Try to use "0000" or "1234" wich are often the standard codes.
I got a similar problem: My HTC Wizard recognises my Bluetooth mouse (HID) and it also pairs. My mouse works without passcode and it Pairs without entering one.
Though, when it comes to register the device as an HID Device after Pairing, WM aks for the Passcode again. This time, the "next" button stays grey until anything is entered. As my mouse works WITHOUT a passcode, I cannot register it the right way.
Is there any solution to adding an HID device without passcode to my wizard?
When using GPS in WM6 make sure the built-in GPS feature in "programs" is diabled. I had problems with my Globalsat BT-359, it wouldn´t pair and it turned out to be the built-in feature that was making a hard time. It was somehow on by default and when I diabled it I could pair on first try.
Just a thought.
on my hermes w/ WM6 i pair it using the (passcode from documentation) then I use 0000 as the passcode when prompted.
I have a different GPS but usually 0000 is the passcode
thanks for the help everybody!
"0000" was the passcode.
I'm a taxi driver and being able to pair my GPS to my Touch to find the shortest routes has changed the way I drive.
All the best,
- Sam
Holux M-241 don't work after pairing
Hi, I paired my Holuix M-241 ith the XDA-Exec, authorized it, created the outgoing COM port as explained on the manual, BUT openning google maps, it don't get current position, I WHAT I have to do?
Please, HELP .
Thanks
passcode
on my hermes w/ WM6 i pair it using the passcode from documentation then I use four zero as the code when prompted.
I have a bluetooth dongle attached to my PC running Windows
When trying to pair it with my Desire, the PC displays one passcode, the Desire another. As such, I can't get them to pair.
Normally the PC auto selects the code, then the phone asks you to type it in. But here the phone is displaying a message asking if the device displaying the code xxxxx can be connected, so I can't change the code on either device and so cant pair.
Any ideas?
Cheers.
Bluetooth
I'm having kind of the same issue, i cant seem to transfer the files/pics/music to another device.......it searches then stops......... can sumone please help? ta
I've searched all over for this and I haven't found a solution. I've even decompiled APKs and deodexed the bluetooth odex searching for some clue on any way to change this, but I haven't found anything.
I've actually found a workaround in my particular case, but I'm still curious as to why this is happening and how no one has noticed...
So my Galaxy S3 will not pair with a bluetooth SPP device that has no passcode. I've paired with devices that support SSP without a passcode, but I can't pair with insecure devices. The reason I am trying to do this is because I need to stream GNSS data to a GPS receiver. The receiver is a Navcom SF-3040. For anyone searching, the workaround was to change to the PIN on the device to something other than "no pin". It was a pain in the ass though considering I can't find any 64 bit driver for this receiver and had to find a 32 bit Windows PC to use.
But my question still remains and I'm curious if anyone knows anything about this. After I successfully paired my phone with the receiver, I deleted the profile off my phone and I deleted the PIN from the receiver again just to reset it and see if it would work, but it didn't. The phone would still ask me for a PIN even when the device didn't have one, and there's no option to continue without inputting a PIN. Inputting any standard PIN like "0000" or "1234" didn't work. The only way to pair my phone with the receiver was to set a PIN for it.
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?