Wifi "disconnected"- no networks "in range" - Nook Color General

My gf's rooted stock nook is on 1.1 rooted stock. The wifi is horribly unreliable. Both of us have rooted nooks on the same setup. My router is set to WEP, since this fixed the problem on mine a while back. Hers connects to the network but when it goes to sleep and tried to reconnect it says "disconnected" in the wireless page. And under Wireless Networks it shows "not in range" for all networks remembered. It's really strange to say the least. Any ideas??
Edit: Could I just flash the 1.1 .zip from XDA HERE?

Try updating to the latest firmware via Barnes and Noble. However that will revert your root, just as a warning. A rooted version will soon be available.

thechrisventura said:
Try updating to the latest firmware via Barnes and Noble. However that will revert your root, just as a warning. A rooted version will soon be available.
Click to expand...
Click to collapse
Thought about that, but losing root and consequently Fruit Ninja would result in rough waters for the time being.

Kayak83 said:
Thought about that, but losing root and consequently Fruit Ninja would result in rough waters for the time being.
Click to expand...
Click to collapse
Ahh life would be rough without Fruit Ninja. You could possibly flash the 1.1 you posted in the link. If you know the risks and are willing to take them it might be worth a shot.

thechrisventura said:
Ahh life would be rough without Fruit Ninja. You could possibly flash the 1.1 you posted in the link. If you know the risks and are willing to take them it might be worth a shot.
Click to expand...
Click to collapse
What risks? Am I not able to simply flash it over the existing setup?

Kayak83 said:
What risks? Am I not able to simply flash it over the existing setup?
Click to expand...
Click to collapse
I would just wipe cache before flashing. I just meant, as always, there is a possibility of something going wrong. Next to no chance, but you never know! Good luck!

thechrisventura said:
I would just wipe cache before flashing. I just meant, as always, there is a possibility of something going wrong. Next to no chance, but you never know! Good luck!
Click to expand...
Click to collapse
Tried it. Still the same problem. Booted my rooted stock along with hers and my wifi in immediately available. I have to go into hers to "forget" and then reconnect if I'm impatient. Both are using the same OC kernel. Hers did it with and without the kernel, btw.
Anything else to try?? Could it be a dynamic dhcp issue?

Have had some flaky wifi experiences on my Autonootered NC 1.1 as well (there are quite a few threads on flaky wifi).
I struggled with Autonootered NC 1.1, Froyo Nookie 0.6.7 and 0.6.8 (off SD card) and flaky wifi but have settled on Phiremod 6.1 (the one with Dual boot HC v4 off an SD card Class 6) and have not had any dropouts (or noticed them).
I have a theory the issue is related to wifi not coming out of sleep properly as CM based roms have 'sleep' issues so wifi doesn't stop, and hence, no issues (just battery drain).
Again, this just conjecture at the moment but I would definitely try a different SD based rom as a start (you can flash a rom straight away but you 'may' still have the issue) as this has worked for me.
Z

Related

[KERNEL] [TEST] CyanogenMod 6

