Database Info

Wifi connection connected but won't load pages

It said connected in the wifi setting and it shows bars but it just won't load any website in the browser .. anyone got a fix for this?

I have the same issue. Tried different combinations of restarting wifi, turning on/off cell data, on/off wifi calling, etc... all with no result. I've also tried on different networks (both public and private)-- it'd start working for a while and then all of a sudden stop and never work again.
Seems similar to the problem here: forums. t-mobile.c om/t5/T-Mobile-G2x/G2x-WiFi-DNS-issue-not-the-4G-switching-one/m-p/831439 (sorry there's a new user no link restriction)
Does anyone have any suggestions?
Thanks

coldest~~~ said:
It said connected in the wifi setting and it shows bars but it just won't load any website in the browser .. anyone got a fix for this?
Click to expand...
Click to collapse
is it specific to the browser or can you not move any data?
Idk, whenever I have had problems connecting to the tmo network, which is a separate issue.. it was always that wifi calling was still on even tho wifi was turned off. Every time I had probs w/ data on tmo network, it's been wifi calling.. Your case seems to be diff tho.
Is it specific to just your network or all other networks? Try shutting off wifi, reboot... then turn it on again? Idk.. just tossing out ideas.

Some found the root cause and I am posting his finding as I do have the same issue and can reproduce the error:
I think I have discovered a new WiFi-related bug in the G2x's software. I have witnessed this occurring on my phone, and have also reproduced it on a store demo unit. I believe it is unrelated to the switching-to-4G problem people are having with the My Account app, since it occurs even if I have set up the Google account on first boot after a factory reset.
The details of the problem are:
- Every so often, the phone randomly gets stuck in a state where it is not able to initiate any new connections that are made using a DNS name. Attempting to navigate to a web site, h**p://w*w.google.c*m for example, will result in a generic failure message.
- However, attempting to connect directly to an IP address instead of a DNS name works perfectly. For example, navigating to 74.125.225.16 will work fine and will load the Google home page.
- When the phone is in this state, using a DNS lookup tool such as "DNS Lookup" from the Marketplace *will* work, even when using the default DNS server address that the DHCP server is giving the phone.
- The problem has occurred for me when data is off and WiFi is on. I do not know if data being off is a requirement, since this is the way I usually run the phone, so this may be coincidental.
- Switching WiFi off and back on again will *sometimes* work to solve the problem, but sometimes will not. When this doesn't work, switching WiFi off, then switching data on, then back off again, and then finally switching WiFi back on again will occasionally correct the problem. However, I have seen situations where none of these things worked, and the only way to get DNS working again was to factory reset the phone.
- I haven't figured out the exact pattern yet, but this issue seems to occur when the phone has been inactive for a certain period of time. I have often discovered that the phone is in this state upon waking up in the morning after leaving the phone on the charger overnight.
- I have, however, found a method to reproduce the problem that seems to work fairly consistently:
1. Turn WiFi on, and data off.
2. Power cycle the phone.
3. When the phone starts up, start the browser and attempt to browse to w*w.google.c*m. It should fail.
4. Try to browse to 74.125.225.16. It should work.
Just wanted to get this issue in the forums to see how many others have been noticing the same thing.

I know that once the device has less than 10% battery it automatically turns the WiFi off to save battery power. Were the devices this was happening on have a low battery?

Fully charged. It even happens when pluged in with the charger.

My Wifi wouldn't even work if I froze it with Bloat Freezer. It has to run in the background for wifi to work. I found that Wifi can get really inconsistent with it disabled.

smartloom said:
Som
- I haven't figured out the exact pattern yet, but this issue seems to occur when the phone has been inactive for a certain period of time. I have often discovered that the phone is in this state upon waking up in the morning after leaving the phone on the charger .
Click to expand...
Click to collapse
Same problem here. After about 30 minutes of being idle, as soon as I pick up the phone it tries to connect 2g/4g. The log are saying theres no connection, so it appears that wifi its going to sleep and not waking up so android is trying to connect 2g/4g
Really starting to be a pain
I have frozen the bloat, and I think the problem is getting worse.
Toggle airplane mode is a quick workaround to get wifi to wake up
Sent from my LG-P999 using XDA App

Same thing happened to me, I did 2 factory resets, and it seems it has been fixed, don't really know what causes it.
Sent from my LG-P999 using XDA App

This may or may not be related, but...
It looks like I found a hacky fix for the dns/wifi/4g bug: install "Set DNS" from the market.
Now when I go into market, and display my downloaded apps, it jumps from wifi to 4g then back to wifi as it should, fast.
Whether or not it should even do go to 4g is debatable, all I can say is my 2 Galaxy Tabs had the same behavior.
If everyones connectivity issues are really due to the DNS settings getting wiped out, then this will work around the problem until I/we find the location of the actual bug.

Would you guys having this problem also post it here?
http://www.lgforum.com/forum/boards/general/lg/topics/g2x-wifi-problems
Thanks.
I figure the more people that post there, the more the chances are of LG fixing it quickly.

Work around:
enable airplane mode
reboot
enable wifi
wait a few seconds after the wifi connects, background crap stops
disable airplane mode.
The set dns app looks like a winner. Haven't tried it but that's what's
wrong.
The freezing and other suggestions are all useless crap.

Updates...
I did a factory reset and installed JuiceDefender (I don't know which one worked) but it seems to be all fine now... will update if things become problematic again

I've been having this problem as well. I've always been able to fix it by toggling WiFi off and back on again. I downloaded SetDNS and when it happened again last night I tried that and it worked great.
Glad to see it's a software problem and not a hardware problem.

same problem here. hopefully it won't happen in cyanogen mod

boylan said:
Work around:
enable airplane mode
reboot
enable wifi
wait a few seconds after the wifi connects, background crap stops
disable airplane mode.
The set dns app looks like a winner. Haven't tried it but that's what's
wrong.
The freezing and other suggestions are all useless crap.
Click to expand...
Click to collapse
This fixed the problem, at least until the next time I reboot my phone

How do you use SetDNS? This software bug in G2X reboots my router (DGL-4500) sometimes.

Question bout SetDNS app
Does the phone have to be rooted to use the setdns app? I try to use it but it says "Cannot get root. App will not function."

Wifi unable to connect from Transformer's Sleep Mode

Guys, I have a problem with the Transformer and it's Wifi that is driving me mad!
Regardless if I have wifi running in the background or put in Plane Mode when I turn on the screen after a short interval I notice the wifi has dropped and there is no longer an internet connection.
Not only that I can not get it to start again unless I switch off the TF and reboot.
On investigation on the settings, when I click on Wireless & Networks I notice the right hand pane of Wifi & Wifi settings to be flashing as if it is trying to connect but gets locked out over and over. As such you can not access any of the wireless settings.
I would appreciate any assistance you can shed on this problem.
Many thanks in advance.
Beards
EDITED:
I believe I have now found what was causing the problem and have explained in detail in Post 10 below.
Basically I found it was after updating to v3.2.1 ~ the WiFi Settings/WiFi Disconnection Policy 'When screen is tuned off' & 'Never when plugged in' was interfering with the state of WiFi, causing it to poll and repeatedly try and switch itself back on, thus a constant flash and inability to activate WiFi..

Ddvvvvvvvvv

Fire n mage said:
Ddvvvvvvvvv
Click to expand...
Click to collapse
Sorry... what does that mean?

Searched the internet, and discovered two things, I did both.
1) Removed the maps update.
2) Changed the the channel on my router to 6
Works fine now.

I'm having this same problem for the past few weeks. Whenever the WIFI goes to sleep, I cannot turn it on unless I reboot my Transformer. It's sort of annoying.

It's got to be software orientated that is interfering with the TF.
I can not think of anything other than software causing it to continually 'flash' as it tries over and over again to connect.
I need to look into date captured software updates to see if I can narrow down the culprit.
Looks like I have a long job ahead of me..... sigh!

I got the same issue, after maps update, but apparently It's got to do with use wifi for determining your location, if i switch this off , tablet connects fine after returning from sleep.
regards
kef

kefje27 said:
I got the same issue, after maps update, but apparently It's got to do with use wifi for determining your location, if i switch this off , tablet connects fine after returning from sleep.
regards
kef
Click to expand...
Click to collapse
Mine has nothing to do with Maps and it's doing this continuous polling even when woken from Plane Mode and then trying to switch wifi back on.
I have a theory and am looking at it.... Will report back later.

Any news yet?
Sent from my Transformer TF101 using Tapatalk

LordNickerchen said:
Any news yet?
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Yes, I've worked out what the problem for me was and was just coming back to report when I read your post....
Basically for me it is to do with Settings/Wireless & Networks/Wifi Settings/Wifi Disconnection Policy.
After I updated to 3.2.1 I changed the policy from 'Never (uses more battery power)' to 'When screen is tuned off'.
Thinking about it the problem has only been since I changed the policy.
So, I changed it back to 'Never' and the wifi remained on and the problem I was getting disappeared.
I then changed it back to 'When screen is tuned off' and the problem came back.
I then altered it to 'Never when plugged in' with the TF not plugged in and the problem was still there.
Plugging the TF in and the problem disappeared.
Only by changing it back to 'Never' when not plugged in does my wifi remain on ~ which if you think about it is exactly what it is meant to do.
Therefore, for me it would appear changing the policy to turn off the wifi is causing this issue of when you wake the phone up from sleep you can not reactivate the wifi and when looking at the wireless settings the whole of the right hand page of wireless settings are continuously flashing thus not allowing you to access and alter them.
At that point the only way you can reactivate wifi is by doing a power down and reboot.
So guys...... Has anyone else noticed the wifi disconnection policy effecting your wifi from sleep?

Mine stopped reconnecting again last night, the tablet would continuously reboot.
The only solution was to reboot the router.
I will try the keep on and I have turnoff wifi location.
Lets see

FSB said:
Mine stopped reconnecting again last night, the tablet would continuously reboot.
The only solution was to reboot the router.
I will try the keep on and I have turnoff wifi location.
Lets see
Click to expand...
Click to collapse
How did you get on with changing the wifi disconnection policy?

Changing the disconnection policy never worked, note sure if this is the best solution, as I recon it will drain the battery.

FSB said:
Changing the disconnection policy never worked, note sure if this is the best solution, as I recon it will drain the battery.
Click to expand...
Click to collapse
Interesting.... as it is the only way I can get a stable WiFi that will turn back on from Screen Off.
Even though it says the battery may use more power it doesn't seem all that much different if anything at all... Prior to the latest update I had the policy set to 'When screen is tuned off'.
After the update it defaulted back to 'Never (uses more battery power)' and again after changing it back to 'When screen is tuned off' this is when my problem started.
I am thinking this is something to do with my TF as no one else has reported a problem with WiFi and the 'When screen is tuned off' policy.

I just re-read my post.
It should read
Changing the disconnection policy to "never". Worked.
Note sure if this is the best solution, as I recon it will drain the battery.
Sorry.
What you describe is exactly what happened to mine.

FSB said:
I just re-read my post.
It should read
Changing the disconnection policy to "never". Worked.
Note sure if this is the best solution, as I recon it will drain the battery.
Sorry.
What you describe is exactly what happened to mine.
Click to expand...
Click to collapse
Thanks.... This now makes a lot of sense in that it points to a possible bug with the WiFi policies.

This is driving me crazy. I have tried everythinig mentioned, but my TF still goes through the wifi connection loop. Gotta be software related...

tn8shooter said:
This is driving me crazy. I have tried everythinig mentioned, but my TF still goes through the wifi connection loop. Gotta be software related...
Click to expand...
Click to collapse
Did you try changing the Wifi disconnection policy to 'Never (uses more battery power)'?
That sorted it out for me.
It's since Honeycomb 3.2.1 came in I now find I can not use any other disconnection policy.

This happens to me if I select anything other than "Never (uses more battery power)"
I have found though that if I uninstall the google maps update, and deselect Wifi Localization, that I can have the TF set to "Never when plugged in" or "When screen is turned off".
( see: google.com/support/forum/p/Google+Mobile/thread?tid=4778cb9a3f187b75&hl=en ) (sorry for broken link - I am new and cannot post these)
So it seems like either a problem with Google maps (that may be specific to the TF), or a problem with the TF firmware?

Wifi problem

Sometimes, my wifi will hang When i switch the wifi on, later the wifi state is showing as turning off and keep on the state until i reboot the phone, finally the wifi can finally turned on. I encounter this issue no matter i was on froyo or gb!!! it is anonying that i must restart the phone several time to keep the wifi working.
Sent from my LG-P920 using XDA

I want to know if any of optimus 3d user have encountered this problem, if not too much users have this problem, i will send back to lg for repair. I want to say when i switch on wifi for ten time. I will encounter this problem for three time no matter which rom or which version of android i am using.because i have encounter this problem in many roms
Sent from my LG-P920 using XDA

it's a common issue, not sure if just with GB, the problem with this is that your battery drains too fast when this happens
just check if the phone warms up if so u have an issue then just restart
lg has not told anything about this issue, they thinkg it's an specific issue from one carrier's fw but it looks like it's in general with GB, my old x10 had the same issue but no battery drain

But i have this issue when i using froyo. Now i am using froyo but have this issue two times a days. Its very annoying to me yo know
Sent from my LG-P920 using XDA

No solution yet!?
or it just depend on the firmware i installed!?
Btw, thank you for your reply
Sent from my LG-P920 using XDA

There isn't any real solution. It happens to me as well as to other people (search the O3D threads here and you'll find many reporting the same), no matter if you have Froyo or GB.
However, in my case it doesn't happen two times a day but less often. It never occurs when I wake up my phone and wifi reconnects. It only happens when I turn on/off the airplane mode (but not all the times).
Do you have this issue when the phone is waking up normally (with the wifi always on) or when you turn on/off the airplane mode or turn off/on the wifi manually?

