[Samsung Galaxy Nexus] lizaSB:
So I've been working in a cafe for ~two months now and I've noticed a similar set of issues with my wifi when attempting to connect to the unsecured wireless network that we offer to our customers. However, after a great deal of troubleshooting, I do not believe it to be related to Franco's kernel. When I first started work in the cafe it was early August (in the days of JRO03C & L) and my wifi worked when I was at work. Sometime near the end of the month (maybe August 25th or so), I came into work one day and I noticed that my wifi would no longer connect. I thought it was no big deal and that I could revert the changes I had made in the previous night (i.e. kernel and rom rollback) to restore connectivity at work. No go.

I believe I was on JellyBro nightlies at the time, so I thought it may have been a problem with CM10. I tried flashing stock AOSP, AOKP, CNA and RBJ. Nothing worked. Perhaps franco's own wifi driver changes borked something? I've tried flashing r223, r241, M5, and I've been on top of each new nightly kernel since M5 (I think the ONLY set of Franco kernels I haven't tried in conjuction with this problem were the r26x_test builds when Franco was trying to fix WEP on the experimental wifi driver). I've also tested the problem on Trinity (Stable 35, A60-63) and on the stock kernel. Nope, that's not the problem either. Perhaps it was the bootloader or changes to radio? UGLC, UGLH and XXLF all have the problem, same with the KK15 and LC03 bootloaders

Because I'm not really in a position to make build changes at work, I only have the opportunity to test 1-2 tweaks per day and the process of troubleshooting has been incredibly frustrating. I've essentially given up and relinquished this as a bug in AOSP and hope that it willl be fixed in future revisions of Jelly Bean. I've found this issue on google code (http://code.google.com/p/android/issues/detail?id=34786) and it seems to be similar to my issue and devs have reported that this will be fixed in a future version of JB; however, I do not have admin access to the router and do not know what link speed things are operating at. However, I DO know that we use a Linksys Cisco WRT120N, so wireless N may very likely be the culprit. We also do NOT have a browser authentication page; however, it's a moot point because I never make it past obtaining an IP address anyway (have even tried static IP).

I've pretty much given up troubleshooting at this point because I've driven myself crazy over the past month and the issue remains. Hopefully the previously mentioned commit will be merged to AOSP soon and I can test if wireless N is indeed the problem. In the meantime, hooray for unlimited data.

A logcat of my connection attempt, for those who care:

I/wpa_supplicant( 1829): wlan0: Trying to associate with 00:25:9c:d8:8c:c4 (SSID='linksys' freq=2437 MHz)
I/wpa_supplicant( 1829): wlan0: Associated with 00:00:00:00:00:00
I/wpa_supplicant( 1829): wlan0: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed (reauth) [id=1 id_str=]
D/CommandListener( 123): Setting iface cfg
D/CommandListener( 123): Trying to bring up wlan0
I/wpa_supplicant( 1829): wlan0: CTRL-EVENT-DISCONNECTED bssid=00:25:9c:d8:8c:c4 reason=0
D/CommandListener( 123): Clearing all IP addresses on wlan0
D/NetUtils( 313): android_net_utils_resetConnections in env=0x2a097a10 clazz=0x5b000001 iface=wlan0 mask=0x3
D/ConnectivityService( 313): ConnectivityChange for WIFI: DISCONNECTED/DISCONNECTED

Rasbeanjelly 9/26 - Franco.Kernel r277