Related
After flashing CM6.1 I got the notorious wifi connectivity issue that numerous people have been reporting around the web. The issue is the following:
1: Wifi discovers neighbor's AP but no longer home AP.
2: Wifi problem randomly fixes itself, but sometime comes back and home AP can't be found again.
Many random solutions on the web include removing all stored AP's on the phone, resetting the router, rebooting and power cycling the phone numerous times, etc. Most people report that wifi miraculously start working again after the above but there is no consistency to exactly why and what works.
I tried all of the above with no luck, and even flashed three different roms with different kernels, did wipes, formatted everything inculding boot partition etc.
Here is the ACTUAL problem:
Different regions use different wifi channels. North America uses the first 11, most of the world uses 13, and Japan uses all 14. After flashing CM6.1 it changed the regulatory domain on the phone to only scan the first 11 channels meaning my European router broadcasting on 13 wouldn't show up. This setting seems to be persistent and doesn't change just because a new rom is flashed.
The reason people report the problem to be randomly fixed after a few days (and sometimes coming back days later) is because most routers automatically select which channel to broadcast on and therefore might end up within the first 11 at occasion. If it changes to something higher after that however, the problem is back.
Solution:
Open Settings, Wireless & network settings, Wi-Fi settings. Press "Menu" and select Advanced. Press regulatory domain and change to 14 channels.
To learn more about this and understand which channels are used in which countries, look here: http://en.wikipedia.org/wiki/List_of_WLAN_channels#2.4.C2.A0GHz_.28802.11b.2Fg.2Fn.29
Thanks man, even I still met an issue which was wifi disconnect frequently (usually after 12 seconds or less, it's re-scanning AP and trying to re-connect again) when I was trying to share my broadband internet from laptop to my legend.
BUT, after I update my wlan driver (now using 8.0.0.238 for my Atheros AR5XXX), the issue seems gone.
I found that by updating wlan driver to the very latest driver (for mine is 9.2.0.xxx) is not a guarantee to resolve this problem.
Now, by combining your suggestion and an "appropriate" driver version for my wlan, it work flawlessly until now
PS: driver version which will work varies from devices to devices. Do trial and error if you must
edit: well, not 100% gone, but much better . the connection is far more stable
Could be a problem for some but not all the issues with WiFi. I knew about this and even posted one or two times this check for the number of channels in different other topics as a possible solution. Still there are times when the connection to the "home" AP is done very late after entering in range or switching on the WiFi and the signal is changing from none to full and back frequently, for the same relative position to the router (I'm standing in the same place). Also even if the signal is full or good, the Legend seems not to have Internet connection that is, the weather updates or XDA applications or browser could not connect. This is still happening even if the selection for the number of channels is correct. And also this is not happening with a stock ROM, I made some comparisons between my Legend and one of my friends that has stock ROM. He is having full signal and excellent browsing experience while I have random disconnects or drops in signal level. My thought is that the difference between drivers made by HTC and the ones in CM ROM is the cause. As it is with some other HTC proprietary developments (like Flash implementation or FM radio), could be that HTC spent some more development time in eliminating bugs and making a better driver.
Of course, this will not stop me use CM ROMS, it is a little bit frustrating, but the other things in CM ROM's makes the difference for me.
Rapier said:
My thought is that the difference between drivers made by HTC and the ones in CM ROM is the cause
Click to expand...
Click to collapse
I think you're right. Yesterday, I tried my friend's phone (which has a stock ROM), using the same AP and there was no dropped signal or disconnected in wifi. I also tried using other android phone brand (5 series from samsung) which also has a stock ROM and there was no problem at all. Drivers is the culprit
Work
Thanks u very much.worked on my milestone
Thanks. Actually worked.
Rapier said:
Could be a problem for some but not all the issues with WiFi. I knew about this and even posted one or two times this check for the number of channels in different other topics as a possible solution. Still there are times when the connection to the "home" AP is done very late after entering in range or switching on the WiFi and the signal is changing from none to full and back frequently, for the same relative position to the router (I'm standing in the same place). Also even if the signal is full or good, the Legend seems not to have Internet connection that is, the weather updates or XDA applications or browser could not connect. This is still happening even if the selection for the number of channels is correct. And also this is not happening with a stock ROM, I made some comparisons between my Legend and one of my friends that has stock ROM. He is having full signal and excellent browsing experience while I have random disconnects or drops in signal level. My thought is that the difference between drivers made by HTC and the ones in CM ROM is the cause. As it is with some other HTC proprietary developments (like Flash implementation or FM radio), could be that HTC spent some more development time in eliminating bugs and making a better driver.
Of course, this will not stop me use CM ROMS, it is a little bit frustrating, but the other things in CM ROM's makes the difference for me.
Click to expand...
Click to collapse
Hello Rapier,
I have installed the CyanogenMod 6.1.1 (stable) on my HTC Desire (GSM / France) with latest radio image (32.49.00.32U_5.11.05.27) and taken some time to configure it. Now, everything seems to run well ... excepted the WiFi (and perhaps also the GSM). My problem is exactlw what you have described:
- on stock ROMs, the WiFi signal is stable and quite strong
- on Cyanogen ROM 6.1.1, the WiFi signal fluctuates, the connection is unstable and gets lost.
I like CyanogenMod ROMs very much. The WiFi issue is the only thing that I was not able to correct. You were speaking about WiFi drivers: would it be possible to extract the WiFi drivers from the latest HTC Desire stock ROM and copy them into the CyanogenMod installation?
My impression is that the CyanogenROM is scanning for networks in the background, even if a stable and strong WiFi network has been found and is currently connected. Perhaps there is a possibility to disable this scanning?
To finish, I have also the impression (I know, this is not very scientific ... but perhaps it could help to determinate where the issue comes from) that the GSM network is also fluctuating. I use WiFi Analyzer (available on the Android market) and when I plot a graph, without moving the phone or even without moving myself, the plot oscillates between -80dBm and -30dBm (I swear that there is nobody playing with the on/off button of my ZyXEL router ).
@sz1a: Thank you very much for your post: this helped me to discover these "hidden" settings, but my configuration is manual on the ZyXEL and everything was fine. Perhaps you should switch the thread to "unsolved".
I'n not a developer, only an ethusiast with a Legend. Also I'm not a Linux expert so I can only guess and experiment...threfore I cannot tell if porting HTC proprietary drivers is possible. I'd say not...if it was, we would have it by now. The main reason I think, is that those drivers are not open source, so nobody can port them since the sources are not available. I'm sure that if it was possible, they'll have been included in CM
Sent from my Legend using XDA App
pleaaaase help, im running CM 6.1 RC 1
wifi was working fine untill yesterday, i tried to connect to my friends router but couldnt.. i tried putting it in manually too.. then i couldnt connect to any router infact my phone wont even pick up any even my home one.. i tried switching to 14 channs like this said but no luck
any help please
Mods--I think due to the nature of this possible fundamental issue, it should be posted in the general section as well as the Troubleshooting forum area. Especially if it is affecting other devices in our homes...but if anyone disagrees, I apologize ahead of time if you feel the need to delete this. Otherwise sticky it!!
Full disclosure. I have the 4.4 160 update, not the very final patch that came out right after it, so it is possible that the patch secretly solved this issue. Also, I just bought my Nexus 2012...so I have no experience with 4.3 or 4.2.
I have an Asus RT66U router with the latest Merlin build and NO issues at all for months and months. It is commonly known to be the best router on the market (so is the AC version) . I have super finicky intermittent internet streaming on the Nexus 2012 Android 4.4, with YouTube buffering every 10 seconds and wifi signal boosting and dropping strength (it seems), but not disconnecting. I also had all of my other devices stop working around the same time I bought the Nexus (within the day I connected it).
I found a very interesting link as well-
http://productforums.google.com/forum/#!msg/nexus/PjerorpdZMA/LIJA7cToUiYJ
Right after buying the Nexus, I had to go into my router and change it's naturally acquired (by my provider) DNS, and put Google's DNS in place. I thought maybe the provider was having a DNS outage....I haven't put it back since then. But now I wonder (and I will check tonight).
So...here is the poll-
How many people, that have any wifi issues, are also having DNS issues?
Do you think this is a ROM issue.....in other words....did it happen with 4.3 or 4.2 to you?
Edit: Also I have heard of people disabling the NFC and taking off the back cover and reseating the wifi module (that is popped out a bit) and solving this issue... or changing the SSID, channel and password.
http://dale-loflin.blogspot.com/2012/12/nexus-7-wifi-internet-connection-issue.html
My i9505 has been misbehaving when trying to connect to 5GHz wifi since the 12th of October, when I flashed the then-newest official Cyanogenmod 10.2 nightly; before that it had been working with any problem on those same nightlies. Something must have been introduced between then and the 2nd of October; I didn't do any flashing during that time as I was abroad on business, so I'm not sure exactly when the change might have been introduced. Since that time I've moved to a 4.4 ROM but the problem persists.
It seems that I'm not the only one having problems with 5GHz wifi on AOSP ROMs - Google turns up various problems on different ROMs and devices. There are even suggested solutions such as editing text files in /system/etc/wifi or changing one's router's channel. None of these work for me.
The symptoms vary. Some of the time the device will simply refuse to connect to 5GHz networks. Other times it will connect and work normally for a time, anything from approx. 1 minute to 30 minutes or more (the latter making me think for a while that the problem is fixed). But, eventually, apps will stop getting a network connection and I'll be unable to ping anything. Despite this total lack of connectivity the wifi indicator will show that the device is still connected to Google's servers. Turning wifi off and on will start the cycle again, until I give up and switch back to 2.4 GHz.
This is rather frustrating and I wonder if anyone has any clue what it might be, or how it might be investigated further.
Has anyone else experienced this problem?
knirirr said:
Has anyone else experienced this problem?
Click to expand...
Click to collapse
Yes, i have similar problem. i changed few custom roms, and nothing helps. First, it works normal, for few minutes, then wi fi go automaticly off, and then i cannot connect to wi fi network
I noticed this on 4.3 all versions, but since I updated to 4.4 official on my i9505G, the problem went away. I think it may be s bug in the NON-HLOS in the 4.3 roms .. official or otherwise.
Sent from my GT-I9505G using Tapatalk
toastido said:
I noticed this on 4.3 all versions, but since I updated to 4.4 official on my i9505G, the problem went away. I think it may be s bug in the NON-HLOS in the 4.3 roms .. official or otherwise.
Sent from my GT-I9505G using Tapatalk
Click to expand...
Click to collapse
I think it came in on 4.3, and I wonder why it is still affecting me on 4.4 as some people are reporting that has been fixed.
When official jfltexx CM11 nightlies come out I'll try a clean flash to see if there's any change.
I decided to try something similar - I updated to the latest UK firmware and then did a clean flash of an unofficial CM11 4.4.1. 5GHz Wi-Fi still doesn't work properly, as above.
I can get better results within a couple of metres of the AP.
Usually i switch on WiFi and disable mobile data manually while at home. It turns out that i don't receive any Push Notifications like WhatsApp, Threema, Facebook and GMail/Inbox (those who are using gcm) when the device is connected to WiFi solely and the screen is locked. If i unlock the device after a certain amount of time, a bunch of notifications are popping up. This is reproducable and won't occur on mobile data. Just do the following, while i.e. at home:
Connect to WiFi
Deactivate your Mobile Data
Lock your screen and let your Device rest for a couple of seconds
Tell someone to send you a Mail to your Gmail Account (or on any other GCM-Push related way)
You probably may notice that your device won't wake up to notify you about this incoming message until you pick it up and unlock it. I have tested this since weeks with multiple official nightlies of CM12, custom builds and even unofficial CM12.1 builds, they all show the same behaviour. Even with official CM11s this issue persists, but can be worked around by unchecking "WiFi Optimizations" in advanced WiFi-Settings. Unfortunately Lollipop doesn't have this WiFi Optimization trigger anymore. Ofc "Keep WiFi on during sleep" is set to "always". After all tests i came to the conclusion that the device simply gets no wakelock trigger from notifications if connected to WiFi solely. I've fixed this for me by fiddeling with the configuration files (root needed).
Open /system/etc/wifi/WCNSS_qcom_cfg.ini and change
Code:
hostNSOffload=0
to
Code:
hostNSOffload=1
After this change and a reboot, your device should be able to wake up from incoming notifications instantly while on WiFi. Some custom ROM, like SlimSaber have set this out of the box, while official cm nightlies and other custom ROM, like exodus, haven't.
Have you tested IPv6 over WiFi with 12.1? As that is also broken on 12.
JaY_III said:
Have you tested IPv6 over WiFi with 12.1? As that is also broken on 12.
Click to expand...
Click to collapse
Usually i've disabled ivp6, because of the known problems with it. I've tested it with ipv6 enabled and it worked.
Meanwhile i was able to test a lil bit more on other networks. It seems like this all is router dependant. While having the chance to exessively using another WiFi network yesterday, i was able to check that there are no such problems as described before. After went home, problems reappeared. I have to conclude that there must be some culprit with my router at least (Telekom Speedport W724V).
I noticed such notification flood several times.
I can't say under which circumstances because I didn't care about it yet but your post made me remember this.
I gonna investigate that asap.
As far as I can say this happened only at home yet. My router is an AVM FritzBox 7390.
On my OPO I have usually always one of the newest official CM12 nightlies installed.
I've tested stock settings while connected to a completely different router a few days ago and wasn't able to reproduce the issue. It really turns out that it has something to do with certain routers, in my case a Speedport W724V Type A (by Huawei). It seems like this issues has something to do with ARP Offloading and filtering of Broadcast/Multicast. As far as i understand, Androids MAC Adress isn't hard coded and the router loses the connection to the device if it goes into sleep state. Therefore the router has to broadcast via arp to look for the device, but the device simply doesn't respond to the arp request, coz the wifi driver is configured to ignore that broadcasts and continue sleeping. This issue is, as i read, present since KitKat where it could at least be worked around by disabling the WiFi Optimizations, which seems to be only a checkbox for above mentioned manual method Lollipop.
Currently i've no idea how to fix this in a better way, since my described method works flawlessly, but it's definately a lil battery drainer. Another way to work around this is by setting "Keep Wi-Fi on during sleep" to "never" and let the device handover the data connection to mobile data while sleeping. This, at least, ensures the battery savings which were intended by the developers.
Steve Kondik merged an interesting commit today, which i am not aware of if this will change anything related to this issue. As this commit was merged into cm12.1 branch i doubt that we will see anything related in cm12 based roms, nor the upcoming cm12s. Maybe some nifty dev like @ak or @Lord Boeffla can take a look into this and implement it into their kernel.
I put the interesting commit into my cm12.1 kernel, which comes out tomorrow.
If all goes well I can look to back port it to cm12 and maybe even cm11(s).
Let's see. First we need opinions on the test kernel tomorrow.
Andi
Genericxx said:
I've tested stock settings while connected to a completely different router a few days ago and wasn't able to reproduce the issue. It really turns out that it has something to do with certain routers, in my case a Speedport W724V Type A (by Huawei). It seems like this issues has something to do with ARP Offloading and filtering of Broadcast/Multicast. As far as i understand, Androids MAC Adress isn't hard coded and the router loses the connection to the device if it goes into sleep state. Therefore the router has to broadcast via arp to look for the device, but the device simply doesn't respond to the arp request, coz the wifi driver is configured to ignore that broadcasts and continue sleeping. This issue is, as i read, present since KitKat where it could at least be worked around by disabling the WiFi Optimizations, which seems to be only a checkbox for above mentioned manual method Lollipop.
Currently i've no idea how to fix this in a better way, since my described method works flawlessly, but it's definately a lil battery drainer. Another way to work around this is by setting "Keep Wi-Fi on during sleep" to "never" and let the device handover the data connection to mobile data while sleeping. This, at least, ensures the battery savings which were intended by the developers.
Steve Kondik merged an interesting commit today, which i am not aware of if this will change anything related to this issue. As this commit was merged into cm12.1 branch i doubt that we will see anything related in cm12 based roms, nor the upcoming cm12s. Maybe some nifty dev like @ak or @Lord Boeffla can take a look into this and implement it into their kernel.
Click to expand...
Click to collapse
It fixed my wifi bug so far on euphoria 5.1
Okay guys, i've tried AK's latest experimental kernel (v203). Beside of some small problems which are still under developement, WiFi seems to be fixed completely with the implementation of the new prima drivers for me. This could mean, that they will be automatically fixed with the release of the official cm12.1 nightlies. As for now i will thank everyone, especially @ak and @Lord Boeffla for participating and help to hunt down and solve this annoying issue. You're great guys :good:
Genericxx said:
Okay guys, i've tried AK's latest experimental kernel (v203). Beside of some small problems which are still under developement, WiFi seems to be fixed completely with the implementation of the new prima drivers for me. This could mean, that they will be automatically fixed with the release of the official cm12.1 nightlies. As for now i will thank everyone, especially @ak and @Lord Boeffla for participating and help to hunt down and solve this annoying issue. You're great guys :good:
Click to expand...
Click to collapse
Thanks. With the latest beta kernel for cm12.1 which I released this morning, these drivers are also included.
If they turn out to work better - my other kernel variants (cm11s, cm11, cm12) are also already ready with these new drivers backported. Just have not released them as I want to give it some more testing.
Andi
Anyone else notice the same issue on Oxygen Os? I'm not sure if it's just the router I connect to at work, since this doesn't happen at home. Can't tell yet, will give this a shot.
xxBrun0xx said:
Anyone else notice the same issue on Oxygen Os? I'm not sure if it's just the router I connect to at work, since this doesn't happen at home. Can't tell yet, will give this a shot.
Click to expand...
Click to collapse
Would be an interesting test.
We cannot look into the driver used for Oxygen OS as the kernel code is not yet released as far as I know (if it is, I would be happily be corrected )
Andi
I'll bet that oxygen suffers of the same problems as every cm12 build does (even if it's more aosp) and CyanogenOS 12 (CM12s) will also.
Genericxx said:
I'll bet that oxygen suffers of the same problems as every cm12 build does (even if it's more aosp) and CyanogenOS 12 (CM12s) will also.
Click to expand...
Click to collapse
Let's see.
I backported the new drivers to CM12, CM11s and CM11 already.
Just need to decide whether I ship that or not
Andi
Lord Boeffla said:
Let's see.
I backported the new drivers to CM12, CM11s and CM11 already.
Just need to decide whether I ship that or not
Andi
Click to expand...
Click to collapse
is it already out ?
reyscott1968 said:
is it already out ?
Click to expand...
Click to collapse
Indeed it is.
Andi
Just to report back, this did seem to fix my wifi issues, although I've since switched to Exodus, so I didn't have a ton of time to play with it.
Thanks for taking the time to investigate this issue. I should have done the same I will ago when it started bothering me.
I will try one of the kernels and see if it fixes it. If not I'll try your method once I am back home.
Thanks!
Jur1nator said:
Thanks for taking the time to investigate this issue. I should have done the same I will ago when it started bothering me.
I will try one of the kernels and see if it fixes it. If not I'll try your method once I am back home.
Thanks!
Click to expand...
Click to collapse
You're welcome. I have to admit that the problem reappeared. So the new Wi-Fi drivers have no permanent solution for me. As told in the other thread I found my temporary solution by simply let Wi-Fi auto turn off when device for to sleep. My data plan allows me this easily, but if you're on a 200mb data plan this could be ****ty for you. Let's see if future commits of cm will change anything.
I fortunately have a 3gb lte contract, so this shouldn't be the issue. I just don't want to accept that there might not be a solution without tradeoffs.
I'll let you know if I find anything
Jur1nator said:
I fortunately have a 3gb lte contract, so this shouldn't be the issue. I just don't want to accept that there might not be a solution without tradeoffs.
I'll let you know if I find anything
Click to expand...
Click to collapse
Would be nice. I'm hunting this issue down since January, so far, as said, without any real solution other than using another router. it works anywhere except at home, so i know exactly how annoying this is. It's not that big problem to use mobile data when screen is off, but is pisses me off, if i just forget this sometimes and miss urgend messages from WhatsApp or Threema, coz they're arriving hours later. As desribed above, there is a way to prevent the OnePlus to not filter the WiFi Broadcasts. You just have to edit this one line in the configuration manually, but it comes at the cost of battery.
It seems that the current Android version on the LG G6 has that annoying wlan_rx_wake issue again. It keeps Android OS and Android System awake for hours (awake and CPU using) and makes nearly 25 percent of battery usage.
In this case Android is just reacting to broadcasts on WiFi but the way it handles it is simply bad. I created a guest network with my device only and this fixed the issue or it circumvents it. But since it's only an issue on LG's Android 7 and no other of my devices has it, it must be a bug.
Is there a settings to ignore broadcasts more aggressively? I've no root fore some reasons.
I've been there myself and have posted what little progress I've made in the Standby drain thread. I don't think this is a problem specific to LG's Android 7 nor do I think it is LG's or Android 7's problem on their own. I thought this affected most (if not all) devices using any modern release of Android when connected to a "noisy" network, but don't quote me on that. I've had this problem on several different android devices running different distributions of Android, including the G6 running both Stock and AOSP-based 7.X ROMs. However, most of my other devices had a custom kernel that did allow me to block this wakelock. It's any easy fix that I've implemented myself in the G6's stock kernel by adding a few lines to LG's publicly released source code, which effectively got rid of wlan_rx_wake for me by changing a setting on my phone. I assume that you say you don't have root not because of personal preference but because you have an unlockable bootloader. If the latter is the case, this kernel fix wouldn't apply to you. You may be able to fix the issue on the other end though. If this happens in your own personal network you might just have to disable a problematic app in a device connected to it or change a router setting. If, however, this happens in an institutional network that you can't control and that a lot of people simultaneously access, you'll have a harder time working around it. In any case, ditching DHCP for a static IP and disabling IPv6 could help. It might also be worth analyzing your network traffic with a packet sniffer and checking what is waking your device. If it turns out be a single or a handful of devices sending packets throughout your network and you don't have access to them, you might be able to block and/or ignore them by running some custom iptables scripts on a firewall app (not sure if this feature is available without root access). I'm assuming that by creating a guest-net you isolated your phone from all of these alleged requests circulating in your main network and that's why your phone isn't woken up as often,. I'm not 100% sure we're facing the same problem nor that any of this could be of any hep at all. Be sure to let us know if you find a fix for this. Cheers!