Regular Intermittent Connection Drop

GoogleCodeExporter commented 9 years ago

Which device (manufacturer, type)?
Droid
Which firmware is installed?
2.0.1
What version of wireless tether are you using?
All (I've tried them all)
What steps will reproduce the problem?
1.Enable tethering
2.Connect
3.Ping

What is the expected output? What do you see instead?
Expected: stable connection, instead I get about 50 successful pings and
then about 15 failures then another 50 good pings and then failures. The
cycle repeats.
Please provide any additional information below.

Original issue reported on code.google.com by j3t...@gmail.com on 24 Feb 2010 at 3:43

GoogleCodeExporter commented 9 years ago

Pinging www.l.google.com [64.233.169.105] with 32 bytes of data:
Reply from 64.233.169.105: bytes=32 time=105ms TTL=240
Reply from 64.233.169.105: bytes=32 time=103ms TTL=240
Reply from 64.233.169.105: bytes=32 time=231ms TTL=240
Reply from 64.233.169.105: bytes=32 time=103ms TTL=240
Reply from 64.233.169.105: bytes=32 time=110ms TTL=240
Reply from 64.233.169.105: bytes=32 time=96ms TTL=240
Reply from 64.233.169.105: bytes=32 time=105ms TTL=240
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
Reply from 64.233.169.105: bytes=32 time=586ms TTL=240
Reply from 64.233.169.105: bytes=32 time=100ms TTL=240
Reply from 64.233.169.105: bytes=32 time=100ms TTL=240
Reply from 64.233.169.105: bytes=32 time=108ms TTL=240
Reply from 64.233.169.105: bytes=32 time=122ms TTL=240
Reply from 64.233.169.105: bytes=32 time=119ms TTL=240
Reply from 64.233.169.105: bytes=32 time=87ms TTL=240
Reply from 64.233.169.105: bytes=32 time=90ms TTL=240
Reply from 64.233.169.105: bytes=32 time=89ms TTL=240
Reply from 64.233.169.105: bytes=32 time=109ms TTL=240
Reply from 64.233.169.105: bytes=32 time=111ms TTL=240
Reply from 64.233.169.105: bytes=32 time=100ms TTL=240
Reply from 64.233.169.105: bytes=32 time=97ms TTL=240
Reply from 64.233.169.105: bytes=32 time=93ms TTL=240
Reply from 64.233.169.105: bytes=32 time=98ms TTL=240
Reply from 64.233.169.105: bytes=32 time=103ms TTL=240
Reply from 64.233.169.105: bytes=32 time=93ms TTL=240
Reply from 64.233.169.105: bytes=32 time=101ms TTL=240
Reply from 64.233.169.105: bytes=32 time=111ms TTL=240
Reply from 64.233.169.105: bytes=32 time=123ms TTL=240
Reply from 64.233.169.105: bytes=32 time=102ms TTL=240
Reply from 64.233.169.105: bytes=32 time=108ms TTL=240
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
Reply from 64.233.169.105: bytes=32 time=633ms TTL=240
Reply from 64.233.169.105: bytes=32 time=101ms TTL=240
Reply from 64.233.169.105: bytes=32 time=95ms TTL=240
Reply from 64.233.169.105: bytes=32 time=105ms TTL=240
Reply from 64.233.169.105: bytes=32 time=159ms TTL=240
Reply from 64.233.169.105: bytes=32 time=98ms TTL=240
Reply from 64.233.169.105: bytes=32 time=95ms TTL=240
Reply from 64.233.169.105: bytes=32 time=101ms TTL=240

Ping statistics for 64.233.169.105:
    Packets: Sent = 52, Received = 37, Lost = 15 (28% loss),
Approximate round trip times in milli-seconds:
    Minimum = 87ms, Maximum = 633ms, Average = 134ms
Control-C

Original comment by j3t...@gmail.com on 24 Feb 2010 at 4:01

GoogleCodeExporter commented 9 years ago

Looks like an unstable mobile-data connection.
What if you ping the default-gateway (default: ping 192.168.2.254)?

Original comment by harald....@gmail.com on 24 Feb 2010 at 5:01

GoogleCodeExporter commented 9 years ago

[deleted comment]

GoogleCodeExporter commented 9 years ago

I'm in downtown Chicago. I've never had a connection issue -Ever. I always have 
full
bars-3G and killer signal strength. My building even has VZW signal repeaters 
in the
building.
GW pings fine but Internet traffic is a mess. I've tried swapping Kernels with 
no luck.

ping www.google.com -t

Pinging www.l.google.com [72.14.204.99] with 32 bytes of data:
Reply from 72.14.204.99: bytes=32 time=297ms TTL=50
Reply from 72.14.204.99: bytes=32 time=103ms TTL=50
Reply from 72.14.204.99: bytes=32 time=96ms TTL=50
Reply from 72.14.204.99: bytes=32 time=156ms TTL=50
Reply from 72.14.204.99: bytes=32 time=88ms TTL=50
General failure.
General failure.
General failure.
General failure.
General failure.
Reply from 72.14.204.99: bytes=32 time=335ms TTL=50
Reply from 72.14.204.99: bytes=32 time=96ms TTL=50
Reply from 72.14.204.99: bytes=32 time=98ms TTL=50
Reply from 72.14.204.99: bytes=32 time=166ms TTL=50
Reply from 72.14.204.99: bytes=32 time=119ms TTL=50
Reply from 72.14.204.99: bytes=32 time=96ms TTL=50
Reply from 72.14.204.99: bytes=32 time=105ms TTL=50
Reply from 72.14.204.99: bytes=32 time=98ms TTL=50
Reply from 72.14.204.99: bytes=32 time=120ms TTL=50
Reply from 72.14.204.99: bytes=32 time=98ms TTL=50
Reply from 72.14.204.99: bytes=32 time=95ms TTL=50
Reply from 72.14.204.99: bytes=32 time=123ms TTL=50
Reply from 72.14.204.99: bytes=32 time=111ms TTL=50
Reply from 72.14.204.99: bytes=32 time=94ms TTL=50
Reply from 72.14.204.99: bytes=32 time=159ms TTL=50
Reply from 72.14.204.99: bytes=32 time=100ms TTL=50
Reply from 72.14.204.99: bytes=32 time=98ms TTL=50
Reply from 72.14.204.99: bytes=32 time=164ms TTL=50
Reply from 72.14.204.99: bytes=32 time=106ms TTL=50
Reply from 72.14.204.99: bytes=32 time=97ms TTL=50
Reply from 72.14.204.99: bytes=32 time=165ms TTL=50
Reply from 72.14.204.99: bytes=32 time=94ms TTL=50
Reply from 72.14.204.99: bytes=32 time=169ms TTL=50
Reply from 72.14.204.99: bytes=32 time=636ms TTL=50
Reply from 72.14.204.99: bytes=32 time=99ms TTL=50
Reply from 72.14.204.99: bytes=32 time=104ms TTL=50
Reply from 72.14.204.99: bytes=32 time=187ms TTL=50
General failure.
General failure.
General failure.
Reply from 72.14.204.99: bytes=32 time=159ms TTL=50
Reply from 72.14.204.99: bytes=32 time=102ms TTL=50
Reply from 72.14.204.99: bytes=32 time=87ms TTL=50
Reply from 72.14.204.99: bytes=32 time=156ms TTL=50
Reply from 72.14.204.99: bytes=32 time=106ms TTL=50
Reply from 72.14.204.99: bytes=32 time=96ms TTL=50
Reply from 72.14.204.99: bytes=32 time=104ms TTL=50
Reply from 72.14.204.99: bytes=32 time=92ms TTL=50
Reply from 72.14.204.99: bytes=32 time=332ms TTL=50
Reply from 72.14.204.99: bytes=32 time=112ms TTL=50
Reply from 72.14.204.99: bytes=32 time=106ms TTL=50
Reply from 72.14.204.99: bytes=32 time=95ms TTL=50
Reply from 72.14.204.99: bytes=32 time=94ms TTL=50
Reply from 72.14.204.99: bytes=32 time=163ms TTL=50
Reply from 72.14.204.99: bytes=32 time=102ms TTL=50
Reply from 72.14.204.99: bytes=32 time=95ms TTL=50
Reply from 72.14.204.99: bytes=32 time=120ms TTL=50
Reply from 72.14.204.99: bytes=32 time=118ms TTL=50
Reply from 72.14.204.99: bytes=32 time=121ms TTL=50
Reply from 72.14.204.99: bytes=32 time=116ms TTL=50
Reply from 72.14.204.99: bytes=32 time=92ms TTL=50
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
Reply from 72.14.204.99: bytes=32 time=227ms TTL=50
Reply from 72.14.204.99: bytes=32 time=105ms TTL=50
Reply from 72.14.204.99: bytes=32 time=105ms TTL=50
Reply from 72.14.204.99: bytes=32 time=109ms TTL=50
Reply from 72.14.204.99: bytes=32 time=188ms TTL=50
Reply from 72.14.204.99: bytes=32 time=107ms TTL=50
Reply from 72.14.204.99: bytes=32 time=97ms TTL=50
Reply from 72.14.204.99: bytes=32 time=86ms TTL=50
Reply from 72.14.204.99: bytes=32 time=119ms TTL=50
Reply from 72.14.204.99: bytes=32 time=99ms TTL=50
Reply from 72.14.204.99: bytes=32 time=105ms TTL=50
Reply from 72.14.204.99: bytes=32 time=101ms TTL=50
Reply from 72.14.204.99: bytes=32 time=93ms TTL=50
Reply from 72.14.204.99: bytes=32 time=104ms TTL=50
Reply from 72.14.204.99: bytes=32 time=82ms TTL=50
Reply from 72.14.204.99: bytes=32 time=108ms TTL=50
Reply from 72.14.204.99: bytes=32 time=195ms TTL=50
Reply from 72.14.204.99: bytes=32 time=88ms TTL=50
Reply from 72.14.204.99: bytes=32 time=96ms TTL=50
Reply from 72.14.204.99: bytes=32 time=181ms TTL=50
Reply from 72.14.204.99: bytes=32 time=118ms TTL=50
Reply from 72.14.204.99: bytes=32 time=96ms TTL=50
Reply from 72.14.204.99: bytes=32 time=175ms TTL=50
Reply from 72.14.204.99: bytes=32 time=97ms TTL=50
Reply from 72.14.204.99: bytes=32 time=106ms TTL=50
Reply from 72.14.204.99: bytes=32 time=167ms TTL=50
Reply from 72.14.204.99: bytes=32 time=100ms TTL=50
Reply from 72.14.204.99: bytes=32 time=94ms TTL=50
Reply from 72.14.204.99: bytes=32 time=181ms TTL=50
Reply from 72.14.204.99: bytes=32 time=68ms TTL=50
Reply from 72.14.204.99: bytes=32 time=102ms TTL=50
Reply from 72.14.204.99: bytes=32 time=158ms TTL=50
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
Reply from 72.14.204.99: bytes=32 time=334ms TTL=50
Reply from 72.14.204.99: bytes=32 time=109ms TTL=50
Reply from 72.14.204.99: bytes=32 time=100ms TTL=50
Reply from 72.14.204.99: bytes=32 time=182ms TTL=50
Reply from 72.14.204.99: bytes=32 time=97ms TTL=50
Reply from 72.14.204.99: bytes=32 time=108ms TTL=50
Reply from 72.14.204.99: bytes=32 time=171ms TTL=50
Reply from 72.14.204.99: bytes=32 time=105ms TTL=50
Reply from 72.14.204.99: bytes=32 time=116ms TTL=50
Reply from 72.14.204.99: bytes=32 time=159ms TTL=50
Reply from 72.14.204.99: bytes=32 time=105ms TTL=50
Reply from 72.14.204.99: bytes=32 time=102ms TTL=50
Reply from 72.14.204.99: bytes=32 time=161ms TTL=50
Reply from 72.14.204.99: bytes=32 time=89ms TTL=50
Reply from 72.14.204.99: bytes=32 time=98ms TTL=50
Reply from 72.14.204.99: bytes=32 time=159ms TTL=50
Reply from 72.14.204.99: bytes=32 time=92ms TTL=50
Reply from 72.14.204.99: bytes=32 time=100ms TTL=50
Reply from 72.14.204.99: bytes=32 time=169ms TTL=50
Reply from 72.14.204.99: bytes=32 time=102ms TTL=50
Reply from 72.14.204.99: bytes=32 time=97ms TTL=50
Reply from 72.14.204.99: bytes=32 time=156ms TTL=50
Reply from 72.14.204.99: bytes=32 time=97ms TTL=50
Reply from 72.14.204.99: bytes=32 time=127ms TTL=50
Reply from 72.14.204.99: bytes=32 time=134ms TTL=50

Ping statistics for 72.14.204.99:
    Packets: Sent = 133, Received = 110, Lost = 23 (17% loss),
Approximate round trip times in milli-seconds:
    Minimum = 68ms, Maximum = 636ms, Average = 130ms
Control-C

Original comment by j3t...@gmail.com on 24 Feb 2010 at 5:11

GoogleCodeExporter commented 9 years ago

ping the gateway please!

Original comment by harald....@gmail.com on 24 Feb 2010 at 5:21

GoogleCodeExporter commented 9 years ago

I did!
It's fine.

Original comment by j3t...@gmail.com on 24 Feb 2010 at 5:28

GoogleCodeExporter commented 9 years ago

Pings sourcing from the phone work fine and do not drop.
pings sourcing from the PC (at the same time) intermittently drop.
Connection to VZW is stable.

Original comment by j3t...@gmail.com on 24 Feb 2010 at 5:29

GoogleCodeExporter commented 9 years ago

so ... the connection between the phone and your computer is just fine. if you 
ping
google.com (the internet) you get packet-loss.

conclusion: you mobile-data connection is unstable.

check the signal-strength:
settings -> telefon info -> status

Original comment by harald....@gmail.com on 24 Feb 2010 at 5:34

GoogleCodeExporter commented 9 years ago

once again ... ping the gateway (which is your phone) from your computer!

if you didn't change the lan-configuration - it's:

ping 192.168.2.254

Original comment by harald....@gmail.com on 24 Feb 2010 at 5:35

GoogleCodeExporter commented 9 years ago

Same issue to the GW.

ping 192.168.2.254 -t

Pinging 192.168.2.254 with 32 bytes of data:

Reply from 192.168.2.254: bytes=32 time=7ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=15ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=421ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=14ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=3ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=6ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=3ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
General failure.
General failure.
General failure.
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=847ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=5ms TTL=64
Reply from 192.168.2.254: bytes=32 time=3ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=13ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=3ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=706ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
Reply from 192.168.2.103: Destination host unreachable.
Reply from 192.168.2.254: bytes=32 time=19ms TTL=64
Reply from 192.168.2.254: bytes=32 time=495ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=7ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.2.254:
    Packets: Sent = 85, Received = 68, Lost = 17 (20% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 847ms, Average = 44ms
Control-C

Original comment by j3t...@gmail.com on 24 Feb 2010 at 5:39

GoogleCodeExporter commented 9 years ago

It's NOT the data connection. Signal strength is steadily at -95dBm

pings from the phone work fine all day long. 
pings from the PC(s) intermittently fail.
The data connection sourcing from the phone is stable.

Original comment by j3t...@gmail.com on 24 Feb 2010 at 5:46

GoogleCodeExporter commented 9 years ago

[deleted comment]

GoogleCodeExporter commented 9 years ago

I'm pretty clear on the fact that google.com is located on the Internet.
I'm a CCIE. The only reason I bring it up is you seem to think I'm a complete 
retard
when it comes to networking (i.e Google is the Internet)
Also data drops beyond the GW (The Internet usually) or high latency is shown 
in Win
7 as a time-outs not 'general failure' The reason for this is the packet is 
sent but
the reply fails. When the packet can't be sent like in this case you see 
'general
failures' if my gateway was healthy the packet would get sent. It's not.

Original comment by j3t...@gmail.com on 24 Feb 2010 at 5:55

GoogleCodeExporter commented 9 years ago

I do appreciate the help and attention to the issue

Original comment by j3t...@gmail.com on 24 Feb 2010 at 6:00

GoogleCodeExporter commented 9 years ago

I'm having the same exact issue. I'm on 2.0.1 Chevy Kernel and BuglessBeast V1

Original comment by contactr...@gmail.com on 24 Feb 2010 at 6:30

GoogleCodeExporter commented 9 years ago

I'm not able to reproduce such a behavior on my nexusone - I don't own a droid 
and 
can't verify this. Ben will take a look (he has one).

I can't assume that every user who opens an issue here is cisco-certified or 
has a 
degree in computer-science or something. That's why I'm asking questions and I 
do 
expect clear answers (otherwise it's not possible to debug).

By the way ... a signal strength of -95 dBm is not that excellent.

However ... ben will check that.

Original comment by harald....@gmail.com on 24 Feb 2010 at 8:35

GoogleCodeExporter commented 9 years ago

 I have also noticed this issue on my Droid with Bekit's 7 slot LV and BuglessBeast V1.

Original comment by Josh.Hab...@gmail.com on 5 May 2010 at 12:41

GoogleCodeExporter commented 9 years ago

I am also having this issue with my Droid. I would like to point out that I can 
consistently ping the GW with no problem, but the 3G symbol will disappear and 
re-
appear. However when browsing the web or downloading files on the phone it 
works fine 
with no connection drops.

Original comment by nathan...@gmail.com on 21 May 2010 at 5:49

GoogleCodeExporter commented 9 years ago

A friend of mine is having the same issue with his Motorola Droid running bekit 
kernel 0.8.3 lv800 and cyanogen 5.0.6.2 with wireless_tether 2.0.2-pre7.

When tethered, the 3g icon blinks on and off and the connection is intermittent 
(usable for email, news, etc. but frustrating for large file downloads, 
youtube, 
etc.). If he disables tethering and surfs from the phone, the connection 
remains 
constant and stable. 

Current signal strength -62dBm.

Original comment by francism...@gmail.com on 21 May 2010 at 3:18

GoogleCodeExporter commented 9 years ago

I've been having this problem with my Droid since I first rooted it, not matter 
what
ROM I use. Right now I'm using Bugless Beast and the latest Wireless Tether 
version
and I'm LUCKY to get 10MB transferred before the connection just disappears. The
signal on the phone IS FINE. AND I can tether with PdaNet for hours with no 
problem
whatsoever. My problem is the same described above - the 3G icon blinks off and 
on
and there's no internet. This only happens when using Wireless Tether.

Original comment by aaronpau...@gmail.com on 22 May 2010 at 3:47

GoogleCodeExporter commented 9 years ago

There is a new test-version of the app online. This new version renames the 
name of
the wireless-interface. No idea if that helps for this issue here (maybe 
something
interferes) but ... give it a shot please and report your results.
http://android-wifi-tether.googlecode.com/files/wireless_tether_2_0_2-pre10.apk

Original comment by harald....@gmail.com on 25 May 2010 at 10:46

GoogleCodeExporter commented 9 years ago

still seeing the same problem with the new test version. What are the chances 
that 
this is something Verizon is doing?

Original comment by francism...@gmail.com on 26 May 2010 at 2:19

GoogleCodeExporter commented 9 years ago

same here and using the new version, figured it was like yall said but never 
check ping until I saw this. Verizon perhaps? Nexus one has no problems.

Original comment by y2gsm...@gmail.com on 14 Jun 2010 at 8:43

GoogleCodeExporter commented 9 years ago

Same issue for me. I've tried 2.1, 2.2, bugless beast, jrummy, belittled,   
Chevy's kernels, etc... this aways happens after a few minutes. It's not the 3G 
connection. A MiFi works perfectly while the Droid isn't even close in 
reliability. 

I'm running the latest MasterBlaster build. 

How can we help you to debug it?

Original comment by Eye.Fi....@gmail.com on 10 Jul 2010 at 12:19

GoogleCodeExporter commented 9 years ago

I'll try 2.0.2 pre10 to see if it's any better.

Original comment by Eye.Fi....@gmail.com on 10 Jul 2010 at 12:22

GoogleCodeExporter commented 9 years ago

I'm having the same issue, but mine is less regular, and more sporadic. I am 
running from Sprint EVO on Damage Control 2.1.  

Perhaps I can provide a perspective from someone using both this program and 
the Sprint sponsored program. Comparison of the two in my experience:
Sprint Mobile Hotspot - slightly slower general connection, higher pings, but 
less standard deviation
Android-Wifi-Tether - faster connection, lower pings, but less stable

I would love to be able to get rid of Sprint Mobile Hotspot, but this issue 
stops is enough to keep me on Sprint's app.  I really appreciate the work on 
this program, and I will be donating regardless, but if I could use 
Android-Wifi-Tether fulltime, I would definitely donate more. :)  This is a 
great project, as a new Computer Science student, I am very impressed with the 
work and I appreciate it very much!

Original comment by berardi1...@gmail.com on 14 Jul 2010 at 2:05

GoogleCodeExporter commented 9 years ago

I'm also getting this issue on Moto Droid running BB 0.4 Froyo, 1.0GHZ ChevyNo1 
& P3Droid kernels.  3G disconnects after approx. 5 minutes and tethering app 
does not always regain connection.  Can't download large files while tethered, 
but works from Android browser.  Connection was fine a few months ago, so I 
tried old APKs but they suffer the same problem.  My ping logs are similar to 
the above poster except mine where done on OSX.  Gateway is stable (0 packet 
loss) and pinging a website ie. google.com or yahoo.com yields about 7% packet 
loss over a period of 10+ minutes.  

Great work too btw and appreciate all the effort you guys have put in.

Original comment by biz...@gmail.com on 20 Jul 2010 at 4:37

GoogleCodeExporter commented 9 years ago

Just updated my towers and now have 0 packet loss pinging Google for 30 
minutes.  This might be the solution.

Original comment by biz...@gmail.com on 22 Jul 2010 at 5:19

GoogleCodeExporter commented 9 years ago

(Note: I'm not very savvy when it comes to networking, so excuse me if my 
terminology is off)

I believe this to be a Verizon issue. After experiencing it myself in this app, 
I tried three other apps including the native USB tethering (using an older 
version of Bugless Beast, before it automatically routed you to the verizon 
page). On all of the apps I tried I had the same results; worked fine for a few 
minutes, but if I put any kind of load (browsing the web, youtube, pandora) the 
3G signal would start to turn off and on, totally disrupting anything I tried 
to do.

On a hunch, I tried PDANet... PDANet works, but I believe that it's because it 
basically proxies via an app on your computer and an app on your phone, 
thoroughly disguising the data essentially.

Original comment by cnostr...@gmail.com on 15 Aug 2010 at 4:57

GoogleCodeExporter commented 9 years ago

You mentioned that your 3G stays up. Are you sure the 3G icon is on the entire 
time?

Oddly enough, I hit this issue with the stock gingerbread USB tethering, but I 
always see the 3g flip off and on in the meantime (like several other people 
here have reported).

Original comment by jer...@nickurak.ca on 7 Jul 2011 at 6:14

GoogleCodeExporter commented 9 years ago

I have a HTC Evo and I found that I had to leave on my GPS while using 
tethering because the Map app would periodically try to figure out the location 
in some way that caused me to drop off the network.  FWIW, /c

Original comment by cgtha...@gmail.com on 8 Jul 2011 at 12:35

GoogleCodeExporter commented 9 years ago

Well. Apps can use wifi for geo-location and this could cause such connection 
drops.

Original comment by harald....@gmail.com on 10 Jul 2011 at 6:02

mmorciegov / android-wifi-tether

Regular Intermittent Connection Drop #268