I have been having this problem for about the last 3 days where I lose the downstream from my wifi after the screen turns off. The wifi is still connected and blue, and within the wifi bars there are the two grey arrows for up and down. The up arrow still flashes meaning the wifi upload is still connected, but the download arrow no longer shows. I'm able to regain the wifi downstream by toggling wifi off and then back on. As long as I don't let my phone go into sleep then I maintain wifi connectivity, but as soon as it goes into sleep I will have to toggle wfi to regain full connection again.
I'm running AOKP JB build 1 with franco kernel nightly 283. I haven't made any recent changes to my router or wifi settings. It seems to have just started happening in the last 2-3 days. My first guess is that there were some wifi issues with recent Google wifi drivers that were included in the franco kernel. Apparently the more recent nightlies reverted the wifi drivers to avoid the problems, but maybe I still have the old drivers despite running a more recent build? Like the got stuck or something on the drivers with problems. I only suggest this because I was reading around in other threads were someone mentioned if you flashed a kernel with new drivers and then another kernel with the old drivers, the only way to actually revert the drivers is to wipe and flash a fresh ROM.
However, if anyone is aware of any other possible solutions then I'm open to suggestions. Oh yeah, before it's mentioned I also have wifi set to always on, and the router is running WPA2 (AES) and the phone has a static IP. I realize this is most likely a kernel problem since that's really all that's changed in the last few days (flashing new nightlies) but I'm unable to post in the development threads and reading through his thread, no one else seems to be having this problem
If you think it could be kernel related, why not flash a stable Franco release?
You could also just upgrade to aokp build 4 then see if wifi is properly, then flash the kernel, there might be your answer.
Sent from my Galaxy Nexus using Tapatalk 2
Fire n mage said:
If you think it could be kernel related, why not flash a stable Franco release?
You could also just upgrade to aokp build 4 then see if wifi is properly, then flash the kernel, there might be your answer.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I've tried reverting to an older nightly, or even to the stable Milestone 5 but with no affect. That's why I'm wondering if it's possible once the updated wifi drivers are flashed, even flashing a different Kernel with the older drivers won't overwrite the drivers since they aren't the most up-to-date.
As far as flashing the newest build of AOKP, I was planning on doing that this weekend to see if it helps. But until then I was hoping someone here may have some answers, because even flashing a new ROM doesn't guarantee a fix.
I'm using nightly 282 of the French Revolution HD 6.1.0 +, and have not had this problem. I was having this problem one day that, with the CM10 Nightly. But I decided as follows:
Settings / Wifi / Advanced / Keep Wifi during inactivity.
Test to see ae of the right.
Settings > WiFi > Menu(the 3 dots) > Advance > Keep WiFi on during sleep > profit
Franco setting
I think your problem is releated to Wifi Driver, of couse wifi driver goes to battery safe mode when you screenoff
It's not releated to your router, for simple reason this is phone problem
It's can be ( mach do it first ) settings, upto android 4x series wifi have wifi autodisconnect on screenoff ( using data instead or nothing ), theorically data cause less battery drain than wifi, this is the sense of this value, and it's to prefer instead juice defender or another non-system app.
You can always disable wifi_pm on franco using
Code:
echo 0 > /sys/module/bcmdhd/parameters/wifi_pm
This dont allow to wifi driver screenoff modes ( less wireless performance -> less battery usage ) but increase battery drain from wireless on screenoff
Related
I recently performed a full wipe and installed the CM9 4/22 nightly, stock kernel, minimal apps in an effort to discover what was causing MASSIVE battery drain on my VZW SGN.
Using CPUSpy I can see my phone isn't going to sleep, and is staying awake @ 350 MHz for hours, but only when associated to my home (D-Link router) or work's (Cisco AP) 802.11n wireless. I am seeing a TON of Kernel Wakelocks caused by "wlan_rx_wake" via BetterBatteryStats, and this aligns to the overwhelming "Android OS" percentage of what is consuming my battery according to the native ICS app (settings -> battery).
According to the research I did, wlan_rx_wake is an event that wakes the kernel when a message is received via wifi, like a gmail push notification. Seems like something outside of my control. The weird thing is...i don't see these wake-ups on 4G. In fact the phone actually goes to sleep and gets better battery life when I'm NOT tied to wireless. What gives? Is the ROM doing something weird with the wireless? TIA for any advice, it's much appreciated.
Are you using a dynamic IP?
hittingsmoke said:
Are you using a dynamic IP?
Click to expand...
Click to collapse
yep, and i increased my DHCP lease times to 8 days.
i *think* i've discovered what the problem is, using WireShark and my HTPC sniffing out traffic to my wifi-joined cell phone. my router, issued by my ISP, is sending out "who-has" ARP requests to every IP address on my subnet, round-robin style. this is waking up my phone about 2x per minute.
i don't know if my ISP has enabled some ARP thing in the router (i looked in its config, can't figure out a way to disable the network scanning), or if the latest CM9 nightlies (i'm on 4/22) has suddenly decided to start responding to these requests...either way i've got to keep my phone on 4G to save battery. didn't have to do this a few weeks ago. very odd.
I experienced the same (along with wlan_ctrl_wake), and did quite a bit of experimenting: http://forum.xda-developers.com/showthread.php?t=1598581&highlight=cm9+wifi
Some wifi related commits, yet to be merged, 03:48 on May 5, maybe the new drivers will help: http://review.cyanogenmod.com/#/q/branch:ics,n,z
In the interim I either use another kernel, or use strictly data, I find the stock CM9 kernel doesn't drain excessively while on data. If you want to try another kernel instead, I'd recommend CM Plus Tuna; wifi drivers were reverted and a wlan_ctrl commit removed and there is no issue.
CMNein said:
I experienced the same (along with wlan_ctrl_wake), and did quite a bit of experimenting: http://forum.xda-developers.com/showthread.php?t=1598581&highlight=cm9+wifi
Some wifi related commits, yet to be merged, 03:48 on May 5, maybe the new drivers will help: http://review.cyanogenmod.com/#/q/branch:ics,n,z
In the interim I either use another kernel, or use strictly data, I find the stock CM9 kernel doesn't drain excessively while on data. If you want to try another kernel instead, I'd recommend CM Plus Tuna; wifi drivers were reverted and a wlan_ctrl commit removed and there is no issue.
Click to expand...
Click to collapse
Many thanks. I try to run the Franco kernel as well but still see the same issues. gonna just use cell data in the meantime till the wifi gets worked out in CM9
mcgoo99 said:
Many thanks. I try to run the Franco kernel as well but still see the same issues. gonna just use cell data in the meantime till the wifi gets worked out in CM9
Click to expand...
Click to collapse
Your issue sounds more app related possibly, since Franco has different wifi drivers than the stock CM9 kernel, unless he's updated them recently. Perhaps a nandroid and then a wipe (without restoring apps) to narrow it down.
CMNein said:
Your issue sounds more app related possibly, since Franco has different wifi drivers than the stock CM9 kernel, unless he's updated them recently. Perhaps a nandroid and then a wipe (without restoring apps) to narrow it down.
Click to expand...
Click to collapse
I don't think it is app related. I already wiped and installed base CM9, and with just two apps I saw the wlan wakes. I saw them on the Franco kernel as well. I'll try the Franco kernel once more and see if its been fixed.
mcgoo99 said:
I don't think it is app related. I already wiped and installed base CM9, and with just two apps I saw the wlan wakes. I saw them on the Franco kernel as well. I'll try the Franco kernel once more and see if its been fixed.
Click to expand...
Click to collapse
Same behaviour on all routers?
Sent from my Galaxy Nexus
CMNein said:
Same behaviour on all routers?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
i believe so. i found a new radio for the SGN posted on 5/1, gonna give that a shot, as well as the newest CM9 nightly, 5/7. if i continue to get wakelocks on wifi, i'm wiping and trying again...
EDIT: after wiping and installing JUST CM9 and 4/29 gapps, no apps other than BetterBatteryStats and CPUSpy, i still get a ton of wlan_rx_wakes show up, not allowing my phone to go into deep sleep and keeping it awake. meanwhile, my Samsung Galaxy Tab, running the same CM9 nightly, same gapps, same wifi network, and a TON of apps is sleeping like a baby. i have no explanation for this, and why it's specific to my phone only.
mcgoo99 said:
i believe so. i found a new radio for the SGN posted on 5/1, gonna give that a shot, as well as the newest CM9 nightly, 5/7. if i continue to get wakelocks on wifi, i'm wiping and trying again...
EDIT: after wiping and installing JUST CM9 and 4/29 gapps, no apps other than BetterBatteryStats and CPUSpy, i still get a ton of wlan_rx_wakes show up, not allowing my phone to go into deep sleep and keeping it awake. meanwhile, my Samsung Galaxy Tab, running the same CM9 nightly, same gapps, same wifi network, and a TON of apps is sleeping like a baby. i have no explanation for this, and why it's specific to my phone only.
Click to expand...
Click to collapse
the system restore process is PAINFULL, but here's the edited version. use these directions:
http://forum.xda-developers.com/showthread.php?t=1426207
with this file:
http://www.mediafire.com/?cnqab1sg2b1u93p
to use Odin to restore to 4.0.2 (windows only, sorry).
then reflash clockworkmod recovery, reflash new 4.0.4 radios, wipe EVERYTHING (factory data, cache, system, dalvik, battery stats - i'm doing it all just to be certain) flash CM9 nightly, flash gapps, then wipe again but no system this time (factory data, cache, dalvik, battery stats). reboot. log into the google acount but don't restore any apps, just install CPUSpy after accepting the Play T&C's.
phone sleeps on 4G. phone sleeps on wifi. i'm happy...for now will report back if anything mysterious happens.
I know this is old but I had the same problem with Cyanogenmod 9 Stable. If this bug is this old (and I actually remember having this problem on some of the early nightlys as well but never found a cause) then it's pretty sad they let it sit this long and then release the ROM as stable. Anyway I fixed it by flashing leankernel. That instantly stopped my wlan_rx_wake wakelocks and allowed my phone to deep sleep. Here's the thread I made on rootzwiki if interested
http://rootzwiki.com/topic/32175-cm9-android-os-keeping-phone-awake/
Old issue again, but this issue plagued my nexus 7.
I narrowed down my issue to a wireless HP printer as well. I disabled the wireless since I wasn't using it and my battery is back to normal.
I recently replaced a RoadRunner provided modem "2100" with a personal modem Motorola SB6141. Ever since my "wlan_rx_wake" is draining battery much faster than it use to. Same router (WRT54G). I did also change from Viatalk PAP2T to Ooma Telo phone service, so not sure if that's related. Also upgraded to android 4.3, so another variable. Nexus on Static IP as well as Ooma Telo. Not rooted.
Anything I can try to keep wlan_rx_wak down? (other than shutting off wifi). I use GrooveIP which needs wifi on. It doesn't look like it's the problem.
I've upgraded to JB, and absolutely love it. Only one thing I cannot figure out after searching extensively and trying out countless apps, is how to force WiFi to stay on at all times. I need it on for incoming VOIP calls. Seems that for me in JB that is really hard to accomplish, where on 2.2 and 2.3 I had no problems. I'm running JRN84D JB with the 3.0.31 Franco kernel on a GSM GN.
Any help is greatly appreciated!
EditorDZ said:
I've upgraded to JB, and absolutely love it. Only one thing I cannot figure out after searching extensively and trying out countless apps, is how to force WiFi to stay on at all times. I need it on for incoming VOIP calls. Seems that for me in JB that is really hard to accomplish, where on 2.2 and 2.3 I had no problems. I'm running JRN84D JB with the 3.0.31 Franco kernel on a GSM GN.
Any help is greatly appreciated!
Click to expand...
Click to collapse
Have you checked Settings > WiFi > 3 dots > Advanced > Keep WiFi on during sleep?
From what I understand, from Honeycomb on, even with this option enabled, Android has been programmed for this option to only use low performance WiFi, meaning that it is throttled and can stutter or even disconnect. Applications that are properly coded for Honeycomb forward should call "WIFI_MODE_FULL_HIGH_PERF" if needed, which will lock in high performance WiFi during sleep. If this isn't occurring, the developer of the app will need to be contacted to resolve the issue.
Reference: https://developer.android.com/reference/android/net/wifi/WifiManager.html#WIFI_MODE_FULL_HIGH_PERF
This might help: https://play.google.com/store/apps/details?id=com.ratcash.wifiperf
JaiaV said:
Have you checked Settings > WiFi > 3 dots > Advanced > Keep WiFi on during sleep?
From what I understand, from Honeycomb on, even with this option enabled, Android has been programmed for this option to only use low performance WiFi, meaning that it is throttled and can stutter or even disconnect. Applications that are properly coded for Honeycomb forward should call "WIFI_MODE_FULL_HIGH_PERF" if needed, which will lock in high performance WiFi during sleep. If this isn't occurring, the developer of the app will need to be contacted to resolve the issue.
Click to expand...
Click to collapse
Thank you very much for your detailed answer. Yes, my settings are indeed correct. I also tried the app you suggested, but still no success. After 15-20 minutes of inactivity, wifi always gets turned off. I'm baffled.
Does constant-on Wifi work for anybody on JB? If yes, what rom are you using? Any special tricks/apps?
I have the opposite problem with JB, even my wifi policy is keep on while sleep only when plugged in, but my wifi seems to stay on all the time...
FYI: I am on stock JB flashed with CWM, didn't flash the new radio yet so I am still on I9250XXLA2 from 4.0.4 yakju
tacz said:
I have the opposite problem with JB, even my wifi policy is keep on while sleep only when plugged in, but my wifi seems to stay on all the time...
FYI: I am on stock JB flashed with CWM, didn't flash the new radio yet so I am still on I9250XXLA2 from 4.0.4 yakju
Click to expand...
Click to collapse
I'm using the same ROM, but I did flash a new radio (XXLF1). I will try and flash a different one. Maybe that'll be a clue.
On completely stock 4.1 GSM and my WiFi just stays on while sleep just fine.
EditorDZ said:
I'm using the same ROM, but I did flash a new radio (XXLF1). I will try and flash a different one. Maybe that'll be a clue.
Click to expand...
Click to collapse
Can you let us know your results?
I'm having a similar issue with WiFi not connecting when i get into the office, event though the router is behind me, and visible.
I've turned off the "don't connect to poor quality networks" option.
Does anyone know the exact functionality of this feature? What defines "poor quality"? Does the phone run a test between your phone data speed vs. the WiFi speed?
Initially when I installed JB (v1 for Verizon) I couldn't get WiFi to turn off. It's doing fine now on v3 with all the little fixes patch.
Hi folks,
I am experiencing a battery drain problem after upgrading my Gnex-gsm via OTA to 4.1.1 (from 4.0.4). I thought that is due to some applications or settings so factory default my device. The only application I installed was Cpu Spy (and better battery stats) to find the culprit. Result was still the same. I googled similar issues introduced by jelly bean but couldn't find a permanent and satisfying solution. Here are the details:
- I had a stock rom/kernel when I was at 4.0.4 (flashed android factory image manually) and didn't see any service/app waking my device like this.
- I upgraded via single OTA to 4.1.1 and started experiencing battery drain to high awake times (%50ish deep sleep, %50ish 350+700mhz). This is not affected after I factory default/wipe cache (as well as dalvik cache).
- After testing several combinations (like disabling google backup service, turning off google sync., disabling gps etc.) the only way to stop this drain is either disabling WiFi (my 3g data packet is still active) or leaving WiFi ON but not connecting it to any gateway. I haven't changed my gateway and my friend with the very same Jelly Bean Gnex is connected to it without having any battery drain problem.
- I wiped my phone 4-5 times and even tried setting up without any Google account, the result is same.
- I flashed latest franco kernel for jelly bean, nothing has changed.
- I modified all wifi options (Avoiding poor connections (I do have good wifi and 3g reception) and let wifi sleep during sleep) but that havent changed things much.
According to my tests, RILJ, GTALK_ASYNC and connectivity service are causing high awake times (their order changes time to time).
You can see my attachments for details. The only thing I haven't tried is flashing a jelly bean custom rom but I am leaving it for the last resort.
I will be really glad if you can put some reasoning about this issue because it is making me crazy
http://forum.xda-developers.com/wiki/Wakelocks#RILJ
Dialer RILJ is the userland counterpart of the RIL (radio interface lib). RILJ handles whatever the phone need to tell or get from the RIL = phone, e.g. dialing but also coarse location.
Click to expand...
Click to collapse
I would try disabling location services to see if that's causing your issue. I noted worse battery life with location services enabled.
Hi Cilraaz,
I had tried that before but retried again. Unfortunately the amount of wakelocks have not been reduced.
Thanks for the references by the way
Cilraaz said:
http://forum.xda-developers.com/wiki/Wakelocks#RILJ
I would try disabling location services to see if that's causing your issue. I noted worse battery life with location services enabled.
Click to expand...
Click to collapse
Using the JB + stock kernel Franco realized that consumption is very high, especially with the screen connected ...
I removed the location data and still got the high consumption and had no decrease in power consumption ..
Maaaan... I am suffering from the same issue with jelly bean stock...
I have tried all the things u mentioned nothing helped.
The strange thing is that it's only consuming on wifi when it should drain less power.
I would be so happy to find a solution...
Sent from my Galaxy Nexus using Tapatalk 2
Tonight I did a test with all syncs and 3g enabled and now it totally seems that it's definitely the wifi that keeps waking up the device... Grrrrrrrrrrrrr
Tapatalk 2-vel küldve az én Galaxy Nexus-ről
It is clear that we are experiencing the very same problem. The problem is due to wifi connection for sure.
I guess one of the system processes do keep trying to reach a server or something if and only if wifi connection is valid.
I have tried 2 different ROMS (one is pure AOSP and the other one is liquidsmooth alpha w/ trinity kernel). Unfortunately the problem persists
I am going to investigate the problem and use a sniffer to track wireless activity.
The thing is this is happening even device is fully formatted (/data /cache /system /sdcard and dalvik cache)
Am I missing any partitions that may affect this and remained dirty?. Hope anyone have any idea.
Ok, after diagnosing the sniffer I find that JellyBean Gnex keeps reconnecting to the access point even tough it is not sending deauth/disassoc. It is not the case with 4.0.4 (probably changes in wpa_supplicant caused this).
Each reconnection request triggers RILJ/Gtalk async. bla bla and causing device to stay awake. I will check wpa_supplicant logs and find out the reason behind the reconnection decision.
Using a cisco gateway (with same wireless settings) fixes the problem.
Not so in my case. Very less awake times and excellent battery life.
Sent from my Galaxy Nexus using Tapatalk 2
Yup that's very strange actually that not all Gnex owners experience this issue. Would be great to find the difference between those devices and ours.
Sent from my Galaxy Nexus using Tapatalk 2
cankavera said:
Ok, after diagnosing the sniffer I find that JellyBean Gnex keeps reconnecting to the access point even tough it is not sending deauth/disassoc. It is not the case with 4.0.4 (probably changes in wpa_supplicant caused this).
Each reconnection request triggers RILJ/Gtalk async. bla bla and causing device to stay awake. I will check wpa_supplicant logs and find out the reason behind the reconnection decision.
Using a cisco gateway (with same wireless settings) fixes the problem.
Click to expand...
Click to collapse
Yeah man that sounds like a progress
Sent from my Galaxy Nexus using Tapatalk 2
You could always try adding the following to build.prop:
Code:
wifi.supplicant_scan_interval=1800
That would make your wifi only scan for a stronger AP every 30 minutes.
Thanks for the suggestion Cilraaz, unfortunately it didn't help. I need a way to increase debug level of wpa_supplicant (using wpa_cli level didnt work).
Dmesg gives a hint though. When device is trying to sleep, a kernel message (no IPv6 router) triggers disconnect (and it reconnects right after). This happens continuously every 10-20secs and waking the device.
<7>[ 86.163146] wlan0: no IPv6 routers present
<3>[ 91.762573] CFG80211-ERROR) wl_notify_connect_status : link down, calling cfg80211_disconnected with deauth_reason:0
<6>[ 91.772399] cfg80211: Calling CRDA to update world regulatory domain
<4>[ 93.140258] wl_bss_connect_done succeeded
<6>[ 93.191009] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
<4>[ 93.349090] wl_bss_connect_done succeeded
Why the hell device needs a IPv6 router? It shoudl be ok with IPv4.
Cilraaz said:
You could always try adding the following to build.prop:
Code:
wifi.supplicant_scan_interval=1800
That would make your wifi only scan for a stronger AP every 30 minutes.
Click to expand...
Click to collapse
Wow. Hope Google is heading this way as well...
Sent from my Galaxy Nexus using Tapatalk 2
Avoid poor connections
Disabling "Avoid poor connections" from Wi-Fi settings fixed the problem for me
laithmurad said:
Disabling "Avoid poor connections" from Wi-Fi settings fixed the problem for me
Click to expand...
Click to collapse
Tried this right now but didn't help for me that's soooooo frustrating!
Sent from my Galaxy Nexus using Tapatalk 2
Anyone having a progress here?
Would be good to reach Google and ask their opinion about that...
That was the first thing I had tried but reconnections are not happening due to poor connection. Signal strength is pretty good (around -40 -50dBm)
and it is still happening.
I also flashed 4.1.1 factory image (as well as AOKP, CM10 and one more jelly bean custom firmware) after wiping everything and I am still experiencing the problem.
I am going to try using 4.0.4 wpa_supplicant binary in a 4.1.1 rom. Albeit, I suspect the problem is introduced by new kernel. (I am not sure 4.0.4 kernel is compatible with 4.1.1 rom, anyone have any ideas?)
laithmurad said:
Disabling "Avoid poor connections" from Wi-Fi settings fixed the problem for me
Click to expand...
Click to collapse
cankavera said:
That was the first thing I had tried but reconnections are not happening due to poor connection. Signal strength is pretty good (around -40 -50dBm)
and it is still happening.
I also flashed 4.1.1 factory image (as well as AOKP, CM10 and one more jelly bean custom firmware) after wiping everything and I am still experiencing the problem.
I am going to try using 4.0.4 wpa_supplicant binary in a 4.1.1 rom. Albeit, I suspect the problem is introduced by new kernel. (I am not sure 4.0.4 kernel is compatible with 4.1.1 rom, anyone have any ideas?)
Click to expand...
Click to collapse
This options was 1st introduced in 4.0.1 and it was terrible for me when enabled, Google removed it since 4.0.2, and now its back on 4.1.1, I only get like 10 Hours while this option is checked, when unchecked battery lasts more than 22 Hours, I guess what happens is that Wi-Fi keeps disconnecting and switching to 3G, then goes back to Wi-Fi frequently.
Cankavera!
Somehow it seems I am unable to send you a PM.
Can you confirm that replacing your router fixed the issue with high waked up times?
I am using a quite old MSI RG60 router so if you say its enough to replace it I will do it...
Hey everyone, just came over here from the HTC One X ( AT&T ) forums, smashed the screen on it and used an upgrade to get an AT&T SGS3, loving it so far. Had it rooted and custom recovery, and was on a custom ROM not even an hour after getting home. Anyway, onto the main part of this post.
I tried CM10 ( the 11/01 and 11/02 nightlies), both of the AOKP, and LiquidSmooth, and on all of them, my WiFi stability is not there. It seems to disconnect at random, if connect at all, and when i walk out of range of the router, and then come back, it will not automatically reconnect until i go into airplane mode. Trying to turn WiFi itself off and back on does not work - it won't turn off/back on, it sticks at what it was at.
TouchWiz ROMs, everything works just fine. I'm pretty sure it was working on MIUI as well, but i didnt have MIUI on there long enough to properly test it.
I am using the UCLH9 radio, since AFTER searching the forums pretty in-depth, i found that all radios prior to UCLH9 had wifi driver issues. Flashing this new radio did NOT fix the issue.
I have tried both stock CM10 kernel AND Ktoonsez's kernel (which is pretty freakin awesome, btw! :good: ) and still have WiFi problems.
I have tried flashing ROMs through both TWRP and CWM Recoveries, and have done a full wip of /system /data /cache and /dalvik-cache 3 times each before flashing a ROM.
I'm a pretty competent at flashing ROMs and troubleshooting problems, I am a pretty well-known beta-tester for multiple Sense and AOSP ROMs over at the One X forums, and I have a very good knowledge of how to work ADB and Fastboot. I've been around XDA for a little while, and I know the way of things around here. (don't want you guys thinking im just another a$$hole that threw a post up the second a problem occurred without doing some research first!)
If anyone has ANY ideas as to what may be causing the wifi drivers to crash, PLEASE fill me in.
I've tried all the same things you have and have had no success. The best wifi stability I got was the AOKP_d2att milestone1 w/ lean kernel combination, but wifi would stay connected for 3-5 minutes as opposed to 30 seconds.
I briefly tried CM9, but that still had wifi issues. I might try a few other ICS roms
I came across these threads that documented the problem across other phones:
code.google.com/p/android/issues/detail?id=34942
code.google.com/p/android/issues/detail?id=36993
I've decided that I'm stuck with ICS until the official JB comes out.
Avram
awalts said:
I've tried all the same things you have and have had no success. The best wifi stability I got was the AOKP_d2att milestone1 w/ lean kernel combination, but wifi would stay connected for 3-5 minutes as opposed to 30 seconds.
I briefly tried CM9, but that still had wifi issues. I might try a few other ICS roms
I came across these threads that documented the problem across other phones:
code.google.com/p/android/issues/detail?id=34942
code.google.com/p/android/issues/detail?id=36993
I've decided that I'm stuck with ICS until the official JB comes out.
Avram
Click to expand...
Click to collapse
Well, I flashed Intergalactic, which is a modded Stock ICS TW ROM based on the AT&T firmware. Shortly after, I reinstalled TWRP recovery and flashed task's AOKP with ktoonsez's kernel, and WiFi works!
This is similar to an issue we had several weeks back with CM10 based ROMs on the HTC One X, you couldn't get LTE unless you flashed a ROM based on Android 4.0.3, it was something with CM10 obviously, because it was fixed in one of the October nightlies iirc.
Try flashing intergalactic and then task and ktoonsez aokp and see if your WiFi is working and let me know
Sent from my SGH-I747 using Tapatalk 2
Nope, no luck this way either.
Wifi under Intergalactic works fine.
TWRP flash AOKP milestone 1 alone, with the ktoonsez kernel, or with lean kernal and my wifi still hangs after ~1 minute of inactivity. The phone grinds to a halt. If you can get to the settings, it says that I am connected to my router, but shows no signal bars. If you can then turn wifi off, the phone un-freezes, and (except for no wifi access), the phone is back to normal. If you now turn wifi back on, it stays up for another minute or two and goes down again.
I'm open to any other suggestions.
Thanks though
Avram
i am using task and ktoonsez rom....when i first installed it, i noticed wifi dropping, it was annoying.
kinda dont happen anymore. The only 2 things i can think of that might have helped me is; i flashed a new modem i747MVLLE8(I'm with rogers), and under Wi-fi(menu/advanced), i unchecked poor connections.
also my router is 2.4ghz and 5ghz band, but i am connected to the 2.4ghz band.
hope it helps somehow.
I had horrible dropouts and speed with my last WiFi router. I forget the name/model but it was a new model (released this year) that had great reviews.
I went back to my old router and all my wifi problems disappeared.
I do get dropouts once in awhile still. But I haven't done a clean ROM install in awhile.
I am using a VZW CDMA Galaxy Nexus.
I was previously on CM10 stable and had no problems. After I flashed (with factory reset) the first CM10.1 nightly, I have noticed that when I wake the phone from sleep, my Wi-Fi is not turned on and it needs to re-connect.
I definitely have the "Keep Wi-Fi on during sleep" setting set to Always. This doesn't seem to work at all.
I have since been using the CM updater to continuously update to the latest nightly in hopes that this issue would be fixed. So far, no dice.
Anyone else have this issue?
Update: did a factory reset and flashed the newest 12/31 nightly. Still having the same issue.
OK another update.
After factory reset and flashing, WiFi worked perfectly until I restored my apps and stuff from TitaniumBackup.
So this time I just did not restore from TitaniumBackup and then everything worked fine.
UNTIL... I dirty flashed 1/9 nightly using CM updater. Now the problem is back!
Having the same problem. Wi-Fi worked perfectly on stock and this issue only started when I switched to CM.
EDIT: From reading a bit, seems to be fairly common problem. Maybe not just CM.
Hey another update.
I noticed that if I turn my Wi-Fi on and off from the actual settings app, this problem goes away.
The problem only happens if I activate my Wi-Fi from the Quick Settings toggle.
I may have found a fix, under WiFi settings, you can view the Advanced Settings, try turning Wi-Fi Optimization off, and settign the Wi-Fi region code, this fixed it for me. i'm not sure if both are required, my guess is that its the Wi-Fi Optimizations.
Destreyf said:
I may have found a fix, under WiFi settings, you can view the Advanced Settings, try turning Wi-Fi Optimization off, and settign the Wi-Fi region code, this fixed it for me. i'm not sure if both are required, my guess is that its the Wi-Fi Optimizations.
Click to expand...
Click to collapse
WiFi region settings is only for changing which frequencies/channels you are allowed to connect to (since it can vary from country to country which are allowed).
Sent from my Nexus 10 using Tapatalk 2
I gave up on this issue for almost a year and I expected maybe the internet would figure it out in time -- but alas it is now September 24th, 2013 and still I am having this issue!
In the time in between I have done a lot of dirty flashes, a lot of wipe + flash, tried multiple kernels (Stock, LeanKernel, Franco). Still this problem persists!
Did everyone else give up just like me?
Destreyf said:
I may have found a fix, under WiFi settings, you can view the Advanced Settings, try turning Wi-Fi Optimization off, and settign the Wi-Fi region code, this fixed it for me. i'm not sure if both are required, my guess is that its the Wi-Fi Optimizations.
Click to expand...
Click to collapse
Turned off Optimization. It seems to be working. Thank you very much. :good: