Related
I think many of us are using some kind of task killer. BUT, I find task killer sometimes cause more problem than it solves. And sometimes it doesnt really increase free RAM.
What I did was create a simple app to force Android memory manager to free RAM (by unloading tasks based on its own logic). This way you eliminate 3rd party task killer wrongful termination of tasks such as those active ones required by widgets etc.
This app just basically starts and creates a huge heap (forcing Android to free RAM) and then closes.
(You may still see this task linger in memory after you run it, but it will be unloaded the next time you start other app. You will see your free RAM increased a lot)
====Edit
You May not see free RAM increase immediately after running. You will see RAM increase a lot a bit later after you have started other app (which forces BfreeMem to be unloaded from memory)
Tip: Just put a shortcut on desktop. Click it when your RAM is low (<50-60Mb) and it will do its job. Dont run it when your free RAM is above 90Mb.
I'm trying it
Sent from my GT-I9000 using XDA App
This app should be tested by more Samsung Galaxy S owners to see if is working as it should be or not.
Try already.... No diff.... What's the difference?
Sent from my GT-I9000 using XDA App
cosmoboi said:
Try already.... No diff.... What's the difference?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
mib1800 already had got ur all private data, no more diffs.
cosmoboi said:
Try already.... No diff.... What's the difference?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
You have to wait for BfreeMem to be unloaded. (If you are impatient use a Task killer to unload it and you see it frees up lots of RAM.
Basically BFreeMem is a very bloated. When it starts it force Android memory manager to unload other tasks to cater to its RAM requirement. After that if you start other app, Android mem mgr will unload Bfreemem thus freeing huge chunks.
I tweak it to works best if your free RAM is around 50-60Mb. When I run it and when BfreeMem is unloaded later, free RAM goes up to about 100Mb.
btw: this app requires no permission so your data is safe
AutoKiller is a much better alternative.
The concept sounds correct. Not entire sure if it will work in practice.
psychedelic'd said:
AutoKiller is a much better alternative.
Click to expand...
Click to collapse
My purpose is to have something that does not circumvent Android memory manager which keeps track of tasks and their stats. It knows better what tasks are best to kill based on their usage/last access/active state/priority. Furthermore, if Android memory manager kill a task due to low memory, it will save the state for that task so that the next time that task is used the saved state is restored.
3rd party task killers sometimes mess this up by killing tasks which are actively use (resulting in those tasks being restarted just after being killed leading to wasted power and more lag) or killing dependent tasks such as those used by widgets without saved state causing widgets to malfunction.
snapper.fishes said:
The concept sounds correct. Not entire sure if it will work in practice.
Click to expand...
Click to collapse
I am using it. It does free up RAM. Is it useful? Depends. If you have lots of active apps (widgets/service etc), those freed RAM is filled up soon as Android restore back those "killed" tasks. Not much gain here. On the other hand, if you have lots of zombie apps lingering in memory then yes. The extra RAM does give a boost to the next app you open
AutoKiller is less of a task killer and more of a memory manager. Sort of like what your app is trying to do, but much better. More information: http://andrs.w3pla.net/autokiller/details
Your concept is good, but having an app that continually increases ram usage will waste battery. Then having to kill that app manually in order to free up ram is tedious. Just my 2 cents.
The new task manager in Touchwiz has a function to manually clear ram any way, which works great.
psychedelic'd said:
AutoKiller is less of a task killer and more of a memory manager. Sort of like what your app is trying to do, but much better. More information: http://andrs.w3pla.net/autokiller/details
Your concept is good, but having an app that continually increases ram usage will waste battery. Then having to kill that app manually in order to free up ram is tedious. Just my 2 cents.
The new task manager in Touchwiz has a function to manually clear ram any way, which works great.
Click to expand...
Click to collapse
OK. AutoKiller is changing Linux configuration. Unfortunately, it needs root.
I have used the TouchWiz TaskMgr clean Ram at safe level - it still messed up my widgets (Beautiful widgets, weather & toggle)
Bfreemem app does not continually run or increase RAM usage. You just run it when the free RAM is low (or close to threshold). At this low RAM level it just knocks other tasks out of RAM. btw: You should NOT run it when you have huge amount of free RAM. You should run it when RAM is low like <50Mb.
You dont really have to kill Bfreemem task manually since it will be quickly unloaded by the Android memory manager when RAM is required since its state is finished.
JUst put a shortcut on the desktop and click it when you feel RAM level is low and it will do its job.
Can it be used with autokiller?
It could be also automated to check if memory is low, and automatically kill applications. Battery drain would be present in that case tho..
Never has the default task killer from samsung messed up my widgets including Beautiful weather, I tried using task killer and never saw the benefits of it since andriod automatically keeps 40MB of free ram...
EarlZ said:
Never has the default task killer from samsung messed up my widgets including Beautiful weather, I tried using task killer and never saw the benefits of it since andriod automatically keeps 40MB of free ram...
Click to expand...
Click to collapse
When I try the option Level 1 - Clear Memory (in Samsung task killer), my beautiful widget clock stop working.
Soniboy84 said:
Can it be used with autokiller?
It could be also automated to check if memory is low, and automatically kill applications. Battery drain would be present in that case tho..
Click to expand...
Click to collapse
Personally, I dont use task killer. Not sure whether Autokiller kills tasks physically or just adjust some running config. Just have a feeling task killers (those that kill tasks physically) cause RAM leak. For example when my phone reboot, I can see at least 12 tasks (in Advanced Task Killer) and free RAM is about 95Mb. If I physically kill those tasks, my RAM may temporarily goes up to 130Mb but sometime later free RAM drops to 50-60Mb and there were no more tasks to kill.
When I use Bfreemem, my free RAM fluctuates betw. 60-100 Mb and I can still see all/most of those tasks that were there just after boot-up.
If you have one of those scheduler/timer app, you can just use those to schedule Bfreemem to run regularly. (I can build another timer app to schedule)
Been using Quick System Info PRO for the past few days, and am truly impressed! Multi-functional as a task manager to close / ignore running apps...cache cleaner keeps system from bogging down. Process tracking / cpu usage tracking. Tons of system specs available to view, etc. Uninstall apps directly from this as well. Find out exactly what apps start on boot up, and trim as you see fit.
I know memory is at a premium for us Archos IT users...I encourage you to check this app out. It's a little more complicated than your standard task killer, but truly helps trim things down. Best of all, it's free! Option to donate to disable ads, I donated just cuz the dev blew me away with this app!!
Enjoy, and please offer up your own opinions!
How do u change what programs run on startup? I downloaded it and its good but I don't see that feature.
Task killers (apparently) shouldn't be used on Android (generally... there are always exceptions)
If an Android app is created properly, it shouldn't be eating away at the RAM, and Android will free up what it needs.
If it killed everything, then the multitasking feature will be as useless as Apple's
I won't explain further, I'll just link Lifehacker instead:
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
Please note: Although I don't use task killers my self, I don't disagree with them. I'm just putting this out there so you can make your own minds up
thefunkaygibbon said:
Task killers (apparently) shouldn't be used on Android (generally... there are always exceptions)
If an Android app is created properly, it shouldn't be eating away at the RAM, and Android will free up what it needs.
If it killed everything, then the multitasking feature will be as useless as Apple's
I won't explain further, I'll just link Lifehacker instead:
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
Please note: Although I don't use task killers my self, I don't disagree with them. I'm just putting this out there so you can make your own minds up
Click to expand...
Click to collapse
While I certainly agree with this...do you own an Archos? Task Killer is almost necessary for the Archos 70it. Until they increase memory allocations, the need to minimize what's running at startup or any given time is absolutely needed.
Bandage said:
While I certainly agree with this...do you own an Archos? Task Killer is almost necessary for the Archos 70it. Until they increase memory allocations, the need to minimize what's running at startup or any given time is absolutely needed.
Click to expand...
Click to collapse
I agree but I still can't figure out how to configure the startup. Can you let me know how?
Bandage said:
While I certainly agree with this...do you own an Archos? Task Killer is almost necessary for the Archos 70it. Until they increase memory allocations, the need to minimize what's running at startup or any given time is absolutely needed.
Click to expand...
Click to collapse
I disagree. They are not needed. I don't use one on my 101.
blazingwolf said:
I disagree. They are not needed. I don't use one on my 101.
Click to expand...
Click to collapse
So what are you using your tablet for? Reading ebooks? If you have more than 1 user process running at a time, in addition to system processes it gets bogged down. Android is great at multitasking...256k RAM is not. I have my 70 trimmed down to skinny, having removed some bloatware apps. Normal is around 55-60% of RAM usage during standby.
If I decide to break out a game, like Dungeon Hunter or another system hog...I run into occassional FC's if I haven't freed up some RAM. A TASK MANAGER helps me select the things I want to shut down to free that RAM for an app / process that I choose to run. Stop confusing TASK KILLER with TASK MANAGER. (Was a typo in my response earlier) Yes the app allows me to kill tasks, the difference is...I'm killing what I CHOOSE to kill.
PS - I haven't done much to alter start up apps thru this Manager, just have used it to trim fat and gain control of my RAM usage.
Bandage said:
So what are you using your tablet for? Reading ebooks? If you have more than 1 user process running at a time, in addition to system processes it gets bogged down. Android is great at multitasking...256k RAM is not. I have my 70 trimmed down to skinny, having removed some bloatware apps. Normal is around 55-60% of RAM usage during standby.
If I decide to break out a game, like Dungeon Hunter or another system hog...I run into occassional FC's if I haven't freed up some RAM. A TASK MANAGER helps me select the things I want to shut down to free that RAM for an app / process that I choose to run. Stop confusing TASK KILLER with TASK MANAGER. (Was a typo in my response earlier) Yes the app allows me to kill tasks, the difference is...I'm killing what I CHOOSE to kill.
PS - I haven't done much to alter start up apps thru this Manager, just have used it to trim fat and gain control of my RAM usage.
Click to expand...
Click to collapse
Play games, read books, video, music, etc. Just about anything you can do with it.
I also used to have a task killer and decided to install Watchdog which works in a different way. Works a lot better that all the rest of the task killers I have used and did not have any issues. Apps run smooth even if I have more than one running.
thanks
i use this apk
Bandage said:
Been using Quick System Info PRO for the past few days, and am truly impressed! Multi-functional as a task manager to close / ignore running apps...cache cleaner keeps system from bogging down. Process tracking / cpu usage tracking. Tons of system specs available to view, etc. Uninstall apps directly from this as well. Find out exactly what apps start on boot up, and trim as you see fit.
I know memory is at a premium for us Archos IT users...I encourage you to check this app out. It's a little more complicated than your standard task killer, but truly helps trim things down. Best of all, it's free! Option to donate to disable ads, I donated just cuz the dev blew me away with this app!!
Enjoy, and please offer up your own opinions!
Click to expand...
Click to collapse
There is a YouTube video showing why not to use a taskiller, and how much lag there is when you kill all the apps, let them cache in the OS and its faster, don't be afraid of having low memory, this was done on the 70 tab 8 gig, sorry for no link, its one of the top ones.
Sent from my PC36100 using XDA App
I am using advanced task killer to manage process. But some process can not be killed. Are these processes not killed or just respawned quickly. How to really kill them. Thanks.
Sent from my Desire HD using XDA App
yeah i wonder how to remove/uninstall apps such as stocks which i do not even touch at all.
The best method is to uninstall your task killer. They are junk and will only slow your phone down. Every time you kill those process, they have to restart which uses more cpu and battery than just leaving them in memory in the first place.
Please google about android task managers and you will find some good explanations as to why you shouldn't use them.
Sent from my super slick Android device.
iroquois said:
yeah i wonder how to remove/uninstall apps such as stocks which i do not even touch at all.
Click to expand...
Click to collapse
You need root and some form of s-off. Then you can either delete with root explorer, titanium backup, out adb.
Sent from my super slick Android device.
Like dr.m0x said, those task killers and other optimizer are the worst thing out there on the market.
Android handles these things just fine. If your RAM gets low it will kill tasks on its own. And if your RAM isn't low - then why kill tasks? Free RAM doesn't help at all.
Also background apps almost never use battery/CPU power. If you don't believe it check the battery usage history. And most background tasks have a CPU usage of a couple of seconds.
About removing stock apps, a nice and clean way is to use ROM Cleaner (download in the dev section). It removes apps from the ROM before you flash it.
Thanks, I think I got what I want
Sent from my Desire HD using XDA App
The title is basically the question, im fed up of alot of programs auto opening on my android phone, it takes battery and is slightly annoying receiving notifications off apps i dont really care about such as the NFL game tells me about small things in the NFL, im in the UK, i dont care.
If you argue that it doesnt take alot of battery currently have 117mb free ram, (2 secs later) killed all my selected apps now have 201mb free so im using 80mb of ram on apps im not using. Ive made 2 or 3 phone calls today no more than 30 mins long altogether and ive lost 55% of my battery since about midday, which is when i unplugged the phone.
And I think all these apps are the problem so how can I stop them from auto opening, please help
Search the market for startup cleaner
Sent from my A101IT using xda premium
yusuo said:
If you argue that it doesnt take alot of battery currently have 117mb free ram
Click to expand...
Click to collapse
More free RAM doesn't really equate to longer battery life or lower power consumption.
Better search for auto starts, this asp shows you the conditions an asp can turn back on and you can bin it off, Facebook for example had like 8 conditions, from full to medium battery life, on charge and change in network....... Use it
Sent from my HTC Desire using xda premium
rootSU said:
More free RAM doesn't really equate to longer battery life or lower power consumption.
Click to expand...
Click to collapse
There's still no reason for most of this apps to use RAM. Apps like facebook and skype shouldn't be actice without user permission. Without login they are complete useless.
I'll try Startup Cleaner, thx.
It's how android works and what RAM is for. There is always a reason.
Sure if someone doesn't use Facebook, it should be uninstallable, but its not and its not causing any harm
Sent from my HTC Desire using Tapatalk
The problem isn't that apps start when I turn on the phone its that even after i use task manager to close they keep reopening and use over 100mb of ram, earlier I checked and only had 78mb ram available.
This must have an effect on battery to some degree i want to kinda ban certain apps from running in the background unless i specifically tell them to
RAM doesn't use more power, the more its used, no.
You don't need a task killer. You do not need to obsess about RAM. Forget about RAM and enjoy your phone
Sent from my HTC Desire using Tapatalk
rootSU said:
RAM doesn't use more power, the more its used, no.
You don't need a task killer. You do not need to obsess about RAM. Forget about RAM and enjoy your phone
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Thanks for you reply but its not really an answer its more of a contradiction, what I was asking is how to I stop apps from auto starting and eating up RAM, regardless of how long the phones been on
...and I'm telling you its a pointless, unecessary waste of time. Also it is not possible. Autostarts as already mentioned is the closest you'll get
Sent from my HTC Desire using Tapatalk
I also turned off the autorun permissions of a lot of apps, for 2 reasons: 1) a device that is smooth sooner after booting, using less cpu cycles/power. 2) preventing Sense from reloading due to RAM shortage and have smooth multitasking.
1) Android loads a bunch of apps to the RAM that have the autorun permission, until it thinks it is "enough" and useful to you. No matter how many apps you have installed, the amount of free RAM is always about the same, just the number of "unwanted" apps in the RAM differs. Removing the autorun on boot permissions prevents the loading of unnecessary apps that will immediately be removed from the RAM the moment you start the browser/a game, saving cpu cycles=power. So for me there is no point in loading them in the first place, because I am never going to use them (right away). I want the apps that don't to any syncing loaded on demand.
2) I hate slow multitasking and I hate it even more when Sense reloads because it got kicked out of the RAM after each time I press HOME.
I use 3G Watchdog (~12MB RAM), Unlock with Wifi (~8MB), Whatsapp (~15MB), Handcent SMS (~18MB), Droidstats (~13MB), Extended Controls (~12MB), Battery Monitor Widget Pro (~13MB). Okay, I maybe could delete some of them, but these app are "OK" to me, because I use them actively or just need a background service to operate normally.
With Gemini I disabled apps like Facebook, a screenshot tool (just load when I want to make a screenshot..), various public transport planning tools, etc from autostarting.
No joy moment: after using the Facebook app (market version), it may take up 50+ MB and it will not be closed when I start another RAM intensive app, because it is a high priority service. Result: Sense gets kicked out of the RAM. Or, when the situation is somewhat less critical: multitasking is as good as unusable: switching between apps makes them load over and over again, because app2 kicks app1 out of the RAM and vice versa, causing unnecessary lag. Therefore: when I am done with facebook, I close it, then STAY the hell closed It may only autostart when it receives a push message. In that case it is nice to have FB already in RAM when I tap the notification.
Why do even some games have background services, or the Engadget app, or .. , or... all eating precious RAM. And yes, I know, once IN the RAM they eat no battery, but they DO eat battery when the app loads itself back in the RAM when it thinks it needs to, after it got kicked the moment I decided to so something else.
Hmm, spent way too much time to try to explain my frustration Oh and by the way, I have a Legend, but the basics are the same of course.
Dwnload an app called internet commander from the market. It shuts off the internet when your screen turns off but still let's you get calls and texts. I've got my phone , rooted of course, clocked to 710 and my battery will last for days.
Sent from my Eris using xda premium
I just re read your post, that won't help with apps but it will help save battery. And when you turn your screen on the internet kicks right on instantly. Good luck
Sent from my Eris using xda premium
yusuo said:
The problem isn't that apps start when I turn on the phone its that even after i use task manager to close they keep reopening and use over 100mb of ram, earlier I checked and only had 78mb ram available.
This must have an effect on battery to some degree i want to kinda ban certain apps from running in the background unless i specifically tell them to
Click to expand...
Click to collapse
The guys here have already suggested you use a certain program from the Market. Have you tried it?
Regarding the whole RAM consumption issue, Android has its own built-in memory management system that ensures that there's always enough RAM for an app whenever it needs it, even if the memory manager shows like 40 MB free. Basically it "ejects" all background, unused apps, from memory making room for the foreground app which needs it most. If for some reason you need to fiddle with that, you can try using the V6 Supercharger script. I find it suitable for my needs but YMMV. It's completely reversible, so if you don't like it you can uninstall it just like that.
P.S. - I agree with rootSU, the ammount of free RAM has nothing to do with battery consumption. If you suspect that an app is draining your battery, check Android's battery statistics to find the culprit.
TVTV said:
Regarding the whole RAM consumption issue, Android has its own built-in memory management system that ensures that there's always enough RAM for an app whenever it needs it, even if the memory manager shows like 40 MB free. Basically it "ejects" all background, unused apps, from memory making room for the foreground app which needs it most. If for some reason you need to fiddle with that, you can try using the V6 Supercharger script. I find it suitable for my needs but YMMV. It's completely reversible, so if you don't like it you can uninstall it just like that.
P.S. - I agree with rootSU, the ammount of free RAM has nothing to do with battery consumption. If you suspect that an app is draining your battery, check Android's battery statistics to find the culprit.
Click to expand...
Click to collapse
I respectfuly disagree. Android built in ram management is just silly. If I open xda app for example (it could actually be any app for that matter), reply to a few posts, read a few more and close it, why does it need to stay in ram? It reloads anyway when I run it again after I've closed it (using the back button or the actual exit command in the app itself). Why does the camera app need to stay in the background after I just shot a few photos and closed it? Because I may or may not use it again in some time? It's rediculous. And the whole theory that ram management doesn't require any power/cpu usage, how do you guys think all those apps get killed? Android will power?! No, kernel scans all running apps and kills the ones based on built in heuristics so it also reads them first. So that doesn't require any power/battery? Awesome if it's true! Although I wouldn't bet on that. And all this fuss just because you may or may not launch the same app sometime during the next day/week/month/year or it'll eventually get killed? Now that's just plain stupid. I get apps that need services like widgets, push notifications etc. but random apps like root explorer, xda app, titanium, youtube etc. which are opened specificly by the user shouldn't be in ram just for the sake of it after they're closed. I closed it, meaning I don't need it anymore. And I don't need the kernel to scan all apps and running services every time I launch an app so it could provide the free ram that app needs. Consumes cpu time, battery, i/o ... every piece of hardware actually just to free some ram that shouldn't be occupied in the first place. Every app that I ever opened on my phone got loaded almost instantly and that's just after phone had been booted. So after that it should stay in ram so I could open it in a blink of an eye instead of instantly? That's just funny.
Anyway, I'm just thinking out loud so don't flame me immediately. There probably are apsects of it that I didn't mention here or am not aware of. And I'm not saying that I'm right and you guys are wrong, I'm just saying what I know and think about this subject.
-. typewrited .-
PlayPetepp, while it might be true that the OS allocates (thus use) some resources to memory maintenance, the impact on battery life is negligible. In the Android OS, apps in memory are ordered according to priority and state, so the OS always knows which apps to kill first if it needs to make room in RAM, without much of a hassle. The only bad consequence of this system seems to be the fact that once the memory fills up, the launcher may lag or even be evacuated from memory. But, as i've mentioned in my previous post, there are ways to prevent that, either via scripts or, if you know what you're doing, via editing system files.
So the OS doesn't need to scan anything as it keeps everything in memory again? Seems like an endless loop. Open, sort, kill if needed, reopen, sort again, kill ... to what end, constant unneccessary multitasking that user is unaware of? I really don't see any benefit of that system and am only seeing the downsides. I mean, who needs every app they ever run remain in ram even if they close them after using? And then opening another app and "waiting" for whatever needs to be closed to get it running. Sure you can mess with the scripts (init.d, init.rc, etc.) but the underlined conditions stay the same. I hope I'm making sense here. Or am I fighting against windmills.
I just figured out that I strayed from the topic of this thread so won't be continuing this discussion if it's considered offtopic.
-. typewrited .-
Stop looking for excuses for poor multitasking in Sense 3+ roms
erklat said:
Stop looking for excuses for poor multitasking in Sense 3+ roms
Click to expand...
Click to collapse
Hello again nice to see you here
Here's an interesting article on what I was talking about. Sense 3.5 doesn't need that many mbs of ram to work smoothly. After booting and setting everything up I have 150+ mb free. That should be enough for decent multitasking but all those apps not getting killed when you close them are eating too much. Can anyone explain in detail what hidden app, perceptible app, backup app and heavy_weight app means? I've been googling this for a week and can't find any decent explanation.
@PlayPetepp - I think i have already said (in my previous post) that the OS does indeed use some resources for managing the memory, but they are negligible in terms of their impact on battery life. IMHO, the only thing a 3'rd party memory manager (task killer) WILL do is improve lanuncher responsiveness (lag) as the lag does increase when free RAM drops under a certain limit. Thus used wisely, a task killer can improve responsiveness, but battery life... very little, in rare cases (it does the opposite, most of the time).
Regarding the so called "memory slots", here's an excerpt from this article:
FOREGROUND_APP: This is the application currently on the screen, and running
VISIBLE_APP: This is an application that is open, and running in the background because it's still doing something
SECONDARY_SERVER: This is a process (a service that an application needs) that is alive and ready in case it's needed to do something
HIDDEN_APP: This again is a process, that sits idle (but still alive) in case it's needed by an app that's alive and running
CONTENT_PROVIDER: This is apps that provide data (content) to the system. HTC Facebook Sync? That's a CONTENT_PROVIDER. So are things like the Android Market, or Fring. If they are alive, they can refresh and provide the content they are supposed to at the set interval. If you kill them, they can't of course.
EMPTY_APP: I call these "ghosts." They are apps that you have opened, but are done with them. Android uses a unique style of handling memory management. When an activity is ended, instead of killing it off Android keeps the application in memory so that opening them again is a faster process. Theses "ghost" apps use no battery or CPU time, they just fill RAM that would be otherwise empty. When this memory is needed by a different application or process, the RAM is flushed and made available for the new app. To satisfy the geekier people (like myself) Android does this by keeping a list of recently used apps, with the oldest apps in the list given the lowest priority -- they are killed first if RAM is needed elsewhere. This is a perfect way to handle 'ghost' processes, so there's no need to touch this part
Click to expand...
Click to collapse
So i saw many posts on which people have asked as to which task killer should be used !
and then i stumble upon this site which provided me the details,
*I HAVE NOT WRITTEN THIS*
sources-by Chris Hoffman
http://www.howtogeek.com/127388/htg-explains-why-you-shouldnt-use-a-task-killer-on-android/
Android Doesn’t Manage Processes Like Windows
Most Android users are familiar with Windows. On Windows, many programs running at one time – whether they’re windows on your desktop or applications in your system tray – can decrease your computer’s performance. Closing applications when you’re not using them can help speed up your Windows computer.
However, Android isn’t Windows and doesn’t manage processes like Windows does. Unlike on Windows, where there’s an obvious way to close applications, there’s no obvious way to “close” an Android application. This is by design and isn’t a problem. When you leave an Android app, going back to your home screen or switching to another app, the app stays “running” in the background. In most cases, the app will be paused in the background, taking up no CPU or network resources. Some apps will continue using CPU and network resources in the background, of course – for example, music players, file-downloading programs, or apps that sync in the background.
When you go back to an app you were recently using, Android “unpauses” that app and you resume where you left off. This is fast because the app is still stored in your RAM and ready to be used again.
Why Task Killers Are Bad
Proponents of task killers notice that Android is using a lot of RAM – in fact, Android stores a lot of apps in its memory, filling up the RAM! However, that isn’t a bad thing. Apps stored in your RAM can be quickly switched to without Android having to load them from its slower storage.
In summary, you shouldn’t use a task killer – if you have a misbehaving app wasting resources in the background, you should identify it and uninstall it. But don’t just remove apps from your phone or tablet’s RAM – that doesn’t help speed anything up.
Empty RAM is useless. Full RAM is RAM that is being put to good use for caching apps. If Android needs more memory, it will force-quit an app that you haven’t used in a while – this all happens automatically, without installing any task killers.
Task killers think they know better than Android. They run in the background, automatically quitting apps and removing them from Android’s memory. They may also allow you to force-quit apps on your own, but you shouldn’t have to do this.
Task killers aren’t just useless – they can reduce performance. If a task killer removes an app from your RAM and you open that app again, the app will be slower to load as Android is forced to load it from your device’s storage. This will also use more battery power than if you just left the app in your RAM in the first place. Some apps will automatically restart after the task killer quits them, using more CPU and battery resources.
Whether RAM is empty or full, it takes the same amount of battery power – decreasing the amount of apps stored in RAM won’t improve your battery power or offer more CPU cycles.
hope u understood!
words of wisdom by fellow-mates
go into settings - apps and see how many running apps you have. now go to cached apps and see there, how many apps there are. you see? nearly 50% of those apps discovered by you in the processes are apps that you didn't opened ever but they are still opened and running. why? because that's how linux manages its resources. instead of having free ram for no use (what's the point of having 14gb of ram when you only use 1gb), linux fills all the ram blocks with useful apps or apps that you are running frequently so that when you call that app, it will bring it on the screen almost instantly. this my friend, is called multitasking.
and no, you are wrong. if you use a task killer killing the apps every 10 minutes, the cycles the whole system does - opening again apps and caching them, task killer closing them - results in much more functions done by CPU => more battery spent. even if you say that the battery life its the same, you are wrong. when using a task killer IT MIGHT drain your battery with 0.1% per hour. it's not that much, but IT EXIST.
oh and yeah, one thing: android has its own task killer. that's why you don't need one app to kill your other apps. because android its doing it by itself. if you don't believe me, strip down one kernel, open the init.rc file and find the values for task killer.
I understand this response, but I don't believe it. Task killers has always helped me in every matter. Even on a computer it helps greatly.
Conclusion: I noticed the same battery life using a Task Killer, than not using a task killer.
Sent from my HTC One V using Tapatalk 2
Curiousn00b said:
I understand this response, but I don't believe it. Task killers has always helped me in every matter. Even on a computer it helps greatly.
Conclusion: I noticed the same battery life using a Task Killer, than not using a task killer.
Sent from my HTC One V using Tapatalk 2
Click to expand...
Click to collapse
you don't have to believe it. those are real facts. go into settings - apps and see how many running apps you have. now go to cached apps and see there, how many apps there are. you see? nearly 50% of those apps discovered by you in the processes are apps that you didn't opened ever but they are still opened and running. why? because that's how linux manages its resources. instead of having free ram for no use (what's the point of having 14gb of ram when you only use 1gb), linux fills all the ram blocks with useful apps or apps that you are running frequently so that when you call that app, it will bring it on the screen almost instantly. this my friend, is called multitasking.
and no, you are wrong. if you use a task killer killing the apps every 10 minutes, the cycles the whole system does - opening again apps and caching them, task killer closing them - results in much more functions done by CPU => more battery spent. even if you say that the battery life its the same, you are wrong. when using a task killer IT MIGHT drain your battery with 0.1% per hour. it's not that much, but IT EXIST.
oh and yeah, one thing: android has its own task killer. that's why you don't need one app to kill your other apps. because android its doing it by itself. if you don't believe me, strip down one kernel, open the init.rc file and find the values for task killer.
salve.
1ceb0x said:
you don't have to believe it. those are real facts. go into settings - apps and see how many running apps you have. now go to cached apps and see there, how many apps there are. you see? nearly 50% of those apps discovered by you in the processes are apps that you didn't opened ever but they are still opened and running. why? because that's how linux manages its resources. instead of having free ram for no use (what's the point of having 14gb of ram when you only use 1gb), linux fills all the ram blocks with useful apps or apps that you are running frequently so that when you call that app, it will bring it on the screen almost instantly. this my friend, is called multitasking.
and no, you are wrong. if you use a task killer killing the apps every 10 minutes, the cycles the whole system does - opening again apps and caching them, task killer closing them - results in much more functions done by CPU => more battery spent. even if you say that the battery life its the same, you are wrong. when using a task killer IT MIGHT drain your battery with 0.1% per hour. it's not that much, but IT EXIST.
oh and yeah, one thing: android has its own task killer. that's why you don't need one app to kill your other apps. because android its doing it by itself. if you don't believe me, strip down one kernel, open the init.rc file and find the values for task killer.
salve.
Click to expand...
Click to collapse
I hope u don't mind if I take some of ur message and put it in the op
Sent from my One V using xda app-developers app
That's great.. I liked the article. I qm giving you a thanks for it
Sent from my One V using xda app-developers app
cybervibin said:
I hope u don't mind if I take some of ur message and put it in the op
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
sure. no problem mate
soham_sss said:
That's great.. I liked the article. I qm giving you a thanks for it
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
Thank you
1ceb0x said:
sure. no problem mate
Click to expand...
Click to collapse
Sent from my One V using xda app-developers app
task killers were great before 1.6 but useless after that
Lloir said:
task killers were great before 1.6 but useless after that
Click to expand...
Click to collapse
+1 android has devloped a long way since!
cybervibin said:
Thank you
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
you're welcome!
I'm using task menager when is needed, and also I'm using custom system memory tweaks, it makes my phone running faster and smoother some apps knows to stuck and they keep the phone from entering deep sleep, and that drains the battery, so if you know what are you doing use task menager and customize when what apps the system should kill
Sent from my HTC One V
I have a task killer installed, but only use it manually, ie. if there's a stubborn app that's crashed/frozen/etc and just won't close and is eating the battery
donJim said:
I'm using task menager when is needed, and also I'm using custom system memory tweaks, it makes my phone running faster and smoother some apps knows to stuck and they keep the phone from entering deep sleep, and that drains the battery, so if you know what are you doing use task menager and customize when what apps the system should kill
Sent from my HTC One V
Click to expand...
Click to collapse
Use auto run manager the answer to most of ur problems
qzfive said:
I have a task killer installed, but only use it manually, ie. if there's a stubborn app that's crashed/frozen/etc and just won't close and is eating the battery
Click to expand...
Click to collapse
Sent from my One V using xda app-developers app
yayyy so task killer only kills my battery
you got that right!
Good to know. Thanks