Like the title says, my phone stops going into deep sleep about 3 days after a reboot. I need to reboot the phone for it to go to deep sleep again. Would anyone know what might be causing this?
Japultra said:
Like the title says, my phone stops going into deep sleep about 3 days after a reboot. I need to reboot the phone for it to go to deep sleep again. Would anyone know what might be causing this?
Click to expand...
Click to collapse
In my opinion, that's not a bad thing. It's better to restart any device with an OS on it at least once a day or two maximum.
A computer device that stays on for days is similar to a human not getting sleep. Things slow down and become fragmented. VRAM, Page File, etc start getting cluttered.
I'm not surprised your phone won't enter deep sleep after three days of being on. After that much use, you'd have used various apps and services causing wakelocks.
That's what I experience, at least.
FiddleGoose said:
In my opinion, that's not a bad thing. It's better to restart any device with an OS on it at least once a day or two maximum.
A computer device that stays on for days is similar to a human not getting sleep. Things slow down and become fragmented. VRAM, Page File, etc start getting cluttered.
I'm not surprised your phone won't enter deep sleep after three days of being on. After that much use, you'd have used various apps and services causing wakelocks.
That's what I experience, at least.
Click to expand...
Click to collapse
My S6 didn't do this though. I could go for a couple weeks without restarting it and it would still enter deep sleep.
I had a similar problem. For me it wasn't every three days, but usually 24-36 hours. But same issue, suddenly wouldn't go into deep sleep and a restart would fix it.
I found my issue to be gas buddy app and it trying to poll locations via bluetooth. Google it, there are lots of threads on it, but basically due to bad programming it would just jam on.
I figured this out as i could get my phone to go into deep sleep by turning off bluetooth, so that might be a quick easy test for you.
Also remember my in case (and unfortunately for a lot of other people) it was the gas buddy app. but others have reported the same issue with other apps.
i don't know if android's implementation on bluetooth location is busted, or the way the apps are using it.
Related
hi all,
I've installed a raft of apps in the last few days (perhaps that was foolish) on my sim-free white Hero, and suddently the battery life has gone to pieces. It now won't even last the night *in standby with wifi off*.
Any ideas as to the known battery killers, or any way I can track down which is causing this? I don't really have to want to start removing apps at random and monitoring.
There's nothing particularly unusual in my list of running apps, following a power cycle (is there?):
Shake Awake, NetCounter, AK Notepad, OI Update & Countdown, Tube Status, Battery Widget, BBC News widget, Peep
(although that does raise a separate question: why do things like ShopSavvy, AK Notepad, start at boot, when presumably they're not really doing anything until you use them?)
Of course, I have other things that get started asynchronously, just not at boot, e.g. SMS Popup.
anyone got any ideas, please?
thanks much indeed.
cdmackay said:
hi all,
I've installed a raft of apps in the last few days (perhaps that was foolish) on my sim-free white Hero, and suddently the battery life has gone to pieces. It now won't even last the night *in standby with wifi off*.
Any ideas as to the known battery killers, or any way I can track down which is causing this? I don't really have to want to start removing apps at random and monitoring.
There's nothing particularly unusual in my list of running apps, following a power cycle (is there?):
Shake Awake, NetCounter, AK Notepad, OI Update & Countdown, Tube Status, Battery Widget, BBC News widget, Peep
(although that does raise a separate question: why do things like ShopSavvy, AK Notepad, start at boot, when presumably they're not really doing anything until you use them?)
Of course, I have other things that get started asynchronously, just not at boot, e.g. SMS Popup.
anyone got any ideas, please?
thanks much indeed.
Click to expand...
Click to collapse
I had the same issue when i put on battery widget, I saw the % going down while watching the phone.
oh! that's ironic
I do get the impression that it's more recent than that, but it could well be, I suppose. I'll remove it and see... thanks.
I've heard that the bbc widget drains the battery.
This is something Google should address with android market. The system should apply various forms of stress testing to all applications and rate them according to connectivity requirements, CPU load, power consumption etc.
I think for people who have a serious drain they need to hard reset and start again, put 1 program on at a time and leave it a day or so with that program on, finding out whats causing the drain.
Logically thinking, i'd expect it to be a program that is using internet in the background, like the bbc widget which could still be downloading without you knowing.
good points, ta.
I already noticed this. I checked the CPU load in idle mode and normally it should be around 10% (using "System Monitor").
Sometimes however, depending on what apps were running, it is increased to 30-40% and staying there constantly.
Closing all apps (incl. Sense) does not help either, the CPU load won't go down again until i make a complete device reset.
So i guess some processes are stuck in thise case causing the high load (and draining the battery empty).
My GPS did not disconnect, after foto geo-tagging, and that goes quick as well.
Also the BBC-app was installed, but got rid of it because I didn't use it. Might be a coincidence.
The BBC app polls really often. There's no setting to tell it how often to poll. It really kills the battery fast
I wonder though: even when the phone is in standby? something is killing me in standby. Oddly, it seems better if the phone is on
I'll try removing the BBC app overnight, and see...
then the battery widget tomorrow, etc...
cdmackay said:
I wonder though: even when the phone is in standby? something is killing me in standby. Oddly, it seems better if the phone is on
I'll try removing the BBC app overnight, and see...
then the battery widget tomorrow, etc...
Click to expand...
Click to collapse
Turn on usb debugging... download the SDK.. cd into tools.. and run
adb logcat
or to send it to a file:
adb logcat > log.txt
(and ctrl + C to stop logging)
Inspect the log file and you'll see what its upto pretty quickly. Maybe its overkill, but I fire that up when it starts behaving strangly.
EDIT: err to answer your question.. yeah the widgets wake the phone up to grab new data, which eats battery. The BBC news one seems to be polling reallllly often, which is unecesarily using power.
quick update: removed BBC News and Battery Widget (separately), no change; phone still dies overnight, in fact in about 5 hours on standby, from a full battery, to totally dead.
I just this minute discovered that my phone whilst in standby is still polling my IMAP server to try and connect, and I have a huge inbox, which it was prob failing to get the headers for. Seems like a possible bug that it still does this whilst in standby, but I've disabled that account anyway. It might be the cause...
What do you mean by Standby? Just inactive? Airplane Mode?
sorry, poor terminology, perhaps. No, not airplane mode, just the screen-off state it goes into after a few minutes.
It does seem a little bit of a waste, if the phone is going to spend all night checking for new Twitter, Gmail, etc, updates, when I'm not awake to read them? So I'd naively assumed that perhaps it wouldn't do that when it's in the screen-off state. Unless you've asked for notification other than on the top bar, of course?
cdmackay said:
It does seem a little bit of a waste, if the phone is going to spend all night checking for new Twitter, Gmail, etc, updates, when I'm not awake to read them?
Click to expand...
Click to collapse
To be fair, the phone doesn't know when you're going to asleep now does it? (especially if you're a night worker).
I notice that there's an application in the market now which can automatically turn airplane mode on according to a schedule, so that may help but of course this does mean you won't get phone calls!
Regards,
Dave
foxmeister said:
To be fair, the phone doesn't know when you're going to asleep now does it? (especially if you're a night worker).
I notice that there's an application in the market now which can automatically turn airplane mode on according to a schedule, so that may help but of course this does mean you won't get phone calls!
Regards,
Dave
Click to expand...
Click to collapse
No it doesn't but I'm developing a widget which will disable data access at certain times (dependent on user) so overnight it wont use data and save battery.
foxmeister said:
To be fair, the phone doesn't know when you're going to asleep now does it? (especially if you're a night worker).
Click to expand...
Click to collapse
Right; I really meant the following, but worded it wrongly...
I had expected apps not to do data access when the phone's screen is off, unless they have been configured to notify via sound, vibrate or light.
i.e. if an app either isn't notifying, or is only notifying via the top bar, then it should disable its data access when the screen is off.
That would mean a short delay in getting updates, when the screen is back on, but I'd rather have that than spending much battery time pointless checking for updates when I'm not going to see them for ages, whether that's at night or just when the phone is sitting on the desk for hours.
nicelad_uk said:
No it doesn't but I'm developing a widget which will disable data access at certain times (dependent on user) so overnight it wont use data and save battery.
Click to expand...
Click to collapse
aha! that sounds great, thanks in advance
would you update us here when you have something testable, please?
and if it's not pushing my luck to ask: any chance that it might also have a manual switch too, for those of us who go to bed at wildly different times?
Or perhaps there is already a way to disable data access manually, with a single setting change, without disabling the phone? I think there might be...
ah yes indeed, there's even an HTC widget to disable mobile networking, whilst leaving phone enabled. That will do for now
My phone is not sleeping itself down after the time elapses.anyone else noticing this, its making me think its draining my battery.
Just tested this myself, and on a one minute sleep timer, my phone did properly go to sleep.
Mine sleeps fine too.
mine sleeps fine as well. Do you have any particular app running? For example, if you have AT&T Navigator running it will not sleep. There are a few other apps that provide the ability to prevent it from sleeping. So, are you on the main screen or in an app when it doesn't sleep?
Cannot say I've had this problem. Worked at its default of 1 min, and still works after I changed to 3.
I am trying to id the app if any that is causing it but with no task manager its impossible.
I do notice an issue with the camera app. If the camera button gets pressed then the phone will stay on and not sleep, for me at least.
It goes off on it's own mostly...thanks for the reports as I work through this. I may need a hard reset anyway, hey why not Ill add a microSD at that time.
Using the new battery usage info in Honeycomb/gingerbread, I can see that there is an app periodically waking the device in pretty frequent intervals.
The only third party apps I have installed on the Xoom I also have on my phone and consider them safe.
Can you guys look at your battery usage? In particular look for times your device is awake but the screen is off. Thanks.
Install spare parts from the markpet. Under battery use there is a wakelock category and you should be able to find the offending application.
At this point, my battery life's so darn good I'm not worried if something is exhibiting this behavior. Seriously, though, I'll take a look as well and see if I can find anything going on.
Think I found it.
I turned off the "backup my data" feature in the privacy settings area. Since I've done that the device now sleeps without interruption.
Before, it was waking up what appeared to be every 5-10 minutes or so. It also, at times, completely and totally wakelocked the device.
It may be too early to claim victory here as its only been a few hours but I'm pretty confident that was the issue.
EDIT: nevermind, still seems to be waking up. Argh.
Inphinitizeit said:
Install spare parts from the markpet. Under battery use there is a wakelock category and you should be able to find the offending application.
Click to expand...
Click to collapse
Crashes for me in Honeycomb.
My screen randomly turns on and sits at the lock screen for a few seconds for no apparent reason. There are no pending notifications, etc. I assume there might be a rogue app causing this, but I don't have that many installed and even less apps doing any background tasks. Any idea on how to find the culprit?
I found this bug report where some apps are mentioned, but I'm not running any of them.
https://code.google.com/p/android/issues/detail?id=39625
On the Galaxy Nexus this issue was sometimes caused by a flaw in the micro-USB connector. I sincerely hope that is not the case with the Nexus 4.
I noticed that the phone wakes up whenever it reconnects to Wi-Fi. I was changing some router settings last night and I constantly saw the phone waking up shortly after the router rebooted. However, this is not the only scenario where it does it.
Mine has done the same, no idea why, only seen it the once, but it certainly happened, sitting three feet away from me, and suddenly Bingo! its on.
Mine wakes every few minutes. Certain apps (tasker, facebook etc) and syncing seem to cause it to happen more often but even if I disable most apps it still happens. I've been unable to identify the source with better battery stats. It happens bone stock and on CM10.1. I'm still getting better battery life than my GNexus but it's maddening.
Mine too. It will do it a few times in succession then be still for a while before starting again. No apps open and google sync off.
ludovicien said:
Mine too. It will do it a few times in succession then be still for a while before starting again. No apps open and google sync off.
Click to expand...
Click to collapse
So my Nexus 4 doesn't want to go to sleep.
- I have sleep set to 15 seconds
- Dream is off (just in case)
It just stays on. It doesn't matter if it's on the the lock screen or at the home screen. I'm guessing some app is keeping it awake. It just started last night, but I don't think I have installed any new apps. Maybe it from an update.
solved
My phone's screen also used to wake up randomly. it was very annoying, especially at midnight
finally, I found out the reason by using "Wakelock detector" app which is freely available in market.
here is XDA thread about WLD: WLD at XDA Thread
the cause of problem was ad Notification, it was holding "full wakelock" (you can see it in screenshot)
good Luck!
Refer Wakelock Detector at XDA
Ramdom screen wake up issue solved
Dear all,
I was experiencing random screen wake issue in my XOLO PLAY smartphone.
The problem was with the AppLock software. After upate is this issue appreard. Earlier AppLock was there and no issue was experienced.
I am writing to AppLock team to fix the bug.
:angel:
All the best
Regards
nitin5062
hcedillo said:
On the Galaxy Nexus this issue was sometimes caused by a flaw in the micro-USB connector. I sincerely hope that is not the case with the Nexus 4.
Click to expand...
Click to collapse
U made an account to post THIS only?
Has anyone else noticed that notifications seem to be super slow in coming after the Pie update? Line and Email can take up to two hours to exhibit a notification. I've looked at the notifications area of the apps, and nothing appears to have changed that I can see, and I can't find anywhere in Pie to tell it to allow more background time for these apps. I've tried force stopping and restarting with no change.
If anyone has any idea on what is going on, and how to fix it, your help would be most appreciated. Being told your wife left you a Line message 2 hours after she did so, or that your kid sent an email 2 hours earlier, is NOT conducive to a happy home life.
Nobody else has this issue? It appears to be connected to the fact that the phone is sitting undisturbed for a long period of time. If I am carrying the phone around with me, the notifications seem to come as expected, but if the phone is just sitting on my desk for a while, they seem to come from minutes to hours later.
You could try to whitelist those apps on Battery Optimization
I'm no expert, but from what you describe sounds like the phone is entering into Doze and notifications cannot come until the next maintenance window
If a user leaves a device unplugged and stationary for a period of time, with the screen off, the device enters Doze mode. In Doze mode, the system attempts to conserve battery by restricting apps' access to network and CPU-intensive services. It also prevents apps from accessing the network and defers their jobs, syncs, and standard alarms.
Click to expand...
Click to collapse
https://developer.android.com/training/monitoring-device-state/doze-standby
I think white listing the app prevents this behaviour
It does sound like you are correct and the phone is entering Doze mode, delaying the notifications. Thanks for that!
I will check into how to add the email and Line app to a whitelist for Doze. Hopefully it's a simple task, but I don't see anything under Battery doing a quick scan.
Just a follow up. After much searching and reading, I finally found where to turn off battery optimization for the two apps I needed notifications from. FYI:
Most things on the web say to go to Settings->Battery, then hit the three dot menu and select Battery Optimization. This does not appear on my phone. (see screenshot) To get to the list of optimized apps, you need to Search->Battery Optimization, select Battery Optimization from the results (it will take a few seconds to load), then tap Not Optimized and select All Apps. Find the app you want, tap it, then select Don't Optimize. You can also go to Apps and Notifications->Advanced->Special app access->battery optimization.
Whether this will actually fix the problem is another question entirely as most posts say that Doze continues to work. I guess we shall see.
I hope this saves someone the aggravation of trying to find something directly relating to Pie. Most things out there are for older builds.
Also, I turned off Adaptive Battery to see what the actual difference is in my light usage use case. If you are interested in the results of this test, let me know and I will post here.
Glad you were able to whitelist those apps.
I think it's weird anyway, as far as I know deep doze takes hours to trigger and the device has to be completely still. Any movement would take the device off deep sleep and enter a less aggressive doze (where notifications would be checked more often)
You did mention this is your case (you were leaving your device on your desk) but just for curiosity, how long approx would you leave your phone unattended?
Thanks and I hope this solves your issue.
Tepig said:
Glad you were able to whitelist those apps.
I think it's weird anyway, as far as I know deep doze takes hours to trigger and the device has to be completely still. Any movement would take the device off deep sleep and enter a less aggressive doze (where notifications would be checked more often)
You did mention this is your case (you were leaving your device on your desk) but just for curiosity, how long approx would you leave your phone unattended?
Thanks and I hope this solves your issue.
Click to expand...
Click to collapse
Unlike some folks, I am not tied to my phone. It often sits on the desk undisturbed for 3 or 4 hours during the day unless a notification comes in and I pick it up to look at it. Most of my screen time is on my computer, so the phone is the external brain when out and about, but not used much otherwise. At night, I turn on airplane mode until I get up the next day, then turn it off. I'm a retired software engineer, so have no real need for constant communication anymore, and I like it that way.