• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Periodic degraded latency with WiFi connection

Hi all,

I have a brand new Nexus 7, next gen. I am finding the WiFi connection really flaky.

When I turn the screen off, the Nexus remains connected to my WAP, but at a certain point the latency goes crazy.

Pinging the unit from my desktop box, here is what I see when I activate WiFi:
[HIGH]ping 192.168.2.6
PING 192.168.2.6 (192.168.2.6) 56(84) bytes of data.
64 bytes from 192.168.2.6: icmp_req=5 ttl=64 time=3.79 ms
64 bytes from 192.168.2.6: icmp_req=6 ttl=64 time=3.99 ms
64 bytes from 192.168.2.6: icmp_req=7 ttl=64 time=1.64 ms
64 bytes from 192.168.2.6: icmp_req=8 ttl=64 time=0.718 ms
64 bytes from 192.168.2.6: icmp_req=9 ttl=64 time=1.34 ms
64 bytes from 192.168.2.6: icmp_req=10 ttl=64 time=2.23 ms
64 bytes from 192.168.2.6: icmp_req=11 ttl=64 time=0.834 ms
64 bytes from 192.168.2.6: icmp_req=12 ttl=64 time=7.04 ms
64 bytes from 192.168.2.6: icmp_req=13 ttl=64 time=4.46 ms
64 bytes from 192.168.2.6: icmp_req=14 ttl=64 time=0.936 ms
64 bytes from 192.168.2.6: icmp_req=15 ttl=64 time=1.22 ms
64 bytes from 192.168.2.6: icmp_req=16 ttl=64 time=2.84 ms
[/HIGH]
Nice!

But at a certain point, ping times go out of the roof:
[HIGH]64 bytes from 192.168.2.6: icmp_req=80 ttl=64 time=1268 ms
64 bytes from 192.168.2.6: icmp_req=81 ttl=64 time=273 ms
64 bytes from 192.168.2.6: icmp_req=82 ttl=64 time=177 ms
64 bytes from 192.168.2.6: icmp_req=83 ttl=64 time=129 ms
64 bytes from 192.168.2.6: icmp_req=84 ttl=64 time=1257 ms
64 bytes from 192.168.2.6: icmp_req=85 ttl=64 time=386 ms
64 bytes from 192.168.2.6: icmp_req=89 ttl=64 time=1715 ms
64 bytes from 192.168.2.6: icmp_req=90 ttl=64 time=742 ms
64 bytes from 192.168.2.6: icmp_req=91 ttl=64 time=1236 ms
64 bytes from 192.168.2.6: icmp_req=93 ttl=64 time=1436 ms
64 bytes from 192.168.2.6: icmp_req=94 ttl=64 time=490 ms
64 bytes from 192.168.2.6: icmp_req=95 ttl=64 time=84.1 ms
64 bytes from 192.168.2.6: icmp_req=97 ttl=64 time=1038 ms
64 bytes from 192.168.2.6: icmp_req=98 ttl=64 time=536 ms
64 bytes from 192.168.2.6: icmp_req=107 ttl=64 time=445 ms
64 bytes from 192.168.2.6: icmp_req=109 ttl=64 time=2631 ms
64 bytes from 192.168.2.6: icmp_req=112 ttl=64 time=1372 ms
64 bytes from 192.168.2.6: icmp_req=113 ttl=64 time=395 ms
64 bytes from 192.168.2.6: icmp_req=116 ttl=64 time=402 ms
64 bytes from 192.168.2.6: icmp_req=117 ttl=64 time=8312 ms
64 bytes from 192.168.2.6: icmp_req=118 ttl=64 time=7332 ms
64 bytes from 192.168.2.6: icmp_req=119 ttl=64 time=6589 ms
64 bytes from 192.168.2.6: icmp_req=120 ttl=64 time=5601 ms
64 bytes from 192.168.2.6: icmp_req=121 ttl=64 time=4609 ms
64 bytes from 192.168.2.6: icmp_req=122 ttl=64 time=3615 ms
64 bytes from 192.168.2.6: icmp_req=123 ttl=64 time=2620 ms
64 bytes from 192.168.2.6: icmp_req=124 ttl=64 time=1624 ms
64 bytes from 192.168.2.6: icmp_req=125 ttl=64 time=644 ms
[/HIGH]

Usually I need briefly switch the WiFi off and on again to get the old ping times back.

FWIW, I don't see this behaviour on my 2012 Nexus 7.

I can't help but wonder whether this isn't being caused by some ultra-aggressive power management

Anyone else seeing this?
 
I will have to check...

Before I got to the end of the first section, I thought you were copmplaining about 4 milliseconds versus 1 millisecond, and I was going to suggest getting a life.

It isn't clear to me in your message whether you cycle the wireless off and on at the Nexus, or at the router... but it does seem like turning the screen back on doesn't correct the issue, or you would have mentioned that.

I have my Nexus set to turn off wireless when sleeping unless plugged in, which might be resetting things. I will keep it constantly on to see if I notice an issue.
 
Upvote 0
I've experimented a little more, comparing both last year's Nexus 7 as well as the new model.

As far as I can tell, there is some difference in the low-power state of the two tablets, if that is the correct term.

If you switch off the screen of the new Nexus (or let the screensaver kick in), the tablet appears to go into a very "slow" mode. I won't call it sleep or hibernation, since the the tablet is still active, but the network speeds drop precipitously (ie, really slow ping times), although it does, after quite a long number of seconds, appear to return to a faster state after a certain amount of network activity.

I don't see this behaviour with the older Nexus 7.

My setup is as follows: I have the QuickSSHd app installed and running on both tablets, and I am using "scp" in a Linux terminal window to copy files (MP3s) to to the tablets.

The solution isn't all that complicated: I leave the screen on while copying files! But I suspect this behaviour might cause problems in other unexpected ways, so I feel like it is worth reporting here. On the other hand, if this contributes to improved battery life, the unexpected side-effects might be worth it.

I'd be curious if anyone else can duplicate this issue.
 
Upvote 0
I don't have my tablet here at work but I get a similar result with my Galaxy Nexus. For this reason, I typically leave the screen on when downloading.

FWIW, ping time goes around 15-50ms with screen on, to 150-450ms with the screen off. I can similarly test my tablet tonight, but I think this is pretty normal behavior on a lot of devices.
 
Upvote 0
Results with my N7 are actually pretty interesting.

When I am touching or otherwise interacting with the tablet, my ping is reliably 1ms. When the tablet is sitting there, screen on but I'm not touching it, it seems to jump to around 17-40ms. When the screen is off, it varies quite a lot, but lowest seems to be about 30ms, more typically in the 100-500ms range.

The interesting part to me isn't what it does when it's asleep, it's that interacting with it so clearly causes the CPUs to rev up, allowing immediate response to packets.

I am not seeing 1000+ ms responses, though, even after several minutes asleep.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones