bluetooth connectivity: Bug found - chefs take note!

[Guest veehexx]

bug found in post 10

i'm having connectivity issues trying to connect to an elm327 bluetooth OBD adaptor on my car.

the elm327 is working fine to a laptop.

i have sucessfully setup the BT pairing and setup TORQUE app to work correctly. however the bluetooth connection cannot be established.

since this seems to be an issue between my SF and the 327, does anyone have similar experiences or maybe a workaround?

i'm currently on the bladevillain 1.1.0 ROM.

bluetooth connectivity between my SF and a nokia phone are fine.

Edited December 25, 2010 by veehexx

[Guest admanirv]

S2000s are crap I have one mate pm me or I'll forget.

[Guest veehexx]

been googling me, eh? :( deffinately not an S2000 issue, even though it is JDM.

it also definately looks like a phone issue; laptop to 327 is working fine.

going from my WM6.5 handset, the elm327 is detected as a regular com port, and i had to manually set wm6.5 to allow the com port service via that pairing.

no such options seem to be available on android; not knowing too much about bluetooth, what device reports which service is enabled/disabled? seems like i might need to tell android what Bluetooth service runs via that pairing.

i've had enough of the cold weather; got a 12v PSU connected to the elm327 so it powers up and allows pairing, just no actual data flow from car ECU.

i know theres a few threads around stating the SF has issues with bluetooth, so is there any debug software i can use to grab data and pass it onto a developer - might be able to find a fix for the bluetooth issues....?

[Guest Phoenix Silver]

i have had issues with eclair 2.1 and bluetooth (phone <----> PC)

issues solved when i have installed Froyo 2.2

don't know if this help

[Guest veehexx]

thanks for that, Silver - i'll try 2.2 just as a test.

wont be permanent due to the issues with lockscreen, but its certainly worth a test :(

[Guest oh!dougal]

it also definately looks like a phone issue; laptop to 327 is working fine.

going from my WM6.5 handset, the elm327 is detected as a regular com port, and i had to manually set wm6.5 to allow the com port service via that pairing.

no such options seem to be available on android; ...

i know theres a few threads around stating the SF has issues with bluetooth, so is there any debug software i can use to grab data and pass it onto a developer - might be able to find a fix for the bluetooth issues....?

Your vehicle-engine-debugger just wants a com port connection.

That isn't a standard android feature.

Especially over Bluetooth.

I doubt its mega complex, but its far from standard.

Its not an "issue".

Its non-standard functionality that you would like.

Just like people wanting to hook devices needing BlueTooth 2.1 onto the SF's current BlueTooth 2.0

What software were you hoping to run on the phone to talk to that com port?

Edited December 24, 2010 by oh!dougal

[Guest Phoenix Silver]

Your vehicle-engine-debugger just wants a com port connection.

That isn't a standard android feature.

Especially over Bluetooth.

I doubt its mega complex, but its far from standard.

Its not an "issue".

Its non-standard functionality that you would like.

Just like people wanting to hook devices needing BlueTooth 2.1 onto the SF's current BlueTooth 2.0

What software were you hoping to run on the phone to talk to that com port?

SF has bluetooth v2.1 with A2DP :(

[Guest veehexx]

'torque' app.

specifically went for torque and the elm327 as it works fine on other android handsets.

it could be down to the 2.0 and not 2.1 bluetooth support (going from what you say; i havent researched it yet) - maybe the elm327 doesnt support 2.0?

that does seem a tad weird though - SF is a new phone, bluetooth2.1 has been out for ages, surely it should have 2.1? (or specifically, 2.1+edr)

[Guest oh!dougal]

'torque' app.

specifically went for torque and the elm327 as it works fine on other android handsets.

...

The app seems to try to handle the whole of the phone end of things ... (so its probably for the developer to sort out)

Selecting the adapter with Torque

* Launch Torque, and go into the applications settings menu

* Scroll down the list of items until you see 'Connection Type' in the list. Make sure this is set to 'Bluetooth'

* Scroll down to the bluetooth preferences section, select 'Choose Bluetooth Device' and select the adapter you paired with earlier.

* Torque is now setup, and should connect to the adapter. To speed things up you might want to quit the app and restart it

Where does it crap out for you?

[Guest veehexx]

found the issue!!

bluetooth drivers on (seemingly) all the cooked roms!

torque is the major OBD app for android, however there are some others like 'my OBD-II reader'. i used this to determine if it was a phone or app issue. connectivity issues the same on both apps so its obviously a phone issue.

so the roms i've tried:

blade villain 1.1.0 (i have a feeling i tried the rls4 too, but not 100%)

r7 de-orangeated rom

alpha3 of 2.2

stock orange (b05 release)

all but the orange rom had issues. in other words, the stock orange rom is working 100% fine with torque! ;)

TORQUE does have know issues with the the ERD79 bluetooth drivers. although i think thats a general bluetooth issue being drivers, and not soly related to torque itself.

hopefully the chefs here will see this thread, and take note of the drivers they use.

@oh!dougal - it crapped out when TORQUE (or any app that tried to talk with the elm327), tried to connect via bluetooth. it just couldnt find it.

i setup the elm327 as normal; go into android settings > bluetooth > create a pairing between phone and the device. this sucessfully completed. when a program attempts to use that pairing, this is where it fails.

i'm gonna try my bt headset now, see if the low quality issue is still present!

thanks for the help guys; you've asked questions/put sugestions forward i didn't think of :(

Edited December 25, 2010 by veehexx

[Guest oh!dougal]

found the issue!!

bluetooth drivers on (seemingly) all the cooked roms!

...

so the roms i've tried:

blade villain 1.1.0 (i have a feeling i tried the rls4 too, but not 100%)

r7 de-orangeated rom

alpha3 of 2.2

stock orange (b05 release)

all but the orange rom had issues. in other words, the stock orange rom is working 100% fine with torque! :(

...

hopefully the chefs here will see this thread, and take note of the drivers they use.

@oh!dougal - it crapped out when TORQUE (or any app that tried to talk with the elm327), tried to connect via bluetooth. it just couldnt find it.

i setup the elm327 as normal; go into android settings > bluetooth > create a pairing between phone and the device. this sucessfully completed. when a program attempts to use that pairing, this is where it fails.

i'm gonna try my bt headset now, see if the low quality issue is still present!

...

Bizarre!

The difference between 05 and Seb's de-orangeated r7 (based on 08) in particular is very odd indeed.

I suspect that the theme of the day is FroYo, so nudging folks about BT might best be left for a while!

[Guest veehexx]

your right - it does seem weird. first thing i did was search the page for 'bluetooth', to see if anything came up relating to updated versions - i dont think any of the cooked roms mentioned bluetooth changes at all!

just seen the froyo thread!

thats good news :(

i've got a working solution, so i'd rather see 2.2 being worked on than my issue ;)

see if an official 2.2 will work with the elm327...

Edited December 25, 2010 by veehexx

[Guest admanirv]

Pm me on s2k torque works fine on modaco alpha 4.

[Guest Torque Monster]

I have the same issue with SS5 on Blade with ELM327!

Did anyone find a solution for this issue!?

[Guest veehexx]

no fix for newer roms that i've found. i've tried alot of the main stream roms.

i've dropped back to official orange 2.1 rom.

i did try modaco r9 (orange B05 build, de-oranged and updated software) but that had the same issue. i guess with a day or 2 more testing, i could probably track it down to a specific product.

right now, i'm suspecting it's down to rooting the phone (busybox/permissions?). the modaco r9 core files claim to be the same as the Orange B05. i cant see how an app can cause bluetooth issues (espeically the ones im using), and rooting seems to be the main thing i havent done on the orange rom yet.

aside from move-to-sd and a slight lag in the apps menu (barely noticable), it's barely noticable from 2.2.

i am trialing roadsync/touchdown with the view to buy for business exchange sync too.

[Guest toyotahilux]

I remember reading this a while ago, I also have a bluetooth elm327 (one of the generic models that are sold on ebay) and it worked fine for me on the stock 2.1, the Modaco 2.1 and flibblesan's 2.2 r6-r11b. Have not yet tested since upgrading to CM7, so I can't confirm it works there.

The only difference I noted between 2.1 and 2.2 was that in 2.1, I could connect while the engine was off and then start normally. With 2.2, I have to have the ignition on, but engine off to connect, then it will connect fine and I can start the car. Also, I am using torque.

Seems a little strange. :mellow:

[Guest veehexx]

that does seem weird, i've been using flb 11b and couldnt get it to connect at all.

bluetooth pairs (says it's paired but not connected; which is correct), open torque, and it would refuse find it.

i am currently using a 12v power supply to power the dongle outside of the car so i've not tried (or though) about ignition position. might be worth reflashing with 2.2 and trying it in the car.

[Guest toyotahilux]

Just been out to the car to test CM7, and it reacts exactly the same as FLB did for me. If you try with the ignition off, it connects to the obd adapter, thne just cycles through protocols. If I quit Torque, put the ignition on, re-open Torque, it connects almost immediately. Not sure why it differs from 2.1, but that may be worth a try for you. :mellow:

[Guest veehexx]

yeah, i found something like that last night; very intermittent and flaky trying to connect with the dongle. flb 11b did connect a few times though, just not good enough for use.

i'll stick on Orange 2.1b05 untill the phone dies or i get a deal on a newer device that i cant refuse. it'd be nice for 2.2, but a luxury i can live without.

although with that said, Parrot have an android headunit due out very soon. maybe it's worth an upgrade so i can rely on the HU for torque usage.

[Guest toyotahilux]

I'm sorry I cannot be of more help.

Offtopic, that headunit looks pretty nice, might be a nice alternative to the mini-itx car PC I had been planning.

[Guest ricky302]

Running 2.2 MoDaCo Custom ROM for the ZTE Blade r12 and using a cheap ebay ELM 327 ODB2 adapter with the free version of Torque form the market.

Have tested and reset DTCs on a few different vehicles, 2004 Nissan Primastar, 2005 Vauxhall Combo and a 1999 Volvo V70.

Worked on all, but the ignition must be on or the vehicle running.

Hope that helps.