botson71 said:
There isn't any real solution. It happens to me as well as to other people (search the O3D threads here and you'll find many reporting the same), no matter if you have Froyo or GB.
However, in my case it doesn't happen two times a day but less often. It never occurs when I wake up my phone and wifi reconnects. It only happens when I turn on/off the airplane mode (but not all the times).
Do you have this issue when the phone is waking up normally (with the wifi always on) or when you turn on/off the airplane mode or turn off/on the wifi manually?
Click to expand...
Click to collapse
if only occur in turning on/off the airplane, it will be fine for me as i seldom use the airplane mode. however, the issue occur when i turn on or off the wifi manually. i have tried to turn off and on the wifi repeated ten times when the phone restart, i have no problem. however, after i close the wifi for about 1 or 2 hour and enable again, it sometime have the problem when i switch on the wifi. i really have no ideas why this problem will occur.

Well when you turn the wifi on/off manually, I guess that it's the same thing (for the wifi connectivity) like turning on/off the airplane mode manually, so it causes the same problem.
Do you have this issue when you just wake up your phone (with wifi on)? If so, you could keep your wifi always on when you outside from home/work. If it's not connected it doesn't consume much battery.

botson71 said:
Well when you turn the wifi on/off manually, I guess that it's the same thing (for the wifi connectivity) like turning on/off the airplane mode manually, so it causes the same problem.
Do you have this issue when you just wake up your phone (with wifi on)? If so, you could keep your wifi always on when you outside from home/work. If it's not connected it doesn't consume much battery.
Click to expand...
Click to collapse
when the wifi problem happens, i must reboot the phone manually, then the wifi will switch on automatically after the phone has rebooted. however, i discover that, wifi drain battery very much when compare to just open 2G network alone, therefore, i would like to close wifi when i just put it to standby. i think this is not a real solution and i have this problem two time a day. it is very annoying actually.
thank you for your reply!!!

I posted this already in thread i started labeled not too clearly http://forum.xda-developers.com/showthread.php?t=1519436
It's a process called tiwlan_wq which starts using cpu @ 48% constantly and drains battery quickly.
No idea how to solve this i've kept the wifi at standard setting of off when phone is in standby or even on always but this occurs randomly.
I thought new v20g rom would have sorted out some issues but no and i'm dead bent on selling this POS LG phone.

sak500 said:
I posted this already in thread i started labeled not too clearly http://forum.xda-developers.com/showthread.php?t=1519436
It's a process called tiwlan_wq which starts using cpu @ 48% constantly and drains battery quickly.
No idea how to solve this i've kept the wifi at standard setting of off when phone is in standby or even on always but this occurs randomly.
I thought new v20g rom would have sorted out some issues but no and i'm dead bent on selling this POS LG phone.
Click to expand...
Click to collapse
try to set the wifi policy to "never", however, the problem still have, but battery drain is lessened i think

WiFi constantly RECEIVING (no apps running)

Basically I am on Nexus S JellyBean 100% STOCK and this issues is happening with work WIFI.
How I noticed it...when I am at home I drop 1% battery on Wifi per hour. 10hours = 10% (sometimes less).
I go to work on the Wifi, I DONT USE ANYTHING ON THE PHONE and the battery is DRAINING LIKE CRAZY!!! 5%/h or more!!!
( I am in airplane mode in both place)
So I was thinking, WTF with this work wifi, i am not doing anything at all on it. Then I look at my wifi icon I have a constant RECEIVE icon. And I bet my phone does not go to sleep or something.
So why in the world my work wifi is draining my battery and the one at home is not. I will check tonight but I dont think I have traffic like this. I am registering 5-6kbytes/s for nothing. There was an explanation given in one of the links below about existing wifi traffic that goes through my phone but I do not agree with it fully. YEs sure there are several pings and beacon emitted back and forth but i do not think it is enough to cause 5-6kbytes/sec . The wifi is not in Monitor mode and it only receives the packets destined to my phone.
This is madness!!!! BTW When I had a different kernel back on ICS this behavior stopped. I will try to monitor again. So there is definitely some kernel switch that can force the wifi to idle.
Here are the links where they discuss this somewhat.
http://forum.xda-developers.com/showthread.php?t=1738171
http://forums.androidcentral.com/verizon-galaxy-s-iii/188929-your-wifi-constantly-downloading.html

