Hi
Quite a nice peace of software, but with some defect. 1. If i send the comm log it will goes through email but you forgotten to pre- fill it with your email and i must say that after 4 hours searchin yet i do not know to which email send it too. Please help because the software goes frozen when connecting to CBT bluetooth and i have LG W620 droid 1.5 thx.
Cl
Ps
I have the paid torque if that makes any software differences. Thx

Hi sorry you've had a hard time trying to find my email

The LG W620 is a bit of an odd phone - I've never seen it before so I'm guessing it is unique to France.

The app should have automatically filled out the email address for you when you tried to send the debug (thanks for trying!), some older installations of Android had an issue where this field was not filled. I will amend the code to put the email address in the plain text part of the message so that in future people will be able to see it.

if you send the debugs after trying to connect to the adapter to torque@prowl.org I'll have a look at what is going on for you.

Ian

Sorry, just to correct the phone model
LG GW620
Cl

in my case, I paid the torque, but not the voltage gauge is working, why?
my veichle is a peugeot 206+ or 207 in Brazil, thanks.

Hi, i’ve a big problem. I tried to use torque on my Samsung spica with OBD bluetooth. It’s work with my dad’s car: Honda model Civic FD2009 but it doesn’t work with my car: Mitsubishi lancer Model CK4 (year 2000) + engine type 4G92.

Some technician told me that Mitsubishi and Nissun use the different protocal from the others (honda and etc.).

Please update your protocal data with mitsubishi.
I’m looking forward to use torque with my car on spica with hope.

I can't get Torque working on my HTC Magic with Android 1.5, is 1.5 now unsupported?

This is the error message I get:
Device Info:
---------------
Brand: htc_europe
Board: sapphire
Device: sapphire
Build id:
htc_europe/htc_magic/sapphire/sapphire:1.5/CUPCAKE/98222:user/release-k
eys
Model: HTC Magic
Product: htc_magic
Tags: release-keys
Type: user
Id: CUPCAKE
Version: 1.5
SDK: 3
UserBuildId: CUPCAKE.eng.u70000.20091208.215718
Application version: 1.1.23
Fast mode: true
Disable Speed adaption: false
1281468698004 **** Connect requested, commsThread=null ****
1281468698008 **** OBD Comms thread starting ****
1281468698033 **** Connecting to OBD via bluetooth ****
1281468698197 **** Connecting to OBD via bluetooth... ****
1281468698380 **** Connecting to: 00:0D:18:B2:22:1B ****
1281468698410 *** class
it.gerdavax.android.bluetooth.BluetoothException:it.gerdavax.android.bl
uetooth.BluetoothException: Can't connect to device 00:0D:18:B2:22:1B
***
it.gerdavax.android.bluetooth.BluetoothException: Can't connect to
device 00:0D:18:B2:22:1B

it.gerdavax.android.bluetooth.LocalBluetoothDevice$BluetoothSocketImpl.
connect(LocalBluetoothDevice.java:559)_
it.gerdavax.android.bluetooth.LocalBluetoothDevice$BluetoothSocketImpl.
(LocalBluetoothDevice.java:510)_
it.gerdavax.android.bluetooth.LocalBluetoothDevice$RemoteBluetoothDevic
eImpl.openSocket(LocalBluetoothDevice.java:323)_
org.prowl.torquefree.comms.bluetooth.gerdavax.GerdavaxBluetoothInterfac
e.connect(GerdavaxBluetoothInterface.java:40)_
org.prowl.torquefree.comms.OBD$CommsThread.run(OBD.java:555)____Causedb
y_Can't connect to device 00:0D:18:B2:22:1B
it.gerdavax.android.bluetooth.LocalBluetoothDevice$BluetoothSocketImpl.
connect(LocalBluetoothDevice.java:555)_
it.gerdavax.android.bluetooth.LocalBluetoothDevice$BluetoothSocketImpl.
(LocalBluetoothDevice.java:510)_
it.gerdavax.android.bluetooth.LocalBluetoothDevice$RemoteBluetoothDevic
eImpl.openSocket(LocalBluetoothDevice.java:323)_
org.prowl.torquefree.comms.bluetooth.gerdavax.GerdavaxBluetoothInterfac
e.connect(GerdavaxBluetoothInterface.java:40)_
org.prowl.torquefree.comms.OBD$CommsThread.run(OBD.java:555)_
1281468698517 *** class java.lang.NullPointerException:null ***
null org.prowl.torquefree.comms.OBD$CommsThread.run(OBD.java:556)_
1281468702565 **** Connecting to OBD via bluetooth... ****
1281468702637 **** Connecting to: 00:0D:18:B2:22:1B ****
1281468702855 *** class
it.gerdavax.android.bluetooth.BluetoothException:it.gerdavax.android.bl
uetooth.BluetoothException: Can't connect to device 00:0D:18:B2:22:1B

