RAM and Multitasking - Galaxy S I9000 General

You are using app 'A' , you press home key, you are back on home screen, app 'A' stays in RAM as is then you open another app or do something else and again open the same app, there it loads quickly (blazing fast as everybody claims) no micro lag even, with same status, where you pressed home key. If I check the CPU uses for good apps it's always 0 %, means app is in suspended state, if app is in background and consumes CPU, task manager suspends it(my observation).
This is how iOS does it, no back key. You keep on opening apps and when needed, multitasking makes room, there you notice a micro lag ALSO in iOS.
Now on Android, you get same behavior as above if you don't use back key, you can really compare smoothness with iOS and only micro lag when RAM should be freed.
Try it with 'whatsapp' for example, you will see it.
Of course back key is needed but not for all the apps and that's where it differs with iOS and creates confusion of lags. Well many people don't care micro or mini lag but the point is why not to have a mechanism on apps, that either app should go in suspended state when back key pressed (same as home key) or app must quit(resource hog apps or games).
It doesn't require user attention to press home key or back key but checks if in what status app should be put in.
I hope I am correct and not missing something major here. Now I am getting used to pressing home key on some apps with my own conscious and think about lag questions everywhere.
Your opinion please. I just want to clear my concept about it.
and yes about battery life, please keep that aside for a moment.
Thanks

I will give it a try for a few days.... will see..

Thanks dude,try it. may be there is an chance of improvement.
Sent from my GT-I9000 using XDA App

With the current state of apps, it shouldn't be necessary to exit apps at all. The home button should suffice. I really don't know how memory efficient Android was back in 1.5-2.0, but currently it works pretty well.
I believe the back button should only be used to navigate within apps, but not to exit apps. It is "in theory" not necessary if the app is properly developed.

A lot of apps stay in ram even if you exit them with the back button.
Interesting post. I have a habit of killing all apps lol, for fear that some will drain my battery life (some definitely do, ie. words with friends!)

Download the App "System Panel" from the Android Market.
It's free and it lets you know how much ram and CPU your apps are currently eating up...
Sent from my MB860 using xda premium

Only thing I have noticed is that not all aplications stay in memory after I press Home.
For example when I open dialer (phone.apk) and then press Home button, next time I start it it starts extremely fast.
But if I leave the phone for a while (not starting anything, about 100mb of free ram) and then start the dialer again it starts slower again (it does not stay in cached proccesses).

voodoofox said:
Only thing I have noticed is that not all aplications stay in memory after I press Home.
For example when I open dialer (phone.apk) and then press Home button, next time I start it it starts extremely fast.
But if I leave the phone for a while (not starting anything, about 100mb of free ram) and then start the dialer again it starts slower again (it does not stay in cached proccesses).
Click to expand...
Click to collapse
That's because some RAM used by the Dialer process is being claimed by the OS to do something else. Even if the phone is sleeping, it could be claimed.
The Android system tries to maintain an application process for as long as possible, but eventually needs to remove old processes to reclaim memory for new or more important processes. To determine which processes to keep and which to kill, the system places each process into an "importance hierarchy" based on the components running in the process and the state of those components. Processes with the lowest importance are eliminated first, then those with the next lowest importance, and so on, as necessary to recover system resources.
Click to expand...
Click to collapse

