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.
Related
Cross-posting this from the CM7 nightly thread since it also helped someone else. If this hasn't been posted before, I hope it is helpful.
Just wanted to drop in with something I noticed regarding the wifi looping bug. I upgraded from 30 to 31 and started getting the issue out of nowhere. The wifi would just constantly loop between connecting/seeking/disconnected. Tried a bunch of things with no results, decided to go for a full wipe, installed Phiremod 5.1 from the XDA forums with the new Dalingrin's kernel (1.1 OC version released 25th March), but when I rebooted the issue was still there.
I honestly don't know much about networking, but I also noticed that I was having to hard reboot the router sometimes because the wifi would appear connected but not actually do anything. After a bit of messing around, it seems that both issues were resolved by simply disabling UPnP on my router. I have no idea if the problem was caused by it being a crap router (it is), or the way the Nook is connecting to it, but I thought it might help out some other people having the issue.
The router for the sake of reference is an old Netgear WGR614v7 cable router.
Sorry if this has been posted before. I just wanted to add that apart from this small issue, the nightlies have been pretty fantastic. The Nook is a week old and my first venture into Android. The CM7 and XDA communities are pretty excellent. Thank you everyone for all your work.
Click to expand...
Click to collapse
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.
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
I bought the Nexus 6 (blue, 64gb) the day one, in November and since that day I noticed random reboots in a particular situation. When I switch to a WiFi network to another it shuts down and so I have to turn it on. When it turns on I have lost all my WiFi networks configurations, so passwords, dhcp settings, etc.
Random reboots rarely happen also in camera/gallery apps.
I tried to send it back to google and I received a new nexus. The first one was produced in June 2014, the new one in December 2014. The issue is still there. [emoji17] I've also tried to update to 5.1 but no resolution.
I have rooted, installed twrp, decrypted both my nexus 6 with toolkit.
How can I solve the problem? I was very happy with this phone.
Try using it completely stock and see what happens. I'd say chances are that if you set both up the same, it's something you're doing and not the hardware on 2 different phones.
But other people have made the same basic mods on their nexus and their phone has not this kind of issue.
Is it every network? Maybe try a stable custom ROM to see if it happens there too. Could be a problem with specific networks or even apps. Troubleshooting is the key. First try full wipe, no restored Apps.
I could be as simple as an app the developer has not updated since gingerbread or something stupid like that.
Is there a way to find the malicious app?
There definitely *was* a bug causing loss of wifi networks, and I think there may also have been a reboot involved there (not sure if we rebooted it manually, or if it just did it on its own as a response to a wpa_supplicant crash...). It was across the board for Android 5.0 though, not limited to Nexus 6. I saw my wife's Nexus 5 do it once. Never actually had it happen on my 6.
I'm not sure if this bug was fixed or not, since it wasn't something we tried to reproduce, and only happened once. The bug is definitely related to wpa_supplicant, since that is the only program that actually interacts with its configuration file (which is where the wifi configurations are actually stored).
As far as galleries go, you're not giving much to guess by. I certainly haven't seen galleries cause reboots like that. Maybe you are using a bad one?
Try this gallery; https://github.com/lbdroid/Android-Binaries/blob/master/Gallery2.apk
That is the actual AOSP gallery, modified to install as a standalone application. The source code is in another repository on my github.
*note: it will not do you any good at all to swap out your phone, since there is no indication that you are experiencing a hardware issue.
But why other people doesn't experience this problem that is related to WiFi? All people use WiFi and every time. Is there a way to fix the WPA_supplicant issue? Maybe a custom ROM?
My first n6 had also an hw issue, I think, because before it rebooted it gave me some little "buzz" from the top speaker.
mouse100 said:
But why other people doesn't experience this problem that is related to WiFi? All people use WiFi and every time. Is there a way to fix the WPA_supplicant issue? Maybe a custom ROM?
My first n6 had also an hw issue, I think, because before it rebooted it gave me some little "buzz" from the top speaker.
Click to expand...
Click to collapse
all people use WiFi is an incorrect statement. you can say most ppl use wifi, but all would never happen. I hate using WiFi and NEVER use it except when its absolutely necessary. ive probably used WiFi 2 times on my n6 since getting my n6 in November, and there's no WiFi issues here.
mouse100 said:
Is there a way to find the malicious app?
Click to expand...
Click to collapse
Yes, start with stock and install a few apps at a time until you get the problem. Given the fact that you have 2 different phones experiencing the same problem, it is much more likely that it is something software related rather than hardware (though I suppose it could be possible if you're really unlucky ).
mouse100 said:
But why other people doesn't experience this problem that is related to WiFi? All people use WiFi and every time. Is there a way to fix the WPA_supplicant issue? Maybe a custom ROM?
Click to expand...
Click to collapse
You said that it happens when you change from one wifi network to another. Most people don't do that. Most people have one wifi network at a time and don't change it.
There is also a huge difference between wifi network configurations... A/B/N/AC, frequency, bandwidth, multiple-bands, encryptions, etc.
My first n6 had also an hw issue, I think, because before it rebooted it gave me some little "buzz" from the top speaker.
Click to expand...
Click to collapse
Normal.
Wiped and flash modified boot from ChainFire + factory image.
PEAP WiFi does not seem to work. Always on 'Connecting' and eventually 'Authentication Error'. Credentials used were correct and is working on my N6 previously.
not sure what is the problem. Tried removing the 'pmf=1' from /data/misc/wifi/wpa_supplicant.conf but it is not working.
Anyone has any idea what might be the problem?
I haven't been able to connect to the 2.4 ghz network in my office since I flashed the M factory image. It uses 802.1x authentication. The 5 ghz band seems to be unaffected.
same thing happened on my N5. probably gonna revert my n6 back to L and stay there till there is a fix.
There is a google tracking thread for this issue. Please let Google know: https://code.google.com/p/android/issues/detail?id=188867
It looks like this issue is very similar to what happened with iOS9 beta deployments. Our office upgraded our Linux radius machines to support TLS 1.2 when that occurred and it didn't fix the issue. Then, another version of iOS 9 ended up fixing the issue. Hopefully enough people can push Google to put out a fix.
No, it's definitely a bug with the RADIUS server, see comments 29 and 37.
I wanted to bump this and not make my own thread since I found it via search.
I contacted my school's IT department to see if they can do anything about the RADIUS server, but it looks like that they'll probably not do anything about it.
Can I do anything on my end?
I've tried using hells Core with the old WiFi drivers but with no success. Not wanting to go back to Lollipop due to Marshmallow's stock battery usage is too good to give up.
Tried connecting with Stock ROM + stock kernel and hells Core.
Same issues for me.
jimmyjoebob said:
Same issues for me.
Click to expand...
Click to collapse
See: http://forum.xda-developers.com/showpost.php?p=63300413&postcount=3
nick.lowe said:
See: http://forum.xda-developers.com/showpost.php?p=63300413&postcount=3
Click to expand...
Click to collapse
looks good. Thanks!
Im unable to test it out now as my network has been patched.