How to disable multitasking? - General Questions and Answers

Hey, I want to know if its possible to disable multitasking or make it so hitting the "back/ok" button will close programs not minimize. I hate the multitasking in windows mobile because its very annoying to hit that tiny task manager on the top right corner just to close programs. It also sacrifices performance and battery life to keep those apps running in the background. I hardly ever need to multitask so is there any way to disable multitasking or something close to that?

Tada1228 said:
Hey, I want to know if its possible to disable multitasking or make it so hitting the "back/ok" button will close programs not minimize. I hate the multitasking in windows mobile because its very annoying to hit that tiny task manager on the top right corner just to close programs. It also sacrifices performance and battery life to keep those apps running in the background. I hardly ever need to multitask so is there any way to disable multitasking or something close to that?
Click to expand...
Click to collapse
Dude, there's 65k+ of software for PPCs including taskmanagers.
I STRONGLY RECOMMEND buying iphone, if you cannot manage.
Or wait for w7.
Anyway, you may give away your device for poor ones, too.
It also sacrifices performance and battery life to keep those apps running in the background.
Click to expand...
Click to collapse
So, maybe CLOSE them with any TASK MANAGER available....
Info for moderators:
Sorry, couldn't resist.
Can you imagine, there are people that are not aware, that "x" is not closing apps?...
Despite of all knowledge of the world, people, internet and FOCKIN twitter.

Iphones are way too expensive. I know that there are task manager apps but none of them solve my problem. Iam saying that its annoying to constantly close apps in the background. It's also annoying to hit the tiny X button, which I know closes apps. The multitasking feature is useless to me and I want it disabled because it would make this phone much better for me. I am not a heavy power user, just a casual user.

Multitasking can not be disabled. That basically defeats the purpose of android and having a smart phone. All you can do is use a task manager or task killer. Whatever you want to call it. I don't know how it doesn't solve your problem because what it does is close the app.

See the thing is that android is a much better multitasker and I didnt see any performance drops when multitasking on a android phone. Windows mobile gets real slow and requires you to either soft reset or clean ram often. Yeah, I think iam done with windows mobile phones for now, Iam really looking forward to Windows phone 7. The perfect phone for casual users like me.

Tada1228 said:
It's also annoying to hit the tiny X button
Click to expand...
Click to collapse
have you ever thought about mapping taskkiller to button....

Advanced Task Killer can end apps on screen-off. I use this keeps phone running smoothly. Can also be set to do it at a timed interval.

You can use app from google play store name Ram Manager Pro this app can manage options multitasking and swap file. When you check more multitasking then depending from your available ram android will keep in memory lot of apps or reverse will be better for games with free memory for hard gaming. You can use swap file 256 mb recommended and swampiness to 80. I have multitasking set at full.

Related

Best Android Task Manager - Open Processes

