Database Info

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

[Q] Confused about ICS 4.0.3 running apps

I am now a ICS user and I realize when you hold the home button you'll have a list of recent apps. Cool, but I realize the list is very very long, are all those apps currently running at low usage for quick access? If so, is there a way I limit the amount of apps, I remember with 2.3.4 (whatever) cyanogenmod you could modify the number for recent apps. I ask because with so many running I imagine it will drain battery. Thanks

You can remove them from the recent apps list by swiping them away (either left or right).

I understand that, but if I let it stay because it is sort of a hassle having to deal with them individually. Will it consume a lot of battery? Am I better off leaving it, or just swiping constantly killing the task.

That, I'm not too sure of. I believe that by swiping it, it'll dismiss it from the recent apps and kill the task because there would be no point to just remove it from the recent apps list and still have it runing in the background but I think you'll need more clarification on that.
Sorry I can't help so much; I'm not running ICS yet, so I can't be too sure.

Thanks, I'll give it a Google anyways
Sent from my Nexus S using XDA App

You are better off leaving it as it is. It is really just a recent apps list, just with a thumbnail, exactly like the one in gb. Swiping can just resets the app, the same as 'backing' out of it. This has the effect of removing some apps from cache completely, though not all.

Thanks mate. My concern was that it would be a battery drain, but I'll let it be.
Sent from my Nexus S using XDA App

No battery drain unless it's some kind of service (which is usually (always?)) in the notification bar. When you press the home button, the app will be put into RAM and classified as cache, so it is quicker to open up next time. Note that filling RAM uses no extra battery, RAM is powered the same regardless. If you are using an app that requires more RAM than is available that is classified 'free', it will start removing some of the apps android has put into ram as cache and fill it up with necessary data from the foreground app.
Task managers are useful, however not any more useful than Androids built in managing (system settings --> apps). There is never a need to close any app forceably UNLESS it is not working as it should, whether it be frozen, excessively slow or not loading in some way or another, etc. All other circumstances are taken care of for you and memory is used as efficiently as possible.

Thank you Harbb for the very detailed explanation. That is exactly what I was looking for. I thought myself the same but needed clarification simply because the list was so long, I semi feared it could be running. Cheers mate!
Sent from my Nexus S using XDA App

No problem mate, just happy to help. Always good to clarify these things.

i disagree Harb. RAM management is sometimes pretty poor without using a task manager.
For example some apps that use a lot of RAM such as Real Racing 2, could force close because of lack of RAM.

I've never experienced something genuinely FCing because of a lack of RAM, but will try out the RR2 demo and see how it gets on, i'll try and get it to crash or FC. 768mb of RAM would've been really nice on the NS though as a good chunk is used by the system.

Just a tip instead of going to settings/apps..ect
Just go to recent apps hold down on the app and click app info much quicker
also most of the top recent apps are not using any resources but the lower ones are swiping will close and free up the RAM
Its a built in taskkiller that Google put into ICS even though they always said one was not needed.

[TUTORIAL] Management and optimization of RAM

