Database Develop

Dummies' Guide to Diagnosing Intermittent Wifi on NC - fixed in BN1.3

This is a compilation of threads found on this forum as well as the BN forum. I thought having it in one place will help.
Edit: problem may be BN NC. See last paragraph
The NC is the first device that I have encountered that had intermittent wifi problems. At home, I have a mixture of Macbooks, iPod, a Viewsonic G Tablet running Android 2.2, desktops running Windows 7 and XP using various brands of USB wireless adapters and have NOT had any problems using 802.11n with WPA2/AES encryption.
From other threads: "As always, everything in this guide is completely at your own risk, I am not responsible for you messing up your device further nor am I responsible in the event that your Nook Color explodes and kills your cat, grandma, etc."
Intermittent Wifi Connection:
This is the issue where your Nook connects to Wifi and then after a few minutes the connection goes away. Typically the NC shows wifi as connected or perhaps connected and testing.
There are five variables that can cause intermittent wifi connections:
-your router
-wifi type 802.11b/g/n
-encrytpion
-wifi frequency 2.4ghz/5ghz
-NC ROM
-NC operating system
In many cases, this is due to 802.11n wifi. A digression: Wifi comes in manner flavors; 802.11b, the first standard; 802.11g, the second; 802.11n the latest standard. These flavors have to do with the physical wireless router.
In addition to the hardware, there are variations in encryption of the wifi signal: WEP, WPA, WPA2 with AES or TKIP. WPA2 with AES is the most secure. Look it up on Wiki for more details. And of course the
OS the NC is running.
In many cases, the NC will NOT connect reliably with 802.11n. I have a Dlink DIR-615 V2 wireless router and when set to 802.11n with WPA2 with AES, the NC connects but after a few minutes goes into a state of "testing connection". Setting the router to 802.11g only fixes the problem. An easy test is to go into Youtube and watch a long video. Most likely, half way through, you will loose the connection.
At work, we have a high end multi-access point Meru networking running unencrypted wifi 802.11n and I have this problem. So this may indicate a driver problem with the NC.
The Fix:
Go into your router's wireless. Select manual setup and find 802.11 mode or something to that effect. On my router, I have a choice of "mixed 802.11n, g, b", "802.11n only", "802.11g" only. Selecting 802.11g only with WPA2/AES fixes it for me.
Interestingly the NETGEAR WNR3500L-100NAS 802.11b/g/n seem to operate reliablely with the NC using 802.11n.
One post indicates that settting encryption to TKIP also fixes the problem.
http://forum.xda-developers.com/show...72&postcount=6
However, using TKIP opens up a hole for hackers
http://en.wikipedia.org/wiki/Tempora...grity_Protocol
One solution on the nookboards and BN forum also suggested turning off 802.11n
http://www.nookboards.com/forum/index.php?topic=5669.0
http://bookclubs.barnesandnoble.com...-Problem-quot/m-p/770856/highlight/true#M3295
If you are having problems, the following information will help in diagnosing the problem:
Router brand and model number: eg: Dlink DIR-615
802.11 mode: b, g, n?
SSID visible?
Encryption: no or if yes: WEP, WPA, WPA2 TKIP/AES\
NC Rom: 1.0.1 or 1.1
NC OS:
I will try to update this guide periodically. Moderators: feel free to delete this thread if it is redundant.
Edit:
BN has acknowledged there is a problem with certain routers. From my own experience, there are many more routers that are incompatible with the NC. My assessment is that it's a driver in the BN. I have a Gtablet running 2.2 with no problems.
http://bookclubs.barnesandnoble.com...ssed/m-p/1030918/message-uid/1030918#U1030918
From BN Administrator: "In general, wifi issues can continue to be fixed by following the troubleshooting guides posted in the FAQ and in other posts. We *are* continuing to investigate reported wifi issues with certain routers that have had issues reported. At this point, we’ve investigated the Belkin F5D8231-4 and found an issue introduced with Android 2.2. We have a fix that will be included in the next release, but do not have a workaround for users. We are also investigating other routers (including the DLink DL- 624 and Westell 327W), but do not currently have a fix for them.
Please continue to post here if you encounter further problems and NOOK_Engineer and I will work together to investigate further."
EDIT 9/7/2011: After I updated to BN1.3 and then rooted with, wifi connects perfectly with 802.11n both at home and work. Work wifi consists of multi-point 802.11n. Note that this is with Dalingren's froyo 9/1/11 kernel with the BN 1.3 source drop.

Thanks for this! Do you have any ideas about intermittent wifi ONLY when on an Adhoc network from my Droid? I had no wifi issues under Rooted 1.1 but when i went to internal Froyo 0.6.6 it is almost unusable. I have upgraded to 0.6.8 and it is still not working correctly, it keeps loosing the IP or pausing the connection.

Done some digging on this, and the issue is that my NC can see either the G or the N channel from my router, but not both (even with different SSID) when G is at 2.4 and N is at 5Ghz. It will only see N on 2.4 Ghz. bah.

I like the idea of putting it all together as it took me awhile to figure it out.
FYI, my wireless modem is:
D-Link DIR-655
On WPA/WPA2 TKIP
Interestingly, I made a setting change to set the wireless mode to only n & g modes. This stopped my nook from getting any wireless till I changed back to n,g & b. Not exactly sure what this means other than it could a router specific issue but good to keep the info in one place considering it is hard to track.

necroscopev said:
Thanks for this! Do you have any ideas about intermittent wifi ONLY when on an Adhoc network from my Droid? I had no wifi issues under Rooted 1.1 but when i went to internal Froyo 0.6.6 it is almost unusable. I have upgraded to 0.6.8 and it is still not working correctly, it keeps loosing the IP or pausing the connection.
Click to expand...
Click to collapse
Not sure of this but if it works with Rooted 1.1 but not Froyo 0.6.6, most likely a Froyo issue.

bonobomidwest said:
Done some digging on this, and the issue is that my NC can see either the G or the N channel from my router, but not both (even with different SSID) when G is at 2.4 and N is at 5Ghz. It will only see N on 2.4 Ghz. bah.
Click to expand...
Click to collapse
The wifi chip in the NC WL1271 supports only 2.4ghz. Interestingly the kernel reports the chip as WL1273 which does support 5ghz.

I don't think the original post regarding 802.11n being an issue is correct. We have two access points running 802.11n and have no issues with the Nook Color. I have them set up to operate 802.11n at 2.5 and 5 Ghz. I connect the NC to the 2.4 GHZ radio and use the 5 GHz for my laptops. I am using a Netgear WNDR 3700s.

@jerrykur - Well that explains that. I'm trying to sprint up the learning curve as fast as i can with this wonderful device... sometimes i miss things ;-)
@Zhousibo - I suggest you grab "wifi analyzer" from the market. It's an invaluable tool for tweaking your network. For instance, it lets you see which bands are cluttered and clashing. In my neighborhood everybody (i.e. about 20+ networks) is on the default channels 1 or 6. I can literally watch as one network pops up above the noise and drops out again. In exactly the same spot in the house we have a several dB stronger signal if we move the network to a clear channel. Also bear in mind that the encryption and frequency are two totally different issues. I would vary one at a time and look at what wifi analyzer is telling you - my guess is that only adjusting frequency will affect signal strength and signal drop outs. I would also start with the simplest working setup and add or remove optiosn one at a time, watching what happens to the signal. Once you have that problem fixed, then worry about authentication issues (i seriously doubt this is the problem, i've tried all combinations of authentication on my router and they all work - just go for the most secure!)

BTW1: in wifi analyzer you can view signals as a graph in time which will let you see signal drop outs (i.e. let's you watch what is coming into the machine), combined with fpga_guy's suggested method (watching you tube - so following what is coming out of the other end of the software, so to speak), will let you nail down where the glitch is - in the network or in the machine. Similarly you could ahve two devices whatching the same or different youtube sources, if they both fail at teh same time it is a network or even further down the pipe (e.g. ISP) issue.
BTW2: if you are using VOIP, then QoS in your VOIP box could be responsible for a lot of this depending on how your wired network is structured.
BTW3: I should have explained my motivation behind these posts - I just have not had any problems with dropped connection on the NC (other than all the problems with waking in rooted ecalir) on either G or N networks. I can pretty much move around town from rememebred netweork to remembered network and almost always be connected. I'm actually extremely impressed with how well networking DOES work on this machine, especially in Frroyo. BUT my home network is pretty complex and very busy (media center PC, streaming to at least one device most of the time, multiple PC's wireless printer, wired NAS, etc) so has had a lot of fine tuning... So I'm doubly impressed at the lack of drop-outs given this deployment... hence my advice to eliminate network issues first.

Here is an update on my testing of the NC with various routers. My ipod touch, HP DV1000 laptop running Windows XP connects to every router listed without problems. This indicates either a chip or more likely an implementation problem with BN's driver to the TI wifi chip.
NC (ROM 1.1 with Auto-nooter 3.0.0) works with:
Netgear WNR3500L running 802.11n with DD-WRT WPA2/PSK
DLINk DIR615 runnign 802.11g with WPA2/PSK
Work wireless running 802.11g (router unknown)
NC does NOT work with
Sites with hidden SSID
DLINK DIR615 running 802.11n
Sites using WEP with 128bit encryption
NC connects on boot with sites using WEP 64b encryption - FC after resuming from sleep.

