Related
anyone else having the problem of wifi no longer connecting after updating TO froyo?
edit:
Okay just had coworker enable his nexus as a hotspot and I connected fine.
Must have something to do with the phone's wifi driver and home router.
Wifi still good for me.
Re: Wifi no longer working with paul's froyo
I see a bunch of people reporting alot of bugs in Froyo, i havent seen any bugs yet. My answer to OP is: No.
-------------------------------------
Sent via the XDA Tapatalk App
i can't get wifi to work on any froyo!
it's just obtaining the ip adress but not connecting
i'm having the same problem on my phone. i flashed the stock rom update-nexusone-EPF21B-signed, the the frf 50 rom and everything was working fine for a few hours then suddenly it stopped working. now when i try to turn on my wifi, it just scans then says it's disconnected then starts scanning again.
everything is working fine but i just can't get any wifi! :'(
Okay, glad I'm not the only one. Wonder how we can go back to older wi-fi drivers.
WebghostDK said:
I see a bunch of people reporting alot of bugs in Froyo, i havent seen any bugs yet. My answer to OP is: No.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
This, I think there's a lot of operator errors going on that are being blamed on FroYo
TFJ4 said:
This, I think there's a lot of operator errors going on that are being blamed on FroYo
Click to expand...
Click to collapse
Hey if you got any ideas on what I did wrong, I'm all ears. All I know is wifi worked fine before switching to Froyo.
(but the new wi fi drivers didn't work on 2.1 either and i had to go back to the old ones)
Re: Wifi no longer working with paul's froyo
Mine disconnects after a while of not using the phone. Wifi on profile widget stays on. But in wifi settings it shows not in range which shouldn't happen anywheree in my apartment.
Need to turn off and turn onwifi again to reconnect.
-------------------------------------
Sent via the XDA Tapatalk App
tanman1975 said:
Hey if you got any ideas on what I did wrong, I'm all ears. All I know is wifi worked fine before switching to Froyo.
(but the new wi fi drivers didn't work on 2.1 either and i had to go back to the old ones)
Click to expand...
Click to collapse
if more than one person is having a problem, i'm certain it's not a user error like one person said it could be (quite an asinine comment if you ask me). it's never an operator error when you turn off your wifi and half an hour later you try to turn it on only to discover it won't turn on.....how the hell is that an operator error?
i didn't have any problems whatsoever. check the md5 hash, make sure your download was fine.
make sure you wipe everything, then reinstall. if you have old data cache'd, and then tried to flash the update, that may very well be the problem.
Yeah, having troubles connecting to 802.1x EAP Wireless Networks, PSK works fine for me at home.
Yes, I wiped, checked MD5 etc..
I'm using Pauls Rooted Froyo zip
i made sure to wipe data/cache/dalvik cache/battery and rotation. i do this everytime i switch roms. after 12 hrs of working fine, i just don't understand why it suddenly quit. before i flashed to froyo, i made sure to read up as much as possible to ensure i didn't miss a step. the worst part is, no matter which rom i'm using now, i have no wifi.
one thing i noticed is pre-froyo, when i flashed pershoot's kernels with new WiFi drivers i could not connect at home, but when i used kernels with older drivers, I was fine. That said, maybe it will work with other WiFi access points a la the point made about not working with certain WiFi router types. Will test when I have the opportunity.
one thing i noticed is pre-froyo, when i flashed pershoot's kernels with new WiFi drivers i could not connect at home, but when i used kernels with older drivers, I was fine. That said, maybe it will work with other WiFi access points a la the point made about not working with certain WiFi router types. Will test when I have the opportunity.
----------
edit:
Okay just had coworker enable his nexus as a hotspot and connected fine.
Must have something to do with the phone's wifi driver and home router.
I had problems connecting to my router (a Belkin N1). I set a static IP on the Nexus One and then it works perfectly.
I have tried to connect to my work router and it got a DHCP lease fine and worked fine (only at 54Mbps G speeds).
Perhaps this new radio image has N enabled and something is screwing up with the DHCP lease. I will try to replace my home router with another N router and report back.
I had the same problem with a message saying connecting but not picking up the IP address.
I suspect it was a conflict with the Static WiFi app I was using. I've unloaded this and after restarting and re-saving the static ip details it connected up OK.
For now I'll have to switch between static and dhcp manually I guess....
I came from Desire R19. My wifi doesn't connect as well now, i.e. seems to need a stronger signal from the AP. Last week I was getting 2 bars of wifi for the AP in my office, and now I get 1 or none. I'm getting a bar or two less at home too. I'm guessing some kind of difference in the Radio.
WiFi issue I have seems to be AP manufacturer specific
At home
Pre 2.2 I could connect without problem to my Linksys WRT 600N, no problems, DHCP etc.
Post 2.2 I cannot connect, gets to acquiring address and then craps out and re-scans
At work
Cisco wireless kit, (no idea of type of AP) pre 2.2 connected OK, post 2.2 connects OK
WPA2 security on both setups
Hi all, newbie poster, but been on the forums for about 2 weeks. Thanks for all who have provided such great methods to unlock the full potential of the NC!
I flashed to Decad3nce's 1.1 ROM yesterday from my Autonootered 1.01 setup, and was able to get most issues worked out, but the one thing left that's bugging me is the WiFi. When I initially boot up, it seems the device recognizes my WiFi network, and connects. However, after I resume the NC from sleep, it doesn't reconnect to my access point. In fact, the only way I've been able to get the connection back it to use the stock browser, at which point I'm asked which network to connect to. It says my network is "remembered", but it won't connect automatically, I need to manually connect every time.
Any ideas on why this is happening, and how I can get the NC to automatically connect to my network after resuming from sleep?
Thank you!
Hi there. Wass havingg the same issue you had. Take a look at the instructions for enabling adhoc wifi on Nookdevs.com Wether you want to enable adhoc or not that's up to you. But i followed the directions for Settings Profile Pro from there. Now everytime i turn off my screen and turn it back in. My nook connects right away to my wifi network.
Edit: Mine connects fine. But with my wifes nook. If she is coming off a reboot. She would have to goto settings and connect initially. But after that. Everytime she turns off her screen and turns it back on it reconnects right away.
Good luck.
Sent from my "NookDroid" using XDA App
Been having a similar issue without the 1.1 rom. Can't connect to my own wifi unless i reboot router but it connects to other wifi fine.
Anyone hits a clue or is it my network (my laptops iphone and desktop all run fine on my wifi)
sent from my nootered nook color
phirephotog said:
Been having a similar issue without the 1.1 rom. Can't connect to my own wifi unless i reboot router but it connects to other wifi fine.
Anyone hits a clue or is it my network (my laptops iphone and desktop all run fine on my wifi)
sent from my nootered nook color
Click to expand...
Click to collapse
I had that problem with 1.01. It occured after I ran the script for swapping the adhoc and infrastructure supplicants without disabling wifi first. The only thing that fixed it for me was a full reset from 1.0.0. Router was a verizon fios router/modem.
I had this problem before and can't test if it still happens but for me it only happens with one wireless network and all the others are fine. Is that the way yours behaves? Since it worked fine with others I didn't really worry about it
You said you can only get it to work by opening the browser - does that mean it doesn't work if you toggle wifi off and on? That was usually how I got it to connect to that one network
Same issue. After sleeping it sees my AP but doesn't connect. Turning wifi off and on recovers it.
Ultimoose said:
Same issue. After sleeping it sees my AP but doesn't connect. Turning wifi off and on recovers it.
Click to expand...
Click to collapse
same here but only if it has been sleeping for a while
sidenine said:
Hi all, newbie poster, but been on the forums for about 2 weeks. Thanks for all who have provided such great methods to unlock the full potential of the NC!
I flashed to Decad3nce's 1.1 ROM yesterday from my Autonootered 1.01 setup, and was able to get most issues worked out, but the one thing left that's bugging me is the WiFi. When I initially boot up, it seems the device recognizes my WiFi network, and connects. However, after I resume the NC from sleep, it doesn't reconnect to my access point. In fact, the only way I've been able to get the connection back it to use the stock browser, at which point I'm asked which network to connect to. It says my network is "remembered", but it won't connect automatically, I need to manually connect every time.
Any ideas on why this is happening, and how I can get the NC to automatically connect to my network after resuming from sleep?
Thank you!
Click to expand...
Click to collapse
Well, it looks like no immediate solution to this other than starting from a factory reset. I restored my backup ROM from CWM that I saved prior to flashing to 1.1.0, and WiFi is working fine again, so I'll stay here on 1.0.1 until I hear of a solution. Plus, XDA app works as expected in 1.0.1 as well. Thanks for any additional help!
I'm having the same issue as others.
Decad3nce wanted some logs so I pasted them into PasteBin:
dmesg - pastebin.com/wsajYF77
logcat - pastebin.com/gPasCEtZ
racks11479 said:
Hi there. Wass havingg the same issue you had. Take a look at the instructions for enabling adhoc wifi on Nookdevs.com Wether you want to enable adhoc or not that's up to you. But i followed the directions for Settings Profile Pro from there. Now everytime i turn off my screen and turn it back in. My nook connects right away to my wifi network.
Edit: Mine connects fine. But with my wifes nook. If she is coming off a reboot. She would have to goto settings and connect initially. But after that. Everytime she turns off her screen and turns it back on it reconnects right away.
Good luck.
Sent from my "NookDroid" using XDA App
Click to expand...
Click to collapse
Thanks for this post. This seems to have solved the problem for me.
Edit: Actually this didn't work I just didn't let it sleep long enough. Once it sleeps for several minutes WiFi requires a reset to reconnect.
rodneyshupe said:
I'm having the same issue as others.
Decad3nce wanted some logs so I pasted them into PasteBin:
dmesg - pastebin.com/wsajYF77
logcat - pastebin.com/gPasCEtZ
Click to expand...
Click to collapse
Dmesg shows nothing wrong with tiwlan driver.
Logcat shows that the "nookwifimanager" just fails at reconnecting to preconfigured networks
Code:
D/NookWifiManager( 1188): Cannot connect to pre-configured networks
What kind of security do you have on your router? (might be wep bug)
Other than that, you can try using the patched wpa for ad-hoc
I was having an issue where it it would connect to Wi-Fi for a minute and then disconnect. I could turn off wi-fi and repeat the process. I restored to my last CW backup then I used the 1.1_r2 and everything worked perfectly. I'd rollback to the backup you did (if you followed Deced3nce's steps) then use the r2 update. It's made all the difference for me.
I flashed r2 and I'm having the same issue...I have to turn off/on wifi after it goes to sleep in order for it to connect
Xhorder said:
I flashed r2 and I'm having the same issue...I have to turn off/on wifi after it goes to sleep in order for it to connect
Click to expand...
Click to collapse
Did you flash it over top of r1? Or did you start with 1.0.1? And were you using any special kernels prior to the flash?
similar issue - wifi only works after a reboot. after sleep it can see but cannot connect to either adhoc or infrastructure networks. no fix other than to reboot. which is a huge PitA
one4thewings said:
Did you flash it over top of r1? Or did you start with 1.0.1? And were you using any special kernels prior to the flash?
Click to expand...
Click to collapse
I actually flashed it over rooted 1.0.0. And I was running the 900 mhz kernel
I am having a wifi connection issue with CM7 nightly build 14&15. When i try to connect to my wifi it allows me to type in my passcode then proceeds to attempt the connection. It appears to be caught in a loop or something. Under wifi connection it shows scanning, connecting, then disconnected then it repeats. Wifi works fine under stock unrooted, rooted and nookie froyo SD. Does anyone else have this issue? I cannot post to android development yet. Thanks in advance.
I have a clean flashed 15 right now, and wifi is working stellar. Did you by chance not format cache/data, and still have a bunch of saved hotspots in wireless? I know a fix earlier was to "forget" all the saved wifi hotspots, and resave them.
Same problem I have been experiencing among others. It seems like if your router is using WPA you will have problems connecting. Switching to a different security encryption or wiping all remembered access points seem to be the only solution that I know of.
Yes, I formated system, data and cache when installing. CM7 works great on my Evo 4g, strange. I tried forgetting the hotspot and received the same error. Will try an unencrypted hotspot and will report back. Don't really understand why I am having this issues and others aren't. Thanks for the replies.
Sent from my PC36100 using XDA App
I've seen like 6 other people with this problem its not just you.
I'm experiencing the same problem of Wifi flashing on and off when I try to connect to a WPA encrypted router. Will try to Forget saved networks and see if that solves the problem. I'm running phiremod's version of CM7.
Mallinj. Same issue here with phiremod. Forgetting did not work for me. Let me know what happens for you. Thanks.
Sent from my PC36100 using XDA App
Guys check out my thread. I was having the same wifi loop problem.
It's [Problem 1]
http://forum.xda-developers.com/showthread.php?t=988802
I had the same issue toggling airplane mode on and off fixed the issue for me however the little airplane icon stayed for a while then just disappeared after a reboot
Sent from my Ginger Tazz using XDA App
That wifi file is named nookie froyo. This definitely works for cm7?
Usually what I have to do is some voodoo with toggling airplane on, then let wifi loop for about five minutes before it finally connects.
Been having this issue as well, what I have been doing when it has been switching on/off in the Wifi Settings is hitting Menu > Advanced settings and waiting a few seconds and it usually connects just fine.
cabbieBot said:
That wifi file is named nookie froyo. This definitely works for cm7?
Usually what I have to do is some voodoo with toggling airplane on, then let wifi loop for about five minutes before it finally connects.
Click to expand...
Click to collapse
Yeah it works. It takes the working wifi file from nookie froyo and pushes it to your CM7 file.
Has anyone submitted a bug report with cyanogen yet?
Sent from my PC36100 using XDA App
ChickenGod said:
Yeah it works. It takes the working wifi file from nookie froyo and pushes it to your CM7 file.
Click to expand...
Click to collapse
I am really hoping I don't start having this problem. The nookie froyo wpa_supplicant file for me was never connecting to ad-hoc, and right now I am connecting to anything.
Send from my Palm VII using courage
sigma0824 said:
I am having a wifi connection issue with CM7 nightly build 14&15. When i try to connect to my wifi it allows me to type in my passcode then proceeds to attempt the connection. It appears to be caught in a loop or something. Under wifi connection it shows scanning, connecting, then disconnected then it repeats. Wifi works fine under stock unrooted, rooted and nookie froyo SD. Does anyone else have this issue? I cannot post to android development yet. Thanks in advance.
Click to expand...
Click to collapse
I had this same problem yesterday morning. What I had to do was forget my network's settings, turn off wifi, then go turn off my router, turn the Nook's wifi back on, let it sit for a few seconds, turn my router back on, then try to connect. Strange as it sounds, this actually worked.
Time pilot aka, Thanks for the tip! Will try it later today.
Sent from my PC36100 using XDA App
Finally
I was able to solve my connection loop issues. I tested WPA and WEP on my D-Link Wireless N router DIR-615 with no success. Tried toggling on and off with airplane mode. Tried forgetting my router, turning things on and off at different sequences and intervals.
Then I set my router to B&G only. Basically turning wireless N off and it worked like a charm. I am able to connect using any encryption method. So from my experimenting it was the wireless N protocol that was the issue.
For people out there with issues and want to keep their wireless router encrypted try turning wireless N off. Worked for me.
Thanks everyone for their input.
I thought this was a CM 10.2 problem so I reverted back to 10.1 final and am having the same issue. My Nook will display that it's connected to wifi but when I try to load anything I get nothing. The only way to solve it seems to be to turn wifi off and then on. When I let it sit for a while and come back to it I have to do the reset again. Is there something wrong with my hardware or is this a common problem? It's happening on two of my Nooks. Thanks.
hfeigel said:
I thought this was a CM 10.2 problem so I reverted back to 10.1 final and am having the same issue. My Nook will display that it's connected to wifi but when I try to load anything I get nothing. The only way to solve it seems to be to turn wifi off and then on. When I let it sit for a while and come back to it I have to do the reset again. Is there something wrong with my hardware or is this a common problem? It's happening on two of my Nooks. Thanks.
Click to expand...
Click to collapse
If it does it on both CM10.1 and CM10.2, sounds like a router problem to me.
Sent from my Galaxy Tab 2 using XDA Premium
leapinlar said:
If it does it on both CM10.1 and CM10.2, sounds like a router problem to me.
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
But why just the Nooks? Everything else is fine on my router to include two Android phones.
hfeigel said:
But why just the Nooks? Everything else is fine on my router to include two Android phones.
Click to expand...
Click to collapse
not sure but ya one of the wifi protocols maybe "N" is a problem if its enabled.
Do a google search for Nook HD+ wifi disconnecting and you'll find which one
you need to disable on your router.
Mine did that as well, so I disabled that one protocol and its been ok
ever since.
Or it's a CM problem. I switched to Carbon and the problem seems to have gone away. Disabling n is not an acceptable solution, at least not to me.
Sent from my BN Nook HD using XDA Premium 4 mobile app
I tried assigning the Nooks a. Static IP but that didn't help. I suppose that I could bump my 2.4ghz network down to 54mps Max, but I dislike that solution.
Sent from my BN NookHD+ using xda app-developers app
Wifi disconnects
Was there a solution to this? My nook hd+ running CM11, version 11-20140403-NIGHTLY-ovation.
My Wifi disconnects intermittently. For example, I might be connected for 10 minutes, and then it just stops working. I have gotten used to having a terminal open pinging my gateway or AP. Latency is typically 2 to 4 ms, but jumps to 90, then 200, then timeout. I have to toggle Wifi or airplane mode to get it to reconnect.
coreyfra said:
Was there a solution to this? My nook hd+ running CM11, version 11-20140403-NIGHTLY-ovation.
My Wifi disconnects intermittently. For example, I might be connected for 10 minutes, and then it just stops working. I have gotten used to having a terminal open pinging my gateway or AP. Latency is typically 2 to 4 ms, but jumps to 90, then 200, then timeout. I have to toggle Wifi or airplane mode to get it to reconnect.
Click to expand...
Click to collapse
As far as I know there isn't. I just updated past the April 13th cm11 build (which I thought I did before but didn't *smacks head into wall*) which fixes a wlan bug and am checking to see if that works right now as I have had the issue on two cm11 devices.
However, I noticed my wifi Access Point has been seeing power failures so unsure if that's related at this time.
I'm not sure of it being the router or ap as one device may be working while one won't be so its possible its cm.
It might be possible to use an app like 'wifi fixer' (I think it can do that) to automatically toggle wifi on/off, to fix it as a workaround. Not at that point in testing yet.
hfeigel said:
The only way to solve it seems to be to turn wifi off and then on.
Click to expand...
Click to collapse
I have a similar problem with WiFi on my HD+ running CM 10.2.1, but not exactly the same. In my case, we have two wi-fi access points (i.e., two routers) in the house on different channels. I stay connected 100% on whichever I first connect with. But over time, the HD+ stops scanning, and doesn't see the other router. (Or the neighbors' wi-fis.)
I remembered seeing something about this with CM when I first joined the forum - the solution is to turn wi-fi off and then on. It rescans, and everything is okay again.
I wonder if it has something to do with the "Wi-Fi optimization" option, that "minimizes battery usage on Wi-Fi." But I haven't tried disabling that. Guess I'll do it now and report in a few days if it makes a difference.
Wifi disconnects
PMikeP said:
I have a similar problem with WiFi on my HD+ running CM 10.2.1, but not exactly the same. In my case, we have two wi-fi access points (i.e., two routers) in the house on different channels. I stay connected 100% on whichever I first connect with. .
Click to expand...
Click to collapse
Hmm, that is interesting. I have a single router but running two instances, a 2.4Ghz and 5Ghz band. Both have the same SSID and pass phrase. I just wanted to make it easier for systems that supported both bands to jump back and forth.
I think I will change the SSID of the 5Ghz band and make them truly separate networks.
Thanks for the feedback.
So i have ViperOne 4.1.0 running with Elemental X 10.8 kernel for over a week now. Everything was working fine up until yesterday when suddenly my phone cannot get an external IP address on my Wifi at home anymore. It connects fine to the Wifi itself however it cannot get any internet connection.
I have reset my router, modem, phone and nothing has worked. Other devices in my home which connect to the same wifi get internet connection just fine only my HTC One does not. Mobile data connection works fine btw.
Whats really puzzling to me is that really i have changed nothing on my phone in the last couple of days and not all of a sudden its simply not working so i'm grasping at straws here...
Anybody experiences similar issues or have any ideas what else i could still try to fix this?
Thanks
Well it turns out that changing the Wifi channel on the router from auto (was actually 9) to 11 in my case solved the problem. Weird ****...
Sent from my HTC One using xda app-developers app