What is Android exactly?
Android is a multitasking operating system, and has been designed from the outset as a system where there was the need of having to close applications. Yes, Google engineers have deliberately made sure that the applications did not need to be closed, and that was the system itself decides when and why close them.
If you look at all applications developed for Android by Google, none of them has a key "exit" to exit, this is because Android is a system designed thinking of the many activities that a normal user plays with the smartphone every day and based on This was done so that the system can efficiently manage the switch from one application to another, from one service to another, without burdening the user decide when, how and why close an application, Imagine what you would normally do , call a friend, send a text message, reply to an e-mail, take a peek at Facebook, news, or give an eye to the weather. There districhiamo between myriads of applications, and the system makes sure as far as possible, to keep in memory all the applications that use repeatedly, either because they will be much faster ripescarle from RAM, rather than from the external memory, either because ripescarle from RAM and not reopen them from scratch, you consume less battery power and processor clock cycles.
This means that Android, inside, has his task killer (yes) and that has precisely the task of managing the best processes and applications, to understand when it's time to close those less useful. But ... the question arises, there is a difference between process and application?
The answer is obviously yes, and now let's see what they are and what they do.
What is the process?
A process is an activity that can be performed by one or more applications. When you think of an application you think of something, such as listening to music, send a Facebook message or synchronize your rss feed,
these processes are rather
Because they are the actions that the application triggers to perform its task. However, it is important to note that just because there is a process in memory, with no known function, does not mean that this process is redundant or not doing anything. In fact, the processes can be in a state of inactivity or active.
What is an application?
An application is something that makes use of many different processes to provide some functionality. For example, applications for Facebook and Twitter, or GPS navigators, or even games etc.. etc. ..
An application can be active or inactive, depending on whether it has all the active processes or not currently associated with it.
When we ship an application, the system allows him to keep his job running in the background (true multitasking), allowing it to continue to do its job.
For example, continue to download emails or listen to music, or download a web page. However, just because the applications leave processes "running" in the background, does not mean that these are not really doing anything or are unnecessary. They are kept in memory if you plan to reuse them again soon. Many people think that this generates an unnecessary battery consumption, but this is not true.
The footprint of an application "inactive" at a given time in memory uses exactly the same amount of battery as it would be if that portion of memory would be free.
What happens if the memory is too low?
We said that Android has its own internal task killer and is smart enough to recognize when you are running out of available memory, in the case will start to close all applications that are low priority for him.
The way it determines the priority we shall see shortly, but in a nutshell means that applications that use less or that are not critical for the phone will be closed first. The latest to be closed, but will be applications that are currently in the foreground, and are therefore critical applications, such as the alarm.
When Android closes applications to free memory, as I said before, he does so very clever because the next time you reopen an application closed, causes to be restored, as if it had never been closed (this is what IOS currently called multitasking, but in reality is only a freezare the application).
So this means that the application of "killing tasks" that are springing up in the market, they only interfere substantially throughout this administration, also creates potential problems of instability and poor performance of the terminal.
So let's see, before continuing to debunk the stereotypes that affect Task Killer
1) The Task Killer make my terminal faster -
FALSE
-
In contrast, task killer makes the system potentially unstable and jerky. Processes kill indiscriminately is harmful, because maybe you can kill processes shared among multiple applications, and this means that the system is forced to re-open applications constantly, to reopen the process shared, and groped to restore the kill maybe just brutal while the task was doing an activity. And this can generate crash or lag that we think will result from the applications themselves, and instead we create all this ...
2) The Task Killer lengthen battery life -
FALSE
-
The Task Killer when they do exactly the opposite ... reduce the battery life!
When an application is freed killa that window of memory occupied, but almost certainly immediately after the re-open, or when the re-open, it will happen that instead of fetch it out again from the RAM, will reopen from zero and this generates more work to the system and to the terminal that it will use up more energy. Since I uninstalled Automatic Task Killer, I have to admit a longer battery life, because before ATK was always pretty nice to them to kill everything in memory and Android reopened shortly after 80% of what moments before had been closed ... This is just the beat and Ribatti antibatteria for excellence ...
3) Using a Task Killer because I do not have the exit button in the application -
FALSE
-
There is no exit button, because Android is designed to prevent the user from the need to close applications. If an application needs to be closed, the Android will be when the time comes.
4) But then the Task Killer does not need to own anything? -
FALSE
-
The applications developed for Android does not have any programming model, poorly developed some applications may generate system instability and prevent proper operation of the terminal. In this case it may be useful to kill one such application that generates problems to recover the situation and uninstall. In this case, use the Task Killer manual, which allow you to decide when and why kill such an application or process.

Thanks for this tutorial :good:

DarkJohn said:
Thanks for this tutorial :good:
Click to expand...
Click to collapse
thanks .. I hope that clarifies some ideas

Thanks for sharing.
SO what is your recommended solutions to use the memory efficiently.
Leaves it as it is ? Or..............

jbctiong said:
Thanks for sharing.
SO what is your recommended solutions to use the memory efficiently.
Leaves it as it is ? Or..............
Click to expand...
Click to collapse
I can not answer, because to judge even approximate because it depends what kind of applications you have installed in your phone, however I think the tutorial explains well why and how to act on the applications in use

When I go to the home screeen, it takes some time to reload my application icons and I thought it was related to a bunch of applications running background.. so I was always stopping services that I mostly not used, but according to what you said, I'm causing the system instability, yes?
Sent from my HTC ChaCha A810e using xda premium