kalinusa said:
Basically I am on Nexus S JellyBean 100% STOCK and this issues is happening with work WIFI.
How I noticed it...when I am at home I drop 1% battery on Wifi per hour. 10hours = 10% (sometimes less).
I go to work on the Wifi, I DONT USE ANYTHING ON THE PHONE and the battery is DRAINING LIKE CRAZY!!! 5%/h or more!!!
( I am in airplane mode in both place)
So I was thinking, WTF with this work wifi, i am not doing anything at all on it. Then I look at my wifi icon I have a constant RECEIVE icon. And I bet my phone does not go to sleep or something.
So why in the world my work wifi is draining my battery and the one at home is not. I will check tonight but I dont think I have traffic like this. I am registering 5-6kbytes/s for nothing. There was an explanation given in one of the links below about existing wifi traffic that goes through my phone but I do not agree with it fully. YEs sure there are several pings and beacon emitted back and forth but i do not think it is enough to cause 5-6kbytes/sec . The wifi is not in Monitor mode and it only receives the packets destined to my phone.
This is madness!!!! BTW When I had a different kernel back on ICS this behavior stopped. I will try to monitor again. So there is definitely some kernel switch that can force the wifi to idle.
Here are the links where they discuss this somewhat.
http://forum.xda-developers.com/showthread.php?t=1738171
http://forums.androidcentral.com/verizon-galaxy-s-iii/188929-your-wifi-constantly-downloading.html
Click to expand...
Click to collapse
for now what u can do, is to set your wifi to go to sleep when the screen is off

Real Cause of battery drain/wake lock in MJ7/MK2 and fix

I am posting this as it is very hard to wade through information in forums. I'm hoping the following will be useful to those, who like me, experienced battery drain caused by Android Wake Locks after upgrading to MJ7 / MK2.
I am 100% certain the battery drain in MJ7/MK2 is caused by connecting to WIFI networks in environments that have multiple AP's. i.e. once WIFI roams from one AP to another the battery drain starts. All my testing confirms this - consistently. I have actually tested being connected to one AP in a multiple AP environment for a long period and observed no wake locks on Android OS. Yet as soon I move to another location (i.e when I make it roam) the wake lock and battery drain starts. All this rubbish about clearing cache, factory resetting, nobbling your phone and so on are all stabs in the dark - It's the reboot that temporarily fixes it so people mistakenly put two and two together. So, if you use WIFI in a large building with multiple AP's try forgetting the network and not connecting to WIFI with multiple AP's. If you have already connected to a SSID with multiple AP's reboot your phone because once the battery drain starts it does not seem to stop until you reboot. You don't have to disable WIFI at all as scanning does not cause the wake lock. I have tested this thoroughly and so far I have not had any battery drain since not connecting to SSIDs with multiple APs. I can also back this up as I can create battery drain at will by simply connecting to a WIFI environment with an SSID distributed over multiple AD's.
My battery life is again fantastic and I am happy now that I know the cause.
Pretty poor testing by Samsung/Google as I see in past versions of Android Roaming has been an issue.

mongoose3800 said:
I am posting this as it is very hard to wade through information in forums. I'm hoping the following will be useful to those, who like me, experienced battery drain caused by Android Wake Locks after upgrading to MJ7 / MK2.
I am 100% certain the battery drain in MJ7/MK2 is caused by connecting to WIFI networks in environments that have multiple AP's. i.e. once WIFI roams from one AP to another the battery drain starts. All my testing confirms this - consistently. I have actually tested being connected to one AP in a multiple AP environment for a long period and observed no wake locks on Android OS. Yet as soon I move to another location (i.e when I make it roam) the wake lock and battery drain starts. All this rubbish about clearing cache, factory resetting, nobbling your phone and so on are all stabs in the dark - It's the reboot that temporarily fixes it so people mistakenly put two and two together. So, if you use WIFI in a large building with multiple AP's try forgetting the network and not connecting to WIFI with multiple AP's. If you have already connected to a SSID with multiple AP's reboot your phone because once the battery drain starts it does not seem to stop until you reboot. You don't have to disable WIFI at all as scanning does not cause the wake lock. I have tested this thoroughly and so far I have not had any battery drain since not connecting to SSIDs with multiple APs. I can also back this up as I can create battery drain at will by simply connecting to a WIFI environment with an SSID distributed over multiple AD's.
My battery life is again fantastic and I am happy now that I know the cause.
Pretty poor testing by Samsung/Google as I see in past versions of Android Roaming has been an issue.
Click to expand...
Click to collapse
Funny thing is that when i am using mobile data the drain is worse, So I'm pretty sure this is not the main issue man. Also, I have a Mobile 'WiFi' router. Only me has WiFi connection in my entire hostel. So I don't really think it's the issue. Good finds tho! It will definitely help someone. Cheers!

Agree with stanley, this is not the only cause.

39089665568
vndnguyen said:
Agree with stanley, this is not the only cause.
Click to expand...
Click to collapse
Agreed. There are many things that will cause elevated use. But Im talking the rapid drain that occurs when you're not using the phone. Ever since taking the action I describbed my battery life has been excellent. Eg 94% after 14 odd hours with no use. And, I'm still connecting to my home wifi. Beforehand it could be below 60% with no use and this is the real problem people are talking about. Hope that makes sense.

Actually it's the opposite. If you set up your modem to have a separate AP for the phone and isolate it from the rest of the network, you'll have much better battery life on wifi because you'll stop your phone from waking up by broadcast packets.