@bonobomidwest
My only thinking is that the NC wifi driver is not as robust with the settings (maybe it is settings, firmware, hardware, not sure).
Interestingly, I spent a bit of time away from my home network which is where I have had no problems since I made the original change (FYI, I recently upgraded from Autonooter 1.1, to Nook Froyo 0.6.7 to NF 0.6.8 and have been stable since the change). I stayed at my folks for a week as am living overseas and they have a Belkin router (can't remember model but I gave them this and was pretty good for it's time). I had issues where the wifi had problems connecting after the screen had timed out so did not use the NC as much as I wanted. I also had problems with the wifi on Galaxy S on this network even though I changed the settings.
I haven't done a scan where I am living now but it should be more than where my folks are due to living in an apartment as opposed to my folks house.
I'm at the stage where my network is not 'broke' so not actively looking to fix it but all my devices NC, Galaxy S, PS3, PSP, etc, are all working now - only the NC has had the most problems with connecting to wifi but have been resolved.

I'm having trouble connecting to an 802.11B (yes B) 11Mbps unencrypted router on the bus I commute to work with. Not sure of the brand or model. Wireless status says I'm connected, but testing. I try to browse the web with Dolphin HD, but I never connect. My iPhone connects to the bus' same router without problem.
However it connects just fine to a Linksys WRT610N v2 (flashed with TomatoUSB) running 2.4Ghz N, 40Mhz bandwidth, WPA2/AES
Running Autonooter 1.1, but given what Zhousibo said in the previous post, I'll try out NF 0.6.8.

Any new ROMs help fix WPA2 connectivity problems?
Just bought my NC and flashed a great Froyo ROM on it.
(The first one I bought had obvious hardware issues, 1bar of wifi signal in the same room as my router. Brought it back same day and had it replaced, immediately better. A known reported issue with some faulty NCs).
Had the same issues with wifi connectivity as described here and everywhere on the net. Essentially, it will connect onto the router with N speeds, but is completely unable to access any internet.
I have a great router (it can broadcast 3 separate SSIDs) but I think it doesn't play nice with the nook. So, it was great up until now =P
Router brand and model number: Buffalo WZR-HP-G300NH
802.11 mode: n
SSID visible? yes
Encryption:
SSID1: (WPA+WPA2 mixed TKIP/AES) OR (WPA+TKIP)
SSID2: WPA2+AES
SSID3: WEP (yuck)
The Nook only fully connects to the WPA+TKIP mode (on SSID1) or WEP. The supposed mixed mode setting probably isn't quite as mixed as advertised. The Nook works fine on WEP, but I hate the fact the security is so poor with WEP.
I'd have no problem dropping the SSID1 settings to WPA security, except for the loss of n speeds. Part of the 802.11n specs (has to be WPA2/AES, or NO encryption--not an option). My DVR/home network is on that ssid, so I don't want to lose my n speeds.
So my question is do any other ROMs here help fix the WPA2 connectivity? I know lots of people swear their NC works fine with their WPA2 router, but I suspect their router is just more capable and is switching to WPA-TKIP discreetly.
This is not the same reported problem as having wifi cut off in sleep mode.
EDIT:
Oh, I just realized as a work-around I could put my home network on SSID2, and just the Nook on SSID1.

Get the right router...
Of course I can't speak for others, but my experience with this problem was that this problem was entirely router related. The rooted NC was very slow (to the point of almost unusable on the internet) from my home Netgear WNR834B Wireless N router, regardless of the speed settings, the channel or the security settings. I was able to experience much faster speeds (allowing UTube and Pandora to function properly) at a friend's home (generic Verizon DSL router) and at 2 public wifi locations. As a result I tried another Netgear WPN824 Wireless G Router with the same results as the other Netgear device.
Then I borrowed a couple of Linksys routers from a friend and tried them. The first, an older WRT54GS Wireless G lacking current security standards and then a WRT150N Wireless N. Both worked fine with the NC, allowing full access, with the latter operating at N mixed B, G and N speeds and WPA2 Personal security.
I am very pleased with the results after a few frustrating hours of trying to diagnose the problem. I hope this information is helpful to others. My friend and I will doing some router swapping. I may not tell him about how great the NC is!

