Related
Hi all
I am using a Samsung Galaxy Note 2 4.3 stock rooted and I am having some issues with greenify. Everytime I start the app to see if it working I get this message: "Auto-hibernation service is stopped" The problem is that I am not using a 3rd-party tool or any other mode as energy saving mode on my note 2 and I still get this message. What should I do to fix it?
thx
This same problem,
S III, rom > http://forum.xda-developers.com/galaxy-s3/development/rom-archidroid-v2-4-6-power-hands-t2354859
Xposed framework installed
Greenify is device administrator
I have full version
Please read the FAQ in post #2 in the main thread. Both of you may be having root issues.
If I may make a suggestion?
I started getting the same error message (it started right after I paid for the app). After reading "thousands" of pages I think I may have hit on the answer. Greenify is in "boost" mode, that somehow, even though it uses xposed framework, doesn't need root. So I checked supersu and greenify wasn't listed. Then I changed to "root" method and greenified an app, then supersu asked to allow greenify, thereby now having it listed again in supersu.
I then changed it back to "boost" and so far haven't had that error. Coincidently, Greenify seemed to work ok anyway even with that error.,
edit: well that blows, I started to get the error message again, so disregard what I wrote above. Maybe a fix is coming, or I'll live with manually starting auto-hibernation.
tnsmani said:
Please read the FAQ in post #2 in the main thread. Both of you may be having root issues.
Click to expand...
Click to collapse
No, I check this 3 times ...
colin p > nothing, still this same problem
anyone has ideas, what else, I can do ?
Just to add additional info, this auto-hibernation error only started after I bought the Donation Package. I don't know if it's something to do with the additional options or not. Before I bought the program, auto-hibernation worked fine.
I have a Nexus 4 (rooted with towel-root) and SuperSu and of course the Xposed framework. I uninstalled/re-installed Greenify, as well as the Donation Package and still the error pops up the first time I open Greenify. I then have to manually start auto- hibernation and it works ok after that, at least it "seems" to as everything is under the hibernated section.
After I re-installed, SuperSu asked to allow Greenify root access, so it is properly listed. I would imagine that if a significant few of us have the issue, a future update will address the error problem.
I would like to try to enable Greenify as root mode. Will the message appear?
If it isn't I would then disable the Greenify module in Xposed, then reboot (no soft reboot, just to be sure), enable module, reboot again, and then select boost mode within Greenify. Then make a last reboot. Then inspect the problem.
This is not a definite fix, though in some weird circumstances, it might work
TechnoSparks said:
I would like to try to enable Greenify as root mode. Will the message appear?
The message appears in either root or boost mode on the first time the program is opened after a boot up.
If it isn't I would then disable the Greenify module in Xposed, then reboot (no soft reboot, just to be sure), enable module, reboot again, and then select boost mode within Greenify. Then make a last reboot. Then inspect the problem.
Tried your suggestion and still get the "auto-hibernation has stopped" error.
This is not a definite fix, though in some weird circumstances, it might work
Click to expand...
Click to collapse
Unfortunately, no dice. Still get that error, thanks anyway.
By George...
Well after a lot of screwing around, I think (at least for my circumstances) I "may" of found the answer. Because the error said something like "auto hibernation service is being blocked by 3rd party tool or system settings (ex.stamina mode in sony devi es. autostart manager in MIUI) Please whitelist greenify for automatic hibernation to work", I uninstalled Donkey Guard and Cydia Substrate (they were installed a couple of days before I got the pro version of Greenify, even though there was no problem with them before I got the paid version of Greenify), but still got the error. Ruling out program issues, this time I actually shut down my phone (no reboot or soft reboot) and on opening Greenify, no error. Since I was using the reboot toggle in "Notification Toggle", I tried rebooting through xposed (not soft reboot) and this time, no error. Tried again with Notification toggle and got the error.
So, at least for me, I think I may have solved the issue.....for now.
BTW thanks TechnoSparks as you gave me something to work with.
colin p said:
Well after a lot of screwing around, I think (at least for my circumstances) I "may" of found the answer. Because the error said something like "auto hibernation service is being blocked by 3rd party tool or system settings (ex.stamina mode in sony devi es. autostart manager in MIUI) Please whitelist greenify for automatic hibernation to work", I uninstalled Donkey Guard and Cydia Substrate (they were installed a couple of days before I got the pro version of Greenify, even though there was no problem with them before I got the paid version of Greenify), but still got the error. Ruling out program issues, this time I actually shut down my phone (no reboot or soft reboot) and on opening Greenify, no error. Since I was using the reboot toggle in "Notification Toggle", I tried rebooting through xposed (not soft reboot) and this time, no error. Tried again with Notification toggle and got the error.
So, at least for me, I think I may have solved the issue.....for now.
BTW thanks TechnoSparks as you gave me something to work with.
Click to expand...
Click to collapse
No problem mate. If it really works for a long time, it might be good to report here as I may take your method as a suggestion to other people facing the same problem as well. :good:
romdroid. said:
I am using a Samsung Galaxy Note 2 4.3 stock rooted and I am having some issues with greenify. Everytime I start the app to see if it working I get this message: "Auto-hibernation service is stopped" The problem is that I am not using a 3rd-party tool or any other mode as energy saving mode on my note 2 and I still get this message. What should I do to fix it?
Click to expand...
Click to collapse
I seem to have this same problem, but I don't think it's easily repeatable, which makes it hard to narrow down a possible cause. I have a Samsung Galaxy Note 3 running Android 4.4.4 but it's not rooted, so the other posts here (which I think all involve root) don't seem to apply in my case. Is there a possible known cause and/or solution for this problem of auto-hibernation stopping on unrooted devices? Thanks for your help!
Can anyone confirm whether it was fixed in 2.4.4 beta 1 or beta 2?
oasisfeng said:
Can anyone confirm whether it was fixed in 2.4.4 beta 1 or beta 2?
Click to expand...
Click to collapse
I had not got this message for quite a long time, but after updating to beta 2, the first time I rebooted and opened Greenify, I got this message. Afterwards, for the whole of today, I haven't got it.
Everything is working great for me.
Make sure you have SuperSu (latest)
Also after installing Greenify, set it as a device administrator.
Settings>security>device administrators>select Greenify.
Enable accessability as well (settings>accessibility>Greenify>Enable.
I have these enabled and have no issues.
Sent from my Nexus 4
gorilla p said:
Everything is working great for me.
Make sure you have SuperSu (latest)
Also after installing Greenify, set it as a device administrator.
Settings>security>device administrators>select Greenify.
Enable accessability as well (settings>accessibility>Greenify>Enable.
I have these enabled and have no issues.
Sent from my Nexus 4
Click to expand...
Click to collapse
You are right. After my last post, I found that Greenify was not enabled in Accessibility settings.
After every update, the Accessibility setting has to be re-enabled. Why?
tnsmani said:
You are right. After my last post, I found that Greenify was not enabled in Accessibility settings.
After every update, the Accessibility setting has to be re-enabled. Why?
Click to expand...
Click to collapse
for me i have to enable it in accessibility after every restart of the phone ....
Anyone found a solution to this? I am getting the same error.
oasisfeng said:
Can anyone confirm whether it was fixed in 2.4.4 beta 1 or beta 2?
Click to expand...
Click to collapse
HI Oasis - just to reply that I am still getting Auto-hibernation stopped with Greenify v2.5.1
Basically after a while auto-hibernate just seems to stop. I have all my apps waiting to be hibernated even after a few hours of screen off. I do not get the 3rd party message saying auto-hibernation is stopped. I have Accessibilty on and have given Greenify Device Administration rights.
I will get the 3rd party message if I force close Greenify or if I reboot. In those cases Accessibility will have turned itself off. After turning Accessibility back on, the message disappears but I still have apps waiting to be hibernated after seveal hours of screen-off.
After every reboot, I find that Greenify does not seem to ask SuperSU for root access. Even though I've granted Greenify automatic access,the log files for SuperSU never show Greenify as either being granted or denied rights. I know that Greenify is meant to ask for those rights when the screen is off. I guess it might be another app is locking the device when the screen is off before Greenify can ask for access. I've tried removing Device Admin privileges for other apps and remove PIN unlocks but this does not seem to help.
The only way I have managed to get Greenify running again is to uninstall and reinstall, which seems to be the only way when the screen is on that I can get it to request root access via SuperSU. This does mean I cannot use the Xposed installer options, because I would first need to reinstall Greenify, grant it root access via SuperSU, then enable the XPosed module, then reboot. But after reboot SuperSU access seems to be withdrawn and I can't get it to request root unless I uninstall and reinstall.
I'm sure I'm missing something but I'm not sure what. I am not sure if there is a way of forcing Greenify to request SuperSU access even when the screen is on without having to reinstall.
I am rooted with SuperSU 2.4 and Xposed installer, HTC One on Viper 7.02 ROM, Greenify 2.5.1 with donation package.
EDIT: I've found that I can get Greenify to ask for Root Access through Xposed if I first degreenify Facebook, re-greenify Facebook, launch another app which wakes up Facebook (eg Agoda) and then request Greenify to cut-off the wake-up. Seems to be working.
EDIT2: Alas, still having problems. Usually nothing auto-hibernates after charging the phone. Yesterday it was working fine, today I unplugged, started some apps, closed the phone and went for breakfast. 1.5 hours later the apps were still waiting to hibernate. Am completely lost on what to do next.
Dronak said:
I seem to have this same problem, but I don't think it's easily repeatable, which makes it hard to narrow down a possible cause. I have a Samsung Galaxy Note 3 running Android 4.4.4 but it's not rooted, so the other posts here (which I think all involve root) don't seem to apply in my case. Is there a possible known cause and/or solution for this problem of auto-hibernation stopping on unrooted devices? Thanks for your help!
Click to expand...
Click to collapse
I occasionally get this message, generally after an update to Greenify, but just tap on the message and continue on with my day. After exhaustive (I'm rather OCD) research, the general consensus is to forget about it as it is just Greenify's way of letting you know that the auto-hibernation has stopped and needs to be restarted. I have gone without tapping on that message and the service still starts up all by itself.
My advice is to open Greenify after an update (updates have slowed considerably anyway) and just tap on the message and it will be good to go until the next update.
Thanks for the response. I have been tapping on the message when I notice it, but it still seems to appear without updates to Greenify. I've tried checking a little more, though probably not as exhaustively as you did, and I suspect that there's some kind of conflict with Tasker. One of the main things I do with Tasker is alternate between "home" and "work" modes, part of which involves using a screen lock for "work" and turning it off for "home". It seems like when things are working fine at home, I go to work making it switch to work mode, and return home at the end of the day going back into home mode, Greenify complains. Since Greenify only works without a screen lock in non-root mode, I'm guessing this switching may be affecting thing, but I'm not completely sure. I guess I just have to live with it. One thing I've tried doing to mitigate the problem is add a Greenify hibernate action to my Tasker profile for turning mobile data off when the screen goes off. I'm not sure how well it's working, because at work I normally hibernate manually and at home I often don't worry about it, but even if it's not working, I think I get a placebo effect of thinking it's doing *something* so I'm less concerned about checking to see if Greenify has stopped auto-hibernating.
I am just wondering if anyone else is having problems with notifications disappearing upon hibernation with xposed 5.1. I have everything set right in experimental settings, I've been using this so for years so I know how to set it properly☺. Just wondering if I am the only one because I am about to loose my mind!! I've tried everything, installing uninstalling downgrading upgrading, I've spent hours on it, just thought I'd ask before giving up. Running in boost mode with donation package. Thanks
Sent from my GT-P5110 using Tapatalk
Shepguessed said:
I am just wondering if anyone else is having problems with notifications disappearing upon hibernation with xposed 5.1.
Sent from my GT-P5110 using Tapatalk
Click to expand...
Click to collapse
Try the Xposed version of the GB Dev available in the super alpha Xposed thread. Also use beta 3 of Greenify with that. This combination is reported to be working.
Another alternative is to disable deep hibernation in Greenify.
tnsmani said:
Try the Xposed version of the GB Dev available in the super alpha Xposed thread. Also use beta 3 of Greenify with that. This combination is reported to be working.
Another alternative is to disable deep hibernation in Greenify.
Click to expand...
Click to collapse
I am guessing he's using that version of Xposed. But yeah this problem is there.
ottomanrage said:
I am guessing he's using that version of Xposed. But yeah this problem is there.
Click to expand...
Click to collapse
Yes I have tried every possible combo, litterally spent hours on it. I am just wondering if it is my problem only or are other people having this problem? I would love to know!
Sent from my GT-P5110 using Tapatalk
Hi guys. I'm on the same boat.
CM12.1, Greenify 2.6.2b5, xposed super alpha and no notifications kept after auto-hibernate for whatsapp, hangouts and skype.
I've only installed xposed again, and greenify module etc, and notifications only affect Facebook, but just noticed by just noticed that they're snoozing too.
I have the same issue, notifications come in, but then they disappear. I have all the required options checked, using alpha 4 xposed + b5 greenify.
Yes, i have this too. All notifications are gone after re-greenify.
---------- Post added at 07:01 PM ---------- Previous post was at 06:38 PM ----------
I may have accidentally found a solution. deleted beta 5(back up in titanium backup first) , reboot, reinstalled beta 4, reboot, restore beta 5. seems to be working for me now. not quite sure why.
davtse said:
I may have accidentally found a solution. deleted beta 5(back up in titanium backup first) , reboot, reinstalled beta 4, reboot, restore beta 5. seems to be working for me now. not quite sure why.
Click to expand...
Click to collapse
Did you activate the xposed module after b4 installation? When you restored b5 using TiBu, did you choose app, data or app+data? For me, your solution doesn't work.
christiano88 said:
Did you activate the xposed module after b4 installation? When you restored b5 using TiBu, did you choose app, data or app+data? For me, your solution doesn't work.
Click to expand...
Click to collapse
yes activated after b4 installation. after that i just restored app+data for b5. alternatively try to enable notification access for greenify as well. might have been a step i missed but its still working for me.
davtse said:
yes activated after b4 installation. after that i just restored app+data for b5. alternatively try to enable notification access for greenify as well. might have been a step i missed but its still working for me.
Click to expand...
Click to collapse
I do not have Greenify under Notification access.
christiano88 said:
I do not have Greenify under Notification access.
Click to expand...
Click to collapse
weird... i do though. see attached picture. i'm on 5.1.1 slimpop
Beta 6 is up, it doesn't address this issue. I tried reinstalling from scratch, greenify appeared in notification access, but as soon as I activated "Keep notifications" (root non-limited one) under greenify, it disappeared from the notification access. @davtse can you please post a screenshot of your greenify settings?
L.E.: I've pretty much figured it out after reinstalling greenify multiple times and trying with different settings. This is what happens:
- Activating the xposed module makes the "Keep notifications (Limited)" disappear from Greenify options, so I went on and activated it before activating the xposed module and restarting the phone. Also make sure to activate Greenify under notification access option in phone settings.
- Even if "Keep notifications (Limited)" doesn't show anymore, if you managed to activate it before activating the xposed module, it will be kept active.
- If you activate "Keep notifications" (the non-limited one), it will cancel the Limited one, and it won't work, and it also makes Greenify disappear from the notification access menu.
These are my findings.
The good part is that I made it work this way, but the notification light goes away when the app is hibernated with a pending notification. At least, the notification stays.
christiano88 said:
Beta 6 is up, it doesn't address this issue. I tried reinstalling from scratch, greenify appeared in notification access, but as soon as I activated "Keep notifications" (root non-limited one) under greenify, it disappeared from the notification access. @davtse can you please post a screenshot of your greenify settings?
L.E.: I've pretty much figured it out after reinstalling greenify multiple times and trying with different settings. This is what happens:
- Activating the xposed module makes the "Keep notifications (Limited)" disappear from Greenify options, so I went on and activated it before activating the xposed module and restarting the phone. Also make sure to activate Greenify under notification access option in phone settings.
- Even if "Keep notifications (Limited)" doesn't show anymore, if you managed to activate it before activating the xposed module, it will be kept active.
- If you activate "Keep notifications" (the non-limited one), it will cancel the Limited one, and it won't work, and it also makes Greenify disappear from the notification access menu.
These are my findings.
The good part is that I made it work this way, but the notification light goes away when the app is hibernated with a pending notification. At least, the notification stays.
Click to expand...
Click to collapse
Glad to know that i am not alone in this I'll try your method and let you know. I don't know if there are many users in our case but in case @oasisfeng you decide to investigate on it please let us know if we can help with some kind of log or anything else. (keeping notifications after hibernation is a major feature i think)
PS : Irrelevant to the problem, but could somebody tell me difference between the root and beast mode in greenify ? (did some research on it but did not see a clear answer)
Edit : Unfortunately that did not go well at 100%, i mean that for example when i got a messenger message, the app can not go to hibernation but for facebook's notifications (e.g. friend request) after hibernation the notification goes away ... Keeping notifications is one of the best features in Greenify IMO so being broken make me :crying:
mbmb8989 said:
Edit : Unfortunately that did not go well at 100%, i mean that for example when i got a messenger message, the app can not go to hibernation but for facebook's notifications (e.g. friend request) after hibernation the notification goes away ... Keeping notifications is one of the best features in Greenify IMO so being broken make me :crying:
Click to expand...
Click to collapse
Are you sure you did exactly this?
- after installing latest version of Greenify, DO NOT REBOOT, go to settings and activate only "Do not remove notifications (Limited)".
- activate "Greenify" in Notification access from phone settings
- activate the xposed module and reboot the phone
- activate "GCM push for greenified apps".
christiano88 said:
Are you sure you did exactly this?
- after installing latest version of Greenify, DO NOT REBOOT, go to settings and activate only "Do not remove notifications (Limited)".
- activate "Greenify" in Notification access from phone settings
- activate the xposed module and reboot the phone
- activate "GCM push for greenified apps".
Click to expand...
Click to collapse
Actually, i did reboot before activating the xposed module
Just to clarify :
- In the third step, i just activate the xposed module (so i shouldn't activate any greenify feature ?) and reboot the phone ?
- In the fourth step, i activate "GCM push for greenified apps" only or among the other features ?
- Do you recommand Deep Hibernation or should i leave it off for now ?
- Concerning greenify mode, what would be more efficient in our case Boost or Root ?
Thanks again and sorry for being a pain in the arse :laugh: :laugh:
I will try again regarding your next answer and let you know how it went
Yes, you only have to activate the module. No, you can activate other features, for example, I have Deep Hibernation enabled (even though it causes some issues with accounts, and making some apps ask to re-login everytime you use them). So, I don't really recommend Deep Hibernation as it is right now, wait for more updates with fixes for it. Instead, you can check Greenify regularly to cut-off wake paths, which gets you close to having deep hibernation enabled.
Boost is the best tehnically, but I am on Root mode (personal choice).
christiano88 said:
Yes, you only have to activate the module. No, you can activate other features, for example, I have Deep Hibernation enabled (even though it causes some issues with accounts, and making some apps ask to re-login everytime you use them). So, I don't really recommend Deep Hibernation as it is right now, wait for more updates with fixes for it. Instead, you can check Greenify regularly to cut-off wake paths, which gets you close to having deep hibernation enabled.
Boost is the best tehnically, but I am on Root mode (personal choice).
Click to expand...
Click to collapse
Unfortunately that did not work :crying: I will try to go back to a previous stable version ? one you'd recommend ?
mbmb8989 said:
Unfortunately that did not work :crying: I will try to go back to a previous stable version ? one you'd recommend ?
Click to expand...
Click to collapse
Try one more time without activating other modules, just go by my steps only. If it still doesn't work, try same method with beta 5.
christiano88 said:
Try one more time without activating other modules, just go by my steps only. If it still doesn't work, try same method with beta 5.
Click to expand...
Click to collapse
I did try it with beta 3 and it worked but the notification icon is not the original one after hibernating the original app (and its the same custom icon for every app that has a pending notification and goes into hibernation).
I will try it with the beta 5. I hope that op is aware of it
Are we the only ones with this issue :crying:
Hi!
Greenify hibernates all apps, even the ones that are active (in my case runtastic and music player)
Before this bug: runtastic and music player active while jogging -> screen off -> all apps beside those too get hibernated
Now: runtastic and music player active -> screen off -> ALL apps get hibernated
Please fix it.
I think it's cm12.1 related.
Tried with Greenify 2.6.2 and 2.7.x all betas.
Still the same.
Edit: could this be the cause?
http://review.cyanogenmod.org/#/c/105617/
Same problem here.
Running CM 12.1 August 16 nightly and getting Spotify hibernated while playing.
I believe there should be another commit in CM which breaks Greenify's ability to detect running apps.
Probably we should continue discussion in this thread.
The issue has been fixed in version 2.7 beta 8.
Many thanks to @oasisfeng for quick solution!
DavisNT said:
The issue has been fixed in version 2.7 beta 8.
Many thanks to @oasisfeng for quick solution!
Click to expand...
Click to collapse
I have beta 8 right now and it works for Google music.
Sent from my LG-D851 using Tapatalk
I just did a 5 mile run and it shows as 1.8 miles. Every time I use Greenify my runs are jacked up
I had the issue, that Greenify 2.9beta3 killed my TTS (Text-To-Speech), TTS fell back to Pico (Samsung, not very good) then.
So I uninstalled the Beta (left the beta program) and installed 2.8.1 (not-beta).
Now it works again.
Anyway with the 2.9b3 there was some notification terror, which wasnt possible to disable constantly in the settings. I had to disable all notification of Greenify app in the system settings to get rid of this annoying stuff. Just Beta it is.
Samsung Galaxy S4 with CM12.1
EDIT: I uninstalled Greenify completely, when I noticed that it uses about 100 MB RAM itself.
I use nite the small Xposed module "prevent running". Much easier and smaller and does the same.
@oasisfeng
Reporting that Greenify donate and Xposed options work with Xposed v77 by rovo89 for Marshmallow on my Nexus 4 with Chroma M ROM and Banks gapps.
Starting a new adventure on M.
Greenify cause reboots on Xposed for marshmallow
I woke up to a flashing yellow notification but no notification in the shade to go with it..
What could this be? I rebooted the phone to get rid of it..
Perhaps it has something to do with greenify xposed mode?
Sent from my Nexus 6P using Tapatalk
Also, a couple random reboots I think may be related to greenify... Not sure tho
Sent from my Nexus 6P using Tapatalk
xiaolvmu said:
The reboots are related to the GCM Push feature. Disable it and it won't cause reboots anymore.
Really hope @oasisfeng can fix this soon
Sent from Nexus 9
Click to expand...
Click to collapse
Neuxs6 with android 6.0(58r) shows the same reboot issue, when the wechat app was pushed & recieved via GCM feature.
I have to disable the GCM option, this is the root cause.
@oasisfeng
[email protected] said:
Neuxs6 with android 6.0(58r) shows the same reboot issue, when the wechat app was pushed & recieved via GCM feature.
I have to disable the GCM option, this is the root cause.
@oasisfeng
Click to expand...
Click to collapse
v78 and still reboot occurs with greenify.
tnsmani said:
@oasisfeng
Reporting that Greenify donate and Xposed options work with Xposed v77 by rovo89 for Marshmallow on my Nexus 4 with Chroma M ROM and Banks gapps.
Starting a new adventure on M.
Click to expand...
Click to collapse
Switched to Xposed v.78 and all features of Greenify work without issues.
Uninstall Greenify and install Greenify v2.7 beta 8 GoodLuck to you
Gescript said:
Uninstall Greenify and install Greenify v2.7 beta 8 GoodLuck to you
Click to expand...
Click to collapse
Can you package the apk? Beta 2 is only available on the download.
kallell said:
Can you package the apk? Beta 2 is only available on the download.
Click to expand...
Click to collapse
Download The beta 2 is support 6.0 .I use it now
I cannot get a single app to hibernate (manual or auto). I am running rooted stock 6.0 on my Nexus 6P with Grennify 2.8 Beta 3 installed. Has anyone else run into this issue?
Oh well
lary50 said:
Same problem here
Click to expand...
Click to collapse
What do you mean by that? What happens when you tap an app? And on which screen, hibernated or app picker?
cmlohff said:
I cannot get a single app to hibernate (manual or auto). I am running rooted stock 6.0 on my Nexus 6P with Grennify 2.8 Beta 3 installed. Has anyone else run into this issue?
Click to expand...
Click to collapse
See above post.
Galaxy Tab S 10.5 running 6.0 AOSP, beta 2 was working fine (except GCM feature causing random reboots like I've seen others mention). Then beta 3 now and boost mode seems to have broken, it takes that 3-4 seconds for each app to hibernate as if it was root mode (or even non root), and I don't think auto hibernation is working at all actually.
tnsmani said:
See above post.
Click to expand...
Click to collapse
This occurred when I tried to add apps in the app picker or just select them from the hibernation screen.
I uninstalled Greenify and then reinstalled it and it temporarily fixed the issue. It was working fine for a few hours and then I woke up this morning and apps were no longer hibernating.
A reboot fixed this but I will need to see if it happens again.
Why this recommendation to uninstall the final and install the beta? What's that for? Why would the beta work better than the final?
BigLisy said:
Galaxy Tab S 10.5 running 6.0 AOSP, beta 2 was working fine (except GCM feature causing random reboots like I've seen others mention). Then beta 3 now and boost mode seems to have broken, it takes that 3-4 seconds for each app to hibernate as if it was root mode (or even non root), and I don't think auto hibernation is working at all actually.
Click to expand...
Click to collapse
Wipe data cache of Greenify and then uninstall and reinstall. It may solve your issue.
cmlohff said:
This occurred when I tried to add apps in the app picker or just select them from the hibernation screen.
I uninstalled Greenify and then reinstalled it and it temporarily fixed the issue. It was working fine for a few hours and then I woke up this morning and apps were no longer hibernating.
A reboot fixed this but I will need to see if it happens again.
Click to expand...
Click to collapse
If it still occurs, something else may be clashing with Greenify.
Blario said:
Why this recommendation to uninstall the final and install the beta? What's that for? Why would the beta work better than the final?
Click to expand...
Click to collapse
There is no recommendation. Betas always contain some improvement or the other over the last final version. But betas may be buggy. Some people who are game enough, try these betas and report the issues faced by them if any and the Dev accordingly adjusts his app and then publishes the next final version. Betas may or may not work better than the previous final.
Hi,
I'm running greenify (donation version) on a nexus 10 running CM13 release, and I can't get auto hibernation to work.
All i get from greenify are notifications listing apps that can be manually hibernated.
On my other devices (all rooted) auto hibernation works fine. Yes I do have root access turned on in CM13, and greenify has root access.
Any suggestions?
Cheers
[L]
What kind of screen lock method?
[Lemmy] said:
Hi,
I'm running greenify (donation version) on a nexus 10 running CM13 release, and I can't get auto hibernation to work.
All i get from greenify are notifications listing apps that can be manually hibernated.
On my other devices (all rooted) auto hibernation works fine. Yes I do have root access turned on in CM13, and greenify has root access.
Any suggestions?
Cheers
[L]
Click to expand...
Click to collapse
hevesi_j said:
What kind of screen lock method?
Click to expand...
Click to collapse
no idea, how can I tell?
Right now I'm inclined to say "Whatever is the default", since I'm not conscious of making any changes to any settings about screen lock methods.
after some observation time I can see that it's always the amazon apps (amazon video, kindle, amazon app store, amazon music) that are not automatically hibernated.
...the strange part is that they go to sleep with greenify just fine on my other devices, none of which runs cyanogen.
edit: just saw several google apps from the gapps package in the list as well.
same problem as yours automated hibernation not work.
[Lemmy] said:
Hi,
I'm running greenify (donation version) on a nexus 10 running CM13 release, and I can't get auto hibernation to work.
All i get from greenify are notifications listing apps that can be manually hibernated.
On my other devices (all rooted) auto hibernation works fine. Yes I do have root access turned on in CM13, and greenify has root access.
Any suggestions?
Cheers
[L]
Click to expand...
Click to collapse
Are you absolutely sure they don't hibernate after awhile? You probably have the setting "Quick Action Notification" turned on and that is what you are seeing? I have both the Nexus 4 and 7 running CM13 and hibernation works on them just fine, however the notification does show the option of manual hibernation as well. I don't worry about it anymore and let Greenify deal with it.
On a side note, I noticed the beta update yesterday does keep my devices "dozing" better.
colin p said:
Are you absolutely sure they don't hibernate after awhile? You probably have the setting "Quick Action Notification" turned on and that is what you are seeing? I have both the Nexus 4 and 7 running CM13 and hibernation works on them just fine, however the notification does show the option of manual hibernation as well. I don't worry about it anymore and let Greenify deal with it.
On a side note, I noticed the beta update yesterday does keep my devices "dozing" better.
Click to expand...
Click to collapse
*facepalm*
thanks! that's what that was.