Hello All,
I wanted to see what everyone thinks is the best application manger for Android.
Also is anyone familiar with the Getjar free app store?
Thx All,
Force
What do people think of "Advance Task Killer"
It seems to me it shows all tasks, not jsut the open ones.
Regards,
Force
FYI,
Many people say talk killers are not necessary, as that is a windows phenomenon, Linux & android treating background processes differently.
Regards,
Force
I personally use Advanced Task Manager for $0.99. I have read the articles about how Android does not need task Managers because it is built in, but I know from personal experience that without it if there are running programs in the background my phone gets really sluggish especially when I get a phone call and it makes it difficult to answer etc. Take in account, this experience was mainly with the Hero (slower) but I use on my Evo now.
You know people will argue either way, because there is evidence to support both sides of the argument. so with that in mind- i honestly havent had the need for one with my evo, but it you truly are considering one- i actually have a pair to suggest.
one is OS Monitor- free on the market- great app for pinning down process that could be an issue- also supports dmsg repporting- and logcat is built in to- so if your testing something and it goes all wonky you can export the log to view on a pc and send it to the developer too.
the second is AMM- or Auto Memory Manager- free and donate versions on the market. There are pretty much a couple of sliders and you set it how you want android to handle the process. I have had great success with this app on my other device- normal free memory was around 30-35 and using this set aggressively i saw gains of 50mb at most times keeping my freememory to around 75-80mb range.
Hope this helps.
I take both sides. I have task manager installed, but use if ONLY when needed. Aka, I used it when I want to kill the browser after I'm done with it so next time I launch it I won't be seeing old pages.
I like EStrongs Task Manager.
http://www.appbrain.com/app/nextapp.systempanel.r1 is nice, it can kill processes, monitor system stats, uninstall apps and more. There is also a free version.
TREYisRAD said:
http://www.appbrain.com/app/nextapp.systempanel.r1 is nice, it can kill processes, monitor system stats, uninstall apps and more. There is also a free version.
Click to expand...
Click to collapse
i installed that last night, cool app
why someone who know don't explaine exactly how android works and do we need killers and if yes which one is best...
Everyone of us using something but question is that which one is best for our needs.
quick system info pro (free)
I only use the manual task killer widget when memory gets down around 100. Spikes it right back to about 250.
Whats your guys' normal memory range? I see someone on here saying 50 was normal for them but that seems REALLY low to me.
frifox said:
I take both sides. I have task manager installed, but use if ONLY when needed. Aka, I used it when I want to kill the browser after I'm done with it so next time I launch it I won't be seeing old pages.
Click to expand...
Click to collapse
Does the stock Sense browser not have an option to kill the windows by hitting menu? On CM, I do menu, windows, and X them out

background applications problem

iam on axura rom for captivate
my problem is that applications always run in background..i use advanced task killer to close those apps and again they start..whenever i open the advanced task killer i see them..actually some apps like dungeon hunter also running in background i dont understand why...can someone tell me how to take care of this problem???
Are you pressing the back button to close them when exiting or the home button?
smackdownn said:
iam on axura rom for captivate
my problem is that applications always run in background..i use advanced task killer to close those apps and again they start..whenever i open the advanced task killer i see them..actually some apps like dungeon hunter also running in background i dont understand why...can someone tell me how to take care of this problem???
Click to expand...
Click to collapse
Looks like android "pre-fetches" most frequently used apps into memory for quick access when u use them. They are loaded into memory, but CPU is not used. They are just loaded and kept. What's the point in keeping RAM free when it can't speed up system. So upto some amount, I don't know to what level though, apps are loaded into memory. And if u notice, u'll find RAM free like about 70-80MB all the time. This is what atleast I have personally observed.
peachpuff said:
Are you pressing the back button to close them when exiting or the home button?
Click to expand...
Click to collapse
iam pressing the back button only please help me solve this problem..and always that damn gmail app is open i background also...it starts like evry 5 mins i think and stays there forever..
diablo009 said:
Looks like android "pre-fetches" most frequently used apps into memory for quick access when u use them. They are loaded into memory, but CPU is not used. They are just loaded and kept. What's the point in keeping RAM free when it can't speed up system. So upto some amount, I don't know to what level though, apps are loaded into memory. And if u notice, u'll find RAM free like about 70-80MB all the time. This is what atleast I have personally observed.
Click to expand...
Click to collapse
ok so is this common?? and also i dont understand why dungeon hunter is there in advanced task killer...it is not some email or sm chat application..i close it..it starts at random time..do u mean these programs are not actually running?
and hey does beautiful widgets take a lotta battery?
smackdownn said:
ok so is this common?? and also i dont understand why dungeon hunter is there in advanced task killer...it is not some email or sm chat application..i close it..it starts at random time..do u mean these programs are not actually running?
and hey does beautiful widgets take a lotta battery?
Click to expand...
Click to collapse
I don't think they are necessarily running. They are kept in memory so next time the application is needed it will open more quickly. It shouldn't use any battery or CPU, the term RAM means Random Access Memory, so apps kept in RAM can just be accessed randomly.
Same is the issue in Galaxy S (GT-I9000) as well... I always see 13-15 background applications running... Although i am using Task Killer, but still these apps start running in background... I think it drains battery as well... Any idea how can we prevent starting the background apps ?
Thanks,
Guru
Baseband: DDJP2
Froyo DDJP6
Just because you "see" an app in atk or another task manager does not mean it is doing anything.
Use spare parts, system panel, power tutor.....anything that shows CPU/network usage and you will see what is happening rather than killing things off which turns into an endless cycle reminiscent of a game of whack-a-mole.
People seem to be going crazy thinking they have to clear and keep ram free. android does a good job of managing it for you. When apps are loaded in ram it is nota bad thing. It is not slowing your phone down or sucking your battery. If you are critically low on ram (less then 40mbs or so) then it is a problem. Would you pull a key off of your keyboard just because you are not using it? Its not hurting anything by being there
Sent from my SAMSUNG-SGH-I897 using XDA App