Or maybe the NC?
jdefgts said:
Of course I can't speak for others, but my experience with this problem was that this problem was entirely router related. The rooted NC was very slow (to the point of almost unusable on the internet) from my home Netgear WNR834B Wireless N router, regardless of the speed settings, the channel or the security settings. I was able to experience much faster speeds (allowing UTube and Pandora to function properly) at a friend's home (generic Verizon DSL router) and at 2 public wifi locations. As a result I tried another Netgear WPN824 Wireless G Router with the same results as the other Netgear device.
Then I borrowed a couple of Linksys routers from a friend and tried them. The first, an older WRT54GS Wireless G lacking current security standards and then a WRT150N Wireless N. Both worked fine with the NC, allowing full access, with the latter operating at N mixed B, G and N speeds and WPA2 Personal security.
I am very pleased with the results after a few frustrating hours of trying to diagnose the problem. I hope this information is helpful to others. My friend and I will doing some router swapping. I may not tell him about how great the NC is!
Click to expand...
Click to collapse
Yep.. no doubt the right router will work with NC. But at home and at work the NC is the only device having problems. I have no luck in convincing my company to swap out 45 routers so my NC can work

waylo said:
Just bought my NC and flashed a great Froyo ROM on it.
(The first one I bought had obvious hardware issues, 1bar of wifi signal in the same room as my router. Brought it back same day and had it replaced, immediately better. A known reported issue with some faulty NCs).
Had the same issues with wifi connectivity as described here and everywhere on the net. Essentially, it will connect onto the router with N speeds, but is completely unable to access any internet.
I have a great router (it can broadcast 3 separate SSIDs) but I think it doesn't play nice with the nook. So, it was great up until now =P
Router brand and model number: Buffalo WZR-HP-G300NH
802.11 mode: n
SSID visible? yes
Encryption:
SSID1: (WPA+WPA2 mixed TKIP/AES) OR (WPA+TKIP)
SSID2: WPA2+AES
SSID3: WEP (yuck)
The Nook only fully connects to the WPA+TKIP mode (on SSID1) or WEP. The supposed mixed mode setting probably isn't quite as mixed as advertised. The Nook works fine on WEP, but I hate the fact the security is so poor with WEP.
I'd have no problem dropping the SSID1 settings to WPA security, except for the loss of n speeds. Part of the 802.11n specs (has to be WPA2/AES, or NO encryption--not an option). My DVR/home network is on that ssid, so I don't want to lose my n speeds.
So my question is do any other ROMs here help fix the WPA2 connectivity? I know lots of people swear their NC works fine with their WPA2 router, but I suspect their router is just more capable and is switching to WPA-TKIP discreetly.
This is not the same reported problem as having wifi cut off in sleep mode.
EDIT:
Oh, I just realized as a work-around I could put my home network on SSID2, and just the Nook on SSID1.
Click to expand...
Click to collapse
I have similar issues. I can't use the internet reliably on my Nook Color or my EVO on my home router unless I'm running WPA+TKIP. I would prefer not to have my router setup this way though because of the security concerns and it not being much harder than WEP to crack.
Guess I'll just stick with WPA2+AES and look for another solution...

just to share some experience that hapenned to me:
In France we have an Internet box (wich is basically a router) that deserve 2 wireless network. One public shared with all user from the same Internet provider and one private for home.
At first my nook only saw the public one (wich is not really fast). The private one was not visible (or just flash in network tools on nook).
After some investigation i change the Wifi canal (from 10 to "automatic"). After that, no to see it and connect (if you forget the nook "special sleep policy")

soobaerodude said:
I'm having trouble connecting to an 802.11B (yes B) 11Mbps unencrypted router on the bus I commute to work with. Not sure of the brand or model. Wireless status says I'm connected, but testing. I try to browse the web with Dolphin HD, but I never connect. My iPhone connects to the bus' same router without problem.
However it connects just fine to a Linksys WRT610N v2 (flashed with TomatoUSB) running 2.4Ghz N, 40Mhz bandwidth, WPA2/AES
Running Autonooter 1.1, but given what Zhousibo said in the previous post, I'll try out NF 0.6.8.
Click to expand...
Click to collapse
Tried Nookie Froyo 0.6.8 on the bus this morning. It connects and gets an IP address, but still can't browse or do anything internet related.
Going to try to exchange my NC for a new one tonight, and see if things improve.

soobaerodude said:
Tried Nookie Froyo 0.6.8 on the bus this morning. It connects and gets an IP address, but still can't browse or do anything internet related.
Going to try to exchange my NC for a new one tonight, and see if things improve.
Click to expand...
Click to collapse
Please give an update after you exchange your NC. I suspect is the wifi chip drivers and not a bad NC.

