I keep trying to tell my TF to suspend the wi-fi when the screen goes off. I know it takes 15 minutes for it to actually do this, which is fine, but I check an hour later and it never went off. This is according to the Battery info graph. And when I return to the setting in Wireless Networks, it is back to "NEVER".
Am I alone in this or is it a bug? Today I rebooted the tablet a few times and also plugged it into the keyboard dock at one point.
Related
Hi there,
With my BlueAngel I could leave the WiFi on all night as when the phone was switched off it did not eat up the battery - when the phone was switched on it would spend a couple of seconds reconnecting to the wireless point.
The Universal seems to behave in the same way, yet it eats up all the battery overnight even when I have switched the phone off and it is not connected to the WiFi access point.
Is there some setting or registry key I can alter to fix this?
Cheers,
Quilty
@Qulity, if you don't close PIE I have found the battery can be drained. I assume overnight you are using Flight Mode.
Are you closing the flip and presuming that the device gets turned off or have you actually set your device to turn off after a fixed period of inactivity in the power settings?
If it is the former, then the device actually does not turn off if there is any activity in the background like active GPRS or WiFi etc. A simple solution to this would be to press the hard-ware on/off button once you are done irrespective of whether wfi is active or not in the background.
Try it out and post your results here.
My device is set to turn off after 2 mins on battery power, but I made a special point of turning it off with the hardware button before testing last night. As I said before my BlueAngel never behaved like this.
my jasjar was turned off yesterday, and every 5min i heard sound for new wifi network!! same problem, i solved it with turnig wifi off!! any other solutions?
okay--i've been struggling with this all week and I can't figure out what is doing this. It might be bluetooth but it could be something else.
As I understand it Wifi should turn off when I put the phone in standby. For the first half of today that was the case. then mysteriously, it stopped turning off and guess what, my battery usage disappeared.
I have checked my BsB tweak settings, it is not set to have wifi on in standby. I have checked my wireless connections to disconnect after 30 seconds. Although that probably only works if i am away from a wifi signal all together.
so what else do i need to do to switch it back to default--I don't want wifi on when it's on standby. At the least, i want to be able to toggle it like it's supposed to.
thanks for the help. Once i get this figured out I am pretty confident my battery usage will be good.
Running a Nook Color with CM7.1 stable. Kind of an odd issue here, I have two different Bluetooth GPS devices, and when they are paired to the Nook and I turn my screen off and then back on, it loses the connection. The only way to reconnect the devices is to restart the Nook, as it fails to connect after the screen is brought back up. I have found that if I have the Nook plugged in for power, this issue does not happen. I have tried multiple GPS apps, reflashed CM7.1 multiple times, but still have no success unless I have the Nook plugged in, or I just ensure the screen doesnt go to sleep.
I really need this to work, as I'm using this as a pilot, and I can't have the screen on the entire flight as it will drain the battery quickly. I swore it used to work before, but I know I had issues with it, and maybe now realize what was causing those issues. On a side note, my friend has also tested everything I have done, but his works consistently and reliably regardless if he leaves the screen off, or turns it on and off repetitively. Hopefully someone may have an idea!!
Thanks in advance.
So noone has any thoughts or ideas at all?
Well seeing as it doesn't happen when your plugged in that would make me think that it has something to do with the fact that WiFi turns off when the screen is turned off. The Bluetooth and WiFi are on the same module i do believe. The default setting for WiFi is to stay on all the time while plugged in and turn off when the screen is turned off while on battery.
My suggestion would be to turn the WiFi to stay on all the time and see if that changes anything. Go to WiFi settings --> menu --> advanced --> WiFi sleep policy -->never. That would be my suggestion, hope that works for ya!
jgore43 said:
Well seeing as it doesn't happen when your plugged in that would make me think that it has something to do with the fact that WiFi turns off when the screen is turned off. The Bluetooth and WiFi are on the same module i do believe. The default setting for WiFi is to stay on all the time while plugged in and turn off when the screen is turned off while on battery.
My suggestion would be to turn the WiFi to stay on all the time and see if that changes anything. Go to WiFi settings --> menu --> advanced --> WiFi sleep policy -->never. That would be my suggestion, hope that works for ya!
Click to expand...
Click to collapse
That's what I was thinking too. It seems that when NC goes into deep sleep Bluetooth will lose connection. By removing deep sleep you should be able to stay connected, although your battery will drain faster than with deep sleep on, it should have a better life with screen off than on.
Well I appreciate both of your responses. However, I should have mentioned that I do already have Wi-Fi set to always stay on/never sleep. Any other suggestions?
Got a weird problem with my AT&T stock non-rooted S4. About 4 or 5 times since I got it on release day when I charge my phone and I get the notification that it's fully charged the screen won't turn back off. I use a Belkin Conserve socket that is set to shut off after 3 hours and I've woken up after charging to find the phone dead. I've managed to catch this happen once and when the fully charged notification comes on the screen won't go to sleep, it just stays on and flickers a little bit. For all but one of these instances I had blocking mode on so I'm not disturbed by email or text notifications in the middle of the night. It did happen one time when I didn't have blocking mode on. I use a pin lock for my lockscreen and usually have BeyondPod playing overnight (only one hour long podcast while it's still charging) if that makes a difference. Is the function that enables the screen to stay on when you're looking at it malfunctioning? Any help? I've attached two screenshots of battery life when this happens.
Tryptonite said:
Got a weird problem with my AT&T stock non-rooted S4. About 4 or 5 times since I got it on release day when I charge my phone and I get the notification that it's fully charged the screen won't turn back off. I use a Belkin Conserve socket that is set to shut off after 3 hours and I've woken up after charging to find the phone dead. I've managed to catch this happen once and when the fully charged notification comes on the screen won't go to sleep, it just stays on and flickers a little bit. For all but one of these instances I had blocking mode on so I'm not disturbed by email or text notifications in the middle of the night. It did happen one time when I didn't have blocking mode on. I use a pin lock for my lockscreen and usually have BeyondPod playing overnight (only one hour long podcast while it's still charging) if that makes a difference. Is the function that enables the screen to stay on when you're looking at it malfunctioning? Any help? I've attached two screenshots of battery life when this happens.
Click to expand...
Click to collapse
So in settings under the Developer Options, there is a setting "Stay awake" if checked screen will never sleep while charging. Now I see that your Belkin shuts off the power but your phones still detects the usb plugged into a power source.
I think things happen in this order: you hookup your phone to charge and shut off your screen, phone charges to 100% and screen lights up saying fully charged, it stays on because of that setting, Belkin kills the power, it is still hooked up to USB so ... you get the rest.
I would find that setting and disable it.
if your next question is "I don't see developers option" it is hidden by default in android 4.2.2 so to make it available, go to Settings > About phone and tap tap tap Build number seven times. Return to the previous screen to find Developer options. Or Indiana Jones might pop up and give you the cup to get eternal life !!!
Thanks for the reply Commodore64 but I already checked that setting when it happened the first time and it's not checked.
No one else has had this problem?
Tryptonite said:
No one else has had this problem?
Click to expand...
Click to collapse
I have this problem as well as my wife's S4. around 3am, I notice our room is bright with our two phones' screens on. It will stay on until the morning.
In the developer's section of the settings, the stay on when plugged in is NOT checked.
Also, on our phones, we notice the phones overheating because the screen is on for hours at a time at night.
I've just spent an hour looking through the internet, and while many report this, they are simply being dismissed by others as in having "checked" the setting in developer section.
Also, when the batttery does get fully charged, the "Battery if full, unplug the power" notification also rings the default notification ringtone. I've installed phoneweaver to set my phone to no sound overnight, but it only stops the sound, the screen still stays on and phone gets really hot.
This is turning out to be a huge problem for us.
pyrophilus said:
I have this problem as well as my wife's S4. around 3am, I notice our room is bright with our two phones' screens on. It will stay on until the morning.
In the developer's section of the settings, the stay on when plugged in is NOT checked.
Also, on our phones, we notice the phones overheating because the screen is on for hours at a time at night.
I've just spent an hour looking through the internet, and while many report this, they are simply being dismissed by others as in having "checked" the setting in developer section.
Also, when the batttery does get fully charged, the "Battery if full, unplug the power" notification also rings the default notification ringtone. I've installed phoneweaver to set my phone to no sound overnight, but it only stops the sound, the screen still stays on and phone gets really hot.
This is turning out to be a huge problem for us.
Click to expand...
Click to collapse
Do you use a PIN (number) lock? I did but switched to the pattern unlock and it hasn't happened since. Also, I've been trying to charge only during the day or evening, not overnight. Maybe, since I charge during the day and I use it periodically while it charges it doesn't go into a "deep sleep" like it would if it charges while sleeping and the full charge notification would keep it awake. I don't know exactly why but it hasn't happened since. Hope this helps.
Power Button Not Working SGS4 Not Sleeping SOLVED
For whatever it's worth, see http://forum.xda-developers.com/showthread.php?p=48871706#post48871706 - maybe that will be helpful.
So I posted this in a different thread but figured I would post it here to see if anyone could duplicate my findings. I have a Note3 from T-Mobile and for whatever reason leaving the Wi-Fi on will not allow the phone to go into deep sleep mode. I noticed when I was down to 40% battery after 10 hours with only one hour of screen on time. After running some tests I had only 2 minutes of deep sleep those entire 10 hours (tested using BetterBatteryStats) I tried setting "Keep Wi-Fi on during sleep" to Never and unchecking "Always allow scanning" under advanced network settings but neither of them fix the issue. In fact, after several tests I concluded that setting never for "Keep Wi-Fi on during sleep" wasn't even functioning as my access points still showed the client connected while the phone was asleep.
Can anyone else confirm this issue is actually a bug and not just my phone being defective?
Here's my original post on the topic regarding how I found the problem and what I have tested so far:
OK so after only 2 days of owning this phone (got it late Monday night, the T-Mobile variant) I finally figured out why I'm getting such bad battery, and I suspect the same thing may be happening for the other people in this thread. Hopefully this information helps at least one person.
My battery stats was almost identical to all the other users in this thread that had bad battery, I would get barely around 10-12 hours on the phone with less than 2 hours of screen on time. After using multiple apps to track down the issue I finally got what it was.
Wireless. Yes, wireless was my cause. But the thing is Wi-Fi didn't show up at all in any of the battery apps so I assumed it was a non issue. I've had other phones and have always kept the wireless turned on the entire time without problems. The basic problem is not that Wi-Fi is using power itself but it's that by default the phone cannot enter deep sleep while connected to Wi-Fi. This is why trying to use apps like BetterBatteryStats will lead you nowhere initially (though they were useful in finding out what was causing the issue) You can discover this by turning on Wi-Fi and connecting the phone to a charger, then disconnecting it so your BBS information will reset. Then power off the screen and power it back on after 10 minutes. You'll notice in the other section that deep sleep will have less than a minute time while awake probably has close to 9 minutes, if not more. This is with everything else turned off, almost no apps, and no special Samsung stuff enabled.
Under Apps > Settings > Wi-Fi > Menu > Advanced there are two options that should help this: "Keep Wi-Fi on during sleep" and "Always allow scanning" I set the "Keep Wi-Fi on during sleep" to Never and unchecked Always allow scanning and rebooted the phone. And low and behold...nothing. Yes, these options don't work (at least not to fix this problem) The phone still won't enter deep sleep mode while the wireless is enabled. Based on my company's wireless devices I can see that even with the screen off for well over 10 minutes it still shows connected as a client meaning the wireless is not turning off properly while it's in sleep mode. Or perhaps it can't go into sleep mode because the wireless is on which stops it from going into sleep mode and turning off the wireless. My guess is that it's a Samsung bug.
The reason why there's so many people here to get good battery usage is because they're either used to turning Wi-Fi on only when needed and keeping it off. You'll also not notice it if you have more than 6 hours of screen on time because you could easily assume that it would make sense that you phone would only last 10 hours total with that much screen on time, even though it should have technically lasted 20+ hours with only 6 hours of screen on time if the phone could have entered deep sleep.
So what's the real fix for this? Unless it's by design my belief is that it's a bug and won't be fixed until Samsung/T-mobile notices. I can't test to see if the same thing happens on other carriers so if someone feels like testing this theory out it would help.
For now, I guess we're just left to manually turning Wi-Fi on only when needed and leaving it off in all other cases. For those that have the T-mobile variant, make sure you also go into Settings > General > Backup and reset > Collect diagnostics and uncheck the "Allow Diagnostics" as that will probably be the highest offender of Partial Wakelocks (it'll show up as com.carrieriq.tmobile.wakelock or System Manager Application)
If anyone wants more information on my testing let me know!
Click to expand...
Click to collapse
That's because the 'Keep WiFi during sleep: Never" setting only disconnects, it doesn't shut down the WiFi radio.
You're going to have to use a manager (Like Deep Sleep Battery Saver).
Or just hit the toggle yourself... If you're going to keep it disconnected in sleep anyway, just swipe down the notification bar and hit the bloody toggle.
ShadowLea said:
That's because the 'Keep WiFi during sleep: Never" setting only disconnects, it doesn't shut down the WiFi radio.
You're going to have to use a manager (Like Deep Sleep Battery Saver).
Or just hit the toggle yourself... If you're going to keep it disconnected in sleep anyway, just swipe down the notification bar and hit the bloody toggle.
Click to expand...
Click to collapse
The problem is that it doesn't disconnect, the access point 100% shows it is connected and transferring data every now and then. But the real issue isn't weather it disconnects or not but it's the fact that Wi-Fi will not allow the phone to go into deep sleep mode. For now I am fine with switching Wi-Fi off and on as needed, but with no other phone have I needed to do this before and definitely seems like a bug.
But regardless, what I'm trying to figure out if this is a legit bug that I should submit to Samsung/T-mobile or if it's just my phone and I should ask for a replacement. If anyone has BetterBatteryStats and could test this with their Note3 that would help.
My stupid phone has just started this same issue!!!! Freaking annoying, after only 8 hrs from 100% charged state, the battery is at 46% with only 26 mins screen ontime, I checked out that the phone never goes into deep sleep. What is going on and what can be causing this? Did you manage to resolve your issue?
PS I checked out wakelock detector but doesn't tell me a thing, as what program is keeping the phone awake all the time. Starting to hate this phone and miss my S3
What is your GPS accuracy setting set to? GPS, Wifi or Networks? Try setting it to GPS only.
GameBoiye said:
So I posted this in a different thread but figured I would post it here to see if anyone could duplicate my findings. I have a Note3 from T-Mobile and for whatever reason leaving the Wi-Fi on will not allow the phone to go into deep sleep mode. I noticed when I was down to 40% battery after 10 hours with only one hour of screen on time. After running some tests I had only 2 minutes of deep sleep those entire 10 hours (tested using BetterBatteryStats) I tried setting "Keep Wi-Fi on during sleep" to Never and unchecking "Always allow scanning" under advanced network settings but neither of them fix the issue. In fact, after several tests I concluded that setting never for "Keep Wi-Fi on during sleep" wasn't even functioning as my access points still showed the client connected while the phone was asleep.
Can anyone else confirm this issue is actually a bug and not just my phone being defective?
Click to expand...
Click to collapse
Well, your issue looks pretty similar to mine, which I solved with this Xposed mod (you could give it a try if you're on KitKat): http://forum.xda-developers.com/xposed/modules/mod-wi-fi-deep-sleep-t2752947. I was experiencing that even when "Keep Wi-Fi on during sleep" is set to Never, Wi-Fi still was awake most of the time according to battery stats.