New to Android - Back Button question - Streak 5 Themes and Apps

In the dell streak - when i use the back button does it close the application or keep it running in the background?
Is there anything similar to HTC Task manager we used in WM which would close the apps after using? Is this possible at all?
I also heard that using task managers generally cause issues with battery, speed etc?
Carify anyone?

devdarshan said:
In the dell streak - when i use the back button does it close the application or keep it running in the background?
Is there anything similar to HTC Task manager we used in WM which would close the apps after using? Is this possible at all?
I also heard that using task managers generally cause issues with battery, speed etc?
Carify anyone?
Click to expand...
Click to collapse
As far as my limtied knowledge goes.
Using the back button does close the apps, unlike hitting the 'home' button which leaves them open in the background.
I don't use a task manager myself and have never had any issues, but I have read (numerous times) that task managers are not required due to the unique way that android controls it's resources.
Thereforeyou can't compare it to other operating systems.
HTH.

Don't worry about task manangers, when I first got my streak I used one until I stopped recieving texts and calls and deleted it. I see absolutely no difference between when I used it and now that I don't, the phone is very smooth either way!

devdarshan said:
In the dell streak - when i use the back button does it close the application or keep it running in the background?
Is there anything similar to HTC Task manager we used in WM which would close the apps after using? Is this possible at all?
I also heard that using task managers generally cause issues with battery, speed etc?
Carify anyone?
Click to expand...
Click to collapse
The Back button will exit the app (unless the app is coded so it does something different) but the app's process will remain running.
The home button will usually suspend the app as it is so you'll be at the same point when you re-open it (again, unless the app has the home button coded to do something different).
The only way to fully close an app is with a task manager but it's completely pointless having one.
Android works by keeping everything running in the background and when it needs memory it will close the ones it thinks are least important.
It does this because it makes things a hell of a lot faster. A good example, is that when you first load the Gallery app, it has to load all your pictures and videos. Once it's done that, it will then be able to open it again very quickly with everything loaded, unless you kill it with a task manager, then it will have to load everything again. Task managers also have a habit of closing necessary things, resulting in a loss of signal, connectivity, etc.
So, in short, don't bother with a task manager. Android has one built in, which is much more effective.

Related

Exit running apps

