yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] ADude:
I have the reverse experience of the OP.

I never had any problems with Wifi ever, until the .32 test builds, when Wifi would stop without notice, requiring a disconnect/connect. This caused me to go back to a .29 stable.

Perhaps what the OP is suggesting is that the change, that was reversed, should be a toggle/option, rather than changed and then changed back.
[Nook Color Android Development] rhester72:
...or generate sufficient interest into the real root cause to produce a solution that solves both problems at once, which was the true intent of starting the thread in the first place, and why it doesn't belong in General ;)

Rodney
[Nook Color Android Development] chemical1der:
I think this is a development issue too but maybe it doesn't need a dedicated thread. If, as ADude suggests, there's a need for a toggle/option, couldn't this be taken up in dal's kernel thread? Or maybe the CM7 thread? Unless, of course, the OP is interested in writing code for such a toggle...? Perhaps the title of the thread needs to be changed to something clearer? Regardless, I just don't want this important discussion to get lost because it's been misplaced or misnamed.
[Nook Color Android Development] rhester72:
I'm unconvinced it's a kernel issue. I think there may be multiple issues in the mix, one being kernel and one in userspace, and having the discussion consolidated into a single thread is nothing but goodness...at least until the (at least two separate) wifi issues are conclusively identified.

Rodney
[Nook Color Android Development] chemical1der:
True that. Perhaps you could rename this thread then and make the developmental concerns clearer in the first post? Or not. Otherwise you might have folks filling the tread with "My wifi works..." or "My wifi doesn't work..." complaints/gloats that don't really help to figure out the specific problem you and other are discussing.

Just trying to help.

-chemical1der
[Nook Color Android Development] miniaturepeddler:
This has been my experience also.
[Nook Color Android Development] rhester72:
Noted and agreed. Honestly, I didn't expect it to get this much attention. I'd really only hoped to gather a concrete list of conditions (ALWAYS behaves like _this_ under _these_ repeatable circumstances) to actually edge toward a solution...but it looks like there are many, many permutations of this that may be difficult to categorize (or differentiate from run-of-the-mill "my router is borked and I don't know it" reports).

Rodney
[Nook Color Android Development] marlonbr:
I confirm the behavior, but not that frequent. Its something that happens in like 30min or so. It keeps trying to load something until timeout, but keeps "connected", so I have to disconnect and connect again.

I'm using the first .32 cm7 build with OC kernel.

Any suggestions? Now that there is an IMEI generator I can go back trying other installs/kernels combos.

-

Marlon Moura
[Nook Color Android Development] Expatriotex:
Wifi always worked perfectly for me though most of the nightlies (i tried almost all of them) and stable releases, up to and including the 3.1 beta and OC. AFter nightly 83 or 85, whenever .32 was merged, wifi connects for about 30 seconds, disconnects for about 15, connects for about 30, disconnects for 15, over and over and over. Green icon, grey icon, green icon, grey icon.....

My router is a belkin, doesnt matter if its wpa2, wpa or wep, all my other android and wifi devices work fine on it, except the nook after nightly 83. Pandigital, cruz, evo, epic4g, blackberry, 4 desktops, 3 laptops, ipad, ect. Changing between aes or tkip has no effect, the nook still cycles connections/no wifi, but every other device works perfectly.

If the problem was the router or settings, i would have problems with other devices. The only device with a problem is the nook running any .32 nightly.

If i flash back to the 3.1 beta, wifi works perfectly again.
[Nook Color Android Development] chisleu:
I only had issues with wifi when going from beta 3.1 to n86, but I had a HORDE of other issues as well.

I recommend to anyone who is having trouble to format system/data/cache(s) and install freshly downloaded nightly+kernel.

If you are having problems, it is important to post what types of connections you have problems with.

I am on WPA2/AES b/g/n right now.

EDIT: (I has nismo gear! I just watched Urotsukidoji recently and one of the cars the main man-beast lands on has a big nismo sticker on the back. haha)
[Nook Color Android Development] yourm0m1:
im pretty sure this is an AES issue but not being a dev and knowing what might have changed in .32 the only solution is to turn off AES or deal in my case since i dont have access to the router. as a note on all .29 kernels i never had wifi issues.

always cm7 and dal OC kernels btw. which in the long run it is all release canidates or test kernels so we cant expect 100% stability.
[Nook Color Android Development] Andy53:
I am using Edimax with 64 bit WEP encription.

When starting with CM, installed 7.0.3 stable - worked perfectly with WiFi, then updated to 7.1.0-RC0-encore-2.6.32-beta3.1 with 13/5 OC - after some problems connecting first time it worked flawlesly. Yesterday I updated to Nightly 87 with 23/5 OC 1100MHz conservative (by the way the upgraded worked perfectly, I am working from the SD with verygreens Size-agnostic SD Card image, now at rev 1.3) and I noticed disconnections from the WiFi, but after 10-20 secs it connected back by itself. Perhaps this info can help somebody.

To all the Devs - awsome work - thanks.
[Nook Color Android Development] nadafinger:
My experiences:

CM7 7.0.3 stable, infinite scanning, connecting, disconnected loops when unlocking the screen. Eventually it stopped "scanning" and without a forum search turning up any solid solutions I downgraded to CM7 7.0.2 to see if it was more stable. Eventually ran into the same issue. Switched to Phiremod 6.2 without realizing it wasn't different, same issue. Finally found a thread on another site the suggested forgetting all of your saved APs to get back to "scanning", which worked. The perma-fix to me was to stop wifi from sleeping, so that it just stays connected, which means only once or twice per day, as I connect at work vs. home or back again, I have to watch it loop maybe 4-5 times then finally connect. Sometimes I will sit at work all day and it will never connect, sometimes it will eventually connect after I toggle wifi on/off. Definitely not a WPA issue, as the connection at work is open, and that's where I have the most trouble. At home with WPA it will usually connect on the 2nd try if it fails the first time.

Anecdotally, I believe the issue to be with the way certain APs and the wifi driver are trying to handshake with each other. I say this as I use the NC at about 6 different places, and at 4 of 6 have no issues at all. 1, only small issues, and at work it's nearly unusable (where I have no access to change settings).
[Nook Color Android Development] kLAcK107:
n87 complete reflash and wipe

Planex MZK-W04N: Can't get a solid connection no matter what

Have tried: TKIP, AES, WEP, NO SECURITY, G ONLY, FACTORY REST

flashed to update-cm-7.1.0-RC0-encore-2.6.32-beta3.1 and wifi working good

wifi also working good on phiremod 6.2
[Nook Color Android Development] paleh0rse:
That started happening to me with n86, and again on n87. Rebooting my router and "forgetting" the connection would fix it... but only as long as I kept the nook awake. Whenever it failed, it was usually right after waking it from deep sleep. The real dilemma was that it wasn't a consistent problem -- sometimes it would happen, sometimes it wouldn't.

I'm hoping n91 fixes the problem... somehow... so far, so good. /shrug
[Nook Color Android Development] smully1:
N91 has not fixed it for me. Still losing connection.
[Nook Color Android Development] bcampano:
My issues were hardware related not CM7 related

I posted my experience and findings in Nook General...

http://xdaforums.com/showthread.php?t=1110199

Might be worth some of you checking out. I haven't had any issues since and am running a Cisco E3000 with AES.

Hope this helps...

Brian
[Nook Color Android Development] Natronics:
had this issue with my thunderbolt and my droid OG along with my nook. I set the thunderbolt and the nook to have static IPs and it will connect automatically the first time and I don't see any drops. Have you guys tried setting up the devices as static?

just an option to try...
[Nook Color Android Development] paleh0rse:
Mine uses a static IP, but on n93 still refused to connect after being in deep sleep for any extended period of time. I had to reboot my router each time to get the NC to reconnect.

I'm on n94 now, so maybe that will help. We shall see...
[Nook Color Android Development] Synssins:
This is a Development issue, and needs it own thread.

It does NOT need to be part of some other thread and thus get buried.

I have had the exact issue described by the OP, in which the Wireless was unstable before n86. It would Connect, run great for about 60 seconds or so, and then it was as if my internet would fail. No data connection to the outside world, or even my internal LAN, even though the icon showed the connection as good.

A restart of WiFi would fix this for another 60 seconds or so.

Doing a complete wipe of the device would not resolve.

Going back to stock DID resolve the issue.

I am now on the latest nightly, and my issue has been resolved almost completely.

I am on the stock kernel.
[Nook Color Android Development] totot1976:
same issues

I have had my NC for about 4 days. I only used the stock OS for 5 minutes to register it - it worked fine with WIFI at the time but that doesn't really prove anything.

My first flash was nightly 87, then 91 and now I am on 94. With all of them I have experienced intermittent connection issues. Sometimes were worse than others.. one time I am on WIFI for half an hour and nothing is wrong, then I might try later and I get disconnections within 5 minutes.
[Nook Color Android Development] chisleu:
been using n91 w/ oc kernel without issue for days.

Today wifi just stopped functioning. I had to disable wifi and reenable to get data to flow properly.
[Nook Color Android Development] Metazoa:
I have a router TP-Link TL-R1043ND. Problems occur only in WPA/WPA2+AES. In this mode, WiFi freezes and I have to manually restart it.

In all other modes (WPA/WPA2+TKIP, WEP, ...) are no problems.

IMHO: this issue is related to an error in AES-encryption in the 2.6.32 kernel WiFi-driver.
[Nook Color Android Development] fulko:
None of these situations are similar to mine

I am using CM 7.0.2, not nightly builds

I haven't downloaded anything new in days.

Yesterday morning was the first time this has happened to me.

Now it seems that if I leave it on LONG enough (minutes to hours), eventually it decides that

its OK to actually use the wifi. Till then it says 'connecting', but all the AP's are 'not in range'

I also have 'wifi analyzer' installed, and it looks like the radio is turned off.

Now I will say, that I probably pressed the 'airplane mode' and/or 'bluetooth' enable buttons

at some point before this all started. But in my own defense I will also say that I have some

of the other apps, that supposedly 'really do disable airplane mode', and that didn't help.

I also used the sqlite3 approach and remove the 'airplane_mode_on' entry from the database.

Once it connects, its OK. I left it on during the drive to work, and when I arrived, it connected

to the work AP, but I rebooted (to test it), and I'm now back in the 'radio is disabled mode
[Nook Color Android Development] PIYIRIO:
I was running a late April CM7 nightly (I think 4-24) and updated to the latest last night. I noticed I couldn't connect to any wifi access point. I tried my U-Verse router, my linksys, and wifi tetheron my Incredible. I get a gray icon and "obtaining ip" then the icon dissapears and it starts over. The linksys is an open network and it still fails. What concerns me is I have done a full wipe and even rolled back to my CWM backup and its doing the same thing... I don't get it... I may try rolling back to the latest stable just to check but I've NEVER had wifi issues with the nook. :confused:
[Nook Color Android Development] shumash:
I had the same issue and fixed it by deleting one of the stored access points. When I added it back in, it rescanned and found everything again.
[Nook Color Android Development] fulko:
That was the same thing I tried earlier...

a) I deleted access points that I didn't use... that didn't help

b) I deleted the access point I was trying to connect to... that didn't help

So after the latest email in this thread, I said "screw it, I can't make it any worse",

so I deleted ALL access points.

It instantly started scanning, and reconnected, etc.

So deleting a single AP may not be sufficient!