2 apps that I think is a must for any/all android devices

<gibberish>
Title says it all.
Yes, the gtab runs pretty darn well on a tegra duo core processor and 512 meg of memory. That said, since this device does well in multitask, nothing ever gets shut off when you press the home screen button.
Say you're watching youtube videos and then decide to play some games. So, you press the home button to "exit" out of youtube and then play your games. You then surf the net a bit, open up quickoffice to read some documents, etc.
Here's the thing. Everytime you press the home button, you're not shutting down the app. You're just going to your home screen. The apps are still running in the background. The more apps are running, the more resources your gtab will have to divert to those apps. I've been testing it, and the lag is definitely noticable after a while. All these apps that are piling up on top of one another will slow you gtab down considerably.
The two apps that I say are a must for every android device are the startup auditor and advance task killer. Use startup auditor to have control over what starts up. Your device will start up a lot faster. Use advance task killer to kill apps after you've used it. After all, what's the point of letting it run in the background when you're not using it? It's just wasting battery and processing resources.
</gibberish>
ATK is bad news. The Android OS DOES NOT need this invasive software. You'll have a lot more problems with it than without it. There are many, many developer-written articles which prove this. You really outta take that off any device you have it on.
Sent from my DROID2 GLOBAL using Tapatalk
deep_powder2012 said:
ATK is bad news. The Android OS DOES NOT need this invasive software. You'll have a lot more problems with it than without it. There are many, many developer-written articles which prove this. You really outta take that off any device you have it on.
Sent from my DROID2 GLOBAL using Tapatalk
Click to expand...
Click to collapse
After reading a few pages on this, I'm convinced. I'll edit the OP.
goodintentions said:
<gibberish>
Title says it all.
Yes, the gtab runs pretty darn well on a tegra duo core processor and 512 meg of memory. That said, since this device does well in multitask, nothing ever gets shut off when you press the home screen button.
Say you're watching youtube videos and then decide to play some games. So, you press the home button to "exit" out of youtube and then play your games. You then surf the net a bit, open up quickoffice to read some documents, etc.
Here's the thing. Everytime you press the home button, you're not shutting down the app. You're just going to your home screen. The apps are still running in the background. The more apps are running, the more resources your gtab will have to divert to those apps. I've been testing it, and the lag is definitely noticable after a while. All these apps that are piling up on top of one another will slow you gtab down considerably.
The two apps that I say are a must for every android device are the startup auditor and advance task killer. Use startup auditor to have control over what starts up. Your device will start up a lot faster. Use advance task killer to kill apps after you've used it. After all, what's the point of letting it run in the background when you're not using it? It's just wasting battery and processing resources.
</gibberish>
Click to expand...
Click to collapse
I get the point you are trying to make, even if the software you have recommended is not the best. I use aCCleaner to clear my cache and SuperBox (10 programs in 1) to free the memory it comes with quite a few other utilities. Installer/uninstaller, App2SD, cache, taskkiller which I seldom need or use, settings, file manager and safeguard which tells you the risk level of the programs or services running on G Tab. Efficiency is everything.
You know, in theory all these articles have grounding but I can say IMHO "every android device I have owned runs more responsive when I kill using a task manager. "
I can feel the difference in speed when I use my photo editing software and then jump online for some image searching. Taskillers may not be perfect, and I especially don't advocate using the constantly running autokill features, I have found greater responsiveness from my devices when using multiple high end softwares consecutively. Like I said JMHO.
Sent from my Chromatic Magic using XDA Premium App

