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."

Atrix 2 known wifi problems?

I have an Atrix 2. It has been replaced twice by AT&T due to this problem. I have factory reset each phone and tried every battery mode, data saver, sleep policy and wifi channel.
The problem:
The wifi turns off by itself! not sleep, off! As in the checked box is unchecked. The phone does it during use and when not being used. The timing between instances is random. The wifi sometimes stays on for hours. Other times it wont last five minutes. I have 4 other wifi devices connected by wifi to my secured router.
Note: I travel across the country for work and the problem occurs at airports, hotels, mcdonalds, ect.
I have called Motorola and their only option is to send it to the with no replacement. I could use some help. I have been searching online and others with this problem dont persist, they simply state that unsecuring their router fixed the problem. That is not an option for me as the routers are not mine.
Any input will be greatly appreciated.

Hi, I recently noticed this problem started after I installed the ATT Smart Wi-FI app. Mine will connect then turn off, wait a second turn back on then I get the WIFI networks avail message and I check it and it's not connecting to the network til I tell it too then it will stay connected all day.

I"ve had my atrix 2 for about a little over a month. It's doing the same thing. Wifi will randomly shut off. I have to go into the settings to turn it back on. It will work fine for a little while then just shuts off again. Does anyone know if this seems to be hardware or software related. I've tried different apps and WiFi sleep settings to no avail. I really like the atrix but this is kind of annoying.

I have the same issue also, except I have top reboot my phone for wifi to work again.
Sent from my MB865 using XDA App

i have the same problem, it's not my wifi connection, but the actual wifi setting turns off whenever i turn off my screen and yes, i've set the wifi sleep policy to "never", so that's not the problem. i've also tried "never when plugged in" and "when screen turns off" and i still get the same problem. i was thinking about going to at&t and asking them about it but decided to come here first.
(a white iphone 4 is looking better and better ) can anyone help?

I had this problem but after I disabled the power saver option under battery and data (set it back to performance) it went away and Wi-Fi works perfect.

Tried different battery saver settings as well, nothing changed.
Sent from my MB865 using XDA App

[Q] Wi-fi Sleeping Problems

Heey,
I'm running the Onecosmic RC3 rom (SGS)now. I always have my wifi on. But when I don't use my phone for like ten minutes, the wifi turns grey in the notification area.
I saw that some people are having the same problem, but since I'm a new member, I'm not allowed to react within the forum of the RC3.1 forum.
My wifi 'sleep' setting is set to never, I've wiped all data before, but it doesn't solve the problem.
Can anyone help me, it's very anoying, because i can't get any mails or other messages when I haven't turn my phone off for 10 minutes. Only turning wifi off and on seems to give me a connection again.
with kind regards

Try this app:
https://market.android.com/details?id=eu.thedarken.wl
Make it aquire a PARTIAL WAKE LOCK and see if that fixes your problem.
It will prevent the cpu from going into a deep sleep and disconnecting the wifi.

Thank u , i try this,
I'll report back
btw. doesn't this drain battery ?

Everything "drains" battery.
You can either have wifi and additional battery drain or no wifi and no additional drain.

Okay I'm back.
I'd have replied earlier, but there was an outage, and for some reason I happy about that.
Because of the fact that found out that it doesn't solve my problem enteirly. When I'm at home than yeah it does. But the moment I go to another location with wifi ( e.g. work or school ) it goes gray again. ( fyi i never turn down my wifi, and i'm not intent to do so )

Well then obviously you didnt setup the connection correctly to work with the other wifi?
Password?IP?Mac adress allowed?

I did set them up good... how I know i'm sure ? If I switch wifi off and on again, I have a proper connexion

Are you using some kind of app like wifi static to switch between dynamic IP on one wifi and static one on the other?

no no no, nothing like that. When i was on a stock rom ( 2.3.3 ) I never had this problem. That's why my first suggestion was the rom. But I can't post in the rc3.1 forum , and when others with the same problem ask things, they don't get a respons.
btw I'm in my battery status overview, and the app ( wake lock ) usses 55%, is that okay ?
the android-operating system is only like 6-7%, where this was higher before.
oh, and thanks for your time helping me

The app prevents the cpu from sleeping (as that is what a wakelock does), thus the device never fully sleeps and uses battery.
As the app has aquired the wakelock, android shows it as the cause.
Nothing wrong there.

I used the app for a couple of days now and it doesnt resolve the problem
more suggestions ?

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.

Wi-Fi/LTE doesn't start working until phone is on for some time

Hello everyone,
I have had my E6653 since mid October, and it was working well, however once I flashed a Taiwanese 32.0.A.6.152 firmware I have this bug. Let me describe what actually happens:
1. All stamina modes turned on (clock, extended standby, extended usage)
2. Start using the phone after it sat idle for some time, sometimes even 10 minutes is enough
3. Whatever app you were in, if it requires internet connection, it won't work. Switch apps, try to use internet connection and it still won't work.
4. Wait for somewhere around 15 seconds, and internet connection kicks in.
It happens when I'm both on LTE and Wi-Fi. I have already tried repairing my phone, and flashed 3 different firmwares (CE, Taiwan, UK), but nothing helps. I have seen someone on reddit with a similar problem, but for them it only occurred when they were connected to Wi-Fi.
Has anybody else experienced this? If yes, were you able to fix it?
Thanks for your time!

I was able to fix it by waiting 15 seconds.
Seriously, turning back on the radios and acquiring an IP address isn't instant. Just be happy you have a phone with Stamina mode available if you want it.

ricodredd said:
I was able to fix it by waiting 15 seconds.
Seriously, turning back on the radios and acquiring an IP address isn't instant. Just be happy you have a phone with Stamina mode available if you want it.
Click to expand...
Click to collapse
I don't think you understood what the problem is. I have LTE and Wi-Fi turned on all the time, never turn either off. Stop using a phone for 10 minutes, turn the screen back on, unlock it, try to use internet connection and then it fails. It hasn't happened on the previous version of the firmware when I had all stamina modes turned on, and it certainly isn't normal. It's a bug, and I was asking if anyone knows the fix. Waiting 15 seconds is not one, unfortunately.

Well one of us isn't getting the issue for sure and I don't think it's me. However, I've been wrong before
You said:
"1. All stamina modes turned on (clock, extended standby, extended usage)"
but also:
"I have LTE and Wi-Fi turned on all the time, never turn either off."
Stamina mode says about Extended standby: "Saves power when the screen is off by temporarily disabling Wi-Fi and mobile data".
These two statements are in disagreement.
So you put the phone down for a few minutes (presumably the screen goes off too), then Stamina mode kicks in and turns off Wi-Fi and mobile data. You wake up the phone after 10 minutes or so => you need to wait for radios to fire up and acquire IP address.
I'm not seeing anything wrong or unexpected with this behaviour...

I've noticed this more aggressive stamina mode myself. In all honesty I can't see a problem with it, it's putting the phone into deep sleep a lot faster (10 seconds or so in most cases) than it was on the firmware before. If it is happening across many different firmwares it is safe to assume that's how it is meant to be functioning. If, in the next firmware, it goes back to how it was it was a bug.

This behavior is different to earlier Xperias so it surprised me as well. In addition the phone shows you still connected to the network which makes it more difficult to determine.