Yeah I know but I am not sure why is the system killing processes even when there is at least 80mb of free memory (and I mean free, everything that's left after you deduct services and other cached processes).
Unless when the phone is sleeping the OS takes up absolutely all free memory to do something...however that sounds like a lot of memory to be taken whatever the system is doing especially while the phone is not awake...

There is also a rule from Android intelligence,remove the process which has not been used for long time,so that OS can do prevent on demand swapping.
These are features for solid RAM management and multitasking but comes at cost of app start/reload smootness.
iOS multitasking in concept looks junky by app suspend machnism but at user expr. it serves good.
I would say, RAM is filled up anyways but keep core apps always there and backkey used only for navigation.
I keep on reading app developers remarks on site like stackoverflow,just to see where from os point of view SGS can't overcome mini lag at core apps.
Sent from my GT-I9000 using XDA App

I also tried to reproduce the scenario where phone or dialer lagged (or removed from cached process) after pressing home key while in dialer and kept phone idle for long time.
Yes it happens, but I tell you when, I had ~100 MB free, started dialer, pressed home key, left phone idle for more than an hour or so, then I checked phone was removed from cached process and starting it was bit slow (although backkey not used) but at the same time I checked my RAM was filled up upto ~278 so only had 50 MB available.
It seems like Android fills the RAM (I think not sure: with frequent used apps, depends user to user what he uses more) upto 90% and 10% always left empty.When I try to fill it I never crossed 285 mark, it came back to same ~278 level automatically(yes I was using smaller apps to fill it).
All,
If you get time, please share your expr. I am trying to learn something here and may be I am getting things wrong.
I am believing that back key power is not utilized in favor of user experience and there is a room for improvement.

Have you had a chance to check out that "System Panel" App I recommended?...
Sent from my MB860 using xda premium

for me home button = minimise & multitask, back button = close

bundi22 said:
for me home button = minimise & multitask, back button = close
Click to expand...
Click to collapse
I know it has been a while but any updates on the issue.

I wonder, would it be possible to force close all processes not necessary to run fundamental services (call, sms receiving) when using resource hog apps like heavy games?
Something like: "if app requires more than 80% of CPU for 5 seconds non-stop and occupies more than [put value here] of RAM, THEN close all unnecessary processes (even system ones) and keep them closed till app shut down"
Sent from my GT-I9000 using xda app-developers app

Related

Back button does NOT end applications!!!

So, after installing Task Manager and opening it I had 31 applications running in the background! Yup, you read that right, 31!!! I ended them all and started playing around. I would launch and app, hit the back button and then go into Task Manager and there it was, still running. I launched several applications hitting back aftewards and they were all still running. I even tried hitting home aftwards and still running. Oh, and I had some apps running twice!!! WTF!?!? Looks like I found a major flaw in the new 2.1 OS.
This is normal android behaviour.
Apps are only shut down when the phone runs out of memory, however if the app is not doing anyting it will be paused and not use any battery / cpu.
And since the nexus has 512MB RAM it can have a LOT of open applications
If it is a background app (like im) it usually has an exit button in the menu.
Apps always run on android if you don't end them with a task manager.
Ya, normal behavior. The app actually has to intentionally end itself when you press the back button for that to really end it. I wouldn't worry about it, though. Apps in the background tend to use very little RAM and CPU.
Not sure why people are freaking out about apps running in the background... This is normal and Android does an amazing job of freeing up memory by killing apps as NEEDED.
Hmmmm, guess I never looked at it that way. I do notice it gets a little sluggish when all of that is running in the background. I'm just used to my MT3G. I've NEVER seen that many apps running at once.
setzer715 said:
Hmmmm, guess I never looked at it that way. I do notice it gets a little sluggish when all of that is running in the background. I'm just used to my MT3G. I've NEVER seen that many apps running at once.
Click to expand...
Click to collapse
try two and two-thirds the amount of RAM and that would explain how you get so many apps running lol.
david1171 said:
try two and two-thirds the amount of RAM and that would explain how you get so many apps running lol.
Click to expand...
Click to collapse
Ha-ha, good point!!!
From my experience the apps never close it is set to idle and is stored in the phone memory therefore decreasing startup time and allowing for a better multitasking experience but on all other previous android devices there wasn't as much memory so only a few apps could run at a time before the memory would be needed so something would get closed.
You're used to having 37.5% of the ram the Nexus One has
Now here's the question: does having 31 apps open affect battery life?
Paul22000 said:
You're used to having 37.5% of the ram the Nexus One has
Now here's the question: does having 31 apps open affect battery life?
Click to expand...
Click to collapse
It depends on the applications. If they just sit quietly when suspended (in the background) and don't do anything, they will have no impact on battery life (because their threads will never schedule/run). If they continue to do work while in the background, that will have some impact, however, unless they hold a wakelock (something they need the "keep phone from sleeping" permission to do), they will have no contribution to battery consumption while the screen is off and no other apps/services hold wakelocks.
In short, "it depends."
The menu / settings / about phone / battery use panel tries to give you as much information as possible about what apps/services are consuming your battery.
martijnve said:
This is normal android behaviour.
Apps are only shut down when the phone runs out of memory, however if the app is not doing anyting it will be paused and not use any battery / cpu.
And since the nexus has 512MB RAM it can have a LOT of open applications
If it is a background app (like im) it usually has an exit button in the menu.
Click to expand...
Click to collapse
Yes. Traditional multitasking (WinMo, BlackBerry) phone OSes will not close an application (or program, on WinMo) until you tell it to close, or it decides to close itself. This is a resource hog, and results in the freezing up or running painfully slowly that we have come to expect from those devices. The iPhone always runs fast because it ALWAYS closes an app--no multitasking whatsoever--so it never runs out of resources and slows down. It "pauses" the app, then closes it, so when you open it, it resumes right where it left off, as if it were open the whole time. The downside is nothing gets done in the background--which is why awesome apps like Locale or Screebl won't run on iPhone. Android is the best of both worlds. It leaves apps running until it NEEDS to close them. When resources run tight, it pauses apps just like the iPhone, so it stays running fast, but as long as you don't overload the system, you can run background apps. And background services will stay running.
Paul22000 said:
Now here's the question: does having 31 apps open affect battery life?
Click to expand...
Click to collapse
I'm sure it does some, but with that monster of a CPU, and as little power as apps use when they're sitting in the background not doing anything, I'm guessing it is a negligible difference. But that's why I love Advanced Task Manager's auto-end feature.
i lol'd -----------__________----------------
When you have 31 applications running, is there a hardware key that you can press (perhaps with a third party software) to show those which are running, and to switch to anyone of them instantly without resorting back to the application menu? Also, does this same tool let you shut down an active tasks in order to conserver memory and battery life? I understand that a long press of the home key only shows the last 6(?) application launched but not necessarily the currently active tasks.
On my jailbroken iPhone, I'm used to be able to double click the home button to show all active tasks, and there I can switch to or terminate anyone of them. While running an application, I also have the option of long pressing the home button to end it directly so that it does not continue running in the background. If I do a normal home press, the application will continue running in the background, and I'm presented with a screen which lets me jumps to any of the desktop in order to launch new applications.
I hope I can have the same level of convenience here.
All of the applications in the backround are essentially in hibernation - it is part of the way Android manages the RAM. I think it's great.

Close apps properly?

I was messing trying to figure out which is the correct method to close apps, back and home do the same thing, holding HOME (i just found out) brings up a list of recently used apps, but i can't figure a way to properly close them. I have Advanced Task Manager to close them now and again but I don't want to keep it running all the time.
Is there any proper way if the app doesn't provide an exit function?
Because an app is on that list does not mean it is not closed. That list is just the history of the last 6 apps you used.
A lot of people say that you do not need to worry about whether or not an app is fully closed because the software manages that to ensure that it has enough free memory. I don't know enough to know whether that is correct or not.
peterc10 said:
Because an app is on that list does not mean it is not closed. That list is just the history of the last 6 apps you used.
A lot of people say that you do not need to worry about whether or not an app is fully closed because the software manages that to ensure that it has enough free memory. I don't know enough to know whether that is correct or not.
Click to expand...
Click to collapse
Yes, sorry, the apps I'm referring to are shown by the Advanced Task Manager, I merely found the Recent list when trying to find a way to exit apps.
I sometimes have 15-20 apps in there filling up my RAM even on startup things like Shop Savy will be there twice and Photoshop.com.
They, amongst others don't seem to provide options to prevent them starting at boot so I simply uninstalled them, but all the running apps do severely affect the performance when it's filling up.
I have been experiencing the same problem.
Advanced Task Manager lists a whole load of apps that start on bootup and each one of those doesn't have an option to disable this.
After a while (about 3 hrs or so) of using my Hero I am down to about 40mb of RAM which if I don't use Advanced Task Manager to kill unused apps my Hero begins to lag big time.
On the Android it is better to leave them resident in memory than stop them, unless they are 'background' processes and there is something wrong with them (a bug) making them slow down your phone.
Don't judge your Android on amount of free memory left; if anything, the the less memory left over the better as it means the memory is being used effectively to make it nice and speedy.
Processes aren't allowed to consume CPU cycles/consume battery/slow your phone down when they are not focused; the exception is background processes which need to keep going, like the music player etc. What's more, if an app is not focused then its state is preserved allowing your phone to free up its memory when needed; its memory effectively becomes 'cache' allowing it to restart quicker if it happens to have stayed in memory.
So don't worry about wiping an app from memory; for many apps there is simply no distinction between closing it and switching away from it; as soon as you switch away from it it's as good as closed; it's not slowing your phone down or taking up any memory that couldn't be freed instantly if needed, but if it is lucky enough to stay in memory it will re-open quicker.
On my experience, if you press the back button to exit an app, then the app is closed properly, running the code in the app that will release the memory and objects. This is the best way.
The only app it will not work on is the browser as the back button will send you back through the history.
Try it...
MercuryStar said:
On the Android it is better to leave them resident in memory than stop them, unless they are 'background' processes and there is something wrong with them (a bug) making them slow down your phone.
Don't judge your Android on amount of free memory left; if anything, the the less memory left over the better as it means the memory is being used effectively to make it nice and speedy.
Processes aren't allowed to consume CPU cycles/consume battery/slow your phone down when they are not focused; the exception is background processes which need to keep going, like the music player etc. What's more, if an app is not focused then its state is preserved allowing your phone to free up its memory when needed; its memory effectively becomes 'cache' allowing it to restart quicker if it happens to have stayed in memory.
So don't worry about wiping an app from memory; for many apps there is simply no distinction between closing it and switching away from it; as soon as you switch away from it it's as good as closed; it's not slowing your phone down or taking up any memory that couldn't be freed instantly if needed, but if it is lucky enough to stay in memory it will re-open quicker.
Click to expand...
Click to collapse
I understand how and why this should be true, but for me it doesn't seem to be, if my memory falls to less than 40 the phone becomes increadibly unresponsive, I get crashes and have to wait forever for it to do things like open the phone. Immediately after killing all with advanced task manager it goes back to normal.
barryallott said:
On my experience, if you press the back button to exit an app, then the app is closed properly, running the code in the app that will release the memory and objects. This is the best way.
The only app it will not work on is the browser as the back button will send you back through the history.
Try it...
Click to expand...
Click to collapse
I have tried both methods, more often than not though, back doesn't seem to do much either, I have experimented with free RAM and using back or Home, it seems the Home certainly isn't the correct way to do it, but back doesn't work very often either, maybe people aren't coding their apps properly to respond to the back button as an exit method?
this is the never ending discussion whether task manager make sense for android or not.
i'm one of those who say: definetly YES! USE TASKMANGER.
I understand that Android works in a way that taskmanager shouldnt be needed because it handles the tasks on its own, but sadly the concept just doesn't seem to work.
When my ram fills up i can cleary see that the device is getting slower, even just opening apps takes more than 5 seconds. After closing some apps the hero is fast again.
now i don't care whether ANDROID is the reason or some POORLY programmed background apps, because the outcome for me as a user is the same. I#m using advanced task manager and im very happy with it, whenever Android starts to slow down i close the open and unneeded apps, and everything is fast again...don't know how people can claim that Android does handle task management perfectly on its own.
Shahpur.Azizpour said:
this is the never ending discussion whether task manager make sense for android or not.
i'm one of those who say: definetly YES! USE TASKMANGER.
I understand that Android works in a way that taskmanager shouldnt be needed because it handles the tasks on its own, but sadly the concept just doesn't seem to work.
When my ram fills up i can cleary see that the device is getting slower, even just opening apps takes more than 5 seconds. After closing some apps the hero is fast again.
now i don't care whether ANDROID is the reason or some POORLY programmed background apps, because the outcome for me as a user is the same. I#m using advanced task manager and im very happy with it, whenever Android starts to slow down i close the open and unneeded apps, and everything is fast again...don't know how people can claim that Android does handle task management perfectly on its own.
Click to expand...
Click to collapse
The point is, Task manager of any kind is another 3rd party app taking up more memory, and quite frankly on such a high end phone i shouldn't have to worry about this problem. I noticed another thread about changing the values at which the internal task manager kills apps etc, if it becomes more of a problem i'll look into this method of fixing it.
alias_neo said:
The point is, Task manager of any kind is another 3rd party app taking up more memory, and quite frankly on such a high end phone i shouldn't have to worry about this problem. I noticed another thread about changing the values at which the internal task manager kills apps etc, if it becomes more of a problem i'll look into this method of fixing it.
Click to expand...
Click to collapse
yes, in theory we shouldn't worry about tasks in the background, but in reality as you said, the device WILL slow down. so there is no other way around than closing apps manually and defining apps to be kept alive by the 3rd party task manager.
changing values for the internal task manager sounds like something which would only work on a rooted device, but im not sure...

Why did Samsung put in a task manager and a "kill all tasks" button?

So Samsung for whatever reason, decides it's a good idea to include an easy to access task manager with a giant "kill all tasks" button in TouchWiz. It seems like everyone I know, that has a Galaxy S II, has adopted a certain behavior due this. What they do is, every time they put their phone away, they will automatically go to this task manager and kill all tasks, before locking the phone. When I ask them why the hell they're doing that, the answer is usually something like "wasting battery blah blah blah" or "wasting CPU blah blah blah"... NO!
For starters:
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
http://www.infoworld.com/t/smartphones/myth-android-devices-need-task-killers-609
http://androinica.com/2010/05/googl...-imply-task-killermanager-apps-are-pointless/
People that are doing this, educate yourself. And Samsung, well done for encouraging this.
Just because a task is in memory, doesn't mean it's doing anything, and certainly doesn't mean it's using up battery. If it's staying in memory, it's because there's no need to release it just yet. If you start it up again, it will already be there, and load up faster. The alternative is, you keep killing it, and every time you run it again, it will have to reinitialize and reload everything. Which option do you think is actually going to cost more battery?
The whole thing with people saying "oh no it's using CPU, i must kill it"... what?! If it's using CPU, it's probably doing something. Why the hell are you killing a process while it's in the middle of doing something? Do you not care about data integrity at all? It could have been in the middle of syncing, or in the middle of a write operation who knows.
If you run other applications and your memory runs low, then Android will close it. And it will close it properly, as opposed to you force killing it, denying it of any chance to clean up.
Obviously there are rare exceptions with dodgy programs. But most of the time, the tasks being killed are system apps, or trustworthy apps, properly written by Google or Samsung.
If you're not a developer, you probably won't understand the whole Android application lifecycle.
http://developer.android.com/reference/android/app/Activity.html
By force closing an application, you're not allowing it to run its onStop() and onDestroy() functions. This is where apps do all the clean up, releasing resources, unregistering things, closing connections etc.
Do you do this on your PC. Open up Windows task manager, and just kill any task that's using CPU. Or hell, just kill all tasks every 2 minutes! Good luck with that.
This has probably been said hundreds of times, but a lot of people i know are getting GSII's and I see them doing this constantly. It's stupid. Do you really think they designed the operating system so that you have to kill everything each time you touch it?
TLDR: Stop "killing all tasks" (unless theres actually something wrong) and well done Samsung for encouraging this. Just stupid.
Damn your right, I never used a task killer on previous android phones, but for some reason I have got into the habit of doing it now. So I'm going to kill that habit. Well noticed
Well according to the user guide (the full one from Samsung's website)... though personally I don't bother killing anything
Use the task manager › ›​
Your device is a multitasking device. It can run more than one application at the same time. However, multitasking may cause hang-ups, freezing, memory problems, or additional power consumption. To avoid these problems, end unnecessary programs using the task manager.​
1 In Idle mode, open the application list and select Task manager → Active applications.
The list of all the applications currently running on your device appears.
2 To close an application, select Exit.​To close all active applications, select Exit all.
i like the placebo effect and stop telling me what i have to do or not to do!
your writing style is to aggressive, stop being aggressive!
For me, it is worth to have the clear memory option because I already faced the glitch or bugs program which cause my phone to run constantly at 1.2ghz and this will cause my phone become extremely hot. I can't see what application is running but for some reason, the cpu gone crazy. It drain battery in no time. With the simple one click button, I can closed the programs without need to restart the phone. Yes, generally I will let the android system to handle the application by itself but I still think it was a good moved by samsung to have task manager if we use it in proper way...
Sent from my GT-I9100 using XDA Premium App
Well it's not all that bad, with 2 cores one core can easily come into a deadlock and the device will continue to function albeit much slower and consuming a lot of power, when this happens in the taskmanager the processes are listed red
Thanks ever so for much for this post I have just got my first Android phone and thought by doing this it would increase the battery life a tad but did kinda think it was a bit daft having a system that required manually killing tasks. Coming from a Windows 6.1 XDA Zest I am still getting my head round an OS that's doesn't require hours on Internet to work out how to do things.
Sad, but true, I was getting onto Android from Symbian, and first thing after I realised that I do not have option of killing all apps, I have installed the task killer and kept using it for like a week, then I've read one of the articles about it, that its wrong, and that Android is not working as Symbian nor Windows, so I realised that I dont need to do that... unninstalled it and not using it at all since
You don't need Task manager / killer if only all android applications are developed by good programmers that implement Android application lifecycle properly.
The problem is not all applications are developed this way. Some application may buggy / in beta stage that still consuming processing time even they are in background.
Task manager is still useful to close nasty program manually. But I do agree, auto-kill is useless and can cause battery drain and system instability.
Yep .. it's mostly services what eats battery. And there is poor control over that. It would be interesting to see what service was active at what time, or even how much battery did it use. All battery discussions are about guessing what is running in the background and how often and how much. We should not guess such things.
As far as I'm concerned an in built task manager is just as important as an in built modem right now. There are far too many unstable applications out there that hang up and Android can never fully deal with them(despite what research may or may not have been done in the past).
I have a few games installed on my S2(namely Pool Break Pro & TNA iMPACT!) that crash quite often and require the use of the task manager to manually end those programs(they are in the task manager highlighted in red when they have stalled).
However, what I will say is that the button to clear memory in the RAM manager really shouldn't be there at all. The task manager alone is more than enough to manually exit necessary apps that crash and stay open for no reason.
I like to have the ability to close programs easily at hand. It gives me better control over "rogue" apps. I only use it for a few programs though, like the Engadget app. It seems to be poorly coded, often using 40-50% CPU when running in the background.
Sent from my GT-I9100 using XDA Premium App
I like it because it lets me close frozen apps quicker..
the_Calen said:
i like the placebo effect and stop telling me what i have to do or not to do!
your writing style is to aggressive, stop being aggressive!
Click to expand...
Click to collapse
Lol yes. Not to be taken too seriously.
Force closing apps with the task manager when somethings wrong with the phone or closing broken apps makes sense. I'm just talking about people that instinctively press the close all apps button every time they use the phone for a second. It's just silly. Basically doing what those automatic task killing apps do.
I use to kill opera everytime i'm done with browsing because even in idle mode the phone gets very hot when opera runs in the backgtound. But after these explanstions i stop force killing every app
Sent from my GT-I9100 using Tapatalk
If a program is badly written and won't stay idle, then kill it.
I am very selective about what I install, and never kill or need to kill anything.
You have 1 GB of ram on this phone. If you want best battery and speed, don't kill anything. loading a running app from ram uses less power than starting from scratch and booting it from nand, then starting it up.
So if apps are well written, don't kill them. If stuff stays around causing drain, kill it individually but find a better app
This thread is spot on... for the most part. Like Pulser said, there are apps when idling/cached, cause detrimental effects like the one I detailed here causing your phone to stay Awake constantly and draining battery:
http://forum.xda-developers.com/showthread.php?t=1094666
ATK isn't the most elegant method, but it allows you to put everything else on ignore and have it actively kill the apps that love to stay cached and cause issues even after you've exited out of them.
Is there a way to "lock" some apps into a memory so they never quit by the android OS except if I would decide to?
Sent from my GT-I9100 using Tapatalk
You have a valid point, but most of the time those apps don't do anything critical that it would hurt to interrupt. I usually prefer to exit them normally, but sometimes I just kill it, like when I forgot the Messages / Internet open. No need to paranoia though, leaving a few open won't kill your battery.
PINki92 said:
Is there a way to "lock" some apps into a memory so they never quit by the android OS except if I would decide to?
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
That's exactly what I needed. There are some apps, like SetCPU, TB, Root Explorer, which can be added to SuperUser authorization and it won't get killed by anything unless someone manually kills it. I'd really really like to know how to add an app under SuperUser or anything which will do the job to add the app in to the OS and which can't be killed by any Task Killer or anything.
Besides I also hate those Task Killer apps, they are meaningless unless an user do nothing regularly with his/her phone.
I've no Task Killer installed but once I used the built in Memory Clear feature and next day my schedule app got closed. From then I never touched it. But one thing if RAM usage goes above 400 MB I think sometime its good to clear the memory as it will help to refresh it. But Samsung should had put the Memory Clear feature more precisely.
Regards.
Sent from GT-I9100

Not really able to multitask due to constant low memory situation?

Hi,
I don't think this is limited to my device so I am asking here. Are you guys really able to multitask on your devices? On mine I start the web browser then I switch over a couple of apps and when I try to go bqck to the browser it gets launched all over again. Of course it remembers all the pages I have opened but they get reloaded. The same happens to other apps all the time. That drives me crazy. I installed an app called System Panel that I used to have on my HTC Desire and it shows that there are a lot of background services running and out of 700 megs of RAM it's only 50-80 free memory. Among those running apss there are services of widgets that I have never used like AP widget, world clocks, Yahoo finance, samsung hubs and etc. That's insane that such stuff occupies memory while apps that I really use gets killed so eagerly. Is there any way to improve on this behavior? My HTC desire seems to handle more apps at once than my GalTab :O
Marcin
Sent from my GT-P7500 using Tapatalk
I'm with you about the browser. So irritating that pages are reloaded when you leave the browser. I put starburst ROM on mine so I'm not sure if that took care of the RAM issues, but the reloading browser is pure fail. (BTW- I use dolphin for pad and it's the same).
I guess it's more a matter of the OS killing background apps to retain memory than the app behavior.
In Android an app(it's called an Activity) cannot forbid the operating system from killing it when the OS decides to. An app can only gets notified about the event of being killed to persist its state to be able to restore it later. And the browser does that.
What the problem really is here is that because of a lot of bloatware(including background services of Samsung hubs, Yahoo widget, Associated Press widget) running in background the OS is not having enough memory to keep the user apps runinng. So soon afther an app is put into background it gets killed to make space in memory for other apps.
And as far as I know killing thresholds for available memory are set to around 56 MB. And this happens to be around how much free memory is available for most of the time. So it makes any app put in background to be killed almost immediately. This makes the OS that is supposed to have an edge over iOS in terms of multitasking to be in fact able to run a single app at a time
And ifor example my HTC desire that runs vanilla Android 2.3.4 (Oxygen) seems to run with close to 200 MBs (out of 576MB built in according to the specs) of free RAM during normal operation. I do not use any task killers or any similiar tools. This makes the OS to easily handle multiple apps in background.
So, the question becomes: "how do we [permanently] kill all those background bloatware processes?"
freeze them with titanium backup
U guys realize it only reloads browser pages if u back out or hit the home button right? X the tabs out and ur browser will not do this
The only app that ever shows me the low memory msg is logmein ignition
Sent from my GT-P7510 using XDA Premium App
This is not really what we are talking about here. Try it this way. Open any page in a browser. GMail for instance. Log in and leave it this way. Now open the task switcher and go to some other app (e.g. Tapatalk). Navigate through some other apps and then select the task switcher and try to go back to your browser. You will notice that it was shut down silently and now it's started again. All previously open pages will be reloaded at this point. On my HTC Desire using the same scenario I end up with a web browser screen restored with the already open page not being reloaded. It even remembers what part of the page I scrolled down to.
bandit_knight said:
This is not really what we are talking about here. Try it this way. Open any page in a browser. GMail for instance. Log in and leave it this way. Now open the task switcher and go to some other app (e.g. Tapatalk). Navigate through some other apps and then select the task switcher and try to go back to your browser. You will notice that it was shut down silently and now it's started again. All previously open pages will be reloaded at this point. On my HTC Desire using the same scenario I end up with a web browser screen restored with the already open page not being reloaded. It even remembers what part of the page I scrolled down to.
Click to expand...
Click to collapse
So the honeycomb memory management system is doing its job and freeing up memory when the browser is in the background idle. You are complaining?
bluskye said:
So the honeycomb memory management system is doing its job and freeing up memory when the browser is in the background idle. You are complaining?
Click to expand...
Click to collapse
Well, it does not really. I just rebooted my device and noticed that now I can switch between tasks without having the one that I've just put into background immediatelly killed. Also after the reboot there is around 300 MB of free RAM compared to 50 MB thad I had after a few days of use. Also the entire device feels way more snappy now. Doesn't it look like a memory leak?
I have not seen this problem - can have many things running and still have close to 100mb memory free. Doesn't seem to have got worse from a few weeks usage, either. But I have noticed some running processes that I have never even opened, which is strange. Solution is definitely to root and then freeze the things you don't need, but personally I am not going to do this as my memory seems fine. You could try taking off certain widgets and not running certain programs after reboot to see if one thing in particular causes a big memory drain. Social Hubs? I have never even opened this as it caused a mess on my Samsung phone.

[Q] Advantage in closing apps?

Hi there
So this is my first android device and i was wondering if there's an actual advantage when you completely close apps (swipe them off in the multitasking button screen), as opposed to just let them keep running in the background.
Will the phone use less battery / be faster if you swipe the apps off there? Or is there no noticable difference at all?
Thanks!
jb91 said:
Hi there
Will the phone use less battery / be faster if you swipe the apps off there?
Click to expand...
Click to collapse
Yes.
also easier to multitask.
IMO, you should let the built-in memory manager do its job. Free memory is wasted memory, so it will be filled with something else. In fact, the phone could be even slower, especially if you reopen the app.
I don't believe (swipe them off in the multitasking button screen) actually closes/exits the app. I believe it only removes it from the history of open apps.
It would help if for example, you are loading a huge web Page, your signal is bad and u lock your phone. In the background the app will be active = battery + wakelocks
Sent from my Nexus 4 using xda premium
Closing app will theoretically increase the battery life, but I personally didn't notice too much on battery unless I have like huge game or page loaded up on the background. I close the apps anyways because it makes multitasking with the recent menu much quicker and less cluttered.
Sent from my Nexus 4 using xda app-developers app
Usually it will close the app in the sense that when you restart it, you have to begin from its home screen. I do this when I do on Facebook, say I try to load something and give up, instead of simply going to home I'll close the app. The reason being is because I find Facebook just continues to try do what it was doing after I've left if, and if I have bad signal or its just being plain stupid it will just continue and start eating up cpu time. So I guess you can close apps to ensure its not trying to run user actioned tasks even after you close it.
Sent from my Nexus 4 using xda app-developers app
aletto said:
IMO, you should let the built-in memory manager do its job. Free memory is wasted memory, so it will be filled with something else. In fact, the phone could be even slower, especially if you reopen the app.
Click to expand...
Click to collapse
the multitasking view is an exception though, you can safely use it as its not the same as forceclosing, it simply sends a couple of events to the app and it can heed them or not - it may give androids memory manager a hint on what you need and what you dont, though (which should in theory make it better, not worse or slower). well and youre not multitasking at all if you dont use swipe out, the entire function will become a meaningless/useless bunch of apps without your management.
Closing apps can have its advantages and disadvantages..For instance...The Netflix application continues to run in the background even after clicking exit from within the app...The only way to completely close it is by swiping it off on the recent apps tray or by using a task manager
ADVANTAGES:
More free ram= no lag
Less open apps= lesser battery drain
DISADVANTAGE S:
Closing an important system app can cause lags or other problems.
Some user apps that run in the backgroung e.g widgets... will restart automatically thereby making your processor work more
Basically, the best way to handle this is to close only apps you no longer need to use and never use autokill feature built into task managers except u are sure the essential apps are in the task managers ignore list..

Categories

Resources