Cross-posting this from the CM7 nightly thread since it also helped someone else. If this hasn't been posted before, I hope it is helpful.
Just wanted to drop in with something I noticed regarding the wifi looping bug. I upgraded from 30 to 31 and started getting the issue out of nowhere. The wifi would just constantly loop between connecting/seeking/disconnected. Tried a bunch of things with no results, decided to go for a full wipe, installed Phiremod 5.1 from the XDA forums with the new Dalingrin's kernel (1.1 OC version released 25th March), but when I rebooted the issue was still there.
I honestly don't know much about networking, but I also noticed that I was having to hard reboot the router sometimes because the wifi would appear connected but not actually do anything. After a bit of messing around, it seems that both issues were resolved by simply disabling UPnP on my router. I have no idea if the problem was caused by it being a crap router (it is), or the way the Nook is connecting to it, but I thought it might help out some other people having the issue.
The router for the sake of reference is an old Netgear WGR614v7 cable router.
Sorry if this has been posted before. I just wanted to add that apart from this small issue, the nightlies have been pretty fantastic. The Nook is a week old and my first venture into Android. The CM7 and XDA communities are pretty excellent. Thank you everyone for all your work.
Click to expand...
Click to collapse
Hello,
So Using CM7 latest nightly along with Dalingrin's latest 2.6.32 OC kernel i cannot seem to get WiFi to work whatsoever (using all 14 channels). WiFi just says "Disconnected" and will not connect to any network. I have tried flashing multiple different CM7 Nightlys, wiping the cache partition and dalvik cache (although whenever i wipe dalvik cache in CWM it freezes...), all to no avail. Every time my WiFi still does not work.
Any help would be greatly appreciated
Thanks,
Moriarty
The system that I am using right now is built with the following pieces:
-- generic-sdcard-v1.3.img
-- gapps-gb-20110307-signed
-- update-cm-cm_encore_full-98
-- update-CM7-dalingrin-OC-sd-060911
This system has been up for about two days and seems to be ok with no wifi problems.
Good luck.
bike2002 said:
The system that I am using right now is built with the following pieces:
-- generic-sdcard-v1.3.img
-- gapps-gb-20110307-signed
-- update-cm-cm_encore_full-98
-- update-CM7-dalingrin-OC-sd-060911
This system has been up for about two days and seems to be ok with no wifi problems.
Good luck.
Click to expand...
Click to collapse
Thats what i am using now but it still does not work... I am not sure what the reason is, OC kernel will also not go above 925Mhz....
I'm having an odd issue with wifi too... though not as bad. I can connect fine, but every reboot turns the wifi off. I have to turn back on and all is fine again.
byproxy said:
I'm having an odd issue with wifi too... though not as bad. I can connect fine, but every reboot turns the wifi off. I have to turn back on and all is fine again.
Click to expand...
Click to collapse
Mine has always been like that... I wish i had that small of an issue
I wonder if this is just a worse version of the Wifi issues that sometime plague NCs? I thought that the nooks have trouble connecting to different forms of encryption and whatnot.
B_Moriarty said:
Thats what i am using now but it still does not work... I am not sure what the reason is, OC kernel will also not go above 925Mhz....
Click to expand...
Click to collapse
Are you sure you installed the OC kernel correctly? That is the top OC for the stock nightly kernel.
Not having wifi issues with n100 or the latest OC kernel; I did in a much earlier nightly only for my home router but it turned out to be one of these router-related issues: a) it was on a very crowded channel, which I changed b) was running TKIP/AES which I changed to TKIP only (seems to have worked for others here so I tried it as well).
Have not had a single drop since, and I've used it at Starbucks, several university wifi hotspots (different buildings), and at home.
angomy said:
Are you sure you installed the OC kernel correctly? That is the top OC for the stock nightly kernel.
Not having wifi issues with n100 or the latest OC kernel; I did in a much earlier nightly only for my home router but it turned out to be one of these router-related issues: a) it was on a very crowded channel, which I changed b) was running TKIP/AES which I changed to TKIP only (seems to have worked for others here so I tried it as well).
Have not had a single drop since, and I've used it at Starbucks, several university wifi hotspots (different buildings), and at home.
Click to expand...
Click to collapse
Well, in About it says my kernel is 2.6.32 which i would think meant that i installed it correctly... Although not sure if my Dalvik Cache was wiping correctly, seeing as it would freeze immediately after wiping
B_Moriarty said:
Well, in About it says my kernel is 2.6.32 which i would think meant that i installed it correctly... Although not sure if my Dalvik Cache was wiping correctly, seeing as it would freeze immediately after wiping
Click to expand...
Click to collapse
All the nightlies past 77(? I think) run on the 2.6.32 kernel. My kernel version running on latest Dalingrin OC kernel is 2.6.32.9 [email protected] #63. I'm not sure if this changes with updating to OC kernel at all, I usually just know OC kernel is flashed correctly when the higher clock rates are available in CM7 performance settings.
Dalvik cache wiping on CWR 3.0.2.8 freezes after the wipe. The latest version, 3.2.0.1, fixes that issue.
Using CM7 on SD card
I recently decided to try out a nightly and picked 98. Did not add overclock kernel just used it as it came.
Been using CM 7.0.3 with overclock to 1100 and have had no problems with wifi, browsing speed or Force closes. Only problem is battery life is not great.
Nightly 98 seems to be great for battery life, but wifi has an intermittent problem. When I wake it up in the morning from charging I find I cannot get a wifi connection unless I reboot it.
Wonder if others have same problem.
I have gone back to CM 703 as the battery life is not as inconvenient as I charge it every night anyway.
Do you guys have the wifi manager app installed?
Like I said my system have been up for more than two days and wifi seems ok:
-- the wifi is off when it goes to sleep and comes back up when I wake it up.
-- I watch movies on Netflix and it is up for as long as I watched the movie
-- there may be some small problems but I have not seen them yet
i had this too. There is a bug with airplane mode : if you use it, then uncheck the airplane mode it stay marked as checked in internal cm7 settings, you can uncheck it with this app : https://market.android.com/details?id=com.advancedprocessmanager&feature=search_result
YES
Ok, THANK YOU This led me to searching for the answer and eventually finding it.
The SQL didn't really work for me but this did (and it is much less tedious)
1. activate wifi
2. go to wifi scanning
3. Forget one secured SSID
4. add a secured SSID: (Manually type in your WiFi Name + Password)
Hope this helps anyone who accidentally enables Airplane Mode and ends up with this bug....
GTT1 said:
Using CM7 on SD card
Nightly 98 seems to be great for battery life, but wifi has an intermittent problem. When I wake it up in the morning from charging I find I cannot get a wifi connection unless I reboot it.
Wonder if others have same problem.
Click to expand...
Click to collapse
Got Nightly 98 + OC 0613, and I always get wifi connection issues after deep sleep, if I left Wifi on beforehand. Have to reboot too then. But it's been an issue for me for a while, with previous nightly and OC too.
Maciej
Matchay said:
Got Nightly 98 + OC 0613, and I always get wifi connection issues after deep sleep, if I left Wifi on beforehand. Have to reboot too then. But it's been an issue for me for a while, with previous nightly and OC too.
Maciej
Click to expand...
Click to collapse
Thanks so its not just my NC as I you have my problem. Will try a later nightly and see if it still happens. Meanwhile I am happy with CM703 OC to 1100
I am sure it will get sorted out eventually.
GTT1 said:
[...]
I am sure it will get sorted out eventually.
Click to expand...
Click to collapse
Good news! (at least for me ) I installed the newest OC kernel and my problem's gone. Maybe you should check it out too.
Maciej
I flashed my device the other week with the nightly build of cm-10.2-2013-12-02 and it is fantastic. Not only does it get twice the battery life the thing is so much more responsive and fluid, however (yes there is a however), the WiFi does not always cooperate. It will show it is connected but the browser or anything that uses a connection will not receive anything. If I disable the WiFi then the phone uses its data with no issues at all. Of course there are limits to data use so the WiFi is much needed. Does anyone have a .zip of the 03,04,05,06 cm10.2 builds? Unfortunately now that cm11 is being rolled out the nightly releases of 10.2 are nowhere to be found. I was hoping hat maybe one of these later releases fixed the issue.
I've been lurking for a while and attempting to solve this problem on my own but I've run up against a brick wall and I need some help.
A bit ago, I was running an older stable CM10 build with no real issues. Then, suddenly, one day, the wi-fi stopped connecting. It sees everything broadcast and saves the network, but any time I tried to connect it would, essentially, time out. It would try for a few seconds, then go back to saying "saved". I tried a few different things to test the connection, rebooting the tablet, rebooting the router, removing all security from the router, installing a new router, and trying a public wi-fi. The results were all the same: the tablet can see all the broadcasts but not connect to any.
So, I wiped CM10 totally from the device and installed CM10.1. When I tried setting it up, the exact same thing happened. It can detect all the wi-fi broadcasts but cannot connect to any of them (and as a side note, any time it tried to connect, the wi-fi bars would drop out from full to one bar).
All in all I tried installs of CM9 (that I had used successfully before), CM10, CM10.1, CM10.2 and Evervolv 4.3.1, each from wiped touchpads. EVERY one of them had the exact same problem. The wi-fi when in WebOS works great, so I'm not thinking it's a hardware failure. There's just something odd going on with android installs and my touchpad and I need help.
If anybody has any ideas, I'm all ears. Thanks!
Hello,
I cant find a answer to my problem. I have been searching and trying to fix it for days. So I got 2 HP TouchPads as a gift. I was able to install CM11 with toolbox on one HP. No issues at all with that one. Then I installed CM11 with toolbox on second one. The only issue I have is the WiFi will not turn on. When the ROM starts I hit English and then it will go to the WiFi screen. At that screen it will say "WiFi turning on". It will stay like that forever and never change. When I decide to skip the setup and turn the WiFi on with the toggle switch it does nothing. The switch will not move. I have tried CM11, Pacman kikat 4.4.4 and Evervolv 5.0.0. WiFi will not turn on will any ROM. When I go back to Webos with toolbox WiFi will work every time. Does any one know how to fix this?
ok so since no one knows that answer. Is it possible to take a backup from the good touchpad and restore it on the bad touchpad. Does anyone think that will work? If it is possible how would I go about doing that. I'm using toolbox and cwm recovery.
Just to eliminate CM configuration as an issue, have you tried using the WIFI in WebOS? I've had problems with my corp WIFI on my Touchpad on and off for a long time. Trying a different OS might eliminate or suggest a hardware related probem.
TrobbL said:
Just to eliminate CM configuration as an issue, have you tried using the WIFI in WebOS? I've had problems with my corp WIFI on my Touchpad on and off for a long time. Trying a different OS might eliminate or suggest a hardware related probem.
Click to expand...
Click to collapse
wifi will work just fine in webos.