Can anyone tell me why my Note is lagging so bad now? I have closed all background running apps. Cleared all caches and data. But for some reason when on the web a long time or an app, every time I hit the home button, none of my icons are there. Then they slowly start popping up. I read some on this, but have tried everything. Please help!
Sent from my SAMSUNG-SGH-I717 using xda premium
Your launcher had left ram, so when you exit out of a program to go to the home screen, your launcher has to restart and load all over again.
Instead of killing background apps, let Android do its thing and don't wiry about used/free ram. Free ram is wasted ram, and this is the perfect example of that.
Related
Ok I have looked around and have not found the answer. SO here Goes
In windows if you want to keep the memory that you have clear of background applications, you can run system configuration and just remove the check-mark for those items you dont want to auto start.
I have Advanced Task Killer installed and will set it up to auto kill and will manual kill apps as well. Instead of consistently looking at ATK to shut down apps, is there a way to just keep all the apps you not using nor have ever started from suddenly being there and sucking the life out of your battery?
Having applications "running" in the background (i.e., still in memory but in a suspended state) does NOT negatively affect your battery life. These applications are actually just remaining in memory because that memory does not need to be used by anything else at the moment. If an active application gets to a point where it needs more memory, Android will automatically close applications that are in a suspended state (i.e., not actively being used) to make room.
In other words, using an app killer is NOT necessary and I definitely recommend NOT using one. By closing the application repeatedly, you are just causing the application to take a longer amount of time to start up next time you use it. You're making your Android experience worse by using one, not better.
There is one caveat to this, and that is when you have an application installed that doesn't play nicely -- i.e., even when you stop using that application, it will continue to use up CPU cycles (never go into a suspended state). This is actually pretty rare unless you are installing really poorly written programs, but it can happen to some popular apps too (usually the result of a bug). In this case, you should either uninstall that application or use an app killer to only kill that one app.
I've heard both sides of this argument, and don't know who to believe. I didn't think I needed a Task Killer, but then I saw it repeatedly on "top 10 apps for Android" and "must have Android apps" lists from respected sites like cnet... who to believe?!
Cnet ≠ respected
Sent from my Liberty using XDA App
drumist said:
Having applications "running" in the background (i.e., still in memory but in a suspended state) does NOT negatively affect your battery life.
Click to expand...
Click to collapse
I need to confirm this. Anyone? I dont care about memory because I bet Android excels at that, and at any rate, memory is there to be used, not to keep it empty.
But I come from a Symbian smartphone and "minimized" applications DO uses battery. Maybe little, but noticeable.
Anyone can confirm that background apps consume negligible battery juice?
Additionally, is there a nice task changer? Like windows Alt+Tab. I feel my Android like an iPhone, that I need to press the home button to move to another already opened app and that's just plain stupid. So far I'm using Multitasking Lite, but it can get sluggish once there are too many apps opened. Any suggestion would be warmly welcomed.
"Running" background apps DO NOT consume battery life unless they're actively syncing. If it's just in the memory saving the state of the app then that is fine.
As far as using a task killer, if you are manually killing apps and they keep starting back up then that is a bad thing for your battery. The app uses cpu cycles everytime it starts up again and syncs data. You can use a task killer to close apps that opened on startup or when you're done with them. If they stay closed until you choose to open them again then you're saving memory, but nothing to do with battery life.
ocswing said:
"Running" background apps DO NOT consume battery life unless they're actively syncing. If it's just in the memory saving the state of the app then that is fine
Click to expand...
Click to collapse
Thanks for confirming ;]
Darius_bd said:
Additionally, is there a nice task changer? Like windows Alt+Tab. I feel my Android like an iPhone, that I need to press the home button to move to another already opened app and that's just plain stupid. So far I'm using Multitasking Lite, but it can get sluggish once there are too many apps opened. Any suggestion would be warmly welcomed.
Click to expand...
Click to collapse
Obviously you can switch over to some apps by pulling down the notification menu and selecting the appropriate app. That only works on apps that put themselves in the notification menu though (multimedia apps and things like Google Nav usually do this).
Otherwise, you can press and hold the home button to bring up the list of 8 most recently opened apps without exiting the active app. This works but like I said, it's the 8 most recent apps, so it will list apps that aren't necessarily still running anymore. It's more of a shortcut to having to go search in your apps menu or home screens to find a recent app than a way to see what is currently running.
drumist said:
Otherwise, you can press and hold the home button to bring up the list of 8 most recently opened apps without exiting the active app. This works but like I said, it's the 8 most recent apps, so it will list apps that aren't necessarily still running anymore. It's more of a shortcut to having to go search in your apps menu or home screens to find a recent app than a way to see what is currently running.
Click to expand...
Click to collapse
What can I say, I hate pressing the home key to hunt for the icon that opens the app I already opened more than 6 other apps ago ;] Guess I'll stick to Multitasking Lite for the time being. Thanks!
What should I prefer: Closing applications completely after use using task manager/back button or is it fine to use the home button and let them run in the background?
searching would have informed you its not good to use task managers/killers
I know, I read that. But I didn't really understand why. I mean an app that runs in the background still uses up ressources, doesn't it?
Lownita said:
I know, I read that. But I didn't really understand why. I mean an app that runs in the background still uses up ressources, doesn't it?
Click to expand...
Click to collapse
Depends on the app. If you leave music streaming in the background, yes, it will use some CPU, data, and battery. But if you leave a Notes app open, you only use a bit of RAM. It's okay to have apps sitting dormant in RAM since that's what RAM is for - helps apps open faster.
Like Darkside Agent said, stay away from task killers. Use the back button to close the app and the home button to leave them in the background.
Leave it all running... Plenty of RAM and Android is pretty good at memory management...
I am confused right now as to what to actually use when trying to close an app. I read that killing an app for RAM doesn't really help. So does this mean that I should just keep pressing the home button even if it leads to a lot of apps piling in the background? What do you do personally?
You can keep pressing back until the app exists, or you can press menu and see if the app has an exit button, or you can just pile apps in the background as you describe it and android will auto kill them when you are running low on ram.
I set the 'hold back button to force kill' option in cm7.
Interesting option, I avoid CM as it is bloated but do you know any other roms with similar function or how to enable it yourself?
franzks said:
I am confused right now as to what to actually use when trying to close an app. I read that killing an app for RAM doesn't really help. So does this mean that I should just keep pressing the home button even if it leads to a lot of apps piling in the background? What do you do personally?
Click to expand...
Click to collapse
Exiting via the back button "kills" an apps. Exiting via home button leaves it running so you can return to it if needed. A taskkiller is pointless as Android will restart a service almost immediately. Stop Maps in Running Services and see it return within 5sec. Lifehacker have some good info on Android taskkillers and why they are fairly pointless.
Sent from a phone with an app.
I use ALWAYS back button,but sometimes keeps running in background so then i use Advanced Task Killer Pro,and DIES.
Depends, browser I use home. Xda app I use back. You just get used to it. Try not to worry about.
Sent from my GT-S5830 using xda premium
I always use back button to closing an app. When you need to go back to an app later, you can use home button
usually back button to don't waste Ram.
I use back button to kill apps by long pressing it (ics final by jusada)...there is option in settings>application>developement> to enable this...NoT sure if its there in any stock rom ..
Sent from my GT-S5830 using Tapatalk
AFAIK back button should kill the app, there's some cases it doesnt, and home just keeps it on the background.
what is the fucntion of ICS third soft button
it is show off the apps on memory which is running on cash memory ?
how can I limited it ! I mean when I exist the app, I don't want put the app on cash memory !
because I find out some of app on cash memory, it can used over 100M on memory at tablet !
Its kind of a appswitcher. You can either slide the apps to left or right to close them or select an app to open it.
Sent from my HTC Glacier using xda premium
mansisingh said:
Its kind of a appswitcher. You can either slide the apps to left or right to close them or select an app to open it.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Its my favorite feature in ics lol
This quick app switching and previews of what the app looked like, bundled with ICS Browser + are the reasons I have not booted webOS on purpose since the first alpha CM9 dropped.
Its as intuitive as the cards, IMO, and an amazing feature of ICS.
AFAIK, ICS operates like all other android builds. In that its meant to fill your RAM with programs to about 75%, then it will start clearing out apps when you need the RAM. This is by design, and why so many Android "Experts" say you don't need, and shouldn't use, task killers. RAM takes the same amount of battery full as it does empty. So, as long as the app is written well it won't cause any excess battery drain to have it sit in your RAM. But, it will save you battery the next time you use it, instead of opening it fresh. All this goes out the window for poorly written apps that cause wake locks or continue to run when put to "sleep". YMMV
Sent from my Galaxy S II (i777)
Most use feature in CM9 for me.
more nice and usefull than before had to hold home button
I've noticed that the home launcher is being killed after opening apps such as google chrome snapchat or even gallery. It is annoying staying 5 seconds to see the launcher. Multitasking is almost impossible. How can I stop killing the home launcher?
cretu01 said:
I've noticed that the home launcher is being killed after opening apps such as google chrome snapchat or even gallery. It is annoying staying 5 seconds to see the launcher. Multitasking is almost impossible. How can I stop killing the home launcher?
Click to expand...
Click to collapse
Welcome to a phone which is poorly optimized, a ui which takes up a lot of memory and so on. And most of all, a discount mini version of a phone.
Sent from my LG-D620 using XDA Free mobile app
It is now 90% solved.. using RAM Manager pro with hard multitasking active, lock launcher in memory and VM heap size to 256. Also tried swap file but after creation it seems that it doesn't work after looking in memory info.