Hi!

Both apps use the same bluetooth connection code. So if the lite version works, then Pro version should definitely work as well

The adapter will only allow one connection to it (from an app/device/laptop) at a time, then it will ignore all other connection attempts. Make sure that you haven't got something else connecting to the adapter

Also, check the settings (Vehicle profile, and General settings) to make sure you have told Torque what adapter to use

I've just tried the paid app on my other phone(Samsung Galaxy Ace 2) running rooted Gingerbread, and it works fine.

My first phone(Samsung Galaxy S 3) is running CM10.1, which is Jellybean. So maybe it's a rom issue. Still if both free and paid use same BT code, I don't understand how the free works yet paid doesnt.

What can I do to help out in case it is the app (or prove it isn't)?

Edit: I did check the settings BTW

I have the same issue.. 🙁

I have yet to try any 4.2 ROM that will connect to my adapter. That's why I'm still running CM 10.0

Edit: sorry, should specify I have a d2att sgs3

Hi!

There are a couple of 3rd party/enthusiast ROMS that are bugged, but if it's working for you in the lite version it should definitely work in the pro as it's the same bluetooth connection code.

In this case, it's very important! to know that the adapter will only accept one app/device connecting at a time, then will ignore all other connection attempts from any other device or app.
Make sure there are no other devices trying to connect to the adapter (this includes laptops which may automatically connect even with no obd2 software running). Power cycle the adapter to help make sure nothing is connected to it.

If you are having trouble getting Torque Pro to connect, then you may need to tell it what adapter to use.
You can tell the app in *2* places which adapter to use. The one in the vehicle profile overrides the main global settings in the 'OBD2 adapter settings' part of the app

* One is in the main settings->OBD2 adapter settings->Choose Bluetooth device

* The other is in the "Vehicle Profile" - this should nearly always be left at "As defined in global OBD2 settings" unless you have multiple vehicles, and one adapter installed in each vehicle (then you can just switch profiles and adapters quickly).

If you have double-checked both those locations, made sure the lite version isn't running then the Pro version should connect without issue!

I have checked multiple times, everything is like it suppose to be, but free works, PRO doesnt.
I uninstalled both versions, installed only pro, still no luck, then installed free - it works(the free one).
Any suggestions?!
In setting it shows OBDII(11:22:33:DD:EE:FF)
And then it says - Torque is idle, Waiting for OBD adapter OBDII(11........)

And then once it was showing - waiting for Bluetooth device bugaround.

also this problem:
http://torque-bhp.com/forums/?wpforumaction=viewtopic&t=3265.0

I did reset my phone in hope to get PRO working, but no success, so still - lite works, PRO doesnt...
When looking carefully, I see, that PRO is looking for OBDII adapter, but can't find it, where lite version finds it.
Please admin come up with at least some kind of solution, otherwise I feel I have paid money for nothing.
I'm using Chinesse i9330 smartphone.

Want to add that I am having the same problem on my Sprint version of the Samsung Galaxy S3 running a 4.2.2 rom, lite version works just fine, but pro will not connect to the adapter at all. My ASUS transformer TF700T running a 4.2.2 rom connects just fine with the pro version.

So maybe it's an S3 problem and not an Android 4.2.2 problem?

Have you tried unistalling the free lite version in case its connecting without you knowing?

Yes, and I only installed the lite version in response to my friend with same phone was able to connect with the lite version. I had never had the lite version installed until I tested it myself. I also rebooted the phone several times making sure neither was running.

realwookie, are you on the latest nightly?

did you try wiping out dalvik/cache?
did you try wiping ROM & Internal Memory?

(Remember to back-up NV partition if you are to wipe /system)

The thing is that the latest nightly and Torque Pro work. Ian, got it working with a workaround a couple of updates ago. The bug is still there notheless, giving the Dev's one last chance before I go to report a bug I want to see if they fix it for the next M-Build.

I had started a thread a while back to report it here, however the bug is in the ROM

Also I found out the bug is probably in the Kernel.
If you are using a non-CM Kernel it's not going to work, I tried keetoonz kernel and it did not work. Stock-CM works fine tho,

An update to BT and Kernel yesterday made the phone give me another error while trying ODBTerminal (Which I use since Torque won't give me that error anymore) than the one I had at the end of the other thread which was:

03-03 14:47:51.777 D/BluetoothAdapterService(1105899880)( 1870): getState(): mAdapterProperties: com.android.bluetooth.btservice.AdapterProperties@41eacaa8
03-03 14:47:51.797 D/BluetoothAdapterService(1105899880)( 1870): getState(): mAdapterProperties: com.android.bluetooth.btservice.AdapterProperties@41eacaa8
03-03 14:47:51.797 E/        (1870): ### ASSERT : external/bluetooth/bluedroid/main/../btif/src/btif_dm.c line 1014 unhandled search services event (6) ###
03-03 14:47:51.797 W/BluetoothAdapter(3681): getBluetoothService() called with no BluetoothManagerCallback

Now it's something else (I'll post a catlog tomorrow). So yeah I don't know what the problem may be, make a catlog and post it somewhere to link here and I'll try to see what it is

G'day everyone.

I am having similar sounding problem here, running latest nightly CM 10.1 on Android 4.2 - Samsung Galaxy 9300

I can connect to the adaptor no worries, but Torque keeps 'cycling' through trying to connect to it and then failing, retrying, etc...

Any ideas what I can try to get it to work? I am tempted to download the free version to try what is mentioned above, but at the end of the day that won't help me.

Thanks,

Jake

It's funny that you mention that it might be kernel related. I have been running Liquidsmooth 2.1 RC2 on my ATT SGS3. I updated to Liquidsmooth 2.1 Stable last night and was unpleasantly surprised to see that Torque would no longer connect ("Adapter not found. Retrying..."). I didn't know if it was related to the Torque update or my new ROM, so I backed up everything, then restored my system from yesterday (a copy of Liquidsmooth 2.1 RC2) and merged in my data from today's backup. Torque instantly worked again. At that point, I realized that the Kernel was different. 2.1 RC2 uses Cyanogenmod, and I believe 2.1 Stable uses a different Kernel.

Guess I will have to make a catlog of the failure and report it to the devs... what a shame. I keep switching ROMs to find one that runs Torque consistently, and now here's another one down the tube. Maybe I should just stick to running regular Cyanogenmod instead of these fancy hybrids.

MD1032, if you are feeling brave you you could try to get the CM kernel and try to flash it to different ROMs. See if that will work and report back if you wish.

jakey, if you can connect to the adapter you are out of this BT connection bug. The cycling you see is the program trying out different ODBII protocols. Check the make and model of your car to see if one of the different protocols are supported. Should that not work it might be a bad plug or adapter...

I was googling last night trying to find a place to download the CM Kernel, but couldn't find it. Can I just use the CM 10.1 kernel in that thread, which is for the galaxy tab? Or do I need one specific to my device (SHG-I747, the AT&T one)?

That Liquidsmooth ROM I'm using is primarily based on CM, so I'm guessing the CM kernel would work just fine, even if they switched to their own kernel in the latest release.

There's a workaround for the CM kernel if you're using it on the samsung devices (the app can identify it and knows what to do), unfortunately with kernels named 'underwear' and so forth, it makes it incredibly difficult to workaround the issue on other roms.

The correct thing of course is to complain to the ROM developers that bluetooth isn't working properly and get them to fix it (then unit test it!!) rather than have 40 developers try to work around various bluetooth issues for their apps

(Unfortunately Android Bluetooth is one of the most buggiest, not properly tested, awful, never been 100% APIs I've had to work with. nearly every android device has some form of issue with bluetooth. I will be a very happy developer when someone writes some proper unit tests for it that test against real-world devices)

Quote from admin on March 21, 2013
There's a workaround for the CM kernel if you're using it on the samsung devices (the app can identify it and knows what to do)

Funny you say that because I AM using CM kernel with CM 10.1 - still no cigar

I use LiquidSmooth 2.1 Stable, tried it with their kernel as well as my normal use ktoonsez kernel, neither work. Before I knew this was a real issue and thought it was just my phone I had been using CarbonRom and SlimBean, neither worked for me as well.