Any way to limit 'recent apps' in list? Noobish Honeycomb question.

I guess this is my honeycomb ignorance (still getting used to the features) but when pulling up recent apps with the softkey I really only want apps that are currently running.
Are some of these apps are already "closed" and by choosing a thumbnail from the list I'm re-opening these?
Is there a setting anywhere to "limit" the history I see? Like <5 apps or something?
I have Task Killer pro intalled now to manage the real running apps but the Softkey is handier, if I can just be sure of what its supposed to indicate.
Thanks
Sent from my Transformer TF101 using XDA Premium App
I was wondering this as well. I haven't found any way to do it yet.
I don't know of any way except to manage apps in the settings and then kill "running" apps....but remember; these are apps "in memory" like you'd think in Windows.....they are not sucking resources...
I think that there is an article here somewhere about this list and why you shouldn't use an app killer in Honeycomb....
I'm more interested in changing it to a grid layout, like a speed dial.
yeah I know theyre not in memory but they are wasting screen space. I finished playing chess yesterday, I dont think the game should stay in the recent apps list. Froyo & Gingerbread are much better at managing this.
moo99 said:
yeah I know theyre not in memory but they are wasting screen space. I finished playing chess yesterday, I dont think the game should stay in the recent apps list. Froyo & Gingerbread are much better at managing this.
Click to expand...
Click to collapse
I agree. I just want a cleaner recent apps list. Sometimes it's hard to find what you're looking for.
I guess a workaround would be to longpress the home screen, put a widget there that is linked directly to "manage applications" and then it would only be one press and then zap the offending apps.
You do realize the Recent Apps button on the homescreen is just that, a Recent Apps button. It's not exactly a "running in the background" button.
"I finished playing chess yesterday, I dont think the game should stay in the recent apps list."
Why not? It is a recently played app isn't it? LOL.
And yeah, agree with the other reply, if you want a list of running apps.... don't touch the Recent Apps list button lol.
Stop worrying about what's running in the background. Just enjoy the damn Android.
Im not near my TF now but I use Multitasking Pro on my Galaxy S for that. you can choose to open it by double clicking the home button and see only running apps or recent apps - its configurable in the application settings. i does cost about 2$ i think but it was the best 2$ I've spent
this is called a 'Recent apps' list for a reason...it's 'Recent'..not current running...
Well you could always downgrade to 3.0 if it really bothers you. That only showed 5 apps!
LOL. Its a nuisance, not so much a grievance; but I'm glad I'm not the only one annoyed, perhaps this will get looked at ;-)
Possibly once Honeycomb is more prevalent there will come market apps or enough reportage to have an updte with a setting for it, or a utility that tweaks it. Regardless, I appreciate the feedback. At least now I know its sort of "normal".
Sent from my Transformer TF101 using XDA Premium App
My number one wish is for Google to improve multitasking (and give back control to the user as to which programs are running).
As is, the implementation just isn't very usable if you consider it to be a multitasking device -- it's really closer to single-tasking with a memory of what it did recently and the ability to reopen with a similar state to what it last had.
For example, I use my tab during F1 races for timing and scoring. I have F1.com's timing and scoring app, and I have access to a (non-public) website which provides further real-time info through Adobe Flash in a web browser.
If I switch from the web browser to F1.com's timing and scoring app for more than say 10-15 seconds, then back again, the flash app has to reconnect to the server because the web browser ceased running, even though the browser and the F1.com app were the only programs running and had ample memory / CPU power / a mains power supply connected, ie. no reason to halt the browser.
This isn't the only time I hit this issue, it's just one easy-to-explain example.
I'd much rather I had the ability to exit programs / apps myself when I'm done with them, and to keep programs / apps running in the background when I want them to. It'd make the whole experience much more coherent and logical.
The Flash plugin was designed to suspend when you switched apps. It's not an android issue.
Adding "close programs" to the current implementation would not make it more logical, it would make it more convoluted. It doesn't need it.
knoxploration said:
.I'd much rather I had the ability to exit programs / apps myself when I'm done with them, and to keep programs / apps running in the background when I want them to. It'd make the whole experience much more coherent and logical.
Click to expand...
Click to collapse
The problem is that the vast majority of users won't want to handle this themselves, and would expect the OS to do if for them.
Personally, I'm in favour of having some sort of mechanism whereby you can tell the OS not to kill specific tasks if you so choose, but otherwise task management performs as is.
With specific regard to your example, I think that the OS believes it is always OK to kill the browser, which is why it can be killed so quickly after switching away. For other apps, this doesn't seem to happen - for example, yesterday I was connected to a remote server using Wyse PocketCloud, and I frequently switched away to do something else for 30-60 minutes at a time, yet my remote desktop connection was never dropped or killed.
Regards,
Dave
Me personally don't need and don't like this "recent" app button. Or I need it to have an option either to clear it or not. You know we sometimes need privacy over such things
JCopernicus said:
The Flash plugin was designed to suspend when you switched apps. It's not an android issue.
Adding "close programs" to the current implementation would not make it more logical, it would make it more convoluted. It doesn't need it.
Click to expand...
Click to collapse
Agreed, if flash is left to run in the background it will drain the battery like hell..and other system resources as well.
Sent from my Transformer TF101 using XDA Premium App
...and it should be *my* choice whether that happens. That is where this argument totaly falls on its face. *I* know whether it is vital to me that an app remain open, or can safely be closed. The tablet doesn't.
As long as it remains in the tablet's hands, it will continue to annoy me by leving open apps that I no longer need running, while closing apps that I strongly do need running.
magicpork said:
Agreed, if flash is left to run in the background it will drain the battery like hell..and other system resources as well.
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
that's just it....it doesn't.
Revisiting Android Task Killers and Why You Still Don’t Need One
from another forum.
We almost hate to approach the topic of Task Killers on Android after all this time, but with so many new faces here at Droid Life and in Android in general, it’s something that needs to be done. In fact, after seeing the Amazon app of the day and reading through the Twitter conversations we just had with many of you, this thing needs to be posted immediately.
Let’s see if we can’t get you all some better battery life!
First off, please ignore the image up at the top of the post. If this was 2009 and we were all running something less than Android 2.2, that statement plastered on that red banner might be somewhat correct. But since it is 2011 and the majority of people on the planet are running Android 2.2, we need to get you away from the mindset that killing off tasks on your phone is a good thing.
So rather than me blabbering about the inner-workings of Android and how it manages RAM for the 10,000th time, I’m going to just pull from some posts that friends of ours have done that explain this in the plainest of ways.
First up is our boy @cvpcs who you may know from CM and his Sapphire ROM days. He knows Android inside-and-out, so when he goes into memory management which is done by the OS itself, you should listen up:
…What people don’t seem to realize is that android is designed to have a large number of tasks stored in memory at all times. Why? Well basically we are talking about a mobile device. On a mobile device things tend to be slower. The hardware isn’t as robust as say a desktop or a laptop, so in order to get that same “snappy” feeling, there have to be workarounds.
One of these is how android deals with memory. Android will load up your apps and then keep them running until they absolutely HAVE to kill them. This is because that way, if you want to re-open an app, the system already has it loaded and can then just resume it instead of reloading it. This provides a significant performance increase.
What a lot of people don’t realize as well is that android kernels have their own task manager. This means that:
it will be more efficient than any app-based task manager as it is run at the kernel level, and
it should be left up to that task killer to decide when to free up memory
There is only one case where having a task killer is a good idea, and that is when you want to kill ONE SPECIFIC APP. Killing all apps is never a good idea. You don’t know what operations they are performing or if they are necessary.
Whitson Gordon of Lifehacker suggests that you should be more worried about CPU usage than what’s going on with your RAM. We agree:
This set-up implies that the goal of killing these apps is to free up memory. Nowhere on the list does it mention the number of CPU cycles each app is consuming, only the memory you’ll free by killing it. As we’ve learned, full memory is not a bad thing—we want to watch out for the CPU, the resource that actually slows down your phone and drains your battery life.
Thus, killing all but the essential apps (or telling Android to kill apps more aggressively with the “autokill” feature) is generally unnecessary. Furthermore, it’s actually possible that this will worsen your phone’s performance and battery life. Whether you’re manually killing apps all the time or telling the task killer to aggressively remove apps from your memory, you’re actually using CPU cycles when you otherwise wouldn’t—killing apps that aren’t doing anything in the first place.
In fact, some of the processes related to those apps will actually start right back up, further draining your CPU. If they don’t, killing those processes can cause other sorts of problems—alarms don’t go off, you don’t receive text messages, or other related apps may force close without warning. All in all, you’re usually better off letting your phone work as intended—especially if you’re more of a casual user. In these instances, a task killer causes more problems than it solves.
More on how Android has a built-in memory-management system, but also on how killing all tasks is not a good thing (via: NextApp):
Android was designed from the ground up as an operating system (OS) for mobile devices. Its built-in application and memory-management systems were engineered with battery life as one of the most critical concerns.
The Android OS does not work like a desktop operating system. On a desktop OS, like Windows, Mac OS X, or Ubuntu Linux, the user is responsible for closing programs in order to keep a reasonable amount of memory available. On Android, this is not the case. The OS itself automatically removes programs from memory as memory is needed. The OS may also preload applications into memory which it thinks might soon be needed.
Having lots of available empty memory is not a good thing. It takes the same amount of power to hold “nothing” in memory as it does to hold actual data. So, like every other operating system in use today, Android does its best to keep as much important/likely-to-be-used information in memory as possible.
As such, using the task manager feature of SystemPanel to constantly clear memory by killing all apps is strongly NOT RECOMMENDED. This also applies to any other task killer / management program. Generally speaking, you should only “End” applications if you see one which is not working correctly. The “End All” feature can be used if your phone/device is performing poorly and you are uncertain of the cause.
And we could go on for hours with source after source on why task killers do nothing but work against Android, but you probably get the point now don’t you? Ready for a quick recap? OK.
Basically, Android keeps tasks handy because it thinks you’ll want to perform them again in a very short amount of time. If you don’t, it will clear them out for you. It also likes to keep as many things handy as possible so that the overall performance of your device is top notch. If Android were to completely kill off everything that your phone is doing, then it would require more resources to restart all of them and you would likely run into slowness and battery drains. By keeping certain things available to you, your phone is actually running better than it would without. So please, stop killing off tasks and let Android do the work for you.
Your goal for the week is wash your brain of the idea that having little RAM available is a bad thing. The more RAM available, the more Android will find ways to use it up which means your battery will be dead in hours. Instead, let it manage itself, so that you can spend more time playing Angry Birds or reading Droid Life.
All good now?
A simple reboot clears the list of recent apps. And as others have stated, it's not about running apps but something like the "recent documents" list in Windows 7

