Related
So ever since I've gotten my Nexus One I've been noticing it drops out of a WiFi way too often. It does it both at home and at work on Wireless routers using the latest firmware. I've set the sleep policy to never go to sleep but most of the times I wake my phone up, I'll find it on 3G instead of the full strength WiFi it should be on. On 2.1 when I'd go into WiFi settings it would show the connection and say something along the lines of "Connection unsuccessful, tap to try again" and on 2.2 it just says "Disabled, Secured by blah blah blah". If I retry, it ALWAYS connects and WiFi will stay active for a short period of time before falling back to 3G.
Is there some way I can tell Android to retry the WiFi connection if it fails instead of just giving up? I've been looking through the WiFi API's on the Android Developer site and I'm this close to writing an application that will attempt to mitigate this issue for me.
If I'm within range of one of my pre configured networks, I want the phone to try it's hardest to stay on WiFi. If it loses connection, retry. It it can't get it after 5 retries, wait five minutes and try it again, don't just give up and mark the connection as disabled.
I've read tons of threads about people with WiFi issues and people always say "it's the router, it's the channel, etc, etc" but my WiFi works perfectly fine as long as there is a human to reconnect it if it drops.
Anyone else in the same boat as me?
ok so apparently I'm the only one with an N1 and a WiFi issue.......
I have the same exact issues.
I have the same issue as well and if it stays on I have to turn wifi off and back on so it will connect properly
-------------------------------------
Sent via the XDA Tapatalk App
same issue here. i had been looking for an app that would force the connectivity, but the market doesn't seem to have it. just a bunch of crappy wifi on/off switcher management apps. i'm surprised that no one has hacked this function or built an app for it.
It's certainly a very annoying problem. Mine will go to known good wifi networks, at work, at home and at other locations where my other devices work flawlessly. I have a coworker with the exact same firmware (we updated using the same file) on a nexus one that has never seen this problem, which I find odd, but I'm fairly new to Android. It looks like a software or driver issue to me, but as I said, I'm new to Android.
My device shows the known networks as "Disabled", but I can connect manually.
Looks like it's worth me coding up an App to fix this then.
what kernel are you using? i used to have that problem but that has gone away with newer kernels. unfortunately a new problem has arisen where after being in standby for a while, wifi shows as connected but doesn't have an outside ip. wondering if its my rogers modem or not.
y2whisper said:
what kernel are you using? i used to have that problem but that has gone away with newer kernels. unfortunately a new problem has arisen where after being in standby for a while, wifi shows as connected but doesn't have an outside ip. wondering if its my rogers modem or not.
Click to expand...
Click to collapse
2.6.32.9-27220-g328f560
android-[email protected]#1
I've never tried a new kernel.. Is this something I should look into?
I'm running the same kernel.
BootsSiR said:
Looks like it's worth me coding up an App to fix this then.
Click to expand...
Click to collapse
Personally I wouldn't do any work towards writing an app to fix this since it looks to me to be an OS or driver issue that should be resolved in a future release (hopefully in very short order).
An app would really just be a band-aid, but I'm the lazy type and I can deal with using my cell ular data when I don't feel like reconnecting my wifi.
Full disclosure: I'm a crummy programmer and it takes me forever to write stuff so I'm usually less inclined to do it.
w9ndb said:
Personally I wouldn't do any work towards writing an app to fix this since it looks to me to be an OS or driver issue that should be resolved in a future release (hopefully in very short order).
An app would really just be a band-aid, but I'm the lazy type and I can deal with using my cell ular data when I don't feel like reconnecting my wifi.
Full disclosure: I'm a crummy programmer and it takes me forever to write stuff so I'm usually less inclined to do it.
Click to expand...
Click to collapse
I'd rather take the time to fix it then wait for an update that may never arrive. Always fun digging into the API anyways
That's cool. I still find it a bit troubling, though, that some devices see it and some don't, using the same firmware, on the same wireless networks.
I guess it could be a board rev. difference or an app conflict or something. ::shrugs::
I have a similar problem. I use APNdroid to keep cellular data off and use wifi, but I continually have to reconnect wifi no matter what if I am not actively using it. Defeats the purpose of push email.
I downloaded APNdroid after checking data usage and finding that with wifi on there was still significant 3G leakage. Especially confusing with wifi set to never sleep and plugged in overnight.
On the plus side, APNdroid has netted me a lot more battery life, I can almost get two days and one night. I almost never use my spare battery anymore.
Just as an additional data point, I am having the exact same issue with 2.2 FRF83 (I had been on FRF50).
It looks to me like it is simply scanning all of the time and never associating with a known network. I'm not sure why it flags them as "Disabled", however.
Have you guys tried to set the "wi-fi sleep policy" to "never"
if not, try this:
Wifi settings->menu->advanced->wifi sleep policy->Never
safeplayer22 said:
Have you guys tried to set the "wi-fi sleep policy" to "never"
if not, try this:
Wifi settings->menu->advanced->wifi sleep policy->Never
Click to expand...
Click to collapse
Yeah, it doesn't help, that was one of the first things I tried. Any time I leave and come back, the networks show as "Disabled". It's a frustrating issue in that it isn't consistant. It's 80% fail, 20% work.
I had my g1 for a year now and just now got my n1. I havent rooted it b/c of this bug. At first i couldnt listen online radio b/c as soon the display went out it would buffer the whole time. I played with the wifi router and the n1 wifi settings an managed to fix it somehow, BUT when i wake up in the morning for some od reason it lost connection and never reconnected again. So i can hear online radio with the display out but after some hours w/o online radio and just in standby it loses wifi connection and never connects again
This issue is not new. There is a thread on the google forum many pages long. Nobody hase even a clue where it could come from. Some1 on the forum said if u call support they will tell its ur routers fault.
The n1 completly ignores the sleep policy settings.
I have rooted two g1s with goldcard and still using one w/o a problem.
-------------------------------------
Sent via the XDA Tapatalk App
Zapo said:
I had my g1 for a year now and just now got my n1. I havent rooted it b/c of this bug. At first i couldnt listen online radio b/c as soon the display went out it would buffer the whole time. I played with the wifi router and the n1 wifi settings an managed to fix it somehow, BUT when i wake up in the morning for some od reason it lost connection and never reconnected again. So i can hear online radio with the display out but after some hours w/o online radio and just in standby it loses wifi connection and never connects again
This issue is not new. There is a thread on the google forum many pages long. Nobody hase even a clue where it could come from. Some1 on the forum said if u call support they will tell its ur routers fault.
The n1 completly ignores the sleep policy settings.
I have rooted two g1s with goldcard and still using one w/o a problem.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Well, I know fore a fact it's not my access point. I am a network engineer and worked on wireless systems for years and debugging these types of problems is something I'm a bit obsessive about. This stinks of a software or driver problem to me. It could potentially be a hardware revision issue since we have a N1 that works perfectly in all scanerios.
I've tested this with the following access points:
Apple Airport Extreme
Apple Airport Express
Meru
Cisco 1231
Cisco 350
Belkin pre-n
Linksys WRT54G stock
Linksys WRT54G dd-wrt (I forget the build number)
Soekris Engineering running pfSense
All exhibit the same behavior, while my control devices (Apple iPhone 3g, Apple Macbook Pro and a MyTouch 3g running Cyanogen 2.1).
I wasn't aware that this was related to rooting, I'd be more than happy to move back to a stock ROM if that solved my problem. Maybe I'll try that today if I get some time.
Could you possibly post a link to the google forum you're referencing?
I'm currently digging through the alogcat output to see if there is anything interesting in there.
This issue is worse since I upgraded to 83. I'm actually holding off to try CM6 when it comes out to see if there is any better performance there. I'm not sure if he uses updated drivers or kernel that may give better wifi performance.
Anyone else's nook have really slow/sporadic wifi? Mine seems to burst, then come to a crawl and sometimes not do anything at all. The dropbox app is basically useless as it fails to download 99% of the time. The browsers are all slow too. I have wireless N and a 16Mbit connection at home so it's not my internet. My Evo downloads and runs 100x faster than my nook, on 3G.
I'm not having any issues.
None of those issues here on home wifi or tether to Evo. Dropbox is one of my newest fav programs and hasnt stopped an in progress DL once..
I am not seeing any sort of weird "slowness", but I will say that Opera Mobile is, **by far**, the best browser for this device in terms of performance.
yeah it does the same for me. reboot it. it works well on that for while, and sometimes turning wifi off, then back on will help.
sisith said:
Anyone else's nook have really slow/sporadic wifi? Mine seems to burst, then come to a crawl and sometimes not do anything at all. The dropbox app is basically useless as it fails to download 99% of the time. The browsers are all slow too. I have wireless N and a 16Mbit connection at home so it's not my internet. My Evo downloads and runs 100x faster than my nook, on 3G.
Click to expand...
Click to collapse
Yes this happens to me, more often I would like and there are times when it just seems to stop but the wifi is at full bars (what ever they are called). I have noticed that when I check the wifi in the Nook settings the wifi will say "connected-testing", this means it is not connecting, it "sees" the signal but no data is being transfered, turning it on and off usually does the trick. When it says "connected to the internet", data is being transfered.
I too have ridiculously slow network connections. It is almost useless in some apps. But browser seems to be okay.
Can you guys that are having this issue post your Wifi settings and Router models perhaps there is a commonality on this,
Personally I have had no trouble out of mine, Using Wireless N, WPA2, off a Netgear WNDR 3400
I have been experiencing the slow wifi also. Downloading apps from Market is like 1KB/sec.
Running Nookie 0.6.7 from SD card (class 4). Using WPA2 AES.
I'm having slow wifi problems on a new Class 10 (supposedly) froyo install as well.
Not just wifi, too. It seems to go off to lala-land for a few seconds when I try to do much of anything. Scrolling and things like that still respond, but the apps themselves freeze.
Ok, so that is Two people using Froyo having the wifi problem? what rom are you other guys using?
I have not had this problem and I'm Running Rooted 1.1
Perhaps this is a issue with the Froyo build?
My nook was rooted on 1.0 and I'm running stock 2.1 android and I'm having the same problems
Sent from my ADR6300 using Tapatalk
My nook's connection is unbearably slow on my home connection, which is wireless b/g with WPA PSK. If connect anywhere else (except for a Border yesterday) it does not have this problem.
Also have the "connection testing" problem. I am returning mine to Best Buy - will advise.
ROM 1.0.1 problem not as bad
ROM 1.1.0 problem unacceptable...
Both rooted...
Yes, it's definitely only a froyo issue with me. My rooted 1.1 stock rom is zip-zip-zippy.
I've tried froyo installs four times (both the std and mod versions) on a Class 4 and a Class 10 card. All had wifi issues and general sluggishness. And yet I see people saying froyo is quick. Hmmm....
brie987 said:
Yes this happens to me, more often I would like and there are times when it just seems to stop but the wifi is at full bars (what ever they are called). I have noticed that when I check the wifi in the Nook settings the wifi will say "connected-testing", this means it is not connecting, it "sees" the signal but no data is being transfered, turning it on and off usually does the trick. When it says "connected to the internet", data is being transfered.
Click to expand...
Click to collapse
This is a hardware problem. I had the identical symptom - tried all sorts of apps (softlocker, etc...)
Just returned by exchanging my NC at Best Buy and the problems are gone. I am at 1.1 with Monster Pack 0.7.
The offending NC serial no is 2010 110 0650xxxx
The good NC serial no is 2010 110 1509xxxx
So make sure the SN of the replacement unit is higher!
I've had this problem since the day I bought my nook.
A couple of things I've found...
1) The problem is with how the nook handles wifi. My college wifi is a piece of crap, and everything has problems connecting. Nook won't/can't establish a reliable connection.
2) I have no problems with wifi using DeeperBlue's HoneyComb. Hell, HC can get a better signal than my notebook. If I can get that to install market, I'll just run that off the sdcard. Battery life seems better there too.
3) If you get internet at B&N, then it's not a hardware problem. Every Nook of any kind has the same problems that i'm having.(on this network)
a couple of solutions I found.
1) Connectify. Nook doesn't really like it, but it works better than no intertubes.
2) Reboot the wifi. It works sometimes.
3) pray?
I've been having odd wifi problems with my NC, and I'm at my end with this.
My NC is stock, unrooted v.1.1. I can boot from one of two Nookie Froyo SD cards (one with an OC kernel, another vanilla).
Quite simply, the Android side will no longer connect to the internet, Marketplace, etc. The B&N stock side does just fine.
The Android side worked briefly -- out-of-the-box, I connected it to an open network and got on the Marketplace, whereupon it locked up on me. I put it away, and didn't pick it up until yesterday, at which time I found that no matter which SD card I used, there's nothing doing on wireless networking. While Android finds and connects to open or secured networks, I can't bring up a webpage, go to email, check the Market, you name it.
I don't think this is a hardware issue given that the Stock side can get online (albeit slowly at times). What the eff is going on with my Android side? Should I start over and build up *yet another* card? What can I do to diagnose and solve this?
I'm willing to return this NC, but I don't see the point if I'm somehow doing something to "break" the wireless connectivity in installing apps and pushing files and customizing the install (and whatever else) in creating my Nookie Froyo cards.
Any tips or suggested resources are greatly appreciated!
I had the same problem with Stock, Rooted with Autonooter, and Froyo boot from sd card. I changed the settings on my router to WEP security from AES and now have no problems with it.
rancherochido said:
I had the same problem with Stock, Rooted with Autonooter, and Froyo boot from sd card. I changed the settings on my router to WEP security from AES and now have no problems with it.
Click to expand...
Click to collapse
On the unit that I exchanged, I had problems with both secured (WPA2) and unsecured (Wifi N). The exchange seemed to fix it...
Hello all
I just rooted my NC last night and I'm having two issues.
First, my NC reboots when I dont use it for a few minutes. It seems like any time I let it idle for more than 1-2 minutes it reboots itself. So far I've seen this happen in the wireless screen multiple times, but I'll be testing it on other screens today as well.
Second, I cant seem to stay connected to my home wifi network. When I rooted it last night it wouldnt connect at first, but I just toggled wifi on/off and it connected. Now I cant seem to access the internet at all. I can see and connect to my network, but the status hangs at "Connected, but no internet." I use a N router on WPA/WPA2 PSK.
I did run into a few weird things when rooting the device, which may or may not be related. The instructions on nookdevs say once you have the SD card in the device and it's then connected to your PC it should boot from the SD card with the screen off, then reboot on its own into the new boot animation. Mine never did this, (left it for about 20 minutes and the screen remained black) so I unplugged it and booted it up myself. It booted with the new animation and loaded into android and I was able to get the marketplace working. At this point the network started doing some really strange things, (dropping connection mid-stream on youtube, failing to load new tabs in market) so I did the 8 failed reboots reset and wiped the device to factory settings. From here I re-rooted it using the same steps with the same outcome. The device did not auto-boot but the root seems to have taken OK, but I have no network access just like before.
I was able to get it working for long enough to open up the market and download angry birds and a few other apps late last night, but I've been trying reboots and toggling wi-fi all day today and it still cannot connect.
Also, I am very new to Android and I can't seem to add shortcuts to applications to my home screen. How do I edit this?
I've been having issues with restarts as well. I think it has something to do with Soft Keys.
I am brand new to Android starting last night, but have been a Pre Homebrewer since July
I do use soft keys. I am unsure if that is causing the problem or not
I am going to go test the wifi issues on some public wifi hotspots today. Will report once I do
swapdotavi said:
Hello all
I just rooted my NC last night and I'm having two issues.
First, my NC reboots when I dont use it for a few minutes. It seems like any time I let it idle for more than 1-2 minutes it reboots itself. So far I've seen this happen in the wireless screen multiple times, but I'll be testing it on other screens today as well.
Second, I cant seem to stay connected to my home wifi network. When I rooted it last night it wouldnt connect at first, but I just toggled wifi on/off and it connected. Now I cant seem to access the internet at all. I can see and connect to my network, but the status hangs at "Connected, but no internet." I use a N router on WPA/WPA2 PSK.
I did run into a few weird things when rooting the device, which may or may not be related. The instructions on nookdevs say once you have the SD card in the device and it's then connected to your PC it should boot from the SD card with the screen off, then reboot on its own into the new boot animation. Mine never did this, (left it for about 20 minutes and the screen remained black) so I unplugged it and booted it up myself. It booted with the new animation and loaded into android and I was able to get the marketplace working. At this point the network started doing some really strange things, (dropping connection mid-stream on youtube, failing to load new tabs in market) so I did the 8 failed reboots reset and wiped the device to factory settings. From here I re-rooted it using the same steps with the same outcome. The device did not auto-boot but the root seems to have taken OK, but I have no network access just like before.
I was able to get it working for long enough to open up the market and download angry birds and a few other apps late last night, but I've been trying reboots and toggling wi-fi all day today and it still cannot connect.
Click to expand...
Click to collapse
Reboots: http://forum.xda-developers.com/showthread.php?t=880785
No problems using or reconnecting to wifi here. No other problems.
And I doubt this reboot problem is related to softkeys, but I'm not going to uninstall it to find out. The problem has been (greatly) reduced by changing the scaling governor from conservative to ondemand, per the thread above.
Ah perfect thank you. I will read that thread fully once I get home.
I just tested the NC's wifi at a Starbucks and had no issues at all. Everything connected on the first try and I had 0 disconnections during 15 min of testing in multiple apps. I have to assume it is specific to my network, but I am not sure what the issue would be. I already have a 360 and a laptop using that network with no problems, and even my iPhone can use it when I tell it to.
Has anyone had similar network woes? I use a DIR 615
I found on other topics / forums that people generally has problem with N routers. I've got Linksys WRVS4400n and it randomly hangs when Nook is on (it just drops everything and there's no network connectivity on any devices @ home). When I have turned off N (I left only b/g) everything seems to work normally again. I did not dump traffic that Nook generates, but N-on configuration was a problem..
I hope that will help somehow.
Thanks very much. I've updated to newer firmware and that seems to be helping. If my issue persists I'll disable N and report my findings.
My wife and I gifted each other with nook colors for christmas, so I have 2 to compare side by side.
I'll be returning mine, as it has definite wifi issues. It can connect sometimes, and I was able to get registered after a couple tries and get a couple books downloaded, but more often than not I can't connect at all and the browser rarely works.
My wife's works fine and connects without any problems at all every time.
Both connecting to the same wireless network just an old 802.11G belkin access point that I've been using for a couple years.
Well, I hate to admit it, but my wifi issues were of my own making, and they're now fixed.
I used to keep my wireless network separate and on a different subnet. Once we got playon for the wii, which connects wirelessly I had to move my wireless network to the same subnet as my desktop PC which was running the playon server.
Long story short, at some point in the past for some reason I hard coded my desktop IP address, but left that address in the DHCP scope for that subnet. My nook color happened to get that IP address, so the root cause was an IP conflict.
I deleted the lease and removed that address from the scope and then reconnected the nook to the wireless network, and now it works great.
Neither the nook nor my desktop reported the IP address conflict.
khaytsus said:
Reboots:
And I doubt this reboot problem is related to softkeys, but I'm not going to uninstall it to find out. The problem has been (greatly) reduced by changing the scaling governor from conservative to ondemand, per the thread above.
Click to expand...
Click to collapse
Can you explain what scaling governor is and how to change it? My NC reboots every so often and I'd like to give this a whirl.
eyecrispy said:
Can you explain what scaling governor is and how to change it? My NC reboots every so often and I'd like to give this a whirl.
Click to expand...
Click to collapse
The frequency scaling governor is the cpu control setting that configures a cpu with built in throttling capability to one of the power options available. In linux this is usually configured as a kernel option and can be set to ondemand, conservative, userspace, powersave or performance. In Win systems it is a configurable item in the power profile settings. Ondemand will keep the cpu throttled at the lowend until the system begins working and then it will speed up to the higher end. Userspace is usually required for apps that control the cpu like some taskbar widgets you would find in Gnome or another desktop environment. Powersave would be always run slow to conserve power. Performance would throttle the cpu at its highest level. Etc.
I'm experiencing both of these issues on my 1.0.1 nook. I downloaded spare parts and set the wifi sleep policy to never and nothing happened, I just changed my router from mixed to B-G mixed, we'll see if that helps. That being said, I also downloaded CPU Tuner and changed everything to on demand and am still experiencing reboots. Hope this info is useful for someone!
Yea, SetCPU set to ondemand has not solved my reboot issue, either. It just rebooted on me again about 10 min ago right after i put the device down. I don't seem to have the wifi dropping issue, though.
CPU Tuner has done nothing but make my wifi stop during sleep. I have all the profiles at leave unchanged or enabled. All file transfers stop during sleep now. The random reboots were a smaller issue before. I think I will undo all the changes I've made.
Just so everyone is up to speed with where I landed on these issues.
Wifi:
It was a problem with my DIR 615. A very knowledgeable poster was kind enough to offer a potential solution, which I never tested as I ended up getting a new router anyway. If you are experiancing issues and dropping N helped, you may want to read that thread and talk to aludal.
Reboots:
Still occurring, but very rarely. I see one every day or two. It was worse before I installed Set CPU and set it to "on demand." For a full list of the settings I am using in Set CPU please see the OP in this thread. It's towards the end of the OP.
Hope this helps.
I also have DIR615 and Slingplayer continually crashes my router's wifi internet connection but it works fine using my phone's wifi hotspot. Thanks for the info.
Only thing to reliably do is shut off wifi when the screen goes off.
This issue will be addressed by B&N with their 1.1 update rumored to release this month. Only 20 days possible left...
Hi all
I rooted my NC a few days back, and it's working great. I'm able to connect to and use any wifi I find, (tried 3 unique locations successfully; 2 for 15 minutes a pop, 1 for about 2 or 3 hours) except for my home wifi It works about... 30% of the time. It seems to be totally random as to when it works. I use a DIR 615 at home, running WPA/WPA2 PSK.
It's not a problem with too many devices. I've run two laptops, a wireless 360, and 2 iphones all at once with no problems. Even when I power off the 360 and laptops and put the iphones on 3G I have the same issues with the NC.
Signal strength is also not an issue.
I've had it work for between 2 and 60 minutes at home, but most of the time it reads "Connected, but no internet."
Has anyone encountered this? Or have any idea what might be causing it?
swapdotavi said:
Hi all
I rooted my NC a few days back, and it's working great. I'm able to connect to and use any wifi I find, (tried 3 unique locations successfully; 2 for 15 minutes a pop, 1 for about 2 or 3 hours) except for my home wifi It works about... 30% of the time. It seems to be totally random as to when it works. I use a DIR 615 at home, running WPA/WPA2 PSK.
It's not a problem with too many devices. I've run two laptops, a wireless 360, and 2 iphones all at once with no problems. Even when I power off the 360 and laptops and put the iphones on 3G I have the same issues with the NC.
Signal strength is also not an issue.
I've had it work for between 2 and 60 minutes at home, but most of the time it reads "Connected, but no internet."
Has anyone encountered this? Or have any idea what might be causing it?
Click to expand...
Click to collapse
I had a friend that had the same problem. He called bn support and they suggested they turn off n on the router and use b/g wireless only and it fixed his problem. I know not having n enabled maybe annoying but it was the only fix he colud find. Might be a router issue since he has the exact same router as you.
What version of the Nook Color firmware are you running? v1.0.1 has some wifi improvements, so it could potentially help.
doomstalk said:
What version of the Nook Color firmware are you running? v1.0.1 has some wifi improvements, so it could potentially help.
Click to expand...
Click to collapse
I am on 1.0. To upgrade I just do a wipe of /system and /data via an 8 failed boots reboot, then update, then reroot with autonooter for 1.01 right?
jameswei said:
I had a friend that had the same problem. He called bn support and they suggested they turn off n on the router and use b/g wireless only and it fixed his problem. I know not having n enabled maybe annoying but it was the only fix he colud find. Might be a router issue since he has the exact same router as you.
Click to expand...
Click to collapse
On the router or on the nook?
Edit: And is this for all N routers, or just mine?
I also have a DIR-615 using N with wpa2 and I have no problems. My NC is 1.0.1 rooted with Autonooter..
I can say that the NC had a very decent wireless reception...
Maybe try another channel? Does your DIR-615 have the latest firmware?
I'm sorry, forgive my ignorance; how do I change channels?
The first thought that comes to my mind is: have you checked to see if there is upgraded firmware for your router?
I had no problems with a DIR614 at my sister's or either of the netgears I have at my own home.
The ONLY time I have had problems is when I was using the ad-hox fix script- something went slightly wrong for me and the infrastructure mode wouldn't stay connected to any wifi signal for long.
My solution has been to manually switch between wpa_supplicant files.
I also have the DIR-615, hw rev B2, fw 2.25 and ended up having to run WEP & b/g only as I found that with b/g/n enabled a b device would kick n devices off.
I didn't miss having n functionality, and had to have WEP as I have several devices that do not/cannot support WPA and are b only.
Also IIRC some hw variation of the 615 had various problems. I don't recall what they were offhand but a quick web search should turn something up. I only got this as I got it for a good price and ATT IIRC rev B2 hw was supposed to be OK...
I've run into a similar situation, running dd-wrt. I noticed that when a dhcp lease is created for my nook I get connected, no internet. I delete the lease and it works again.
enfox said:
I've run into a similar situation, running dd-wrt. I noticed that when a dhcp lease is created for my nook I get connected, no internet. I delete the lease and it works again.
Click to expand...
Click to collapse
I will try this next time it craps out. It's working ATM.
cutterjohn said:
I also have the DIR-615, hw rev B2, fw 2.25 and ended up having to run WEP & b/g only as I found that with b/g/n enabled a b device would kick n devices off.
I didn't miss having n functionality, and had to have WEP as I have several devices that do not/cannot support WPA and are b only.
Also IIRC some hw variation of the 615 had various problems. I don't recall what they were offhand but a quick web search should turn something up. I only got this as I got it for a good price and ATT IIRC rev B2 hw was supposed to be OK...
Click to expand...
Click to collapse
I'd miss N for sure. I need N to stream 720p MKVs to my 360 Just in case I want to test that though, how would I go about disabling N on the DIR 615?
As a previous poster mentioned, i changed the settings on my router to b/g only and it fixed the connnectivity issues right away. I wasn't 100% keen on losing n to fix it, but it will do for now. I do get on to the wifi at my work and other places which i wouldn't be diabling n for any reason.
I am on 1.0.1 already and will try putting n back onto the router settings and see when i have some spare time.
I had "DIR-615" problems with WiFi for my Pandigital Novel. Until it just burn out. Well it was a $24.99 gamble of "open box" merchandize at Fry's 2 years ago, and it did work fine as is, just reflashed to the latest firmware. But it was before 615 become DD-WRT-able, and it didn't work for my PDN half the time anyway. So, I got me a Fry's FR-300RTR which is $29.99 rebrand of 615 (open boxes should be like around $15 or so, but there were none at the time.)
Long story short, I put DD-WRT on it, procedure is in the regular DD-WRT forum for Fry's router 95% of the way. The remaining and quite important 5% is in my blog http://fineoils.blogspot.com, enjoy.
For both PDN and Fry's routers to work stable on 802.11n, I used (it's also quite important, as I didn't find anybody else mentioned these) wireless basic settings like:
AP (don't use the "Router" unless you have another "gaming" router for $180 or so in your network(s), but then you don't need this cheapo device in the first place, right?)
NG-Mixed (I'd be working on pure N, but have couple of ancient b/g laptops, plus throaway dumb phone, I'm a cheap skate, as you can see, lol)
Full (20 MHz) (don't go for 40/20, or Turbo, or whatever if you have too many phones around -- which is usually the case today)
Auto (but the actual channel is "1", as it's less crowded in my area; so first scan your area and choose whatever you like more, 3 or 4 APs on your best channel compared to 8-10 on a default channel)
[whatever]
[whatever]
[Advanced Settings] should be left default, OFF, without mark in the box (one may spend a lot of time trying to improve something instead of reading one's nookbooks; I tried a little, had some problems, turned it OFF, and everything goes OK.
Replace all "regular" 2.4 GHz "wireless" phones in your household for the 5GHz ones, as long as you don't use BT/tethering, don't use your cell phone too close to your NC.
Use default 20db gain, it's just fine. This cheap piece starts to overheat even on default signal level, so consider voiding the warranty on your 615 or Fry's and set some heat sink like it's shown in my article. The picture shows a different router (and with some other weird mods), but you get the idea.
On less than 15% of battery charge, there might be some problems with WiFi (and I yet to see someone finding what is a default NC transmission level, and if it's 100%, I'd rather play with 20....40% instead and see what happens).
However, on a deplete battery there's lots of other things that may become dysfunctional.
Firmware did not help. Looks like I've fixed it by replacing my router. Thanks, boxing day! Using a DIR 825 now.
swapdotavi said:
Hi all
I rooted my NC a few days back, and it's working great. I'm able to connect to and use any wifi I find, (tried 3 unique locations successfully; 2 for 15 minutes a pop, 1 for about 2 or 3 hours) except for my home wifi It works about... 30% of the time. It seems to be totally random as to when it works. I use a DIR 615 at home, running WPA/WPA2 PSK.
It's not a problem with too many devices. I've run two laptops, a wireless 360, and 2 iphones all at once with no problems. Even when I power off the 360 and laptops and put the iphones on 3G I have the same issues with the NC.
Signal strength is also not an issue.
I've had it work for between 2 and 60 minutes at home, but most of the time it reads "Connected, but no internet."
Has anyone encountered this? Or have any idea what might be causing it?
Click to expand...
Click to collapse
I can confirm this.... though this was on a friend's tmobile dlink router (for uma support).
Sent from my SGH-T959 using XDA App
Look. What I proposed is using DD-WRT on DD-WRT-able D-Links. Which, in their original form (firmware), are either lower than average, or barely average routers in terms of throughput/throughput stability, stress under the load of multiple hosts/DNS/wired&wireless combinations/wireless signal attenuation, and overall QoS/load balancing, or lack of it. Then, many ISPs tend to shape traffic dynamically and drastically when observing some bursts of traffic on some ports (think P2P). D-Link devices do not like that. So no wonder they are cheapest on the market (seems like TRENDnet junk might be cheaper, but these just don't work stably even under low loads).
DD-WRT on 615 helps to alleviate many of most acute problems described above. Sure, one can decide like swapdotavi to put up extra $80...$100 and buy DIR-825 with twice RAM and 60 % faster processor, but guess what: it has a commercial version of DD-WRT as its firmware
aludal said:
Look. What I proposed is using DD-WRT on DD-WRT-able D-Links. Which, in their original form (firmware), are either lower than average, or barely average routers in terms of throughput/throughput stability, stress under the load of multiple hosts/DNS/wired&wireless combinations/wireless signal attenuation, and overall QoS/load balancing, or lack of it. Then, many ISPs tend to shape traffic dynamically and drastically when observing some bursts of traffic on some ports (think P2P). D-Link devices do not like that. So no wonder they are cheapest on the market (seems like TRENDnet junk might be cheaper, but these just don't work stably even under low loads).
DD-WRT on 615 helps to alleviate many of most acute problems described above. Sure, one can decide like swapdotavi to put up extra $80...$100 and buy DIR-825 with twice RAM and 60 % faster processor, but guess what: it has a commercial version of DD-WRT as its firmware
Click to expand...
Click to collapse
Your advice seems very applicable. I wanted to test the easy fix (firmware upgrade) first before I started deciphering your post which, honestly, went way over my head. I didnt mean to overlook your post or anything; your advice seems valuable.
By the time I found out my lazy firmware upgrade didnt work my girlfriend was so fed up with the outages I was causing by constantly rebooting and playing with the router that she dragged me out to look at boxing week sales and bought the 825 herself. I wasnt about to stop her
I was simply presented with an easier option is all.
swapdotavi said:
Your advice seems very applicable. I wanted to test the easy fix (firmware upgrade) first before I started deciphering your post which, honestly, went way over my head. I didnt mean to overlook your post or anything; your advice seems valuable.
By the time I found out my lazy firmware upgrade didnt work my girlfriend was so fed up with the outages I was causing by constantly rebooting and playing with the router that she dragged me out to look at boxing week sales and bought the 825 herself. I wasnt about to stop her
I was simply presented with an easier option is all.
Click to expand...
Click to collapse
Ever tried to reboot your GF?
Jokes aside, your brand spank new 825 should have a commercial DD-WRT distro on it, and for it to show best possible wireless performance (like in: overall throughput, load balancing, QoS, filtering of cell and other parasite interference/frequencies), you may want to look at my first post for 6 or so basic wireless parameters that I have found useful for use 2 tablets, 2 laptops, and 2 wired PCs in my household, porch, and backyard.
Sure it should work fine out of the box (unlike 615), but it takes some effort and play with a router when tuning your NookColor for predominant usage of 802.11n
If problems arise still, try to touch your router at its different outer body parts and check their temperatures. These should be mildly warm, anything hotter requres a trip to the shop for the replacement.
Not yet rooted Nook would refuse to stay connected, but dropping wireless N worked like a charm. All of the devices in the house are using G anyhow, side for a laptop, so this worked great.
aludal said:
Look. What I proposed is using DD-WRT on DD-WRT-able D-Links. Which, in their original form (firmware), are either lower than average, or barely average routers in terms of throughput/throughput stability, stress under the load of multiple hosts/DNS/wired&wireless combinations/wireless signal attenuation, and overall QoS/load balancing, or lack of it. Then, many ISPs tend to shape traffic dynamically and drastically when observing some bursts of traffic on some ports (think P2P). D-Link devices do not like that. So no wonder they are cheapest on the market (seems like TRENDnet junk might be cheaper, but these just don't work stably even under low loads).
DD-WRT on 615 helps to alleviate many of most acute problems described above. Sure, one can decide like swapdotavi to put up extra $80...$100 and buy DIR-825 with twice RAM and 60 % faster processor, but guess what: it has a commercial version of DD-WRT as its firmware
Click to expand...
Click to collapse
I have the impression that Dlink don't actually make their own hw, and possibly even their own firmware as IIRC even with the 6XX series of routers they went through SEVERAL various CPUs and fw variants in those routers. e.g. IIRC the 615 had 3 different hw variations and 3 different fw families...
Back when I got it there was no choice other than stock fw and possibly one of their betas, and at that time it was one of the better performing routers in that price range overall, or more specifically the rev B2 hw variant...
Disabling N: it's in one of the router setup pages... probably have to use the manual setup rather than their "wizard", which is what I always do anyways...
I am on my third Nook Color. First one had wifi issues and a couple of dead pixels. I even had issues installing ADB drivers on XP. Had to use Adb Wireless. 2nd one had absolutely no software issues (Wifi Connectivity was good and ADB installed easily also) but connector had issues (micro usb was a problem) and chord wouldn't go in. took it back also. The third one has wifi issues again. I have to reset my router everytime it goes to sleep. Nook is the first device that has problems connecting to my wireless network. Never before have i seen this. I tried everything (non secured, WPA, WP2, WEP). Haven't bothered rooting it as I think this is the last one i will own. I am returning it and getting my money back. I think there are small differences in each unit which cause them to behave differently. Not sure how or why that would happen. I really like the screen but looks like i am gonna wait for 2.2 before I make my mind.
Bummer for you. You should've just had them switch the cable on the second one. For some reason sometimes the cable doesn't go in, but if you try a few one of them will eventually work. I work at B&N and it is annoying but an easy fix. The device was fine.
As to your issues connecting to your WiFi, has your device been updated to official B&N version 1.0.1? This should fix any issues with connecting to a home wireless network.
I would almost bet that your first and third nooks did not have the update, and that is why they wouldn't connect properly. The second one probably had it and that was why it worked flawlessly.
I think you were a frustrated after returning the first one. The cable is an issue with all Nooks, you just have to take you time inserting it. As far as Wifi goes, the first Version connected better than 1.01. My Nook suffer a fall from six feet and is still rocking!. It is awonderfull device. I have more than a 100 apps on it already and can't even go the bathroom without it!.
Sent from my LogicPD Zoom2 using XDA App
I had the wireless problem @work but not @home. Is the SSID on your home wirless broadcast?
I updated my Nook out of the box. I'm rooted and screamer'd. It works at home, at work and all over town. At home I have wireless G and N routers, it works on both.
Being a happy Sprint customer, I'm used to crummy micro USB cables (PRO TIP: get the blackberry ones for your EV0!), be careful when inserting, and you'll be O.K.!
Hope this helps,
Joe
What exactly were your wifi problems? Mine will surf the web for a while then stops loading unless I turn wifi off then on again. Pretty frustrating. It did it with stock rom before and after the update and it still does it after rooting. I would love to figure out how to fix it.