aydc said:
Actually it's the opposite. If you set up your modem to have a separate AP for the phone and isolate it from the rest of the network, you'll have much better battery life on wifi because you'll stop your phone from waking up by broadcast packets.
Click to expand...
Click to collapse
I don't get it. What am I supposed to do exactly?

aydc said:
Actually it's the opposite. If you set up your modem to have a separate AP for the phone and isolate it from the rest of the network, you'll have much better battery life on wifi because you'll stop your phone from waking up by broadcast packets.
Click to expand...
Click to collapse
What about unicast traffic? i know the Client Isolation sort of "VLAN"s every client associated, just wondering if that might affect client to client communication?
Good point btw, im also wondering how many services wake the damn thing up, waking up over network is more an enterprise workstation scenario...to me it sounds like HotSpot 2.0 services being active, but i have not enabled it.
HS2.0 can let client and AP sort of talk without associating.

Nazty111 said:
I don't get it. What am I supposed to do exactly?
Click to expand...
Click to collapse
Most modems have a sort of 'guest mode' or allow you to open another access point and isolate it from the rest of the network. If you connect your phone to this guest access point or isolated access point, your phone will reach internet without problems, but will not reach the local network through the router. Nor will any other device on the network reach your phone.
Most of the problems with Wifi draining battery, like wifi wakelocks, occurs because devices on the network keep sending packets to the phone waking it up. With the method I describe above, you will isolate your phone and the phone will remain in deep sleep, significantly increasing battery life.

aydc said:
Most modems have a sort of 'guest mode' or allow you to open another access point and isolate it from the rest of the network. If you connect your phone to this guest access point or isolated access point, your phone will reach internet without problems, but will not reach the local network through the router. Nor will any other device on the network reach your phone.
Most of the problems with Wifi draining battery, like wifi wakelocks, occurs because devices on the network keep sending packets to the phone waking it up. With the method I describe above, you will isolate your phone and the phone will remain in deep sleep, significantly increasing battery life.
Click to expand...
Click to collapse
This is very true. Back on my old GNex i used to have crazy wifi wakelocks and I couldn't for the life of me figure it out. I never figured it out, actually. But I am positive it is one of the two PC's on my network that are broadcasting packets across the network, waking my phone up. I haven't had time to extensively test the wifi wakelock in the environment i've previously encountered it in to see if it still applies, but since I haven't changed anything regarding any of the two computers involved on that network, I'm positive I will have the same wifi wakelock issue when I get back and test. Is there a way (besides using Shark) to see what programs are broadcasting packets across the network?
But to get back on topic, I am experiencing battery drain connected to ONE router with ONE AP. I am in an apartment building with several other routers nearby, though. Maybe they are broadcasting packets somehow that the kernel is interpreting and keeping the phone awake? However it seems as though the Android OS bug keeps coming back for everyone no matter what, even in airplane mode.

Wifi has evolved a lot the last decade, not just by technology standards but into integration as well. carriers use them as small cells, we'll see them more often in the future (malls, stadiums, etc), and HS2.0 adds to make it a bit more seamless, they call it offload, taking your data needs through small wifi cells rather then the macro cells (3g, 4g), hence offload.
my point is that they would have never invested in that if the wifi chips inside consumer products were not efficient enough, so nearby APs shouldnt be a problem at all. But im still puzzled for what would one need the waking up process through wifi?
If Wifi is the general bugger, then somebody throw an eye on the Passport service, thats the consumer name for HS 2.0 services.
PS, tested AP Isolation on my sh!tty WRT120N, no difference unfortuantely.

Will there be a future update from Sammy or will we get Kitkat directly
Sent from my SM-N900 using Tapatalk

Just a follow up. I have still had no battery drain since avoiding connecting to wifi networks that use multiple APs. Now, i only connect to wifi networks where i know there is only one AP. Before I stumbled across this the drain and Android os wake lock was bad, really bad, after I had connected to large wifi networks - I just hadn't put two and two together. This is more than coincidence - my testing is sound and replicable. And, this week I have been in remote areas with weak to no 3g signal and the battery life has still been fantastic and no wake locks so that sort of rules that out - Sure there is a little increase in battery usage but nothing dramatic, something to be expected and certainly not something to complain about. I have seen many claims to fix battery drain but these are just fine tuning and not addressing the major drain caused by Android OS wake locks. Clearly, there must be an issue with the wifi software driver in MJ7/MK2 and I hope Samsung/Google are aware of it. The annoying thing is getting Samsung to acknowledge the issue and take feedback.

