Related
I'm attempting to try to increase my battery life so it lasts longer than 12 hours (~13 seems to be my limit). (I'll admit I'm a bit jealous of those who can run the phone 24+ hours) Though it's somewhat painful, I'm shutting down most the programs I have running in the background. However there seems to be a number that like to restart even after I think I've disabled their startup, widgets, notifications, etc.
Is there a way to make sure programs that you install don't run? Or at least don't launch during start up? Perhaps something like msconfig in windows?
Thanks.
Raleran said:
I'm attempting to try to increase my battery life so it lasts longer than 12 hours (~13 seems to be my limit). (I'll admit I'm a bit jealous of those who can run the phone 24+ hours) Though it's somewhat painful, I'm shutting down most the programs I have running in the background. However there seems to be a number that like to restart even after I think I've disabled their startup, widgets, notifications, etc.
Is there a way to make sure programs that you install don't run? Or at least don't launch during start up? Perhaps something like msconfig in windows?
Thanks.
Click to expand...
Click to collapse
Killing background tasks will only decrease your battery life. When an application goes to the background, it sits in memory but does NOT consume any CPU power. since the memory is in solid state, it requires no power to stay in that state. By constantly killing background applications, it will need to start up, reinitialize, and consume more power then if you had just left it alone. Also, long term performance will be negatively affected, even if you do expereince a small short term performance gain. the Android OS is designed at the core level to have applications behave this way, and modifying that behavior will make for a worse experience.
asrrin29 said:
Killing background tasks will only decrease your battery life. When an application goes to the background, it sits in memory but does NOT consume any CPU power. since the memory is in solid state, it requires no power to stay in that state. By constantly killing background applications, it will need to start up, reinitialize, and consume more power then if you had just left it alone. Also, long term performance will be negatively affected, even if you do expereince a small short term performance gain. the Android OS is designed at the core level to have applications behave this way, and modifying that behavior will make for a worse experience.
Click to expand...
Click to collapse
Eh, this is the first I've heard this. I don't remember reading this in the various battery optimization guides.
Still is there a was to stop things short of uninstalling? For example, I want to stop using the Yahoo Mail app but don't want to install yet. I went through all the options I could to disable checking/notifications, etc but it still pops back into memory constantly.
I assume youve tried the obvious, turn off WiFi (3G) and screen when not actively using it?! Those are the big batt.-eaters
Sent from my HTC Magic using XDA App
asrrin29 said:
Killing background tasks will only decrease your battery life. When an application goes to the background, it sits in memory but does NOT consume any CPU power. since the memory is in solid state, it requires no power to stay in that state. By constantly killing background applications, it will need to start up, reinitialize, and consume more power then if you had just left it alone. Also, long term performance will be negatively affected, even if you do expereince a small short term performance gain. the Android OS is designed at the core level to have applications behave this way, and modifying that behavior will make for a worse experience.
Click to expand...
Click to collapse
Documentation? As far as I have read an application does not go into any type of dehydrated state when running in the background / minimized. It can do anything it wants including using CPU cycles.
I do agree that most applications do not need to be killed with a task killer but leaving 3D games (for example) running in the background could hurt your battery. Also not all applications are progammed with ther same fore thought and skill level.
I get about 33% more runtime out of my battery using a task killer to kill specific applications that I know I do not want running in the background.
Streaker said:
I assume youve tried the obvious, turn off WiFi (3G) and screen when not actively using it?! Those are the big batt.-eaters
Click to expand...
Click to collapse
I leave wifi on since I'm usually in range. It's more efficient than 3g right? I alway sleep the device when I'm done. I still have huge percentages on the screen when looking at the battery usage. I'm trying a completely black screen now.
Mainly your widgets and icons and stuff still cover large portions of it, so: a black screen will help, not but alot.
Also, to keep items in RAM, to the second poster... What do you think is keeping those items in RAM?
Ummm... It's the CPU.
Task Killers won't help you on RAM usage at all (Because Android will automatically shuffle them out if it has to, or so I've read... I've yet to hit max memory). Task Killers DO help you as far as battery use goes, though... Keeping the browser killed if you aren't using it, etc.
Bjd223 said:
Documentation? As far as I have read an application does not go into any type of dehydrated state when running in the background / minimized. It can do anything it wants including using CPU cycles.
I do agree that most applications do not need to be killed with a task killer but leaving 3D games (for example) running in the background could hurt your battery. Also not all applications are progammed with ther same fore thought and skill level.
I get about 33% more runtime out of my battery using a task killer to kill specific applications that I know I do not want running in the background.
Click to expand...
Click to collapse
I should clarify. I guess the term I meant to use is "suspended." If a program is actively "running" in the background, it will use CPU cycles. But if you simply stopped using a program, say for example the xda app, and returned to your homescreen, the application stays "suspended" in the background and consumes no CPU cycles until you go back to it. Now services that are updating, such as email or SMS, will use CPU cycles in the background because they are still actively running. But if you want to conserve battery life you can simply disable the notifications from most of these programs.
asrrin29 said:
I should clarify. I guess the term I meant to use is "suspended." If a program is actively "running" in the background, it will use CPU cycles. But if you simply stopped using a program, say for example the xda app, and returned to your homescreen, the application stays "suspended" in the background and consumes no CPU cycles until you go back to it. Now services that are updating, such as email or SMS, will use CPU cycles in the background because they are still actively running. But if you want to conserve battery life you can simply disable the notifications from most of these programs.
Click to expand...
Click to collapse
The app itself at that point may not be but the Android OS still does to maintain that suspended state.
I have some applications I rarely use or even some that I've never used but may want to in the future. I see absolutely no benefit in keeping these applications in the background. Further more, I've noticed a signficant drain on the battery when extra applications are running in the background. I'm sure it's not all of them, but I've yet to discover who exactly the culpit is. Right now I suspect it's the NPR app, perhaps due to data use?
The point is, there are perfectly good reasons to keep some apps in the background, and perfectly good reasons to kill others - or perferrably not have them start up at all unless I do it myself. Could be due to data usage (especially if you do not have unlimited data), could be due to concerns about excessive cpu usage. There really should be a clear method in which you can stop applications from opening on their own.
You can use the program "Autostarts" to keep applications from starting at startup. With it you can also prevent things from launching under a number of other situations. That might be what you are looking for. Just do a google search for the APK as I don't think it is in the market.
Sent from my SAMSUNG-SGH-I897 using XDA App
Shuggins said:
You can use the program "Autostarts" to keep applications from starting at startup. With it you can also prevent things from launching under a number of other situations. That might be what you are looking for. Just do a google search for the APK as I don't think it is in the market.
Wouldn't tasker also help?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Sent from my AOSP on XDANDROID MSM using XDA App
To me, it's not a matter of "task killer or not", but rather when and where to use one. And I think it's simple: Don't bother, unless you suspect a specific app is doing something you don't want it to do in the background. Then, just kill that specific app and leave everything else alone. A Task manager that shows CPU% for each process can be handy for this as well.
I generally try to avoid killing tasks, but one night I had 50% battery on my phone and after about 2 hours or so I took it out of my pocket to make a phone call, and it was very hot and had about 12% of batter left -- something was running wild that shouldn't have been (I think it was Pandora, even though it was not currently playing any music!) So, background apps do occasionally run out of control, and you do need to occasionally kill them, but do it on an "as needed" basis.
Raleran said:
I'm attempting to try to increase my battery life so it lasts longer than 12 hours (~13 seems to be my limit). (I'll admit I'm a bit jealous of those who can run the phone 24+ hours) Though it's somewhat painful, I'm shutting down most the programs I have running in the background.
Click to expand...
Click to collapse
Unless the background process is syncing data, it won't eat your battery. So instead of wasting your time, you should focus on other energy hogs. Things like screen brightness, bluetooth, wifi, and gps.
Shuggins said:
You can use the program "Autostarts" to keep applications from starting at startup. With it you can also prevent things from launching under a number of other situations. That might be what you are looking for. Just do a google search for the APK as I don't think it is in the market.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I installed Advanced Task Killer from the Market. It lets you kill all running applications including itself.
durrence
jsmith8858 said:
To me, it's not a matter of "task killer or not", but rather when and where to use one. And I think it's simple: Don't bother, unless you suspect a specific app is doing something you don't want it to do in the background. Then, just kill that specific app and leave everything else alone. A Task manager that shows CPU% for each process can be handy for this as well.
I generally try to avoid killing tasks, but one night I had 50% battery on my phone and after about 2 hours or so I took it out of my pocket to make a phone call, and it was very hot and had about 12% of batter left -- something was running wild that shouldn't have been (I think it was Pandora, even though it was not currently playing any music!) So, background apps do occasionally run out of control, and you do need to occasionally kill them, but do it on an "as needed" basis.
Click to expand...
Click to collapse
Or an auto-killer would've killed it before it killed your battery by 38% lol
Task Killings are bad, mmmkay...
Slightly off topic:
To help conserve battery power,
Use an all black desktop background since the black areas dont use battery power.
Hmm, people in this thread have said a few things that I haven't heard or seen much before. Specifically that killing apps could decrease battery life. When I first downloaded advanced task killer I tended to kill most things. I slowly backed off and now I've been watching what launches and what tends to come back and not kill those (mail apps, widgets, performance watchers, etc). The second is that not having a black background doesn't necessarily improve battery life. Makes sense considering I have icons everywhere on my screen.
@Shuggins - Thank you! That's exactly what I was looking for. I've downloaded it but now I have to, er charge my battery a bit before I can take a close look at it.
@jsmith8858 - Are you running setCPU? A couple days ago I noticed my battery running pretty hot. I stopped using setCPU and the battery cooled down a lot. I've used setCPU since them without the heat issue so I'm not sure what was going on.
Well during todays iteration I ran for about 12 hours (typical). I had a couple short phone calls, 2 email accounts syncing as well as other bg syncing processes. I did eat up 30% in an hour messing with a game. I'd probably have 13-14 hours if I didn't play anything (but if I didn't what's the point of the phone . Still, as much as I love it the screen is killing me. Guess there's nothing to do about it though (usually brightness is all the way down, turn it off when I'm not using it, using a darker background). I didn't kill any of my background processes today. I'm going to set up that Autostarts program and start auto-killing various programs tomorrow.
You can try using autokiller and art it to extreme, but I don't recommend this
Sent from my HTC Dream using XDA App
The last couple of days my battery has been draining ridiculously fast. It just went from 50% to 8%, just sitting in my pocket without otherwise being used, in the last 3 hours. Here's what the battery usage displays:
while unplugged for 3h 3m 24s:
Android OS 81%
Cell standby 10%
Phone idle 4%
Display 3%
Android System 2%
Obviously something is going on with Android OS and I suspect something I've installed is doing this. I have Watchdog installed but it hasn't given me any warnings. Is there some way to determine exactly what is causing the battery drain, other than removing apps one by one?
Thanks!
I've suspected that my display keeps coming on when my phone is in my pocket.
Both the power button, and the trackpad turn on the backlight for 15 seconds when pushed, and it's very easy to do both when the phone is in your pocket.
I stopped using the HTC weather app, there is no way to stop it from constantly searching your location and it kills the battery FAST if you are on the move. Since I stopped using it I have seen 10+ hours of battery life a day and I use it hard, internet, gps, music, twitter.
It's the suspend process.
I can't link it to you cause I'm on the phone but if you look around, you'll be able to find it.
Sent from my HTC Glacier using XDA App
I don't think it's the display because the battery usage isn't showing the display as the main battery usage (unless I'm really using it for a long time). It's definitely something belonging to "Android OS". I wish there was a way to determine specifically what process within "android OS" is to blame. I really don't know much about Android or Linux in general so "android OS" is mostly a mystery to me.
I did uninstall several programs yesterday night and was almost convinced it was behaving better but it looks like after the first hour that Android OS is creeping up and overtaking the battery usage and the battery is draining pretty fast despite not using the phone other than to occasionally check the battery usage. At the current rate I'd be lucky if the phone isn't dead before the end of my workday. It probably doesn't help that I have a rather weak signal at work but if it was increased power to the cellular radio that was the culprit, would it show up under "Android OS" or "Cell standby"? I'd suspect the latter, but maybe Android isn't so logical in how it groups processes....
I'll try removing the HTC weather widgets as suggested and look up the sleep process.
Thanks!
It is the "suspend process" like that other poster said. Here is the defect, you can read through if you like. It's a known problem and not only isolated to mt4g
http://code.google.com/p/android/issues/detail?id=11126
How did people determine it's the "suspend" process? I can't seem to find any way to determine what processes are specifically involved. Is there an app that will tell you that? I am running Watchdog Lite set to alert me at 50% cpu and have never got an alert which makes me question whether my issue is the same one described in that thread. Various people were describing 100% cpu activity by the suspend process and it doesn't seem to be the case with me.
I did have 2 weather widgets on my home screen. I deleted both and since then the problem appears to have gone away. I'll have to wait a while to see if it's truly fixed or just a coincidence. Someone in the suspend thread did mention that plugging into a charger temporarily fixed the issue and I did charge the phone for a while after deleting the widgets so I'm not convinced just yet.
One thing I did notice in the battery usage is that google maps seems to have a significant presence, despite the fact that I haven't used maps at all since last unplugging the phone. What is maps doing in the background? I wonder if it's trying to determine my location and cache map data...
Thanks!
Install Watchdog and in its settings, include, monitor, and display all phone processes.
HTC Glacier running CM7 #15
Enable system process and set thrashold to 30% and you will see the suspend process. Or when you notice the drain is happening go to the phone hidden menu. You know the #*#*3626*#*# in the dialer and then from there go to battery usage then select CPU usage, you will see the suspend process on the top or near the top.
Just use some memory management apps. I currently use ES task manager and in advanced settings, i set it to kill all processes when i power down screen. I never use any battery when phone is unplugged(i literally left my phone unplugged overnight midnight to about 7am and it stood at 73% entire time). And having it rooted, i use SetCPU and set the phone at around 768mhz powersave when i'm not messing with the phone heavily. I easily can squeeze about a day and a half out of the battery.
knaries2000 said:
Enable system process and set thrashold to 30% and you will see the suspend process. Or when you notice the drain is happening go to the phone hidden menu. You know the #*#*3626*#*# in the dialer and then from there go to battery usage then select CPU usage, you will see the suspend process on the top or near the top.
Click to expand...
Click to collapse
Is that the correct sequence/code? I put that in and didn't get anything. Is root required?
Sent from my HTC Glacier using XDA App
sorry, that was not the correct sequence at all. I was trying to do it by memory. It is *#*#4636#*#* then select battery history, in the first dropdown box select cpu usage. That menu is pretty useful for other things to like network usage breakdown per app, gps usage, etc.
el-jodio said:
Is that the correct sequence/code? I put that in and didn't get anything. Is root required?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Thanks for all the info. I particularly like that hidden menu. I had no idea that existed...
Since removing the HTC weather widget my battery drain issue has completely disappeared. The battery now lasts a reasonable amount of time.
Thanks!
knaries2000 said:
sorry, that was not the correct sequence at all. I was trying to do it by memory. It is *#*#4636#*#* then select battery history, in the first dropdown box select cpu usage. That menu is pretty useful for other things to like network usage breakdown per app, gps usage, etc.
Click to expand...
Click to collapse
Thanks. Are there any other secret codes that do other things? Like the *#*#checkin#*#*
Sent from my HTC Glacier using XDA App
checkin menu does exist too. Those are the only 2 I know off. If other people here know of any please post.
Actually I have removed the HTC weather widget couple of days ago and also disabled the water sync in account settings too. That seems to have help with the suspend process on my phone also.
knaries2000 said:
Actually I have removed the HTC weather widget couple of days ago and also disabled the water sync in account settings too. That seems to have help with the suspend process on my phone also.
Click to expand...
Click to collapse
What's the "water" sync? Is that a swype typo for "weather" sync? (Swype errors are annoying in that their usually not so obvious.)
I had also disabled the weather sync (forgot to mention it). Seems to be a lot of little bugs in Sense that need to get fixed.
Why don't you guys do what I did... I have profiles set on setCPU so that when the screen is off the phone runs at 368mhz max and the when the screen is on it'll go up to opp speed... That actually saves alot of battery for me.
Sent from my HTC Glacier using XDA App
Sorry it is weather sync. Yeah keyboard error. I stopped using swype recently for this very reason, but touch input isnt perfect either but still much better for me.
Ya if you are using OC based kernel then use SetCPU to scale your mCPU. Set few profiles for example my max is 1.7ghz, avg is 1.2ghz, min is 768mhz, idle is 368mhz.
Sent from my HTC Glacier
I have been obessing over my battery stat page and am trying to figure out what exactly "Android System" is. It is usually consuming the highest percentage of battery power. I have tried everything to figure out what action exactly makes Android System get added to the battery stats page. I have disabled everything, every radio, syncing, deleted all widgets. I hardly have any apps as it is. It just seems rather inconsistent because sometimes Ill check the page after making a call and will find that Voice calls has consumed a small percentage of battery and Android System isn't even on the list. Other times I will take it off the charger and make a 30 minute call, but when I check the stats page 70% battery was used by Android System and only 3% was Voice Calls.
Can anyone tell me exactly what triggers Android System so I can make sure I cut down on its battery usage in any way possible
Sent from my Microwave
I assume you are looking in the settings > about phone > battery. You can select android system also and it will tell you more info.
Agoattamer said:
I assume you are looking in the settings > about phone > battery. You can select android system also and it will tell you more info.
Click to expand...
Click to collapse
I see that but under more info its not very clear about what's using the batt.
Sent from my Microwave
http://img.photobucket.com/albums/v673/seh6183/screenshot-1312932238053.png
Sent from my Microwave
Anyone have any comments on this?
Sent from my Microwave
Did a battery calibration and now android system isn't the number 1 thing consuming battery as usual. Weird:
http://img.photobucket.com/albums/v673/seh6183/testshot.png
This seems to be more in line with what normal battery usage should look like in my opinion.
Sent from my Microwave
I had this problem too until I did a calibration. Now cell standby consumes over 50% of my battery regularly, with android system consuming only 2%.
Sent from my HTC Inspire 4G using XDA App
Yea I did a calibration and all is well
http://img.photobucket.com/albums/v673/seh6183/screenshot-1313102466360.png
Thank you
Sent from my Microwave
Aaaaaaaaand were back LOL
http://img.photobucket.com/albums/v673/seh6183/screenshot-1313118381659.png
Sent from my Microwave
Its still occurring
What would you guys do?
Android system will occasionally use CPU as well, as shown in the following screenshots. Also! My good buddy let me see his Droid x recently. He had 42% battery life left and android system had only taken up 4% of that.
I'm pretty upset about this.
http://img.photobucket.com/albums/v673/seh6183/screenshot-1314312490137.png
http://img.photobucket.com/albums/v673/seh6183/screenshot-1314312473018.png
http://img.photobucket.com/albums/v673/seh6183/screenshot-1314312512785.png
Sent from my Microwave
If you asked me I would say all your values are a little screwy. Do you even turn the screen on, on your phone and use it? If you use your phone the Display should be by far the most used. To me it looks like you physically use your phone very little. That is why Phone idle and Android System seem to be the higher numbers.
Guessing you have many accounts syncing in the background. One of the biggies for Android System. So its not that Android System is using so much, the rest of the processes are using so little.
Oddly enough the same thing started happening with my phone recently too.
@Agoattamer
The system wouldn't eat most of the charge in less than 8 hours in normal circumstances. Also about your question concerning accounts, while I'm not seh6183, personally I only have my email account synchronizing and the very same thing happens.
Something is causing the CPU to remain awake, in my case stuck at 800MHz.
The factory reset will most likely solve it, but it'd be best to find the culprit to just try and rectify a specific anomaly rather than reinstalling the whole system.
Has recently any core Google apps been updated? Email, Maps, anything?
I do agree that in 8 hours of non physical use your battery should not be going dead. So I couldn't sleep last night and I did some google searching. Here are some things I found out.
Do you have Googles Goggles installed? Seems it may have a bug where it keeps the camera on even when the phone is supposedly asleep.
Seeing that seh6183 always has his wifi active maybe it has something to do with wifi. I found this from Juri's TechBlog
couple of days ago I finally got the eagerly awaited system upgrade to Gingerbread on my Nexus One. The update went pretty well, although some Nexus One users reported about problems with the updating process. The only thing I noticed is that Dropbox didn't work after the upgrade.
A re-install solved the issue. All-in-all Gingerbread is great. Beside UI enhancements it feels also faster than Froyo. However, after trying it for two days now, I noticed a substantial increase in battery consumption. By looking at the system battery stats (Settings -> About phone -> Battery use), Android System was listed to consume 23% of the battery .
Apparently the problem is a bug in Gingerbread version 2.3.3 (you know there is 2.4 as well) on how the system handles the Wifi adapter. If you go into your Settings -> Wireless & Networks -> Wi-Fi settings, press the menu button and click on "Advanced", you'll see a menu entry "Wi-Fi sleep policy". Gingerbread seems to have a problem when that option is set to "When screen turns off". While that may sound to be the most energy-saving option, the bug turns it into a battery killer. If you switch the option to "Never", the Android system will only consume ~3% in the battery stats.
Obviously, in addition to this, the best battery saver is to just turn Wi-Fi off when you don't need it . Caution, if one of the future updates fixes this problem (which I strongly hope), you have to set the option back again.
Click to expand...
Click to collapse
Something I didn't see but killed my battery on my windows mobile phone was instant messengers. Do you use any apps that are for instant messaging.
Found this thread also talking about the same bug with wifi
http://code.google.com/p/android/issues/detail?id=15057
So it seems that if you (cmdr001) also are a full time wifi user, you may be affected by the same bug. Check your wifi sleep policy and adjust your settings to "Never".
Install a battery monitor app from the market or spare parts to see what is using your battery. Install Juice Defender to stop all that excessive useage.
Excellent find!!!!!
Just switched the sleep policy to "never" (which ironically I've always used until very recently). Ill return with results after about 5 hours. The only thing is that I'm on android 2.3.5 not 3.3 so we will have to see if the bug was affecting me.
I also don't have Google goggles. And to the above poster, my phone regularly went into deep sleep so it wasn't my CPU that was staying active.
Oh and I've been using watch dog to look for rogue programs for the last 24 hours. I haven't got a single alert.
Sent from my Microwave
I guess the first question should have been what ROM were you using and to try a different one then. Needless to say it still has 2.3.3 components in it. And if you recently changed that setting then my bet is thats the issue. Goodluck.
Watchdog may alert you if you are using too much cpu at one time but I don't think it will let you know what is constantly using the cpu.
Ok there's a glitch somewhere in the battery tracking. I just checked it and android system was consuming 12% battery. I placed one 17 minute phone call and re checked it, I then had 57% android system consumption.
No way.
I'm using a cm7 nightly and I'm about to flash the stable version with a different kernel. Ill do a full wipe as well.
Sent from my Microwave
You could check your wakelocks.
After recharging my battery to 100% and wiping the battery stats, my android system consistently uses 2% of the battery, while the display sucks up around ~40%.
I know I've made a few posts about this in the past, but now I've learned a few things since then.
I know the battery isn't the greatest on the infuse (no rom that I'm using atm..) but would like to get the most juice out of my device that I can. I have root access and currently use the apps "battery calibration" and "no-frills CPU control" which I set my cpu at a relatively low frequency to help keep juice.
My phone is drained throughout my day, even without use. I believe it primarily happens because my data (mobile network) consumes it. I know apps such as "juice defender" are great at reducing idle drainage because it shuts off your network connection while in idle to save battery. However, I have used this application in the past and after a few days of use, it shuts off my mobile connection altogether.
My question is, if I were to use this application again and my mobile network were to malfunction, would I be able to change my apn to regain my network connection? In the past I had to reset my phone to regain connection, which isn't really worth using if that's the only solution.
Or are there any other battery saver apps worth using??
Thanks
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
Dr_Nacho said:
I know I've made a few posts about this in the past, but now I've learned a few things since then.
I know the battery isn't the greatest on the infuse (no rom that I'm using atm..) but would like to get the most juice out of my device that I can. I have root access and currently use the apps "battery calibration" and "no-frills CPU control" which I set my cpu at a relatively low frequency to help keep juice.
My phone is drained throughout my day, even without use. I believe it primarily happens because my data (mobile network) consumes it. I know apps such as "juice defender" are great at reducing idle drainage because it shuts off your network connection while in idle to save battery. However, I have used this application in the past and after a few days of use, it shuts off my mobile connection altogether.
My question is, if I were to use this application again and my mobile network were to malfunction, would I be able to change my apn to regain my network connection? In the past I had to reset my phone to regain connection, which isn't really worth using if that's the only solution.
Or are there any other battery saver apps worth using??
Thanks
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
A bit more information is needed before a specific course of action can be recommended. How much battery life are you using in an average 24 hour period? Also, what version of Juice Defender(beta, free, plus, ultimate) are you using, and what specific settings are you utilizing. It is a very customizable program after all. You might look into Battery Indicator Pro, which estimates your total remaining battery life based on your level of usage. I would also recommend CPU spy, which, if your device is rooted, will show the percentages that your device is running at various CPU levels.
If you turn off all the locational stuff, turn off 'update my current location' in Navigator, and set your CPU gov to conservative, you might get better battery life. I've not had any lasting luck with any of the battery saving apps. In the end, I decided to buy a couple of Anker batteries from Amazon just in case I have a bad battery day... Also some of the battery saving mods work, but I'm not sure about applying them to ICS and JB ROMS. I haven't tried!
Battery life is what you make of it..
Anything running in the background will drain the battery.. email constantly checking for new messages, twitter, Facebook, GPS, WiFi if no connection is found, etc..
Anything that makes the phone process even while the screen is off is going to kill a battery..
What ROM are you using? Some ROMs have better life than others..
How much are you actually using the phone?
What's the brightness set at?
Have you tried changing the processor and slowed it down?
Lots of information that is missing is helpful..
Its powered by Jellybeaned AOKP!
I know apps such as "juice defender" are great at reducing idle drainage because it shuts off your network connection while in idle to save battery
Click to expand...
Click to collapse
Some have good luck with these, others don’t. I prefer to try to adjust settings myself.
I believe it primarily happens because my data (mobile network) consumes it.
Click to expand...
Click to collapse
How about putting a widget on your homescreen to toggle data on/off. Keep it on only when you need it. I go a step further, I use Tasker to automatically turn my data off every time my screen times out (because that means I’m not using it... I can restart my data later with my widget when I need it). Maybe that’s extreme, but I’m not just watching my battery.. I’m managing my limited data plan.
My phone is drained throughout my day, even without use.
Click to expand...
Click to collapse
It may be that you have wakelocks keeping your phone awake when it’s supposed to sleep. One way to see this is (in GB or above) Settings / About-Phone / Battery Use...then click on the small graph at the top... should expand it to a large graph with traces along the bottom including Awake and Screen On. If you have long periods of time where phone is awake while screen is off, that’s a wakelock problem. A good program to troubleshoot that is Better Battery Stats. If nothing else, follow the instructions in the first post in the BBS thread linked below, and then post a dump to the end of that BBS thread (the developer and a lot of other knowledgeable people follow that thread and will help you interpret results):
http://forum.xda-developers.com/showthread.php?t=1179809
Thru use of BBS, I found that Google Maps is one that was keeping mine awake and I think someone else on the forum reported the same. If that program (Maps) is causing problems, you can disable it from auto-starting on boot using Gemini Manager. It will still be available when you need it, just take a few seconds longer to load the first time after boot. Then need to reboot to stop it from causing wakelocks after use (there may be other easier ways, but this works for me).
Another program (Power Tutor) was helpful to me to see programs that were consuming unusual amount of battery although not necessarily thru wakelocks. In my case Dolphin Browser HD was occasionally drawing very high power even when that program was not actively in use.
electricpete1 said:
I found that Google Maps is one that was keeping mine awake and I think someone else on the forum reported the same. If that program (Maps) is causing problems, you can disable it from auto-starting on boot using Gemini Manager. It will still be available when you need it, just take a few seconds longer to load the first time after boot. Then need to reboot to stop it from causing wakelocks after use (there may be other easier ways, but this works for me).
Another program (Power Tutor) was helpful to me to see programs that were consuming unusual amount of battery although not necessarily thru wakelocks. In my case Dolphin Browser HD was occasionally drawing very high power even when that program was not actively in use.
Click to expand...
Click to collapse
So how can I stop maps to running in background? only rebooting the device is the only option?or is there any other option?
TIA
atrix4nag said:
So how can I stop maps to running in background? only rebooting the device is the only option?or is there any other option?
TIA
Click to expand...
Click to collapse
Just to provide more details on my previous post (not sure if it's answering your question):
I followed instructions here:
http://forum.xda-developers.com/showpost.php?p=29420959&postcount=7059
In particular, I installed the free program "Gemini Apps Manager". That allows you to stop programs from auto-loading at boot.
So I used the program to stopp Google Maps from auto-loading at boot.
That stopped a large chunk of my wakelocks, as long as I don't manually launch Google Maps.
If I do manually Google Maps, then those wakelocks come back, and to get rid of them I have to reboot.
I don't use Maps that often (only when I go on trips), so it's not a big problem for me to reboot when I'm finished with my trip to help keep my battery use low.
It may also be possible to kill it from the list of applications at Settings/Applications/ManageApplications and killing botht the application and the process...but I'm not sure if it will stay killed that way... haven't tried. I know some applications have hooks that make it hard to get rid of them once they're launched.
But (if you haven't already), I think it's a good idea to use BBS to find out what programs are causing problems on your phone. You may have other apps causing lot bigger problems than Maps. And it certainly may be the case that a program that acts up on one phone can be fine on another phone due to differences in the way the user configures the application settings and the phone settings (along with other possible differences in application version, ROM used, etc etc).
electricpete1 said:
Just to provide more details on my previous post (not sure if it's answering your question):
I followed instructions here:
http://forum.xda-developers.com/showpost.php?p=29420959&postcount=7059
In particular, I installed the free program "Gemini Apps Manager". That allows you to stop programs from auto-loading at boot.
So I used the program to stopp Google Maps from auto-loading at boot.
That stopped a large chunk of my wakelocks, as long as I don't manually launch Google Maps.
If I do manually Google Maps, then those wakelocks come back, and to get rid of them I have to reboot.
I don't use Maps that often (only when I go on trips), so it's not a big problem for me to reboot when I'm finished with my trip to help keep my battery use low.
It may also be possible to kill it from the list of applications at Settings/Applications/ManageApplications and killing botht the application and the process...but I'm not sure if it will stay killed that way... haven't tried. I know some applications have hooks that make it hard to get rid of them once they're launched.
But (if you haven't already), I think it's a good idea to use BBS to find out what programs are causing problems on your phone. You may have other apps causing lot bigger problems than Maps. And it certainly may be the case that a program that acts up on one phone can be fine on another phone due to differences in the way the user configures the application settings and the phone settings (along with other possible differences in application version, ROM used, etc etc).
Click to expand...
Click to collapse
Thanks for your detail explanation. My main question was how can close the app without restarting? i feel my major battery drain is from dolphin browser, befor dolphin i used opera, even that has the same problem. Most of the time, if I dont open dolphin, my phone battery is good, but once I open it, it drains battery. So i am looking for soemthing simple which does, without rebooting the device.
Any way thanks for your help.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------What I have right now out of Doze are "Bluetooth MIDI Service", "Bluetooth Share", the "Clock" app and two other Clock apps.
I am not sure how effective is the method listed below after the last update. Stay tuned.
Also I think the current version of Facebook Messenger is draining too much battery.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------Hello everyone,
when I bought my Zenfone 3 ZE520KL, I was amazed by it's battery life. I could easily get around 8 hours of SOT in a single charge with moderate usage. My device was running Android Marshmallow 6.0 out of the box, but performance wasn't as good. On Nougat, performance is much better and faster, also I used to get some lags and frozen screen, the capacitive keys also sometimes froze when I was charging my phone, but now I don't get issues like that as often as before. Interface is so much more appealing and I love it.
But what about battery life? I started getting around 5 hours of SOT.. which is still good, but not really close to 8 hours. I thought a lot about these 3 hours that were missing so I decided to start investigating. I wanted to share my findings with you so maybe you would know something that could help.
It's been two weeks since I have been testing out different things. The apps I used to do my research are:
Carat. What I love about this app is the process list. It shows exactly which apps and system processes are running in the background, so I can control them very easily.
Greenify. Thanks to the Carat app, I can see which apps continue running in the background, so I can use Greenify to hibernate them after I'm done using them. (Examples: Youtube, Snapchat etc.). Also I bought the Donation Package, and unlocked the other modes using adb commands (my device is not rooted).
BetterBatteryStats. This app is usually used to detect wakelocks. I limited the Google Calendar App from syncing so it doesn't use too much battery in the background. This app is paid in Google Play but you can get it for free from here.
What I did to get better battery life:
I excluded the services, that were always running in the process list from the Carat App from Doze. Apparently, the new Doze in Nougat gives us permission to optimize more system processes and services than before, which can backfire - Doze starts trying to kill processes that can't be killed, and this results in consuming more battery juice than saving it.
How to enter Doze settings and make the following changes:
Go to "Settings" > Select "Battery" > Tap on the three dots at the upper-right corner > Select "Battery Optimization" > Select "All Apps" > Find and tap on the Apps/Services/Processes I have listed below > Select "Do not optimize". The other apps and services should stay optimized.
The apps, processes and services that I removed from Doze are:
Android Services Library
Android System
ASUS Calling Screen
Bluetooth MIDI Service
Bluetooth Share
Camera
Clock
com.android.smspush
com.asus.keyboard
com.asus.shim
com.qti.qualcomm.datastatusnotification
com.qualcomm.qti.tetherservice
org.codeaurora.bluetooth
org.codeaurora.ims
com.qualcomm.qcrilsgtunnel
ICESound Service
Mobile Manager
MobileManagerService
System UI
Telecom Service
Telephony Service
ZenUI Keyboard
ZenUI Launcher
Some other apps that I'm using: Do It Later, Greenify, Messages, Nova Launcher, Timely, Weather.
Please do a full charge to 100% afterwards and check if the battery still drains as quickly as before. Your feedback will be greatly appreciated.
I am already starting to see improvement in my battery life. I was losing around 2% on Stand By and battery was draining fast when I was using the phone, but now I lost 0% on Stand By overnight and 10% for 1 hour of SOT (before this I was losing 10% for 30 min. of SOT). I am still trying to figure out which services exactly are causing the drain, when they are being optimized. Maybe the services, included in the Android System? (Check them from Settings > Battery > Android System > Included Packages). I deleted Facebook and Twitter apps and started using them from Chrome (almost the same thing, I quickly got used to that). Please check the updates below for more info and share your opinion or advice in the comments so we can all reach a better experience with this amazing smartphone.
Thank you for reading!
Update1: 6h30min SOT with 30% left (917mAh, 35%), but I will have to charge now. I have been messing with Doze a lot, maybe I'll get more clean results later. Progress has been made though, at least with my device.
Update2: Something interesting - my J-Score with the Carat app before and after starting this experiment: http://i.imgur.com/Q8u6HBD.jpg
Update3: There is a battery drain when making voice calls - 226mAh (7%) were lost because of 43 minutes long talk time.
Results were worse after testing with the second list removed, although there wasn't much draining with the screen on: SOT - 5h20min for 70% of battery (752mAh, 20%).
Update4: com.android.phone appears as a wakelock at BBS (Wakeups:8). Also 2h30 SOT for 30% used battery (100-70%~408 mAh). I'm updating the list and trying again.
Please note that my phone is updated to the latest firmware WW_Phone-14.2020.1703.28-20170410.
Update5: com.android.phone is still an active wakelock (Wakeups:14), but SOT is 2h34min for 30% used battery (100-70%~343mAh). At 30% battery left, SOT is almost 6hrs(28%~787mAh), Device Idle is at 10% (291mAh). The MobileManagerService is causing way too many wakelocks and is probably the reason for the high Device Idle battery usage.
Update6: MobileManagerService is no longer showing as a frequent wakelock. com.android.phone (Telephony Service - Wakeups:9) and com.google.android.apps.messaging are the most persistent wakelocks, other than that battery life is amazing at the moment. SOT is 2h45min for 30% used battery (100-70%~366mAh). I also had 27 min of talk time (4%~145mAh). At 30% left, I have 6h33min of SOT (32%~912mAh). Device Idle is again at 10% (292mAh). We are ready for the final test.
Update7: The results are quite interesting. After removing com.qti.qualcomm.telephonyservice from Doze, com.android.phone stopped appearing as a frequent wakelock at first, but now, at 70% it has 16 wakeups. SOT is 2h22min (100-70%~318mAh), so it's not better. I'm going to try a few more changes.
Update 8: I posted it as a reply here.
Update 9: I shouldn't have put Task Manager out of Doze, I get so much better battery life now. The update is ready, check it here.
Good post, thank you for investigating this, please let us know if you find more stuff or what exactly is responsible for it and an easy way of fixing.
1noob said:
Good post, thank you for investigating this, please let us know if you find more stuff or what exactly is responsible for it and an easy way of fixing.
Click to expand...
Click to collapse
Hello! Thank you for your reply. I'm so happy I could help others and myself with this thread, but I also need to know if you are also seeing any difference. Please check here regularly!
Also, I'm guessing that when you put your system processes and services in Doze, you also decrease their performance, which causes battery draining, as they try to run normally and do their work. Doze is trying to prevent them from doing that. This is my conclusion, but only results will show if I'm correct. If you own yourself a Zenfone 3, please feel free to report if you experience any changes using my method.
Thank you and have a nice day!
Hi, thank you for the post. I have a zenfone 3 here and will try your method.
I'm trying it on ze520kl with marschmallow, it seems working fine. :highfive:
Do you remove the first and second list from doze ? or ate testing with only the second list now?
Nice findings btw
pedromms86 said:
Do you remove the first and second list from doze ? or ate testing with only the second list now?
Nice findings btw
Click to expand...
Click to collapse
I have removed everything from both of the lists. It's still early to say but no major battery drain is noticed for now. Thanks!
bibbomio said:
I'm trying it on ze520kl with marschmallow, it seems working fine. :highfive:
Click to expand...
Click to collapse
Awesome! :good:
Thank you so much for this article. Well written as well. I have applied the changes and so far no issues (it has been 6 h is). Will report once I have more history
I remove the apps from doze, and can say it really improve battery (test for one day)
thanks !
@Blackrose110 any news improvements after update3 ?
New update is released via OTA (~500MB).
pedromms86 said:
@Blackrose110 any news improvements after update3 ?
Click to expand...
Click to collapse
Too early to say, also I got a weird wakelock, and lost 2% overnight. I lost the results (100-90%) after a restart. Now I'm going to update my phone and start again.
I had 8% used up on 43 minutes of SOT, and 2% lost on voice calls (100 and something mAh). I went to bed with 92%, I guess the other 2% were lost on that wakelock and the clock wakelock. These 2% were lost on equal intervals.
It's going to take a while, I'm just using my device normally. I don't have time to be on my phone all the time, also the battery is harder to drain now. At this point, I'm just trying to get better results.
Cheers!
pedromms86 said:
@Blackrose110 any news improvements after update3 ?
Click to expand...
Click to collapse
Check again tomorrow!
RobinRo said:
New update is released via OTA (~500MB).
Click to expand...
Click to collapse
Updating...
I don't think it is a good ideea to change Doze settings for system services like com.qualcomm.* or telephony*.
In theory, these services should be compatible with operating system and they should work as designed. I would focus on third-party apps who doesn't work well on Nougat.
Anyway, is just an opinion and i'm looking forward for updates
ci6i said:
I don't think it is a good ideea to change Doze settings for system services like com.qualcomm.* or telephony*.
In theory, these services should be compatible with operating system and they should work as designed. I would focus on third-party apps who doesn't work well on Nougat.
Anyway, is just an opinion and i'm looking forward for updates
Click to expand...
Click to collapse
Hello ci6i, I also agree with you, and that's why I excluded all of them from Doze when I first tried this out. At the moment, I removed only those system services, that run in the background all the time. My goal is to find the least amount of system services and processes, that are causing battery drain when the phone is in use.
I am not saying that you should do exactly what I did. It's best if you try out yourself on your own device what works and what doesn't.
I also have only excluded from Doze apps that I use daily. But everyone is using different apps and it depends only on the developers to update them.
You can download Carat for free from Google Play and check the process list, it's very useful. The app itself doesn't use any battery.
Good luck!
Blackrose110 said:
...
I am not saying that you should do exactly what I did. It's best if you try out yourself on your own device what works and what doesn't.
I also have only excluded from Doze apps that I use daily. But everyone is using different apps and it depends only on the developers to update them.
...
Click to expand...
Click to collapse
I agree with you and i really appreciate your work Yesterday I've installed Carat after i read your first post and today i did new OTA update and cleared cache partition. Let's see how it works in the next few days.
What should I do next, guys? Remove other com.qualcomm/com.android/com.asus services or remove just MobileManagerService from Doze? I'm thinking about the second one, I'm curious to see if ti makes any difference. I think the results from the first test were the best, and the MobileManagerService was out of Doze as far as I remember. Might as well try and see what happens.
It's a bit hard to drain the battery these days, so updates might not be fast. Patience is key!
Yeahh final test!! Looking forward to the result