pakdaman said:
When I go to the home screeen, it takes some time to reload my application icons and I thought it was related to a bunch of applications running background.. so I was always stopping services that I mostly not used, but according to what you said, I'm causing the system instability, yes?
Sent from my HTC ChaCha A810e using xda premium
Click to expand...
Click to collapse
is very likely

stempox said:
I can not answer, because to judge even approximate because it depends what kind of applications you have installed in your phone, however I think the tutorial explains well why and how to act on the applications in use
Click to expand...
Click to collapse
Thank you I understood.
This explains why V6SuperCharger does not work the same on everyone's phone, right?

This is a great thread for all new Android users!!
Well done! :good:

jbctiong said:
Thank you I understood.
This explains why V6SuperCharger does not work the same on everyone's phone, right?
Click to expand...
Click to collapse
can be a friend : Bene:

The most simplest option is to remove all bloatware. Those are really a mess which keeps restarting and eating up RAM even after they are killed.
Or just add ".bak" extension to the apk using RootExplorer incase if u will ever need it again. I did the same.
Sent from my GT-i9100 equipped with Grenade Launcher and ZN6 Prototype

Thanks forma this tutorial

blonde90 said:
Thanks forma this tutorial
Click to expand...
Click to collapse
thank you

thanks for the tuto

Always glad it's useful for the community

blonde90 said:
Thanks forma this tutorial
Click to expand...
Click to collapse
thanks, not translated perfectly, but I understand

delete

Good read. Some grammatical errors but all around nice.
Sent from my MB865 using Tapatalk 2

Yeah, Sony kept saying this for a while to all people asking for a way to force close applications.
Still I wonder if the camera app consumes battery or can take photos when parked out/idle.

since I have galaxy s2 I have no ram issues

[Q]Ram issues Nexus S Jelly Bean!

This is my first post on XDA and although i'm not new to the android scene having owned a lot of devices in previous years but I never came down to post queries of my own cause everything used to go real smooth!
I recently got a Nexus S i9020t from a friend and tried flashing a Jelly Bean rom on my device.
No issues so far with everything working with every rom that i've tried...
The only thing that bugs me is the ram.
I've tried several kernels on top of different roms (Matrix, Air (Big-Mem version), Marmite etc.) designed for Jelly Bean but I never to seem get any greater ram than about 150-170 mb even on first boot with no applications installed and when I restore about 50 of my apps through titanium it goes down to 120-150 at max.
I have tried rebooting my device every now and then but the ram leak doesn't get any better.
That way most apps that I run crash my device (im a big fan of chrome on android but the lack of availability of free ram degrades performance)
I've been looking into using different free task managers on the play store but of no use.
Simply put, my question relates to the free ram this device can generate!
Can anyone give me an explanation as to the lack of free ram and what kernel, tips and tricks I could follow to improve it?

You can try flashing a kernel that supports BIGMEM(check the development section). Since you're new you won't be able to post any question regarding said mod. Basically gives you 50mb of extra RAM which, IIRC, takes away from the HD recording portion of the phone or something of that nature. The 512MB RAM sucks, but I never had an issue with it on mine. Then again, I never really ran a lot of applications. Android can handle the tasks on its own and free up memory when needed. But you may face a few launcher redraws now and then.

chronophase1 said:
You can try flashing a kernel that supports BIGMEM(check the development section). Since you're new you won't be able to post any question regarding said mod. Basically gives you 50mb of extra RAM which, IIRC, takes away from the HD recording portion of the phone or something of that nature. The 512MB RAM sucks, but I never had an issue with it on mine. Then again, I never really ran a lot of applications. Android can handle the tasks on its own and free up memory when needed. But you may face a few launcher redraws now and then.
Click to expand...
Click to collapse
Yeah so like you said I did try the Big Mem versions of Air Kernel and Matrix but it was never really of much use. Matrix gives me about 180 mb of ram when the device has no foreground apps running (except the system processes of course) and Air goes to about 140-160 not more.
The thing that I don't get is that this other friend runs Jelly Bean on his Galaxy S with Devil Kernel or something and his free ram is above 190-ish.
Technically both sport the same hardware with a few extras on Nexus S (led flash, lack of gorila glass, NFC etc.) but it really doesn't make sense.
And about those Launcher redraws. Yeah, they've been going really frequent now that I installed and use chrome as my daily browser.
Overall, in my experience I'd say Matrix Kernel would be perfect if it weren't for that Voodoo Colour Mod. It gives a weird hue to my display orangy in nature but Air comes around well in that department.

