Galaxy Nexus working great, but disconnect after every hours

[GoogleCodeExporter]

Which device (manufacturer, type)?
Galaxy Nexus
Which firmware is installed?
4.0.3
What version of wireless tether are you using?
wifi_tether_v3_1-pre111.apk
What steps will reproduce the problem?
1.it's working like charm but it's disconnected on me every hours
2.it's quickly heat up the device after hours

anyone have same issues ?

Original issue reported on code.google.com by davidkim...@gmail.com on 26 Dec 2011 at 5:35

[GoogleCodeExporter]

Well. I don't think that this is a heat-problem. I believe the wifi-radio is 
shutdown by the system - if you restart tethering it's working again?

We need some input about that issue.

So please download the latest experimental-version:
http://android-wifi-tether.googlecode.com/files/wifi_tether_v3_1-pre112.apk

Install it and start tethering.

Then connect to your phone using adb.

Execute these commands and upload the output here:
adb shell
su
cd /data/data/com.googlecode.android.wifi.tether/bin
./rfkill list

Original comment by harald....@gmail.com on 26 Dec 2011 at 9:10

[GoogleCodeExporter]

Yes, its working after I restart the wifi tether...  I don't know to adb 
..sorry 

Original comment by davidkim...@gmail.com on 26 Dec 2011 at 9:28

[GoogleCodeExporter]

I have a similar issue on the Galaxy Nexus, if not the same, where my laptop 
disconnects periodically from the tether network and the network is no longer 
visible when I try to reconnect, requiring a restart of the tether. 

I'm running ZYGOT3 1.8 (Android 4.0.3) and pre112.

C:\Windows\System32>adb shell
sh-3.2# cd /data/data/com.googlecode.android.wifi.tether/bin
cd /data/data/com.googlecode.android.wifi.tether/bin
sh-3.2# ls
ls
dnsmasq
ifconfig
iptables
iwconfig
rfkill
tether
sh-3.2# ./rfkill list
./rfkill list
0: bcm4330 Bluetooth: Bluetooth
        Soft blocked: no
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
2: brcmfmac-wifi: Wireless LAN
        Soft blocked: no
        Hard blocked: no
3: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
sh-3.2#

If it will help, I'll run './rfkill list' again the next time the network 
disconnects.

Original comment by sabrsore...@gmail.com on 27 Dec 2011 at 1:36

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

count me in on this as well (dropping the access point the same as comment 3 
above), but only when tethering 4g...and there doesn't appear to be any rhyme 
or reason as to how long it works before dropping.

3g seems to work fine.

this is a stock rooted verizon galaxy nexus, 4.0.2, wifi tether beta 9.  
there's an ongoing discussion in the master galaxy nexus thread (issue 1257).

Original comment by crackers...@gmail.com on 28 Dec 2011 at 7:13

[GoogleCodeExporter]

I have the same issue on a galaxy nexus 4.0 2. Haven't tried it with 3g yet. It 
seems to be related to activity on my phone; if I'm messing around with stuff 
on my phone while tethering my computer will disconnect quite frequently, 
whereas if I leave my phone with the screen off it lasts much longer. Toggling 
the tether off and back on makes it detectable again every time.

I'll download the experimental version and give the adb stuff a shot when I get 
the chance at home.

Original comment by smith...@gmail.com on 4 Jan 2012 at 10:42

[GoogleCodeExporter]

Ok, what you guys could try (regarding the disconnect-issue).

Use the latest beta-version (it's 3.1-beta10).
Start tethering
Connect to your phone via adb
su
cd /data/data/com.googlecode.android.wifi.tether/bin
./rfkill block 3
exit

Now try if you have still some kind of disconnects.

Original comment by harald....@gmail.com on 4 Jan 2012 at 11:10

[GoogleCodeExporter]

Can we do that from terminal emulator rather than adb?

Original comment by crackers...@gmail.com on 5 Jan 2012 at 1:21

[GoogleCodeExporter]

Can you restate your instructions with a bit more explanation. 
1. How do we get the latest beta version 3.1 downloaded to the phone?
2. Connect to your phone via adb. What is adb and how is it done?
3. The next section is code, we type this in where?
su
cd /data/data/com.googlecode.android.wifi.tether/bin
./rfkill block 3
exit

Doesn't SU offer contact info. 
They did not reply to my post. 
Why don't they issue an update to fix the disconnect problem?
Thanks for the help, 
frustrated

Original comment by RJPast...@gmail.com on 5 Jan 2012 at 3:09

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

here's what I got after a disconnect using ./rfkill list:

0: bcm4330 Bluetooth: Bluetooth
        Soft blocked: no
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
2: brcmfmac-wifi: Wireless LAN
        Soft blocked: no
        Hard blocked: no
3: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
shell@android:/data/data #

Original comment by smith...@gmail.com on 5 Jan 2012 at 5:31

[GoogleCodeExporter]

@7 - I gave that a shot and didn't have any more disconnects last night or 
tonight. I'll post again if I do.

Original comment by smith...@gmail.com on 6 Jan 2012 at 2:57

[GoogleCodeExporter]

@smith148: It would be great if you could if you could verify that.
This can be built into the application but I need to know if it really helps or 
if it's just a placebo (don't have a galaxy nexus).