fpga_guy said:
This is a compilation of threads found on this forum as well as the BN forum. I thought having it in one place will help.
The NC is the first device that I have encountered that had intermittent wifi problems. At home, I have a mixture of Macbooks, iPod, a Viewsonic G Tablet running Android 2.2, desktops running Windows 7 and XP using various brands of USB wireless adapters and have NOT had any problems using 802.11n with WPA2/AES encryption.
From other threads: "As always, everything in this guide is completely at your own risk, I am not responsible for you messing up your device further nor am I responsible in the event that your Nook Color explodes and kills your cat, grandma, etc."
Click to expand...
Click to collapse
i dont experience any of these problems where ever i go
i have been able to connect into every coffee shop, book store, and school campus(i go to 3 different schools) plus i can hold a wifi connection at home
ill give you my router settings because it may have something to do with it
Router brand and model number: eg: NETGEAR : unknown
802.11 mode: b,g ,n
SSID visible: yes
Encryption: no or if yes: yes WPA2
NC Rom: HC preview 4
NC OS: 3.0
and my droid x works as well with the WPA/WPA2 security

WiFi Adhoc working with wpa_supplicant tweak !

Good news, the wpa_supplicant replacement tweak works on the Streak 7 too so the silly "neutering" by Google (to please the carriers apparently) can be circumvented. You can now connect to WiFi AdHoc networks, that's generally the type of network that a tethered smartphone creates, iPhone/iPad with MyWy, Barnacle on Android (http://szym.net/barnacle/), etc...
The Streak uses the v0.6.10 version.
Original trick is here : http://forum.xda-developers.com/showthread.php?t=754961
Since there was some confusion with the files I am uploading the one I used to make it easier.
The way I installed is :
- RootExplorer (requires rooted device)
- Go to /system/bin/
- Tap R/W at the top so it becomes R/O
- rename existing wpa_supplicant in /system/bin/ to wpa_supplicant.old
- paste new wpa_supplicant
- start and restart wifi
If you prefer to use adb, this command should do it :
adb push wpa_supplicant /system/bin/
You'd have to rename the existing one first though.
Hope it helps !

What exactly will this do?
Sent from my Dell Streak 7 using XDA App

Lets you connect to WiFi AdHoc networks, that's generally the type of network that a tethered smartphone creates, iPhone/iPad with MyWy, Barnacle on Android (http://szym.net/barnacle/), etc...

My s7 connects to my phones hot spot no problem?
Sent from my Dell Streak 7

Good for you, but that's probably because your phone creates a REAL wireless network like a wireless station, most tethering apps don't, like MyWi on the iPhone/iPad.

i have a streak 5 and with patches i got on other sites. They let me see the ad-hoc networks (*) but don't let me connect. All it does is go to obtaining ip address and the keeps looping at that.
Would this one act differently or will it not work for my little streak 5?

Probably wouldn't be any different, but that's strange, what AdHoc networks are you trying to connect to? Try to set their WiFi channel to 11 to see if it helps.

i tried to connect to my ar.drone and also a ad-hoc network i created on my pc. My wpa_supplicant is 0.5 on my streak at the moment. could that be the problem?
I can connect my ardrone to my pc. I can connect a laptop to my pc. But i can't get the streak past the "obtaining ip address". When i use static it connects right away but it connect nowhere.
With the new version of streakdroid it can with the ad-hoc fix included. When it didn't work i tried other ones and all with the same result. So i'm expanding my search to include similar systems.

Awesome!!!
webvan said:
Good news, the wpa_supplicant replacement tweak works on the Streak 7 too so the silly "neutering" by Google (to please the carriers apparently) can be circumvented. You can now connect to WiFi AdHoc networks, that's generally the type of network that a tethered smartphone creates, iPhone/iPad with MyWy, Barnacle on Android (http://szym.net/barnacle/), etc...
The Streak uses the v0.6.10 version.
Original trick is here : http://forum.xda-developers.com/showthread.php?t=754961
Since there was some confusion with the files I am uploading the one I used to make it easier.
The way I installed is :
- RootExplorer (requires rooted device)
- Go to /system/bin/
- Tap R/W at the top so it becomes R/O
- rename existing wpa_supplicant in /system/bin/ to wpa_supplicant.old
- paste new wpa_supplicant
- start and restart wifi
If you prefer to use adb, this command should do it :
adb push wpa_supplicant /system/bin/
You'd have to rename the existing one first though.
Hope it helps !
Click to expand...
Click to collapse
THANK YOU SOOOOOOO MUCH!!! This worked perfectly on my Streak 7......I even ended up buying "Root Tools" for this but ended up really liking it!
I can finally hook up to the iphone 4 data plan I'm already paying for ;-)

works for me
Thanks for the help.

Error Message-DjSteve HoneyComb RC3
I get an error message when trying to turn on wifi on DJSteve's HoneyComb RC3 version.

Awesome
Thank you so much for this! Works great from my Hero to DS7