A test/stock anykernel for CM6 inc is up on rom manager under the Koush section. Please test it out and let me know how it compares. I am working on tracking down some instability issues.
Having issues with built in tethering says error. Pre 9 seems to work however after toggling wifi.
Anyone else?
Used it for a day...
I'd have to say one of the biggest downfalls was that it didn't have most features within the kernel enabled. I didn't notice any immediate problems even with the stock kernel, unless what I ran into (described below) might be involved.
When trying to initially download the new kernel via ROM Manager, I was in a location where cell was -120 dBm (basically non-existent) but I had Wifi. Wifi always seemed to take forever to link up, unless I went into settings (then it'd find the AP immediately and connect). ROM Manager basically said it couldn't do anything, despite having Wifi. I don't know enough about the inner Android workings to know if that's unrelated or not.
With the new one I noticed mainly I had very few governors to work with. TBH I only spent a day with it because I couldn't stand how often I ended up having to charge it. I don't OC so that sort of thing has never been an issue - just UC
Edit -- I should mention I'm using 2.15.00.09.01 baseband and CyanogenMod-6-09202010-NIGHTLY-Inc build. Haven't tried newer dailies yet.
sucker4pa1n said:
I'd have to say one of the biggest downfalls was that it didn't have most features within the kernel enabled. I didn't notice any immediate problems even with the stock kernel, unless what I ran into (described below) might be involved.
When trying to initially download the new kernel via ROM Manager, I was in a location where cell was -120 dBm (basically non-existent) but I had Wifi. Wifi always seemed to take forever to link up, unless I went into settings (then it'd find the AP immediately and connect). ROM Manager basically said it couldn't do anything, despite having Wifi. I don't know enough about the inner Android workings to know if that's unrelated or not.
With the new one I noticed mainly I had very few governors to work with. TBH I only spent a day with it because I couldn't stand how often I ended up having to charge it. I don't OC so that sort of thing has never been an issue - just UC
Edit -- I should mention I'm using 2.15.00.09.01 baseband and CyanogenMod-6-09202010-NIGHTLY-Inc build. Haven't tried newer dailies yet.
Click to expand...
Click to collapse
2.15.00.09 radio literally KILLED my battery. I went back to 2.15.00.07 and battery life is great again. FYI.
Everything is good for me with this kernel. No issues. Flashed it last night.
dnoyeb said:
Having issues with built in tethering says error. Pre 9 seems to work however after toggling wifi.
Anyone else?
Click to expand...
Click to collapse
At the moment, I'm using Miui but wanted to note that this is the only kernel which allows Pre-9 Wifi tether to work on Miui (in my hands, King's #1 and #2 AOSP kernels gave me errors with Wifi Tether). Thanks for providing this kernel, Koush. Will give it a try with CM and see how that goes.
I had a soft reboot last night with this new kernel while I was on facebook. 0 wifi used.
Radio 2.15.00.07
Not sure if it's the kernel or just the latest nightly, but I'm loosing my data connection quite often. Otherwise, its running great.
dnoyeb said:
Having issues with built in tethering says error. Pre 9 seems to work however after toggling wifi.
Anyone else?
Click to expand...
Click to collapse
My built in wifi tethering isn't working either....sad day. I was loving how fast my phone charged
New version, number. 11 is online, testing now.
I haven't had any problems with this kernel yet even on wifi. I have also noticed decent battery life.
Droid Incredible
S-off
.77 hboot
Latest radio
Ruby Rom
mikeacela said:
I haven't had any problems with this kernel yet even on wifi. I have also noticed decent battery life.
Droid Incredible
S-off
.77 hboot
Latest radio
Ruby Rom
Click to expand...
Click to collapse
Funny, I'm running the test2 on Ruby as well. Been rock stable for 4hours. Practically a record for my phone on Ruby. Hope it makes it through the night.
Using the "test2" kernel.
Built in tethering works for me.
I'm running the 9/27 nightly.
No other issues so far.
P.S. I would love if internal memory was mounted properly in Windows.
Does anyone know if this new kernel is underclocked?
Sent from my INCREDIBLE using Tapatalk
Another question would be, does anyone know if test kernel #1 or #2 is the test kernel in rom manager?
Ty07allstar said:
Does anyone know if this new kernel is underclocked?
Sent from my INCREDIBLE using Tapatalk
Click to expand...
Click to collapse
showing up as a 245-998mhz one with compcache optional... Not that I put much credence in quadrant scores, but I'm pulling over a 1300 on that. So plenty quick.
Also does anyone know if its undervolted?
Sent from my INCREDIBLE using Tapatalk
Ty07allstar said:
Does anyone know if this new kernel is underclocked?
Sent from my INCREDIBLE using Tapatalk
Click to expand...
Click to collapse
#2 is running at default clock.
So far looking good on test#2 for me (9.26 nightly). I just had a meeting in a location where the phone has frozen up nearly every time I was running CM 6.02 or any previous build and it worked fine. If I make it out to lunch, then back home later today without a freeze I think we may have a winner. Or at least I'll have a winner...
I grabbed the test kernel on friday night via the ROM manager, am I running the latest test, or is there a new one with the same name? In other words do I have to redo it to get the test #2 I am seeing comments about?
I am running test2 and my only issue is with wifi cutting out and erroring out when running things like streaming media in the background, but no reboots. Tt just cuts out the wifi, and resumes relatively well upon turning the screen back on. For some reason the screen being off sets off a timer that cuts out the wifi after a while. I've tested this with both Pandora and Slacker. No cut outs when running over 1x CDMA (3G doesn't work in my office) except when my signal becomes nonexistant.

Unstable Wifi Connection on CM7

I'm having issues with the wifi connection having to be reset every few minutes when used. It seems to outright lose signal and can't even scan for networks until a reset. I'm on CM7 stable, using the latest OC kernel by Dalingrin. Anyone experiencing similar?
I have a similar issue.
From time to time (something like every 5 min), the connection seems ok (in the wifi pannel, it is stated as connected), but I can't access anything anymore by wifi. I have to disconnect and reconnect to my wifi router in order to make it work.
(I also use the last stable CM7... And apart from that, it's gorgeous ! )
So I'm indeed not alone in seeing this... interesting. Thanks for letting me know. As well, I agree, everything aside from the wifi works great and the tablet tweaks incorporated are nothing short of brilliant.
Mine is table with CM7 final and with Philmod 6, both with the 03/31 and 04/04 kernels.
same here - cm7 stable + 4/4 OC
just loaded up nightly 39 + 4/14/11A OC to try that combo
politiclaw said:
I'm having issues with the wifi connection having to be reset every few minutes when used. It seems to outright lose signal and can't even scan for networks until a reset. I'm on CM7 stable, using the latest OC kernel by Dalingrin. Anyone experiencing similar?
Click to expand...
Click to collapse
Is this not the same issue all over about AES? Check your router, if it's WPA2 it's AES, if it's WPA it could be AES.
CM7 and some routers have issues when AES is used, try to disable it.
installed nightly 39 + oc 4/14a no wifi issues so far
khaytsus said:
Is this not the same issue all over about AES? Check your router, if it's WPA2 it's AES, if it's WPA it could be AES.
CM7 and some routers have issues when AES is used, try to disable it.
Click to expand...
Click to collapse
Tanks : that worked for me !
FixB said:
Tanks : that worked for me !
Click to expand...
Click to collapse
You mind Starring this issue on the Cyanogen tracker? Make sure you put all the relevant information as well as your Router HW and FW. Thanks!
http://code.google.com/p/cyanogenmod/issues/detail?id=3314
I posted my remarks in a comment on the tracker.
But I'm afraid I don't know what you meant by "my Router HW and FW" ?
FixB said:
I posted my remarks in a comment on the tracker.
But I'm afraid I don't know what you meant by "my Router HW and FW" ?
Click to expand...
Click to collapse
hardware and firmware, ie brand name and model number and the version of software it's running.
animatechnica said:
installed nightly 39 + oc 4/14a no wifi issues so far
Click to expand...
Click to collapse
Can anyone else comment on this? I might just go down this route, but I'm wondering if there a few more who did similar and are seeing no wifi issue as a result.
Also, I'm surprised to see a CM7 final release with a wifi issue such as this. If it indeed is related to encryption (AES vs TKIP), that's further perplexing. While I could go about changing the settings for my router, I can't go about doing so for many others - particularly in public. As well, if I'm to tether from my N1, I'm going to do it with a password, meaning I'm to do it with AES as there isn't much choice built in.
I hate to say this as I'm impressed with the amount of work that went into (and normally always goes into) CM, but I figure it has to be said. To be fair, I'm not sure how widespread this issue may be (does it affect the version of CM7 on tablets, only?) but I'm surprised it can exist in a version of cm7 considered stable.
politiclaw said:
Can anyone else comment on this? I might just go down this route, but I'm wondering if there a few more who did similar and are seeing no wifi issue as a result.
Also, I'm surprised to see a CM7 final release with a wifi issue such as this. If it indeed is related to encryption (AES vs TKIP), that's further perplexing. While I could go about changing the settings for my router, I can't go about doing so for many others - particularly in public. As well, if I'm to tether from my N1, I'm going to do it with a password, meaning I'm to do it with AES as there isn't much choice built in.
Click to expand...
Click to collapse
I'll try 39 etc but I suspect if they made changes in that regard they would have said to retest in that logged bug.
As far as I know, I've heard reports this happens on some phones as well, not just tablets, not just the NC.
And it doesn't affect most people, in fact I'll bet it affects a minority of folks. If it affected everyone I'm sure CM7 wouldn't have released that way of course.
And yeah I'm with you, I _do not_ want to use my N1 tethered with Open encryption, but not much I can do until this is fixed.
khaytsus said:
I'll try 39 etc but I suspect if they made changes in that regard they would have said to retest in that logged bug.
As far as I know, I've heard reports this happens on some phones as well, not just tablets, not just the NC.
And it doesn't affect most people, in fact I'll bet it affects a minority of folks. If it affected everyone I'm sure CM7 wouldn't have released that way of course.
And yeah I'm with you, I _do not_ want to use my N1 tethered with Open encryption, but not much I can do until this is fixed.
Click to expand...
Click to collapse
Did you try 39 out? This issue is MIGHTY annoying for me as it is kind of hard getting a company with 39 000 employees to back away from AES on the WLAN..
Also going away from AES at home means that I cannot have my access point using 300 Mbit 802.11N which also is a real bummer.
I found this at the CM7 bugtracker, look at the final few posts there is a wifi-driver to try out.
http://code.google.com/p/cyanogenmod/issues/detail?id=3314
Also noticed there was a complete guide about pushing the file here: http://forum.xda-developers.com/showpost.php?p=11974146&postcount=22
So if CM7 on my phone works fine on wifi, that means a NC should work the same more or less, correct?
henel321 said:
Did you try 39 out? This issue is MIGHTY annoying for me as it is kind of hard getting a company with 39 000 employees to back away from AES on the WLAN..
Also going away from AES at home means that I cannot have my access point using 300 Mbit 802.11N which also is a real bummer.
I found this at the CM7 bugtracker, look at the final few posts there is a wifi-driver to try out.
http://code.google.com/p/cyanogenmod/issues/detail?id=3314
Also noticed there was a complete guide about pushing the file here: http://forum.xda-developers.com/showpost.php?p=11974146&postcount=22
Click to expand...
Click to collapse
I guess you didn't notice who posted in that bug, and posted tiwlan_drv.ko in the bug?
Anywho, for me it did help my own and work AP's, but it's still broken tethering to my phone. So it seems better but not perfect, give it a try. Just make a copy of the original tiwlan_drv.ko and push the single file from that zip up in its place and reboot.

CM7 Wifi Needs to be restarted every 3mb

Ok this is not your typical "my wifi wont connect issue"
i have tried a fios router, linksys cisco router w/ dd-wrt and linksys router stock. I first had cm7 on sd and assumed that was the issue so I flashed to emmc. It works great but the wifi stalls after about 3mb of transfer (or a couple of minutes of light usage) and i have to restart wifi with the power widget and it starts working again. EDIT: droid x and moto bravo work perfectly with these routers at the same time of the issue.
I already disabled wifi sleep policy.
I am using CM7 stable installed to emmc. its works fantastic otherwise but this is making it completely ususable for me. I dont think its a bad wifi chip since wifi was solid with HC on sd and seemed fine with stock nook 1.1.0
if i try to install an app it dies 75% through, if i try to play a youtube video it buffers 75% and then dies. it seems anything more than a simple web page lookup kills the wifi stack.
I havent had time yet to really dive in (been porting CWM to the motorola bravo in most my spare time) but hoping there is a simple fix out there, maybe i need to switch to dalgrin's kernel? but it also mentioned wifi issues and seems 2 weeks older than the kerenl supplied w/ cm7 but i am not sure.
This makes the nook completely unusable. Id rather not flash something else, it seems other people are having success w/ cm7 so I would like to work this out.
any ideeas? thanks
that sounds like possibly defective hardware honestly.... But you say it was fine on other ROMs so I dunno. I have had fewer problems on CM7 than Froyo myself. In fact CM7 has been solid with wifi. I wander around a lot with my NC and use many access points.
Do you have a logcat dump per chance?
If nothing is in the log, what is output of dmesg? Anything there that might suggest what's going on?
Also you might try checking out the command line program "wpa_cli". See if it helps you narrow down the issue. You can turn on additional debugging there.
Or, if you know how to rebuild your uRamdisk, appending "-DD" to the wpa_supplicant line in init.encore.rc would also give you more info in logcat...
One last thought-- if you are using dalingrins oc kernel, he took out a lot of debugging stuff (for speed), so if you want more info, revert to cm's stock...
swaaye said:
that sounds like possibly defective hardware honestly.... But you say it was fine on other ROMs so I dunno. I have had fewer problems on CM7 than Froyo myself. In fact CM7 has been solid with wifi. I wander around a lot with my NC and use many access points.
Click to expand...
Click to collapse
I hope its no hardware, its over 30 days old, i didnt get the extended warranty and I have a ghost armor on the screen
good to know your wifi is solid w/ cm7 and its not a general cm7 wifi issue. what encryption are you using?
bandroidx said:
I hope its no hardware, its over 30 days old, i didnt get the extended warranty and I have a ghost armor on the screen
good to know your wifi is solid w/ cm7 and its not a general cm7 wifi issue. what encryption are you using?
Click to expand...
Click to collapse
You have 1 year manufacture warranty.
Hello-
Its very unlikely to be Nook issue. I have had this issue with laptops and its always the ISP or the router.
Hope this helps.
Cheers,
mg
I had almost identical symptoms. I disabled encryption on my router and have had zero issues since.
Sent from my NookColor using Tapatalk
the same thing was happening to me and it just seemed to stop one day.. i think it was after nightly 35 or 36
Sent from my NookColor using Tapatalk
Calla969 said:
I had almost identical symptoms. I disabled encryption on my router and have had zero issues since.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Check out my thread on wifi http://forum.xda-developers.com/showthread.php?t=959823&highlight=dummies
My guess is that it's something in the wifi chip driver ir the wifi software stack. I have the identical symptom where on youtube, it stops after a few mb of download. (Note for mine it was stock NC with auto-nooter 3.0.0) The fix for mine was to set the router to 802.11 g only. So try this test:
1. set the router to 802.11 g only
2. turn off encryption
Let us know what happens.
I'm thinking that these devices have varying wifi quality.
My Nook Color is rock solid with wireless, regardless of encryption. WPA2 AES works as well as no encryption. I use my NC regularly with about 5 different access points around town. I'm using Dalingrin's 1100 MHz kernel with CM7 stable.
On the other hand I have a Motorola Droid that barely works unless I either turn off encryption or go to 802.11b! Those Droids were rather notorious for poor wifi. It does the same thing the OP mentioned - it stops transferring after a few megabytes although it says it's still connected. The wireless must be disabled and re-enabled.
It's AES, plain and simple. Turn it off on your router. if you're using WPA2, set it to WPA.
Your problems will go away. Now go to this thread, star it, and add your info please: http://code.google.com/p/cyanogenmod/issues/detail?id=3314
khaytsus said:
It's AES, plain and simple. Turn it off on your router. if you're using WPA2, set it to WPA.
Your problems will go away. Now go to this thread, star it, and add your info please: http://code.google.com/p/cyanogenmod/issues/detail?id=3314
Click to expand...
Click to collapse
Lol I was 99% sure of this. I had the same problem on 2.6.29 kernels on my dx. it magically went away on 2.6.32.
I am using AES, I was going to try to turn it off next, now I know
thanks.
Fattire, thanks, I checked wpa_cli and it just fails to find anything and the scans fail once the issue happens.
The one thing all those routers I tried had in common was AES, its the only thing I really trust. I guess i will have to setup a stub network and seperate AP for the nook color
thanks!
After setting the AP to WPA2/WPA Mode the Nook's wifi is working perfectly under CM7 (except for needing to be restarted after the screen is off when sleep policy is on but i beleive this is a common documented issue)
thanks!
I posted on the cm7 thread and hopefully they will get this fixed asap.

[Q] Cm 10.2.1 And A Linksys EA4500

Updating from CM9, I notice that the phone now loses it's authentication with the router multiple times in one day. That is, the icon changes from blue to white, and no data can pass through. It is necessary to turn wi-fi off and then back on to restore the connection.
On the premises, we also have a Motorola G, Nexus 7, Samsung Galaxy Nexus and a Nexus One. All but the GNex have no problems with this router. The GNex is still stock, so it would appear to have something to do with these older Samsung phones running 4.3. Searching Google, someone suggested forcing the phone to use the 2.4 band, and doing so with the GNex doesn't completely fix it, but it does happen less often. However, I can't find a "wi - fi frequency band" setting in CM.
So, does anyone have any idea what's going on? And is there a way to force the Captivate to use the 2.4 band?
Thanks much
gibosi said:
Updating from CM9, I notice that the phone now loses it's authentication with the router multiple times in one day. That is, the icon changes from blue to white, and no data can pass through. It is necessary to turn wi-fi off and then back on to restore the connection.
On the premises, we also have a Motorola G, Nexus 7, Samsung Galaxy Nexus and a Nexus One. All but the GNex have no problems with this router. The GNex is still stock, so it would appear to have something to do with these older Samsung phones running 4.3. Searching Google, someone suggested forcing the phone to use the 2.4 band, and doing so with the GNex doesn't completely fix it, but it does happen less often. However, I can't find a "wi - fi frequency band" setting in CM.
So, does anyone have any idea what's going on? And is there a way to force the Captivate to use the 2.4 band?
Thanks much
Click to expand...
Click to collapse
CM9 is quite old, chances are that the kernel modules don't support it.
BWolf56 said:
CM9 is quite old, chances are that the kernel modules don't support it.
Click to expand...
Click to collapse
Thanks for your reply.
Before, while running CM9, the phone would remain properly connected to the router indefinitely. This problem of losing authentication did not occur until after upgrading the Captivate to CM10.2.1
gibosi said:
Thanks for your reply.
Before, while running CM9, the phone would remain properly connected to the router indefinitely. This problem of losing authentication did not occur until after upgrading the Captivate to CM10.2.1
Click to expand...
Click to collapse
Oh misread your post.
If forgetting and re-entering the network doesn't work, try another kernel (make sure it's compatible).
BWolf56 said:
Oh misread your post.
If forgetting and re-entering the network doesn't work, try another kernel (make sure it's compatible).
Click to expand...
Click to collapse
I am willing to give this a try, but I am still pretty new at this sort of thing. While I have rooted and put Cyanogen Mod on two phones, I have never tried different kernals. Would you be able to give me a short list of 3 or 4 compatible kernals that I could try?
Thanks much!
gibosi said:
I am willing to give this a try, but I am still pretty new at this sort of thing. While I have rooted and put Cyanogen Mod on two phones, I have never tried different kernals. Would you be able to give me a short list of 3 or 4 compatible kernals that I could try?
Thanks much!
Click to expand...
Click to collapse
Just look in the Dev section and use one that matches your version (4.1, 4.2, etc).
NeatKernel seems to be popular around here.
Installed NeatKernal today so will see how it goes.
Thanks much for your help!
Installing NeatKernal didn't solve the problem, so decided to try the most recent CM 11 nightly....
After installing CM 11, the router and the phone still do not play nicely together. I contacted Linksys about this issue quite some time ago, but never received a response, so it is beginning to appear that the best solution is to simply replace the router. However, the Captivate is just a spare phone to play with, so it's not worth the extra expense and time, so will probably leave things as they are...
Cheers