You need "to block" the right device ... I think I gave a wrong instruction.

If you do a ./rfkill list ...  you should take an entry similiar to ...
2: brcmfmac-wifi: Wireless LAN

The index is in that case 2 - entry starts with 2.
You should then execute:
./rfkill block 2

Original comment by harald....@gmail.com on 6 Jan 2012 at 9:53

[GoogleCodeExporter]

I won't be tethering too much this weekend but I will post again if it happens 
again, and I'll make sure the right entry is blocked.

Original comment by smith...@gmail.com on 6 Jan 2012 at 9:58

[GoogleCodeExporter]

With the right entry blocked there are still disconnects. Each time this 
happens it looks like there are two duplicate clients connected to wireless 
tether according to the status bar on my phone, but no actual connection.

Original comment by smith...@gmail.com on 7 Jan 2012 at 8:49

[GoogleCodeExporter]

I've got a Galaxy Nexus - CDMA/LTE. Usually tether when I'm on the road and 
mostly on 3g. I have blocked #2 - brcmfmac-wifi. Speeds have greatly improved. 
Before it was mostly 300-600kbps, sometimes 800-1000kbps. Highest I've ever 
seen is 1800kbps... Right now I'm pulling 2-2.25mbps and before rfkill I was in 
that 300-600 range. I'm on 3.1-pre115. Was using pre111 before, didn't start 
having issues with disconnects until I switched from Axi0m 2.3/imoseyon's 
kernel to Axi0m 2.4/Apex kernel. Been connected for 45min so far with no 
disconnects. Before using rfkill, I was getting 1-10min and it would reset the 
connection so I'd have to turn of wifi-tether, then turn it back on and 
reconnect. So far so good, I'll post again if I get any issues...

Maybe adding rfkill to the init script of wifi-tether so it will softblock the 
interface when you start & unblock when you stop?

Original comment by coy...@gmail.com on 11 Jan 2012 at 1:17

[GoogleCodeExporter]

Still seems to die after a period of inactivity. Computer still says connected, 
WiFi Tether shows computer still connected. No internet. Double checked and 
automatic shutdown is NOT enabled.

Original comment by coy...@gmail.com on 11 Jan 2012 at 2:39

[GoogleCodeExporter]

i had a disconnect last night on beta9, not when i received a text but when i 
replied to it.  when i replied, the tether disconnected and the phone rebooted.

i just downloaded pre115 to give that a shot today.  running it now with the 
following settings:

cdma nexus
auto
encryption on
access control off
dont disable bluetooth off
wifi driver reload off
disable wake lock on

gonna do some testing and will report back later.

Original comment by crackers...@gmail.com on 11 Jan 2012 at 4:58

[GoogleCodeExporter]

note about above: i haven't rfkill'ed anything.

Original comment by crackers...@gmail.com on 11 Jan 2012 at 4:58

[GoogleCodeExporter]

