Connection Drops Consistently

[GoogleCodeExporter]

Which device (manufacturer, type)?

Samsung Intercept using Samsung Epic 4G profile

Which firmware is installed?

Froyo 2.2

What version of wireless tether are you using?

3.1 Beta1

What steps will reproduce the problem?
1. Samsung 4G Profile
2. Softap Master
3. connect

What is the expected output? What do you see instead?

I used this set up with 3.0 Pre 11 and it worked find just had its own set of 
problems of course.  Got the update today and it worked fine earlier in the 
day.  Now though for some reason it connects with internet then shows where I 
lost internet and says "identifying network".  If I stop tethering and start 
again it will connect for a few 10 to 15 secs again fine then drop again.

Please provide any additional information below.

3.0 Pre 11 Works fine as of not dropping connections.  3.1 Beta1 worked fine 
for the first few hours then started dropping connections.

Original issue reported on code.google.com by jedgell...@gmail.com on 8 Jul 2011 at 6:12

[GoogleCodeExporter]

Just to update.  I uninstalled and reinstalled and again it worked perfectly 
fine for the first hour or so then started dropping again.  I can 
restart/battery pull, nothing seems to help it.  Then I noticed that it will 
connect at times perfectly fine.  Probably just a small glitch somewhere.

I did check on my side to make sure it wasn't Windows 7 messing with me.  
Everything was fine on my end and I even checked with my girlfriend's laptop 
with Windows 7 and got the same issue right off the bat.

I did test other aspects though being I am using it on the Samsung Intercept.  
It used to crash hard by restarting the phone if I was to use the camera while 
wifi tether was on or searching through the gallery or market.  3.1 Beta1 
though I can tell you has completely fixed these problems.  I think I've had 
maybe one or two hard crashes which were completely random so couldn't figure 
out the cause but it's not nearly as bad.

Keep up the great work guys!

Original comment by jedgell...@gmail.com on 8 Jul 2011 at 6:30

[GoogleCodeExporter]

I looked through the other post that also having problems with connection drops 
and read where you guys asked the to ping the gateway so I did it as well.  The 
weird thing is right now I'm connected fine at the moment.  I'm using the 
default gateway ip so I ping and it times out right away and kills my 
connection.

Original comment by jedgell...@gmail.com on 8 Jul 2011 at 6:42

[GoogleCodeExporter]

Been working with it more today and it seems that 1 out of 10 or so times 
trying to connect it works but for how long can be between a min to a few hours 
before timing out.  Every other time it says "Limited Access".

Original comment by jedgell...@gmail.com on 13 Jul 2011 at 2:07

[GoogleCodeExporter]

Noticed you guys put out a quick update. I installed 3.1 Beta2 and set it up 
again.  It connected right away!  Also I went ahead and recreated situations 
that would have normally crashed 3.0 Pre11 and it runs perfectly.  Of course 
its still a tad early to tell cause it worked fine for the first day on Beta1.  
I'll send one last later on in the day to let ya know that I'm confident of its 
stability.

I will say though you can add Samsung Intercept to the list of compatible 
devices using the Samsung Epic 4G Profile.  Great work guys!

Original comment by jedgell...@gmail.com on 13 Jul 2011 at 7:19

[GoogleCodeExporter]

Okay so I've been using the newest beta for quite some time now and have had 
only 2 forced phone restarts which seems to be just at random.  This is still 
much better than 3.0 pre11.  As for this issue though 3.1 Beta2 fixes the 
connection issues.  Great Work!

Original comment by jedgell...@gmail.com on 13 Jul 2011 at 7:13

[GoogleCodeExporter]

Real quick too just to add that I do not need a custom kernel to run Wifi 
Tether.  I am rooted using stock kernel and rom.

Original comment by jedgell...@gmail.com on 13 Jul 2011 at 7:21

[GoogleCodeExporter]

It seems this issue lingers even with BETA6 but now I finally found the root of 
the problem.  It seems that the Access Control feature is interfering whether 
it is turn on or off.  When the internet becomes unresponsive, if I toggle 
Access Control for Disable to Enable then back to Disable, wait a min and it 
works fine again until it interferes yet again. 

Original comment by jedgell...@gmail.com on 9 Nov 2011 at 7:25

[GoogleCodeExporter]

Well. The access-control feature is fully built with iptable-rules. I don't 
believe this is related to the connection drops. Is your phone probably 
switching between 3g and 4g mobile networks?

Original comment by harald....@gmail.com on 10 Nov 2011 at 8:47

[GoogleCodeExporter]

The Samsung Intercept is 3G only so that's not the problem.  I am not sure why 
though but only when i toggle access-control on then off again it works again.  
I personally think access control is glitching and blocking the IP to my 
computer until I reset it.

I'm by far a programmer though but I am a long time techie.  I'm about to get 
my phone back on which is the same brand and model and I'll see if it works 
too.  Usually this is the case though...

I turn on wifi tether beta6... all connects fine and well.  Then after say an 
hour or two while I'm surfing the web the page will hang and finally time out.  
I go back to wifi tether and have to turn it off and make sure its process isnt 
running, then reset wifi and 3G. Then start wifi tether and connect again.  
Sometimes this forces a reset but most of the time it works fine for a lil bit 
then resets.  The resets though is due to overheating and the intercept isn't 
the best device to stay cool haha.

So I'll get my phone back on and try the access control disable/enable and see 
it fixes my connection as well.  At least this way we will both know if the 
incident is isolated or not.

Original comment by jedgell...@gmail.com on 11 Nov 2011 at 6:44

[GoogleCodeExporter]

Noticed I left out some info but the phone I figured about the access control 
fix was on my girlfriends phone which is the same as mine.  My phone has been 
out for a couple weeks now so I haven't got to try it on mine yet.

Original comment by jedgell...@gmail.com on 11 Nov 2011 at 6:48