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 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?