I get wake locks even if I manually turn wifi off and only use data. When I use wifi i am connected to only one AP and I still get wake locks. The wake locks aren't apps, they are "Powermanager.wakelocks" and "Powermanager.Display" and show up as "Android OS" in battery settings.
I am still not convinced avoiding multiple AP wifi networks is the one-for-all solution for everyone.
However, I have put "wifi on during sleep" to "never," yet my phone slept maybe 50% yesterday but wifi was on 100% of the time. Why is this? Shouldn't it have turned off the 50% that the phone was sleeping?
Something is weird with the wifi module..
Sent from my SM-N9005 using xda app-developers app

EddieN said:
I get wake locks even if I manually turn wifi off and only use data. When I use wifi i am connected to only one AP and I still get wake locks. The wake locks aren't apps, they are "Powermanager.wakelocks" and "Powermanager.Display" and show up as "Android OS" in battery settings.
I am still not convinced avoiding multiple AP wifi networks is the one-for-all solution for everyone.
However, I have put "wifi on during sleep" to "never," yet my phone slept maybe 50% yesterday but wifi was on 100% of the time. Why is this? Shouldn't it have turned off the 50% that the phone was sleeping?
Something is weird with the wifi module..
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Have you ruled out any other wifi connections? Have you tried rebooting if you have connected to another wifi network? Have you tried forgetting all wifi networks? Reboot after forgetting all networks. Then give it a couple of days with out connecting to any wifi network - just a test to confirm it is wifi related. I tend to think setting wifi to never on during sleep makes no difference - I had previously tried it too. Once the drain starts the only way to stop it is to reboot.

mongoose3800 said:
Have you ruled out any other wifi connections? Have you tried rebooting if you have connected to another wifi network? Have you tried forgetting all wifi networks? Reboot after forgetting all networks. Then give it a couple of days with out connecting to any wifi network - just a test to confirm it is wifi related. I tend to think setting wifi to never on during sleep makes no difference - I had previously tried it too. Once the drain starts the only way to stop it is to reboot.
Click to expand...
Click to collapse
Yes, just last week I was on another Wifi AP about ~300km away (totally different environment) and I still had the same wake locks. I have rebooted when connecting to another wifi network. I have tried forgetting all wifi networks i have connected to, and reconnecting to them. I have also rebooted once forgetting networks. During this time I also took the liberty of doing the normal rounds of disabling location services etc. before rebooting, but nevertheless i did reboot once forgetting the network. All networks I have been connected to have been single-AP wifi networks.
I have not let it sit for a few days without connecting to any wifi networks. That's the only thing I haven't tried. However I have let it go a whole day with wifi turned off (and only data enabled), but the same wakelocks persisted. For me it's always "Powermanage.Display" and "Powermanager.Wakelocks" no matter how long i just let my phone sit around with the screen turned off. I have it right beside me so I always have visual access to the screen in case the phone wakes up on its own, but it never has. I guess I could try turning wifi off for a few days and seeing how it fares, but I doubt I will see any difference (wake lock wise).
I'm thinking something is strange with the wifi module anyway. Surely wifi should turn off by itself once the phone sleeps, right? Like I said in my other post, my phone slept maybe 50-60% of the time on a 14 hour day. That means Wifi should have been on 40-50% of that time, and off 50-60% since the phone technically should have been sleeping. Yet I can see in the battery settings menu that wifi is a solid green bar all across the 14 hours.

EddieN said:
Yes, just last week I was on another Wifi AP about ~300km away (totally different environment) and I still had the same wake locks. I have rebooted when connecting to another wifi network. I have tried forgetting all wifi networks i have connected to, and reconnecting to them. I have also rebooted once forgetting networks. During this time I also took the liberty of doing the normal rounds of disabling location services etc. before rebooting, but nevertheless i did reboot once forgetting the network. All networks I have been connected to have been single-AP wifi networks.
I have not let it sit for a few days without connecting to any wifi networks. That's the only thing I haven't tried. However I have let it go a whole day with wifi turned off (and only data enabled), but the same wakelocks persisted. For me it's always "Powermanage.Display" and "Powermanager.Wakelocks" no matter how long i just let my phone sit around with the screen turned off. I have it right beside me so I always have visual access to the screen in case the phone wakes up on its own, but it never has. I guess I could try turning wifi off for a few days and seeing how it fares, but I doubt I will see any difference (wake lock wise).
I'm thinking something is strange with the wifi module anyway. Surely wifi should turn off by itself once the phone sleeps, right? Like I said in my other post, my phone slept maybe 50-60% of the time on a 14 hour day. That means Wifi should have been on 40-50% of that time, and off 50-60% since the phone technically should have been sleeping. Yet I can see in the battery settings menu that wifi is a solid green bar all across the 14 hours.
Click to expand...
Click to collapse
Well that's interesting. At least in both cases we know it's Wi Fi. I wonder if it's something if it comes down to the type of connection. Eg 2.4 vs 5ghz

