Thread Rating:
  • 1 Vote(s) - 1 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Pair OBD2 on Android car stereo
#81
(11-30-2017, 09:32 PM)kiltym Wrote: But the unfortunate thing is vendors advertise BT4.0, which doesn't convey the meaning of what they actually support (since there are multiple variations now).  And I agree, it is a vendor issue, not a specification issue.  But it perhaps could have been done a bit more "clean" such that the vendors couldn't be so ambiguous, and poor consumers like us actually knew what we were getting.

Anyway, back to topic, the net result is the Joying unit will support BT 4.0 "classic", but not LE.  

So now I need to sort out what the dongle actually supports, just buy the BT 3.0 version.

Like I said, I BLAME CHINA.
They are the vendors, and no matter HOW CLEAR you are with your specifications, they'll FUCK IT UP.

In this application, there is no benefit to going over 3.0. With 3.0, you are guaranteed that it is "classic".
Reply
#82
Response from vendor about iCar Pro OBD dongle I referenced. Also nice to see they responded fairly clearly.

"1) For iOS : support BLE mode only
2) For Android : support classic BT4.0"

So, it should be OK, but obviously trying it is the only way to know.
Reply
#83
(12-01-2017, 03:54 PM)kiltym Wrote: Response from vendor about iCar Pro OBD dongle I referenced.  Also nice to see they responded fairly clearly.

"1) For iOS : support BLE mode only
2) For Android :  support classic BT4.0"

So, it should be OK, but obviously trying it is the only way to know.

That's not clear at all, and could actually suggest extreme ignorance on their part.
In fact, ANDROID supports LE just fine! Its just THIS DEVICE that does not (even though its specifications say that it does).
Reply
#84
(11-23-2017, 09:24 AM)TheDarkEngineer Wrote: Just a quick post about pairing ODB2 devices:

- I bought an ELM327 2.0 or whatever they're called.
- 1234 or 0000 or you name it never worked.
- That was because I set the PIN of Joying bluetooth to another number.
- I set it again to 1234.
- I could pair the device by entering 1234 when prompted to do it.
- I changed Joying's PIN again.

Yep. Stupidest thing EVER. It took me forever to figure out that the DEFAULT PIN in the JOYING has to match the one for the bluetooth adapter.
Reply
#85
(12-06-2017, 04:37 PM)braddman Wrote:
(11-23-2017, 09:24 AM)TheDarkEngineer Wrote: Just a quick post about pairing ODB2 devices:

- I bought an ELM327 2.0 or whatever they're called.
- 1234 or 0000 or you name it never worked.
- That was because I set the PIN of Joying bluetooth to another number.
- I set it again to 1234.
- I could pair the device by entering 1234 when prompted to do it.
- I changed Joying's PIN again.

Yep. Stupidest thing EVER. It took me forever to figure out that the DEFAULT PIN in the JOYING has to match the one for the bluetooth adapter.

Definitively the most important information on this whle thread. I spent two days trying to pair my OBDLINK LX without success. Finally found this thread and voila, it works.

So, easy answer is to set the PIN within the BT settings to (settings menu from the Bluetooth app) to the same value as the pairing code. It is 0000 by default, so change to 1234 if that is right. THis and the code you enter must be the same.
Reply
#86
(12-22-2017, 08:12 AM)EX460 Wrote:
(12-06-2017, 04:37 PM)braddman Wrote:
(11-23-2017, 09:24 AM)TheDarkEngineer Wrote: Just a quick post about pairing ODB2 devices:

- I bought an ELM327 2.0 or whatever they're called.
- 1234 or 0000 or you name it never worked.
- That was because I set the PIN of Joying bluetooth to another number.
- I set it again to 1234.
- I could pair the device by entering 1234 when prompted to do it.
- I changed Joying's PIN again.

Yep. Stupidest thing EVER. It took me forever to figure out that the DEFAULT PIN in the JOYING has to match the one for the bluetooth adapter.

Definitively the most important information on this whle thread. I spent two days trying to pair my OBDLINK LX without success. Finally found this thread and voila, it works.

So, easy answer is to set the PIN within the BT settings to (settings menu from the Bluetooth app) to the same value as the pairing code. It is 0000 by default, so change to 1234 if that is right. THis and the code you enter must be the same.

There's a better way, which is to set the system property persist.service.bdroid.ssp=true, which will fix the pin prompts.
Reply
#87
Hello!

Has anyone been able to pair a PLX Kiwi3 to a JY-JM001N2.
The Bluetooth app sees the Kiwi, and when I try connecting it says Paired, however the link beside it stays "broken".

I've tried using both Torque and DashCommand with no success.

Any input would be appreciated!

Cheers,
Nick
Reply
#88
(01-09-2018, 03:02 PM)nick-nhs Wrote: Hello!

Has anyone been able to pair a PLX Kiwi3 to a JY-JM001N2.
The Bluetooth app sees the Kiwi, and when I try connecting it says Paired, however the link beside it stays "broken".

I've tried using both Torque and DashCommand with no success.

Any input would be appreciated!

Cheers,
Nick
I'm getting this same thing. I have a ELM327 Mini and trying to pair with JY-UMS03P2 (octa core). I have followed everyones steps, but no matter what i do, it will say 'device connected', but the chain link stays broken and torque continues to try to turn bluetooth on or won't connect. If i change the code to 0000 or something else, it says it couldn't connect. My phone has no problem connecting to the HU, so i'm at a bit of a loss. 

Does anyone have any ideas?
Reply
#89
(01-11-2018, 12:06 PM)Spalf Wrote:
(01-09-2018, 03:02 PM)nick-nhs Wrote: Hello!

Has anyone been able to pair a PLX Kiwi3 to a JY-JM001N2.
The Bluetooth app sees the Kiwi, and when I try connecting it says Paired, however the link beside it stays "broken".

I've tried using both Torque and DashCommand with no success.

Any input would be appreciated!

Cheers,
Nick
I'm getting this same thing. I have a ELM327 Mini and trying to pair with JY-UMS03P2 (octa core). I have followed everyones steps, but no matter what i do, it will say 'device connected', but the chain link stays broken and torque continues to try to turn bluetooth on or won't connect. If i change the code to 0000 or something else, it says it couldn't connect. My phone has no problem connecting to the HU, so i'm at a bit of a loss. 

Does anyone have any ideas?

I bought exactly the same unit (UMS03P2) and the same ELM327 Mini. I have the same problem and tried everything too : bluetooth obd2 does not connect. I looks like it pair : I get the same message : 'device connected' but can't see it in Torque. Furthermore, Torque say "bluetooth not enabled". phones BT connections are ok. I suspect torque is using the standard bluetooth stack while those kind of units use their own implementation...

I have 2 others running problems : 

- wifi show no network after wake up, I have to reboot the unit, then wifi is ok.
- the radio RDS AF function (Auto follow the same program radio among different frequencies broadcasted) does not work as expected : When enabled, it select the more powerful frequency of any program instead of the more powerful frequency of the listening program.

Did you have the same bugs ? I'm looking for solutions too. may be we can open a new thread for this unit ?
Reply
#90
Issues with ODB2 here as well. I can connect the EM327 mini bluetooth dongle and Torque also sees it, but the connection is very unstable. Torque doesn't seem to stay properly connected, shows error reading the ECU and has a 'fault' counter increasing. When connecting the dongle to my phone everything works as expected. I'm on the December ROM, previously on the July (or May, not sure) ROM I had no issues.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)