[Question][Task Killer] Leaving Only Selected Apps and Kill the Rest? - Android General

Hi,
First of all, this is a task killer question, and I know it has been preached again and again that task killers should not be used, which I do agree but need more clarification. I've googled and still can't find the answer to my question.
Current Phone : Huawei P9 Lite
Current Protected Apps Setting : Nova Launcher, Whatsapp, Inbox, Amplify, Greenify
So Huawei phones has this Phone Manager which is essentially a Task Killer and Memory Cleanup Utility to me.
To ensure that an app doesn't got killed after screen off, I need to add that app to be "Protected"
We all know that killing an app and have it restart/reload when being opened is bad(extra battery drain)
Hence my question:
Does killing an app, for example Chrome or Facebook, stops all it's background process after screen off? and thus stops battery use from that app? Previously before using Greenify, I have had incidences whereby Chrome kept my phone awake for the night if I didn't kill it.
Does this incident happens to you? As in, you trust android to manage memory, but having those app behind in background would simply just gives it a chance to run and keep your phone awake, such as Google Now, Maps(This! is notorious.....)
Looking to have 0.5% battery drain overnight if that is possible..

Related

Managing Memory

Hi all,
One habit I've developed with the Captivate is using Advanced Task Killer to kill apps that otherwise would just be hanging out in memory. I do this probably because I'm anal retentive like that, but also with the thought that it save me battery life if I do.
This has led to two questions of mine (excuse the noobiness to Android if these have been discussed):
1.) Why do so many applications start automatically when the phone boots up? (browser, gallery, etc etc). Is there a startup ini somewhere I can edit to prevent this or do all the apps just wake up? It's easy enough to kill, but I find some of the apps that start up very odd.
2.) Over the course of the day, even with Autokill on and security set to "Low", eventually my memory is consumed and it only gets back to its full state until the phone is rebooted. After all obvious apps have been killed the memory usage will will go from ~170mb (after a reboot) to as low as ~130mb (at the end of the day). Does anyone know why that happens and if there is a better way to manage memory/apps?
Thanks.
I used to use task killers, but I have uninstalled them and just let android do its thing. The only reason I'll end a program is if the program has an exit function or has froze, which is rare. With this method I don't have any slowdowns and great battery life. On the flipside I don't install poorly developed apps. Thats just me though.
Sent from my SAMSUNG-SGH-I897 using XDA App

Sure fire way to stop background programs from running?

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

[Q] Q: Battry

pls I have purchased Desire S. in fact, i face a problem with battry life
could you advice me for any solution?
Settings>Sound>Pocket mode off (uncheck) that will help a bit.
Oh and don't try task killers they are useless.
And leave only syncing of essential programs on(like mail, weather, facebook/twitter..) and stop the stocks, news... useless stuff.
Thank you for your early reply
Also turn off auto brightness adjustment, set it to 30% (very good when inside) and add brightness widget to your home screen (to adjust when outside, bcs of sun)
are task killers really useless?> but how can I exit all of the apps that are running in the background? I think they drain a lot of battery juice on my desire S.
ghuk said:
are task killers really useless?> but how can I exit all of the apps that are running in the background? I think they drain a lot of battery juice on my desire S.
Click to expand...
Click to collapse
Thats what i tought at first...well is not how you think.
1. The memory uses same amount of battery even if used 99% or 5%.
2. When you "exit" one app, even if it doesn't close, it will use 0% cpu, and only stay in memory for quick start the next time you start it.
3. If you run out of memory, android will take care and close background apps to free up memory.
No need for task killers. Anyway, if you use task killers it will only use more battery because, some apps autorestart, using battery.
Background apps (not services, but apps you closed recently) run in background mode and only for some time, Android has it's own memory management.
ghuk said:
are task killers really useless?> but how can I exit all of the apps that are running in the background? I think they drain a lot of battery juice on my desire S.
Click to expand...
Click to collapse
It's just how latest Android works thus making task killers useless.
If you're still paranoid, install System Panel app. With it, you can see a crapload of apps running in the background, but none is using the CPU which is what drains the battery. You can still end tasks with it, but you'll notice some of it will be back up instantly.
So if you're constantly auto killing those background apps which then instantly comes back up and then killed again and then up again and on and on, it will end up using more battery than leaving it in the background.
I even see some games in the background apps lol. But does it drain my battery? No.
Don't worry about the memory, it'll never run out.
There is a section regarding extending battery life within this extremely helpful guide
http://forum.xda-developers.com/showthread.php?t=1097538
Sent from my HTC Desire S using XDA App
Once I have the syncing under control, and resist the urge to spend hours playing games, I find the biggest drain is the screen.
I'm using Screen Filter to reduce the backlight level in situations where the automatic brightness is just too bright. This is especially useful in the evenings.
Only problem with Screen Filter is it sometimes interferes with the touch-screen in places, like when installing an .apk - the Install button doesn't respond until I switch Screen Filter off. Weird.
Rather than use an application or the Auto setting which I think aims far to high.
I just simply switch screen brightness down to about 25-30% and then turn it up when I'm outdoors in bright sun light if and when needed.
I recommend what friend above said. You can add widget to your desktop and switch brightness by one tap.
Sent from my HTC Desire S using Tapatalk