hi i have only just got the hero and was wondering how to close apps properly. i have noticed that when you hold the home key for a while a window pops up showing some apps ...is this how you close them? or is simply pressing the home key shutting them .
The long press on home just brings up a list of apps that have been recently run. It's almost a task switcher, but not quite!
Many apps will exit if you "back" out of them - i.e. when in the app keep pressing back until you get back to the home screen. However, this isn't the case for all applications. Some may have an explicit exit or close button, whereas others may have nothing at all.
However, Android is pretty good at managing its own applications, and will kill/exit them as necessary. In my experience, there's little to be gained from explicitly killing applications using a task killer, but some people swear by it.
Regards,
Dave
foxmeister said:
The long press on home just brings up a list of apps that have been recently run. It's almost a task switcher, but not quite!
Many apps will exit if you "back" out of them - i.e. when in the app keep pressing back until you get back to the home screen. However, this isn't the case for all applications. Some may have an explicit exit or close button, whereas others may have nothing at all.
However, Android is pretty good at managing its own applications, and will kill/exit them as necessary. In my experience, there's little to be gained from explicitly killing applications using a task killer, but some people swear by it.
Regards,
Dave
Click to expand...
Click to collapse
Most Task Killers free up memory thats used by background apps.
so basicly back out of the app and let android do the rest of the worring. thanks for advise
risterdid said:
Most Task Killers free up memory thats used by background apps.
Click to expand...
Click to collapse
Yes, but the point is that Android itself will start killing applications if it starts to run low on resources. (see http://developer.android.com/guide/topics/fundamentals.html)
Regards,
Dave
I'll attempt to sum it up once and for all, to try and set the record straight.
In Android's virtual machine, there is no functional differentiation between "closing" an app and "switching away from" an app. They are the same (the exception is things like music players which need to keep playing after you switch away from them, but even then only the 'service' part needs to keep running).
Whenever you switch away from an app, its current state is remembered so that even if it is effectively "killed" it can be returned to in just that state next time it's opened. Then Android either kills the process or it keeps it open, killing it when it needs the memory. You won't notice any difference between either scenario, except maybe that an app loads a little bit faster if it was kept in memory. At any rate, "closed" apps do not "run", and they do not take RAM or CPU cycles from other apps.
In terms of process/memory management, Android's VM has more in common with a web browser than a desktop OS - sure it can remember your state when you switch apps (like switching tabs, going back/forward/home in a browser) but whether behind the scenes it loads it all into and out of memory when you switch back and forth, or it all stays in memory is irrelevant to the user. Nobody worries that a long forum page on another tab or in their back button history is occupying 80 megs in the background or not, the browser takes care of loading/unloading it from RAM as needed, and that's just like how Android's VM works when switching between various pages of various apps.
Once you understand this you understand that all these 'task killer' apps are really unnecessary - all they'll do is make it slower to restart an app once closed. They don't reclaim RAM that was previously unavailable to other apps.
To cut a long story short, pressing "home" is a great way to close an app, whether you want to return to it later or not.
MercuryStar said:
Nobody worries that a long forum page on another tab or in their back button history is occupying 80 megs in the background or not, the browser takes care of loading/unloading it from RAM as needed, and that's just like how Android's VM works when switching between various pages of various apps.
Click to expand...
Click to collapse
that is not true for me, my firefox can eat a lot of resources as long as it is open. and i can see a performance difference when having a lot of apps open on my hero. not that it would be a problem, but you can see the menus scrolling more "fluid" after killing all bg apps, for example.
kendong2 said:
you can see the menus scrolling more "fluid" after killing all bg apps, for example.
Click to expand...
Click to collapse
I would wager that's the placebo effect. It feels faster because you believe it should. If you understand how the OS works you realise that apps you've switched away from do nothing to slow down or take memory from any other app (see my exception above about apps that launch background services such as music player).
kendong2 said:
that is not true for me, my firefox can eat a lot of resources as long as it is open. and i can see a performance difference when having a lot of apps open on my hero. not that it would be a problem, but you can see the menus scrolling more "fluid" after killing all bg apps, for example.
Click to expand...
Click to collapse
I do notice this too. There is a general 'sluggishness' with my Hero when there are lots of app sleeping/running/hibernating/whatever in the background. As soon as I kill off a few unwanted ones, all the menus scroll faster and home screens change quicker.
And this is not the placebo effect either. The menu's DO scroll more fluidly after I have killed a few apps, regardless of how you describe the RAM management...
Micksta said:
And this is not the placebo effect either. The menu's DO scroll more fluidly after I have killed a few apps, regardless of how you describe the RAM management...
Click to expand...
Click to collapse
exactly, you can tell easily if it is one motion or looks like it is "skipping frames". even it is only because it takes the device some cpu cycles to kill other apps, it does make a difference. like i said a rather cosmetic one, since it doesn't really effect the general usage. nevertheless i like to know what is running and what's not, and so far im running good with advanced task manager free.
WOW i didnt expect a massive response for my question but i thank you all for your responses
MercuryStar said:
I would wager that's the placebo effect. It feels faster because you believe it should. If you understand how the OS works you realise that apps you've switched away from do nothing to slow down or take memory from any other app (see my exception above about apps that launch background services such as music player).
Click to expand...
Click to collapse
that's not true, my phone gets so sluggish sometimes that i can't answer a phone call, the phone doesn't register that i press the answer button. and when that happends i usually have like 20 mb of free ram.
Daniehabazin said:
that's not true, my phone gets so sluggish sometimes that i can't answer a phone call, the phone doesn't register that i press the answer button. and when that happends i usually have like 20 mb of free ram.
Click to expand...
Click to collapse
Just as a matter of interest, do you use swapper or AppsToSD?
My phone never gets into the situation you've described, but even though I do have the full version of TasKiller, I almost never use it, and I don't see a need at present to use AppsToSD.
In addition, I'd imagine that having a swap partition would cause an issue with Androids own memory management, since I guess it can't distinguish between real and "virtual" memory. So where a "non-swap" device would start killing processes, a "swap" device would just continue on regardless because it thinks it still has physical memory available.
Regards,
Dave
Yesterday I downloaded "Advanced Task Killer Free"... anyone who has experiences with this? Is is better than just "Task Killer" or is it just an updated version of "Task Killer" ?
thanks!
have been using atk free for a while (lol 2 weeks since i got the hero) now, i really like it. its advantage over all other task managers IMHO: it has an ignore list, things you ignore are not shown in the running tasks list. in the list you have check boxes, where you can select the tasks that will be killed, and this list is remembered. for example "htc sense" is on my ignore list, but "music" is only checked, so i can uncheck it when i don't want to kill it while listening to music. next time i want to kill music i just have to tap the checkbox, no dealing with the ignore list here...
Daniehabazin said:
that's not true, my phone gets so sluggish sometimes that i can't answer a phone call, the phone doesn't register that i press the answer button. and when that happends i usually have like 20 mb of free ram.
Click to expand...
Click to collapse
I get this problem a lot, and in answer to fox meister, I don't have AppsToSD.
I don't know if the problem is RAM or CPU related, but the CPU often jumps to 100% when things are really slow.
Is the issue likely to be background apps, or widgets even?
Sausageman said:
I get this problem a lot, and in answer to fox meister, I don't have AppsToSD.
I don't know if the problem is RAM or CPU related, but the CPU often jumps to 100% when things are really slow.
Is the issue likely to be background apps, or widgets even?
Click to expand...
Click to collapse
Same for me with the processor.
When i reboot my phone i usually have 90 mb of free ram, after starting a few applications, like browser and phonebook, it plummets down to 20 mb.
I do have some extra applications that starts as services, like systray monitor and 3g watchdog.
when i open atk after a fresh reboot i see that some applications that i don't even use is started, like footprints, settings and calendar, even my webrowser is started, whats up with that, can it be disabled?
I think the issue is that we have some applications that autostart withous us using them, and also programs that we download that autostarts as services and maybe having memory leaks...
I came to chime in with my experiences of the CDMA hero and sluggishness.
I watch memory like a hawk (thanks Mogul) and I too have around 80-90mb free ram on start, but it can get down to around 30 rather quickly. Once it gets down here, I notice that screen transitions and random lag occurs in apps. If I go into Advanced Task Killer and kill many of the stragglers, my menus are as smooth as can be.
It is most certainly NOT a placebo effect.
One thing I really like about Advanced Task Killer (pay version) is that it has the "Auto End" feature, where it will kill all apps not chosen to be excluded at the interval that you choose. For example, I have determined the system applications that need to be on all the time, and I've excluded those. Every hour, ATK kills everything else. For the most part, my Hero hovers around 70MB now at all times, although it can get down there to around 30-40MB if I'm right around the 1 hour mark.
That feature alone makes it much better than Taskiller IMO. Totally worth 99 cents
This definition would imply that android works exactly like the iphone osx? I mean saving "screenshots" of the last state of an app. But NOT having real multitasking?
Because it's not possible to have multitasking and at the same time "inactive" background apps everytime you hit the home button...
MercuryStar said:
I'll attempt to sum it up once and for all, to try and set the record straight.
In Android's virtual machine, there is no functional differentiation between "closing" an app and "switching away from" an app. They are the same (the exception is things like music players which need to keep playing after you switch away from them, but even then only the 'service' part needs to keep running).
Whenever you switch away from an app, its current state is remembered so that even if it is effectively "killed" it can be returned to in just that state next time it's opened. Then Android either kills the process or it keeps it open, killing it when it needs the memory. You won't notice any difference between either scenario, except maybe that an app loads a little bit faster if it was kept in memory. At any rate, "closed" apps do not "run", and they do not take RAM or CPU cycles from other apps.
In terms of process/memory management, Android's VM has more in common with a web browser than a desktop OS - sure it can remember your state when you switch apps (like switching tabs, going back/forward/home in a browser) but whether behind the scenes it loads it all into and out of memory when you switch back and forth, or it all stays in memory is irrelevant to the user. Nobody worries that a long forum page on another tab or in their back button history is occupying 80 megs in the background or not, the browser takes care of loading/unloading it from RAM as needed, and that's just like how Android's VM works when switching between various pages of various apps.
Once you understand this you understand that all these 'task killer' apps are really unnecessary - all they'll do is make it slower to restart an app once closed. They don't reclaim RAM that was previously unavailable to other apps.
To cut a long story short, pressing "home" is a great way to close an app, whether you want to return to it later or not.
Click to expand...
Click to collapse
Shahpur.Azizpour said:
This definition would imply that android works exactly like the iphone osx? I mean saving "screenshots" of the last state of an app. But NOT having real multitasking?
Because it's not possible to have multitasking and at the same time "inactive" background apps everytime you hit the home button...
Click to expand...
Click to collapse
No, you've not understood the explanation.
The iPhone will always* terminate an application that isn't on its list of "approved" multi-tasking apps once it isn't active any more (i.e. you've switched tasks).
Android will try to keep whatever it can in memory, but eventually will start killing processes in order to keep the system running.
So, if you're on an iPhone listening to something on Spotify and you want to browse something on the web, the iPhone will "kill" Spotify when you switch to the web browser. On Android this won't occur except in the most critical of resource low situations, but then again, I'd imagine other apps would get killed before Spotify.
Read this article, specifically the section from "Component Lifecycles" onwards specifically "Activity Lifecycle", "Saving activity state" and "Processes and lifecycles".
Regards,
Dave
* Unless it has been jailbroken!

Closing Apps vs Running In Background

Hey Everyone,
Just got my Droid Eris yesterday and I'm having fun exploring the phone and checking everything out.
One question, I noticed that many apps (in fact, almost all) don't have a direct "Quit" or "Exit" command. So I'm usually pressing "back" or "home" when I'm done with something. This left me wondering though... when I use "back" or "home", does the app actually exit? From what I can tell, it doesn't... so does the OS automatically clean up these apps from time to time? I came from WinMo 6.1, and it was irritating that everything defaulted to running in the background. How does Android treat it? Is there something special in this regard with the HTC Sense UI? I've seen there are some third-party task manager apps you can get... are they worth getting? Or just "let the phone do it's thing" and i will be fine?
Thanks!
I use a Task Manager from the Market called "Taskiller." But I'm still trying to figure out how the Hero handles the apps because sometimes it gets sluggish and taskiller helps out but then theres other times when I have all sorts of apps open and it runs smoothly, lol, I guess it just works sometimes.
I wonder if it's like the iPhone, where it kills the task when you hit the "Home" button. It doesn't seem like it, as some apps seem to just come up instantly when go back in them, as if I was "switching" to them, and no re-opening them...
false_apology said:
I wonder if it's like the iPhone, where it kills the task when you hit the "Home" button. It doesn't seem like it, as some apps seem to just come up instantly when go back in them, as if I was "switching" to them, and no re-opening them...
Click to expand...
Click to collapse
No I dont think thats the case because Android has a special way of "Multitasking," though I'm not completely informed so you might have to research that on your own. But like I said download a Task Manager from the market so you can see how much available memory there is.
By default, Android applications never really "close" as their components can be called upon at any time. (Android applications are structured to be very modular, allowing individual components to be used from each.) When an application needs memory immediately, and another hasn't used it for a while, it shoves the old app into what's called swap space (presumably it's on your SD card) while the new one takes over. This is why you'll occasionally see a delay while performing a "hard" operation (like opening an app) while the system is under heavy load. That's the old app's memory getting written out to temporary storage and the other one taking it over.
At least this is my understanding of the situation.
From what I've heard Android (linux) does a much better job of managing the memory used by our apps. And, that we "...shouldn't have to use a task killer..." to close out apps that are running in the background, especially on our phones.
For instance, the myTouch 3G usually only gets about 20-30 MB of RAM freed after a full clean up of background apps, the Eris will have about 80+ MB after a cleanup and they both feel about the same to me.
I still use Task Panel to close my apps sometimes because I just like starting fresh in an app from time to time. Also if things start getting fishy (screen stuttering, touch screen not working properly) I'll kill all running apps to see if it fixes the problem which in some cases it just does not and a reboot is still required.
I have found that by holding the home key it will bring up all the apps so you can switch to the one that you want so it is still running them in the background.
refthemc said:
I use a Task Manager from the Market called "Taskiller." But I'm still trying to figure out how the Hero handles the apps because sometimes it gets sluggish and taskiller helps out but then theres other times when I have all sorts of apps open and it runs smoothly, lol, I guess it just works sometimes.
Click to expand...
Click to collapse
i use a Task application called Task Manager. It gives lists of all Applications running, all process and even has an uninstall feature. It also has a auto end application feature but on my eris it's greyed out(maybe Pro only?)
Here are a couple of links that I found on this subject. Don't mind that it says Hero in the thread title it talks about android phones in general. Also something to look into once we get the Eris rooted in the second link.
Task Managers and your Hero by romeosidvicious @androidforums.com
How to configure Android's *internal* taskkiller by androcheck @xda-developers.com

Do task killers make your Vibrant lag?

I installed a task killer and noticed that when killing certain apps, the phone just lags real bad. I discontinued use of it and now the phone has no serious pausing. I was killing unknown apps with Android box icons.
heygrl said:
I installed a task killer and noticed that when killing certain apps, the phone just lags real bad. I discontinued use of it and now the phone has no serious pausing. I was killing unknown apps with Android box icons.
Click to expand...
Click to collapse
yeah I uninstalled it as well. I heard Android does great job of managing ram and as soon as it gets low, it will start killing other apps automatically.
you need to learn what apps need to stay running, but some apps are just fluff and worthless... you may need to set up you task killer to ignore certain apps like handcent and clock... killing any android processes is usually a bad idea.. I just kill my 3rd party apps that open for no reason or use it to close apps when I am done using my phone for a while...
You should not need a task killer with this phone. Android has been managing its own memory and background services quite nicely for a while now.
SkOrPn said:
You should not need a task killer with this phone. Android has been managing its own memory and background services quite nicely for a while now.
Click to expand...
Click to collapse
Thats what i was told but when i uninstalled the task killer my phone lagged with everything i did. Even when closing programs properly it still lagged. Im keeping my task killer.
acjames said:
Thats what i was told but when i uninstalled the task killer my phone lagged with everything i did. Even when closing programs properly it still lagged. Im keeping my task killer.
Click to expand...
Click to collapse
yeah maybe its not as good as most people say it is at controlling its own memory usage.
Task Killers = meh,
Android has a way of doing things and that means keeping apps open for some time, I tried using app-killers and it did not seem to make my phones run better, and auto kill everything is even worse...
heygrl said:
I installed a task killer and noticed that when killing certain apps, the phone just lags real bad. I discontinued use of it and now the phone has no serious pausing. I was killing unknown apps with Android box icons.
Click to expand...
Click to collapse
idk if youre rooted or not, or if this app works on the vibrant cuz it does an amazing job on the g1, but you could try autokiller, tho it requires root. what it does is change the android memory management settings and will kill apps more frequently depending on the settings you choose.
speedysilwady said:
idk if youre rooted or not, or if this app works on the vibrant cuz it does an amazing job on the g1, but you could try autokiller, tho it requires root. what it does is change the android memory management settings and will kill apps more frequently depending on the settings you choose.
Click to expand...
Click to collapse
I still need to use it for those unruly apps but I got so used to it because my old phone would lag with Slacker even in the background and I had to kill it. I've stopped using it and I've stopped having major problems. Just an FYI for those out there that still use one, it's not needed here on a regular basis really.
I noticed that I can't use the "kill all" function in Advanced Task Manager by Arron La any more without making my phone freeze up. My brother suggestion Task Manager by Rhythm Software (he has a MyTouch Slide). This program doesn't give me any problems when killing files and also doesn't list system files (that I've noticed).
The people who are having problems with task killer are the ones that are not setting it up correctly or don't have enough apps installed for it to make any difference.
If you don't setup the ignore list correctly your phone will freak out or make your existing problem worse.
Android 2.2 is a different story though, Froyo is faster without a taskiller
Buddy here's what .....
Download AutoKiller from the market , then go to the dev's webpage ,there he has a lot of information about android and memory management .... then you can make an informed decision .... the lag issue you continue to have .,.,..., you might have to do a hard reset to clear the system of that poorly coded task/app killer ....
Here's some more information http://androidforums.com/samsung-vibrant/124542-constant-apps-restarting-themselves.html
I hope that here on xda we can help people to understand Android and memory management , so they are not fooled by these task/app killers that work against the system ......
heygrl said:
I still need to use it for those unruly apps but I got so used to it because my old phone would lag with Slacker even in the background and I had to kill it. I've stopped using it and I've stopped having major problems. Just an FYI for those out there that still use one, it's not needed here on a regular basis really.
Click to expand...
Click to collapse
I used to have the original my touch 3g, lag central, even on custom roms. Task killer was handy, so I got in the Babbitt if killing tasks. I then got me a nexus, and it seemed to have not needed one, but I still used it out of the Babbitt and being paranoid of my plbattery being wasted with apps on the background and lag lol. Well, I'm now done with them, seriously, no need for task killers. I think on this phone it does more damage then good, most apps need to be running on the background, killing them just lags your phone. Like you'd lose signal, or it would run time and date update again, etc.
Task killers may not be necessary for memory management, but it will help save on battery by killing 3rd party apps that stay running in the background. I use Advanced Task Manager myself, and never get any lag when I run it. The main thing you need to "exclude" if you havnt already, is the TWLauncher(or whatever launcher you're running).

[Q] There are Apps in the background

Dear Friends!
Glad to be here today (after 2 days! )
My dear Streaker is here!!
As the norm is, I have been busy tinkering with the stock material for couple o days, and I will continue to do so for some more time!
___________________________________________________________
Query: There are too many apps running (background) all the time!! I kill them, they resurrect!, How to do away with that?
Solution applied: Used Advanced task killer (but, apps resurrect!)
Another Solution tried: In Settings>Account & Sync settings> Unchecked Background data and Auto sync options. (Now, they dont connect to the net, but, they still restart!!)
Another Solution: Force close (from Manage apps) .. (Still same issue!)
Now, How can I tell the apps to come up only when I call them!?
(And some other apps I want to schedule them to come up every hour or so.. like my Gmail/FB)
____________________________________________________________
And, So far has been amazing experience!!
The screen is football field sized!! (Monster! yikes Scooby!)
Digging up all old posts to read some problems faced by new users..
Current hobby: Market and apps.
Future hobby: Roms and Flash!
Thank you all for your help!
care,
Sony.
Welcome to the cool kids club! I'm in a somewhat similar situation, I got my streak just before the massive snowstorm hit. Some of those apps need to be running... if you close some of them you may not get updates/notifications, or you can shut down your phone/data connection, or lose the use of multitouch.
Sent from my Dell Streak using XDA App
from what i understand, froyo is really good with resource management and there is no need to constantly kill processes or apps, its best to just leave them unless your streak is slow like a snail
Telal said:
Welcome to the cool kids club! I'm in a somewhat similar situation, I got my streak just before the massive snowstorm hit. Some of those apps need to be running... if you close some of them you may not get updates/notifications, or you can shut down your phone/data connection, or lose the use of multitouch.
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
Lose multi touch!
How?
@rptw
So, It wouldnt really matter if there are apps running in the BG, and they start by themselves too!?
care,
Sony.
well in terms of the laws of nature (in most cases) stuff doesnt happen spontaneously so i think its safe to assume that your app that "started by themselves" were probably opened somehow either by you directly or indirectly by something else. if, however, you have a large number of apps that have started that you dont recall opening, maybe something is wrong with your software and you shouldnt try to cover the problem with a task killer.
So, what next!?
rptw said:
well in terms of the laws of nature (in most cases) stuff doesnt happen spontaneously so i think its safe to assume that your app that "started by themselves" were probably opened somehow either by you directly or indirectly by something else. if, however, you have a large number of apps that have started that you dont recall opening, maybe something is wrong with your software and you shouldnt try to cover the problem with a task killer.
Click to expand...
Click to collapse
So, Now, can you or other guys here please suggest how to go to the "root" of this problem!?
Ok.
Look, these apps are open right now!
Voice Search
Email
Messaging
Maps
Astro
Assistant free​
I use the Adv Task Killer free.
(It says 7 apps killed and 180 MB free)
I open Adv task killer after 5 seconds.
and these apps are running!
Email
astro
Voice Search
Assistant Free​
and I am sure, If I wait for some more time, the other apps will join in too!
(Now it says, 3 Apps killed, 171 MB free!!)
care,
Sony.
have you tried using the stock app manager and killing the apps there? i just checked my phone and i have the same apps under the running tab using the stock manager, i think email and messaging are always running since you have push features on them, in terms of the others im not sure. whats so bad about email and messaging running anyways? im sure you use them often enough to not want to have to open and close them right?
Hey, you posted the same question over at Pocketables forum.
As stated earlier, 2.2 is really good at managing back ground tasks.
I can tell you if you use a task killer and you have a problem with an APP, which currently you do not, the programmer for the app probably will not help you till you remove the APP killer program.
What you might try to do is run though your menus and see what you have selected to run, such as locations and sync services and disable what you can. Also if you do not want some thing running, you may want to just uninstall it. I do understand that you want some programs but you only want them to run when you ask, not sure how to tell you to handle that.
But, are you seeing any difference when you have the background tasks disabled. Try to find the APK for the programs and rename them just to see if you have any issues.

Actual Task Manager That Works???

Is there a task manager that'll kill apps and permanently kill tasks processes? I've noticed that some will kill the task then the task will automatically start back up again...
Looking for the best that'll actually purge the memory and all that.
You should never use a task killer. Android manages memory on its own. Killing tasks will only lead to instability.
Tapatalked from Desire S running Andromadus
They say that but I've yet to ever see it happen! LMAO
I've seen "so called" task managers handle memory better than that this nonexistent invisible task manager android speaks of.
What are ya supposed to do when ya have 20 something app's running in the background, just leave them running and let this unknown task manager "supposedly" handle them...
How bout managing startup app's and what not? Furthermore if android has a built in task manager where is it and why isn't it working or why not make it better?
n1nj4Lo said:
They say that but I've yet to ever see it happen! LMAO
I've seen "so called" task managers handle memory better than that this nonexistent invisible task manager android speaks of.
What are ya supposed to do when ya have 20 something app's running in the background, just leave them running and let this unknown task manager "supposedly" handle them...
How bout managing startup app's and what not? Furthermore if android has a built in task manager where is it and why isn't it working or why not make it better?
Click to expand...
Click to collapse
I'd suggest a little more reading on the subject.
If there's something you really don't want running then freezing or removing it is a more efficient alternative than repeatedly killing it only for it to restart over and over.
Sent From My Fingers To Your Face.....
I use All-In-One Toolbox. Yes, I use a task manager, I have been using it since I got my LG Optimus One. I have been a developer for 9 years on both windows and linux platforms. It is true that linux manages memory better than windows, therefor Android benefits from this being build on the linux kernel. The fact remains, an app that doesn't run, doesn't use memory. Applications on android behave much like applications do on Windows Mobile, the don't exit but remain in memory in order to have quicker start up times. Unfortunately, killing an up does cause to restart, but I have noticed from personal experience that in that case, since the UI haven't shown yet, it uses less memory. I have no problem waiting for an app to start up, as long as while it runs, it runs smoothly. For that reason I disable many apps from start up that I don't need to run on a day to day basis but only when I need the app. AIO Toolbox handles all of that, task killer with whitelist, start up management, file manager, apk backup and restore and a slew of features I hardly ever use.
moving to Q&A section
conantroutman said:
I'd suggest a little more reading on the subject.
If there's something you really don't want running then freezing or removing it is a more efficient alternative than repeatedly killing it only for it to restart over and over.
Sent From My Fingers To Your Face.....
Click to expand...
Click to collapse
What are some good articles on the subject then?
cornelha said:
I use All-In-One Toolbox. Yes, I use a task manager, I have been using it since I got my LG Optimus One. I have been a developer for 9 years on both windows and linux platforms. It is true that linux manages memory better than windows, therefor Android benefits from this being build on the linux kernel. The fact remains, an app that doesn't run, doesn't use memory. Applications on android behave much like applications do on Windows Mobile, the don't exit but remain in memory in order to have quicker start up times. Unfortunately, killing an up does cause to restart, but I have noticed from personal experience that in that case, since the UI haven't shown yet, it uses less memory. I have no problem waiting for an app to start up, as long as while it runs, it runs smoothly. For that reason I disable many apps from start up that I don't need to run on a day to day basis but only when I need the app. AIO Toolbox handles all of that, task killer with whitelist, start up management, file manager, apk backup and restore and a slew of features I hardly ever use.
Click to expand...
Click to collapse
Yea I'm the same way when I used winmo I loved HTC CleanRAM, Pocket Mechanic and SKTools I really wish I could find a tool for android like SKTools, that was one powerful app. LoL
But I'm the same type of user you are it seems, right now it's at a toss up for me between Go Task Manager and ES Task Manager, but if anybody askes me for a good task manager to use I tell them ES Task Manager, cause it's startup list editor is a lot more newby user friendly telling ya whats safe to remove from the list and what isn't.

Categories

Resources