Related
Hi ppl, I'm having some serious problem with my wify connection getting lost every time since the 3.2 update the wify icon! Goes gray and blue each moment, it's like it lost the inernet from the router. Because of this gtalk doesn't keep connected. Hope y can help me here
Xoom wifi us stock 3.2
Hope ur xoom is not configured to get static IP from the router if yes remove the static IP or u can configure the static IP on the xoom itself hope it helps
Sent from my Xoom using Tapatalk
Yep, same issue here. I think there is a bug with the update...
Its no bug
Sent from my Xoom using Tapatalk
I had the same issue it use to dissconnect and get stuck at obtaining IP address when I removed the static IP I configured from the router i for xoom a day earlier when I got the update
Sent from my Xoom using Tapatalk
I have no problem getting an ip, and it's not static. And how do you know for sure this is not a bug? Are you and Android developer?
2 of us have the same issue afte updating. I bet there will be more as it rolls out.
I won't say anything here was just trying to help I faced a similar problem so I thought it might help you as we'll have fun figuring it out
Sent from my Xoom using Tapatalk
The router its configured to assign an static ip to my xoom. Until the update was perfect now doesn't keep the connection. Have to add that the xoom get its ip with no problem, but had I say keep disconnecting
ahmed007 said:
Hope ur xoom is not configured to get static IP from the router if yes remove the static IP or u can configure the static IP on the xoom itself hope it helps
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Wow this actually worked like a charm, it's weird that this be a problem with the xoom now, it should be totally transparent to it. Well I guess that later will come out some sort of explanation to this. Thx!.
Ur welcome
Sent from my Xoom using Tapatalk
I don't have such problems, but i want to point out that gray wifi icon doesn't mean there is no internet connectivity. If you disable sync the icon will turn gray, but you still have internet.
i have the exact same problem with losing connection to the Google server and the wifi icon switching from blue to grey constantly. When this happens my internet cennections also times out for a split second causing downloads in progress to end. I do also believe that it is a bug associated with 3.2. I've tried everything that I can think of to resolve it with no luck too. First I went through all of my router settings and did a wipe of the xoom. It didn't work so I went through the hassel of unrooting, relocking, and starting from scratch on 3.0, and I still have the same problem now that I'm back to 3.2. The xoom did not experience this issue on 3.0 or 3.1 and my Asus transformer is not having any problems running on the same connection, so the only thing left to blame my issues on is the 3.2 update itself.
droidx1978z4 said:
i have the exact same problem with losing connection to the Google server and the wifi icon switching from blue to grey constantly. When this happens my internet cennections also times out for a split second causing downloads in progress to end. I do also believe that it is a bug associated with 3.2. I've tried everything that I can think of to resolve it with no luck too. First I went through all of my router settings and did a wipe of the xoom. It didn't work so I went through the hassel of unrooting, relocking, and starting from scratch on 3.0, and I still have the same problem now that I'm back to 3.2. The xoom did not experience this issue on 3.0 or 3.1 and my Asus transformer is not having any problems running on the same connection, so the only thing left to blame my issues on is the 3.2 update itself.
Click to expand...
Click to collapse
I agree, my wifi turns off when the screen is off even though I have it set to always on!
I am also seeing some strange WiFi connectivity issues that I did not have on 3.1. The indication goes from blue to grey constantly and does cause a interuption of any downloads. Nothing has changed on my router or Xoom settings and both are set to dynamically assign the IP address. While I can still surf when it is grey, something is just not right. I have tried resetting both the router and my Xoom, nothing seems to solve this issue. This definately seems like a bug to me.
Can anyone confirm this is not an issue with the latest Tiamat kernel? I am currently 100% stock and this would give be one more reason to root.
HuckFinn said:
Can anyone confirm this is not an issue with the latest Tiamat kernel? I am currently 100% stock and this would give be one more reason to root.
Click to expand...
Click to collapse
I just finished reunlocking the bootloader, rerooting, and reinstalling cwm. I am in the process of downloading the deodexed 3.2/tiamat 2.0.0 rom to see if this has any effect on the wifi problems that I have been experiencing on 3.2. If this does not work then I am going back to 3.1 until another update comes out. I'll report back to tell you whether I still have these wifi issues tomorrow.
Unfortunately the deodexed 3.2/tiamat 2.0.0 rom did not help with my wifi issues. I flashed the tiamat 1.1 rom, which is based on 3.1 and now everything is working great. I don't know what my problem was with 3.2 or why so few people seem to be suffering with the same problem, but I'm sticking with this rom for awhile.
Was having similar wifi issues... connection retry messages in Market, failed to load web pages, etc. Additionally, network indicator remained primarily "gray". Removed DCHP reservation from router as recommended in earlier post and problem seems to have disappeared. Network indicator remains "blue" and retry messages have completely vanished. Thanks for suggestion
I think I have solved my issues. On the networks I manage (home and portable hotspot) I set the profile on the Xoom to use a static IP. What is strange is that on networks that I do not have control over (work and public hotspots) I left it as DHCP and I am not having any issues. I was having issues before I changed the OTHER profiles to static. Very strange.
I have opened issue 18648 at google code for this:
http://code.google.com/p/android/is...CP&colspec=ID Type Status Owner Summary Stars
DHCP seems to renew my IP address every 2-3 mins according to the adb debug log. Please star the issue if you are still getting it.
Just chiming in...I have a (new to me) XOOM with 3.2, 100% stock, no root, no funny business -- and I have the exact same problem.
There is a constant shift from blue to grey WiFi connection status icon, and issues with playing games online (server disconnections) and downloading apps.
I watched the log and do not see DHCP re-attempts as a new comment suggested, however.
I will attempt to set a static IP when I am home tonight and see if that fixes my issues there...
Hey, scoured the NC forums for any answer, no luck.
I just got a new router, and setup encryption with WPA/WPA2 PSK. All of my devices (laptop, wii, phone -- an HTC Evo SHift w/ cm7) connect without issue.
My NC (with CM7 stable & Dal OC kernel) will attempt connect... authenticate, then say disconnected. Sometimes it'll loop, sometimes it won't.
Now, would re-flashing CM7 or my kernel fix this? Would a different kernel fix this> What can I do? I get real sick of having to logon to guest access all the time
That particular symptom that your describing is very indicative of a bad password. You might try grabbing something like free logcat and see what the actual error is.
Tekara said:
That particular symptom that your describing is very indicative of a bad password. You might try grabbing something like free logcat and see what the actual error is.
Click to expand...
Click to collapse
I know the password is 100% right, because all of my other devices connect.
After a few failed connects, it says "disabled" next to my wifi
I'm gonna try a logcat, thanks for the tip
I/wpa_supplicant( 2050): Authentication with 00:00:00:00:00:00 timed out.
Can anyone help?
This is a shot in the dark. The stock NC (rooted) has had all sorts of wifi problem. See http://forum.xda-developers.com/showpost.php?p=11458921&postcount=1
Finally after BN1.3 came, all my wifi problems went away. My NC connects at home with 802.11n, WPA2 encryption. It previously had connect/disconnect problems at home and at work, a multipoint 802.11n high speed system. Now the NC connects flawlessly everywhere. There may be chance that Dalingren's latest OC kernel may have fixed it too.
This may or may not help depending on where the CM7 wifi drivers came from.
I added the EI03 ROM for the verizon LTE tab. Everything was great, only problem was it was a little slow. Had it for two days. Today, I get home form work and the damn thing wont connect to Wifi. It sees my home network but gets stuck and says "obtaining IP adress". The crazy thing is I can connect to 3g or LTE with no problem...My Driod Bionic and this laptop are currently on the same network.
Heres what I have done...
1) I unplugged my router and modem for ten minutes twice.....no luck
2) I tried the Allshare work around that peopl posted about...nothing
3) downloaded the galaxy tab DHCP fix app ....nothing
4) reset the tab at least 7 times....nada
I am guessing this is the 3.2 Build? I got nothing else. I am guessing I have to reload 3.1 and go back to liquidspeed....
Am I missing someting? is there ANY suggesitons?
Thanks in advance
You've probably done it but haven't listed it; delete wifi network settings for your network and set that up again . . . then if that doesn't work delete ALL wifi network settings for ALL networks you've connected to and set up your network again . .
If after all that you still get nothing, see what happens when you strip all network security temporarily from your network, just to see if wifi is truly hosed on the tab.
Just brainstorming things I'd try before going back to Liquidspeed.
So far my wifi has been rock solid for the past two days. At home I'm running WPA2 Personal and at work I'm running standard WEP. I toggle my wifi on/off when I leave either location and haven't had any connection issues thus far.
I did that as well. Literally everything connected to the router without encryption on except the tab. It just was suck on "obtaining IP address"
after some research this seems very similar to the wifi cutoff issue the wifi only owners had with the 3.2 official OTA update that Samsung had to fix.
I'm hoping this isn't the case. Any body else got any other suggestions
Sent from my DROID BIONIC using Tapatalk
UPDATE
I see what went wrong. In an effort to re root the tab, I applied Kernel.zip that should only be used for 3.1 LTE devices.
I reloaded TW 3.2 on the LTE and could connect to wifi immediately. When I tried to root again, I applied kernel and this happened again.
Apparently I dont get this. Oh well. I a, gonna go back to EG01 where I am comfortable rooting and Overclocking.
The instructions said to apply Recovery (the new one), but ti continued to fail, so I assumed I needed to apply kernel first. This is just not working for me.
I tried and failed about 4 times. back to the original rom it is
reloading 3.2
How did you reinstall 3.2? I'm having the same wifi issues on my GTab LTE.
I've worked around this problem; I just thought developers might be interested in my experience...
I use a WRT54G for wifi in my house; it's an old device (v 3.0), but it's been rock solid for years. I also use a Nook Color, which until a week ago, was running CM7.1. The router was configured to use WEP. Everything was hunky dory.
I installed CM9 on my NC, and started to notice strange behavior from my WRT54G - every few hours, all wifi connections in the house would be dropped. I would need to reset the device to get things working again.
Through experimentation, it was clear that the NC was causing the issue. I have no idea why, but the interaction between the two was making the WRT54G very unhappy.
Thinking it might be buggy firmware on the WRT54G, I updated it to the latest version. Same behavior. Thinking it may be an issue w/ CM9, I installed the ICS version of AOKP on the NC. Same behavior. So, it doesn't seem to be a problem w/ a specific ROM, but rather something in the ICS networking stack. I was using WEP this entire time, and did not test to see if other configurations would work properly.
My final solution was to install DD-WRT on the router. Problem solved. So, perhaps this isn't an issue w/ ICS, but rather the Linksys/Cisco firmware on the router.
Just FYI.
I hate the stock firmware on the WRT. But DD-WRT runs great.
Sent from my xt862 using xda app-developers app
With 4.2.2 I had no issues with wifi and can still go back to that version and have no issues, but with version 4.3 and 4.4 I have had and still have the following problem.
I have a list of known wifi connection points as well as available access points. Everything appears as it should, but the wifi will not automatically connect to any wifi (protected or unprotected/known or previously unknown) without first turning the wifi off and back on. Additionally, this only works if the persistent background wifi option is toggled off. If I do toggle the wifi on and off and connect to an available access point everything is fine so long as I remain in range and stay connected. If I go out of range and lose the connection, when I next reenter the range and the access point shows up on the list it will not connect unless wifi is cycled on and off. This happens every single day at work and home, although there is a workaround, it is quite annoying to have to cycle the wifi off and on. The networks will show as available and if I click on them and try to force it to connect, it still won't work unless I cycle on and off.
I have seen prior threads with this issue on 4.3 and there was a topic in the official Google issues page and was frankly hoping desperately that 4.4 would fix it, but alas, it has not. I know it is not the device itself since reverting back to 4.2.2 solves the problem.
Does anyone know of a permanent fix to this wifi issue that doesn't involve reverting to an older version of android or some kludged together solution?
Ya.. I have also been facing this problem since i have installed KitKat 4.4 on my i9300
Are you stock? Maybe try another ROM? I had the exact same problem, but my problem was my wifi AP.
1- My router was setup for a/b/g/n, I set it to only what I really had using the Wifi AP, which was g/n
2- I had a weird cable modem to router to Wifi AP setup. The router was handing out IPs, not the Wifi AP. I removed the router and only let the Wifi AP give IP addresses (DHCP). It seemed like the "further hops" away that the DHCP addresses were, the more issues i had with my Android connection.
No other devices on my network had these issues, but doing the above made a world of difference.
All that made my connections lightening quick, no issues at all since then.
odd Wifi behaviour
I got a refurbished delivered N10 last evening, came with 4.2.2, played with it a little, did a network benchmark test (FTP off a LAN NAS) and was getting comparable peformance to my other fastest system (a Thinkpad Ubuntu laptop). It seemed stable but I only used it for like an hour as 4.2.2. I was getting FTP of max 4MB/s over a N-router.
I then let it OTA to 4.3 and then played with it for some hours. Issue I found was the Wifi would work and then have "authentication problem" I had to turn Wifi off then on to make it connect to router. I've had that issue with other devices at times. I was thinking of staying on 4.3 to allow 4.4 to have another bugfix (its not been long out on N10) but I had a key issue for me (PPP Widget didn't work) so I did a stock 4.4. flash upgrade.
On 4.4. the Wifi speed is still fast, but periodically it just stops working, a glitch.
One key thing that stands out is the N10 is connecting at much higher Mbit speeds than any other of my devices, it is showing 130Mbits vs say 20-65Mbits on other devices. I'm wondering if my N10 is "too good" for my router an old low-spec refurbished model (Cisco E1200 v2, which I flashed to latest DD-WRT) ?
I'm not so far disappointed with network performance, just network stability, but I can't tell for sure if its the N10's fault or my router's fault. I'll play with settings a while til I find something stable.
When I first got my N10 I had a lot of trouble with wifi connection. Mostly authentication issues, or it would authenticate but not have internet access. It was frustrating, and Google's support was clueless.
I then tried using wireless tether from my N4 and it worked as it should. The issue ended up being the Arris router that Time Warner uses. I bought a Linksys router and have had 0 issues since. So if you're using an Arris router, or it shares the same chipset, that might be the issue.
The router is the Arris DG860.
Ichiban Rei said:
When I first got my N10 I had a lot of trouble with wifi connection. Mostly authentication issues, or it would authenticate but not have internet access. It was frustrating, and Google's support was clueless.
I then tried using wireless tether from my N4 and it worked as it should. The issue ended up being the Arris router that Time Warner uses. I bought a Linksys router and have had 0 issues since. So if you're using an Arris router, or it shares the same chipset, that might be the issue.
The router is the Arris DG860.
Click to expand...
Click to collapse
Good anecdote.
Well in our house, the proliferation of gadgets has changed progressively to a large number, I make it 14 devices from an initial 2 devices 5 years ago. I count 4 wired and my 4 devices, my son's 2 and my daughter's 3 and my wife's 1. They all compete for router bandwidth, Wifi spectrum, router CPU / cache.
What I might do with this high-performance (capability and demand N10) is segment my network using an old G router I hard fix to non-overlapping channels from N-router, and connect the low-spec devices to the G and high-spec to the N. That will involve no $ and naturally reduce congestion. I run a NAS and download media to it and then stream to gadgets off NAS so I'm Wifi-limited often more than Internet-limited, and even tweaking I get 2MB-4MByte (16Mbit~32Mbit) off a NAS is making my typical LAN speed the same as the Internet bandwidth I buy (16Mbit).
My NEtbook (EEE 1015PN) if it ever felt a Wifi hiccup it would lock-out that frequency and so not see the router til I powered off netbook and remove battery.
I do wonder if some of the N10 Wifi complaints are really just generic or bad combinations with router or "straw that broke the camel's back".
I'm having wifi issues with my N10 as well. I had a few wifi issues at work, but not at home while using 4.3. Now with 4.4 I'm having serious wifi connection issues both at work and at home. In fact my N5 running 4.4.1 is having issues connecting to wifi both at work and at home. Not as often as my N10, but it still happens. I'm running stock on both and have no problem connecting to either network with my laptop.
I've installed wifi fixer, but so far it doesn't seem to be helping much. Does anyone have any suggestions on what might be done to fix this that doesn't involve rooting either device?
I'm now running 4.4.2, and I'm experiencing better wifi connectivity, but it still drops out more than it did on version 4.3. Is anyone else having this issue?
Sent from my Nexus 10 using Tapatalk 4
droidfan77 said:
I'm now running 4.4.2, and I'm experiencing better wifi connectivity, but it still drops out more than it did on version 4.3. Is anyone else having this issue?
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
I'm in the same boat, more drops in 4.4.2 than on 4.3 and I'm running stock
same here...waiting for a fix
experiment with the router
metzner said:
same here...waiting for a fix
Click to expand...
Click to collapse
Some of your problems might be just coincidence, something changed in your area around the same time as you upgraded. Some of these are just the wrinkles of firmware of device vs firmware of router, some combinations work bad and isn't really "fault" of Android in that you can't test every combination. You could wait for a fix from Android... or just try to avoid the wrinkle by changing settings on the router. A common thing is to move the router from auto to fixed channel and fix to 20mhz narrow. Go the place you mostly are with the N10 and use a Wifi analyser to find the least-congested channel and then set the router to that. What that does is reduce channel-hopping and gives less opportunity for firmware issues on both router and the Android device.
I also had a problem with my N7 when I moved house. The answer was to flash DD-WRT on my router and the problems went away.
So either wait+complain or go look at your router now.
Right now I have DD-WRT on an old refurbished Cisco E1200 and I set it to channel 3 with 20mhz and I got very good Wifi performance. With the stock Cisco firmware I was getting Android Wifi drops and poor performance. Yes, that's partly Android's fault but I fixed it myself quicker flashing firmware on the router.
I also took opportunity in DD-WRT to setup IPTABLES for a transparent proxy so all the devices in my LAN now share a large harddrive as http cache so e.g. any downloads from Play store for say my N4.... is cached to my N10 so I only ever download anything once.
If you have issues still with the N10, then what I find solves a lot of problem is do a stock flash of 4.4.2, on setup untick all the backup+restore from Google, then manually install and configure yourself to make it "vanilla". That often fixes accumulated wrinkles unique to your history of your device and places to more mainstream with less likely of having a unique problem. I do that on all my Android devices now (N4, N7, N10).
Similar wifi problems here
I've had similar issues with my N10.
I will have fast internet speeds (30+ Mbps) and it will just freeze. I'll be watching youtube and it will start buffering. Doing a speed test on my phone shows the speeds as normal. It makes no difference whether connected to 2.4 GHz or 5 GHz wifi.
I just resolved my WiFi issue this past weekend. Connectivity is rock solid
Here is what I did I.
Purchased my own cable modem/router. New router had updated firmware. time warner cable modem did not.
Change beacon interval from 100 to 20 on router and repeater.
Made sure router was on a less congested channel.
All is rock solid
YMMV
bflatmajor said:
I just resolved my WiFi issue this past weekend. Connectivity is rock solid
Here is what I did I.
Purchased my own cable modem/router. New router had updated firmware. time warner cable modem did not.
Change beacon interval from 100 to 20 on router and repeater.
Made sure router was on a less congested channel.
All is rock solid
YMMV
Click to expand...
Click to collapse
Great! Often just tweaking settings can do wonders. I flashed DD-WRT on mine and it solved a lot of issues on an old low-spec router.
Hey Guys,
I posted this in General section but saw this so I will add this info:
I just want to share what and why I did it. First off I did not have problems with my wifi on 4.2.2 with the Nexus10. the second that I went to Slim Kat and Vanir 4.4.2 I had weak wifi signal at work and at home when my nexus 7 slim kat and my galaxy note 2 Vanir did not. I noticed that RAM was also weird on the nexus 10. Even though it showed 2gb of ram on the specs it was only showing 1099 on 4.4.2 when I show that I have 1647 ram available with 4.2.2.
Concerning the OS using Ram. Google said that they would make Kit Kat more RAM friendly but I was using 535mb of RAM for 4.4.2 and right now I am showing only 357.3 mb for 4.2.2. I am using the same apps launchers and screen savers
I just flashed back to 4.2.2 this morning so I will update later, I do see an improvement in the wifi though.
I just want to say that I love Slim Kat and that is why I am on the 4.2.2 I just think Google somehow hosed up the wifi on the Nexus 10.
B][/B] Ok so I am at work and have went back and forth between 4.4.2 and 4.2.2. the 4.4.2 connects and disconnects back and forth. When it does connect to router but it says poor connection and it is only 24mbps. "It drops way more than connected" I am 45 ft from router in an open environment.
The 4.2.2 Slim Kat has a fair connection with 78 Mbps and has not dropped once. So I don't know what the difference is with Kit Kat compared to Jelly Bean but for my nexus 10 my wifi is great now with Jelly Bean. I wish I could figure out why and fix but I do not know programming.
I also installed on both 4.4.2 and 4.2.2 a app called WiFi Connection Fixer *Root* by ZEXTR. It did not help 4.4.2 but it did help with 4.2.2. this app helps connect to poor connections or when Android says avoided poor connection.
I don't know why the Nexus 10 is having issues with wifi with KitKat but I wish I could fix it. So I will be on 4.2.2 until a new version comes out and I will test it to see if it fixed it.
update; I have used 4.2.2 all day with the wifi connection fixer and I have not dropped wifi once and the download speed is fast. It is much faster than what 4.4.2 was, at least on my tablet.
Joe
Nexus 10 4.4.3 WiFi Bottleneck Problem
Hello there everyone,
I just wanted to confirm that I personally found a fix on my end for my Nexus 10 WiFi bandwidth problem that was definitely evident for many people that upgraded from 4.4.2. First off, I'm totally stock. I will most likely root & ROM this thing in this near future. I was having a bottleneck on my Nexus 10 around ~2 mbps when I tested using the speedtest.net application (may not be the best measurement application but it works). I ended up fixing the problem by changing my router settings in the WiFi section of my browser based software to N/G Mixed instead of just Mixed (which allows 802.11a/b as well as 802.11g/n to run on the router's WiFi signal). I use DD-WRT on my router as well so that may have played a factor in it but I did NOT see an increase in bandwidth until making the N/G Mixed change in the settings. I found this suggestion earlier in the thread and wanted to give it some credit. Thanks everyone!