[Q] Apps that drain battery?

Is there a definitive list of current apps that drain battery (whether on purpose or accidentally) in the background?
I have about a dozen apps installed and one that seems to consistently drain battery in the background is the Bank of America app. I'll notice my drain increasing dramatically throughout the day after I've used the app. Many hours later, I will see a Force Close message for the app.
I don't know what it's doing in the background, but it doesn't show up in the Running Applications or Services (I checked after I used and closed the app). Nonetheless, the Force Close message appears 4-6 hours later.
Has anyone else noticed similar behavior with the Bank of America app?
First make sure you don't have unneeded sync connections running. They are the fastest way to kill your battery.
Go to Settings > Accounts & Sync - Turn off the sync connections you don't need, especially anything HTC.
Use a task manager like ADT to monitor what apps are running. Some apps, like the ones included in the ROM will just run again, so no point in killing them. You could also use a battery monitoring app.
I've optimized my phone per best practices on these forums, but I'm talking about specific applications that may be buggy. The FC on the Bank of America app is unusual because it didn't show up in the Running Applications list, yet was killed later.
Are these Force Close messages (I've seen them for Bank of America and Pandora so far) Gingerbread killing off the app for memory? It usually happens many hours after I've opened the application.
This is my method: I kill all programs using the built-in task manager. Then I head to Running Services and whatever is there, it's draining battery.
Sent from my HTC Sensation 4G using XDA Premium App

[APP][2.x-5.x] [APK] BATTERY SAVER ULTIMATE

Overview
Battery Saver Ultimate application provides the best power settings to saves the battery time of your device or your tablet. Whenever the battery runs low or goes too much down, just tap the power saver app to turn on the saving mode.
Battery savers help you to switch off all the extra functions like WiFi, Bluetooth, GPS, sound and other energy consuming apps on the device. The app will notify when the power gets down in percentage and it even shows the charging stages.
Charging Stages:
Free Battery Saver Ultimate app regulates the manner in which your device is charged with a Unique 3 Stage Charging system to ensure you get the most out of your battery and reminds you not to over charge.
Types of Mode :
1. Saving Mode: (Use in lowest Battery Status)
Device Brightness set to 10%
In Activate WiFi of the Device
Stand By time to 15 seconds
2. Sleep Mode: (Use when you sleep)
Turn Off Call & SMS and turn ON the Flight Mode
Set Vibrations Off.
Airplane Mode.
Sound Off and mute media sound too.
Brightness set to 10% or minimum level.
3. Customized Mode
You can Customize app usages as your need to save Battery Power.
Can adjust the battery saving setting freely depend on your need and usage.
Can adjust WiFi, Bluetooth, vibration, sound, device brightness, synchronization and stand by time.
Features and Requirements
Accurate battery remaining time
Shows Standby Time.
Accurate charging remaining time
Schedule power saving modes for work/class/sleep and more!
3 Stage Charging system 1. Fast charge 2. Continuous Charging 3. Tickle Charging.
Wifi/Data/Bluetooth/GPS/Flight Mode toggle!
Brightness control!
Shows Battery Health, Current Battery Power in mAH, Temperature, Voltage and Battery life status.
Interesting app. I installed it on my tablet. Look up how it will work. Pity that application is not in material design...
Can I say dodgy app here full of ads and nothing as you say it is. Gives me to play games and full of ads. Avoid
Looks very Good though
Full of ads, nothing like advertised. Avoid.
mr_stax123 said:
Looks very Good though
Click to expand...
Click to collapse
Please state more
i want to prevent apps to auto start to save battery and ram, which app should i use, grrenify or autorun manager or any other?
First, you need not concern yourself with free ram on an Android device. Android manages resources better by itself. As for the apps that launch on startup, you can got to menu>settings>apps and select the "running" tab to show you exactly what is really running. Then, the easiest way is to uninstall the app in question.
Automated task killers do nothing but cause more problems than they can potentially solve.
You might find this thread enlightening.
mr_stax123 said:
i want to prevent apps to auto start to save battery and ram, which app should i use, grrenify or autorun manager or any other?
Click to expand...
Click to collapse
The task killer discussion gets old. I think there is risk of oversimplifying both sides. ie on one side people want to treat it like pc...not correct. On the other side people seem to imply any discussion of memory management considerations is irrelevant/rejected because "android will handle it all"....which is not always entirely correct either. The latter may be closer to the truth especially for new devices, but there is still room for middle ground. Not all programs are equal, some launch "services" which takes priority over other app processes. Too many of those services can eventually crowd out cache and slow your phone down. Maybe most people with newer phones will never get there, but there are still people with older phones (including the op for all we know) and also some folks with new phones who (if they listen to the oversimplifications) may get carried away on the number and type of apps they install over the life of their phone
---------- Post added at 12:47 AM ---------- Previous post was at 12:43 AM ----------
Even so, killing off those services is not the answer. If an older phone has too many running services so it taxes it's resources then it's either time to uninstall some or get a device that can handle it. If it's a problem with the app itself hogging resources, then let the developer know and find an alternative.
If you try to tow a boat with a bicycle, the answer isn't to throw away the boat's engine to make it lighter. Similarly, a task killer may make the phone's performance improve briefly, but over time it will make things worse. And it fixes nothing.
An app preventing another app from "auto-starting" is a task killer. Look at it this way: The phone boots up and runs it's processes. The auto-start blocker detects an app it doesn't want to run, so it kills it. Now, depending on what app it is, the phone may call for it again and thus running it later, which defeats the purpose of an auto-start killer, unless that app is a task killer which again kills said flagged app to keep it killed.
The way to properly manage an app you don't want to have enabled on the phone at bootup is to disable the app on the system manager (newer phones have it AFAIK), freeze the app via Titanium or similar apps, get into the app settings and disable certain features like auto-sync and set everything to manual.
However, the OP did not specify what phone and which apps. It may be apps which the phone requires to run at some level, like Maps (which several apps call for), or maybe the apps he is seeing are just RAM cached, which really don't matter at all.
Adjusting with app settings is preferred if you can, but does not always solve the problem (I referred to wakelock/battery drain problem with a certain version of Maps on my previous phone ... many people we having the same problem at the time and the only way to stop it was to block the app from starting as indicated in link below, or else to freeze it). Freezing has the disadvantage that you cannot run the program easily (requires you to launch TiBu to thaw the program). If you have blocked the program from autostarting, then it does not start at boot or other automatic time, but it remains available to manually launch the normal way (clicking the program icon). At that point (if it's a program like Maps), it will probably stay running until next reboot. It was my preferred solution when maps was giving me wakelocks and battery drain on my phone. Maps didn't run automatically on boot and never started until I manually started it. After that point I could live with the battery drain or reboot
Rom Toolbox Pro is a great app with many features and of course, there's an auto start manager that allows you to disable various receivers off the apps that start on boot. There's also a freeze/deep freeze feature as well. Great app

Categories

Resources