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!
At boot, once I close everything, I keep 80mb of ram free. (besides what I need.)
I have auto task killer set to aggressive, every 30 minutes. Phone is generally fast, however sometimes everything just gets restarted at once. Phone crawls until autotask killer does its magic again. These are default GAPPS and the like. I love maps, gmail, and the like, but I'm damn near ready to delete them.
Is there anything I can do?
(overclocked to 710, any higher and the phone gets slow as soon as it gets warm, anything lower doesn't help at all)
Maybe I'm missing something. I come from a blackberry, before that a windows phone. Task killing was important, I've read that it isn't so here. But I just don't know what to do to keep my phone from going into a crawl.
viogrep said:
At boot, once I close everything, I keep 80mb of ram free. (besides what I need.)
I have auto task killer set to aggressive, every 30 minutes. Phone is generally fast, however sometimes everything just gets restarted at once. Phone crawls until autotask killer does its magic again. These are default GAPPS and the like. I love maps, gmail, and the like, but I'm damn near ready to delete them.
Is there anything I can do?
(overclocked to 710, any higher and the phone gets slow as soon as it gets warm, anything lower doesn't help at all)
Maybe I'm missing something. I come from a blackberry, before that a windows phone. Task killing was important, I've read that it isn't so here. But I just don't know what to do to keep my phone from going into a crawl.
Click to expand...
Click to collapse
They really aren't so important here, and most ROM's already come overclocked with task killers and/or governors.
What ROM are you using?
Do you have alot of widgets on your homescreen?
The only time I've had your problem is when I had like a total of 5 homescreens COMPLETELY filled with widgets.
viogrep said:
At boot, once I close everything, I keep 80mb of ram free. (besides what I need.)
I have auto task killer set to aggressive, every 30 minutes. Phone is generally fast, however sometimes everything just gets restarted at once. Phone crawls until autotask killer does its magic again. These are default GAPPS and the like. I love maps, gmail, and the like, but I'm damn near ready to delete them.
Is there anything I can do?
(overclocked to 710, any higher and the phone gets slow as soon as it gets warm, anything lower doesn't help at all)
Maybe I'm missing something. I come from a blackberry, before that a windows phone. Task killing was important, I've read that it isn't so here. But I just don't know what to do to keep my phone from going into a crawl.
Click to expand...
Click to collapse
Personally, I used to use the task killers a lot, and while on 2.1 I think it helped a little. But as I switched around different froyo ROMs and am now on gingerbread, I noticed that the task killers actually hindered my phone's performance. Battery would discharge quickly, the phone would become sluggish and sometimes lag so bad I would reboot.
I found that just leaving the android system to do its own thing worked out the best. Memory management has been greatly improved, and really eliminated the need for task killing apps and the like.
Always good reading:
"FAQ: Why You Shouldn’t Be Using a Task Killer with Android"
"Multitasking the Android Way"
"Android Task Killers Explained: What They Do and Why You Shouldn’t Use Them"
Using Gingerbread, clocked at 604mhz. CPU governor ondemand. (Bump it to 748mhz and interactive for heavy games)
No killers, although I used to be religious about autokiller memory optimizer. GB handles memory and app killing very well.
And the stock app management tool loads quick and is easy to use to kill something that's acting naughty or hung.
I use cache cleaner, set to clean once a day.
I am picky about my apps. If I don't like their startup and shutdown behavior, I find an alternative program.
I'm also rather anti social so no twit, face, up ur butt, whatcha doing apps constantly syncing for me.
I do use genie for news and weather and smooth calendar synced with my exchange via gmail. But these don't update but one every 3-4 hours. Gmail on demand unless I'm expecting something, then I'll let the sync run.
Used to be an adw fanboy. But switched to LP. Its simple and light. Adw is still my favorite especially EX, but LP performs better for me.
I also uninstall everything I don't use, email, dpm, stock music, HTML viewer, setup wizard, keyboard tutorial, development, rom manager, carhome, couple other none dependencies. Use that free space to more some of my root apps, widget apps, utilities.
Also use. Zach's cache2cache. Freeing up a little more data room. No apps on SD.
Widgets I use; note everything 3+ Widgets, genie news and weather, smooth calendar, a photo slide widget app. Usually about it. Sometimes a full month calendar.
No lag or performance loss. My daily usage averages 4 to 6 hours a day.
Edit - also turn off orientation if I don't need it to keep my screen from redrawing every time I pick upmy phone or adjust my wrist
Sent from my GSBv1.7-ERIS using XDA App
I do as little as possible.
I kill some tasks when my phone first starts up, that's the only time I use my task killer unless a program is glitching out.
I keep setcpu profiles.
I keep my apps up to date.
I keep my ROM up to date.
After installing/ uninstalling a lot of programs (Such as when I first flash a new rom) I always make sure I Wipe my dalvik cache.
I always wipe between ROMs. It's more stable and always faster.
I suggest to keep your phone fast you DONT:
use setcpu's widget.
use autotaskkiller (it's just one more process. And once you kill tasks, there's no reason to continuously re-kill persistent ones)
Clear your cache too often. Your cache is there for a reason. I personally never clear mine, just my dalvik.
Dedication
amfetamine said:
Using Gingerbread, clocked at 604mhz. CPU governor ondemand. (Bump it to 748mhz and interactive for heavy games)
No killers, although I used to be religious about autokiller memory optimizer. GB handles memory and app killing very well.
And the stock app management tool loads quick and is easy to use to kill something that's acting naughty or hung.
I use cache cleaner, set to clean once a day.
I am picky about my apps. If I don't like their startup and shutdown behavior, I find an alternative program.
I'm also rather anti social so no twit, face, up ur butt, whatcha doing apps constantly syncing for me.
I do use genie for news and weather and smooth calendar synced with my exchange via gmail. But these don't update but one every 3-4 hours. Gmail on demand unless I'm expecting something, then I'll let the sync run.
Used to be an adw fanboy. But switched to LP. Its simple and light. Adw is still my favorite especially EX, but LP performs better for me.
I also uninstall everything I don't use, email, dpm, stock music, HTML viewer, setup wizard, keyboard tutorial, development, rom manager, carhome, couple other none dependencies. Use that free space to more some of my root apps, widget apps, utilities.
Also use. Zach's cache2cache. Freeing up a little more data room. No apps on SD.
Widgets I use; note everything 3+ Widgets, genie news and weather, smooth calendar, a photo slide widget app. Usually about it. Sometimes a full month calendar.
No lag or performance loss. My daily usage averages 4 to 6 hours a day.
Edit - also turn off orientation if I don't need it to keep my screen from redrawing every time I pick upmy phone or adjust my wrist
Sent from my GSBv1.7-ERIS using XDA App
Click to expand...
Click to collapse
THAT is a lot of work and you do this EVERY day? WOW that is dedication!
Kent_Davis said:
THAT is a lot of work and you do this EVERY day? WOW that is dedication!
Click to expand...
Click to collapse
Errrrrrrrrrr?
Just an update. I used the majority of advice here. Installed watchdog. After about 4 days worth of running and watchdogs help I just Uninstalled Google Reader and Facebook. Never have to kill a task and everything runs smooth now.
Thanks!
Kent_Davis said:
THAT is a lot of work and you do this EVERY day? WOW that is dedication!
Click to expand...
Click to collapse
Hee-hee... I live on my Eris
Naw, pretty much just the new rom setup routine. But I do seem to spend more time in settings menus than in actual apps
Sent from my GSBv1.7-ERIS using XDA Premium App
Contrary to what most people will tell you, I use a Task Killer and some will call me a liar but I see a very good improvement on my battery life. As soon as I'm done doing whatever I was doing on my phone, I open Advanced Task Killer and kill every task running then lock my phone (press the end button) and tuck it away. People say it doesn't work but everyone's Eris is different and reacts different to different apps. I love having it and I love using it. I usually go in to cyanogenmod settings and use the overclocker, 748Max, 122Min, Ondemand gov, set to boot. I also use LauncherPro Plus which seems to be faster and smoother than ADW therefore using less power. I also have absolutely no widgets whatsoever. Wifi is only on when I'm home and GPS is never on unless I'm using navigation. That's really about it and my Eris runs smooth as a baby's backside !!
How can I do this? I noticed yesterday that my scramble with friends app with only 2 games, was taking up 135Mb RAM. I'm sure there's another issue behind there, but this got me noticing other apps that don't need to always be open and running, but for some reason are. How can I stop these apps from auto launching and running in the background?
cgibsong002 said:
How can I do this? I noticed yesterday that my scramble with friends app with only 2 games, was taking up 135Mb RAM. I'm sure there's another issue behind there, but this got me noticing other apps that don't need to always be open and running, but for some reason are. How can I stop these apps from auto launching and running in the background?
Click to expand...
Click to collapse
Just because something is loaded doesnt mean its actually running. Android takes programs that are often used and load them into RAM so that they are ready and waiting when you want to run them. They are then dropped out of memory when that memory is needed for something else. Read up on memory management to get a better idea. If you want to kill it anyways, you can probably just use Titanium to freeze it, but this requires root.
Thanks for the response. I'm rooted and also running RAM manager. It seems that certain programs are taking up my RAM that don't need to be. Another example, words with friends, was in my RAM usage after reboot, and I've never even used this game before. Games like scramble with friends I'd imagine always need to be running or in active RAM since that game has notifications and built in messaging. But I don't need to constantly have that app checking for new data. I tried setting the in app settings to check every few hours rather than 5 minutes, but it was still shown as taking 130MB of RAM usage (though the number is normal now after reboot).
So, it sounds like there is no way.. or what you're saying is more of, no need? I just don't want a bunch of little used apps taking up my active memory.
cgibsong002 said:
Thanks for the response. I'm rooted and also running RAM manager. It seems that certain programs are taking up my RAM that don't need to be. Another example, words with friends, was in my RAM usage after reboot, and I've never even used this game before. Games like scramble with friends I'd imagine always need to be running or in active RAM since that game has notifications and built in messaging. But I don't need to constantly have that app checking for new data. I tried setting the in app settings to check every few hours rather than 5 minutes, but it was still shown as taking 130MB of RAM usage (though the number is normal now after reboot).
So, it sounds like there is no way.. or what you're saying is more of, no need? I just don't want a bunch of little used apps taking up my active memory.
Click to expand...
Click to collapse
No real need. Android sees that you use this app a good bit so it preloads it, and it's sitting there in unused RAM untill it's either called upon to run or untill another process needs that RAM that its using.The application is not running and that RAM would otherwise be sitting unused, so there's no need to get rid of it unless it happened to be a suspicious application. This process is what gets alot of folks all wound up about never having enough RAM because they think that almost all of their RAM is being used for running processes when in reality this isn't really true, kinda half true.
Download Autostarts from the Market, it will let you prevent apps from starting automatically.
And what Chief Geek said is true, he's missing a big part of the picture, and I see statements like his all the time. Yes Android does a good job of loading things in and out of memory as needed. However, if there is crap you don't care about coming in and out of memory all the time, then that means Android is going to dump stuff out of memory that you DO care about (browser, games, etc.) So if you have a bunch of extra crap running, that means if you pause a game, check and email, and come back, Android may have released it from memory and you have to wait for it to reload. If you cut back on the things that are constantly running, it will keep more of your apps that you care about in memory longer, meaning when you go back to that game they will be there right away.
The more stuff you can prevent from running the better. I use Titanium Backup to freeze stuff I will never use. I use autostarts to prevent certain apps from running at startup that I don't want to - Maps, Facebook, etc. Doing this gives me tons of extra free RAM which translates to more useful multitasking.
EvoXOhio said:
And what Chief Geek said is true, he's missing a big part of the picture, and I see statements like his all the time.
Click to expand...
Click to collapse
I understand where your coming from, as this is a very common argument, but what you didn't mention is your method favors empty/available RAM for multitasking while sacrificing fast launches leading to some folks experiencing a laggy system. I completely agree with freezing the junk as the bloat always seems to have pointless priority, but I feel as once these steps are taken that android does a perfectly fine job of managing RAM. Very rarely do I have to wait for applications to reopen as I'm jumping back and forth between them and never have trouble multitasking. I'm not going to be curt and say your theory is wrong, I'll leave it as just another way of running your device as it certainley has it's merits, but I don't agree that it's for the average user who is more likey to be jumping from one app to another and not back and forth between the same ones needing all the data to be exactly where they left it.
Chief Geek said:
I understand where your coming from, as this is a very common argument, but what you didn't mention is your method favors empty/available RAM for multitasking while sacrificing fast launches leading to some folks experiencing a laggy system. I completely agree with freezing the junk as the bloat always seems to have pointless priority, but I feel as once these steps are taken that android does a perfectly fine job of managing RAM. Very rarely do I have to wait for applications to reopen as I'm jumping back and forth between them and never have trouble multitasking. I'm not going to be curt and say your theory is wrong, I'll leave it as just another way of running your device as it certainley has it's merits, but I don't agree that it's for the average user who is more likey to be jumping from one app to another and not back and forth between the same ones needing all the data to be exactly where they left it.
Click to expand...
Click to collapse
You're misunderstanding what I am saying. I am suggesting to prevent apps you don't care about from getting loaded into memory automatically at startup. By doing that, it means more free memory for the system, which means better multitasking.
My method doesn't sacrifice fast launches at all. If anything, by having more free memory, it means more applications will remain in memory, which equals better multitasking and faster relaunches. Initial launches will be the same either way.
I am NOT suggesting to prevent apps you care about from autostarting - just the crap that you never use nor care about. Maybe that's where you misunderstood me.
EvoXOhio said:
You're misunderstanding what I am saying. I am suggesting to prevent apps you don't care about from getting loaded into memory automatically at startup. By doing that, it means more free memory for the system, which means better multitasking.
My method doesn't sacrifice fast launches at all. If anything, by having more free memory, it means more applications will remain in memory, which equals better multitasking and faster relaunches. Initial launches will be the same either way.
I am NOT suggesting to prevent apps you care about from autostarting - just the crap that you never use nor care about. Maybe that's where you misunderstood me.
Click to expand...
Click to collapse
I appologize for the misunderstanding, I assumed that since we were discussing an app that he says he does use that you meant to prevent apps such as this all together. Such is an argument that some make in an attempt to maximize the amount of available unused RAM.
Chief Geek said:
I appologize for the misunderstanding, I assumed that since we were discussing an app that he says he does use that you meant to prevent apps such as this all together. Such is an argument that some make in an attempt to maximize the amount of available unused RAM.
Click to expand...
Click to collapse
I was addressing what he said here:
but this got me noticing other apps that don't need to always be open and running, but for some reason are. How can I stop these apps from auto launching and running in the background?
Click to expand...
Click to collapse
But in all honesty, if his app is using 135MB of RAM when doing nothing, it is probably better off being prevented from running in the background entirely. 135MB is less than 1/3 of the free RAM on the system after a fresh boot.
I been using system tuner pro. You can freezes apps stop them from start up. It also has a task manager that you can choose which apps run what you want to kill.you can also exclude apps so if you kill all it will keep the apps you need running like widget locker bln or avast and kill the rest. Also gives you in depth everything on yor phone
Sent from my oversized communication device.
+1 for Autostarts
Sent magically through the air from the mighty Note!
kimocal said:
+1 for Autostarts
Sent magically through the air from the mighty Note!
Click to expand...
Click to collapse
+2 for Autostarts.
The best by far is Gemini app manager... https://play.google.com/store/apps/details?id=com.seasmind.android.gmappmgr
long press on the icon of the app to get a menu with an option to disable start up.
And the nice part it has very granular selection of start up permissions.
Hi Everyone,
Basically, I got my Samsung Galaxy Player 4.0 in January, and when it comes to the features, I have been loving it. This is my first Android device.
However, I have been having problems lately. First, some basic information: it's an 8gb device, and I have a 32gb class 10 microSD card in it. I have a huge number of apps on it (over 200), however, I keep careful tabs on what is running in the background, reporting an app if it runs in the background even when not needed and that will reopen if killed, and if I don't really need it, deleting it after a week. I've only had to do that with a couple of apps so far. As I use this a lot as a PDA (I don't have a phone, this basically covers those bases), I have a couple of things that always run in the background, which I want there (textplus, Linphone, MailDroid, SwipePad). After getting rid of the services that I don't need, I'm still looking at over 100MB free RAM. I'm still on the stock ROM, and I'm using GO launcher Ex. I reboot daily.
My problem is that it crashes often - sometimes daily. Usually, it will go something like this: An application freezes, the whole system becomes unresponsive, and I either have to reboot it by holding down the power button for 8 (?) seconds, or something snags and it reboots by itself. Usually the first sign is that the haptic feedback for the home button comes about a second later after I press it - except then it is almost always too late. The power button will usually turn the screen on or off, but the lockscreen won't appear, I'll see the screen as it was before, frozen. Sometimes, it eventually reboots, while sometimes it doesn't, making me hold down the power button to reboot it, and sometimes, just as it will start "becoming unfrozen" (it goes to the home screen and it starts loading), it will reboot.
It seems to be that after an approximate time of active use, it will crash. Before that, apps can freeze, FC, and within a few seconds, I'll be back on the home screen or in another app, doing something else. After that, on the other hand, it seems to me that whenever an app freezes or has a problem, it basically takes down the whole system with it.
Something tells me that this isn't just normal (otherwise Android wouldn't have over 50% of smart phone market share ), because I haven't heard of problems like this before, and other people with Android I know don't seem to be having the same problems (if any, at all). I have been reading around, and saw some thread about another phone describing similar problems, and it turns out it was a motherboard problem, so the phone was returned for warranty, except I don't remember where that was, I'm just hoping it's something like that...
OK, now that you've read my long post (sorry, I thought it would be best to give more details than get asked about them), I really hope this isn't something normal, because outside of this problem, I'm really enjoying all the possibilities, capabilities and flexibilities of Android (I'm looking at you, iPod). It's really quite aggravating, today I lost my public transit itinerary on Google Maps (I feature I love), and thankfully, I remembered enough to make it through, but it is quite frustrating. Please tell me this is not Android being Android?
Go Launcher is not Officially supported on these devices and swallows the small amount of ram very quickly, I tried it for a day and got rid of it because of how badly it impacted performance.
edit: looks like since I tried it they added support for our players, still won't run it, its to much of a system hog.
I don't know, but I tried switching to the default launcher, and it already crashed earlier than usual. Any other ideas? I'll try some other launchers over the next few days.
Sounds like you are running out of system resources. You say you have a couple hundred apps installed and I bet some of those are becoming active and hogging precious ram and cpu resources in the background until the system crashes. I have a 2 year old Samsung Captivate and I only have minimal amount of apps because it will often big down and become unresponsive and crash. So before you head out to a repair shop, remove some of your many apps and see if that helps.
So, if I understand, even if an app runs in the background for a short period of time, it still consumes resources, even after it's stopped running?
trainman261 said:
So, if I understand, even if an app runs in the background for a short period of time, it still consumes resources, even after it's stopped running?
Click to expand...
Click to collapse
If you have a titanium backup freeze apps that run in backround and see what happens ..when you open programs they will stay in memory so use some memory kill widget to clean memory from time to time.I have a stock rom witch is not very good with memory menagment so sometimes when memory is full it just stop and only help is restarting ..so i use app "quick system info" which give you memory ajd cpy usage displayed in status bar and when memory is close 2 full i just click on that and it kill all other aps except what a use in that moment.
Sent from my GT-I9000 using XDA
So, basically, the ROM is to blame? As to Titanium backup, I think that needs root, and I'm not quite ready to root yet (I've done enough hacking on my iPod). I do plan on upgrading to android 4.0 eventually (once all the issues get fixed, this is my main device, after all), and I think I'm going to have to root it at that point, but I'll be able to test it on a different ROM then, as well as try freezing apps. For now, I've tried LauncherPro, which seems a lot more lightweight, and it seems to be making it through the day until I reboot, and seems to be very stable... it also loads my widgets lightnight fast, which is great.
Correct me if I'm wrong, but the way I understand it is:
obviously there are memory leaks, every OS has that
Android will not kill services, but only programs
If there are places where memory can be freed, Android will do that when necessary
If no memory can be freed, and there is barely any memory left, than a minor FC or a frozen app is all it will need to push Android off the cliff
Is this the way it works? And, then, when I upgrade to 4.0 (CM9), most of those problems should be gone (because of better memory management)?
Hi.
First: I haven't found a thread which is only meant for my problem.
So: As written above, I'm on XXDLIB, but this behaviour is there in earlier JB releases, too (all WanamLite).
When I minimize an app (means: press home button in an app) it won't stay there long. It will be closed after a (volatile) period of time.
Example: I'm navigating and want to read something in (stock) browser. I read and minimize this app too.
I'll go back to navigation.
Afterwards I want to read my opened page (which should be in browser) and waht happens: the browser reloads the page and hasn't been listed in task manager (hold home button, left side).
So it has been closed.
First i thought that this is a out of memory issue. So I removed many apps that I don't need from /system/app and observed the memory usage then.
Same scenario as mentioned above: Navigation (Navigon) is opened, I open the browser, finish my navigation... and .. the browser is closed again.
This is vice versa: when I minimize my navigon app and use the browser for.... let's say 3 to 4 minutes the app will be closed.
Then I got deeper into it. I opened FM radio, browser, WhatsApp and evernote and minimized them, before I slept. No app with that great memory usage I would say.
But at morning ALL apps are closed.
For short: I HATE it. When I want to have my browser opened, it should be opened until I want to close it.
Sometimes I minimize my navigon app and I only need audio orders... unusable now, because the app closes very fast...
Same for browser: It eats my monthly provided data, because it reloads the last viewed page (its not reloaded from cache; with flight mode enabled there is only an error page).
It's no memory issue I would say. After opening all these mentioned apps I have more than 230 MB of free ram.
I know that wanam adds a modified services.jar with some kind of 'memory optimization script/code' from XDA devs.
But as far as I understand it, it should not lead to any closed apps.
As far as I can see, this problem is 'new' since JB (AOS 4.1.1).
In 4.0.4 it hasn't been there.
Anyone with the same problem?
Stock or mod?
Any suggestions?
I'm missing my S2... never had this kind of problems there...
Greetings,
Mario
EDIT: I'm using the newest apex launcher (free). I don't know if this could be important.
The issues you describing are present big time in ICS also. That's what I hate this phone.
I don't even think this is a Galaxy S III issue. It seems to be more of an issue with Android itself. I've noticed things like this with the pure stock android Galaxy Nexus and even on the US Galaxy S III which has a total of 1.6gb of ram available.
Mine keeps it in memory and when I return to it is still there as I left not re-started. In fact I just opened xda app after not using all day today but using many other apps it was still on the last thread I was reading. I'm running stock but rooted.
It's all about the RAM. More precisely about the amount of available RAM.
Get the free app 'Advanced Tools', go to 'options' and tick 'Root functions'.
Then go to 'System'->'System Manager'->LMKiller and configure the values.
They are thresholds, meaning that if this amount of total available RAM (disk cache deduced) has been reached, it will start killing apps off to free at least enough Ram to go above the threshold again. Lowering the values means it will only do it much later.
Make sure that you don't lower them too far, since a device running low on RAM uses the OOM-Killer to kill apps regardless of their status.
It should help to set the Dalik heap size to 128MB too, but some side effects with large games/apps have been reported.
I have also realised this problem as someone who comes from Samsung Galaxy S 2. Now I am on Omega Rom v27 and use hard swap, I should not be having this problem but no, I see that many apps are closed by system although I have huge ram available after some time. There must be a way to deal with it; I play with auto memory kill settings but have not seen a difference so far.
Regards
GT-I9300 cihazımdan Tapatalk 2 ile gönderildi
This is an Android issue even with GB, if the phone runs out of memory for the foreground process, it closes other processes in order to free up memory. However, what you're talking about (web browsing) if you're using Chrome I believe this is a chrome thing (does the page get greyed out?) Happens to me even if I leave the page on. For example:
Browsing, put phone aside, the phone automatically locks, as I unlock it does that. Doesn't bother me much though, as long as the page loads again normally. I haven't had any issue with the S3 concerning closing other applications for the foreground one.
d4fseeker said:
It's all about the RAM. More precisely about the amount of available RAM.
Get the free app 'Advanced Tools', go to 'options' and tick 'Root functions'.
Then go to 'System'->'System Manager'->LMKiller and configure the values.
They are thresholds, meaning that if this amount of total available RAM (disk cache deduced) has been reached, it will start killing apps off to free at least enough Ram to go above the threshold again. Lowering the values means it will only do it much later.
Make sure that you don't lower them too far, since a device running low on RAM uses the OOM-Killer to kill apps regardless of their status.
It should help to set the Dalik heap size to 128MB too, but some side effects with large games/apps have been reported.
Click to expand...
Click to collapse
Thanks. I will have a look - but I would say, its now memory issue, because of the free ram that is left.
Heapsize is at 128 MB, heapgrowlimit too. I played around with these values. Nothing helped.
I'll give a report tomorrow.
EDIT: On stock the heapsize is 256m. Why should someone *lower* this value, like wanam?
Any idea? I'm no programmer...
Removing the bloat helped here a lot and that change in the build.prop from 256 to 128m.
Delete kiesexe from system/bin if you don't use kies. Freeze all the Samsung applications and services. Finally don't use Supercharger.
Swyped on I9300 - XXDLIB - Siyah kernel - JKay & Thunderbolt tweaks.
To me, it happens randomly. Sometimes the browser just show the same page without reload even after a few days! But sometimes it just reload after receiving a call!!!
Is not big problem on a daily usage but is very very big problem when I'm downloading something and have to worry about incoming call.
Sent from my GT-I9300 using xda app-developers app
hey guys, it makes me miss my little "Eclair" or "Froyo" phone...
a phone with this huge capabilities can't have this type of issue...
im getting this issue when im playing and need to change a track in song player...
then it always restart the game and it sucksssssssssssssss!!!!! ;/
So, thank you all.
I increased heapsize to 276. Now the apps are hold longer in memory.
I observed something strange: When I use flight mode, apps are closed too... but thats ok.
im playing Football Manager Handheld
and it closes everytime too...
cant handle this!!!!
i want a phone that does the things correctly.....so sad!!
Ya this is really sad!!
We keep on saying how Android does true multitasking and all, but at the end of the day it's not getting done what we want to.
I was downloading Shadowgun the other night, and after about 50%, I got a msg so I pressed home button to go to the Msg app and then:
1) Home Redraw ..grrrrrrrrrrrr.
2) I replied back to text and opened the Shadogun from Recent Apps and the downloading had stopped.
Had to start it again.
WTF??
Why does android not kill the other useless cached things which is taking upto 300-400 mb ram.
Why does it have to kill Launcher and the latest foreground operation??? The worst kind of management ever!!
Why doesn't it kill Maps instead of Launcher. I've not touched maps in two days and it takes about same ram as my Launcher does??
It has got the sorting all wrong...I hate it...
I don't know how it is in iOS, but it couldn't be worse
d4fseeker said:
It's all about the RAM. More precisely about the amount of available RAM.
Get the free app 'Advanced Tools', go to 'options' and tick 'Root functions'.
Then go to 'System'->'System Manager'->LMKiller and configure the values.
They are thresholds, meaning that if this amount of total available RAM (disk cache deduced) has been reached, it will start killing apps off to free at least enough Ram to go above the threshold again. Lowering the values means it will only do it much later.
Make sure that you don't lower them too far, since a device running low on RAM uses the OOM-Killer to kill apps regardless of their status.
It should help to set the Dalik heap size to 128MB too, but some side effects with large games/apps have been reported.
Click to expand...
Click to collapse
Best reply in this thread. I have these settings :
LMkiller: 32/40/48/56/64/72
dalvik.vm.heapsize=256m
To fix launcher redraws, change it's OOM value. Supercharger V6 can help with that. Also debloated ROMs help a lot
j0ep0 said:
Best reply in this thread. I have these settings :
LMkiller: 32/40/48/56/64/72
dalvik.vm.heapsize=256m
To fix launcher redraws, change it's OOM value. Supercharger V6 can help with that. Also debloated ROMs help a lot
Click to expand...
Click to collapse
This is where Apple wins and Samsung fails.
So much just to make your phone smoothly, something Samsung should have done and not the user.
j0ep0 said:
Best reply in this thread. I have these settings :
LMkiller: 32/40/48/56/64/72
dalvik.vm.heapsize=256m
this settings will solve the problem????
if so, how to set up?????
Click to expand...
Click to collapse