Heyho,
I'm an former iPhone user, and as we all know.. it doesn't support real multitasking..
But it saves much batterylife by freezing procecess of apps...
Now i wanted to ask if there is any app for Android wich can, for example, freeze an app that runs in background for like 5 minutes, unfreeze it and let it check its things, and then freeze again for 5 minute
Edit: Greenify (didn't exsit to time of posting)
Related
I have read that taskkiller is not necessary on Android as the OS will kill off running apps when it needs memory - what are people's thoughts on this?
Hmmm...I read somewhere (maybe on here) heard if the App is coded properly that when not in use it will be background so not take up memory.
Not too knowledgable, but in that case would imagine they are acting like a windows service so will be taking up memory somewhere....so perhaps what I read was nonsense
Well, I have stopped killing tasks and guess what - I notice no difference at all! Hero is just as speedy (or slow depending on how you wanna look at it!).
Interesting!
Killing truly idle applications wont have significant effect. There are however many applications which appear idle, but still drains resources. An example is Peep, the twitter client, which starts automatically even if there's no twitter account configured. It has some frequent checks that put load on the CPU and thus helps drain power. Killing it adds many hours of standby time.
i'm not using any task manager/killer, did try them for a couple of days, can't really tell the difference, except i was wasting time constantly killing apps :/
suisen said:
i'm not using any task manager/killer, did try them for a couple of days, can't really tell the difference, except i was wasting time constantly killing apps :/
Click to expand...
Click to collapse
Ditto... surely there is no need as the OS will kill a unused app if it needs the memory ??? I don't have any problem running any apps one after the other... they just load.
The only lag I get is while the handset starts a widget update, once they are started everything runs slickly.
I found it a little slicker without taskiller. Especially in the use of big apps like copilot or documents2go. It seems to be managing itself pretty well.
Yep. I can report that the phone is working very well without Taskkiller. I have uninstalled it now.
If you are reading this, give it a try for a few days and tell us what you think. You may be pleasantly surprised...
Ditto - I've removed taskiller so I don't get tempted. Surprise surprise, no problems, no lag, etc. Now mostly this is due to removing the clock and people widget, but memory management seems fine after playing many different games and browsing the internet.
I think a benefit to doing this is that you aren't going to get and bizarre problems caused by killing system processes by accident - ie you won't miss alarms or stop receiving email alerts.
Hi, after reading some information on the internet I have seen people have said that task killers dont help at all and it doesnt help save battery either. Can anyone confirm this?
Thanks
Alot of apps that you see running in Task Killers are apps that are on pause in the background.
What happens alot of the time if you kill them, that they restart again in a couple of seconds. And apps that are restarting the whole time will cost you more battery that just some apps on pause/sleep in the background.
So as far as i know, these days Task Killers dont help at all, they can even make it worse.
*If i am totally wrong about this, enlighten me*
Razje said:
Alot of apps that you see running in Task Killers are apps that are on pause in the background.
What happens alot of the time if you kill them, that they restart again in a couple of seconds. And apps that are restarting the whole time will cost you more battery that just some apps on pause/sleep in the background.
So as far as i know, these days Task Killers dont help at all, they can even make it worse.
*If i am totally wrong about this, enlighten me*
Click to expand...
Click to collapse
Agreed, I personally haven't seen an improvement in the past and there are a number of articles that say they are un-needed.
It's not needed because Android, having the Linux base, has good memory management which is different from Windows.
Thanks for this. As on my last android phones I spent about 10 minutes a day killing apps.
Razje said:
Alot of apps that you see running in Task Killers are apps that are on pause in the background.
What happens alot of the time if you kill them, that they restart again in a couple of seconds. And apps that are restarting the whole time will cost you more battery that just some apps on pause/sleep in the background.
So as far as i know, these days Task Killers dont help at all, they can even make it worse.
*If i am totally wrong about this, enlighten me*
Click to expand...
Click to collapse
You are right. Killing apps will make things worse. With the exception of an occasional rogue app, which can be killed fromt the default app management offcourse.
I hardly ever kill an app. Generally it's not necessary.
Seems like many applications spring back up after "killing" them though the Android task manager or any of the task managers available in market. Is annoying the hell out of me. If im not using the app I dont want it to.run in the background..
I understand that messaging applications need to run in background but not all.
How do you guys make sure
that any application which you close "remains" closed until the next time you open it?
Thank me if I helped you..
~n0tr1x on t989~
You might try Gemini app manager to disable auto start apps
Sent from MARVEL using Tapatalk 2 Beta-4
Easy Task Killer can help too..
use Easy Battery Saver too along with it!
Thanks.for your replies guys. However.i believe the main question here is,.how.to.stop these background app processes from running until the next time I start them manually.
Problem with task managers is that they stop these apps after a certain interval. Once they do, the.apps restart after 2-5 seconds. And.remain there till the next interval of the task killer is reached. This in turn take up more memory a compared to keep the running.. In addition, these apps run in the background on their own taking up a junk of memory/processor space..
Thanks again for your replies. Please correct me.if my understanding is wrong and you are feel otherwise.
Thank me if I helped you..
~n0tr1x on t989~
Those "apps" that you say keep opening are actually the processes running in the background. I know of many apps that keep re-enabling their processes after killing them. (IE: Facebook, some Google stuff, and a couple games that run in real-time)
Best solution: try to go into the app's settings and see if there is an option to disable anything that would require a background service to run, IE: sync, updates... If not, then just stop killing that app. Ignore it in the list or set a task killer to ignore it. If the app keeps re-opening, you killing it all the time is only doing bad because it puts more stress on the operating system because it has to take the time to reinitialize the app/service. If you are really that anal about background running apps, set android to limit a lower amount of background apps to run.
Like asdot suggested above use Gemini App Manager to disable the apps autostart permissions. If an app is set to automatically start after a certain intent is broadcast by the system (ie, at boot, or at a change in connectivity, etc.) you can use Gemini to stop that app from automatically starting. You can stop an app from automatically running in the first place instead if trying to kill it after it has started.
Hello!
I installed ES task manager today on my new Nexus 7 and I was shocked to see that several apps are consuming 20mb+ of RAM when I don't even have them open, such as Titanium Backup, Facebook Messenger, PIE Controls, Auto Hide Softkeys. Even apps like YouTube, Gallery, Chrome, Currents and Hangouts seem to be running and using RAM and I have never opened any of these applications before. The actual app switcher shows that I have no apps open, yet ES Task Manager reports that 25% of my CPU is being used. All in all, an almost fresh install of Android idling is consuming 1GB of ram and 1/4th of my CPU time.
I have Googled this issue and discovered that many people are annoyed at developers who have background services, and sometimes even refuse to use an app that has such background services, but I haven't been able to discover why these background services use so much RAM (or even why titanium needs a background service), and I would really like to be able to just kill Chrome, Youtube, Currents etc because I never use these, but of course when I kill them in ES Task Manager they re-open within several minutes.
Can anybody shed some light on what's going on here? From what I can gather after searching around the forums, some people advocate the use of task killers, and some people also say killing all these services and apps just makes battery life even worse.
Edit: google+ is using 20mb of ram and I never even use it-- why!
If you are rooted you can use apps like Greenify to pause them temporarily until you run them. You can also use apps like Clean Master that will kill all task on every screen off. Ultimately you can remove these apps that are taking up a lot of ram as the best solution.
youngnex said:
If you are rooted you can use apps like Greenify to pause them temporarily until you run them. You can also use apps like Clean Master that will kill all task on every screen off. Ultimately you can remove these apps that are taking up a lot of ram as the best solution.
Click to expand...
Click to collapse
Wow, didn't know something like greenify existed, thank you!
My background apps are killed way too often. Is it possible to change that behaviour? Even music apps are killed while I'm playing music.
I have tried several custom roms and kernels but nothing seems to change the settings. Is either able to change RAM management settings?
I have also tried several apps that claim to be able to change RAM management settings without success.
Disabling battery optimisation doesn't help.
I have uninstalled unused apps and disabled autostart (boot completed receiver) for non-essential apps to reduce RAM usage.
When I use a RAM monitor it will show RAM usage at ~75% when apps are killed.
My old phone (Note 4) only had 3 GB ram but could still keep more apps in memory.
I don't have that problem.
Have you tried Greenify or similar app to hibernate unwanted apps running in the background? They will only open then when being used and will automatically hibernate again when closed.
ChazzMatt said:
I don't have that problem.
Have you tried Greenify or similar app to hibernate unwanted apps running in the background? They will only open then when being used and will automatically hibernate again when closed.
Click to expand...
Click to collapse
That's the reverse of what I'm looking for. I want the apps in the background to keep running.
Telorast said:
That's the reverse of what I'm looking for. I want the apps in the background to keep running.
Click to expand...
Click to collapse
Then you misunderstood what I wrote. Read it again.
It's exactly what you want, because then apps you don't want running won't take up your RAM and kick off the apps that you do want running. Like your flashlight app should NOT be running the background all the time. One example. Lots of devs think their apps are most important and should always run in the background, so when you "launch" them they are there instantly.
Like I said, I don't have your issue. My apps I WANT running stay running.
If you hibernate the UN-wanted apps, that will give more freedom to apps you DO want running in the background.
There are other apps besides Greenify which may do that task even better, it's just the most well known. It shows you complete list if apps running in the background and you can choose which you WANT to run and which you want to stay killed until you choose to activate them. Those apps will be forced hibernated from then on -- until you manually activate them. When you close them, they will STAY closed and not run in the background sucking up your RAM. It also allows you to go through your entire inventory and decide yes/no. For instance, weather widget, email, yes. Benchmarking app, NO.
Worth a try. Installed Greenify and added most apps with ignore background-free.
Telorast said:
Worth a try. Installed Greenify and added most apps with ignore background-free.
Click to expand...
Click to collapse
I even hibernate alleged background free apps, just in case.
ChazzMatt said:
Lots of devs think their apps are most important and should always run in the background, so when you "launch" them they are there instantly.
Click to expand...
Click to collapse
VERY TRUE!
This always infuriated me, not just on phones, PCs too, all the way back to the DOS days. An obsession with running in the background, as if it's particularly clever. :cyclops:
I've also found that turning off battery optimization for apps I don't want killed helps. I've had the same experience with music and podcast apps getting killed in the background and turning off their battery optimization usually fixes it.
There are some simple things to try that do not require any special apk's. One is to look in the apps section of the "Developer options" sub-menu. The default settings work well in most instances. Perhaps you accidently enabled closing of apps when a background limit has been reached or have ticked force closure of apps on exit.
Another place to look is in the "Power saving exclusions" sub-menu in the Battery settings. Music makes some boring forms of exercise less tiresome and provides additional motivation for activities that are challenging but fun (mountain biking). The music should not stop, but it might for default settings. Enabling a power saving exclusion for your music app will keep it running.
ChazzMatt said:
Then you misunderstood what I wrote. Read it again.
It's exactly what you want, because then apps you don't want running won't take up your RAM and kick off the apps that you do want running. Like your flashlight app should NOT be running the background all the time. One example. Lots of devs think their apps are most important and should always run in the background, so when you "launch" them they are there instantly.
Like I said, I don't have your issue. My apps I WANT running stay running.
If you hibernate the UN-wanted apps, that will give more freedom to apps you DO want running in the background.
There are other apps besides Greenify which may do that task even better, it's just the most well known. It shows you complete list if apps running in the background and you can choose which you WANT to run and which you want to stay killed until you choose to activate them. Those apps will be forced hibernated from then on -- until you manually activate them. When you close them, they will STAY closed and not run in the background sucking up your RAM. It also allows you to go through your entire inventory and decide yes/no. For instance, weather widget, email, yes. Benchmarking app, NO.
Click to expand...
Click to collapse
Been using Greenify for a bit now and doesn't seem to help much. It shows a bunch of hibernated apps but multitasking is still nearly impossible.
I had assumed the problem was related to the Mem Free settings rather than actual free memory but no one here has mentioned it. Is that because no one else thinks it's the problem or maybe I have misunderstood what those settings do?
I thought apps were free to use as much memory as they want until certain thresholds on total memory usage were met, then the system would ask or force apps to release memory.
Apps that let you edit those settings usually shows several thresholds where the system gets progressively more aggressive at freeing memory as memory is running out. But they all look hopelessly out of date so maybe it works completely differently today?