[Nook Color Android Development] bonobomidwest:
Hey guys, well I certainly don't know enough about writing kernels to help out the CM7 guys, but troubleshooting networks, i might be able to help a little bit with... no promises :)

If I were in you shoes i would first de-constipate the NC's wifi system (i.e. make sure that the system has forgotten all of it's wifi snetworks, and default settings, so you have a virgin wifi system, I've never had to to do more than tell it to forget networks - but i bet there's a deeper scrubbing technique out there :) ) The reason i say this is that if your problem is persisting across nightly flashes then it is most likely either your network, or the aspects of android that are not being over-written (i.e. data and cache)

I experienced the cycling problem you both descirbe on both eclair and froyo. In eclair the culprit was definately the ADHOC patch. In Froyo the culprit was still using settings profiles to manage wifi in sync with the screen - lesson learned start with the stock install and confirm everything works! ;-) In the case of Froyo i had to go back and have it forget every network it new, and as if by magic it was at 100% health. One possible scorched earth policy would be to use titanium backup to selectively backup everything (i.e. apps and settings) but the wifi system's data, reflash the ROM to a virgin state, including ensuring data and cache are clean, and then reinstalling from TB. This isn't as bad as it sounds- i transferred my almost my entire user system from froyo to CM7 this way very quickly.

Sooooo assuming we want to really rule out the network before taking such drastic measures.... Then I would step back to the simplest config that works. I.e. a vanilla open g network and then start adding in options until it breaks. If you are worried about security (i would be), you can set your router to only allow known MAC addresses at this point. The downside of this painstaking process of elimination is that it pisses off the wife and kids as the home network reboots every five minutes :)

It might be splitting hairs but i would not call auto wpa/wpa2 aes/tkip g/n a kosher setup.. at least not from a security point of view. Unless you have some very old legacy equipment. I would set it to simply WPA2 with AES. WPA and TKIP are not really secure. I could imagine that with the plethora of possibilities to choose from the NC can't settle on one... perhaps... though my router allows aes/tkip and that does not throw the NC off.

Anyhoooo... also my g/n router defaults to 2.4Ghz for g and 5.0 GHz for N in dual mode, and so the NC can't see the N network. So I actually have an older b/g router slaved to the N router, both running on different empty 2.4Ghz channels, with different SSIDs (i.e. myawesomenetwork_G and myawesomenetwork_N). Which is somewhat besides the point, but I'd be surprised if your router isn't doing the same. Try setting it to G only, and then adding N into the mix.

Personally I really underestimated the issue of crowded airspace - in my not particularly crowded neighbourhood there are probably 5 or 6 networks on each of channels 1, 6 and 11. Certainly at work i get frequent dropouts as i move between overlapping routers - and that often looks like the cycling you describe. At home I drop my networks in channels 3 and 9 (which do have some overlap with the ideally separated 1 6 and 11, but it's better than being smack on top fo the chatter). My signal strength is better, and the range i can move before i lose my networks is greater than when i ahd them on my routers' defaults (ch 1 and 6).

anyway, that's a lot of ideas to try. if you do one at a time and have a eureka moment than please post back, because loads of people are asking about this!

Anybody else have any other ideas?