Related
I upgraded my Cingular 8125 last night with the excellent 2.17 rom provided by summiter. All was looking great until I tried to connect to my wireless network (Linksys WRT54GX4 SRX400 router with WPA-PSK security). I entered the key and it tried to connect, but then my wireless network switched from "Available" to "Unavailable" and dropped to the bottom of the network cards list. I could click on the network and tell it to reconnect, but it would do the same "available...unavailable" sequence every time. Wondering if it was a bad flash, I reapplied the 2.17 ROM and tried again with the same results. Not to give up too easily, I grabbed the 2.16 iMate ROM and applied it to see if the Cingular customizations could be causing the issue. Same problem.
So I disabled all security on my Linksys, cleared the net card settings on the 8125, and tried to reconnect. No luck. My neighbor has a plain Linksys WRT54G, so I tried to connect to hers and it worked just fine. At this point, I had to go back to the stock Cingular ROM because I need access to my wireless lan. All works well with the stock Cingular ROM.
Has anyone else seen this behavior with the 2.x ROMs? I'm wondering if there is a bug in the wireless networking support in the updated version of WM5 or if it is some weird incompatibility with the new Linksys WRT54GX4.
-BK
edit: corrected the router model number
At this point, I had to go back to the stock Cingular ROM because I need access to my wireless lan. All works well with the stock Cingular ROM.
Click to expand...
Click to collapse
Hey, does this ROM upgrade allow you downgrade. i have read stuff on this forum with people saying that they get an error "upgrade only" if they try to downgrade.
Way to keep the same topic going...start your own thread. :roll:
Unfortunately I don't have any feedback or value to add. I've connected successfully to a WRT54G, a Belkin Pre-N, and a Belkin Pre-N running Linksys WRT54GX firmware. No problems, but then again I use only WEP (I'm not overly concerned about the security of the traffic on this particular network, hence I use WEP instead of better encryption).
It's odd that with all encryption turned off you still can't connect. You don't by chance use MAC address inclusion/exclusion do you?
Yes, I normally use MAC filtering along with WPA to only allow certain devices onto the wireless network, but I disabled the MAC filtering for the same test where I disabled the security. The stock ROM works with both WPA and MAC filtering enabled. It's quite a strange problem. I must say that I find myself wanting the features of the newer firmware so much that I'm considering just not using the wifi connection anymore...
Thanks for putting the work into packaging the new ROMs for us. Cingular sure does drag their feet releasing their own updates.
-BK
my Cingular works good with Netgear WGR614 v5 & Linksys WTR54G
I've had the same problem with the updated roms. I'm running a D-Link 614+ rev b router using MAC filtering and no encrypton. My 8125 sees the router but it can't connect. I adjusted mty power settings but still no luck. I think everyone who has this problem should list their gear here so we can figure out a way to get around this problem.
I had WPA issues connecting my 8125 with my linksys WRT54G.
I'm in the same position as summiter, I'm really not concerned about the security of my home network, so I went back to WEP - which works fine. A combination of not broadcasting the SSID, MAC filtering, and WEP seems secure enough for my purposes.
I had the same problem after I updated my 8125's ROM. After many minutes of frustration playing with settings, I unplugged the router for a couple of minutes, and then plugged it back in and my phone began to work just fine. You may want to give this a try.
CameronJ said:
I had WPA issues connecting my 8125 with my linksys WRT54G.
I'm in the same position as summiter, I'm really not concerned about the security of my home network, so I went back to WEP - which works fine. A combination of not broadcasting the SSID, MAC filtering, and WEP seems secure enough for my purposes.
Click to expand...
Click to collapse
It's more a matter of security through obscurity, since there are tools to both find devices not broadcasting ssid, and for cracking the wep key in a matter of seconds or minutes. On the particular WiFi net I use I assume everyone can see it and don't use it for sensitive stuff. MAC filtering can be overcome, but it takes someone determined and knowledeable, and I don't think my neighbors or the casual wardriver fit that bill. =)
Hello All,
This sounds like their is some settongs on the phone are set wrong, try changing the select network setting on the top bar select the second set of settings witch are I belive my work network, then soft reset the phone it should work it did for me but not until the soft reset. you my want to setup the connection again and reset again after putting in the key. I do use the newest 2.17 rom as well seems to be good so far.
I also used this to trouble shoot it. http://www.htcamerica.net/support/cingular_8125.htm
great source of help.
I think it is definitely something with the 2.X ROM’s and this router. I have the same setup and can’t get anything but the original Cingular ROM to connect.
Using Summiters excellent 2.17 with WRT54G with no problems on QTEK 9100.
porky145 said:
I've had the same problem with the updated roms. I'm running a D-Link 614+ rev b router using MAC filtering and no encrypton. My 8125 sees the router but it can't connect. I adjusted mty power settings but still no luck. I think everyone who has this problem should list their gear here so we can figure out a way to get around this problem.
.
Click to expand...
Click to collapse
summiter
I'm having the same issue, i'm acutally using the same router as the person above, it will see the router but wont connect unless i reset the router. Plus it wont connect to any hot spots that it used to when it was on the old OEM cingular rom, so it must be something with the new 2.17 Rom. Did you make any changes in the WiFi settings?
please help us, i would love to keep the new rom on my wizard, it's so much quicker and it has all the extra bells an whistles.
thanks
Chiming in...
I actually found that the WIFI works better with the latest ROM (2.17/CF2, etc.) from summiter. There were networks that I couldn't connect to to save my life... now I can get in no problem.
Sorry you guys are having problems though.
marcini said:
porky145 said:
I've had the same problem with the updated roms. I'm running a D-Link 614+ rev b router using MAC filtering and no encrypton. My 8125 sees the router but it can't connect. I adjusted mty power settings but still no luck. I think everyone who has this problem should list their gear here so we can figure out a way to get around this problem.
.
Click to expand...
Click to collapse
summiter
I'm having the same issue, i'm acutally using the same router as the person above, it will see the router but wont connect unless i reset the router. Plus it wont connect to any hot spots that it used to when it was on the old OEM cingular rom, so it must be something with the new 2.17 Rom. Did you make any changes in the WiFi settings?
please help us, i would love to keep the new rom on my wizard, it's so much quicker and it has all the extra bells an whistles.
thanks
Click to expand...
Click to collapse
I can third this comment about he DLink 614+ and the DLink 524. My 8125 connects to the routers but then immediately locks up and I have to take the battery out to get it working again. I have not upgraded the firmware on either router so I might try doing that this weekend before doing anything. I know that DLink has upgraded some of ther routers due to some issue they had with NTP.
So far, I tested two routers with WPA: Linksys WTR54GS travel router and DLink DI-634M. And my workplace's wireless network using Cisco Access Points (54G) with no security (we use additional Cisco VPN in order to access network). All worked fine without issues. There are definitely changes in new wireless drivers. For one, it has a lot more parameters in registry. For two, it now supports LEAP. Thirdly, in the wireless networks window, it now shows signal strengths for each network. These are all positive improvements.
I haven't try to connect to a 11b router because I can't find one. Sounds like the issues are specific to DLink DI-614+ and the similar. If that's the case, time to get a new router. It's only $40 and you get much faster speed.
The router giving several of us problems is the Linksys WRT54GX4 SRX400, which is the latest MIMO router from Linksys...
-BK
foxbat121 said:
If that's the case, time to get a new router. It's only $40 and you get much faster speed.
Click to expand...
Click to collapse
I understand what you are saying but I don't think thats the point. Replacing the router is easy, but what was changed in the rom to cause this problem. And if anyone wants to know Circuit City has G routers on sale, I got a WRT54G for about $65 out the door. But i would still like to know what caused this problem
I believe there is a difference between the network adapter driver from ROM2.17 and Cingular ROM. Anyone with network connection problem after upgrade to ROM 2.17 may want to try this:
Download and install WiFiFoFum2 from Aspecto Software, then run this program everytime you turn on wifi, it will help detect and connect to your network. I can't explain why but it works for me so I hope it would work for you too. My network is Dlink-524 with WPA enabled and MAC filtering.
Anyone else having trouble using the internet over wifi (wep & wpa) with the actiontec router that comes with Verizon fios? I can ping the G1 and telnet into it. Just can't use the browser. I am able to connect to other WPA encrypted routers and everything works great. This problem existed on rc19 and continues on rc30.
Thanks for any help.
aad4321 said:
It worked well with my actiontec, with WPA as well. sounds strange...maybe a router reboot
Click to expand...
Click to collapse
Was the first thing i tried.
I don't have one yet (it is coming December 13th HAHA) But can you two compare firmware versions? Maybe you need to update that... or maybe there is a setting that is preventing the phone from getting to the net. It sounds more like a setting on the router than the phone.
I would check DNS settings and make sure all works well... Can other wifi devices connect to the net?
Same here, 4.0.16.1.56.0.10.7.
Have also tried static and dynamic ip's. My daughters DS and computer are connected via wifi. Next I'll try turning UPnP on.
Thanks for everyone's help.
Edit: UPnP is a no go. I don't want to do a factory reset but, looks like I'm headed that way.
have the same problem
what did you end up doing?
tried it
didnt work...
I have fios myself and the wifi portion of the Actiontec router is craptacular. I've had all sorts of compatibility problems with various wifi cards. I have replaced the primary router with a .N aftermarket one and hooked up the Actiontec as a regular client so the TV cable boxes can still get programming updates. Naturally, I turned off the wifi on the actiontec.
So its basically like this:
Actiontec -> D-Link N (or whatever you want) -> Internet
If you go down this route you just have to make sure whatever router you make your primary is not on the same private network. Actiontec uses 192.168.1.X. I've had no problems since switching to a higher end router. Also, you can clone your mac address from the actiontec or call verizon and have them reset your DHCP lease. They know the drill.
I have FIOS with the newer Westell routers and the wifi sucks on them as well. I got a belkin and use it as a wifi expansion. So it uses the same IP as the router but just adds a wifi network. Pretty neat if you ask me.
so i think may have found a solution that may work for you (it worked perfectly for me). what i did was switch my security to WPA2 and left the encryption standard to AES only as a pose to TKIP+AES. I also reset the router before this but im sure you dont have to do that. let me know if this works.
http://forum.xda-developers.com/showpost.php?p=10035476&postcount=10
neoobs said:
I have FIOS with the newer Westell routers and the wifi sucks on them as well. I got a belkin and use it as a wifi expansion. So it uses the same IP as the router but just adds a wifi network. Pretty neat if you ask me.
Click to expand...
Click to collapse
Could you be kind and give us more details of exactly how you connected and setup the belkin router to improve the wifi? My FiOS wlan also sucks and Verizon tech support is useless.
Thank you.
Oops! Just realized this is a very old thread......
German G1, stock firmware CRC37, 2.6.27-00393-g6607056
Well, I am in the process of upgrading to 802.11n routers. At my family's place this turned to be a Linksys WRT160N, here at home it's a Buffalo WZR-HP-G300NH.
With both routers, I am having trouble establishing reliable connections. I've been looking a bit more into it with my Buffalo router: the phone connects to the WLAN, but finally, varying from a few seconds to several minutes, i receive timeouts resulting in UnknownHostExceptions. Toggling wifi will restore connectivity, just to run into the same problem again.
I have had no problem with my Linksys WRT54G, nor with any other devices in my place (two 802.11n devices, a MacBook Pro and an AppleTV). There's also a Wii (802.11g/b?!) and an HP 2133 (802.11n) I haven't tried yet.
The Buffalo router operates on a custom Linux, 40MHz bandwidth, WPA2/AES in the 2.5MHz spectrum, 3 Antennas, 300MB (mimo).
All in all, googling makes me believe that a fair amount of people have problems in similar settings, but none of what I found could point directions into a solution.
Router setup is not the issue (i have been able to reproduce in two totally different setups that work with any other devices I have tried). Neither do I believe that a mix of 802.11g and 802.11n devices necessarily causes these kind of problems (at my family's place a 802.11g imac works flawlessly alongside of my 802.11n MacBook in an 802.11n network).
I am attaching a logcat that I captured while producing the problem. It only illustrates the problem a little.
In the end, probably the broadcom WLAN chip/driver gets stuck at one point and android cannot do much against it. If this is the case, posting a bug report against google/android open source developers probably won't help much, as it seems to be an issue of the driver/wifi chipset combo HTC/TMo uses in the G1.
If you agree on this, in the end I am looking for a way to file a bug report either at htc or t-mobile, but contrary to Android/Google, I haven't found anything on the net that I can file a bug report into... 1.0 companies *sigh*
What other ideas do you have? While I could leave the G1 just on 3g while at home, I don't have reception in every corner and the whole point of having it is being online essentially most of the time in order to catch my mail (it is set to keep wifi on while charging).
Regards
Interestingly, if I start streaming after connecting to WIFI, like speedtest or YouTube, the connection stays alive for the time being...
Hello
My N1 can connect easily to all kind of wifi routers and modems without problem but not with my fitness club's one, they have a Linksys N160.
My N1 can detect the signal,enter the password but then it's stucked with the message ''getting ip...''
Where is the problem? is it a know hardware or software compatibility stuff?
Sometimes rebooting the wifi router helps. Also make sure that when the guy over at your fitness club reboots the router you don't have the wifi of the club saved. delete the saved wifi profile, reboot the wifi router and then try. Cheers.
Already tried it several times. I saw that OS4 of iphone/ipod have the same problem with router enabling Wireless-N, I will ask him to limit the router to B/G
I also had similar problem with Linksys WAG54G2 (at latest firmware). Then I changed to much cheaper adsl router, TP-LINK WD-W8960N and no more connection problem.
Sent from my Nexus One using XDA App
I had problems using my Nexus One on my SMC Barricade 802.11b/g/n router when 802.11n was enabled. Turned it off; problems were gone. I don't think that works well yet, though some people have said otherwise. Could be a router-specific issue.
Ok so it's a WAG160N to be specific.
He tried to use mixed B/G instead of mixed (which would imply N too) but it still stuck at getting ip...
I told him to throw this router in the garbage because anyway SE and HP mobiles can't connect too,but he said he would do it but his boss will never accept to pay a penny more
My parents had a router that did exactly the same, my phone got stuck on Obtaining IP, whilst the missus 5800 connected and broswed just fine.
It was a crappy old thing and they replaced it the other week, now I can connect and browse just fine.
I also use a linksys WAG160N.
bought a nexus one, could not for the life of me get an internet connection.
turns out dns on router is poofed, so i just set DNS from my isp manually on the nexus one together with a static ip and booya interent at full 802.11n speeds.
sometimes its the simple things.
This sounds similar to when I set my router to channel 13 or whatever the max was on it. My N1 would only sometimes get a connection, but would eventually drop it and stay off. Solved it by selecting a lower channel (WifiAnalyzer suggesten channel 1 as the best alternative to channel max) on the AP.
I can see that in CM6 nightly that I have since started using I can choose regulatory domain, and thereby open up channels previously blocked. If you can't change anything on the AP this might help you solve the problem on your end.
So suggestions if none of the posts above me provide a solution is to run WifiAnalyzer and see how the channel-graph looks.
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