mongoose3800 said:
Well that's interesting. At least in both cases we know it's Wi Fi. I wonder if it's something if it comes down to the type of connection. Eg 2.4 vs 5ghz
Click to expand...
Click to collapse
It could be. Both networks I have been connected to have been 2.4GHz Wireless-N capable routers. I just find it odd that a lot of things don't add up when looking at awake times in Settings -> Battery and comparing it to kernel/partial wakelocks in BBS/WLD/CPU Spy. All of the times seem to be roughly in the same ballpark, but they never add up to correspond to each other. Surely there must be information missing in this regard.

I can confirm the WiFi issue on my N9005 but there's another one.
1. Wifi: I experienced this at my university, where we have good Wifi coverage on the whole campus. They use Radius for logging in. After using Wifi for about 15min, I had these wakelocks, which didn't stop until I rebooted the phone. Since I knew this, I haven't been using Wifi there any more. But: In the meantime, I did a factory reset and got this little stability update. A few days ago, I gave it a try again. Used Wifi at university for ~25min and hat no issues. Maybe it's gone, I will test again some day.
2. I had an app called "gentle alarm". On my GNexus, which I used before my Note 3, I also had wakelocks, but couldn't figure out what it was, since wakelock detector, better battery stats etc. didn't show more than PowermanagerService.Wakelocks/Display. So I got my new Note 3 and still had these Wakelocks - I did much Monitoring and: It was this tiny alarm app. Very funny: After having excluded every other possibility and having the wakelocks active I uninstalled the app on my Note 3 and it instantly rebooted!
Great battery life now.
Hope this helps someone. BTW: The Wifi issue on larger networks seems to be a problem not only on Samsung phones, many people are experiencing this (e.g. found similar reports for Nexus 5...).

duffmannr3 said:
I can confirm the WiFi issue on my N9005 but there's another one.
1. Wifi: I experienced this at my university, where we have good Wifi coverage on the whole campus. They use Radius for logging in. After using Wifi for about 15min, I had these wakelocks, which didn't stop until I rebooted the phone. Since I knew this, I haven't been using Wifi there any more. But: In the meantime, I did a factory reset and got this little stability update. A few days ago, I gave it a try again. Used Wifi at university for ~25min and hat no issues. Maybe it's gone, I will test again some day.
2. I had an app called "gentle alarm". On my GNexus, which I used before my Note 3, I also had wakelocks, but couldn't figure out what it was, since wakelock detector, better battery stats etc. didn't show more than PowermanagerService.Wakelocks/Display. So I got my new Note 3 and still had these Wakelocks - I did much Monitoring and: It was this tiny alarm app. Very funny: After having excluded every other possibility and having the wakelocks active I uninstalled the app on my Note 3 and it instantly rebooted!
Great battery life now.
Hope this helps someone. BTW: The Wifi issue on larger networks seems to be a problem not only on Samsung phones, many people are experiencing this (e.g. found similar reports for Nexus 5...).
Click to expand...
Click to collapse
Thanks for your input. Is the wifi issue you are talking about the fact that it doesnt turn off when having "wifi on during sleep -> never" set? Or the multiple-AP issue the thread is talking about?
What stability update is it that you have received? What country are you in and what firmware are you using? Did you get this stability update while on MJ7/MK2 firmware? I haven't received any notification for a stability update OTA...
Thanks for the Powermanager.Display/Wakelock issue. I guess I will have to sift through my apps and uninstall each, one by one, to see if the wakelocks disappear. If not, there is some other issue

EddieN said:
Is the wifi issue you are talking about the fact that it doesnt turn off when having "wifi on during sleep -> never" set? Or the multiple-AP issue the thread is talking about?
Click to expand...
Click to collapse
It's the issue about "multiple" APs, but I don't think that it is about the number of APs. What I have read is that there is so much traffic on those big networks, e.g. broadcasts from other devices. I don't know how it should be with your problem that wifi doesn't turn off - can you see if it's reconnecting after some standby time? If yes, then wifi is turned off during sleep, but is just not shown in statistics.
EddieN said:
What stability update is it that you have received? What country are you in and what firmware are you using? Did you get this stability update while on MJ7/MK2 firmware? I haven't received any notification for a stability update OTA...
Click to expand...
Click to collapse
I'm currently on MJ7/MK2. My device is unbranded and I'm living in Germany. It came on 26th of December and was about 30MB or so.
EddieN said:
Thanks for the Powermanager.Display/Wakelock issue. I guess I will have to sift through my apps and uninstall each, one by one, to see if the wakelocks disappear. If not, there is some other issue
Click to expand...
Click to collapse
It's definitely worth a try! There was absolutely no hint that pointed to this one app. I started with having a look at the battery statistics ~every 30min after a fresh reboot. After a few days it was clear that it only could be the alarm app, battery draining started only in the morning.