I have been working on tether connection issue with a DROID 2 for a couple days now. following your thread i have been able to connect to the PLX wifi, but it does not fail. It stays connected. But I still can't seem to sync up in torque. I have made sure that the setting in torque are set to wifi.
Not sure if i still need to run the
su
ifconfig tiwlan0 192.168.0.11 netmask 255.255.255.0 broadcast 192.168.0.255
command if the connection does not fail. The below thread is how I got to this point. ian has been provided some support.

http://torque-bhp.com/forums/?wpforumaction=viewtopic&t=469.0

Any ideas on how to get to torgue to sync after the maintaining the adhoc connection?

Droid 2 running 2.3.3. rooted

Pinging the IP of the adapter is essential to checking that you have a working ad-hoc connection - if you get replies then all is good and you can proceed with connecting with Torque

If you don't get replies, then your ad-hoc connection is failing somewhere so will have to hunt around further

The command for pinging in the terminal would be:

ping <your adapters ip address>

which would look something like:

ping 192.168.1.1

if your adapter was at 192.168.1.1

You should then see something like the following on a working connection:

ping 127.0.0.1
PING 127.0.0.1 (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.095 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.114 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.116 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.102 ms
--- 127.0.0.1 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.095/0.107/0.116/0.009 ms

(use Ctrl-C to stop the ping)

On a non working connection you would see something like:

ping 127.0.0.2
PING 127.0.0.2 (127.0.0.2): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
--- 127.0.0.2 ping statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss

OK,
we are up and running. thanks for the help.
I will go over the steps that worked for me.
Not sure which ones were relevant and which were not.
I was able to connect but not able to ping.
I edited the /etc/wifi/wpa_supplicant.conf file with the bolded changes
ctrl_interface=DIR=/data/misc/wifi/wpa_supplicant GROUP=wifi
update_config=1
ap_scan=2(was 1)
the data/misc/wifi/wpa file had the below info already there ..I did not change them.

network={
ssid=”PLXDevices”
key_mgmt=NONE
scan_ssid=1
mode=1
priority=1

Now for the tweeks..
I was not able to ping till I ran the ifconfig script below in a term window.
su
ifconfig tiwlan0 192.168.0.11 netmask 255.255.255.0 broadcast 192.168.0.255

short of running this command everytime I get in my vehicle, how can I replicate this setup without doing an ifconfig?

DROID 2 running 2.3.3

got this thread from Ian ..it helped alot.

http://torque-bhp.com/forums/?wpforumaction=viewtopic&t=1619.0

Quote from lower.alabama on January 17, 2012
got this thread from Ian ..it helped alot.

http://torque-bhp.com/forums/?wpforumaction=viewtopic&t=1619.0

So were you able to get it working? I'm sorry, when i said "Fail" in my post, it actually "connects" it just fails to aquire an IP address, defaulting to the default of 169.*.*.* so thats why you have to issue the ifconfig command to manually set the ip address so u can ping the device.

I (unfortunately) don't know of any way for someone to connect without the ifconfig statement unless you created a bash script or a mini program that calls a bash script that sets it up for you.

It works..just a couple steps to get there, would like to be able to just put the phone in the cradle, connect and go...we will get there.
As for the connection, i tried to do the static option in the advanced setting but it would not connect..it kept erroring out. So what's the difference? it connects using the the auto IP but not static..

Hi

There's no DHCP server running on either device so the automatic assignment will fail and it wil fallback to the 169.* addresssing scheme (which is no good when the adpater is on 192.168.x.x

You need to set the IP to be adjacent to the adapter (preferably), so if the adapter is on 192.168.0.1, then you want to configure your IP as 192.168.0.2 preferably with a netmask of 255.255.255.0

The ad-hoc may say 'connected' (even before the client/host mode swap, which is required), but until you can ping the device, you won't know for certain whether everything is configured correctly

Do you think this would work with the innovate OT-2? Since it uses wifi instead of bluetooth, there is no android support for it? If I could get the OT-2 to connect, could I use it to monitor and log my wideband and egt data using torque via the OT-2?

Depends on what protocol the OT-2 adapter uses - if it's ELM based/compatible then it should work straight out of the box (however if it's like the garmin ecoroute adapter then it may be a completley different protocol)

Will not work out of the box. All I know is that it uses ad hoc, and that is why innovate doesn't have an android app for it. I'm thinking all I need to do is use a rom that will allow ad hoc access, but this is not really my area of expertise. If I am able to connect with an Android tablet, hopefully I can get someone who is smarter than me to add the extra plugins to the torque app, such as wideband AFR and egt etc. From the lack of data that I've found, it appears that this has not been done yet. It appears that nobody has ever been able to connect a wideband to an Android tablet and that needs to change. This alone would make the torque app extremely valuable to any tuner.

If anyone can help with this, please chime in. I haven't purchased my tablet yet and I really don't want to buy a stupid iPad. I want Torque.