Idetifying and Limited Connectivity

[GoogleCodeExporter]

Which device (manufacturer, type)?
Samsung Spica

Which firmware is installed?
2.1 rooted

What version of wireless tether are you using?
2.0.1

What steps will reproduce the problem?
1.Turn on Wifi Tether by clicking it

What is the expected output? What do you see instead?
It should be connected successfully, but then my laptop identifying the
connection without stopping before i disconnected it. And once, it give
"Limited Connectivity" result.

Please provide any additional information below.
The download stop at 0.4kB and upload 0.1kB.
I've tried on Windows 7 x86 and Windows Vista x86, no one working.

Original issue reported on code.google.com by liphz.o...@gmail.com on 29 May 2010 at 4:16

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

The problem here seems to be that samsung has removed some wifi-"features" with 
the 
new firmware. Do the following to make it work:

1) Download a Samsung Galaxy firmware (or dump) - PLEASE NOTE: A 
CUPCAKE(android 1.5) 
RELEASE IS REQUIRED - and extract the file "rtecdc.bin" which is located in the 
"/system/etc".
2) Mount the sdcard on your pc.
3) Create a directory named "android.tether" on the sdcard.
4) Put the extracted "rtecdc.bin"-file into that directory!
5) Uninstall older versions of "Wireless Tether".
6) Install the latest experimental version:
http://android-wifi-tether.googlecode.com/files/wireless_tether_2_0_2-pre13.apk

This should do the trick. Good luck. And please report if that worked for you.
Thanks. 

Original comment by harald....@gmail.com on 29 May 2010 at 5:16

[GoogleCodeExporter]

i'm sorry, do you mean by
"Download a Samsung Galaxy firmware (or dump) - PLEASE NOTE: A CUPCAKE(android 
1.5)
RELEASE IS REQUIRED"
is to change my OS back to Cupcake from Eclair?
Thanks.

Original comment by liphz.o...@gmail.com on 29 May 2010 at 5:40

[GoogleCodeExporter]

No. You need only one single file from a cupcake-release! You need to extract 
"rtecdc.bin" which is located under "/etc" and put it on the sdcard like I've 
described 
above.

You will still have eclair (Android 2.1) but for tethering the old 
firmware-binary for 
the wifi-interface is loaded (which is located on the sdcard).

Original comment by harald....@gmail.com on 29 May 2010 at 6:00

[GoogleCodeExporter]

it still not makes it working yet..
anyway, when i tried to find the problems, the windows said that "The default 
gateway
is not available".

Original comment by liphz.o...@gmail.com on 30 May 2010 at 5:06

[GoogleCodeExporter]

Try to start tethering from command-line:

adb shell
su
cd /data/data/android.tether/bin
./tether start 1

This will generate some debug-output. Post this output here.

Original comment by harald....@gmail.com on 30 May 2010 at 11:02

[GoogleCodeExporter]

Hi i have the same problem too...
here. i capture the output...

# ./tether start 1
./tether start 1
about to run: [/data/data/android.tether/bin/ifconfig eth0 192.168.2.254 netmask
 255.255.255.0]
about to run: [/data/data/android.tether/bin/ifconfig eth0 up]
about to run: [/data/data/android.tether/bin/iwconfig eth0 mode ad-hoc]
about to run: [/data/data/android.tether/bin/iwconfig eth0 essid AndroidTether]
about to run: [/data/data/android.tether/bin/iwconfig eth0 channel 6]
about to run: [/data/data/android.tether/bin/iwconfig eth0 commit]
about to run: [/data/data/android.tether/bin/iptables -N wireless-tether]
about to run: [/data/data/android.tether/bin/iptables -F wireless-tether]
about to run: [/data/data/android.tether/bin/iptables -t nat -F PREROUTING]
about to run: [/data/data/android.tether/bin/iptables -t nat -F POSTROUTING]
about to run: [/data/data/android.tether/bin/iptables -t nat -F]
about to run: [/data/data/android.tether/bin/iptables -A wireless-tether -m stat
e --state ESTABLISHED,RELATED -j ACCEPT]
about to run: [/data/data/android.tether/bin/iptables -A wireless-tether -s 192.
168.2.0/24 -j ACCEPT]
about to run: [/data/data/android.tether/bin/iptables -A wireless-tether -j DROP
]
about to run: [/data/data/android.tether/bin/iptables -A FORWARD -j wireless-tet
her]
about to run: [/data/data/android.tether/bin/iptables -t nat -I POSTROUTING -s 1
92.168.2.0/24 -j MASQUERADE]
about to run: [/data/data/android.tether/bin/dnsmasq -i eth0 --resolv-file=/data
/data/android.tether/conf/resolv.conf --conf-file=/data/data/android.tether/conf
/dnsmasq.conf]
script result was []

Original comment by bram...@gmail.com on 4 Jun 2010 at 7:19

[GoogleCodeExporter]

the issue 353 answer it...

http://forum.samdroid.net/threads/610-Dev-Testing-WiFi-tether-for-i5700-Eclair-u
pd-19.04

thx guys
bravo....

Original comment by bram...@gmail.com on 4 Jun 2010 at 10:05

[GoogleCodeExporter]

This is an unofficial and unsupported fork of this project. 

If you do exactly what I've suggested here:
http://code.google.com/p/android-wifi-tether/issues/detail?id=357#c2
the app should work flawlessly.

Original comment by harald....@gmail.com on 4 Jun 2010 at 10:23

[GoogleCodeExporter]

EVO here and I'm having the SAME issue.  I tried to download the dump file and 
find that file you mentioned but it's not the same on the EVO.  Please help, I 
cant use WT and it freezes up at .4kb just like everyone else.  Thanks

Original comment by TFalw...@gmail.com on 20 Jul 2010 at 1:45

[GoogleCodeExporter]

EVO 2.2 cyanogen mod 6.x here. I *think* this issue is caused by a 3rd party 
app because up until a few weeks ago, I was able to use wireless tether fine, 
and I've changed nothing but installed more apps here and there since it last 
worked flawlessly. Traveling this weekend and been troubleshooting it. I get 
the issue mentioned above (strong signal from phone which can be seen from 
laptop, local access only, but Internet is not getting passed through my EVO to 
the laptop like it did before. I do know that I installed AntiVirus at some 
point right about when I noticed the issue first (just now got around to 
troubleshooting this), so I'll freeze that with Titanium BackUp, and see if 
that helps. Also, this *might* have occurred when I converted to Cyanogen, but 
I don't recall if that was before or after, so if freezing the AntiVirus and 
other apps doesn't work, I'll flash back to OMJ, which is what I was using 
before and I KNOW it worked then. I'll report back if I discover the issue. I'm 
fairly confident it's something simple.

Original comment by MikeGer...@gmail.com on 27 Feb 2011 at 6:53