Related
According to Juicedefender battery saver-Autotask killer bad for our battery & which cause more battery draining.they directely said that avoid auto task kill.Is it true?
share your thoughts on that i,e sentence.
sent from sgm 5570
It really depend on how u use ur phone. If u kill task that u do not yse fir a long time it actually save ur battery on the ither hand if u kill an app amd then run it again it will drain mire battery. Also dont kill system app they will just start right up which lead to battery drain. I personnaly use advanced task killer and set ignore the app u often use, dusable autokiller and set security level to low to avoid killing system. But it just a matter of opinion really so just decude for ur self.
Cheer
Sent from my GT-S5570 using Tapatalk 2
Im using easy task killer for months now. Though I wasn't aware about it draining my battery. Thanks for this info. Though I havent had any issues, still Ill look more to it. :beer:
Sent from my GT-I8150 using xda premium
It’s still up in the air.
I'm using Advanced taskkiller.should i disable auto taskkiller.or auto taskkiller can effect battery?
[email protected] said:
I'm using Advanced taskkiller.should i disable auto taskkiller.or auto taskkiller can effect battery?
Click to expand...
Click to collapse
yes, it's better to kill app's manual
I also using two different task killer, but never set them to auto.. just like other opinion, it's true iff we continuously set the app to kill system or app we recently use, it might be drained our battery more effectively.. theoritycally it's just like you do the same task all over again in the same day.. wouldn't it gave you more exhausted than you do it only one time and manage to do it the other day..?
Sent from my PG06100 using Tapatalk 2
Here, i give you a reason why autotask killer is battery draining.
#1. Android kills app every 15 minutes when phone is almost out of memory, Android drastically pushes old app process and kill them so currently running app can be running. AutoTask Killer kill app foreground & underground apps process, underground apps generated by app itself, and generating underground app is use some battery & CPU cycle. Android kill app only it's FOREGROUND apps which still save alot battery rather than generate another Underground app which eats battery & CPU cycle.
#2. AutoTask killer kills system app. System app generates more cache & underground process than user apps, since system app always runned by Android for some reason (at JB 4.2.1 it's managed more extensively). Just like reason number 1, underground & cache generating in Android consumes ALOT of battery.
#3. Task killing consumes CPU Cycle, CPU will need to get it's higher hertz to keep speed, higher the CPU, more battery killed
#4. Task killing MAY free RAM, until Android generate another cache which eats up X2 RAM than old cache, since new cache refreshed and need to be intergrated with apps. More RAM, no More Multitasking !
#5. AutoTask Killer make apps process blocked, which slow-down apps, since app cache is deleted. To make the app keep smooth, CPU is set to it's higher hertz, just like reason number 3, higher CPU, more battery killed.
F4uzan said:
Here, i give you a reason why autotask killer is battery draining.
#1. Android kills app every 15 minutes when phone is almost out of memory, Android drastically pushes old app process and kill them so currently running app can be running. AutoTask Killer kill app foreground & underground apps process, underground apps generated by app itself, and generating underground app is use some battery & CPU cycle. Android kill app only it's FOREGROUND apps which still save alot battery rather than generate another Underground app which eats battery & CPU cycle.
#2. AutoTask killer kills system app. System app generates more cache & underground process than user apps, since system app always runned by Android for some reason (at JB 4.2.1 it's managed more extensively). Just like reason number 1, underground & cache generating in Android consumes ALOT of battery.
#3. Task killing consumes CPU Cycle, CPU will need to get it's higher hertz to keep speed, higher the CPU, more battery killed
#4. Task killing MAY free RAM, until Android generate another cache which eats up X2 RAM than old cache, since new cache refreshed and need to be intergrated with apps. More RAM, no More Multitasking !
#5. AutoTask Killer make apps process blocked, which slow-down apps, since app cache is deleted. To make the app keep smooth, CPU is set to it's higher hertz, just like reason number 3, higher CPU, more battery killed.
Click to expand...
Click to collapse
so a ram manager app or a script for ram is better?
Actually it depends on how you use. I use Advanced Task Killer pro to kill apps after a session and to monitor which apps open by itself and run in background. Those apps are the ones I freeze in titanium backup pro. Some of them are Google Maps, Facebook (I use it rarely, FB app sucks)
Dont use the scheduled auto kill option, that will drain the battery.
Saver battery
mortum said:
so a ram manager app or a script for ram is better?
Click to expand...
Click to collapse
I'm using TouchWiz V5 (JB 4.2.1) + Ram Manager Pro and also Seeder have saver my battery.
I'm not charge my LilG for about 2days and still working fine..
Seeder ==> http://forum.xda-developers.com/showthread.php?t=1987032
A little Tip
Our mini can't handle a task killer. I suggest you to not use any of them.
If you want to kill an app, use the "long press back to kill" option in cyanogenmod.
I need a app that freeze apps and make my ram low so I can have more memory some times apps are running when am not even using them I have been using ram manger pro and ram boost but the thing is that on ram boost it don't auto boost so is there any thing I can do
Sent from my SGH-I897 using xda app-developers app
To be perfectly frank, relax a little bit about it. When you see those apps loaded into memory, that's actually a good thing.
What's happening is that the Dalvik app, which is where Android's memory management tool is located, loads apps into memory where it can pull them up quickly. It takes less time for Dalvik to take an app that is loaded in memory and start it up for use than it does for it to pull it from storage, allocate memory, and start it.
Dalvik is usually pretty good about memory allocation, too, so if a program that needs more RAM appears, it will unload other programs from memory to provide the necessary space.
Any memory that isn't loaded with an app is, ultimately, wasted, as Dalvik will clear room as necessary. If you have a lot of memory available, that's all memory that could be used to load apps faster, giving you a better user experience.
If you have a custom kernel on your device, you should be able to find some tools to tweak how Dalvik handles the system (e.g. how much memory it allocates to each app, how it handles the ramping up/down of the processor speed, etc).
But am having heating issues on the phone
Sent from my SGH-I897 using xda app-developers app
IMO, Heating issues can be caused by an app overtaking the processor. that should be where most of your heat is generated anyways, not from the RAM. ON that note, Titanium Back will allow you to Freeze apps.
Rom toolbox (free or paid version) is an invaluable tool also
Sent from Mars via Curiosity
I understand the apps in the memory being useful part. What confuses and does turn it into an issue is that when you have many apps installed there is many in the memory. So if you are running a couple things and have many apps and the phone runs down to say 35-40mb ish then it sometimes starts to choke. But old phones with slower processors and less ram can go down to 20mbish. Is that just the standard cut off in most ROMs where its starts automatically freeing memory?
Sent from my SGH-I897 using xda app-developers app
Hey there, this problem might have been discussed before but I wasn't able to find it, so the problem is with ram usasage, I once went to the apps in settings and on the running apps I always see 250mb+ ram used by something, then I killed all the apps, but that just made a dliference of 50mb ram, It's real anoying because when I want to switch between apps it's slow and when I turn a browser back on after using aother app the page realoads which I guess wpuldn't happen with 300 mb ram, does anyone know the reason for this, I am currently running cm10.1.
Thanks!
ltkipras said:
Hey there, this problem might have been discussed before but I wasn't able to find it, so the problem is with ram usasage, I once went to the apps in settings and on the running apps I always see 250mb+ ram used by something, then I killed all the apps, but that just made a dliference of 50mb ram, It's real anoying because when I want to switch between apps it's slow and when I turn a browser back on after using aother app the page realoads which I guess wpuldn't happen with 300 mb ram, does anyone know the reason for this, I am currently running cm10.1.
Thanks!
Click to expand...
Click to collapse
What ROM and Kernel are you using?
Mango Polo said:
What ROM and Kernel are you using?
Click to expand...
Click to collapse
ROM; cm10.1 nigtly 20130330 galaxysmtd Kernel: 3.0.70-g7b668b [email protected] #1
Free RAM is useless. It just sits there sucking up power and being available in case you need it. It's pretty much a waste to have 300 MB of RAM and then only use 100 MB. Instead you should try to keep your RAM full at all times with the things you are likely to need in the near future. For example, if your phone is currently only using 20% of your RAM but already caches the browser in case you'll use it soon it will be faster to load the browser. If you decide to use the music player on the other hand the cached browser can be overwritten with the music player without requiring any additional time, so no harm is done.
Modern systems don't have "free" and "in use" RAM, they have "free" (wasted space), "in use" and "cached". You shouldn't look at the amount of free RAM but rather the amount of actually used RAM is a better indicator.
The reason you only gain 50 MB when you kill all apps is because only 50 MB will be actually in use by apps and all remaining unused space is used for caching things. If your phone is slow, this is not the cause of it. You may just have a slow phone or the ROM might be slow for some (other) reason.
Marshian said:
Free RAM is useless. It just sits there sucking up power and being available in case you need it. It's pretty much a waste to have 300 MB of RAM and then only use 100 MB. Instead you should try to keep your RAM full at all times with the things you are likely to need in the near future. For example, if your phone is currently only using 20% of your RAM but already caches the browser in case you'll use it soon it will be faster to load the browser. If you decide to use the music player on the other hand the cached browser can be overwritten with the music player without requiring any additional time, so no harm is done.
Modern systems don't have "free" and "in use" RAM, they have "free" (wasted space), "in use" and "cached". You shouldn't look at the amount of free RAM but rather the amount of actually used RAM is a better indicator.
The reason you only gain 50 MB when you kill all apps is because only 50 MB will be actually in use by apps and all remaining unused space is used for caching things. If your phone is slow, this is not the cause of it. You may just have a slow phone or the ROM might be slow for some (other) reason.
Click to expand...
Click to collapse
yeah only 50mb is used to keep the apps running, but it probably takes up a whole lot more when using the apps, and this is a problem for me that it is slow to change between apps, and when I do change between the for example if I wanna text some one back while using a browser, once i turn the browser back on it restarts the page, and that didn't happen in my zte blade, unless I had some more apps running.
I wanna know what is using those 250+mb of ram!
ltkipras said:
yeah only 50mb is used to keep the apps running, but it probably takes up a whole lot more when using the apps, and this is a problem for me that it is slow to change between apps, and when I do change between the for example if I wanna text some one back while using a browser, once i turn the browser back on it restarts the page, and that didn't happen in my zte blade, unless I had some more apps running.
I wanna know what is using those 250+mb of ram!
Click to expand...
Click to collapse
see exchange service,any svn services n keep track of system usage. normally 100mb+ will be taken for ui, framework...etc.
but. eventhough u keep track of it,then slaughter it, it will come back to life n running, so i wouldnt recommend slaughtering system usage.
switching between app normally slow for full or stock rom. try find some debloated rom. it will be suitable for u if u wanna more free ram rather than liquidity.
Sent from my GT-I9000 using xda app-developers app
I also observed some sluggishness after some time of usage. Sometimes the phone got totally unresponsive, not catching any push events (from buttons or screen), so that I couldn't even wake it after the screen timeout. I had to wait even few minutes before it was alive again.
Google Chrome was the most ram-eating app as far as I know.
Sometimes the best method is just restart your phone from time to time or even make a wipe - this is normal for all low-end android phones as they get sluggish after some time.
Long story short: I ended up buying a new phone with 2gb of RAM
pawci0 said:
I also observed some sluggishness after some time of usage. Sometimes the phone got totally unresponsive, not catching any push events (from buttons or screen), so that I couldn't even wake it after the screen timeout. I had to wait even few minutes before it was alive again.
Google Chrome was the most ram-eating app as far as I know.
Sometimes the best method is just restart your phone from time to time or even make a wipe - this is normal for all low-end android phones as they get sluggish after some time.
Long story short: I ended up buying a new phone with 2gb of RAM
Click to expand...
Click to collapse
well...good luck on ur new fone
wish i had extra money to buy one......
but, bigger ram doesnt solve anything as far as i know.stock gapps n app from firmware will be da 'pacman' here. unless ur obtain 'god mode' for ur fone.
Sent from my GT-I9000 using xda app-developers app
I have the same issue
I'm using CM10.1 RC5, kernel 3.0.76-gc0a8d45 [email protected] #1
I have same symptoms pawci0 and ltkipras mentioned.
But I don't want to buy a new phone...
The lack of memory is noticeable when I run Waze or maps . It just opens for a couple of minutes and closes by itself or rather hangs the entire device.
What should I do? Go for the CM10.1 stable, try a different ROM (i.e. Slim). Change kernels?
nope, waze doesnt use that much ram, try to fix permission first n clear cache in recovery
n try to use other kernel, mine ok with multitask, rather heavy with online games n hearing mp3 n receiving whatsapp, line n we chat at da same time
n try greenify app to control app thats always running.
Sent from my GT-I9000 using xda premium
Just try a other rom or kernel you would be amazed how lets say a change of kernel can speed things up. The point is everyone uses their phone differently different apps and things so you need to find the rom that suits you mostly.
Sent from my GT-I9000 using xda app-developers app
I found an application named AutoKiller Memory Optimizer by which applying its tweaks It makes my phone more smoothly and saves my battery very well!
There are some reviews below links:
http://forum.xda-developers.com/showthread.php?t=622666
http://andrs.w3pla.net/autokiller
http://andrs.w3pla.net/autokiller/details
http://andrs.w3pla.net/autokiller/kernel
If anyone has installed this application plz give your opinion !
already use that damn thing in 2010, not so bad app, but not so good also, it claims it can kills app but itself running?? n also killing background app n process without consent of owner juz draining ur battery as da process will be revive by system over n over again.
if u wanna some liquidity, try browsing dev sec n find some tweak n if u already choose something, come here n ask us silly question...dont ask there as they already given instruction but some user doesnt even bother to read
Sent from my GT-I9000 using xda premium
i've made the experience that android's build-in mechanismens already are pretty clever and know when to kill an app and when not.
killing an app and open it 5 minutes later again is not the best way to save battery
Things are kept in ram for faster startup and saving cpu power hence increasing battery life.you don't want a complete free ram in android
If you hibernate apps with greenify that spawn unwanted background processes, stay away from widgets and use a bigmem kernel, then you wont need a background app killer to keep your phone smooth
There are many good apps that dont need much ressources...so keep ramhoggers away...cause our i9000 is getting old...^^
Sent from my GT-I9000 using Tapatalk 2
I am wondering if we have a task manager/process explorer app for Nexus 4? Currently I am using AirDroid v2 that includes a task manager, but I am looking for one with more options.
I travel a lot & would like to kill as much unwanted applications running in the background as possible to conserve battery.
There is no more need to use task killer to manage android systems any more. You will be doing more harm than good, in fact there is no good in killing tssks manually.
Sent from my SAMSUNG-SGH-I747 using xda premium
Point noted.
But when I use Airdroid task manager, I see a process when the corresponding app is not running the background.
To mention a few; Cut the rope free, stocks & Hill climb racing.
Few system process like picasa uploader, chrome etc.
As you said andoird may optimize most of them, but I would like some control when running thin on battery.
mohan_168 said:
I am wondering if we have a task manager/process explorer app for Nexus 4? Currently I am using AirDroid v2 that includes a task manager, but I am looking for one with more options.
I travel a lot & would like to kill as much unwanted applications running in the background as possible to conserve battery.
Click to expand...
Click to collapse
use greenify https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en to hibernate any persisting apps/processes (except system). apps relaunch when you open them.
Killing apps and then having to reload them actually uses more battery than them being dormant in the background and already loaded when called upon. The problem is when you have misbehaving apps that stay in the foreground eating up cpu, instead of going dormant into the background. And this does happen. I use an app called Watchdog that alerts me when this happens. It allows you to kill the app when this happens. It also allows you to whitelist and blacklist apps and processes.
Sent from my Nexus 4 using Tapatalk 4 Beta
main phone setting, apps, running.. default task/process manager. in the top right will be an option to show cached process as well.
simms22 said:
main phone setting, apps, running.. default task/process manager. in the top right will be an option to show cached process as well.
Click to expand...
Click to collapse
We all know that is there. The op mentioned wanting more options, mainly monitoring and kill options.
Sent from my Nexus 4 using Tapatalk 4 Beta
mohan_168 said:
I am wondering if we have a task manager/process explorer app for Nexus 4? Currently I am using AirDroid v2 that includes a task manager, but I am looking for one with more options.
I travel a lot & would like to kill as much unwanted applications running in the background as possible to conserve battery.
Click to expand...
Click to collapse
fernandezhjr said:
We all know that is there. The op mentioned wanting more options, mainly monitoring and kill options.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
fast reboot(free), but the paid version i like better https://play.google.com/store/apps/details?id=com.greatbytes.fastreboot&hl=en
rayiskon, I will try greenify & let you know how that helps.
fernandezhjr, I agree restarting app is not an optimal way, but I require to squeeze battery to atleast make phone calls when I am away from charging options.
simms22, fast reboot looks promising. I'll try the free one for now and take it from there.
It's kind of already been said, but I want to clarify as much as possible.
Apps running dormant in the background (using RAM) use no more power than if it weren't running. This is because all of the memory you have is being refreshed all the time, the controller has no idea whether there is actually data there, it still refreshes the entire space of memory.
Apps running "dormant" but using CPU do use more power than if it weren't running. I assume OP is wanting some sort of monitoring app that shows which apps are using CPU, in which case is fine. If OP is wanting to kill all apps that he isn't using at the time to conserve battery, then he would actually be doing the opposite of what he wants, as it requires to CPU to spin back up to restart it later. Again, the difference here is RAM vs CPU, one doesn't use battery (or rather, uses the same amount of battery, no matter how much of it is being utilized), and one can use more or less battery depending on how much it's used.
Johmama said:
It's kind of already been said, but I want to clarify as much as possible.
Apps running dormant in the background (using RAM) use no more power than if it weren't running. This is because all of the memory you have is being refreshed all the time, the controller has no idea whether there is actually data there, it still refreshes the entire space of memory.
Apps running "dormant" but using CPU do use more power than if it weren't running. I assume OP is wanting some sort of monitoring app that shows which apps are using CPU, in which case is fine. If OP is wanting to kill all apps that he isn't using at the time to conserve battery, then he would actually be doing the opposite of what he wants, as it requires to CPU to spin back up to restart it later. Again, the difference here is RAM vs CPU, one doesn't use battery (or rather, uses the same amount of battery, no matter how much of it is being utilized), and one can use more or less battery depending on how much it's used.
Click to expand...
Click to collapse
Thanks for the detailed explanation. I understand killing process, shutting down cached process or apps & later restarting them is only going to fire up the CPU usage which completely defeats the purpose of conserving battery.
Though not a daily ask, at times I am stuck in situation where a phone call or SMS is all I need to keep me going.