Finally working "Adhoc"!!
Use this method on my rooted, stock 2.2.2, T-Mobile S7, works great!! Thanks.
My S7 finally sees and can connect to the adhoc networks.
Tried the S7 on two phones using "adhoc" wifi tethering, both works!!
First one, my old but beloved Nokia 5800, using "JoikuSpot", S7 sees the adhoc network and connect to it with "wep enable" with no problem.
Second one, Sony Ericsson Xperia X10 mini pro, stock android 2.1, rooted, using "Barnacle". S7 can see the Adhoc network but have a hard time obtaining IP or may I say most of the time failed to connect. Then I went onto the Barnacle forum and they suggest a solution, which is first connect another device to the Barnacle first then connect your S7 after that. Somehow this method works. By the way this method also works on iPads. Barnacle aware of this problem, and is working on it. So what I do is first "jump start" the network connection by using either my laptop computer or my retired 1G iphone, both works great, after that adding addition connection to the Barnacle network is a piece of cake.
Once again, thanks "webvan" for the information and the mod. This finally make my S7 complete!!

Does this file need to be switched back for any reason or will it be ok if its left in place?
I mean will it change anything else by leaving it?

Someone please help me. I follow the steps by OP and when I try to access wifi I get a error and can't connect. Any ideas what I am doing wrong.

Worked great for me! I'm really mad at tmobile for not updating the s7 4g, I will enjoy halting my data plan.
Sent from my Dell Streak 7 using xda premium

i followed the instructions precisely, but when i turn on the wifi, it says "obtaining IP address...." then it turns itself off.... i returned to the old wpa_supplicant file (the original)
any idea about how to fix this?

I have a similar problem with my dell streak 7 honeycomb 3.2.
I can connect to Ad-hoc network created with my Android 2.1 phone. Every thing seems to work ok but after using internet browser for few secounds wifi is going down. Also if I connect to another, infrastructure network after that, problem repeats until reboot.
I used adb to push patched wpa_supplicant. To make it executable i used command:
adb shell chmod 777 system/bin/wpa_supplicant

I'm having the same problem. After applying the patched wpa_supplicant file using adb I can no longer stay connected to infrastructure networks. Ad-hoc networks stay connected fine. I've tried deleting the connections and re-adding them to no avail. A reboot or disabling/re-enabling the wireless works for about a minute and then it disconnects.
At this point I'm ready to go back to the stock wpa_supplicant file, if I could find a copy of it somewhere.
Any suggestions would be greatly appreciated.

jason331 said:
I'm having the same problem. After applying the patched wpa_supplicant file using adb I can no longer stay connected to infrastructure networks. Ad-hoc networks stay connected fine. I've tried deleting the connections and re-adding them to no avail. A reboot or disabling/re-enabling the wireless works for about a minute and then it disconnects.
At this point I'm ready to go back to the stock wpa_supplicant file, if I could find a copy of it somewhere.
Any suggestions would be greatly appreciated.
Click to expand...
Click to collapse
Are you on HC? I am still on stock and it works fine on either ad-hoc or normal points.

[Q] Wifi not connecting to infrastructure network (802.11x)

Hey guys, so here at PITT, the school runs a 802.11x infrastructure wifi network, and I cannot connect.
I am running HC v4. When I go into WIFI, the Nook will see the network. Then when I put in PEAP, my username, and password, nothing happens. I just hit "connect" and the nook does nothing. It is like it does not remember the settings I just put in.
It connects fine to the adhoc network on my phone (tether). Also, it connected to PITTnet fine before when just rooted, and with nookie froyo.
I tried doing this (with slightly different settings): http://forum.xda-developers.com/showthread.php?t=974689&highlight=wifi
But it did not work. It is like the Nook sees the network, but just refuses to do anything with it.
Any ideas? Thanks.

I connect to an 802.11x network here @ work, and my recommendation is to hop on the market on another wifi connection, and download "Wifi ACE" to facilitate editing the config easier. If you can't download from market but have ADB working, you could manually install the .apk from here: http://code.google.com/p/android-wifi-ace/
I will tell you - I've had spotty capability to access this network using HC v4, internal eMMC build v2. I have 100% success using Nookie Froyo and Phiremod, by comparison, using the exact same settings - I manually saved off the wpa_supplicant.conf file between installs. I experience the same symptom you do, I see the network fine, just refuses to connect.
Think we're just stuck till AOSP releases and we get a new version of HC on the NC.
Same as you, any other WiFi network connects with ease. It is just the 802.11x network I have problems with. It worked for me on HC eMMC v1 though, so if you haven't tried that give it a shot.

[Q] Wifi stopped working?!

