Hello everyone,
My Greenify constantly shows the auto hibernation being stopped message. I check every app and don't find any third party app that can kill apps. My device is Samsung s6 edge, rooted with xposed installed. I use boost mode in Greenify. I'm now wondering if it is killed by the android system? But some of my apps can keep running all the time, so maybe this issue is related to Greenify only?
Oh, one more thing, I installed Amplify, so is there any chance that I blocked some wakelock that wakes up Greenify? But I checked all the wakelocks I blocked, there is no one that belongs to Greenify.
zhjn921224 said:
Oh, one more thing, I installed Amplify, so is there any chance that I blocked some wakelock that wakes up Greenify? But I checked all the wakelocks I blocked, there is no one that belongs to Greenify.
Click to expand...
Click to collapse
Did you block anything relating to Play Store? Greenify donation pack requires Play Store to function properly.
tnsmani said:
Did you block anything relating to Play Store? Greenify donation pack requires Play Store to function properly.
Click to expand...
Click to collapse
No. Now I disabled Amplify and that issue is still there. I think Greenify is killed by Android system, is that possible? Because I often see that message after heavy use. Or maybe it is killed by deep sleep? Sometimes I leave the phone for some time and see that message. I just can't find the pattern here.
Try clearing data and cache of Greenify or uninstall and reinstall it and check.
If you have any other Xposed modules apart from Amplify, disable them also and check.
tnsmani said:
Try clearing data and cache of Greenify or uninstall and reinstall it and check.
If you have any other Xposed modules apart from Amplify, disable them also and check.
Click to expand...
Click to collapse
The message still pops up.
Anybody got an idea? I tried disabling Greenify module and using root mode, but this didn't resolve the issue. Neither did revoming donation package. Is this issue Rom related? But I didn't remember having this issue before. Or it's related to Xposed framework?
Here is a clip of my build.prop file which is preset by the Rom I use (except the last line). Does anybody know which line might cause the auto hibernation stopped issue?
#Tomatolei Tweaks
#Some_Tweaks
debug.performance.tuning=1
debug.composition.type=gpu
ro.config.hw_fast_dormancy=1
ro.config.vc_call_steps=20
ro.ril.enable.amr.wideband=1
debug.enabletr=true
debug.overlayui.enable=1
debug.qctwa.preservebuf=1
hw3d.force=1
ro.config.disable.hw_accel=false
ro.fb.mode=1
ro.sf.compbypass.enable=0
ro.vold.umsdirtyratio=20
persist.sys.ui.hw=1
ring.delay=0
ro.telephony.call_ring.delay=0
ro.lge.proximity.delay=15
mot.proximity.delay=15
power.saving.mode=1
proximity_incall=enable
ro.config.hw_quickpoweron=true
ro.config.hw_power_saving=true
ro.ril.disable.power.collapse=0
#Experimental_Tweaks
boot.fps=24
shutdown.fps=24
wlan.wfd.hdcp=disable
ro.media.enc.jpeg.quality=100
persist.sys.root_access=3
ro.ril.fast.dormancy.rule=0
ro.wmt.blcr.enable=0
logcat.live=disable
#Debug
persist.adb.notify=0
persist.mtp.notify=0
persist.usb.notify=0
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
ro.config.combined_signal=true
# Better_Responsiveness_Speed
windowsmgr.max_events_per_sec=300
ro.max.fling_velocity=15000
ro.min.fling_velocity=8000
ro.min_pointer_dur=8
touch.pressure.scale=0.1
dalvik.vm.dex2oat-filter=balanced
dalvik.vm.image-dex2oat-filter=everything
# MultiTasking Tweaks
ro.config.fha_enable=true
Guys, I finally found the reason!
When I was installing this rom, I chose to uninstall smart manager. However, it seems that smart manager is the only app that can correctly set the auto run state of an app (I've tried App Ops and LBE, but they all say that Greenify is already set to auto run). Yesterday I manually installed smart manager and found that Greenify is forbidden to auto run. I changed the permission, and then the message never poped up again!
Hope it will be helpful to others who have the same problem.
Which permission did you change
Sorry for not making it clear. The permission for Greenify to auto run.
Auto hibernate is not working for me
I've been having this same issue and I also disabled Smart Manager. I'll see if re-enabling Smart Manager will fix the issue.
Related
Hey,
it seems that many games are wasting battery with the Wakelock AudioMix even when the whole audio is turned of (and I think they have not really other possibilities). I know I could compensate with the XPosed Module Amplify, which would let me set a time that has to be between two wakelocks, but that would also influence the media players. So is there a possibility to block the access to that Wakelock for some Apps only without affecting Apps that should use it? Or any other solutions?
With App-OPS and the Module "App Settings" I can mute apps and restricting acces to audio settings, but that seem to have no effect.
Artim_96 said:
Hey,
it seems that many games are wasting battery with the Wakelock AudioMix even when the whole audio is turned of (and I think they have not really other possibilities). I know I could compensate with the XPosed Module Amplify, which would let me set a time that has to be between two wakelocks, but that would also influence the media players. So is there a possibility to block the access to that Wakelock for some Apps only without affecting Apps that should use it? Or any other solutions?
With App-OPS and the Module "App Settings" I can mute apps and restricting acces to audio settings, but that seem to have no effect.
Click to expand...
Click to collapse
Interesting!!! Some developer could create this Xposed module .. "AudioMixTurnOff" .. With widget included to easily activate and deactivate, lol..
Or a module that automatically increases the amount of seconds that is limited in Amplify, in case, Audiomix (if it's not possible to turn off completely)
Well, I said some ideas..
Hi,
when using aggressive doze on a rooted Nexus 4 with Android 6.0.1 in my GPS tracking app (I tried several), even though whitelisted, the tracking stops after a few minutes.
The apps still show as tracking thus I suspect the GPS itself gets killed and provides no signal/values anymore.
Is it a bug or a feature?
Thanks for the great work
DarsVaeda said:
Hi,
when using aggressive doze on a rooted Nexus 4 with Android 6.0.1 in my GPS tracking app (I tried several), even though whitelisted, the tracking stops after a few minutes.
The apps still show as tracking thus I suspect the GPS itself gets killed and provides no signal/values anymore.
Is it a bug or a feature?
Thanks for the great work
Click to expand...
Click to collapse
Uninstall Greenify and check.
If I disable aggressive doze it works.
If I uninstall the app too of course.
This is a limitation of the doze mode itself enforced by Android. I'm afraid there's no way to workaround that.
A new Tasker plug-in is added in 2.9.5 beta 1 to toggle Aggressive Doze. Hope this could do some help here.
Ah no problem, I thought it might be something like this. I'll just disable aggressive doze while using the app.
The tasker plugin would do this automatically for me, did I get this right?
oasisfeng said:
This is a limitation of the doze mode itself enforced by Android. I'm afraid there's no way to workaround that.
A new Tasker plug-in is added in 2.9.5 beta 1 to toggle Aggressive Doze. Hope this could do some help here.
Click to expand...
Click to collapse
Shouldn't it be enough to disable "Doze on the go" to maintain the gps sensor on?
I have this same problem, and the only way to allow a foreground sports tracking app to access the gps data is to disable both "Agressive doze" and "Doze on the go"...
daniel.mota said:
Shouldn't it be enough to disable "Doze on the go" to maintain the gps sensor on?
I have this same problem, and the only way to allow a foreground sports tracking app to access the gps data is to disable both "Agressive doze" and "Doze on the go"...
Click to expand...
Click to collapse
No. As someone tested before, the stock Doze also disables GPS.
Hello,
I had the same behaviour. I tested something this morning : added to whitelist my navigation app + LocationServices + FusedLocation.
And while I was on the road, the gps worked till I arrived. In the agressive doze log I see that the device did'nt went in Doze during that time.
Don't know if this is directly related, I'll give it another try tonight.
Didn't work tonight, lost gps signal. Something else prevented doze this morning.
Will give a try to the beta and the toggle.
Any news on the subject? I get GPS signal lost while using maps...
RFrancis said:
Any news on the subject? I get GPS signal lost while using maps...
Click to expand...
Click to collapse
I'm now using the beta + Tasker to prevent doze when my navigation apps are on. Works great.
madxxcow said:
I'm now using the beta + Tasker to prevent doze when my navigation apps are on. Works great.
Click to expand...
Click to collapse
Could you export the profile
Here is an example for Google Maps.
madxxcow said:
Here is an example for Google Maps.
Click to expand...
Click to collapse
You should probably re-enable aggressive doze with an exit task. This does not seem to be one of those system settings that will auto restore when the task terminates. Also note that this profile will not trigger if Maps or your GPS app is in the background. I am debating whether aggressive doze is worth the hassle.
I've been having the same issue for a while. I use Locus Maps to record tracks on airplanes (so it may run for 12hrs) and it turns off GPS. Sometimes its hard to tell if its lost because of Doze or I simply lost the signal.
Also, it is plugged into a power source (charging) so I believe Doze should be disabled while charging.
I see above mention of "Tasker". What is this?
eng3 said:
I've been having the same issue for a while. I use Locus Maps to record tracks on airplanes (so it may run for 12hrs) and it turns off GPS. Sometimes its hard to tell if its lost because of Doze or I simply lost the signal.
Also, it is plugged into a power source (charging) so I believe Doze should be disabled while charging.
I see above mention of "Tasker". What is this?
Click to expand...
Click to collapse
The simple solution is to avoid aggressive doze which is tagged 'experimental' and is known to cause some odd device/radio/app behaviors.
Davey126 said:
The simple solution is to avoid aggressive doze which is tagged 'experimental' and is known to cause some odd device/radio/app behaviors.
Click to expand...
Click to collapse
I'm sorry, I should have clarified. I was broadening to Doze itself as I thought I read that it will also disable GPS (but not as fast or "aggressively").
My behavior has been a little different. I notice that if I run maps navigation at the same time as recording my track, there is no issue. but if I just record my track, then it not be able to prevent GPS from stopping.
Perhaps this should go in another forum, I'm just not sure which
eng3 said:
I'm sorry, I should have clarified. I was broadening to Doze itself as I thought I read that it will also disable GPS (but not as fast or "aggressively").
My behavior has been a little different. I notice that if I run maps navigation at the same time as recording my track, there is no issue. but if I just record my track, then it not be able to prevent GPS from stopping.
Perhaps this should go in another forum, I'm just not sure which
Click to expand...
Click to collapse
Try running a GPS Status app (example) concurrent with your tracking app. Aside from helping to keep the GPS 'awake' most have a variety of useful features and functionality.
I have tried that but it does not seem to work. I'll have to check the GPS status options to see if there's something for keeping it awake.
I have noticed that if I run Navigation (not just Maps) in parallel, then the GPS will stay awake.
eng3 said:
I have tried that but it does not seem to work. I'll have to check the GPS status options to see if there's something for keeping it awake.
I have noticed that if I run Navigation (not just Maps) in parallel, then the GPS will stay awake.
Click to expand...
Click to collapse
- as previously noted make sure Aggressive Doze is disabled as it can break cross-app/component communications
- also add you tracker app to 'white list' of you haven't done so already
- good chance Google Maps (any navigation app) is using wakelocks to keep GPS active
- assume all is well when you disable Greenify
- if true you many need to step away from Greenify or consider another app with similar functionality like Force Doze
Team - I am running the latest version of greenify posted on the playstore. I've followed guides for enabling agressive doze on android 6.0 on my moto x pure (non root) -- including adbing to the device to grant permissions on the app. It seems to be working most of the time. The device seems to go to sleep and i've seen a great increase in battery. However, seemingly randomly i'll notice battery draining fast. When i look at my usage its google play services keeping the device awake 100% of the time. If i reboot the phone, google play services stops doing that and all is well for awhile, till it repeats. I've been unable to find the cause of this. I imagine i'm missing some information that we might need to track this down. thanks in advance!
tange1 said:
Team - I am running the latest version of greenify posted on the playstore. I've followed guides for enabling agressive doze on android 6.0 on my moto x pure (non root) -- including adbing to the device to grant permissions on the app. It seems to be working most of the time. The device seems to go to sleep and i've seen a great increase in battery. However, seemingly randomly i'll notice battery draining fast. When i look at my usage its google play services keeping the device awake 100% of the time. If i reboot the phone, google play services stops doing that and all is well for awhile, till it repeats. I've been unable to find the cause of this. I imagine i'm missing some information that we might need to track this down. thanks in advance!
Click to expand...
Click to collapse
That may not have anything to do with Greenify unless you have greenified Play Services. If you have, remove it from hibernation.
Usually Play Services will go berserk upon updating itself in the background. What you can try is clear it's data and cache and reboot. If you have TWRP, do it in recovery. If not, do it in Settings>Apps.
tnsmani said:
That may not have anything to do with Greenify unless you have greenified Play Services. If you have, remove it from hibernation.
Usually Play Services will go berserk upon updating itself in the background. What you can try is clear it's data and cache and reboot. If you have TWRP, do it in recovery. If not, do it in Settings>Apps.
Click to expand...
Click to collapse
Thanks for the info. Here's what i've done:
I removed greenify, performed the actions you suggested and left greenify off for about 12 hours. No issues with google play services and keep awake. I reinstalled greenify and everything was good for a number of hours. Unfortunately the play services keep awake started again about 3.5 hours ago. The phone has a solid 'awake' bar in battery settings and play services is the culprit with 3.5 hours awake. While i dont blame greenify, there's some sort of correlation of events here that I can't explain.
tange1 said:
Thanks for the info. Here's what i've done:
I removed greenify, performed the actions you suggested and left greenify off for about 12 hours. No issues with google play services and keep awake. I reinstalled greenify and everything was good for a number of hours. Unfortunately the play services keep awake started again about 3.5 hours ago. The phone has a solid 'awake' bar in battery settings and play services is the culprit with 3.5 hours awake. While i dont blame greenify, there's some sort of correlation of events here that I can't explain.
Click to expand...
Click to collapse
Do you have Xposed? If so, install AppOpsXposed and untick the "Keep Awake" function of Play Services. Another thing you can try is uninstalling the update to the Play Services, reboot and then manually update it and again reboot.
If it is still not arrested, Google is your friend.
Unfortunately I've the same problem on my OnePlus 2 with stock ROM. I've installed Greenify two days ago, and enabled aggressive doze with amazing results! Last night I enabled Doze on the Go (using ADB) and since unplugging my phone this morning there is this constant wakelock of Google Play Services. Disabling Doze on the Go as well as reinstalling Greenify didn't help. Looking forward to a solution!
This is a known problem. Sometimes it's worse and sometimes less, but Google Play Services is a known offender in this manner. And Google processes in general. Part of the reason for this is that Google often wakes up your device, periodically, to track your location (horrible, yes, and it continued to happen for me even when all Google location options I could find, as well as GPS, were turned off).
Solutions that have reportedly worked for some people in the past (try one at a time or all of them) - they don't require root:
-Make sure you do not Greenify/freeze/hibernate Google Play Services, or similar processes, as this may make the issue worse.
-Clear cache and data of Google Play Services.
-Manually update Google Play Services to latest APK version available from your device, downloaded from the web. Make sure you select the right version for you. http://www.apkmirror.com/apk/google-inc/google-play-services
-Try turning off as many Google background features as you can, such as location tracking/history, etc.
I guess some of these steps may only work after the next reboot, so reboot the device when you're done.
But as I said, this process is a known big offender. The above may not work, or may work temporarily. The stronger and more permanent solutions require root (you don't really need to try the above options if you do these). The more of them you do, the less 'keep awake' you should experience:
-Install Xposed Installer app and install Xposed Framework, so you can use the modules mentioned below...
-Use AppOpsXposed module (or CM Privacy Guard if you have it) to deny keep awake permission to Google Play Services, and other Google background apps.
-This is a big one: Install Amplify (Xposed module) from the Play Store, and it will automatically take care of limiting Google wakelocks. That's it. If you pay for the pro version, then you can additionally tweak and limit all wakelocks, alarms and services on your device (pretty cool and useful, but more involved, so for advanced users).
Cultar said:
..............
-This is a big one: Install Amplify (Xposed module) from the Play Store, and it will automatically take care of limiting Google wakelocks. That's it. If you pay for the pro version, then you can additionally tweak and limit all wakelocks, alarms and services on your device (pretty cool and useful, but more involved, so for advanced users).
Click to expand...
Click to collapse
The unpaid version of Amplify will block a maximum of a couple of wakelocks related to location. Only the pro version is capable of blocking other wakelocks and alarms including those of Play Services. But as you said, it is not automatic and you will have to set it up.
Any updates on this?
Google play services is awful
MSK1 said:
Any updates on this?
Google play services is awful
Click to expand...
Click to collapse
Not a Greenify issue. Some devices/ROMs/configs seem more susceptible to GPS runaway. Clearing GPS cache+data on occasion followed by an immediate reboot has proven helpful for some. Good luck.
Greenify 3.9.5 beta, Android 8.0, htc 10, magisk, xposed systemless
Just wanna make sure it wasn't my issue / permission issue..turned everything on, tried uninstall and reinstall.
Thank you for your developing!
29988122 said:
Greenify 3.9.5 beta, Android 8.0, htc 10, magisk, xposed systemless
Just wanna make sure it wasn't my issue / permission issue..turned everything on, tried uninstall and reinstall.
Thank you for your developing!
Click to expand...
Click to collapse
All three, Enhanced Wake-up Tracker, Wake-up Cut-off and Advanced Wake-up Cut-off, are enabled in mine. But I had to repeatedly enable/disable them initially for them to be enabled.
tnsmani said:
All three, Enhanced Wake-up Tracker, Wake-up Cut-off and Advanced Wake-up Cut-off, are enabled in mine. But I had to repeatedly enable/disable them initially for them to be enabled.
Click to expand...
Click to collapse
That was weird. I clicked so many times under many circumstances but unable to even enable it once.
All it showed was something like "mayyybe your rom is not supported"
I really want to cut off some notorious intent that get triggered via sharing/network state change/media scan...because they significantly slowed my device.
: (
Is there any logcat that I can provide to help @oasisfeng debugging?
Hi,
I recently installed Greenify on my Pocophone F1 /MIUI 10.3 on which I have already Tasker.
For Tasker, I have removed all battery restrictions so it is never optimized and it is fine. If I stop it manually, then for I don't know which reason accessibility and notification services get disabled so I have to enable them again.
The problem since I installed Greenify is that although Tasker is not part of the apps to hibernate, after some time when the screen is off, the same services get disabled on Tasker, exactly as if Tasker was forced to stop. So I am wondering why Greenify acts like this and how to prevent it? Isn't there any kind of whitelist?
I have not changed any default setting in Greenify.
Any idea what is happenning?
Thx.