Hope this helps someone... It helped me.
[Nook Color Android Development] PIYIRIO:
Thats what sucks about my situation. I did a complete wipe so I have no access point stored that I can delete and it wont freaking connect. I restore that last backup and try it again... :(
[Nook Color Android Development] paleh0rse:
Tried rebooting your router? I've found that's the only thing that works for mine when it refuses to connect...
[Nook Color Android Development] muness:
My experience

I never had this intermittent connect/disconnect until Sunday when I updated from #86 w/ 0523 OC Kernel to build #94. After the upgrade I tried to watch Cowboy Bebop episodes with the PlayOn Mobile app, and it kept disconnecting. From there I tried:

* #96 - intermittent connect/disconnect

* #97 - intermittent connect/disconnect

* #97 w/ the 0609 OC kernel - intermittent connect/disconnect

* Stock 1.2 w/ Factory Reset - good connectivity

* #97 w/ the 0609 OC kernel - intermittent connect/disconnect

* #86 w/ Factory Reset - intermittent connect/disconnect

* 7.0.3 stable - good connectivity

* #97 w/ Factory reset and the 0609 OC kernel - intermittent connect/disconnect

I am stumped. Would try more if someone could point me at which logs I should look into and for what.
[Nook Color Android Development] muness:
I got tired of just trying different ROMs randomly, so I started looking at logs. What I see is that the wifi connection itself is connecting just fine but the DHCP negotiations are failing on renewal. Here's an example from my logs (filtered by "wifi"):

The lease duration is an absurd 9 years. The N1 forum shows someone else having similar problems with long DHCP leases.

Switching to a static IP address fixes the disconnects here.

I don't know much about DHCP in practice, only having looked at the spec for a networking course I taught years ago. However, it's not clear to me:

* why the lease is so long. Is this a trick used by some routers to emulate reserving an IP address for a mac address?

* why the Nook Color asks to renew the DHCP lease so quickly. From the wikipedia article on DHCP: "Clients begin to attempt to renew their leases once half the lease interval has expired." Maybe because the lease is so large it overflows something and becomes 0?

* why the DHCP server is timing out on the renewal. Maybe it's related to Android issue #11236? Or because the server is fed up with all these requests and ignores them?

* what changed between older CM7 builds (running 2.6.29?) and (running 2.6.32?) that ends up causing this constant connect/disconnect?

Are there any devs in here who can shed insight into any of these questions?

I'm heading in to the office shortly and will see what how the routers/nc interact there.

Update: At the office I get sane lease times and the NookColor Wifi connection works fine.
[Nook Color Android Development] muness:
On a whim, I decided to look at what my HTC Vision was doing with these long lease times. Every second, I see a DHCP renewal request (but not the time outs we see on the NC.

No wonder the battery life has been awful on wifi when I am at the apartment on wifi.
[Nook Color Android Development] jzh797s:
I am using WPA2+TKIP and experiencing the dropout issue on Nightly 98.

Resetting the router... no change.

Setting nook to static IP... no change.
[Nook Color Android Development] muness:
@jzh797s can you install aLogcat and filter by Wifi? See if you can see anything that looks off? Something failing, or timing out.
[Nook Color Android Development] dalingrin:
muness thanks for the very helpful posts.

I will be looking into the dhcp lease issue this weekend.
[Nook Color Android Development] muness:
:) Glad I could help. I just switched laptops and don't have my CM build environment setup. Will try to get that up soon so I can start digging into the code again.

Thanks for all your awesome work on the NookColor!
[Nook Color Android Development] jzh797s:
I see:

D/dalvikvm( 8363): GC_EXTERNAL_ALLOC freed 1K, 50% free 3223K/6407K, external 1412K/1420K, paused 32ms

quickly followed by:

D/WifiStateTracker( 1048): DHCP renewal failed: Timed out waiting for DHCP Renew to finish

among many other things. After which, DHCP eventually renews.

I do have this set to a static IP.
[Nook Color Android Development] dalingrin:
Lease issue is fixed: http://review.cyanogenmod.com/#change,6098
[Nook Color Android Development] philburkhardt:
I am running n102 which has this included, and my wifi is just as bad. It has been especially bad in the last 24 hours.

Do you think trying an install with a data wipe would help?
[Nook Color Android Development] edboston:
I was having WiFi problems and changed the security settings on the connections and that fixed the problem. With this new changed, I increased the security settings and I am still not having the problem like I did before so it would seem that it has helped in my case.

Do a backup and try the data wipe. At least, if that doesn't help, you can always restore the backup and be right where you are now.
[Nook Color Android Development] philburkhardt:
I've been through the security settings a million times over. Changing the security settings has never helped. Wifi is the only persistent problem I have.

I'll try a clean install just for the heck of it, but even that has never helped in the past. The best is when I do a full wipe and install, and then wifi starts failing on the first boot :eek:.
[Nook Color Android Development] edboston:
Sounds like it could be bad hardware then.
[Nook Color Android Development] philburkhardt:
Haha, no it's not my hardware. My hardware has been problem free. So, everyone here having wifi issues has faulty hardware because changing the security settings didn't fix it?

Isn't this the wifi dis(re)connection/dropout thread? So should we all just give up and blame it on hardware?

EDIT: It looks like I lost my static IP settings somehow. I just re-entered them, and my wifi seems to be rock solid (at the moment). I actually just had the fastest download speeds I have ever had on my nook. I'm gonna keep my fingers crossed and hope it sticks.
[Nook Color Android Development] rhester72:
I don't want to pretend the problems _I_ was having with WiFi are necessary the same as others...but I can say that I've been happily listening to Pandora for more than an hour at work (where I couldn't stay connected longer than 5 minutes) without so much as a blip. Thank you!

Rodney
[Nook Color Android Development] edboston:
well, if the software is setup correctly, which in your case it sounds like it wasn't, then that would only leave a hardware issue to explain it. I never said or implied we should just give up and blame the hardware. Only saying if all the software fixes don't address the problem, it *could* be a hardware problem.
[Nook Color Android Development] philburkhardt:
I wouldn't exactly say it wasn't set up correctly, I am sure the majority of nook color users are not using a Static IP. But, I will admit that using a static IP seemed to help.

One thing I notice in alogcat is that when my wifi drops the log reads:

E/wpa_supplicant(1108): Ongoing Scan action...

D/NetworkLocator(3179):null cell state delivered

D/NetworkLocator(3179):null cell state delivered

D/NetworkLocator(3179):null cell state delivered

This seems to continue on, and then I don't have wifi until I turn it off and back on. I don't know that this has anything to do with it, just something I noticed.

This hasn't happened yet today, since I entered the static ip settings. But, I don't believe static ips have helped everyone.
[Nook Color Android Development] muness:
Indeed. No more needless lease renewal requests. Definitely fixes my NookColor wifi issues on the router that sends 9 year DHCP leases.
[Nook Color Android Development] Expatriotex:
posting to report that my wifi issues have been resolved with the release commit in nightly 102.

huge thank you to dalingrin
[Nook Color Android Development] christoophat:
As is mine, same nightly + 6/13 kernel. Having to refresh wifi any time I want to use Pandora or Netflix. Wifi icon stays green even when app report no connection.
[Nook Color Android Development] rhester72:
I'm afraid I may have spoken too soon on this one - or we had more than one issue.

It worked well for a few days, but now, even with the stock kernel and conservative governor (seems the safest choice for testing) on n103, if I run nothing but Pandora in the background and let it sit for 60 seconds until the screen turns itself off, Pandora cuts out at that exact instant. Turn the screen back on and the wifi icon shows green but no actual connectivity. Recycling wifi brings it back.

I've also re-encountered the nothing-shows-up-on-a-wifi-scan-unless-you-delete-every-remembered-entry problem.

Rodney
[Nook Color Android Development] paleh0rse:
Would Pandora normally override the wifi setting "turn off when screen is off"? Perhaps it requires you to set wifi to "always on"?
[Nook Color Android Development] rhester72:
Pandora keeps the screen awake on its own, but I've also set wifi to always on so I can test by keeping the CPU Spy screen up.

I'm getting a bit closer to understanding this, but there are so many variables...right now I'm working on an assumption that having more than one wifi connection defined causes trouble regardless of kernel, but there seems to be something specific to the 0616 test kernel even then (maybe related to governor)?

Lots of combinations to test through :/

Rodney