My Nook is having CM7/Phiremod v5.2 and has been connecting to my home wifi with no problems.
Suddenly it can't connect. There is a small question mark on the wifi icon.
It scans and finds the usual networks. Try to connect, it seems to be negotiating, but it doesn't connect. I have tried to re-enter the key, but no success.
Has powered down and restarted several times. No luck.
Ran a "fixing permissions" from Rom Manager (dunno' if it could help, but...). No luck.
Other devices can connect to my home wifi.
Connected the Nook to the wifi access point at my work. No problems, good connection.
Tried to boot Honeycomb of the SD-card. Wifi couldn't connect.
The wifi hardware of the Nook works, but it won't connect to a network that it has been connecting to ever since I got the Nook.
What's going on?
Anybody has a cure?

Caspar07 said:
My Nook is having CM7/Phiremod v5.2 and has been connecting to my home wifi with no problems.
Suddenly it can't connect. There is a small question mark on the wifi icon.
It scans and finds the usual networks. Try to connect, it seems to be negotiating, but it doesn't connect. I have tried to re-enter the key, but no success.
Has powered down and restarted several times. No luck.
Ran a "fixing permissions" from Rom Manager (dunno' if it could help, but...). No luck.
Other devices can connect to my home wifi.
Connected the Nook to the wifi access point at my work. No problems, good connection.
Tried to boot Honeycomb of the SD-card. Wifi couldn't connect.
The wifi hardware of the Nook works, but it won't connect to a network that it has been connecting to ever since I got the Nook.
What's going on?
Anybody has a cure?
Click to expand...
Click to collapse
First off, have you rebooted your AP? Sometimes they go stupid.
Have you tried deleting and reconfiguring the connection? IE: The "Forget" option?
Also, verify that your access point is not using AES encryption for the connection. AES seems problematic. TKIP seems to work okay.

Just stRted happening to today as well.
Sent from Fascinate SuperClean 2.9.2 Voodoo Using Xda Premium App

khaytsus said:
First off, have you rebooted your AP? Sometimes they go stupid.
Have you tried deleting and reconfiguring the connection? IE: The "Forget" option?
Also, verify that your access point is not using AES encryption for the connection. AES seems problematic. TKIP seems to work okay.
Click to expand...
Click to collapse
No reboot yet. The reason is that my home AP is managed by my work, and reboot means all sorts of hassle. So I'll avoid as long as possible. But other devices (my laptop) connects.
Yeah, deleted and reconfigured. No change.
It's using TKIP.
Now I'm doing a backup of the Nook, considers installing Phiremod v5.3.
Maybe that'll change something.
What about deleting some of the caches of the Nook. Anything there?

Same here. Wifi was working until today (4/4). All other devices in my home network are connected without problems.
I have 1.1, rooted with autonooter.

Updated with Phiremod v5.3.
Problem still there
Enter passkey, says "Authenticating" and then the connection to the AP is "Disabled".
In addition Market has disappeared.
Not good.

Caspar07 said:
In addition Market has disappeared.
Not good.
Click to expand...
Click to collapse
Ok, connected to another wifi - no problem.
Market popped up. Good.
But it still won't connect to my access point at home. And it worked perfectly until sunday!?
Mindboggling.

Did you try hitting menu while in the WiFi options menu, and going to advanced? You can force the nook to have a static IP and connection information. It might help, you never know.

woot1524 said:
Did you try hitting menu while in the WiFi options menu, and going to advanced? You can force the nook to have a static IP and connection information. It might help, you never know.
Click to expand...
Click to collapse
Haven't tried that. Will do tonight. Thanks.
I did go to Advanced and choose not to let wifi go to sleep. Didn't help.

Caspar07 said:
Haven't tried that. Will do tonight. Thanks.
I did go to Advanced and choose not to let wifi go to sleep. Didn't help.
Click to expand...
Click to collapse
And you still haven't unplugged it for 30s? Do it.

Happy end, just like the fairy tales
My access point needed a kick in the butt!

Is this a problem specific to Phiremod (5.3), or are people having WiFi issues with the Nook Color in general?
New to Nook Color and to Phiremod. Have everything up and running just fine, but keep getting repeatedly kicked off WiFi every few minutes. Have to disconnect then reconnect. No other devices have issues. I never used the Nook Color stock, so no idea if it's just the device itself.
Router's an up-to-date Netgear WNDR4000, running WPA2-PSK [AES]. WEP or WPA-PSK [TKIP] not an option -- not secure.

Caspar07 said:
Happy end, just like the fairy tales
My access point needed a kick in the butt!
Click to expand...
Click to collapse
Surprise........

my icon also disappeared and can't connect to any web access via app or widget, can't go to market either... HD2 T8585 O2 UK...

OUSCA2007 said:
my icon also disappeared and can't connect to any web access via app or widget, can't go to market either... HD2 T8585 O2 UK...
Click to expand...
Click to collapse
Uh, wrong forum?

[Q] Does WiFi Ad Hoc Mode work with 1.2?

I was wondering if anyone had tested the new update (1.2) with Wifi in the Ad Hoc Mode as is commonly used with WiFi Tethering apps? Version 1.1 could not see a ad hoc WiFi network without some file modifications.

answer from a newb
No it still does not see adhoc networks, what modifications do you speak of, for that is what i would like my nook to do, see and connect to adhoc networks. i assume i will have to root it, and if so is there a clear easy way to root the 1.2 update? or even better have the stock system and rooted system side by side (i think i read that you can use the sd card to hold the root info on. i a newb to all this rooting stuff, but want to expand and learn.

Cpt420 said:
No it still does not see adhoc networks, what modifications do you speak of, for that is what i would like my nook to do, see and connect to adhoc networks. i assume i will have to root it, and if so is there a clear easy way to root the 1.2 update? or even better have the stock system and rooted system side by side (i think i read that you can use the sd card to hold the root info on. i a newb to all this rooting stuff, but want to expand and learn.
Click to expand...
Click to collapse
I am rooted on the stock 1.1. I use the ad hoc switcher (search these forums) when I need ad hoc to connect to my rooted Moto Droid with WiFi teather. If ad hoc is still not working with 1.2 then I will probably continue to use the switcher for the few times when I need it.
Still waiting on an auto-neuter for 1.2. When it is available, I will flash back to stock, upgrade to 1.2 and then auto-neuter 1.2. I used it for 1.1 and it was flawless.
If you are on stock, unrooted 1.2 then you might want to wait for the auto-neuter as well.

Ad Hoc is still broken. I had trouble also trying to use connectify (win 7 wi-fi sharing app)...my NC couldn't pick up the WPA2-PSK network. So no luck there either.

Ad-Hoc works for me without any modifications under 1.2 and sleep works without having to turn on and off the nook to get wifi to work again. I am in love!

Ad hoc now works fine with 1.2 -- just tried with with Wireless Tether and my Droid X.

Has anyone tried with the myWi from any iphone version?

Yes that's how I tether...it's working wonderfully with 1.2 no hack needed
botossi said:
Has anyone tried with the myWi from any iphone version?
Click to expand...
Click to collapse

You getting adhoc on MN or just stock 1.2?

jtxmobile said:
Ad-Hoc works for me without any modifications under 1.2 and sleep works without having to turn on and off the nook to get wifi to work again. I am in love!
Click to expand...
Click to collapse
Are you sure it is stock 1.2 and you are on a ad hoc network? It is still an android system that will not see ad hoc. I tested it today with windows wifi router on ad hoc and the nook would not see it.

My personal experience ... the ad hoc patched wpa_supplicant file on nookdevs.com and some xda forums works on all versions of nook color, stock mods or even honeycomb preview. But does not work on stock or rooted update 1.2. Apparently this is because the working os versions are using version 5 of wpa_supplicant and the patched verson is also version 5 ... nook color update1.2 however uses supplicant version 6 and no one has recompiled an ad hoc patched version 6 wpa_supplicant yet for the nook color as has been done for other phones and tablets on xda forums. While some people think they are connecting with phones via ad hoc, using version 1.2 of the nook, there phones are most likely generating aps in infrastructure modes and not ad hoc mode.

New, rooted 1.2 needs WPA supplicant fix for adhoc
At least in my experience. I bought my nc with the 1.2 already pre-installed. It would only recognize the infrastructure wifi. I have the droid 1. It does not have the option to become a WiFi hotspot as newer phones do (30$ through Verizon). With wireless tether/barnacle I've been able to connect through the droid as an adhoc network, but only after the wpa_supplicant fix. I use it every day this way, as there's no WiFi at my office.
BTW, it does go between my home wifi and my droid adhoc without having to make any additional hacks beyond the most basic one. It seems to recognize both easily, back & forth every day.

Rsptexas, just wanted to (respectfully!) be clear that the droid 1 is definitely adhoc, no question whatsoever. Though I'm aware people are getting confused about what their phone puts out. I can't recall which version of the supplicant fix finally worked, as I tried several. Don't give up on it folks, you can really get adhoc to work on 1.2

Final thing then I'll shut up: 'toolbelt' says the wpa supplicant fix in post 872521 on this forum has the version of the fix that works for the rooted 1.2 ( junior member, can't do links yet, sorry).
Just type the number of the post in the search box at the top of the page

I can verify that http://forum.xda-developers.com/showthread.php?t=872521 does work for Manual nootered 1.2. I did not even need to apply the change back to infrastructure.
There is a lot of false info. out there. Many people think their phones are running AdHoc when in fact they are running infrastructure. Many modern modern phones can do infrastructure, and some roots provide it for free.
My lil old Eris, definitely does not support it.
Now my Nook can connect through AdHoc.
~Leko