Alter automatic hibernation sometimes a app properties windows remains opened after forced shutdown is executed. No particular app.
Related
auto hibernate when app is closed : eg. FB, music players many other apps & services stay on even no need after closing.
If anybody know how to auto stop these with other apps or tricks, plz let me know!?
Per App Hacking doesn't help..
------
auto start when screen is on : eg. I don't need clean master to stay on when I'm not on wifi and screen is off.
again, any workaround for this?
Greenify is already the greatest app out there, but if it had these features, it would b God of apps IMHO
kennyk09 said:
auto hibernate when app is closed : eg. FB, music players many other apps & services stay on even no need after closing.
If anybody know how to auto stop these with other apps or tricks, plz let me know!?
Per App Hacking doesn't help..
------
auto start when screen is on : eg. I don't need clean master to stay on when I'm not on wifi and screen is off.
again, any workaround for this?
Greenify is already the greatest app out there, but if it had these features, it would b God of apps IMHO
Click to expand...
Click to collapse
I think that you have not understood the working of Greenify correctly. It comes into play for hibernation only after the screen is off. When screen is on, it merely collects info about the apps that are running, closed etc to determine which apps are to be hibernated once screen is off.
Reg. auto hibernation, do you have root and have you enabled it in Device Administrator and Accessibility under Settings? Under which mode are you running Greenify: Root, Boost or Unrooted? And have you enabled Auto hibernation within Greenify and selected the apps to be greenified?
Check the thread title
tnsmani said:
I think that you have not understood the working of Greenify correctly. It comes into play for hibernation only after the screen is off. When screen is on, it merely collects info about the apps that are running, closed etc to determine which apps are to be hibernated once screen is off.
Reg. auto hibernation, do you have root and have you enabled it in Device Administrator and Accessibility under Settings? Under which mode are you running Greenify: Root, Boost or Unrooted? And have you enabled Auto hibernation within Greenify and selected the apps to be greenified?
Click to expand...
Click to collapse
It's a wish list. you don't understand what wish list is?
I fully understand how Greenify works.
Use Tasker and task kill plugin.
And for Greenify create hibernate shortcut and don't forget that it won't hibernate of application is in recent Apps list.
It's easy to kill every app on exit.
Just use LMT(PIE) app , and instead of standard ''home, or back button'' use ''KILLAPP'' button from PIE menu.
In combination with greenify it works fine.
I was think to use only PIE(pie ''kill app process'' on exit), but this is not the same, greenify realy put this apps in hibernation.
So i must use combination of these 2.
Would be great, that greenify do this itself..
I have greenify installed on xiaomi redmi note 4 snapdragon (mido) on lineageOS 13 with xposed(v87) module enabled and donation apk installed. There is a weird error happening with greenify installed. Whenever I open shareit app to send something, it freezes as soon as it tries to discover greenify on app tab. There after it stops responding until it Force closes/crashes.
This problem is specific to greenify v3.6.x and upto 3.5.2 everything works smooth. Following features as enabled-
1. xposed module
2. aggressive doze
3. wake up tracing and cut off
4. automated hibernation
5. xposed settings - doze on go, wake up coalescing, telephony wake up, dont remove notification, block app state abuse, GCM push.
Please consider looking into it as shareit is really useful app and i dont seem to use it.
Although on nougat shareit and greenify behaves properly.
souravipc53 said:
I have greenify installed on xiaomi redmi note 4 snapdragon (mido) on lineageOS 13 with xposed(v87) module enabled and donation apk installed. There is a weird error happening with greenify installed. Whenever I open shareit app to send something, it freezes as soon as it tries to discover greenify on app tab. There after it stops responding until it Force closes/crashes.
This problem is specific to greenify v3.6.x and upto 3.5.2 everything works smooth. Following features as enabled-
1. xposed module
2. aggressive doze
3. wake up tracing and cut off
4. automated hibernation
5. xposed settings - doze on go, wake up coalescing, telephony wake up, dont remove notification, block app state abuse, GCM push.
Please consider looking into it as shareit is really useful app and i dont seem to use it.
Although on nougat shareit and greenify behaves properly.
Click to expand...
Click to collapse
Try disabling aggressive doze. It buys little/nothing in battery savings while introducing a host of other issues. May or may not fix your specific issue but easy enough to try. Toss in a reboot after twiddling the setting to insure a clean test.
Since the first time I used greenify I thought it was strange that I had to add manually each of the 100 apps I have to hibernation (plus everytime I install a new one), but I never found anyone with the same problem. I wanted to know if there is some way to make greenify hibernate all apps with exceptions instead of manually add each one of them.
Also, my phone isn't rooted (warranty issues, going to return my phone soon), so I have to see that black screen when I lock my phone. However, sometimes I turn of my phone off and on after some seconds and it's terrible to have to stop the hibernation process. I wanted to know if there is a way to add a 5 minutes delay before it starts to hibernate things.
TL;DR:
- How to select all and use exceptions instead of selecting the apps you want to hibernate.
- How to add a 5 min delay before hibernation process starts after the screen is locked (on non-rooted phone).
Kinark said:
Since the first time I used greenify I thought it was strange that I had to add manually each of the 100 apps I have to hibernation (plus everytime I install a new one), but I never found anyone with the same problem. I wanted to know if there is some way to make greenify hibernate all apps with exceptions instead of manually add each one of them.
Also, my phone isn't rooted (warranty issues, going to return my phone soon), so I have to see that black screen when I lock my phone. However, sometimes I turn of my phone off and on after some seconds and it's terrible to have to stop the hibernation process. I wanted to know if there is a way to add a 5 minutes delay before it starts to hibernate things.
TL;DR:
- How to select all and use exceptions instead of selecting the apps you want to hibernate.
- How to add a 5 min delay before hibernation process starts after the screen is locked (on non-rooted phone).
Click to expand...
Click to collapse
No need to add your entire app suite to Greenify on recent Android versions; Marshmallow/Nougat/Oreo do a good job reining in background tasks via doze. That said, occasional bad actors may need some additional attention. Identify and add those to Greenify. Leave the rest out.
I don't believe there is a way to add a hibernation delay on unrooted devices. Make sure you are not using deep/aggressive hibernation which can trigger the behaviors you describe.
I'm emulating DOS inside Android because my calendar program, Lotus Agenda, is on that platform. The problem is that as soon as I switch to another app, or the screen turns off, the program goes in idle mode and the clock stops ticking, so the alarms don't go off. This happens even when I disable battery optimization. Does anyone have a solution?
P.S. battery drain shouldn't be an issue, because I use a program called Dosidle, which lowers CPU usage drastically. The emulator I use is called Magic Dosbox.
Bump.
@emanresu2
That's Android's default behaviour. Process priority is managed by the OS. If an app is in the foreground, it will run with foreground priority. If an app is not in the foreground, it will not run with foreground priority.
If you're on a rooted Android OS then you can try to change an app's priority. But keep in mind, that such a change will be overwritten by the Android OS, after some time, when OS thinks it was necessary to give the process another priority.
Code:
su
renice <PRIORITY> <PID>
More info here.
i was wondering..... some apps like greenify or superfreezZ use accessibility usage to track the app behaviour and auto hibernate them, but since android 9 there is a new command to restrict the background activity of an app and it is RUN_ANY_IN_BACKGROUND
you can simply enable in app info>battery>background restriction set to RESTRICT.
is it a "better" way to hibernate an app and stop all trackers, alarms and services that DRAIN the phone battery? or maybe it's is less powerfull than "force stop" the app?
how does compare DOZE to RUN_ANY_IN_BACKGROUND ? i suppose 1st is a generall switch off for all apps, BUT only on screen off. when you use the phone the "bad" app could continue to do what he wants, wakelocks, call some strange domains to receive or updload datas.... BUT WHAT IF it is restricted by RUN_ANY_IN_BACKGROUND? the app is not force stopped but should be something like hibernated when it's not foreground....?
i found some info here
App Power Management | Android Open Source Project
source.android.com
realista87 said:
i was wondering..... some apps like greenify or superfreezZ use accessibility usage to track the app behaviour and auto hibernate them, but since android 9 there is a new command to restrict the background activity of an app and it is RUN_ANY_IN_BACKGROUND
you can simply enable in app info>battery>background restriction set to RESTRICT.
is it a "better" way to hibernate an app and stop all trackers, alarms and services that DRAIN the phone battery? or maybe it's is less powerfull than "force stop" the app?
how does compare DOZE to RUN_ANY_IN_BACKGROUND ? i suppose 1st is a generall switch off for all apps, BUT only on screen off. when you use the phone the "bad" app could continue to do what he wants, wakelocks, call some strange domains to receive or updload datas.... BUT WHAT IF it is restricted by RUN_ANY_IN_BACKGROUND? the app is not force stopped but should be something like hibernated when it's not foreground....?
i found some info here
App Power Management | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
Force Stop = "Hibernate"
Force Stop = App is killed and removed from memory, and (for the most part) not be able to start itself up again. User can. I read you asked the exact same question elsewhere and some talked how apps can restart themselves. Yes, its true BUT its the exceptioopn, not the rule. The only app that ciones to mind at the moment in my past is Google Play. His statement is misleading in practical everyday use. Test it for yourself.
I havent used it, but, RUN_ANY_IN_BACKGROUND explicitly requires the "deny" or "allow" attribute. The app is still in memory and therefore would have some possibility of bringing itself back to life; much more so than a force-stop. Some apps are developed with running a service as a foreground app. Also, RUN_ANY_IN_BACKGROUND is a TESTING feature of android.
ie Force Stop > RUN_ANY_IN_BACKGROUND
I have a hot spot on my home screen (custom launcher allowing scripts) that turns my screen oof and then force-stops all apps that I do not want running in the background.
You want an app to stop consuming battery, then force-stop is the way to go.
"RUN_ANY_IN_BACKGROUND is a TESTING feature of android."
mhhh so u say that not every app will really stop his background behaviour for sure? i thought that the command is quite sure to keep a closed app a "not battery hungry" app, stopping some services, alarms.
basically if u would choose an app to force close apps, would u choose superfreezz (because it s foss) over other alternatives like greenify or brevent?
because i would avoid to install any app for this, IF the command RUN_ANY....... is to consider quite powerfull and acceptable to "stop draining " battery from malicious apps...
realista87 said:
"RUN_ANY_IN_BACKGROUND is a TESTING feature of android."
mhhh so u say that not every app will really stop his background behaviour for sure? i thought that the command is quite sure to keep a closed app a "not battery hungry" app, stopping some services, alarms.
Click to expand...
Click to collapse
If you want to stop it, the a force stop is the way. Its much more "powerful" than what you found.
realista87 said:
basically if u would choose an app to force close apps, would u choose superfreezz (because it s foss) over other alternatives like greenify or brevent?
because i would avoid to install any app for this, IF the command RUN_ANY....... is to consider quite powerfull and acceptable to "stop draining " battery from malicious apps...
Click to expand...
Click to collapse
I explained to you, I use a shell script to get the job done. No need for another app, that also may consume unnecessary battery and memory.