How to keep an app Alive in background - Android Q&A, Help & Troubleshooting

Hi guys,
I'll try to be understandable.
I have 2 apps (app1 and app2), I want to be able to use app1 while app2 keep running in background, and switch to app2 while app1 keep running in background.
I know that Android kills app if it needs RAM, mine has 6gb RAM maybe it's not enough or simply not possible.
Let me know about it, if I'm looking for something not possible.
I found some answers on internet but I think I didn't use them properly.
I heard about freeform mode (using a kind of floating apps).
I though about using split screen, it works, but I used the built-in feature and I can't resize both split screens. It is forced to 50/50.
I tried to use the "Don't optimize" feature, "Standard limit" in battery settings etc... but it doesn't work properly with my apps.
Maybe it comes from the apps themselves ?
Thanks in advance,

Hi
You can check Battery in settings, Allows apps to continue running the background with high power consumption.
Gaarnom said:
Hi guys,
I'll try to be understandable.
I have 2 apps (app1 and app2), I want to be able to use app1 while app2 keep running in background, and switch to app2 while app1 keep running in background.
I know that Android kills app if it needs RAM, mine has 6gb RAM maybe it's not enough or simply not possible.
Let me know about it, if I'm looking for something not possible.
I found some answers on internet but I think I didn't use them properly.
I heard about freeform mode (using a kind of floating apps).
I though about using split screen, it works, but I used the built-in feature and I can't resize both split screens. It is forced to 50/50.
I tried to use the "Don't optimize" feature, "Standard limit" in battery settings etc... but it doesn't work properly with my apps.
Maybe it comes from the apps themselves ?
Thanks in advance,
Click to expand...
Click to collapse

hiepv said:
Hi
You can check Battery in settings, Allows apps to continue running the background with high power consumption.
Click to expand...
Click to collapse
There is an option in developer settings which allows to choose how many apps you want running in background before system kills them.

Related

[Q] Question about keeping background apps off

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!

[Q] when minimize, app hibernating or running in background?

