Printable View
Hi everyone,
I received my Nexus 7 in mail yesterday and I've had problem KEEPING a steady WiFi connection. My laptop is keeping connection but the Nexus 7 drops connection at same place, pretty close to the router, every few minutes and then re-connects after about a minute of hanging.
Anyone else having issues keeping a WiFi connection?
Other than that tablet works perfectly. No screen leaks like other reported.
I'm having the same issue. Any work around yet?
Got the same problem, not every few Mins but like every hour or so, I mean what can be done?
Hi, all.
New here. Having MAJOR bogus issues connecting.
Has not connected once to WiFi.
Was planning on installing new router tomorrow anyways. We'll see if that is the fix.
Also, in the meantime, I found a little more techno forum addressing the same issues:
[Only registered and activated users can see links. Click Here To Register...]
Hope this is not against forum rules (posting another forum's URL. But the developers forum seem to think it my be a hardware issue or bug in the Jelly Bean.
Have a good evening.
I had the exact same issue the first night I had the 7. At first I thought it was my wifi, but tested other devices and none had the problem. I started a continuous ping on the nexus and found that every couple of minutes, the ping would drop. The nexus was still connected to the network, but traffic stopped.
To make a long story short (too late), I did a full wipe and restored the nexus back to factory. The problem went away completely. It's been about 5 days and have not had a single recurrence of the issue.
Sent from my Nexus 7 using Android Central Forums
I seem to be having this issue as well. I'll try the factory reset and see if that works.
My Nexus 7 connects fine at home, but at work with the WPA2 Enterprise using TLS it's a no go. I've found a few other links indicating this is a Jellybean issue. I don't think anybody has been able to connect using Jellybean without rooting their device. Supposedly there is a fix that can be applied, but you have to have root to apply it. There are bug reports logged with Google, also I've called Google's support line and they said they would look into it. Hopefully this will be fixed in a patch soon. Very disappointing to not be able to connect at work.Quote:
Originally Posted by gleg [Only registered and activated users can see links. Click Here To Register...]
When I power on my Nexus 7 (not wake from sleep) it takes almost a minute before it connects to my wifi. Also get a very weak signal if I go upstairs. :(
And it's this weak wifi signal that triggers the screen flicker. :mad:
Do not have this problem with my Transformer TF-101 , iPad 3 or PlayBook.
guys, this device looks weird to me. it appears they haven't tested the most important part of a tablet, the Wifi. :(
its so unstable. check this link [Only registered and activated users can see links. Click Here To Register...] .
I am suffering from same issue but only when I hold it top left in portrait mode.
See the pic and I also pasted the ping results. man it is timing out. :(
[Only registered and activated users can see links. Click Here To Register...]
Pinging 192.168.0.222 with 32 bytes of data:
Reply from 192.168.0.222: bytes=32 time=3ms TTL=64
Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
Reply from 192.168.0.222: bytes=32 time=21ms TTL=64
Reply from 192.168.0.222: bytes=32 time=3ms TTL=64
Reply from 192.168.0.222: bytes=32 time=6ms TTL=64
Reply from 192.168.0.222: bytes=32 time=3ms TTL=64
Reply from 192.168.0.222: bytes=32 time=10ms TTL=64
Reply from 192.168.0.222: bytes=32 time=5ms TTL=64
Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
Reply from 192.168.0.222: bytes=32 time=193ms TTL=64
Reply from 192.168.0.222: bytes=32 time=214ms TTL=64
Reply from 192.168.0.222: bytes=32 time=72ms TTL=64
Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
Reply from 192.168.0.222: bytes=32 time=5ms TTL=64
Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
Reply from 192.168.0.222: bytes=32 time=13ms TTL=64
Reply from 192.168.0.222: bytes=32 time=5ms TTL=64
Reply from 192.168.0.222: bytes=32 time=3ms TTL=64
Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
Reply from 192.168.0.222: bytes=32 time=5ms TTL=64
Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
Reply from 192.168.0.222: bytes=32 time=2ms TTL=64
Reply from 192.168.0.222: bytes=32 time=40ms TTL=64
Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
Reply from 192.168.0.222: bytes=32 time=2ms TTL=64
Reply from 192.168.0.222: bytes=32 time=2ms TTL=64
Reply from 192.168.0.222: bytes=32 time=110ms TTL=64
Reply from 192.168.0.222: bytes=32 time=15ms TTL=64
Reply from 192.168.0.222: bytes=32 time=27ms TTL=64
Reply from 192.168.0.222: bytes=32 time=49ms TTL=64
Reply from 192.168.0.222: bytes=32 time=50ms TTL=64
Reply from 192.168.0.222: bytes=32 time=67ms TTL=64
Reply from 192.168.0.222: bytes=32 time=142ms TTL=64
Reply from 192.168.0.222: bytes=32 time=64ms TTL=64
Reply from 192.168.0.222: bytes=32 time=58ms TTL=64
Reply from 192.168.0.222: bytes=32 time=17ms TTL=64
Reply from 192.168.0.222: bytes=32 time=7ms TTL=64
Reply from 192.168.0.222: bytes=32 time=12ms TTL=64
Reply from 192.168.0.222: bytes=32 time=36ms TTL=64
Reply from 192.168.0.222: bytes=32 time=5ms TTL=64
Reply from 192.168.0.222: bytes=32 time=14ms TTL=64
Reply from 192.168.0.222: bytes=32 time=85ms TTL=64
Reply from 192.168.0.222: bytes=32 time=5ms TTL=64
Reply from 192.168.0.222: bytes=32 time=5ms TTL=64
Request timed out.
Reply from 192.168.0.222: bytes=32 time=71ms TTL=64
Reply from 192.168.0.222: bytes=32 time=13ms TTL=64
Reply from 192.168.0.222: bytes=32 time=8ms TTL=64
Reply from 192.168.0.222: bytes=32 time=28ms TTL=64
Reply from 192.168.0.222: bytes=32 time=5ms TTL=64
Reply from 192.168.0.222: bytes=32 time=3ms TTL=64
Reply from 192.168.0.222: bytes=32 time=30ms TTL=64
Reply from 192.168.0.222: bytes=32 time=9ms TTL=64
Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
Reply from 192.168.0.222: bytes=32 time=3ms TTL=64
Reply from 192.168.0.222: bytes=32 time=8ms TTL=64
Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
Reply from 192.168.0.222: bytes=32 time=3ms TTL=64
Reply from 192.168.0.222: bytes=32 time=3ms TTL=64
Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
Reply from 192.168.0.222: bytes=32 time=7ms TTL=64
Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
Reply from 192.168.0.222: bytes=32 time=3ms TTL=64
Reply from 192.168.0.222: bytes=32 time=2ms TTL=64
Reply from 192.168.0.222: bytes=32 time=5ms TTL=64
Reply from 192.168.0.222: bytes=32 time=3ms TTL=64
Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
Reply from 192.168.0.222: bytes=32 time=6ms TTL=64
Reply from 192.168.0.222: bytes=32 time=6ms TTL=64
Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
Reply from 192.168.0.222: bytes=32 time=5ms TTL=64
Reply from 192.168.0.222: bytes=32 time=3ms TTL=64
Reply from 192.168.0.222: bytes=32 time=9ms TTL=64
Reply from 192.168.0.222: bytes=32 time=5ms TTL=64
Reply from 192.168.0.222: bytes=32 time=9ms TTL=64
Reply from 192.168.0.222: bytes=32 time=5ms TTL=64
Reply from 192.168.0.222: bytes=32 time=15ms TTL=64
Reply from 192.168.0.222: bytes=32 time=3ms TTL=64
Reply from 192.168.0.222: bytes=32 time=5ms TTL=64
Reply from 192.168.0.222: bytes=32 time=9ms TTL=64
Reply from 192.168.0.222: bytes=32 time=15ms TTL=64
Reply from 192.168.0.222: bytes=32 time=17ms TTL=64
Reply from 192.168.0.222: bytes=32 time=11ms TTL=64
Reply from 192.168.0.222: bytes=32 time=8ms TTL=64
Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
Reply from 192.168.0.222: bytes=32 time=13ms TTL=64
Reply from 192.168.0.222: bytes=32 time=31ms TTL=64
Reply from 192.168.0.222: bytes=32 time=22ms TTL=64
Reply from 192.168.0.222: bytes=32 time=26ms TTL=64
Reply from 192.168.0.222: bytes=32 time=38ms TTL=64
Reply from 192.168.0.222: bytes=32 time=48ms TTL=64
Reply from 192.168.0.222: bytes=32 time=34ms TTL=64
Reply from 192.168.0.222: bytes=32 time=63ms TTL=64
Reply from 192.168.0.222: bytes=32 time=236ms TTL=64
Reply from 192.168.0.222: bytes=32 time=207ms TTL=64
Request timed out.
Request timed out.
Reply from 192.168.0.222: bytes=32 time=393ms TTL=64
Reply from 192.168.0.222: bytes=32 time=120ms TTL=64
Reply from 192.168.0.222: bytes=32 time=15ms TTL=64
Reply from 192.168.0.222: bytes=32 time=39ms TTL=64
Request timed out.
Reply from 192.168.0.222: bytes=32 time=209ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.8: Destination host unreachable.
Reply from 192.168.0.8: Destination host unreachable.
Reply from 192.168.0.222: bytes=32 time=2182ms TTL=64
Reply from 192.168.0.222: bytes=32 time=272ms TTL=64
Reply from 192.168.0.222: bytes=32 time=241ms TTL=64
Reply from 192.168.0.222: bytes=32 time=207ms TTL=64
Reply from 192.168.0.222: bytes=32 time=202ms TTL=64
Reply from 192.168.0.222: bytes=32 time=217ms TTL=64
Reply from 192.168.0.222: bytes=32 time=206ms TTL=64
Reply from 192.168.0.222: bytes=32 time=221ms TTL=64
Reply from 192.168.0.222: bytes=32 time=25ms TTL=64
Reply from 192.168.0.222: bytes=32 time=8ms TTL=64
Reply from 192.168.0.222: bytes=32 time=49ms TTL=64
Reply from 192.168.0.222: bytes=32 time=10ms TTL=64
Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
Ping statistics for 192.168.0.222:
Packets: Sent = 126, Received = 119, Lost = 7 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 2182ms, Average = 60ms
Control-C