interesting - sent a text, had the same thing happen as last night (tether 
disconnected, counters reset and app still said "press to stop tethering" even 
though the computer couldn't connect to the AP.  the difference here is that on 
stopping the tether to restart it, the phone didn't reboot.

just now, after stopping the tether, i turned wifi driver reload on, and don't 
disable bluetooth on.  started tether up, PC connected.  received and sent a 
text message reply...i'm still connected.  we'll see how stable this setup is 
for the rest of the day...all other settings are the same.

no rfkill.

Original comment by crackers...@gmail.com on 11 Jan 2012 at 5:05

[GoogleCodeExporter]

alright, more interesting info here...

connection got slow all of a sudden, so i checked my phone - it had dropped 
from 4g to 3g.  at least the tether kept running through that, so i guess 
that's a good sign...but since the 3g signal is so strong here i couldn't get 
it to go back to 4g.  so, i decided to stop the tether and force the phone back 
to 4g (by doing the airplane mode on/off trick).

on stopping the tether, i noticed the phone got stuck on trying to turn wifi 
on.  then a soft reboot.  then, on trying to start the tether (after the soft 
reboot), my computer could see the AP but would not connect.  kept getting 
"acquiring network address" followed by an immediate disconnect.  no matter how 
many times i stopped/started tethering, i still couldn't get it to connect.

a hard reboot has resolved it for now, and i'm connected again.  this time, i 
did...

./rfkill block 2

before starting tether.  we'll see what happens...although an interesting thing 
is now speedtest.net doesn't know where i am.  i'm sitting in nyc, and it 
thinks i'm in the middle of massachusetts.  before, it knew exactly where i 
was...

Original comment by crackers...@gmail.com on 11 Jan 2012 at 6:29

[GoogleCodeExporter]

only tethered for a few minutes, but with rfkill blocking i didn't have a 
reboot when i stopped tethering.

i'm back tethering without rfkill now, i feel like it's a much more stable 
connection (not to mention location based sites know where i am without 
rfkill)...

i'll keep testing.

Original comment by crackers...@gmail.com on 11 Jan 2012 at 7:46

[GoogleCodeExporter]

ok...further testing today, this time WITH rfkill.  here's the result:

- open terminal emulator, run ./rfkill block 2
- start tether
- runs perfectly for a while
- still, just had a disconnect (netbook lost connection to AP)
- app said tether still running, but counters had been reset
- stop tether
- start tether
- netbook could connect again

so, while i lost the AP on my netbook and couldn't reconnect (even though the 
app said the tether was still running and the counters had been reset), i was 
able to stop and re-start the tether and reconnect from my netbook.  this is 
stark contrast to earlier today when i had this happen without using rfkill 
block 2, and after stopping the tether i had a soft reboot, followed by unable 
to connect to AP...which took a full hard reboot to be able to connect again.

i'm going to leave the AP up overnight and leave my netbook connected, and see 
where we're at in the morning.  will report back...

Original comment by crackers...@gmail.com on 12 Jan 2012 at 7:07

[GoogleCodeExporter]

Btw, netbook disconnected at some point during the night...i was able to just 
stpp tethering, unblock 2, and carry on with using my phone.  Without rfkill 
block i would have had a reboot by now

Original comment by crackers...@gmail.com on 12 Jan 2012 at 2:46

[GoogleCodeExporter]

I don't see any benefit of using rfkill so far. Mmmh ... or maybe something 
else to try:

1) After you have started tethering open "adb shell" and execute "./rfkill 
list". Copy the output to file so we can compare it later.
2) Now connect with a client and wait till the client drops the wifi-connection.
3) Connect again with "adb shell" and execute "./rfkill list" again. Did 
something change here?

Original comment by harald....@gmail.com on 12 Jan 2012 at 10:43

[GoogleCodeExporter]

I noticed today that it disconnects much more frequently if the app is in
the background than if I leave it running in the foreground. Perhaps this
has something to do with acquiring wakelocks in Android 4.0?

Original comment by bradm...@gmail.com on 13 Jan 2012 at 1:40

[GoogleCodeExporter]

Issue 1313 has been merged into this issue.

Original comment by harald....@gmail.com on 13 Jan 2012 at 10:54

[GoogleCodeExporter]

I am getting similar issues - at first I thought it was completely random, but 
it seems like when I start downloading a torrent with lots of peers 
(connections) it seems to hasten the "hang" - also not sure why but it appears 
that it may keep a download going but will block web browsing, until the 
download is complete...

Stock Android 4.0.2 not rooted.

Original comment by lan...@kismicro.com on 27 Feb 2012 at 5:52

[GoogleCodeExporter]

Hi, i have the same Problem here.

my tab wifi is connected to my galaxy nexus work for minutes then it stop,
1) i DC my tab then reconnect it gets ip from my Galaxy nexus, but no internet.
2) i toggle the tether on my Nexus internet work again, after couple of minutes 
stop.
3) i plug the Galaxy nexus to power internet works for hours,

the only problem is happening here its when the phone is discharging,
when its charging all works fine.

Original comment by zia...@gmail.com on 23 Mar 2012 at 1:44

[GoogleCodeExporter]

For mine, this problem happens mostly just shortly after I turn off the wifi, 
and the signal bars will become grey out and unable to reconnect. 
But it also happens randomly throughout the day occasionally 

Original comment by Cassandr...@gmail.com on 15 Aug 2012 at 3:43