well, on the ipad, or any ios device, when apps are minimize, they "freeze" or hibernate, using minimal resources. (correct me if i'm wrong)
android is good at multi tasking, but i hope there's more control over this.
running in the background is not always a good thing.
example, while browsing, the page is loading a youtube video, i minimize and go have use another app, the browser video will continue to load while i'm in the other app. even if i lock my device, the browser video continue to load.
thats good if i want to multi task.
but sometimes, if i'm playing a game, i just want "freeze" it and continue later, maybe few hours later. so i minimize it and lock screen. but this may cause the device to not enter "sleep mode" and draining power as if it was running.
not all apps behave this way, i'm confuse as well. this is not a tab specific problem, my sgs2 as well, maybe all android device too.
my friend can calmly press the home button and lock screen on her ipad and never worry about power.
but i have to worry constantly whether or not the minimized app is draining power.
is there a way to know the minimized app is still running at back ground or able to "freeze"?
or better yet, is there a way to choose how we want it?, free or running at background after minimize.
PS: please dont recomend me to buy the ipad, i'm more of a android person.
Ray1 said:
well, on the ipad, or any ios device, when apps are minimize, they "freeze" or hibernate, using minimal resources. (correct me if i'm wrong)
android is good at multi tasking, but i hope there's more control over this.
running in the background is not always a good thing.
example, while browsing, the page is loading a youtube video, i minimize and go have use another app, the browser video will continue to load while i'm in the other app. even if i lock my device, the browser video continue to load.
thats good if i want to multi task.
but sometimes, if i'm playing a game, i just want "freeze" it and continue later, maybe few hours later. so i minimize it and lock screen. but this may cause the device to not enter "sleep mode" and draining power as if it was running.
not all apps behave this way, i'm confuse as well. this is not a tab specific problem, my sgs2 as well, maybe all android device too.
my friend can calmly press the home button and lock screen on her ipad and never worry about power.
but i have to worry constantly whether or not the minimized app is draining power.
is there a way to know the minimized app is still running at back ground or able to "freeze"?
or better yet, is there a way to choose how we want it?, free or running at background after minimize.
PS: please dont recomend me to buy the ipad, i'm more of a android person.
Click to expand...
Click to collapse
Run an app called os monitor or watch dog and you can see what app is using up resources.
Sent from my GT-P7510 using Tapatalk
If an App is running in the background (not to be mistaken with Services or System Apps like the browser) you usually should have a notification in the system bar;
If it doesnt show, then the app is hibernating.
For the majority of apps it's just to switch the home button and don't worry, this is how it should be. However, a few games that I've tried are still using CPU resources if I don't select quit from within the game. You can use the in built Task manager to check this.
I don't worry for anything but games - and I just check the behavior once after install.

When you hit the home button, does the program close?

When you have a program open, example is a video player. When I hit the home button does that program really fully close? Why I ask this is because I'll open up a web browser and input a web page. Before the web page even fully loads I'll hit the home button. Then even after a few minutes I'll load up that same browser and that page that didn't fully load will be there loaded up. I just want to make sure that when I close a program, it really is closed. That's all.
Hitting home does not "Close" or quit the program it rather puts it in the back round to fully quit it you must hit the recent apps button (Third on the left) and swipe the app away or get a task manager for those pesky back round apps.
Tech Faded said:
Hitting home does not "Close" or quit the program it rather puts it in the back round to fully quit it you must hit the recent apps button (Third on the left) and swipe the app away or get a task manager for those pesky back round apps.
Click to expand...
Click to collapse
Actually swiping apps away from recent list doesn't really close the apps. It just removes them off the recent list. Only a task manager can do that or going into settings, then apps, then force stopping it. But really,Android manages the memory very well itself. Alot of times, the way Android works, manually stopping a program will be more harm than good. Most of the time Android will just pull it back up itself therefore causing more CPU usage for that task tl bring it back. ANDROID keeps some apps semi-loaded. Ones it feels with load faster once you launch it since its already partially loaded. ANDROID is not like a PC where the processes in background will automatically slowbthings down or drain battery faster. Only certain apps that truly run in background can have that effect if too many loaded up. Whatever you do, don't use any auto memory killers or auto task managers or battery saver apps like juice defender, etc... those do more harm than good.
Unless your tablet is running with alot of lag, just try to ignore or resist the urge to keep constantly killing apps or whatever. You will see Android itself does a great job at managing it and will free up memory when actually needed. I'm still trying to do the same also resisting the urge. I just use Asus built in Task manger widget to see what's running in the background. If something clearly not needed then ill kill it. Beware though not to kill system apps or you might cause them to crash or be unstable.
A good app I came across is called BetterBatteryStats. Made by an xda member. Just type name of app in search box here in forum. That app will let you see what's truly running in the background and using up most battery or CPU processes. Has some great tips in there also in help section. IT LET me see how the Google currents app, although I wasn't using it, kept running in the background and using up processes and adding to battery drain. I would always see it pop up in my task manager although I never opened it and I have the refresh data set to long intervals. So it's basically a rouge app..lol. I uninstalled that mofo. Its a great app but runs to much in background regardless of data refresh settings and sometimes doesn't allow prime to stay in deep sleep when screen is off. Partial wakelocks, kernel wakelocks, etc...are all things you have to look over when determining what apps are causing most battery drainage or not allowing prime tl stay in deep sleep. Because they will partial wakelock n get data or whatever. It gets technical..lol learned alot from that one app. Free here in xda forums .
demandarin said:
Actually swiping apps away from recent list doesn't really close the apps. It just removes them off the recent list. Only a task manager can do that or going into settings, then apps, then force stopping it. But really,Android manages the memory very well itself. Alot of times, the way Android works, manually stopping a program will be more harm than good. Most of the time Android will just pull it back up itself therefore causing more CPU usage for that task tl bring it back. ANDROID keeps some apps semi-loaded. Ones it feels with load faster once you launch it since its already partially loaded. ANDROID is not like a PC where the processes in background will automatically slowbthings down or drain battery faster. Only certain apps that truly run in background can have that effect if too many loaded up. Whatever you do, don't use any auto memory killers or auto task managers or battery saver apps like juice defender, etc... those do more harm than good.
Unless your tablet is running with alot of lag, just try to ignore or resist the urge to keep constantly killing apps or whatever. You will see Android itself does a great job at managing it and will free up memory when actually needed. I'm still trying to do the same also resisting the urge. I just use Asus built in Task manger widget to see what's running in the background. If something clearly not needed then ill kill it. Beware though not to kill system apps or you might cause them to crash or be unstable.
A good app I came across is called BetterBatteryStats. Made by an xda member. Just type name of app in search box here in forum. That app will let you see what's truly running in the background and using up most battery or CPU processes. Has some great tips in there also in help section. IT LET me see how the Google currents app, although I wasn't using it, kept running in the background and using up processes and adding to battery drain. I would always see it pop up in my task manager although I never opened it and I have the refresh data set to long intervals. So it's basically a rouge app..lol. I uninstalled that mofo. Its a great app but runs to much in background regardless of data refresh settings and sometimes doesn't allow prime to stay in deep sleep when screen is off. Partial wakelocks, kernel wakelocks, etc...are all things you have to look over when determining what apps are causing most battery drainage or not allowing prime tl stay in deep sleep. Because they will partial wakelock n get data or whatever. It gets technical..lol learned alot from that one app. Free here in xda forums .
Click to expand...
Click to collapse
I was under the assumption that ICS fixed that? I suppose I was mistaken I apologize for my misunderstanding.
Demandarin, what makes you think swiping doesn't close a program? It does and its very obvious it works, just swipe then open the same program and you will see it starts over and will not be where you left off.
Try Settings > Developer Options > Don't Keep Activities. Sounds like it will fully close tasks once they are closed.
atgmartin said:
Try Settings > Developer Options > Don't Keep Activities. Sounds like it will fully close tasks once they are closed.
Click to expand...
Click to collapse
This is a very bad setting to enable if you ever have to switch back and forth between two different activities (for example email & web browsing). In general you should just leave the developer options alone.
As for closing apps.. why does it matter?
Apps that are not actively running don't use CPU and therefore don't use battery. Some apps sync information in the background, such as weather apps and email and while they do this battery is being used, however you can optimize the frequency of the updating to preserve as much battery life as possible.
In general unless you have experiencing performance issues, let Android manage itself.
If you absolutely need to turn off running apps, use the Asus Task Manager widget that comes pre-loaded on your tablet. You can use the Asus Task Manager to kill individual apps or all apps with a single click.
ON ICS, the swipe does stop the task running in the background, but I've seen where it the app may begin again, but as a background activity as almightywhacko describes.
People don't understand. Apps DON'T "run" in the background. They only run when you interact with them.
Buff McBigstuff said:
People don't understand. Apps DON'T "run" in the background. They only run when you interact with them.
Click to expand...
Click to collapse
Well, it depends. Apps don't run in the background like they do in windows, but some apps do continue to run processes in the background like data syncing and what not. However, it the app doesn't do this stuff then it only holds its state.
Also, I have not seen swiping recent apps closing apps. I think it is just happenstance if an app is closed by swiping it off the recent apps. Looking at the logging and monitoring the app state I have seen no correlation between running/not running apps and the recent app list.
However, as other people said, manually closing apps in Android will most likely reduce your performance rather than do anything beneficial.
I always get mad at those stupid apps that pretend to be providing a service. They won't go away. even if kill them they just come back(like Kenny). The app that likes to bother me the most is Zen pinball. I really like the game but it is always popping up prompting me to enable openfeint which I had already signed up for. I press enable but it still does not go away.
UmbraeSoulsbane said:
Well, it depends. Apps don't run in the background like they do in windows, but some apps do continue to run processes in the background like data syncing and what not. However, it the app doesn't do this stuff then it only holds its state.
Also, I have not seen swiping recent apps closing apps. I think it is just happenstance if an app is closed by swiping it off the recent apps. Looking at the logging and monitoring the app state I have seen no correlation between running/not running apps and the recent app list.
However, as other people said, manually closing apps in Android will most likely reduce your performance rather than do anything beneficial.
Click to expand...
Click to collapse
Only if they spawn a service. As far as activities, which most people would consider to be the "app" part, those do not run in the background. It just sits until it gets killed or used.

EASY way to instantly exit current app?

...and I don't mean 'minmize' like what pressing the home or back button does. (which merely puts it in the multitasker menu list, still open.)
I mean closing it like when you swipe it out of the menu list. (which are far as I can tell, seems to close it off enough to stop what it's doing and free up the memory it was using!)
Sometimes I want to just close an app since I know I won't be using it for a while and I want to conserve cpu/memory/battery - or merely manage the list of things in my multitask list. kinda like on Desktop. (you don't want every app on your pc open all at once, do you, do you?!) and I just want a simple way like on the desktop to close that app when I want to close it.
SO: Is there some app that can assign a custom screen gesture (like the lovely letter C for 'close') to perform 'fully exit current app' or some solution like that? I started to research, but couldn't seem to find one very quickly, so thought I'd ask here, at THE place to ask.
also I apologise for using things like Windows terms ('minimize'), i know that's not how it works in android. But you do know what I mean.
Thanks
This is a question that a lot of people ask when moving to Android and the answer simply is, forget about it.
Android handles processes and memory in a completely different way to Windows. When an app is "minimized" it obviously leaves a footprint in the memory, but it uses no CPU (unless it's a polling app or something that keeps alive for a specific purpose).
Just trust Android to handle memory management - it does a very good job of it.
If you really, really MUST do something about it then the best thing you can do is get something like Juice Defender (there's tons of similar apps) and make it kill apps periodically. Most apps that people use for this type of purpose are merely placebo, but if it makes you feel better then I guess it's serving a purpose.
Archer said:
This is a question that a lot of people ask when moving to Android and the answer simply is, forget about it.
Android handles processes and memory in a completely different way to Windows. When an app is "minimized" it obviously leaves a footprint in the memory, but it uses no CPU (unless it's a polling app or something that keeps alive for a specific purpose).
Just trust Android to handle memory management - it does a very good job of it.
If you really, really MUST do something about it then the best thing you can do is get something like Juice Defender (there's tons of similar apps) and make it kill apps periodically.
Click to expand...
Click to collapse
Thanks for your answer. I can sense you have wisdom and experience in your words there, but I want to probe a little further.
surely there can be an almost macro-like (again, windows terminology, sorry) functionality, that can be assigned to a gesture swipe that can emulate pressing home button, then swiping the bottom item away from the multitask menu? (which is always the one you just 'minimized')? Could an app like Tasker even do it?
i agree that good memory management is a beautiful thing, but there really should be manual control of closing apps, my reasons above are stated.
i wouldn't touch automatic time-based closing, i sometimes have saved states in apps and wouldn't want them closed when i don't want them closed.
Most apps that people use for this type of purpose are merely placebo, but if it makes you feel better then I guess it's serving a purpose.
Click to expand...
Click to collapse
you really think it's all placebo, and that say, running 50 apps in android with finite set amount of ram on the device is all fine simply due to memory management?
is me experiencing lag in some android apps (or battery draining faster than I'd like), then closing off several running apps in the multitask list, then noticing the problem go away, all placebo????? what about google maps, say?! I'd love a one-step swipe action to CLOSE google maps when I'm done with it, not having to press home button, then multitask button, then swipe away google maps. (I know when minimized it consumes nothing like it does when open, but I think still it consumes more than if it were fully closed...)
it's not just about memory. edit: and I already stated in addition, I often want to simply manage what I have open. this is a basic function in desktop OSes, I think it's time it came to mobile. if not officially, there surely must be some hack/tool to do it. :S
download a task killer app with a widget.
press home button and press the widget and you're done
If you're using AOKP based ROM then there is hold back to kill in Settings > ROM control > general UI
Sent from my GT-I9100 using 1st ROM
Hold homesçern key
Sent from my ST23i using xda app-developers app
jman2131 said:
download a task killer app with a widget.
press home button and press the widget and you're done
Click to expand...
Click to collapse
that's about 2/3 the way towards the current 3-step solution though :/.
Am I to be amazed that a function to put this simple task into a single gesture hasn't been done? or isn't possible? it HAS to be possible. Otherwise I'd be flabbergasted.
I have googled further and just can't seem to find something :|.
WAIT! I think I have! here. https://play.google.com/store/apps/details?id=com.goodmooddroid.gesturecontroldemo&hl=en it has a "kill task" function that you can set up a custom gesture for. it's a start.
however I'm getting a "ERROR! No ROOT permissions?" error despite being rooted with supersu and successfully using other root apps etc, so I've emailed the dev and hope I can get it working :S.
But still, it seems a little clunky the offering of custom gesture types. I can't set a nice curvy gesture defined by tracing it on the screen. oh well - it's a start.....
jootanen said:
If you're using AOKP based ROM then there is hold back to kill in Settings > ROM control > general UI
Click to expand...
Click to collapse
That seems the holy grail! too bad I'm on stock jb with plans for upgrading to CM .....

Suggestions for Greenify

Greenify is the most useful app yet made for Android but still so much can be done to make it better so I thought to make a thread to make Greenify better and I hope @oasisfeng would look at it.
Post your feature requests and suggestions here in this thread.
My suggestions: I think there should be an option, like a timer, after which greenify automatically greenifies apps even when the screen is on so that if I use a lot of apps continuously and then without turning the screen off once I start to watch a movie or play a game or anything on a phone, greenify should hibernate the background triggered apps automatically and save battery and provide better overall performance.
I know Tasker can do that but personally I don't like using Tasker because of its complex UI so I've set a shortcut on my phone when I double tap the menu button it triggers the hibernate now shortcut of greenify. But it would be of much help if greenify does it itself, having a timer of something between 1min-1hour to greenify apps automatically.
Also I would like the ram usage of greenify to be less, as sometimes it starts using as much as 60-70mb of ram, which is quite much. I hope you can find a way to reduce the ram usage.
If developer read this, i would like to have an option to disable startup apps.
If you have too much apps that starts in same time when you turn on your phone, you will have a slow boot..
I think that this is option that should exist in such great app..
And yes, some timer should exist also...
@oasisfeng
Hi sir. & tnx for the amazing greenfy.
As i talked with you I have some suggestions for greenfy & i want everyone to share more suggestions:
1) Add an option to put some apps in a group. Then put them in hibernation or degreenfy them with one click or widget.
Let me explain: for example i use some sound mods that keep special apps in memory. But when i dont listen to music i dont need them. So i want them to be in hibernation. But when i want to listen to music, i need to degreenfy them with one click
2) Add an option to deactivate & freeze some apps temporarily & easily in the greenfy app.
For example i dont want the google play services be in the memory all the time. I just need it when i want to use a google app. So i freeze it in the greenfy. & when i need it i defrost & activate it.
3)Add an option to force greenfy some apps instead of cut off the services one by one. Or an option to choose the services that we dont need them. & deactivate them.
4) Add an option to degreenfy some apps by a period of time & put it back in hibernation after that automatically.
For example: i use a calander app. That if i put it in hibernation the date that it shows freezes & sticks on a certain day. But if there be an option to degreenfy it daily for an hour automatically & put it back, it was great.
5) Add an option to change the cpu governer from ondemand(or balance) to power save automatically when the screen turns off. & when it turns on or we receive a call or notificstion it goes back to ondemand( or balance)
6)Add an option to not put in hibernation for some apps when they are downloading or uploading. ( i think it's not possible to determine this ) but just a suggesttion)
7) Add an gaming mode. That greenfy put all of the apps in hibernation instead of call,message, or apps that we mention.
kassaaam said:
Greenify is the most useful app yet made for Android but still so much can be done to make it better so I thought to make a thread to make Greenify better and I hope @oasisfeng would look at it.
Post your feature requests and suggestions here in this thread.
My suggestions: I think there should be an option, like a timer, after which greenify automatically greenifies apps even when the screen is on so that if I use a lot of apps continuously and then without turning the screen off once I start to watch a movie or play a game or anything on a phone, greenify should hibernate the background triggered apps automatically and save battery and provide better overall performance.
I know Tasker can do that but personally I don't like using Tasker because of its complex UI so I've set a shortcut on my phone when I double tap the menu button it triggers the hibernate now shortcut of greenify. But it would be of much help if greenify does it itself, having a timer of something between 1min-1hour to greenify apps automatically.
Also I would like the ram usage of greenify to be less, as sometimes it starts using as much as 60-70mb of ram, which is quite much. I hope you can find a way to reduce the ram usage.
Click to expand...
Click to collapse
Alright im not oasisfeng but i can certainly answer some questions as to why this might be possible atm
First, the so-called hibernation whem screen on will only drain your battery futher and will cut-off android system's background process for apps. To put it shortly, it'll cut-off the functions of apps that needs another app for its services.. Some instances includes xposed for whatsapp and the whatsapp itself and others alike. This will have an excessive power drain due to two reasons:
1.) Greenify will constantly monitor background time when screen on hence battery drain
2.) Hibernating apps while screen is on will only re-trigger it, as an example is facebook/messenger.. As hibernating them screen on would only awaken it again after a few seconds which results in more wakelocks and more unneccesarry battery drain
And for the ram usage i have never encountered such, the biggest i have is 11 mb so im quite puzzled.. What services are running in your greenify? I personally disable campaign tracking and analytics services to minimize ram usage
mire777 said:
If developer read this, i would like to have an option to disable startup apps.
If you have too much apps that starts in same time when you turn on your phone, you will have a slow boot..
I think that this is option that should exist in such great app..
And yes, some timer should exist also...
Click to expand...
Click to collapse
Disabling startup apps is the job of other 3rd party apps such as appopsxposed and bootmanager.. Greenify hibernates but not limits. You can never have too much butter on one bread sir

Categories

Resources