Task killer vs no task killer?

I use a task killer so im curious why some people say not to use them. What are your opinions?
Sent from my Inspire 4G using xda premium
I personally use them and havent come across suggestions not to, as long as u know what you are "killing" and its not a system process , it should be ok and yes it does free up RAM
I dont use any task killer and Im happy
I personaly would have a task killer one that kills all when idle. and frees up ram due to the fact i like to do cpu hungry tasks often
Ystrem said:
I dont use any task killer and Im happy
Click to expand...
Click to collapse
Same here, kill the task, and then feed the task killer the battery power saved.
I have tried them and found most of them didn't help much.
cnavi said:
Same here, kill the task, and then feed the task killer the battery power saved.
I have tried them and found most of them didn't help much.
Click to expand...
Click to collapse
Same here.
I don't use any of them.I used before but i don't saw too much help.Just task killer use cpu more and load ram.I use now just a shortcut of standard runing services default from android.
Don't use task Killers. Android has its own built in task manager Which works far better than 3rd party task killers. All you doing is making android reload everything again. Then you wonder why this app doesn't update in the background or work properly it is your fault. Your killing off the processes. Ram is essentially useless in android if it's not being used.
If you have lets say most phones have 512-1gig of ram. Your phone will never say you have 512 ram full please free up ram. It gets to a certain memory limit like depending on what it was set to and then end the processes automatically by itself. If there are many processes running android will start swapping out processes to replace for the new one. When your playing a game and say oh i want to browse the web to check on some game codes or whatever you can go right back to the game.
What if you want to listen to your own music as well. You can then go right back to the game in the exact spot left off. But if you go I'm kill the game process off you won't be able to do that. Don't press that Clear ram in that task manager you have either. All process will be killed including google services. Which will be reloaded again as well as system processes. Everytime android needs to reload its using more power meaning worst battery life.
The only time you should use a task manager is when there is a rogue application or a memory leak.
Watchdog
I don't use a Task Killer, but I do like Watchdog. It's more of a system monitor and lets me know if any background apps jump over a particular CPU usage threshold.
---------- Post added at 02:02 PM ---------- Previous post was at 01:55 PM ----------
There is a free, Lite version if you want to give it a try. Amazon had the pay version as their free app o' the day a while back, and I jumped on it.
market.android.com/details?id=com.zomut.watchdoglite&hl=en
I use to use taskkiller but my phone seems to run the same with or without, so I got rid of it.
exileinoblivion7 said:
I use a task killer so im curious why some people say not to use them. What are your opinions?
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
i dont like task killers, if your really desperate for ram and use android, i recommend using the v6 supercharger script made by zeppelinrox. ofcourse the thread can be found here in xda. Iwouldnt recommend task killers for several reasons:
1 they take some ram space themselves
2 they use some cpu thus making ur phone slower
3 they use some cpu thus draining your battery faster
4 they make your boot time on your phone longer because they are being loaded whereas scripts dont have that issue
5 i havent actually seen any propper task manager that has like autokill option and woks properly so you constantly have to press the end tasks button (like on system panel for example) and thats quite boring if your doing it all the time... scripts dont have that issue
Killbynature said:
Don't use task Killers. Android has its own built in task manager Which works far better than 3rd party task killers. All you doing is making android reload everything again. Then you wonder why this app doesn't update in the background or work properly it is your fault. Your killing off the processes. Ram is essentially useless in android if it's not being used.
If you have lets say most phones have 512-1gig of ram. Your phone will never say you have 512 ram full please free up ram. It gets to a certain memory limit like depending on what it was set to and then end the processes automatically by itself. If there are many processes running android will start swapping out processes to replace for the new one. When your playing a game and say oh i want to browse the web to check on some game codes or whatever you can go right back to the game.
The only time you should use a task manager is when there is a rogue application or a memory leak.
Click to expand...
Click to collapse
Great job explaining this man, I've been aware that killing apps just makes them restart. I really only kill apps if they are acting a fool.
And to clear things up I don't have a task killer installed, however I do use the one built into the go launcher app drawer to kill apps that go nuts.
I have used the v6 script before, however I recently downloaded Rom toolbox and it let's you adjust minfrees from there. You guys should check it out
Sent from my Inspire 4G using xda premium
I don't use a task killer. My phone burns less than 1% of battery per hour when idle.
Nexus One on Cyanogenmod 7.1
exileinoblivion7 said:
I have used the v6 script before, however I recently downloaded Rom toolbox and it let's you adjust minfrees from there. You guys should check it out
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
i have a low end phone, as i ran out of cash after buying myself headphones and an itouch, so i couldnt get the phone of my dreams and had to settle for a really cheap samsung galaxy 3 so i dont have a very wide choice of minfrees i can choose from... i got like 256 ram or something, and i dont use swap because i hate partitioning my sdcard...
im so definitly changing my phone in 2012, im either waiting for the nozumi to come out (huge sony ericsson fan ^_^) or im settling for the HTC gigabeats
Task killers are good when you see a rogue app that is draining a ton of your battery life but aren't good when you use the "Kill All" button. As long as their are poorly developed applications, there will be a use for task killers.
some people will tell you not to use task killers because it inhbits Android's normal functioning by interfering with RAm use, causes things to go wrong, running apps don't use battery, blah blah blah. but there are a few problems with these claims.
First, Android's RAM management is not flawless. no Operating system is. fanboys keep claiming it is yet offer no support for whether a 3rd party task killer is better or worse. in fact, they were all claiming this when Froyo was the latest. but then when Gingerbread came out, one of its new features was better RAM management, which fanboys around the internet praised it for, which means there had, in fact, been room for improvement, which they had been denying for quite some time.
second. there are around 500,000 apps on the market. some are flawed, causing RAM leaks and various other malfunctions that ANdroid can't always handle. a task killer is your best, and sometimes only option in this situation, as you might not reasonably have the option of deleting the app permanently.
third, battery life. it may be true that apps simply being running in the background alone doesn't use battery; I'm not sure. yet what fanboys routinely ignore is, many of these apps don't just sit there waiting to be turned on again. some of them turn on so as to collect user data about all sorts of things, then broadcast it to the developer for various uses. this broadcasting uses your phone's radio even when in the background, and that DOES use electricity - from your battery, not to mention data if you have a limited plan. a very large amount of apps do this, which is one major reason why ICS now includes a data management menu that monitors all apps' data usage, as well as a built in app freezer that stops apps from running until you allow them to again.
I use the one that comes stock, and alathough it frees up ram I dont notice any difference in battery drain (1% per hour) or any difference in performance
Falkner09 said:
some people will tell you not to use task killers because it inhbits Android's normal functioning by interfering with RAm use, causes things to go wrong, running apps don't use battery, blah blah blah. but there are a few problems with these claims.
First, Android's RAM management is not flawless. no Operating system is. fanboys keep claiming it is yet offer no support for whether a 3rd party task killer is better or worse. in fact, they were all claiming this when Froyo was the latest. but then when Gingerbread came out, one of its new features was better RAM management, which fanboys around the internet praised it for, which means there had, in fact, been room for improvement, which they had been denying for quite some time.
second. there are around 500,000 apps on the market. some are flawed, causing RAM leaks and various other malfunctions that ANdroid can't always handle. a task killer is your best, and sometimes only option in this situation, as you might not reasonably have the option of deleting the app permanently.
third, battery life. it may be true that apps simply being running in the background alone doesn't use battery; I'm not sure. yet what fanboys routinely ignore is, many of these apps don't just sit there waiting to be turned on again. some of them turn on so as to collect user data about all sorts of things, then broadcast it to the developer for various uses. this broadcasting uses your phone's radio even when in the background, and that DOES use electricity - from your battery, not to mention data if you have a limited plan. a very large amount of apps do this, which is one major reason why ICS now includes a data management menu that monitors all apps' data usage, as well as a built in app freezer that stops apps from running until you allow them to again.
Click to expand...
Click to collapse
Could you please explain what third party task killers do that the Android system manager doesnt do natively?
johnston9234 said:
Could you please explain what third party task killers do that the Android system manager doesnt do natively?
Click to expand...
Click to collapse
From my personal experience it doesn't kill some rogue apps that drain my phone's battery life. Occasionally I use the app "GPS Status" to help find my location faster and if I don't immediately kill the app after my location is locked, the app shoots up to 30-40% on Battery Status.
johnston9234 said:
Could you please explain what third party task killers do that the Android system manager doesnt do natively?
Click to expand...
Click to collapse
work responsively, to start with. every time i've tried to open the application manager on android, I first have to go through all the sub menus to get to it, then sit and wait for it to slooooooooooowly load up the list on installed apps, then running apps, then click on the app, then wait for it to load that particular app's info, THEN I can force close it.
two, they often catch apps running that the default manager doesn't notice, I presume because their developers code them to be hidden somehow.
so yeah, they're occasionally a valid option to use.
I'm happy with or without task killer )
Sent from my GT-S5830 using xda premium

Categories

Resources