Nope, it should still work - it seems that Torque can't see your OBD device - check your bluetooth is turned on and that you have the correct device setup in the preferences (and also the correct PIN for the device).

Depending on the version of android, 1.5 may ask twice for the pin - make sure it's correct both times.

The program does not work for me. Or I am doing something wrong. I sent email with debug log. Thanks

Phone: Samsung Galaxy S (I 9000) and bluetooth ELM327
Auto: 2000 BMW 318 (E46) Europe
P.S. Sorry for my english

@piemmm: I Gave up, rooted my phone and installed Cyanogenmod 5.08. Now it works fine, so I bought the payed version which also works fine. Thanks for the help anyway.

Quote from Aisiur on August 13, 2010, 21:06
The program does not work for me. Or I am doing something wrong. I sent email with debug log. Thanks

Phone: Samsung Galaxy S (I 9000) and bluetooth ELM327
Auto: 2000 BMW 318 (E46) Europe
P.S. Sorry for my english

Hi there,

Did you ever solve your problem? I have a similar setup and similarly aged car and am having the same problems.

Cheers,
J

I downloaded Torque on an HTC incredible, PLX blue tooth interface, 2003 Porsche Turbo. Some functions worked when first installed (torque, RPM) but stopped functioning after the first day. Some never worked (boost, manifold pressure, speed, ambient temp). Right now all that works is HP, coolant temp and acceleration functions. Is there an update. Or should I reload the proggy and re-pair the devices.
Thanks, Duane

Hi

Displays working once or intermittently is usually a sign of using a faulty ebay adapter - unfortunately it's not something I can sort out programatically

Once a display has worked once, then you know the ECU supports it so it should work all the time. Torque checks twice when starting if the PID responds correctly (so it knows if it is supported) but a faulty adapter gets in the way of that check causing Torque to think the PID requested from the ECU doesn't work

Hiya, Downloaded the free app to try it on my cars; using bluetooth elm327 ODB-II.

Altezza RS200 (JDM) Cannot find the ECU, trying a few protocols and then loops
Nisasn 350z (JDM) finds the ecu but can't read or delete error codes (says there is none etc)
Volvo S60T5 2002 Finds the ECU but cannot read or delete error codes (says there is none but I've got lights on it and know there's codes to erase) ALso does not show boost / psi.

Anything I can do to get these working? (suggestions?)

Cheers
Anders

99 Dodge Dakota. It connects to the device but not the computer. I tried it this morning and never got anything. Tried a few times tonight and only once somehow it updated once. Worked pretty good all day today with my 01 Firebird at the racetrack..

This is a debug file for the developer. If you have a problem, it would be really cool if you could take the time to add a description of what your issue is and I will have a better chance of fixing any bugs in Torque(if possible).
Many thanks!

Device Info:
---------------
Brand: Samsung
Board: SGH-I897
Device: SGH-I897
Build id: Samsung/SGH-I897/SGH-I897/SGH-I897:2.1-update1/ECLAIR/UCJH7:user/release-keys
Model: SAMSUNG-SGH-I897
Product: SGH-I897
Tags: test-keys
Type: user
Id: ECLAIR
Version: 2.1-update1
SDK: 7
UserBuildId: ECLAIR
Application version: 1.2.46 Boost fix setting for Mitsubishi ECUs, Fix for Android battery monitor incorrectly labelling Torque as a high battery user, NVIDIA Tegra2 tablet support, Check the changelog in the developer website forums for more information
Fast mode: false
Disable Speed adaption: false

