I am just curious, how much "Free Memory" (RAM) do you have when you just turn on the phone and turn on Advanced Task Manager/System Monitor etc?
And how much "free memory" do you have when you have used your phone for a while even though you have killed all the tasks you do not want?
In my case, mine is:
Free Memory:
Just turn on: up to 80M (32 processes)
After a while of using different apps and killing them: can be down to early 30M or late 20M (with the same number of processes)
What is yours? Let's share it and see how your memory is doing. I want to see if mine is normal.
Been of for about a day and a half
Free MEM: 93MB
Processes: 22
Micksta said:
Been of for about a day and a half
Free MEM: 93MB
Processes: 22
Click to expand...
Click to collapse
****, you have that much, what is wrong with mine?
Point is, there are many apps that I am not sure if i can kill them. e.g. HTC sense, customization setting, customization setup, socialnetwork.provider, HTC media uploader, DCS CHT component, weather provider, provider.settings, DCS weather component, DSC service, service.stock etc.
These I always leave them on. I wonder which apps are taking up the most mem.
schizophrenia said:
****, you have that much, what is wrong with mine?
Click to expand...
Click to collapse
Nothing, i've rooted time and removed apps like Stock and QuickOffice etc..
And i've also removed Peep for twitroid as peep was a resource hog.
Can anyone suggesr me which is the best task killer available in the market..m using task killer from rhythm software..
Sent from my X10i using XDA App
gupta.anurag08 said:
Can anyone suggesr me which is the best task killer available in the market..m using task killer from rhythm software..
Sent from my X10i using XDA App
Click to expand...
Click to collapse
I'm running on the Advanced Task Killer, I do not have any issues with them. What's your problem?
I tried 2 3 task killers and all were showing different 'available memory'
Sent from my X10i using XDA App
Yeah, ATK is the best task killer app I've been using
gupta.anurag08 said:
I tried 2 3 task killers and all were showing different 'available memory'
Sent from my X10i using XDA App
Click to expand...
Click to collapse
It is because different task killer have different security policy, which allow them to show the system apps or not. So, in the lower security policy, you can see more running apps and gain more memory after kill them
i do have a question. why are you using a task killer?
I'm not having a dig at people that use them, but more trying to educate people that they are not required
"free memory" is not indicative of a healthy system in linux based machines.
please remember the way in which linux based OS's (which Android is) handles memory. Basically, if you have a heap of free memory it is simply wasted, the OS is not running any more efficiently. It is actually slower.
Here is a quick overview. Written for the desktop computer perspective, but translates over to a mobile phone OS quite well.
"Traditional Unix tools like 'top' often report a surprisingly small amount of free memory after a system has been running for a while. For instance, after about 3 hours of uptime, the machine I'm writing this on reports under 60 MB of free memory, even though I have 512 MB of RAM on the system. Where does it all go?
The biggest place it's being used is in the disk cache, which is currently over 290 MB. This is reported by top as "cached". Cached memory is essentially free, in that it can be replaced quickly if a running (or newly starting) program needs the memory.
The reason Linux uses so much memory for disk cache is because the RAM is wasted if it isn't used. Keeping the cache means that if something needs the same data again, there's a good chance it will still be in the cache in memory. Fetching the information from there is around 1,000 times quicker than getting it from the hard disk. If it's not found in the cache, the hard disk needs to be read anyway, but in that case nothing has been lost in time."
Read more here - http://www.linuxhowtos.org/System/Linux Memory Management.htm
So u mean to say that we shud not use task killers?
Wat if i exit a game in btw then wat happens..will it get automatically killed??
Sent from my X10i using XDA App
gupta.anurag08 said:
So u mean to say that we shud not use task killers?
Wat if i exit a game in btw then wat happens..will it get automatically killed??
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Nope, that is the reason why i have to use task killer
For me, it help me save much of battery
Since I stopped using a task killer my battery is better.
Don't use a task killer for a week and watch the difference.
gupta.anurag08 said:
So u mean to say that we shud not use task killers?
Wat if i exit a game in btw then wat happens..will it get automatically killed??
Sent from my X10i using XDA App
Click to expand...
Click to collapse
yes and yes!
if your phone requires the resources, it will kill tasks that are no longer required. its all automatic. let it do it itself and you will have a much happier phone
AND better battery life, because the android OS is not continually restarting processes that your task killer deems unnecessary. I would trust the actual OS over a 3rd party app. It is designed that way for a reason (see my previous post).
mrtim123 said:
i do have a question. why are you using a task killer?
I'm not having a dig at people that use them, but more trying to educate people that they are not required
"free memory" is not indicative of a healthy system in linux based machines.
please remember the way in which linux based OS's (which Android is) handles memory. Basically, if you have a heap of free memory it is simply wasted, the OS is not running any more efficiently. It is actually slower.
Here is a quick overview. Written for the desktop computer perspective, but translates over to a mobile phone OS quite well.
"Traditional Unix tools like 'top' often report a surprisingly small amount of free memory after a system has been running for a while. For instance, after about 3 hours of uptime, the machine I'm writing this on reports under 60 MB of free memory, even though I have 512 MB of RAM on the system. Where does it all go?
The biggest place it's being used is in the disk cache, which is currently over 290 MB. This is reported by top as "cached". Cached memory is essentially free, in that it can be replaced quickly if a running (or newly starting) program needs the memory.
The reason Linux uses so much memory for disk cache is because the RAM is wasted if it isn't used. Keeping the cache means that if something needs the same data again, there's a good chance it will still be in the cache in memory. Fetching the information from there is around 1,000 times quicker than getting it from the hard disk. If it's not found in the cache, the hard disk needs to be read anyway, but in that case nothing has been lost in time."
Read more here - http://www.linuxhowtos.org/System/Linux Memory Management.htm
Click to expand...
Click to collapse
The idea is absolutely right if memory is being used for apps you are likely to open frequently. ATK allows you to unselect the apps you want to keep running. That way you can unselect the ones you use the most and then use the widget to kill everything else.
I notice when I press the home screen many apps don't kill them selfs and after a while I have loads of apps running and the system starts to lag, specially when I try to run something else.
There are advantages in both approaches and I find a mixed combination (available with ATK) makes it best, although the user need to use some common sense to do it right. Killing everything means the system will be more responsive but regularly used apps will take longer to start up. Not killing means the apps you use a lot "startup" faster when you use them repeatedly (as in fact they never stop running) but after a bit the system will lag when using other apps and may need to use pagefile/swap to atone for the lack of free RAM. That causes page faults which make the system even slower.
The iphone developers aren't complete idiots for killing every app. They have a priority for system responsiveness and they did achieve it at the cost of background running apps. I like the possibility to choose what I want to keep running and kill the apps I'm not likely to use again and it's one of the reasons I picked android.
A little Offtopic to both ifanboys and ihaters:
I never owned any apple product as I think of them as over priced. That said I think the iphone has great merit and I doubt very much we would have Android if the iphone didn't pave the way. Besides I jailbreak my brother's 3G and made it multitask enabled. Now it runs apps in background and there is little diference between it and my android. Except for the extra 200€ it cost, the lower hardware specs and expensive service provider contract my brother pays for a mandatory 24 months, while my X10 cost ~65% initially and came free of any contract.
well said, PCO
pco.vaz said:
I notice when I press the home screen many apps don't kill them selfs and after a while I have loads of apps running and the system starts to lag, specially when I try to run something else.
Click to expand...
Click to collapse
Thats what I and others have found, which is why some people choose to use one, myself included. Someone posted a link to an article last week with similar information posted here about the OS handling itself, but the comments section of the article were full of comments similar to what pco and myself have said, so it's all down to personal preference whether or not you choose to use one.
I did use a task killer for a while, then stopped. Personally my phone is better without. I have nothing except weather that updates automatically, I do it manually when I need it.
It is one of those things, just like on a laptop, everyone has different configurations and usage patterns that results will vary.
Sent from my X10i using XDA App
Don't apps exit when you keep hitting the back button? And for games doesn't hitting exit shut down the app?
I thought its a feature that apps don't close when you hit the home button?
gavriel18 said:
Don't apps exit when you keep hitting the back button? And for games doesn't hitting exit shut down the app?
I thought its a feature that apps don't close when you hit the home button?
Click to expand...
Click to collapse
The browser for instance doesn't. Same with many other. I think it's up to each individual developer to program that behavior for his app.
I got Visual task switcher and I notice lots of apps just stay running forever.
Task killer caused probs for me. A daily switch off doesnt hurt, but have run mine for 7 days and been ok. Even a bberry cant do that!
Sent from my X10i using XDA App
Guys, don't use home button to exit apps.
Will just send them in background.
Use the back button... this won't exit (most of) the apps but will put them in a "sleep" state so, next time when you will use it, it will load faster.
So, again, home button will put the app in background, still running.
Test it with an audio player for ex.
Or a browser... send it in background with home button and the player will still play or the browser will still have that page loaded.
With back button, after all views are "closed" the app will close too (well, put in sleep state).
I use ATK only to kill the apps i use once in a while ... the rest of the stuff, is always in memory.
My X10 has usually about 25Mb free
Actually I used ATK to kill application that need to connect to internet, and in my case there is extra charge payment. But after i used ATK I don't notice that the battery live is longer. So I ever ask someone in my thread about after ATK kill applications and so forth....
And somebody told me to quit using ATK and now I realize that the battery last longer than before.
But one thing still bother me is:
Setting - Wireless control - mobile network - mms & data (no checklist)
means: I can not access internet and receive or send mms either.
Actually I only need MMS, not internet.
May be somebody can help me solve this problem.
Thanks.
But my conclusion:
NO NEED ADVANCE TASK KILLER.
After I uninstall ATK, my phone still running smooth and the battery last longer.
May be we just need best Cache cleaner. But I still trying some of that.
@pco.vaz
I don't want to be mean, but you are wrong.
Even those iOS versions that are not multitasking enabled keep apps in memory. Leaving an app on an iPhone resets its UI state and halts its processes, but parts of the app are left in the memory. You can see the difference in loading speed if you decide to reopen it.
There were apps that could show memory usage and clean it on the App Store, but Apple removed them. You can still get them through Cydia and see for yourself how memory management on iTouch devices actually works. Basically the iPhone goes as low as 3-4 megs of free memory and handles it in smiliar way as Android.
On both Android and iOS, apps that are in background are paused after a while and do not use processor cycles. Memory they keep occupying is overwritten if needed by another process.
I do not recommend using task killer to people who do not know what they are doing exactly. Killing even simple processes often causes phone instability and drains battery faster, as others have already said.
If you feel your phone is stalled, perform a simple reboot. There are apps that run in background (in most cases you are warned about this) or are poorly coded that could cause this behavior. Other than that, inbuilt application manager is able to force close apps pretty well, if you need to kill a single app causing problems
Which is better/necessary for maintaining max speed and free memory?
neither, you do not need any type of task killer with android. why do people insist on using these apps.
rlxurmnd said:
neither, you do not need any type of task killer with android. why do people insist on using these apps.
Click to expand...
Click to collapse
You forgot a question mark.
The stock JI6 task manager and a shortcut to "running services". This will show you EXACTLY what's RUNNING on your phone. Key word is running!
rlxurmnd said:
neither, you do not need any type of task killer with android. why do people insist on using these apps.
Click to expand...
Click to collapse
Well I don't know why the task related apps exist. If they didn't exist I wouldn't be asking the question.
the one with the JI6 is very useful for me.
Sent from my SGH-T959 using XDA App
stevenmcneal83 said:
Well I don't know why the task related apps exist. If they didn't exist I wouldn't be asking the question.
Click to expand...
Click to collapse
Some devs are stuck with the Windows Mobile mentality that Android requires task managers. Android will free the memory as needed, all you need is the stock J16 task manager if you'd like to close the occasional/accidentally left open app.
You guys are doing a very poor job of answering his question and most of it is misinformation.
Auto Killer is NOT a task killer. It is a memory optimizer. It basically uses the same system that is built into Android and modifies the intervals at which it clears memory. It does not kill tasks unless you specify it to.
For instance, default Vibrant is set to start freeing RAM from "empty" apps at 63 MB of RAM left. Empty apps are apps that have been sitting for awhile, not using cpu and not being used but are stored in RAM. You could see why these apps would be the first to go. Well, with Auto Killer, I can change the threshold to 98 MB so when it drops below that, the Android system frees up RAM from the apps that aren't being used.
Auto Killer is nowhere near the same as a task killer or task manager and it actually benefits your system greatly because it just modifies Android memory management system.
Again, the default Android system ALREADY starts clearing RAM automatically at 63 MB left meaning you will always have at least 63 MB of RAM unless you are using tons of apps at once, since they would all be active and Android will not free RAM from active apps unless you are critically low on memory. I'm talking less than 10MB. I like to have at least 98 MB left though so Auto Killer modifies that. Auto Killer does not modify the way Android handles apps, you just tell it the thresholds and then Android does its thing.
kangxi said:
You guys are doing a very poor job of answering his question and most of it is misinformation.
Auto Killer is NOT a task killer. It is a memory optimizer. It basically uses the same system that is built into Android and modifies the intervals at which it clears memory. It does not kill tasks unless you specify it to.
For instance, default Vibrant is set to start freeing RAM from "empty" apps at 63 MB of RAM left. Empty apps are apps that have been sitting for awhile, not using cpu and not being used but are stored in RAM. You could see why these apps would be the first to go. Well, with Auto Killer, I can change the threshold to 98 MB so when it drops below that, the Android system frees up RAM from the apps that aren't being used.
Auto Killer is nowhere near the same as a task killer or task manager and it actually benefits your system greatly because it just modifies Android memory management system.
Again, the default Android system ALREADY starts clearing RAM automatically at 63 MB left meaning you will always have at least 63 MB of RAM unless you are using tons of apps at once, since they would all be active and Android will not free RAM from active apps unless you are critically low on memory. I'm talking less than 10MB. I like to have at least 98 MB left though so Auto Killer modifies that. Auto Killer does not modify the way Android handles apps, you just tell it the thresholds and then Android does its thing.
Click to expand...
Click to collapse
Awesome! Thanks so much for being thorough, I'm kinda new. One more quick question, since auto killer seems to be the best way to manage free memory, do I need to remove the task manager if I plan on using auto killer?
Yes. I use just auto killer. No task killer or anything. If I do need to close an app that is frozen or something, I just use the task manager built-in with JI6. Otherwise, just pressing the back button in 99% of all apps will properly close it.
kangxi said:
Yes. I use just auto killer. No task killer or anything. If I do need to close an app that is frozen or something, I just use the task manager built-in with JI6. Otherwise, just pressing the back button in 99% of all apps will properly close it.
Click to expand...
Click to collapse
The built in task manager is the one I was referring to. The one that came included with fusion 1.1. So you currently have both auto killer and task manager on your phone? Forgive me for the confusion
Yes, but like I said, I only use it when I really need to close something which isn't that often. Like if a game I am playing freezes. When I am done with an app, just press the back button and it will close. Try it.
Open an app, press home then look in the task manager. It will be there.
Open the same app, press back, open the task manager and it won't. So using the task manager is like just for emergencies if the app won't close properly.
Thanks alot man
I often find all of the preloaded apps opening in the bg. I used to handle this with auto killer but since I have no root yet I'm manually killing then with task manager. Are there any alternative methods of doing this?
when theyre open I'm under 200 left of mem space, when I kill em I'm back up to 300+ so it's kind of a big deal in terms of performance.
Thanks
Sent from my 3vo using XDA App
Task killers haven't been needed since Android 2.2. The apps may be running, but they're not doing anything. They're just chilling in the background. Android automatically manages the memory and kills things when it gets too full. I have 124MB of RAM right now, no big deal.
But if you insist, advanced task killer.
Sent from my PG86100 using XDA App
This isn't the usual question about low memory etc etc its about the remaining memory in the task manager and in the application manager.
Why does the task manager show less remaining ram than the application manager? Which one should I believe?
I think application manager as it accounts for all system processes too
Sent from my GT-I9300 using xda premium
Nice one, just thought it was a bit weird for it to show different values even thought it's the same thing but worded differently