[Q] WiFi Reception Issues, Nook HD+, Regardless of ROM

Hey guys. I have made a couple posts about WiFi issues in other threads, such as the CM12 development thread, and I started a thread about my WiFi issues in CM12, but haven’t gotten feedback. Anyways, I now know my WiFi woes go beyond just CM12, so I’m not trying to duplicate threads, but rather I’m making a general thread about this issue as I am desperate for help.
Some time back I started having very poor WiFi reception on my Nook HD+. What I attributed it to at the time was installing CM12. However, it’s possible this started happening prior to CM12 when I was on SlimKat or CM11. I have done some more extensive testing on this and would like to give you guys the run-down and see if you have any ideas.
For the first 1+ year I had this tablet, I ran CM10.2.1 without any issues at all, and although the WiFi reception was a little bit weaker than my other devices, it was never weak enough to cause any issues. At some point this past fall I tried out some KitKat builds, CM11 and SlimKat. I had trouble with the stability of those builds, and I can’t recall if my WiFi reception was good or bad on those, but I think it was okay. Because of the stability issues on those ROMs, when CM12 came out I hopped on that to see if it was going to be better.
My WiFi reception on CM12 was very poor. Only sometimes could I stream my video and even then it would cut off after a few minutes. I figured CM12 was the issue so I rolled back to the ‘Jamus28’ ‘Unofficial CM10.2.1 Stable w/ TabletUI + ArchiDroid Optimizations’, since CM10.2.1 ran great for me for so long. I figured that although I wouldn't be running the latest and greatest (Lollipop), at least I would have my stability and more importantly, my WiFi stability back. Apparently I was mistaken.
I am still having WiFi reception issues regardless of which ROM I am on. I have tested at areas around my apartment on the different ROMs. I’ve done most of the testing on the CM10.2.1. The WiFi signal fluctuates greatly, mostly at very very low speeds (using Speedtest app, 1-2 Mbps in some areas, but never gets above 8 or so even right next to the router). On my other devices I get 20-30 Mbps. I've had similar troubles now at my church on their network, which used to have a great connection for me, so I don't feel it's specific to my network.
I have done a ‘hard factory reset’ of my router and set it up from scratch. Last night, I couldn't even start a stream up at all. All of my ROM flashes are always clean flashes. Part of what I’m wondering is – is there something that could be sticking in my tablet files, despite doing clean flashes, that could be causing these issues? Is there any universal command or file between the different ROMs I can check on? Do I need to try a complete and utter wipe of my Internal Storage and start from scratch? Or do you think I just have a device that the hardware has gone bad on? The main apps I stream and thus have had trouble with are WatchESPN and Netflix. I've also had the troubles with YouTube.
Any input, suggestions, or tips are greatly appreciated! Please let me know if I can provide any other information to help troubleshoot. Thanks in advance.
Have you installed a WiFi Analyzer? It can be very helpful for finding both sweet spots and trouble spots.
WiFi can be a fickle beast. Interference can come from a myriad of sources. If you're sure its your HD+, it could even come down to how you hold it. Do you have big,wet hands?
wellersl said:
Have you installed a WiFi Analyzer? It can be very helpful for finding both sweet spots and trouble spots.
WiFi can be a fickle beast. Interference can come from a myriad of sources. If you're sure its your HD+, it could even come down to how you hold it. Do you have big,wet hands?
Click to expand...
Click to collapse
Yes, thank you for the tip. I've used that app and optimized my network channels for my location, but it hasn't helped out the ole Nook.
And joking aside, I've tried all sorts of locations and positions!
d9ct said:
Yes, thank you for the tip. I've used that app and optimized my network channels for my location, but it hasn't helped out the ole Nook.
And joking aside, I've tried all sorts of locations and positions!
Click to expand...
Click to collapse
As you have found out it is hard to differentiate between hardware and software but my "guess" would be software. My thinking is signal strength is not your problem as distance makes very little difference. My suggestion, and I'm sure you have thought of this, would be to go back to stock (Leapinlar has great info and instructions) and move forward into CM 10.1 or CM 10.2. You can still download the official stable from the CM site. If going back to completely stock does not help then moving on to a different tablet is the option.
Kokercey just reminded me that I once had WiFi problems with my old tablet (BNTV250). I used WiFi Fixer from the Play Store. I recall that it solved the problem, though I don't recall what exactly the problem was. Anyway, it can't hurt. And it's a lot less traumatic than restoring to stock and starting over. But that would be my next step.
Thank you both for the suggestions. I will check out that WiFi fixer when I am at home.
I had thought about and read about the benefits of going back to stock. My curiosity is, does full-wiping and going to stock OS and then back to CM have an advantage over a complete Internal Storage wipe and then going back to CM?
d9ct said:
Thank you both for the suggestions. I will check out that WiFi fixer when I am at home.
I had thought about and read about the benefits of going back to stock. My curiosity is, does full-wiping and going to stock OS and then back to CM have an advantage over a complete Internal Storage wipe and then going back to CM?
Click to expand...
Click to collapse
One of the advantages of going back to stock and wiping instead of just wiping is going to stock also resets your bootdata and recovery partitions and wiping does not. That may not make a difference in your issues, but who knows.
Sent from my BN NookHD+ using XDA Premium HD app
Thanks guys. I tried the WiFi Fixer, but it seems more geared towards issues connecting to a network. I seem to connect okay.
One clue I forgot to mention is that when I use the speedtest app, my upload speeds are faster than my download speeds 98% of the time. Usually 5-7 Mbps compared with the dismal download speeds of ~1-3 Mbps.
@leapinlar, to go back to stock, I would reference item #6 in your CWM Root Tools thread? Flash the older recovery, full wipe, and flash the stock zip? Which stock zip do you recommend for just the reason of cleaning things up? Can I use the rooted zips? Whichever one makes it easiest to get back to a newer recovery and CM is obviously what I'd be looking for.
Thank you all for the help.
d9ct said:
Thanks guys. I tried the WiFi Fixer, but it seems more geared towards issues connecting to a network. I seem to connect okay.
One clue I forgot to mention is that when I use the speedtest app, my upload speeds are faster than my download speeds 98% of the time. Usually 5-7 Mbps compared with the dismal download speeds of ~1-3 Mbps.
@leapinlar, to go back to stock, I would reference item #6 in your CWM Root Tools thread? Flash the older recovery, full wipe, and flash the stock zip? Which stock zip do you recommend for just the reason of cleaning things up? Can I use the rooted zips? Whichever one makes it easiest to get back to a newer recovery and CM is obviously what I'd be looking for.
Thank you all for the help.
Click to expand...
Click to collapse
Yes, item 6. The newest plain stock, not the rooted one. And just use the older bootable CWM SD to put the cm10s on. Don't bother with putting recovery on internal until you are ready to put the newer one on for CM11, if you get that far.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
Yes, item 6. The newest plain stock, not the rooted one. And just use the older bootable CWM SD to put the cm10s on. Don't bother with putting recovery on internal until you are ready to put the newer one on for CM11, if you get that far.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Thanks. Can you please check and/or correct my steps below?
- Make older bootable CWM card
- Boot to the bootable card recovery
- Wipe everything except external storage (will this wipe the current internal TWRP? Everything?)
- Flash stock zip
- Boot to stock?
- Reboot to the SD card CWM
- Factory reset wipe
- Flash CM10.x as normal
Will the device automatically boot to the SD card CWM and not my internal TWRP?
d9ct said:
Thanks. Can you please check and/or correct my steps below?
- Make older bootable CWM card
- Boot to the bootable card recovery
- Wipe everything except external storage (will this wipe the current internal TWRP? Everything?)
- Flash stock zip
- Boot to stock?
- Reboot to the SD card CWM
- Factory reset wipe
- Flash CM10.x as normal
Will the device automatically boot to the SD card CWM and not my internal TWRP?
Click to expand...
Click to collapse
The CWM SD should boot on its own after inserting it. If it does not then you need to remake it. After booting to the CWM SD do a factory reset with the CWM. That is the only wiping necessary. It does not remove the internal TWRP. The next step does that as part of flashing the stock zip. And yes boot to stock and set it up to test your wifi issues before moving on to CM.
Sent from my SCH-i705 using XDA Premium HD app
leapinlar said:
The CWM SD should boot on its own after inserting it. If it does not then you need to remake it. After booting to the CWM SD do a factory reset with the CWM. That is the only wiping necessary. It does not remove the internal TWRP. The next step does that as part of flashing the stock zip. And yes boot to stock and set it up to test your wifi issues before moving on to CM.
Sent from my SCH-i705 using XDA Premium HD app
Click to expand...
Click to collapse
Okay. I did the following:
- Made older bootable CWM card
- Booted to the bootable card CWM recovery
- Performed factory reset in CWM
- Flashed stock unrooted 2.2.0 zip
- Booted to stock and activated into the tablet through my WiFi network.
I've done a little testing running in the stock OS. The WiFi speeds seem to be almost identical to before this exercise (via the Speedtest app). The one difference I am noticing is in the usage of the WatchESPN app. Beforehand, a stream would start at a decent resolution (or not start at all) and then the stream would cut out and not reconnect, presumably when the signal fluctuated too low. Now on the stock OS, it is staying connected, but at a very very low resolution. So it almost seems to be more stable but a really low quality.
I don't remember exactly what the speeds used to be in the tablet's good days, because I never had a reason to study any speed tests. All I know is that anywhere around my apartment it would stream all of these apps at HD resolution with no problems. This is a bummer. Maybe it's just hardware gone bad.
d9ct said:
Thanks. Can you please check and/or correct my steps below?
- Make older bootable CWM card
- Boot to the bootable card recovery
- Wipe everything except external storage (will this wipe the current internal TWRP? Everything?)
- Flash stock zip
- Boot to stock?
- Reboot to the SD card CWM
- Factory reset wipe
- Flash CM10.x as normal
Will the device automatically boot to the SD card CWM and not my internal TWRP?
Click to expand...
Click to collapse
It sounds more like a router change if it is the same on both ROMs. Have you done anything different lately. Even connecting some other new device to the router. Other users have had issues when two devices interfere with each other. Like two HD+s on the same router.
Sent from my SCH-i705 using XDA Premium HD app
leapinlar said:
It sounds more like a router change if it is the same on both ROMs. Have you done anything different lately. Even connecting some other new device to the router. Other users have had issues when two devices interfere with each other. Like two HD+s on the same router.
Sent from my SCH-i705 using XDA Premium HD app
Click to expand...
Click to collapse
Interesting. I did get a new HP computer in December, which come to think of it could be when these problems started, but I can't say for sure. It runs on the same 2.4 GHz band that the Nook HD+ runs on. Some time before that my wife and I both changed phones. We almost always have the phones on my 5 GHz band. Other than that I have a laptop and Kindle Fire that we've had for a very long time.
Last weekend I did a factory reset of the router due to issues I was having with my phone connecting on Lollipop. I set it back up the same as it was prior. After doing the reset my phone was able to connect again. As noted above, it runs on the 5 GHz. Prior to last weekend the router had been the same for quite some time, certainly well before the tablet WiFi issue.
Perhaps try some testing with the new laptop shut down?
Edit: I did get a new router some time back, but I feel it was surely before these troubles, maybe last summer or so. Let's say it wasn't... how would I test this?
d9ct said:
Interesting. I did get a new HP computer in December, which come to think of it could be when these problems started, but I can't say for sure. It runs on the same 2.4 GHz band that the Nook HD+ runs on. Some time before that my wife and I both changed phones. We almost always have the phones on my 5 GHz band. Other than that I have a laptop and Kindle Fire that we've had for a very long time.
Last weekend I did a factory reset of the router due to issues I was having with my phone connecting on Lollipop. I set it back up the same as it was prior. After doing the reset my phone was able to connect again. As noted above, it runs on the 5 GHz. Prior to last weekend the router had been the same for quite some time, certainly well before the tablet WiFi issue.
Perhaps try some testing with the new laptop shut down?
Edit: I did get a new router some time back, but I feel it was surely before these troubles, maybe last summer or so. Let's say it wasn't... how would I test this?
Click to expand...
Click to collapse
To eliminate potential interference from other devices temporarily disconnect everything from the router except the Nook. Bluetooth could also be an issue. It runs on the 2.4GHz band too. As I remember the earlier issue was when an HD+ and an HD both connected the HD+ (and other devices) slowed way down. There was a software problem with the HD which got fixed eventually.
Sent from my BN NookHD+ using XDA Premium HD app
Your quickest path is to simply turn them all off and test only with what's needed for the nook, which is wifi router/modem and the nook. Unplug the house phones, turn off computers, forget the wifi on the mobiles/tablets, airplane mode, or similar. etc.
One other thing I will point out is that testing max wifi speed over internet isn't the best idea as the results are less guaranteed.. The internet is out of your hands and devices are recognized and delt with on that end as well. Using btsync (http://www.getsync.com/ , https://play.google.com/store/apps/details?id=com.bittorrent.sync&hl=en) and transferring locally a large file (few hunderd MBs or so) from your dektop/laptop to the device though the wifi router/modem (the desktop/laptop should be wired to the router for troubleshooting here) will be able to max out the wifi connection and it shows the transfer speed. Unfortunately, simple ways such es file explorer or similar cannot do so. Transferring small files though btsync also shouldn't max it out as that creates a bottleneck.
The best these things can do is just over 4MBps.
Okay guys, thank you for the help, I do appreciate it. I did a little more testing. I turned off everything I have and just ran the Nook on the modem and router. Unfortunately I didn't notice an improvement in the speeds doing my poor-mans tests (speedtest app and streaming). Similar to yesterday I am able to stream a decent-to-good quality in the immediate proximity of the router, but a low quality further away. I then whipped up the WiFi Analyzer again and decided to try a different channel, but I am still having similar results.
I have not tried the Sync app yet, but thank you for that suggestion, perhaps I will give it a try. Is 4 MBps really all these devices can do? That sure seems low, but I guess I don't know what is typical for a tablet...
I would like to point out clearly that I am in an apartment building. There are a LOT of surrounding networks and devices. However, I've been here for more than two years now and it wasn't an issue prior to these last however many months. Is it possible I have a new neighbor with some new device(s) that are causing additional interference, perhaps?
A side question I have, and maybe it should go in a new thread, is that I've tried a few times to bluetooth tether the Nook to my phone and use the phone's WiFi for the Nook, but when I get to the step of actually selecting to use the phone for WiFi, the Nook wouldn't allow me to select/activate. I would just press and nothing would happen. This was happening on CM; I haven't tried today as I still have it on the Stock OS. Any idea why that wouldn't work on CM?
d9ct said:
but a low quality further away. I then whipped up the WiFi Analyzer again and decided to try a different channel, but I am still having similar results.
Click to expand...
Click to collapse
With wifi analyzer if your wifi is -30 your in great shape with signal strength which one less bar may occur in the -50 range. And if it shows your wifi is on a good channel then its not going to do much for you.
d9ct said:
Is 4 MBps really all these devices can do? That sure seems low, but I guess I don't know what is typical for a tablet...
Click to expand...
Click to collapse
It is for the nooks. 65 link speed is absolute max.
d9ct said:
Is it possible I have a new neighbor with some new device(s) that are causing additional interference, perhaps?
Click to expand...
Click to collapse
I assume you have a mimo router (multiple antennas) and dual band as well in which case the nooks can't take advantage of that and interference could be more of an issue. But, if you have a cheap end HP laptop it may have the same basic wifi as the nooks - if you look at the connection info in the nook wifi settings and the connection info on the HP networking and they both show 65 link speed that would help confirm the nook is indeed having a problem with something (ignoring any possible differences between internal antenna design). (It looks like HP laptops MSRP above $1k get various combinations of dual band, dual antenna, ac wifi.)
sandsofmyst said:
With wifi analyzer if your wifi is -30 your in great shape with signal strength which one less bar may occur in the -50 range. And if it shows your wifi is on a good channel then its not going to do much for you.
It is for the nooks. 65 link speed is absolute max.
I assume you have a mimo router (multiple antennas) and dual band as well in which case the nooks can't take advantage of that and interference could be more of an issue. But, if you have a cheap end HP laptop it may have the same basic wifi as the nooks - if you look at the connection info in the nook wifi settings and the connection info on the HP networking and they both show 65 link speed that would help confirm the nook is indeed having a problem with something (ignoring any possible differences between internal antenna design). (It looks like HP laptops MSRP above $1k get various combinations of dual band, dual antenna, ac wifi.)
Click to expand...
Click to collapse
I will check this evening what type of signal strength it was. It is a low end HP laptop and it only runs the 2.4 GHz band so it sounds like what you're talking about. I can check on the device info this evening. However, I had it off yesterday when testing around again and I don't think I noticed much of a difference. Last night I watched a little more streaming and it's possible it was slightly better quality for longer periods, but I can't say for sure.
sandsofmyst said:
With wifi analyzer if your wifi is -30 your in great shape with signal strength which one less bar may occur in the -50 range. And if it shows your wifi is on a good channel then its not going to do much for you.
It is for the nooks. 65 link speed is absolute max.
I assume you have a mimo router (multiple antennas) and dual band as well in which case the nooks can't take advantage of that and interference could be more of an issue. But, if you have a cheap end HP laptop it may have the same basic wifi as the nooks - if you look at the connection info in the nook wifi settings and the connection info on the HP networking and they both show 65 link speed that would help confirm the nook is indeed having a problem with something (ignoring any possible differences between internal antenna design). (It looks like HP laptops MSRP above $1k get various combinations of dual band, dual antenna, ac wifi.)
Click to expand...
Click to collapse
Hey guys, I had some very busy weeks of work and then a vacation and then some more busyness. I haven't had any improvement in the tablet WiFi in that time. I did some testing today using the BT Sync software. Let me note a few more things first:
- I checked the Link Speed on my Nook HD+ and it mostly read 54 or 72 mbps. I never saw it at 65. I actually saw it go down to 1 a few times but then back to 54 or 72.
- I checked the Link Speed on my HP Laptop and it read 72 mbps, again I never saw 65; it stays steady at 72.
I've done some more using of the tablet around the HP laptop and it doesn't seem to have an effect that I can tell whether the HP is off or on.
FYI I have a Netgear N300 router.
My WiFi analyzer app shows that with my Nook literally within one foot of my router my signal strength gets no stronger than -50. Nowhere near -30 ever. In my further rooms from the router it drops to -60 to -70.
I did the testing using BT Sync you recommended. I connected my other laptop directly to the router and disabled it's wireless as well as the wireless on the HP laptop. I installed Sync on both the laptop and my Nook. I transferred (actually it's still attempting to transfer) a folder with several files, the main one being around 200 megs which it has been chugging away on. With all the other devices off this transfer topped out around 350 KB/s. More consistently it has been around 200 - 250 KB/s.
Edit: Let me know if you think I'm using the Sync app incorrectly to have that slow of speeds. However it doesn't seem far fetched to me based on my performance I have at times (browsing, app installs, etc.)
I hope this provides some more clues for you guys, I'll add a post if I think of anything else. I appreciate all continuing suggestions. Thank you for your help thus far.

Categories

Resources