Related
Hi,
I have noticed that my Nexus' performance starts to drop after some hours on: going from one home screen to the other becomes quite choppy, and so do the animations of opening an application.
Have you guys noticed that too, or is it just me?
It was like this for me until I bought Advanced Task Manager. I have it auto end applications that I don't need to run all the time. It runs much better now.
The issue is RAM. The kernel that shipped with the Nexus One doesn't support the full 512MB of RAM. However, CyanogenMod 5.0-beta4 does and the difference in speed is amazing. With 26 apps running I have 167MB free atm.
But like stickerbob said, you should have Advanced Task Manager at the least.
Deathwish238 said:
The issue is RAM. The kernel that shipped with the Nexus One doesn't support the full 512MB of RAM. However, CyanogenMod 5.0-beta4 does and the difference in speed is amazing. With 26 apps running I have 167MB free atm.
Click to expand...
Click to collapse
I don't get it. Isn't Android supposed to kill unused apps when it's running out of RAM?
frandavid100 said:
I don't get it. Isn't Android supposed to kill unused apps when it's running out of RAM?
Click to expand...
Click to collapse
Yep but some people just don't get that, ah well...
efeltee said:
Yep but some people just don't get that, ah well...
Click to expand...
Click to collapse
Well, that doesn't really explain the performance drops. Does the phone run out of RAM, or not? It seems to be snappy again after a reboot, so there must be something.
frandavid100 said:
I don't get it. Isn't Android supposed to kill unused apps when it's running out of RAM?
Click to expand...
Click to collapse
That is what I have read, but it did not work for me. I downloaded the free version of advanced task man to troubleshoot the problem and found that most of my apps were still running in the background even when my ram was down to 10-20mb. That is about when the phone would start acting up on me. When I ended the tasks the phone would act normal again. So I just broke down and bought the app for $.99. If you do this make sure you exclude some system apps, if you don't your phone could freeze while it is trying to restart them.
10-20mb free is normal operation. This is how the OS is designed to operate, linux and even windows7 now also operate in this fashion (show very little 'free' memory). there is no performance problem with low free memory, purely a misconception on modern memory managment. Whats going on is that you have a buggy application, which is why 'killing' apps looks to be resolving your issue. You're only resolving the symptom, not the problem.
I never kill apps and have had weeks of uptime without any slow down. This gets rehashed over and over again by people claiming task killers help performance. The reality is they do nothing for performance, only nice to have around for that great once and a while an app runs away from you, or in troubleshooting if you have a poorly written app. It should not be anyones habit to do a kill all on a regular basis, if it were the OS would do this automatically.
btw, compcache has been known to cause this slowdown over time issue, it has since been removed from most of the popular custom baked rom's.
frandavid100 said:
I don't get it. Isn't Android supposed to kill unused apps when it's running out of RAM?
Click to expand...
Click to collapse
Yes it does...
bofslime said:
10-20mb free is normal operation. This is how the OS is designed to operate, linux and even windows7 now also operate in this fashion (show very little 'free' memory). there is no performance problem with low free memory, purely a misconception on modern memory managment. Whats going on is that you have a buggy application, which is why 'killing' apps looks to be resolving your issue. You're only resolving the symptom, not the problem.
I never kill apps and have had weeks of uptime without any slow down. This gets rehashed over and over again by people claiming task killers help performance. The reality is they do nothing for performance, only nice to have around for that great once and a while an app runs away from you, or in troubleshooting if you have a poorly written app. It should not be anyones habit to do a kill all on a regular basis, if it were the OS would do this automatically.
btw, compcache has been known to cause this slowdown over time issue, it has since been removed from most of the popular custom baked rom's.
Click to expand...
Click to collapse
Well then there must be many buggy applications. I had to rely on Advanced Task Manager to keep my G1 running acceptably fast. The N1 slows down without its full RAM available so I needed to use Advanced Task Manager then too.
If the RAM is not the issue, why does having the extra 200 MB available make the phone run much smoother with 20+ apps running?
frandavid100 said:
I don't get it. Isn't Android supposed to kill unused apps when it's running out of RAM?
Click to expand...
Click to collapse
well technically no, it reallocates what is being used and frees up memory for programs currently running but non the less the OS manages itself
personally i close apps that i do not have going with the task manager. i seem to notice a performance difference if i do it manually, it takes 2-3 extra taps for peace of mind rather than relying on the OS to figure it out for me...
Deathwish238 said:
The issue is RAM. The kernel that shipped with the Nexus One doesn't support the full 512MB of RAM. However, CyanogenMod 5.0-beta4 does and the difference in speed is amazing. With 26 apps running I have 167MB free atm.
But like stickerbob said, you should have Advanced Task Manager at the least.
Click to expand...
Click to collapse
The speed benefits of CM's ROM isn't due to the HIGHMEM supporting kernel, but rather other tweeks he's done with his build. Extra ram is nice, but there is certainly no limitation with the 213 or so userspace memory that is available now. Android itself does not even use this memory, it has its own reserved memory space, userspace memory is only for applications to be loaded in. And there is speed for keeping as much of your applications loaded in memory as possible.
swetland said:
Roughly 220MB is available to userspace in the shipping build (ERD79).
Quite a lot of memory is dedicated to the radio firmware (41MB), dsp firmware (32MB), display surfaces (32MB), gpu (3MB), camera (8MB), a/v buffers (41MB), and dsp buffers. Much of this needs to be set aside for these specific tasks due to hardware requirements of very large physically contiguous buffers which can be difficult or impossible to obtain after boot once the physical memory space gets fragmented.
The big limitation though is that the Linux kernel needs to do a 1:1 physical:virtual map of general purpose memory used by the kernel and userspace (which excludes the special purpose stuff described above). This eats into the available kernel virtual address space, which is also needed for cross process shared memory used by the binder, etc. Run out of virtual memory and things get unhappy.
In 2.6.32, HIGHMEM support for ARM will allow us to avoid this requirement for a 1:1 mapping which will allow us to increase memory available to userspace without running the system out of virtual memory adddress space.
Click to expand...
Click to collapse
The speed difference I'm talking about is what I experienced when running CM beta3 and CM beta3 w/ highmem. The difference was huge. I assumed the change was mainly attributed to the double RAM available.
Even now with the full RAM available, things run faster when I end the other apps running. It's not necessary, but the difference is there.
It would be nice to be able to pinpoint which apps caused slow downs.
The best way I've seen this put I found in a thread where someone wanted to disable apps from auto-starting entirely. I saved it, because I though it was very elegant way to explain androids mem management.
equid0x said:
I just wanted to chime in here about the whole apps on startup thing....
Android has the concept of services which are programs that typically have a frontend piece, like a GUI for IM that you would normally use, that only runs when you are using it, and a background piece, the service, which is constantly running to keep you connected to your IM servers. This will account for some portion of the things you see running on startup, depending on how many apps you have installed, and whether or not they were written to run as a service.
There are also some, usually older, android programs that existed before "services" were really used.. that basically use triggers to keep reloading themselves. These programs are less efficient, and probably should be re-written to use the official service method of operation, caveat emptor.
Android also makes several modifications to the stock process handling that comes with any Linux kernel, which is already radically different from what most would be used to seeing on Windows as it is. Android attempts to keep commonly used applications running(loaded into memory), but in a sleeping state (using no cpu), so that they may be quickly resumed on request. Android also contains some agressive modifications to the behavior of the OOM(out of memory) task killer in Linux, that seem to cause it to keep applications running until nearly all memory is consumed, killing apps it deems unnecessary only when absolutely necessary. However, Android also supports a methodology of saving the running state of a program, so that if it is killed due to an OOM condition, it may be restarted with relevant data restored, to give the appearance of never having been killed at all.
This functionality is not all to alien to Linux as a platform in general, though Android has many modifications which tend to favor aggressive app management in memory, and less so filesystem cache. This was likely a design choice made to suit the low-speed/low memory platforms Android targets.
Click to expand...
Click to collapse
Good read.
So then given that...only services running should slow down the phone and not the background apps running.
However, this doesn't really answer the OP's question. If it's not a memory issue...what's causing his slowdowns?
Could be too many widgets on the home screen, I don't run that many but its possible that while in an app for a while, and switching back to home the OS may have to kill a whole bunch of apps to allow it to reload all the widgets on the home screen.
I tested this, and loaded the crap out of my home screens with widgets, and then launched a game. When I exited the game there was a good 500ms - 800ms delay in my homescreens from displaying anything other than the background. However, after it loaded, scrolling between screens looks smooth. The new kernel with highmem support can help this, but I would suspect some crazy widget filled homescreen with a 3rd party live wallpaper (star's configured with too many stars) and all of that combined could be an issue even still. Apple combats this by allowing only one app at a time, they know people will go overboard if allowed.
Well, that doesn't really explain the performance drops. Does the phone run out of RAM, or not? It seems to be snappy again after a reboot, so there must be something.
Click to expand...
Click to collapse
There's probably no easy answer to this question. There could be IO contention, a runaway process, high CPU usage, a memory leak, shoddy code in some app, etc etc... One would really have to take a look at the whole state of the system at the time the problem is happening to be able to ascertain what is causing the slowdown.
The phenomenon is in no way unique to Android. I'm sure nearly everyone is familiar with the common complaint "my computer is running slow". The reasons that can happen on a common PC are the very same reasons that can be happening here, and unfortunately there are many of those reasons. While in many cases, throwing memory at the issue may appear to solve the problem temporarily, it often is not a permanent fix.
The amount of userspace memory available really amounts to 1 thing and 1 thing only -> the total number of running processes that we can keep totally in memory at any given time. On stock android, slowdown due to an OOM condition should be minimal, since stock android doesn't swap. Discounting any other bottlenecks, there is a practical limit to the number of programs once would be able to run in the memory space that is available. Realistically speaking, android programs tend to be fairly small, so you'd really have to be running a lot of them to exhaust this space. It is far more likely one or 2 poorly written programs are hogging huge amounts of memory (and probably other resources), which is causing constant killing and restarting of other apps you are trying to run concurrently. You end up with contention on the slow flash, resulting in poor performance.
You can't even really compare the Nexus One to the G1 in this regard, because the G1 truly is terribly deprived of memory. Though, the argument in both cases could really be made that you are attempting to run the hardware beyond its design specifications...
Its been my experience that the culprit is usually one or 2 specific programs. Sometimes the best, although inconvenient, way to figure out which programs these are, is to keep watch of your usage habits, and if you suspect something is the problem, uninstall it, and see if the issue persists. Its time consuming but there really isn't any better way to figure it out without using all kinds of tools that android doesn't really provide convenient access to. There are a few apps on the market that help with this but I am not sure what they are called offhand.
Programs that were identified as sources of slowdown for me have been:
Weatherbug
The Weather Channel
Calorie Counter
Locale
SMS Popup
10000
USA Today
National Geographic Wallpapers
CNN News Widget
Streamfurious
Nav4All
Waze
Just about every app with Admob Ads
And this is really just what I can think off offhand... there are more...
equid0x said:
There's probably no easy answer to this question. There could be IO contention, a runaway process, high CPU usage, a memory leak, shoddy code in some app, etc etc... One would really have to take a look at the whole state of the system at the time the problem is happening to be able to ascertain what is causing the slowdown.
The phenomenon is in no way unique to Android. I'm sure nearly everyone is familiar with the common complaint "my computer is running slow". The reasons that can happen on a common PC are the very same reasons that can be happening here, and unfortunately there are many of those reasons. While in many cases, throwing memory at the issue may appear to solve the problem temporarily, it often is not a permanent fix.
The amount of userspace memory available really amounts to 1 thing and 1 thing only -> the total number of running processes that we can keep totally in memory at any given time. On stock android, slowdown due to an OOM condition should be minimal, since stock android doesn't swap. Discounting any other bottlenecks, there is a practical limit to the number of programs once would be able to run in the memory space that is available. Realistically speaking, android programs tend to be fairly small, so you'd really have to be running a lot of them to exhaust this space. It is far more likely one or 2 poorly written programs are hogging huge amounts of memory (and probably other resources), which is causing constant killing and restarting of other apps you are trying to run concurrently. You end up with contention on the slow flash, resulting in poor performance.
You can't even really compare the Nexus One to the G1 in this regard, because the G1 truly is terribly deprived of memory. Though, the argument in both cases could really be made that you are attempting to run the hardware beyond its design specifications...
Its been my experience that the culprit is usually one or 2 specific programs. Sometimes the best, although inconvenient, way to figure out which programs these are, is to keep watch of your usage habits, and if you suspect something is the problem, uninstall it, and see if the issue persists. Its time consuming but there really isn't any better way to figure it out without using all kinds of tools that android doesn't really provide convenient access to. There are a few apps on the market that help with this but I am not sure what they are called offhand.
Programs that were identified as sources of slowdown for me have been:
Weatherbug
The Weather Channel
Calorie Counter
Locale
SMS Popup
10000
USA Today
National Geographic Wallpapers
CNN News Widget
Streamfurious
Nav4All
Waze
Just about every app with Admob Ads
And this is really just what I can think off offhand... there are more...
Click to expand...
Click to collapse
I'm banking on it being an issue with an app that the OP has installed as well...not the phone or Android. I have only a handful of tried and true apps, and haven't experienced a slowdown even after 150 hours without a reboot.
OP... start uninstalling apps a couple at a time and wait several hours in between to narrow down the problem app.
I can't speak for the OP, but when I was having that problem I had 5 widgets running on my home screen. The Google Search, Sports Tap, Power Control, Calendar, and The Small Weather Channel. Does this seem like too much? I hope not.
stickerbob said:
I can't speak for the OP, but when I was having that problem I had 5 widgets running on my home screen. The Google Search, Sports Tap, Power Control, Calendar, and The Small Weather Channel. Does this seem like too much? I hope not.
Click to expand...
Click to collapse
It's not just widgets that you should be thinking about... any app you've installed can throw something off.
stickerbob said:
I can't speak for the OP, but when I was having that problem I had 5 widgets running on my home screen. The Google Search, Sports Tap, Power Control, Calendar, and The Small Weather Channel. Does this seem like too much? I hope not.
Click to expand...
Click to collapse
I removed the weather & news widget and the phone seems much faster now. I'll keep it like that for a day, see if it stays fast.
Hello, all. I am currently running the free version of Advanced Task Killer, which seems to work ok, but there has to be something better. What I've noticed is, that after a reboot, the app will tell me that I have about 240 MB of available memory when all apps are closed with the exception of the task killer itself.
However, by the end of the day, after I've opened and closed a few apps, sent some messages and emails, made some calls, etc, the task manager will show significantly less available memory available. It could drop to as low as 135 MB with all apps closed with the exception of the task killer.
This leads to me to believe one of two things:
a) The Task Killer is full of it and it does not have an accurate read of how much memory is actually available.
b) The Task Killer is only able to "kill" certain tasks while others remain running in the background and it does not show that the app(s) are actually running.
Honestly, I think it is option B, because I do notice that when the app tells me that I have less than normal available memory, the phone does tend to function slower and lag a bit. Nothing that cannot be fixed by a powering it off and on, but I am hoping that someone knows of a good app (even if it is a paid app) that will actually bring up ALL tasks running and kill them. I've also noticed that even with this task killer, Google Talk (which I have never used) always remains open in my phone and I have to manually go into into the settings and turn that off.
Any suggestions?
My suggestion is to not use one.
I do use Autokiller though which tweaks the thresholds for Android's internal "task killer".
It's best to let Android do it's thing.
Tikerz said:
My suggestion is to not use one.
I do use Autokiller though which tweaks the thresholds for Android's internal "task killer".
It's best to let Android do it's thing.
Click to expand...
Click to collapse
Really? Do you mind elaborating on why you feel that way a bit so I can understand? Because I do notice that when the I am running a bunch of things at once and I use this app to kill the tasks, it does improve the performance of the phone.
I can understand why some people say you don't need one but I do think it is necessary to have it installed for when you do. I'd rather kill apps than pop the case, battery cover and battery to fix a frozen phone.
I have some GPS apps I run occasionally that after exiting them they don't turn off the GPS or lock the GPS on and drain my battery. So for those apps where the developer didn't put a close buton on the menu it helps shut them down. I don't know why Google Market doesn't require apps to have a close option.
get OS MONITOR from the market
PAPutzback said:
I don't know why Google Market doesn't require apps to have a close option.
Click to expand...
Click to collapse
Because users shouldn't have to manage their own memory. Apple folks already love laughing at us for that very reason, and even though it pains me to say it they're absolutely correct.
I can certainly buy the argument that task killers are nice for those occasions when something does go haywire and it needs to be forcibly killed, and I can understand using one just because you're curious and want to see what's running and how much memory you have, etc, but beyond that I find that they're unnecessary. My EVO runs very smoothly without me manually intervening, even after many days of uptime with many apps running.
GHOST99K said:
get OS MONITOR from the market
Click to expand...
Click to collapse
Wow! That's detailed and a lot more than I bargained for....lol. Thanks! Good thing my phone is rooted and I was able to use it since I never did the recent update to the 1.47.xx OTA update and I'm waiting for a fully functional version to be released, but there is a lot of stuff on this that goes well beyond my basic knowledge. Apparently, my phone has 89 processes running with no apps running (according to Task Killer) and only one widget running and the CPU is fluctuating at 10-40% usage.
Interestingly enough, but apps report the same amount of available memory......EXACTLY the same. So it can be assumed that both apps provide an accurate figure of available memory.
I would advise against using a Task killer. Android has its own memory management, which works extremely well on the EVO, to be honest. The latest update (1.47) feels like its makes the EVO perform much better and allows it to be more efficient.
If anything, I would suggest you read this thread about an app called Autostarts, which isn't a task killer, rather a startup manager that can be tweaked to do many different things. By not allowing certain things to start up when your phone boots, you'll have more memory to begin with and Android will be more efficient in memory management. I would try Autostarts before using a task killer.
Hope that helps.
eagle63 said:
Because users shouldn't have to manage their own memory. Apple folks already love laughing at us for that very reason, and even though it pains me to say it they're absolutely correct.
I can certainly buy the argument that task killers are nice for those occasions when something does go haywire and it needs to be forcibly killed, and I can understand using one just because you're curious and want to see what's running and how much memory you have, etc, but beyond that I find that they're unnecessary. My EVO runs very smoothly without me manually intervening, even after many days of uptime with many apps running.
Click to expand...
Click to collapse
I agree, but having to run a task killer is a small price to pay to not be part of the iPhone bandwagon crew, IMO.
Are you running a custom rom on your phone? I just have a rooted stock rom. Maybe that's why your phone can go days without the performance being affected? I still have all the bloatware on mine, and I've put off removing it because I am still a noob at this and I'm in the learning process. I wonder if the new update that was just released improves this aspect of the phone at all.....?
pseudoremora said:
I would advise against using a Task killer. Android has its own memory management, which works extremely well on the EVO, to be honest. The latest update (1.47) feels like its makes the EVO perform much better and allow it to be more efficient.
If anything, I would suggest you read this thread about an app called Autostarts, which isn't a task killer, rather a startup manager that can be tweaked to do many different things. By not allowing certain things to start up when your phone boots, you'll have more memory to begin with and Android will be more efficient in memory management. I would try Autostarts before using a task killer.
Hope that helps.
Click to expand...
Click to collapse
Thanks, I will definitely look into it. All advise is appreciated as I am very new to all of this. You answered my last question on my previous post with this, too.... I can't wait for a fully functional rooted OEM rom to be released with the goodies from the new update to try it out. I'm hesitant to update my phone now and lose superuser as I use the WiFi tether a lot.
Many people say it's harmful using app killers, especially on android as it may interfere with important system resources or close important system files and can do harmful damage in the longrun such as errors, things not working, etc...
When you open various programs such as file manager, picture gallery, etc you then see a list of all running programs in system/task manager.
Many of these running programs are ones you have recently used and are draining ram/cpu/battery.
Is there not ANY safe app to use that will ONLY close apps that YOU have used?
There must be some app out there that closes/kills open apps, not system or phone apps but only the ones you have installed and used?
This could be a ram killer or maybe a simple app which is not dangerous and will safely close running apps not needed.
Looking forwards to seeing what others recommend.
Thanks in advance guys,,,
kanej2006 said:
There must be some app out there that closes/kills open apps
Click to expand...
Click to collapse
yes, there are, but android just restarts them after they have been closed (froyo only)
panyan said:
yes, there are, but android just restarts them after they have been closed (froyo only)
Click to expand...
Click to collapse
Names please of a good app that kills ONLY programs you open, not system files.
What if I was to install an appkiller, but instead of having it on autokill, I was to manually click apps I opened and kill them?
Surely this way there is no danger as I'm only closing selected apps, not system files?
kanej2006 said:
Names please of a good app that kills ONLY programs you open, not system files.
What if I was to install an appkiller, but instead of having it on autokill, I was to manually click apps I opened and kill them?
Surely this way there is no danger as I'm only closing selected apps, not system files?
Click to expand...
Click to collapse
The point is, even after killing your own apps, most of the time froyo will restart them
I very much like ES' offerings - ES File Explorer and ES Task Manager. They're both free, give em a birl.
You can install Advanced Task Killer (free) and there you can perfectly select which apps to close and which not... still I rarely use it
for example your homescreen widgets are always unchecked when killing tasks, so unless you check them, they won't be killed...
Hmmm, ok.
What is the BEST way to preserve & save battery/cpu & free up as much ram as possible without harming/interfering with the phone??
When I used to use the task killer app it would consistently give me around 400-424mb free ram.
Without the app killer I would only have around 100mb of free ram since all the programs are running in the backround.
So to all you experts out there, what can I do or what options do I have in which I can safely free up as much ram as possible and safely close running apps not needed when not using the phone?
I just want the best and most effective way to make my battery last longer.
I'm having to charge my phone every day, it struggles to get through the day even when hardly used.
Looking forwards to hearing some expert opinions based on the above.
kanej2006 said:
I'm having to charge my phone every day, it struggles to get through the day even when hardly used.
Click to expand...
Click to collapse
There's definitely a problem there but you're not going to find it chasing free ram. I have approx 20Mb free ram at the moment, the phone hasn't been rebooted for at least a week but I'm easily getting through 2 days with light use. Task killers / app killers are not the answer, (in froyo at least) free ram is wasted ram.
The programs that are 'running' in the background are not actually using CPU resources unless they have a service running (see the eBay app/service for an example). Your best bet is to check the running services (settings/applications/running services) and battery usage to work out what process is hogging the CPU time. Also check your sync settings, though I'd imagine you've already tried that.
christonabike said:
There's definitely a problem there but you're not going to find it chasing free ram. I have approx 20Mb free ram at the moment, the phone hasn't been rebooted for at least a week but I'm easily getting through 2 days with light use. Task killers / app killers are not the answer, (in froyo at least) free ram is wasted ram.
The programs that are 'running' in the background are not actually using CPU resources unless they have a service running (see the eBay app/service for an example). Your best bet is to check the running services (settings/applications/running services) and battery usage to work out what process is hogging the CPU time. Also check your sync settings, though I'd imagine you've already tried that.
Click to expand...
Click to collapse
Maybe it's the anipet fish aquarium live screensaver...
Systempanel is good, I use it to stop a bad app thats using to much memory..you should never kill your apps with froyo, the OS wasn't designed like that, thats the whole point of Android, it looks after the apps perfectly well by itself, systempanel is just there as a....just in case method.
Saving battery power is a common misconception, Task killers actually get in the way of Android handling memory management as intended.....a pointless app to have with 2.2 which actually drains you battery quicker.
The LCD screen is the biggest drain on battery power, turning the brightness down, stop using a live wallpaper, turn off wifi, bluetooth, GPS ect....
With all that said the 1250mah battery is just not powerful enough to run this device period...but then most of us knew this before we bought the phone..we needed a 2000mah battery really, its just a lipo battery and can be easily increased, maybe next year we will see an improvement in the new smartphones.
kanej2006 said:
Maybe it's the anipet fish aquarium live screensaver...
Click to expand...
Click to collapse
I hope you're joking
Black1982 said:
I hope you're joking
Click to expand...
Click to collapse
LOL, well some people do say that live wallpaper kills battery...
Hi,
i just bought an Ideos x5 and it's great.
I've loaded most of the usuall stuff including task manager.
Now i found that on average my free memory when i'm not using so much apps is around 180(that's how much free RAM i have).
Is this normal..i mean...the thing says it has 512 mb of RAM.
Sorry for beeing a noob..
Van
its said 128MB go to the GPU, 32MB are used by android system, which leaves about 352MB (353MB as shown in Elixir) for application use..
and then those google apps (Maps, Search, Market, etc.) all take up RAM in the background, plus other background apps you have installed and widgets you have enabled..
on average i usually have around 80-120MB free RAM left.. and since android 2.2 is said to have a good task manager which frees up the RAM when needed, i dont think its a place to worry about..
As iamelton said, Android's in-built task managing system does a good job of managing what apps are using the processor, memory and battery. Task manager apps don't really do all that much useful, and can sometimes be counterproductive if you're trying to use them to save battery. Lifehacker has a really great article on this called Android Task Killers Explained: What They Do and Why You Shouldn’t Use Them (I can't link because I don't have enough posts, but the article's a search away and is really worth reading). It runs through why it's generally best to avoid task manager/killer apps, plus it also explains how Android uses RAM - in a similar way to Windows Vista/7 (basically to speed up launching or re-opening apps).
It's probably worth noting that Android already has a function to force stop apps. If you go to Settings > About phone > Battery use, you'll get a list of what's been using the battery since it was last unplugged. Some widgets like Switch Pro have shortcuts to Battery use. It's useful if you've got Maps or a launcher or a rogue app sucking up battery in the background. As a rough idea, you may have an issue if anything not a system process is using more than 10%.
If you do need to force close an app, Battery use is generally the best way to go about it.
thx to cyvros for ur mentioning of the good article..
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
its a good read indeed, and for this topics discussion, i think the following paragraph gives a very good view on androids ram usage:
The problem is that Android uses RAM differently than, say, Windows. On Android, having your RAM nearly full is a good thing. It means that when you relaunch an app you've previously opened, the app launches quickly and returns to its previous state. So while Android actually uses RAM efficiently, most users see that their RAM is full and assume that's what's slowing down their phone. In reality, your CPU—which is only used by apps that are actually active—is almost always the bottleneck.
Click to expand...
Click to collapse
This article was posted on Android Central and should be mandatory reading for everyone in these forums:
http://feedproxy.google.com/~r/andr...hat-it-how-its-used-and-why-you-shouldnt-care
Good read, reminds me of how XP's memory handleing is compared to Vista/7's system.
Basic jist:
XP: System asks for very little: Task manager shows only ~100mb used on a very slim system
Vista/7: System uses ~40% of available memory if it's free, surrenders it back as programs are loaded that need it. Task manager shows ~2gb used on a slim system (assuming 4gb total rom)
What's it look like? Vista/7 uses 2gb vs XP uses 100mb.
What it does: Not much difference really, Vista/7 is just as stable with ram intensive apps (example: a virtual machine asking for 3gb ram on a 4gb system) both on XP and Vista/7 it will run and not bog the system down (from a ram perspective, we're completely ignoring cpu usage).
It's reasonably similar in android: recently loaded apps stay resident in memory, if the foreground app needs more ram android will unload older apps that arnt running. If you wanna run an app unloaded from memory, android has to reload it from storage.
If you task-kill everything immediately, android will ALWAYS have to reload from memory. The only exception is if the app didnt behave well in the first place (like auto-loading with a memory heavy service), if that's the case you're just as well off complaining to the dev because he/she needs to fix it anyway.
Though with the streak stageui is a pretty good example of this, widgets pretty much always stay loaded as they're widgets. Most of them use background services to update themselves and they're rather cpu/ram intensive.
You could task-kill them, but the right thing would be to freeze/completely remove them if you dont use them.
Thanks for sharing
I repair cell phones for a living and I notice carriers puting task killer on peoples phones....this is a phone killer some important processes get killed and I've had customers complain about phones not rotating right cause of thus also it causes alot of phone freezes and other problems cause of this....if u haveba task killer get rid of it and you will notice the difference..
Sent from my Dell Streak using XDA Premium App
very useful.
personally never used task killers and the like , coming from the old school just dont feel at ease with applications doing things