Tethering problem on Froyo (works for only a few mins at a time then stops)

[biz79]

To clear permissions, open up the superuser permissions app, click wifi tether and hit forget. To clear data/cache for the app, go to settings -> applications -> manage applications -> wireless tether -> Press clear data.

I did a quick read on EVRC and EVRC-B. Yeah I saw that you might not be able to make calls if u use it, but EVRC-B and 13K codecs could make call quality better? I just followed another post to reupdate my towers, since it was a while since I updated my baseband.

So no one pinged a website from their broken tethering app? I should of done it after each step, but it was just a guess for me. I'm interested to see if it helped other people. Nice to hear that the newest update fixes the issue too.

My cable is out and I'm using my wifi tether(sooo useful!!), but anyway I'm using BB.4 so I doubt its rom related. Does wifi tether show up in permissions? Also wiping data/cache would probably fix it.

I didn't see an option on the tether app for clearing data/cache

If this does fix your problem, it probably indicates that with the new Froyo baseband your original EVRC-B setting was changed back to the default EVRC setting...

I've read that EVRC is typically the default setting for most Verizon support areas in the USA. The reason is that the older EVRC codecs will work in EVRC-B areas, but the newer EVRC-B codecs will not work in EVRC areas. In other words, you may not be able to make calls out if you travel to an area that does not support EVRC-B.

Ain't local implementations great ???

...
Optionally - dial ##program, password 000000, change vocode to evrc-b.
...

It's definitely not ROM specific. I went to try this option but when I dial ##PROGRAM the verizon message that it can't complete the call comes up. Weird.

[CompleteGFX]

Thanks for the support.

I will ping google and run your tests as requested.


But I have to ask... is anyone out there using a hacked 2.2 rom with FLAWLESS wired/wireless tethering? If yes, please list your build, creator, and link(s) to your current build.

I would definately say that I had absolutely NO problems on 2.1 ultimate droid, but froyo dosent like my laptop

Cheers,
Andrew from texas

[biz79]

Thx dude. Yeah mine was flawless with 2.1 also, so maybe updating the 3g towers will fix your issue too.

Thanks for the support.

I will ping google and run your tests as requested.


But I have to ask... is anyone out there using a hacked 2.2 rom with FLAWLESS wired/wireless tethering? If yes, please list your build, creator, and link(s) to your current build.

I would definately say that I had absolutely NO problems on 2.1 ultimate droid, but froyo dosent like my laptop

Cheers,
Andrew from texas

[Jim 777]

I only tried it once (I only use it when I need to) for about 15 minutes. It never failed that I saw and before it would drop by around 5 minutes or so.

I'm running JRummy's 2.2 build number V5.0.9 right now.

[BayouFlyFisher]

But I have to ask... is anyone out there using a hacked 2.2 rom with FLAWLESS wired/wireless tethering? If yes, please list your build, creator, and link(s) to your current build.

Cheers,
Andrew from texas

I have been on one or another 2.2 custom rom since it became available. I am currently on Sapphire 0.8.4 with P3 125mhz-1.25Ghz kernel. I was, until recently, using the Wifi Tethering for Rooted Users 205 pre1. I am now using 205 pre3. I am having absolutely no tethering issue. I use it infrequently, but it works well. I actually use the wired tethering program now because it is faster. But it too works flawlessly.

[CompleteGFX]

Bayouflyfisher, I will give that rom a try. I home its going to work well! *crosses fingers*



EDIT:

*********************
*** 1 minute
*********************

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Andrew>ping google.com

Pinging google.com [74.125.159.99] with 32 bytes of data:
Reply from 74.125.159.99: bytes=32 time=160ms TTL=46
Reply from 74.125.159.99: bytes=32 time=214ms TTL=46
Reply from 74.125.159.99: bytes=32 time=144ms TTL=46
Reply from 74.125.159.99: bytes=32 time=146ms TTL=46

Ping statistics for 74.125.159.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 144ms, Maximum = 214ms, Average = 166ms


*********************
*** 3 minutes
*********************

C:\Users\Andrew>ping google.com

Pinging google.com [74.125.47.106] with 32 bytes of data:
Reply from 74.125.47.106: bytes=32 time=181ms TTL=46
Reply from 74.125.47.106: bytes=32 time=163ms TTL=46
Reply from 74.125.47.106: bytes=32 time=157ms TTL=46
Reply from 74.125.47.106: bytes=32 time=215ms TTL=46

Ping statistics for 74.125.47.106:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 157ms, Maximum = 215ms, Average = 179ms


*********************
*** 5 minutes
*********************

C:\Users\Andrew>ping google.com

Pinging google.com [74.125.47.106] with 32 bytes of data:
Reply from 74.125.47.106: bytes=32 time=1216ms TTL=46
Reply from 74.125.47.106: bytes=32 time=154ms TTL=46
Reply from 74.125.47.106: bytes=32 time=157ms TTL=46
Reply from 74.125.47.106: bytes=32 time=295ms TTL=46

Ping statistics for 74.125.47.106:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 154ms, Maximum = 1216ms, Average = 455ms


*********************
*** 7 minutes
*********************

C:\Users\Andrew>ping google.com

Pinging google.com [74.125.47.105] with 32 bytes of data:
Reply from 74.125.47.105: bytes=32 time=131ms TTL=46
Reply from 74.125.47.105: bytes=32 time=158ms TTL=46
Reply from 74.125.47.105: bytes=32 time=132ms TTL=46
Reply from 74.125.47.105: bytes=32 time=139ms TTL=46

Ping statistics for 74.125.47.105:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 131ms, Maximum = 158ms, Average = 140ms

C:\Users\Andrew>

As requested.

[biz79]

Ooops Complete, actually it be better to test the connection with a continuous packet stream. But at least the wifi tether was still working after 7minutes. I did mine in OSX but for Windows do 'ping -n 2000 google.com'. That should test the internet connection continuously for at least 5 minutes. Just see if there's any packet loss. If not, it would seem that the internet connection was stable.

[CompleteGFX]

Here is the retest. I was using the internet and watching videos. The tethering seems to work pretty good. However when I download torrents tethering stops. every test i did, before this one, utorrent app was running.

Ping statistics for 74.125.47.103:
Packets: Sent = 2000, Received = 1993, Lost = 7 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 105ms, Maximum = 3237ms, Average = 185ms

My tethering connection has been active and working now for almost 40 minutes straight! Also i think the packet loss that is there was when i received a phone call (didn't answer).

Right now I am on the latest Simply Stunning Rom.


P.S. Anyone know how to get utorrent working again?

[biz79]

Your connection seems pretty stable now, so that's good news. You just used another rom? Did u update ur towers or use the latest apk? Hmm not really sure why utorrent wouldn't be working if it worked before, but I'm guessing its a fair trade off. I've never tried dl'ing a torrent on tether since it spawns many active connections.

[ChugIt]

Running ESE81update2 with BB0.4 I have zero issues using Wired Tether For Root Users. However, I was dropping my connection often using paid easytether and free PDANet. Since going to Wired Tether For Root Users I have had no problems. I wish I could help, all I can do is tell you what is working for me. Good luck and I hope you guys figure it out.