1290296932761 --> OK
1290296932770 OK
1290296932913 OK
1290296932988 OK
1290296933246 OK
1290296933294 NO DATA
1290296933457 **** Protocol 0 was not successful ****
1290296933457 **** Sending reset sequence ****
1290296933558 ELM327 v1.4
1290296936060 ATE0
1290296936108 --> +OK
1290296936112 OK
1290296936164 OK
1290296936226 OK
1290296936390 OK
1290296936442 OK
1290296936685 ?
1290296936744 OK
1290296936828 NO DATA
1290296936990 **** Protocol 1 was not successful ****
1290296936990 **** Sending reset sequence ****
1290296937090 ELM327 v1.4
1290296939593 ATE0
1290296939635 --> +OK
1290296939637 OK
1290296939684 OK
1290296939729 OK
1290296939873 OK
1290296939918 OK
1290296940171 ?
1290296940254 OK
1290296940315 CAN ERROR
1290296940419 **** Protocol 6 was not successful ****
1290296940419 **** Sending reset sequence ****
1290296940519 ELM327 v1.4
1290296943021 ATE0
1290296943053 --> +OK
1290296943064 OK
1290296943107 OK
1290296943160 OK
1290296943313 OK
1290296943348 OK
1290296943601 ?
1290296943637 ?
1290296943680 OK
1290296943742 BUS INIT: ...OK
1290296946606 --> +4100BE3EB810
1290296946788 **** Protocol 3 appears to work. ****
1290296946789 OK
1290296946835 3
1290296946868 ?
1290296946911 ?
1290296946943 3
1290296946995 ?
1290296947057 4100BE3EB810
1290296947538 **** Checking how many ECU(s) we have in the system... ****
1290296947538 **** headersOn=false fl=3eb810 ll=1 ****
1290296947538 **** Exiting header test loop ****
1290296947538 **** ll=1 fl=4100be3eb810 ho=false feu=null ****
1290296947538 OK
1290296947580 411C02
1290296948058 NO DATA
1290296948408 410442
1290296948862 410581
1290296949239 NO DATA
1290296949589 410B3D
1290296949981 410C2374
1290296950392 410D75
1290296950777 NO DATA
1290296951132 410F4F
1290296951520 410EC2
1290296951910 411140
1290296952323 NO DATA
1290296952672 4114987E
1290296953064 41158CFF
1290296953443 NO DATA
1290296953790 NO DATA
1290296954129 NO DATA
1290296954493 NO DATA
1290296954831 NO DATA
1290296955169 NO DATA
1290296955519 NO DATA
1290296955909 NO DATA
1290296956279 NO DATA
1290296956624 NO DATA
1290296957007 NO DATA
1290296957379 NO DATA
1290296957737 NO DATA
1290296958095 NO DATA
1290296958518 NO DATA
1290296958873 NO DATA
1290296959247 NO DATA
1290296959607 +OK
1290296973908 OK
1290296973953 OK
1290296974016 OK
1290296974170 OK
1290296974213 OK
1290296974487 OK
1290296974546 SEARCHING...
1290296979577 --> +UNABLE TO CONNECT
1290296979587 **** Protocol 0 was not successful ****
1290296979587 **** Sending reset sequence ****
1290296979687 ELM327 v1.4
1290296982191 ATE0
1290296982256 --> +OK
1290296982268 OK
1290296982320 OK
1290296982386 OK
1290296982562 OK
1290296982602 OK
1290296982848 OK
1290296982914 NO DATA
1290296983078 **** Protocol 1 was not successful ****
1290296983078 **** Sending reset sequence ****
1290296983178 ELM327 v1.4
1290296985680 ATE0
1290296985726 --> +OK
1290296985736 OK
1290296985780 OK
1290296985814

Sorry its hard to post from my phone. Through email it wouldn't let me type anything. Hopefully that was enough info. I think it cut some of it off . Its the full version of torque if that matters. Its probably suppose to but it pops up with the 'is your ignition on, can't connect to ecu ' error.

Thanks
Aaron

Hm, thats looks like you have a busted bluetooth stack on your phone, though because it's been posted on the forums I'm missing some of the information (the forum removes stuff near left chevron characters

If you could send a debug via email I'll have more of a chance of understanding what is going on, though I would be looking to see if there is a firmware update available for your phone

Ian

I'm a noobe and may be missing the obvious but I'm getting no data on boost, coolant and throttle among others. I'm using PLX Wiki bluetooth and a Nexus One on a 2010 Volks Jetta TDI. Are there things specific to Volks that I could enter or am I just doing something studpid? I have tried disabling ELM327.

BTW Torque does not seem to like it when you run it from the SD card on the Nexus. I had to transfer it back to the phone before it would see the ECU.

Thanks in advance for any help.

I have a Samsung Acclaim, just bought your app and a bluetooth adapter, this one here. http://cgi.ebay.com/ebaymotors/ws/eBayISAPI.dll?ViewItem&item=290503377338&viewitem=&sspagename=STRK%3AMEWNX%3AIT I plug the adapter in and I get a red light and a few yellow lights flashing, then just the red light. The app says connecting to bluetooth. It seems to be connected, when I unplug it I get a error message. I unplugged my MAF to get a DTC code, but when I check it says no codes. I also get no live data. I sent a log file. Is my problem that I missed a setting, or is it possible the bluetooth adapter is not working? I tried this on 2 different cars, a 1997 Bonneville and a 2005 Montana.

Was able to connect one time. Looks like a bad adapter. Should have spent the money on a good one.