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!
I'm looking for any app that can provide me facility to lock an app in memory so that I can access it quickly without waiting time.
Purpose for this hunt is, I needed "Smart Dialer" which stock dialer of CM failed to provide.. I installed GO Contacts EX and I loved that app. But, it takes like 5-7 seconds to load in memory if it was killed. I tried "RAM Manager" with hard multitasking feature but again, no perfect solution so far.
Hi all,
I just got my Transformer Prime this week, and as a new user both of Android (my phone is a WP7 device) and of tablets in general, I do have a couple of questions that maybe you guys can help me with...
1) Shut it down or not?
Being a tablet something in between my phone and my laptop, I'm still not sure exactly how to manage it. I know this will come with experience, but do you guys leave it always on like your phone or do you shut down like a laptop? I actually only hibernate my laptop, but I don't know how to do that on my TP... is it possible?
2) Services: my battery and OS responsiveness
OK, so I got my TP and started downloading apps... Skype and Facebook were one of the firsts. I quickly realized that, by default, after opening them for the 1st time, they kept giving me notifications, even if I swiped them left of the task manager (i.e. closed them, AFAIK). This is OK for Skype, but I really don't want Facebook bothering me that much, so I disabled notifications on its settings. Is that all that is needed to remove these permanent services? Does the "services" tab under Settings -> Applications really show everything that is running or can some apps hide from there?
3) Closing apps: should I care about it or not?
I still didn't fully understand how "closing apps" work on Android (ICS at least). If I have an app with notifications enabled (i.e. its service is enabled, right?), even if I close it from the task manager, the notifications keep coming. However, if notifications are disabled, is swiping them left from the task manager REALLY closing them? At the end of the day, to improve battery and responsiveness, should I keep closing my unused apps?
4) Launcher: Is ICS launcher the best for tablets?
This is actually part of a more general question, coming below. But anyway, I read that the ICS launcher is much improved from previous Android versions, and at the same time I didn't find a good launcher comparison for tablets only. Many of the launchers reviews only apply them for phones, and only compare them to the Gingerbread launcher (or some device-specific launcher). Since many of the launchers are paid apps, I would like to know: is there any launcher that is really worth trying in my new TP? What do you guys use?
5) Tablet-optimized apps???
I don't have my TP for even a week and I'm already tired of reading great things about an app, only to download it and see that it is not optimized for tablets at all. So, is there any good source of info/reviews on tablet-optimized apps?
Many thanks!
Leo.
1) Shut it down or not?
Personally, I always leave mine tablet running. There is a price to pay from a battery perspective when shutting down / starting up, so unless you know you are not going to be using it for an extended period of time, I would recommend leaving it on.
2) Services: my battery and OS responsiveness
I believe the 'Services' tab will show all the user app services that are running, but I am not sure if you can permanently prevent them from starting back up with ICS. I have seen task manager apps in the market that can prevent services from starting up. In all reality though, if you are concerned about background services draining your battery, the Prime has excellent battery life to begin with, especially if you have the dock, so if I was you I wouldn't get too worked up over the background services. Now if we were talking about a smart phone here (like my Thunderbolt for example which has horrible battery life), I would be much more concerned about this type of thing as I would want to do anything possible to squeeze as much life out of my battery just to get through an entire day.
3) Closing apps: should I care about it or not?
From my understanding swiping an app on the Recent Apps tray won't actually kill the process. Swiping an app from the Recent Apps tray more or less just removes the app from the list of Recent Apps. ICS automatically takes care of shutting down processes and releasing memory when appropriate. If you want to manually kill an app you can Force Close it from the list of apps from the Settings -> Applications menu. But again, my personal preference is to let ICS do its thing and take care of process management. I will remove apps from the Recent Apps tray just keep the tray less cluttered with apps that I don't use or need to switch to that often but I normally won't kill apps manually from the task manager.
On a side note, I would think removing an app from the Recent Apps tray would signal the OS that I am not going to be using the app again any time soon and the OS is free to shut down the process and release its memory, but I am not sure if this is what happens or not. All I know is that I have read elsewhere that removing an app from the Recent Apps tray will not immediately kill the process.
4) Launcher: Is ICS launcher the best for tablets?
Personally, I really like ICS so I haven't tried any of the other launchers that are out there (on the tablet side of things anyways). I used the GO Launcher on my phone for a little while but ended up switching back to the default HTC Sense launcher. This is one of the things I love about Android though; the ability to totally change the look and feel the device by simply customizing and switching between different launchers. If I ever get tired or bored with ICS, I can download a new launcher and just like that, everything will seem new and fresh again.
5) Tablet-optimized apps???
This is one of the big problems with Android and the Android Market right now; not just the small selection of tablet optimized apps but being able to find these apps in the Market. There is an 'editors top picks for tablet apps' section or something like that in the Android Market that I have used. Unfortunately, many of the apps in there are not that great, but at least they are optimized for tablets. Typically I will just do a google search for 'top android tablet apps' to get a feel for some of the best tablet optimized apps that are out there.
Try the Tablified website or app to find tablet optimized apps. Can't download directly from there, but the install link will take you to the market page for whatever app you want.
http://www.tablified.com
jordache16 said:
1) Shut it down or not?
Personally, I always leave mine tablet running. There is a price to pay from a battery perspective when shutting down / starting up, so unless you know you are not going to be using it for an extended period of time, I would recommend leaving it on.
Click to expand...
Click to collapse
First of all, thanks for taking the time to reply me! Anyway, my point was exactly about the times when I will not use it for an extented period, like when I go to bed or something... But I guess since I don't want any notifications when I'm sleeping, I think it is wiser to shut it down. On the other hand, is there a quick-way to completely silence the tablet, i.e. turn off the volume AND the vibrations?
jordache16 said:
2) Services: my battery and OS responsiveness
I believe the 'Services' tab will show all the user app services that are running, but I am not sure if you can permanently prevent them from starting back up with ICS. I have seen task manager apps in the market that can prevent services from starting up. In all reality though, if you are concerned about background services draining your battery, the Prime has excellent battery life to begin with, especially if you have the dock, so if I was you I wouldn't get too worked up over the background services. Now if we were talking about a smart phone here (like my Thunderbolt for example which has horrible battery life), I would be much more concerned about this type of thing as I would want to do anything possible to squeeze as much life out of my battery just to get through an entire day.
3) Closing apps: should I care about it or not?
From my understanding swiping an app on the Recent Apps tray won't actually kill the process. Swiping an app from the Recent Apps tray more or less just removes the app from the list of Recent Apps. ICS automatically takes care of shutting down processes and releasing memory when appropriate. If you want to manually kill an app you can Force Close it from the list of apps from the Settings -> Applications menu. But again, my personal preference is to let ICS do its thing and take care of process management. I will remove apps from the Recent Apps tray just keep the tray less cluttered with apps that I don't use or need to switch to that often but I normally won't kill apps manually from the task manager.
On a side note, I would think removing an app from the Recent Apps tray would signal the OS that I am not going to be using the app again any time soon and the OS is free to shut down the process and release its memory, but I am not sure if this is what happens or not. All I know is that I have read elsewhere that removing an app from the Recent Apps tray will not immediately kill the process.
Click to expand...
Click to collapse
Hum, ok, I will try to freak out less about open apps. What's still bugs me, for instance, is the behavior of Google Talk vs. Skype. After turning the tablet on, Skype doesn't open automatically, and after I open it, it will gracefully inform-me of its status on the notifications bar. However, today I just got surprised by a incoming IM from Google Talk, even if I did'nt open it! I realized that it is hidden under "Google Services" in the app list, but there is no setting in the app to disable it from running on start-up! I can only "sign out"... Anyway, on the other hand, there's no setting to have Skype launch automatically on start up...
jordache16 said:
4) Launcher: Is ICS launcher the best for tablets?
Personally, I really like ICS so I haven't tried any of the other launchers that are out there (on the tablet side of things anyways). I used the GO Launcher on my phone for a little while but ended up switching back to the default HTC Sense launcher. This is one of the things I love about Android though; the ability to totally change the look and feel the device by simply customizing and switching between different launchers. If I ever get tired or bored with ICS, I can download a new launcher and just like that, everything will seem new and fresh again.
Click to expand...
Click to collapse
I'll second that. I've quickly used the Iphone 4 a couple of times and its dullness just bores me to death... hehe
jordache16 said:
5) Tablet-optimized apps???
This is one of the big problems with Android and the Android Market right now; not just the small selection of tablet optimized apps but being able to find these apps in the Market. There is an 'editors top picks for tablet apps' section or something like that in the Android Market that I have used. Unfortunately, many of the apps in there are not that great, but at least they are optimized for tablets. Typically I will just do a google search for 'top android tablet apps' to get a feel for some of the best tablet optimized apps that are out there.
Click to expand...
Click to collapse
Yeah, I saw that, but I hate that I cannot filter that list between apps and games... stupid Google or stupid me? hehe
wikedawsum said:
Try the Tablified website or app to find tablet optimized apps. Can't download directly from there, but the install link will take you to the market page for whatever app you want.
http://www.tablified.com
Click to expand...
Click to collapse
Thanks for the tip! I'm cheking it out right now...
reguarding open apps
At times i noticed my stock launcher was laggy to switch between screens. After swiping to close the recent apps it was a lot more responsive, so i think that swiping the apps from the recent list does close them, at least in mose cases.
As to optimization apps, usually they are intended for phones running older software. You need to remember that every phone (aside from the google phones) is running a slightly different version of android.
Since each version of android is different, even between the Froyo on my phone and your phone, because they have different modifications on them there is a chance that the customized software on my phone may be better at handling unused tasks than your phone (in fact HTC phones by default have a LOT of running processes in the background, whereas Samsung phones generally have fewer).
A lot of these optimization apps do several things:
Turn off wifi and bluetooth when not needed
Close tasks when they are unused
lower screen brightness
turn off 3g and use 2g if available and not in a call
Now this may be excellent for your phone, it spends most of its time in your pocket, soon as you unlock it it can connect to wifi again, turn on bluetooth, etc.
HOWEVER!
If you have, say, the weather widget, or a clock, or in my case battery monitor pro, and the task killer is killing those tasks those widgets will no longer update.
Some tasks, like Maps, tend to start up automatically, meaning your wasting MORE battery life closing this app and then it restarts and you have to close it again. It takes less battery life having it run in the background.
Sometimes an app will close (like the browser) that your not fully done using. Theres a difference between the app being frozen in memory and fully closed. Both do not require much power, however when you open that process again the frozen one takes a LOT less battery than the unfrozen one.
On a tablet, having a case that has a magnet in the apropriate spot and, say, tasker (very good app for custimizing your own triggers to turn things on and off) to detect that sensor and shut off wifi, gps, bluetooth, etc. would be very cool. Many apps use the proximity sensor to detect if its in a pocket and shut off everything, or the lockscreen. Because the way a tablet is used many of these battery saver apps will actually use more battery than what would be used in the first place.
You also have to remember that as android advances there are more tweaks for battery life put into them. For instance, you can have ICS close tasks that are not being used right away to save memory and its pretty good about freezing things in background memory.
Older versions of android lacked these features, or they were poorly implimented. I remember on my vibrant i was always going back to make sure all my tasks were closed properly when i was done with them. With newer devices its not an issue android takes care of that for me.
TLDR: Try as many battery saver apps as you like, just be warey as to what devices they are designed for and what version of android they were made for. Doesnt mean they wont work, just means they may do something thats useless for using on a tablet.
1) Shut it down or not?
Never. We got the companion core for a reason.
2) Services: my battery and OS responsiveness
No, everything is shown except core processes. You can get systempanel if you want to see.
3) Closing apps: should I care about it or not?
Don't unless you somehow got froyo or eclair onto your tablet.
4) Launcher: Is ICS launcher the best for tablets?
Depends on your tastes. I would suggest trying all of them.
5) Tablet-optimized apps???
What the other people said.
1) Mine is always on. I shut down when I expect it to be idle for a long time or when I want maximum battery conservation while idle. Pressing the power button is as close as you get to hibernate, officially with Android. I'm interested to know if any of the usual Linux power management stuff applies to these systems or if it's tied to ACPI (A PC thing), and if there would be a way to wake the system. It's certainly not supported by ASUS .
2) Google how Android services work and about the application life cycle. For the most part things like Facebook don't do all that much harm, unless it is dealing with a lot of data. If you do not want it to run and the application lacks a setting for turning the service off, uninstall the app. A startup manager may or may not be able to help but be warned: auto task killers are generally bad, you would actually want to manage the startup services not auto kill them!
3) No. Android will take care of this OK. Closing apps generally refers to the "Activity" not the service. Android has taken decent care of that since at least version 2.2 and this tablet runs 4.0.3 . Swipping stuff out of the multi-task menu is most useful for keeping it tidy, it will not generally improve your life in most cases. For a good explanation you should look for a post Dianne Hackborn reshared on G+, I believe Android Police even carried it.
4) Depends on what is best for you. It's great except for the lack of customization. Nova Launcher offers a bit more. ICS's launcher versus e.g. GB's is almost what could be called a basic custom launcher, i.e. all the important stuff is there but you can't tweak the hell out of it. For more serious work try ADW Launcher Ex (scrolling widgets currently broken) or Go (not quite fully tablet optimized yet but works). I use ADW Launcher Ex, and there is a free version with less features.
5) Tablified Market and XDA usually helps I guess. I rarely have problems except with rarely updated stuff.
Sent from my Transformer Prime TF201 using Tapatalk
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.
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