We all understand what you're experiencing. Basically, our Nexus S devices just are not able to keep up with the ever increasing size of electronic files. Even though it's nice to be able to run JB, it really stretches the Nexus to it's limits. I too am torn, because I love the smoothness of 4.1.1, but to be honest, the phone can handle GB much easier. One other thing, Chrome is a huge consumer of ram ... really too much for the NS. As much as I love my Nexus, the handwriting is on the wall, if I really want to continue to enjoy all the new stuff coming our way.

The colors can be adjusted to your liking. Some kernels have a setting that's not the factory norm(ie Trinity). You also have to keep in mind some of that RAM has to be dedicated to the OS itself. You're gonna have to deal with the fact the phone has a memory limitation on 4.1. Sucks, but there's really not much else you can really do about it.

I could never get above 125MB on GB even with a custom kernel. With only 512MB ram, more than half of that is already used by Android itself, there's not much left for apps. That said, I would remove unnecessary widgets on home screens, install Autostarts, or ROM Toolbox, or Gemini App Manager or other autostart management app and turn off autorun triggers on apps. The less background apps the more rams you can free up. I'm currently running with about 75MB and it's smooth. I set auto free rams to start killing apps if it's below 45MB.
Sent from my Nexus S using xda premium

[email protected] said:
I could never get above 125MB on GB even with a custom kernel. With only 512MB ram, more than half of that is already used by Android itself, there's not much left for apps. That said, I would remove unnecessary widgets on home screens, install Autostarts, or ROM Toolbox, or Gemini App Manager or other autostart management app and turn off autorun triggers on apps. The less background apps the more rams you can free up. I'm currently running with about 75MB and it's smooth. I set auto free rams to start killing apps if it's below 45MB.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Those auto triggers you talk of what software do you use to counter those cause I just looked at the cached processes inside the stock Application Manager and it showed a few that always show up when my phone boots. Of those that I usually encounter is Titanium, Maps, Google Search and a two or three more. Killing them doesn't make much of a difference though. Either the ram display at the bottom is screwed or the ram just doesn't go up when I abort any one of them and after a while they again show up. How do I deal with them?

Some general points.
Yes we want more ram. But we want it to use it. Free ram is wasted ram.
Task managers suck. All of them.
Low ram should not crash your device.
Stop worrying about how me free ram you have
Chrome sucks. It sucks on all devices. Sucks on n7. AOSP just runs better.
Want to keep a little more free ram because your device lags when its low on ram. Go to developer options and limit background processes

I'm with al. No point in over-obsessing about it. Cached processes aren't doing anything. They're there for when you want to switch apps for quicker access, which part of the way Android operates. You can limit what starts on startup to increase boot time(probably not even worth it), which I do even though I just said it probably doesn't help much, with a startup manager.

I to am no fan of task killers. I've heard that they can sometimes consume more ram since some of the killed apps will try to start again.
I found the autostarts app very useful. I have disabled around 50% of all auto starts. Mainly for installed apps but also a bunch of system apps. Another useful tool is Auto Memory Manager which sets the ram level where the system kills apps according to their category (e.g. Foregroud, visible, hidden etc). I use the "mild" manager with the level for empty apps raised. I manage to get around 80 MB free when running nothing. However I have a performance ROM which might affect that number.

My Nexus S has been retired a long time now.. I'm currently using the GS3 with lots of rams so it's not an issue for me anymore dealing with low rams... However, same symptoms on the GS3 or any Android phone, the less available rams means more processes are running which can cause slow app responsiveness. Also, some app even runs in the background hogging load of cpu usage, that definitely slows down your phone. I use task manager to kill off those high cpu apps when they go wild. OS Monitor is a good app for monitoring cpu usage... GO SMS Pro is an example app that sometimes persistently consumes 30% - 50% cpu, killling it off makes the phone smooth again.
S-beamed from my GSIII via xda premium