Related
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!
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
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.
I am new to Android - just got a Droid 3.
How do I stop the system from auto-killing a certain app? When I play Angry Birds, if the phone goes to sleep on timeout, when I turn it back on, the App has to re-load from scratch (rather than opening to where I left off last time). I'm assuming the system decided to kill it for lack of memory, but how do I STOP it from doing that (like an ignore list)?
Will I need a third party app?
Any help is appreciated!
not really. the Android system does a pretty good job of reclaiming unused memory. ive been dealing with this for a while trying to keep a replacement lock screen in memory
Sounds like Verizon installed a task killer. I know their employees do that saying you need one. But you don't. Make sure you uninstall it. It is most likely set to kill apps off ever x minutes. Usually Android keeps foreground apps in memory for a long time unless the system needs it. But doesn't sound like it would. I wonder what the Droid 3 memory settings are for stock now. I have the Evo 3D and they are set at a higher threshold(as I'm kills unused apps sooner) compared to my older HTC phones(Evo and Hero). How long do you let the phone sit idle before coming back?
Sent from my iPhone with the bigger GeeBees.
notasimpleway said:
Sounds like Verizon installed a task killer. I know their employees do that saying you need one. But you don't. Make sure you uninstall it. It is most likely set to kill apps off ever x minutes. Usually Android keeps foreground apps in memory for a long time unless the system needs it. But doesn't sound like it would. I wonder what the Droid 3 memory settings are for stock now. I have the Evo 3D and they are set at a higher threshold(as I'm kills unused apps sooner) compared to my older HTC phones(Evo and Hero). How long do you let the phone sit idle before coming back?
Sent from my iPhone with the bigger GeeBees.
Click to expand...
Click to collapse
It's not obvious which program that would be - there's nothing called Task Killer. Plus, most of the VZW bloatware can't be uninstalled anyway. Apart from rooting (locked bootloader on Droid 3), what can I do to force it to stay open?
Also, it gets killed immediately on turning off the phone. As in, I start the game, hit sleep, hit wake a second later and the game reloads from scratch. Very irritating.
Any thoughts are appreciated, thanks!
jbroses said:
It's not obvious which program that would be - there's nothing called Task Killer. Plus, most of the VZW bloatware can't be uninstalled anyway. Apart from rooting (locked bootloader on Droid 3), what can I do to force it to stay open?
Also, it gets killed immediately on turning off the phone. As in, I start the game, hit sleep, hit wake a second later and the game reloads from scratch. Very irritating.
Any thoughts are appreciated, thanks!
Click to expand...
Click to collapse
I just tested this with Angry Birds from the time I posted till just now and it was right where I left the game. It may be called Advanced Task Manager. Or something like that. And you should be able to uninstall it. It would have been installed by the person selling the phone and not at the factory.
Sent from my iPhone with the bigger GeeBees.
Go to the Market, download Spare Parts. Open and scroll down to Activity/Process Management. Select normal. It may not have been the problem, but worth a shot. Are you hitting the home button before putting the phone to sleep? What do you see immediately upon turning the screen on and unlocking the phone? Angry Birds? The home screen?
Sent from my iPhone with the bigger GeeBees.
When you haven't used an app for a long time, Android automatically recycles all open activities from the app, except the root activity.
By default, every application runs in its own Linux process. Android starts the process when any of the application’s code needs to be executed, and shuts down the process when it’s no longer needed and system resources are required by other applications.
[...]
If the user leaves a task for a long time, the system clears the task of all activities except the root activity. When the user returns to the task again, it’s as the user left it, except that only the initial activity is present. The idea is that, after a time, users will likely have abandoned what they were doing before and are returning to the task to begin something new
Click to expand...
Click to collapse
From geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/ (sorry I can't make a link yet)
Shinigami20 said:
When you haven't used an app for a long time, Android automatically recycles all open activities from the app, except the root activity.
From geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/ (sorry I can't make a link yet)
Click to expand...
Click to collapse
it actually happens instantly. in other words - open angry birds, begin level. sleep phone, wake phone. angry birds reloads from the beginning. this is all within the span of 5 secs.
i thought it might be my lock screen - widgetlock, but i disabled that and it just happened again, this time with opera mini as i was writing this. I was writing this post, went to a text, came back to opera within 30 secs and it had shut down and reopened (no tab with my partially composed message).
is the droid 3 just shutting things down more aggressively? is there a way to tweak that? maybe too much other crap is running and I should get a task killer? thoughts?
jbroses said:
it actually happens instantly. in other words - open angry birds, begin level. sleep phone, wake phone. angry birds reloads from the beginning. this is all within the span of 5 secs.
i thought it might be my lock screen - widgetlock, but i disabled that and it just happened again, this time with opera mini as i was writing this. I was writing this post, went to a text, came back to opera within 30 secs and it had shut down and reopened (no tab with my partially composed message).
is the droid 3 just shutting things down more aggressively? is there a way to tweak that? maybe too much other crap is running and I should get a task killer? thoughts?
Click to expand...
Click to collapse
do not sleep your device, try entering level then return to home switch to other apps. Then open angry bird again and see what happen
On my desire Z, it kill the app every time i sleep the phone. Keep the phone alive then I have 3 apps running at same time without being killed. But it's not likely that I have RAM shortage. 3 apps is constant no matter what apps
Flipz explains that well. Autokiller is a great little app to adjust those settings. Used it for over two years now. I actually got to watch that app evolve. Great dev. Only works if you are rooted.
Shinigami20 said:
When you haven't used an app for a long time, Android automatically recycles all open activities from the app, except the root activity.
From geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/ (sorry I can't make a link yet)
Click to expand...
Click to collapse
Sent from my iPhone with the bigger GeeBees.
Thanks for all the responses. I've tried to address them all:
Spare Parts - I installed this and set the Activity to Normal (it WAS set on aggressive). Unfortunately, this didn't help.
Press the Home key - Pressing the Home key and then going back to Angry Birds DOES work. It picks up right where you left off. Unfortunately, when the phone goes to sleep, it restarts Angry Birds on waking.
What do I see when I wake the phone - It goes to my WidgetLocker lock screen. Once unlocked, the very first thing that shows up is the Angry Birds "Rovio" loading screen. No home screen in between.
Any other thoughts are much appreciated! Is there any way to simply exempt Angry Birds from being closed by the system automatically? It seems like this should be possible!
Can you try something out for me? I want to give evidence to my theory.
Download another 3d game, load a level, then sleep the device. See if there's a lot of stuttering/reloading when you wake the device back up.
Any news on this? I got the same problem with CM 9.1 on my Doubleshot (aka M4GS). When I have like 10 tabs or so opened in Opera, Android kills the task. But not when I put it into sleep, but right when I'm browsing! That's really annoying since after restarting Opera I have to reopen every single tab manually from the history.
Already tried Spare Parts, but it doesn't offer some kinda whitelist for apps that shouldn't be autokilled.
It's really frustrating, Android's autokilling feature was one of the few things, that I didn't like about that OS when I switched from Windows Mobile to Android a few years ago. And I still hate that feature. Why can't I decide by myself which apps to be closed and which ones not? Give back the power to the user I say!
At least there HAS to be a solution to force Anddroid, not to kill a specified app (e.g. Opera) and kill all the other running apps instead. Any 3rd Party task killer has some kinda ignore list, so how could Android be tweaked to do the same?
Shani Ace said:
Any news on this? I got the same problem with CM 9.1 on my Doubleshot (aka M4GS). When I have like 10 tabs or so opened in Opera, Android kills the task. But not when I put it into sleep, but right when I'm browsing! That's really annoying since after restarting Opera I have to reopen every single tab manually from the history.
Already tried Spare Parts, but it doesn't offer some kinda whitelist for apps that shouldn't be autokilled.
It's really frustrating, Android's autokilling feature was one of the few things, that I didn't like about that OS when I switched from Windows Mobile to Android a few years ago. And I still hate that feature. Why can't I decide by myself which apps to be closed and which ones not? Give back the power to the user I say!
At least there HAS to be a solution to force Anddroid, not to kill a specified app (e.g. Opera) and kill all the other running apps instead. Any 3rd Party task killer has some kinda ignore list, so how could Android be tweaked to do the same?
Click to expand...
Click to collapse
I agree. I was downloading a file in Opera, switched to other apps, then went back to opera and it reopened.. Needless to say the download failed. This really sucks.
Use titanium and freeze the stock task manager (if any).
Android, by default, keeps only 3 (correct me if I'm wrong) applications' sessions in memory, but that's obviously no reason for it to kill angry birds right after the display is closed.
Try installing Minfree (I think it's available on the Play Store) to understand when and why Android is killing the application. It'll give you the parameters on which the Android Auto killer operates, but you will need ROOT to be able to edit them.
And no, there isn't a way to earmark an application such that it isn't killed, at least, not that I know of.
Hope this helps.
Haters gonna hate
potatoes gonna potate.
Check out v6 supercharger and all ur questions will be answered.
http://forum.xda-developers.com/showthread.php?t=991276
sent from my DNA
jbroses said:
I am new to Android - just got a Droid 3.
How do I stop the system from auto-killing a certain app? When I play Angry Birds, if the phone goes to sleep on timeout, when I turn it back on, the App has to re-load from scratch (rather than opening to where I left off last time). I'm assuming the system decided to kill it for lack of memory, but how do I STOP it from doing that (like an ignore list)?
Will I need a third party app?
Any help is appreciated!
Click to expand...
Click to collapse
Hi, excuse me for not reading other posts and replying directly but wanted to share something that works for me and does not kill certain launched apps. Open any app, then come out of the app and tap on recent apps button and you will see the apps that are currently launched. Depending on your OS and model, are you able to lock an app (by slightly dragging the app icon down and then tapping on the lock icon). I did that for one of the games and surprisingly even after several minutes, I was able to continue from exactly where I left off. Hope this helps. Let me know.
Screenshot: http://1.bp.blogspot.com/-9Bs7dxj7t3o/VZHLFAF6fdI/AAAAAAABI0Q/WXFhUv1c2gw/s1600/IMG_0023.JPG
Hi,
I installed Amazon App Store app to get one of the free app of the days. But now, it keeps running in the background. Probably collecting info.
I added the app to the Auto-End list (where it SHOULD kill the app after 2 minutes of screen off). The Amazon app seems to start when phone boots up. It also someone resurrects itself. I've made sure to not use it, and at some point during the day I checked running tasks and there it is.
If I kill it manually, it eventually shows up again some time during the day.
There are other apps that turn on by themselves on startup, but don't resurrect themselves. On windows, it's easy to manage auto-startup services. It's in the administrative tool. Is there the equivalent of this on Android?
Amazon is annoying like that; it does the same thing with me. Its really not hurting your battery or phone but just looking at it can be annoying so i understand. If it really bothers you that much get "titanium backup" from the market and freeze it when you aren't using it. Also your phone is smart enough to close apps/end processes on its own, moto just put the task killer there as it really serves no purpose. Also auto killing apps isnt smart; your phone probably uses more battery when it has to open up a new process everytime you open an app since you autokill and dont let it manage process/apps on its own. Android likes to let apps that aren't being used rest in memory in the background...id suggest you stop auto killing apps and do some research for yourself on how the android linux kernel works.
Thanks.
I did read into Android developer's way of thinking about how apps on a smart phone should behave, and their philosophy regarding memory management.
However, this philosophy opens up the possibility for abuse by app developers (Amazon). Programs that I use maybe once a month really don't need to be running (especially on startup), regardless of how little memory they use up, or how awesome Android's memory management scheme is.
I don't intend on micromanaging every process. Just those that are obvious wastes.
coachclass said:
Thanks.
I did read into Android developer's way of thinking about how apps on a smart phone should behave, and their philosophy regarding memory management.
However, this philosophy opens up the possibility for abuse by app developers (Amazon). Programs that I use maybe once a month really don't need to be running (especially on startup), regardless of how little memory they use up, or how awesome Android's memory management scheme is.
I don't intend on micromanaging every process. Just those that are obvious wastes.
Click to expand...
Click to collapse
I agree with you. Try out bloatware freezer or other apps in the market that blk apps from starting up when the phone turns on. Android definitely needs to get small issues like this fixed in future builds for sure.