Related
My own experiences were as follows (on a wide variety of routers, both G and N, running anything from stock Linksys/Cisco to Tomato and DD-WRT, using no encryption or WPA2/AES):
- ALL stable CM7 releases: Completely unreliable. Would connect initially, maintain communication for maybe 1-2 minutes at best, then lose connectivity (although the icon would remain green)
- Beta 3.1: For the first time, WiFi was rock solid. Worked absolutely flawlessly.
- n86: WiFi broke again, in much the same (apparent) way as stable.
It would seem those with WiFi problems (all of us?) fall into one of two categories - those for whom WiFi worked great with the .32 kernel until n86 (that would be me, and from what I've read, several others), and those for whom WiFi *never* worked properly on .32 _until_ n86, who now work flawlessly.
Is this a reasonable assumption? If so, I would guess this change:
Don't renew the leases if mDhcpInfo.leaseDuration is not positive
actually made things better for some and worse for others.
Anyone else with thoughts on this? The inability to maintain connection long enough to even copy a few hundred meg video over Samba is frustrating to no end - especially when, for a brief but glorious time, it was perfect!
Rodney
I own two NC and one is on n86 and the other is running Phiremod 6.3 which is Cm7 based with zero wifi issues
I've seen one WiFi issue:
My WiFi graphic indicator would show only the lowest signal strength. I have no idea if the signal is that bad, or it's just a bug.
I've not seen any disconnect issues.
In fact, my Nook Color has been more reliable with WiFi than my iPad 2!
I've connected to public WiFi, WiFi routers running stock Netgear, Tomato, DD-WRT, etc. No issues.
I've mostly ran the CM7 nightlies. I've used a little of Phiremod and Stock, but by far the nightlies.
I have this problem currently on both of my nooks running n87. its been happening for me since .32. weird thing is, it only seems to happen on my wifi, when i go to work and connect its all fine, or if i steal my neighbors wifi its fine too. but if i connect to my home wifi, it connects for 1-2 mins, then disconnects me but still shows that im connected. i even replaced my netgear router on stock firmware(i did try updating it) to a linksys that im currently using dd-wrt on and its still happening.
Have you tried N86+ with the OC Kernel and WiFi update?
Homer
What is this "wifi update" you speak of?
WEP works every time for me. Anything WPA protected is hit or miss.
I have a NC running CM-N86 and no WiFi issues.
Also, I my coworker's NC running CM-N87 doesn't have any WiFi issues either...
1) I have been running CM7 since it has been available. I have not once seen problems with WIFI. At home I have a linksys WRT54G router running DD-WRT using WPA2.
2) you posted in the wrong area. This should be in the CM7 user thread or the general forum area.
mr_fosi said:
What is this "wifi update" you speak of?
Click to expand...
Click to collapse
i wasnt aware of a wifi update >.>
CM7 Nightly - NO issues with Wi-Fi. Use it everywhere Wi-Fi is available...
i actually only have issues when i'm connecting to wpa2 enterprise. after disconnecting and trying to reconnect, the credentials no longer work. i have to delete and recreate it every time.
i'm running nightly 87 w/ oc kernel on emmc.
No wifi issues here either. No matter what I connect to.
Also... this should be in general... not dev section...
Sent from my HTC Glacier using XDA App
mr_fosi said:
What is this "wifi update" you speak of?
Click to expand...
Click to collapse
How about here. You must push the system folder contents or flash.
Homer
Homer_S_xda said:
How about here. You must push the system folder contents or flash.
Homer
Click to expand...
Click to collapse
thats not a wifi update, its the OC kernel. and at the very least my issue occurs wether i have the oc kernel installed or not
Homer_S_xda said:
How about here.
Click to expand...
Click to collapse
Yeah, I'm running 5/23 and I still have wifi issues on my home router (D-Link with WPA2-PSK).
Oh well.
re: general vs. dev...I respectfully disagree. I submit there _was_ a change in behavior, in the negative, for some users beginning with n86...and that is most definitely a -development- concern.
Rodney
The issue relies in the type of security and if you are using Aes or tkip. I have confirm this changing my router settings. The problem is that if I get my setting for the nook, tgen I have to reboot the router almost daily for my phone to connect.
I'm on nightly-87, Dal's 1.2GHz OC Kernel 5/23, and I'm experiencing something very similar. I went from 7.0.2 to N87 without a hitch, but I immediately started to see the WiFi icon go gray and lose it's connection. I was forced to restart WiFi as a remedy. As of today I'm getting something closer to what you're talking about; when WiFi turns on, the nook will infinity cycle through: disconnected->connecting->disconnecting->scanning. I've wiped Cache, Delvik-cache many times to no avail. Also tried re-flashing N87 and the OC Kernel, which did not work. I'm still not able to connect to my home network(netgear, WPA). But, after enabling/disabling airplane mode, I was able to connect to my LG vortex and obtain the interbuttz.
The last time I did a fresh install was around N20 something. As far as possible causes to this erratic and ethereal bug, my money is on certain update paths for both the OS and Kernel having different remnants. Example: with 87 different experimental OS installs and, to a lesser degree, the three different stable OS installs. There are technically !90 different upgrade paths. Compounded by being paralleled by kernel installs, but I believe when a kernel is updated the former is completely replaced instead of merged. I'm not calling out the Dev's, it would be nearly impossible to foresee and head-off all of the permutations of merging 87+ releases.
I'm no expert, just my two-cents. I'm not really concerned about this as a long term bug. There are fine people hard at work, and unfortunately have far more pressing issues to contend with. It's a sad reality that community driven projects, notably the nook Color, rarely reach maturity or complete/efficient hardware-software integration before the allure and newness of a product wares off.
As a consumer of .rockbox, a Linux based OS for G5.5 ipods and below, Of which I've been using for years and years. And, I would say it's just now becoming 'perfect', even with it's lack of support for many peripheral devices. I'm long term with my gadgets.
I'm rambling now.
Hope this helps to narrow down symptoms and possible causes.
I love spending time on a post, just to realize after it was posted that I was typing in the wrong thread reply tab. Oh well. Que Sera, Sera.
I have the reverse experience of the OP.
I never had any problems with Wifi ever, until the .32 test builds, when Wifi would stop without notice, requiring a disconnect/connect. This caused me to go back to a .29 stable.
Perhaps what the OP is suggesting is that the change, that was reversed, should be a toggle/option, rather than changed and then changed back.
I just got the thing and it came with GSB3.6 and it had SO many problems i put 3.7 on there and most where fixed, but my wifi disconnects every 15 seconds or so. any known fixes?
EDIT: Tried OMFGB, Same problem. i hope its fixable. someone help meeee
Check Settings, Wireless & networks, Wi-Fi settings, then tap Menu and Advanced. Change the 'sleep' policy (try "Never") and see if it continues disconnecting.
I would like to think that the default setting, "When screen turns off" does not kick in when there's an active connection...
I've used GSB v3.7 (Odex) with my WiFi without any problems.
Based on the fact that you observe the same symptoms with two different dev ROMs, I would suspect that the problem is either (a) your WiFi hardware, (b) your WiFi router, or (c) a software incompatibility between your WiFi router and the Eris' device driver (very similar from ROM to ROM).
You could try installing a completely stock ROM, for instance the
[ROM] HTC Eris March 2011 OTA Stock ROM - v2.41.605.6
(Note that although this ROM is "completely stock" and "not rooted", flashing it does not touch your recovery boot, so you treat it just like any other dev ROM).
Running this test - if you still experience the problem - will exonerate any Eris dev ROM, and you have a couple of options at that point:
- see if your WiFi router has a firmware update available (router firmwares contain bugs, too). I have experienced incompatibilities with the Eris which were solved by flashing WiFi routers to newer firmware.
If you try that and you still experience problems, you actually still won't know if the problem is (a) or (b) - but if you take your phone to a Starbucks or other place with a WiFi hotspot available, and you still experience problems of the same nature, then it is time to suspect that the problem is "(a)" - hardware trouble with your handset.
good luck
bftb0
I switched the router from duel band N to single channel G, and now i only disconnect every 45 minutes or so.
also i tried swapping routers to a diff one, and then my dads DX, his wifes Droid, nor my Eris, could connect at all, under any settings. so it seems Android has alot of issues with wifi? anyways, i still disconnect, but not enough to bother me. thanks for the replies!
as much as it might suck, you should try doing a full wipe of data/dalvik and see if it fixes the issue. i had gone from 2.4 or so up to 3.7 without doing a wipe, and eventually things started to happen (widgets would not show up for new programs). i did a full wipe and everything is working great now.
I also am having wifi issues, didn't have them til I put the gingerbread cyanogen rom on.
I will do some more trouble shooting today and see if I can narrow down some of the variables. I have a Buffalo router with WPA2 for security on it. Some have suggested the security, but then I've talked to others that have WPA2 set up and no problems.
The wifi was working previously, did a full wipe of data and dalvik when I installed. I am running 3.2 or something close to that, haven't upgraded to the most recent version yet.
SO. Theres my info. But I love the rom and won't get rid of it, even if it is the rom.
My husband is fine just running 3G.
i have a linksys wrt54g running ddwrt using wpa2 with no problems, gsb 3.7 on my eris.
Bunie89 said:
I switched the router from duel band N to single channel G, and now i only disconnect every 45 minutes or so.
also i tried swapping routers to a diff one, and then my dads DX, his wifes Droid, nor my Eris, could connect at all, under any settings. so it seems Android has alot of issues with wifi? anyways, i still disconnect, but not enough to bother me. thanks for the replies!
Click to expand...
Click to collapse
In general, WiFi compatibility from clients to APs is far worse than most people expect; I've experienced interop problems with all sorts of gear. It is hard to draw general conclusions, as the results you get are highly dependant on specific hardware models & firmware versions.
About the only generality that can be stated is this: the more bells and whistles you enable on the AP, the more likely it is you will experience a problem.
FWIW, my GSB 3.7 Odex Eris seems to work flawlessly with a Linksys WRT54G with WPA2. I think I have multiband (A/B/G) turned off in favor of G-only.
cheers
Bunie89 said:
so it seems Android has alot of issues with wifi?
Click to expand...
Click to collapse
I certainly wouldn't say that.
hallstevenson said:
I certainly wouldn't say that.
Click to expand...
Click to collapse
Yeah I wouldn't say that either. I've had my Inc for a year, never had any problems with it, and like I said before this rom, no problems with wifi.
I also have an android tablet. No problems with stock.
So clean install with 3.7, did data wipe and cache, first thing I did was try to get wifi going, all it does is scan. Entered my SSID and everything. Says it's not in range. Bah.
I need some assistance trying to narrow down what is causing my issue. I posted this in the TMobile SGS3 Q&A section but I wanted to post here to get more exposure and perhaps someone more knowledgeable can chime in. I believed this to be a AOSP JB kernel issue but I also tried CM9 on my phone and the problem persists.
For some reason my phone will randomly disconnect from my WiFi connection when running an AOSP rom. The actual WiFi service will remain on; I can see available networks but it will not reconnect to my saved AP unless I toggle WiFi off/on, and even then it will randomly disconnect again. The same thing happens with CM, and ALL CM-based roms. I have tried Faux, Imoseyon, Trinity, stock, and Ktoonsez kernels and none seemed to fix this issue.
Stock TW roms, both ICS and JB, keep my connection just fine. I also used the same CM nightly build on my GS3 and my Galaxy Nexus for testing purposes. The GS3 will lose connection while the GNex does not, so I figured it had something to do with the kernel since those are usually phone-specific.
As for the WiFi signal, I don't have any issues neither at work nor at home with TW-based roms. This only happens on AOSP. Any insight you guys have regarding this issue is appreciated. Thanks!
I ran a logcat but to be honest, I do not know what to make of it. would anyone happen to understand where my issue is?
Link to original thread
Infamous_Cheez said:
I need some assistance trying to narrow down what is causing my issue. I posted this in the TMobile SGS3 Q&A section but I wanted to post here to get more exposure and perhaps someone more knowledgeable can chime in. I believed this to be a AOSP JB kernel issue but I also tried CM9 on my phone and the problem persists.
For some reason my phone will randomly disconnect from my WiFi connection when running an AOSP rom. The actual WiFi service will remain on; I can see available networks but it will not reconnect to my saved AP unless I toggle WiFi off/on, and even then it will randomly disconnect again. The same thing happens with CM, and ALL CM-based roms. I have tried Faux, Imoseyon, Trinity, stock, and Ktoonsez kernels and none seemed to fix this issue.
Stock TW roms, both ICS and JB, keep my connection just fine. I also used the same CM nightly build on my GS3 and my Galaxy Nexus for testing purposes. The GS3 will lose connection while the GNex does not, so I figured it had something to do with the kernel since those are usually phone-specific.
As for the WiFi signal, I don't have any issues neither at work nor at home with TW-based roms. This only happens on AOSP. Any insight you guys have regarding this issue is appreciated. Thanks!
I ran a logcat but to be honest, I do not know what to make of it. would anyone happen to understand where my issue is?
Link to original thread
Click to expand...
Click to collapse
Are you using any kind of signal extender or an acess point? I've seen similar problems with android getting confused on wich point they need to connect, if the answer is yes try to turn off the extender before connecting to see if that's what's causing the issue. Unfortunatelly I don't have simple steps to solve this, it's all trial and error, turn off the devices individually and start connecting until you get an order that suits your phone.
Hope it helps!
Thanks for the input. I don't use either of those. The phone connects directly to the router. The router sits in the same room so signal is always strong and no other devices connected to the router have any issues. This is definitely a bummer because I would love to run AOSP as my daily driver. I will keep troubleshooting.
Sent from my SGH-T999 using Tapatalk 2
I've been having this issue since I first flashed a LiquidSmooth ROM a couple months back, but as I've installed official CM10.1 and AOKP roms, the issue has persisted across them. Currently I have Avatar 2.13b on slot 1, AOSP r6 on slot 2 and LiquidSmooth 2.4 in slot 3 and the problem exists on all 3. Bluetooth will work fine on an initial flash, but a some point later on, it disables itself, and the only way to get it back is to wipe dalvik and reboot. Is this simply an instability of the kexec kernel, or something more. I've seen a few posts related to this, but not enough that it seems like a common issue. Any one else having this problem or any thoughts on why its happening to my RAZR MAXX xt912? Wiping dalvik isn't a huge inconvenience, as I typically only use BT to and from work, but after a long day in the office, not being able to connect my headphones can just add to my frustrations. Any thoughts or help is greatly appreciated, thanks in advance!
Did you ever make any progress on this problem? I'm having a similar, tho not identical, BT problem . . . posted it, hoping to get some idea how to approach it. Thanks
Sorry, no luck yet. Happened today while sitting idle at my desk, no reboot, not even being used. If I run into a solution on another site, I'll update this post
Posted from along the edge of a straight Razr
psudeke said:
Sorry, no luck yet. Happened today while sitting idle at my desk, no reboot, not even being used. If I run into a solution on another site, I'll update this post
Posted from along the edge of a straight Razr
Click to expand...
Click to collapse
Too bad. I was hoping to piggyback, or at least get some insight.
I like to think I'm not an idiot, but short of changing hardware I can't think of anything new to even try.
I would have posted this in CDMA dev, but I don't have enough posts yet. First, ROMS like dastin's CM11 ROM usually list "Standard CM11 Issues" under issues. However, I've never been able to find a comprehensive list of "standard" issues for CM release since CM only has wiki entries for supported phones (which does not include CDMA 3D/V 4G). I'm running Angrybean CM10.1/AOSP/AOKP, and only vaguely knew "standard" CM10.1 issue for this phone usually meant no MMS. I only discovered that issue by happening upon a thread post skimming through a lot of threads. So, is there a place where "standard" issues gets documented, or is this one of those "if you read a lot of posts in this forum, you'll understand what 'standard' is"?
Also, ever since Gmaps 7 came out, I've had flickering/glitching/screen tearing issues that some people seem to have. I've tried a lot of the recommended fixes, which usually include disabling HW overlays, forcing GPU rendering, reinstalling, or downgrading to Gmaps 6 (not a solution in my eyes). Just wondering if anyone has found a definitive answer as to why this happens, and what the solution is, because I see the same issue has popped up in dastin's CM11 ROM. I'd love to flash CM11, but the flickering is driving me crazy.
Thanks for any info or help you can give me.