Hi XDA Community,
I have recently flashed Cyanogenmod 13 after performing a clean Factory Reset on my OnePlus One. More details at the end of the post. However, Greenify is now unable to cut off wakeup paths of greenified apps, which worked fine before on Cyanogenmod 12.1.
The phone is rooted, Greenify has been granted Superuser rights by SuperSU and is entered as a device administrator under Settings -> Security -> Device Administrators. Greenify - Automated Hibernation under Settings -> Accessiblity was usually set to off, as Greenify shouldn't need that when rooted as far as I'm aware, but I have now turned it on. Still no change. "Draw over other apps" is set to "Yes" for Greenify.
Greenify is running in Boost mode, all Xposed-based features are enabled. Greenify is checked in the Modules section of the Xposed Installer app. Google Play Services and Google Now are permanently on and Greenify shows their status as "Working".
I found the cut off wakeup path feature really useful and would like to use it again.
Could anyone help me with that, please?
Thanks in advance!
Greenify version: 2.8.1 with Donation Package, both from Google Play Store. Legally bought, purchase verification works.
Xposed Framework version: xposed-v82-sdk22-arm
OS: Cyanogenmod 13, cm-13.0-20160419-SNAPSHOT-ZNH0EAO2O0-bacon to be precise
Device: OnePlus One
@Neehlanfyr
The title of the thread is not correct. Cut off wake-up paths works in 6.0.1. I don't know about its working with CM but in my ROM it is working.
When an app is in "working" state, you will not get the option to cut off wake-up path. It needs to be in "pending hibernation" list for that. And it has to be clicked and not long pressed.
tnsmani said:
@Neehlanfyr
The title of the thread is not correct. Cut off wake-up paths works in 6.0.1. I don't know about its working with CM but in my ROM it is working.
When an app is in "working" state, you will not get the option to cut off wake-up path. It needs to be in "pending hibernation" list for that. And it has to be clicked and not long pressed.
Click to expand...
Click to collapse
Hi tnsmani,
thanks for responding. The thread's title is correct, as I can not cut off wakeup paths on my Android 6.0.1 device. I know very well that it should generally work, but it does not for me, which was my reason for opening this thread. I am looking for a solution that allows me to use this functionality again. To be more precise: I can't cut off the wakeup path of any greenified app, regardless of its condition/status. I forgot to mention that in the opening post, sorry.
The "scissors button" just isn't showing. I have used this feature before on Android 5.1, 5 and 4.4 and if it hasn't been changed radically, I should still know how to use it.
Best regards,
Neehlanfyr
Neehlanfyr said:
Hi tnsmani,
thanks for responding. The thread's title is correct, as I can not cut off wakeup paths on my Android 6.0.1 device. I know very well that it should generally work, but it does not for me, which was my reason for opening this thread. I am looking for a solution that allows me to use this functionality again. To be more precise: I can't cut off the wakeup path of any greenified app, regardless of its condition/status. I forgot to mention that in the opening post, sorry.
The "scissors button" just isn't showing. I have used this feature before on Android 5.1, 5 and 4.4 and if it hasn't been changed radically, I should still know how to use it.
Best regards,
Neehlanfyr
Click to expand...
Click to collapse
Still the title is not correct. It should have been "on CM13" instead of "on Android 6.0.1"
Same problem here
My device is moto g (xt1033) running cm 13(based on Android 6.0.1). To be precise 06-08 nightly. Greenify version is 2.8 beta 3. Xposed version v86 sdk 23. The scissors icon doesn't even show up when I select an app which is listed for hibernation.
Yeshu94 said:
My device is moto g (xt1033) running cm 13(based on Android 6.0.1). To be precise 06-08 nightly. Greenify version is 2.8 beta 3. Xposed version v86 sdk 23. The scissors icon doesn't even show up when I select an app which is listed for hibernation.
Click to expand...
Click to collapse
You can update to the stable 2.9 version and check.
The scissors icon will appear only if a hibernated app is woken up by another app/process.
tnsmani said:
You can update to the stable 2.9 version and check.
The scissors icon will appear only if a hibernated app is woken up by another app/process.
Click to expand...
Click to collapse
It seems that since v2.9 beta4, there is no scissors icon any more. So I have to use beta3 now.
wyc said:
It seems that since v2.9 beta4, there is no scissors icon any more. So I have to use beta3 now.
Click to expand...
Click to collapse
thank you for the info buddy
Related
Hi everyone. I have been using greenify since its early days. An issue has occurred recently that greenify no longer auto-hibernates apps & I have to manually do so using the shortcut. I am using the boosted mode with all non-donation features activated. I am using the latest stable version & also have the XPosed plug-in installed. Any idea about how to fix this issue?
Salman Babri said:
Hi everyone. I have been using greenify since its early days. An issue has occurred recently that greenify no longer auto-hibernates apps & I have to manually do so using the shortcut. I am using the boosted mode with all non-donation features activated. I am using the latest stable version & also have the XPosed plug-in installed. Any idea about how to fix this issue?
Click to expand...
Click to collapse
if you're using Sony device do this
http://forum.xda-developers.com/apps/greenify/sony-stamina-mode-vs-greenify-t2902062
Salman Babri said:
Hi everyone. I have been using greenify since its early days. An issue has occurred recently that greenify no longer auto-hibernates apps & I have to manually do so using the shortcut. I am using the boosted mode with all non-donation features activated. I am using the latest stable version & also have the XPosed plug-in installed. Any idea about how to fix this issue?
Click to expand...
Click to collapse
I am assuming you didn't get the message that "Greenify service is stopped by another xxxxxxx". You might want to enable Greenify's device administrator to make sure most features work without any problem.
Are you referring to turning greenify on settings->accessibility menu ? Also I have another problem. Few months back there used to be wakelock cut feature (scissors icon) but I can no longer find it. Has it been removed or am I missing something?
Salman Babri said:
Are you referring to turning greenify on settings->accessibility menu ? Also I have another problem. Few months back there used to be wakelock cut feature (scissors icon) but I can no longer find it. Has it been removed or am I missing something?
Click to expand...
Click to collapse
Greenify has to be enabled both in Device Administration and Accessibility.
The wakelock cut feature exists and is working fine in my devices.
tnsmani said:
Greenify has to be enabled both in Device Administration and Accessibility.
The wakelock cut feature exists and is working fine in my devices.
Click to expand...
Click to collapse
I have now enabled greenify in both of them (previously it was disabled in Device admin). The issue of hibernation & wakelock cut seems to be resolved now.
The scissor icon will be shown only when the app/program is invoked by another app/program, not when it launches itself or when you launch it.
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:
This is the first beta version of Greenify 2.7. This major version is aimed to improve the over-all user experience in every aspect (if possible).
Beta 8
Fixed the detection for background active app on Android 5.1.1_r9 and 6.0, with new implementation.
Fixed crash on Android 4.0.x.
Simplified the confusing state reason of postponed hibernation.
Beta 7
Fixed crash during auto-hibernation in non-root mode.
Beta 6
Due to a permission change in the newest revision of Android 5.1.1 and 6.0, Greenify has to use the usage stats permission to detect the foreground app and avoid hibernating it. Unfortunately, this new implementation could no longer detect the active background apps (such as music player).
Improved compatibility with Android 6.0.
FIX: Xposed feature settings lost issue on arm64.
Beta 5
Foreground app no longer hibernates even if "state always ignored" is checked.
Reduced the impacts of wake-up cut-off.
FIX: Native processes cleaning.
FIX: Wake-up action in Tasker plug-in on Android 5.x.
FIX: No longer list disabled apps.
Beta 4
Fixed the reboot issue in root mode if core system app is greenfied.
Beta 3
Greenify now cleans up native processes after hibernation, to prevent self-reviving.
Fixed root mode on Android 4.0 & 4.1.
Fixed non-root mode on Android M.
No longer pause auto-hibernation when charging.
Beta 2
Fixed the manual hibernation not working issue when charging. (introduced in beta 1)
Beta 1
Dim the screen when performing auto-hibernation on non-root device.
Auto-hibernation will pause when external power is connected.
"Hibernate and Lock Screen" shortcut does not require device-admin privilege activated, and is now compatible with Smart Lock on Android Lollipop & M. (root-only)
Experimental support for Android M Developer Preview, with new "Shallow Hibernation" - application context and push notification are all preserved in hibernation.
Click to expand...
Click to collapse
About Android M support (experimental)
Since Android M is still in early developer preview stage, anything could change before the final version is out. So is the experimental support in Greenify.
Greenify now takes advantage of App Standby feature in Android M and combine it with the efforts of traditional implementation to create a new "Shallow Hibernation" state for greenified apps. In this state, app won't lose the context before being switched to the background and could also receive GCM push message in hibernation.
Known issues
The "... Lock Screen" shortcut with new implementation is reacting slower than before in some lower end device, due to slow root invocation.
Get beta versions
Opt-in to beta channel or download the apk file.
Please apk file Greenify v2.7 beta 1 ..
http://www13.zippyshare.com/v/HAwp78U6/file.html
Any changes for LP? or for M only?
aeonix_05 said:
Any changes for LP? or for M only?
Click to expand...
Click to collapse
Only the first one is for Android M.
cenzo1996 said:
Please apk file Greenify v2.7 beta 1 ..
Click to expand...
Click to collapse
Link is now provided in OP.
@oasisfeng Thanks for the update. Working fine but the problem that the notifications don't get delivered unless the screen is turned on manually remains on LP. Greenify shows as push received "x" minutes ago but no notification sound or anything related when phone screen is off.
nice
I have a slight problem with the newest version: Any app that happens to be awake when I open Greenify just stays awake. At the moment Google App, Google Play Store, ACalendar Plus and Weather don't wanna get closed, they just stay persistently. If I press to hibernate them, I get a toast message that they're hibernated, but they are not... Now I don't know whether it's an error of function or of displaying
gALEXyS4 said:
I have a slight problem with the newest version: Any app that happens to be awake when I open Greenify just stays awake. At the moment Google App, Google Play Store, ACalendar Plus and Weather don't wanna get closed, they just stay persistently. If I press to hibernate them, I get a toast message that they're hibernated, but they are not... Now I don't know whether it's an error of function or of displaying
Click to expand...
Click to collapse
Yup, I have that problem too. The toast says hibernated but they actually don't get hibernated.
I have a slight problem with the newest version: Any app that happens to be awake when I open Greenify just stays awake. At the moment Google App, Google Play Store, ACalendar Plus and Weather don't wanna get closed, they just stay persistently. If I press to hibernate them, I get a toast message that they're hibernated, but they are not... Now I don't know whether it's an error of function or of displaying
Click to expand...
Click to collapse
+1 for Samsung Galaxy S6 android 5.0.2 root
gALEXyS4 said:
I have a slight problem with the newest version: Any app that happens to be awake when I open Greenify just stays awake. At the moment Google App, Google Play Store, ACalendar Plus and Weather don't wanna get closed, they just stay persistently. If I press to hibernate them, I get a toast message that they're hibernated, but they are not... Now I don't know whether it's an error of function or of displaying
Click to expand...
Click to collapse
+1
Sent from my SM-G900F using Tapatalk
gALEXyS4 said:
I have a slight problem with the newest version: Any app that happens to be awake when I open Greenify just stays awake. At the moment Google App, Google Play Store, ACalendar Plus and Weather don't wanna get closed, they just stay persistently. If I press to hibernate them, I get a toast message that they're hibernated, but they are not... Now I don't know whether it's an error of function or of displaying
Click to expand...
Click to collapse
Same here. S4 with S6 featured ROM.
Gesendet von meinem Nexus 7 WiFi mit Tapatalk
Sony Z1c LP 5.0.2 too . I am back on the last version now.
Gesendet von meinem D5503
ottomanrage said:
@oasisfeng Thanks for the update. Working fine but the problem that the notifications don't get delivered unless the screen is turned on manually remains on LP. Greenify shows as push received "x" minutes ago but no notification sound or anything related when phone screen is off.
Click to expand...
Click to collapse
I'm sorry, I still can't figure out the cause of that issue yet. It seems like only affect some apps in some situations. This combination is not clear in any form.
gALEXyS4 said:
I have a slight problem with the newest version: Any app that happens to be awake when I open Greenify just stays awake. At the moment Google App, Google Play Store, ACalendar Plus and Weather don't wanna get closed, they just stay persistently. If I press to hibernate them, I get a toast message that they're hibernated, but they are not... Now I don't know whether it's an error of function or of displaying
Click to expand...
Click to collapse
Which Android version and device model? What working mode?
oasisfeng said:
I'm sorry, I still can't figure out the cause of that issue yet. It seems like only affect some apps in some situations. This combination is not clear in any form.
Click to expand...
Click to collapse
Thanks for the reply. For me it's mostly in whatsapp and viber. I have the logs for the GCM push if you need. And it happens everytime. Basically in all situations.
And as for the latest beta update, I have an I9300 running 5.1.1 with boost mode (xposed).
oasisfeng said:
Which Android version and device model? What working mode?
Click to expand...
Click to collapse
android 5.0.2 SAMSUNG GALAXY S6
ottomanrage said:
Thanks for the reply. For me it's mostly in whatsapp and viber. I have the logs for the GCM push if you need. And it happens everytime. Basically in all situations.
And as for the latest beta update, I have an I9300 running 5.1.1 with boost mode (xposed).
Click to expand...
Click to collapse
I have collected many logs in the past months. But both Google Play services and these apps are closed source. Logs are not enough to figure out why they can't post notifications even if push message was received.
Several attempts have been made trying to fix the issue, but still no luck yet.
Maybe they are not prepared to receive push message in hibernation state.
gALEXyS4 said:
I have a slight problem with the newest version: Any app that happens to be awake when I open Greenify just stays awake. At the moment Google App, Google Play Store, ACalendar Plus and Weather don't wanna get closed, they just stay persistently. If I press to hibernate them, I get a toast message that they're hibernated, but they are not... Now I don't know whether it's an error of function or of displaying
Click to expand...
Click to collapse
Have you connected external power to the device? If so, that's because Greenify will not perform auto-hibernation during charging since this version. The incorrect prompt information is the known issue I've listed in the OP. I'll add more clear prompt for this.
all ok with hypernate here
Hi,
for my basic understanding of Greenify I would like to know:
I ran Greenify 2.7 in root mode, currently without Xposed. This because I want to read more about Xposed first before installing.
It normally should hibernate the configured Apps automatically if I understand right.
In what time intervalls does Greenify check if such a App has been woken up and therefore hibernated again?
I watch the battery comsumption with 3C Tools and see, that the saving effect takes place only if I check manually every hour or so. Doing so, Greenify hibernates woken up Apps well and the battery saving effect is really good. But during the night I can see that the hibernation does not take place and I have 20% less capacity.
Sorry, if this question has already been discussued elsewhere. I have seearched here already, but being not sure, to find the right answers.
Edit: Now I Installed Version 2.8 Beta 8 and watch the behaviour.
Regards, Onurbi
onurbi said:
Hi,
for my basic understanding of Greenify I would like to know:
I ran Greenify 2.7 in root mode, currently without Xposed. This because I want to read more about Xposed first before installing.
It normally should hibernate the configured Apps automatically if I understand right.
In what time intervalls does Greenify check if such a App has been woken up and therefore hibernated again?
I watch the battery comsumption with 3C Tools and see, that the saving effect takes place only if I check manually every hour or so. Doing so, Greenify hibernates woken up Apps well and the battery saving effect is really good. But during the night I can see that the hibernation does not take place and I have 20% less capacity.
Sorry, if this question has already been discussued elsewhere. I have seearched here already, but being not sure, to find the right answers.
Edit: Now I Installed Version 2.8 Beta 8 and watch the behaviour.
Regards, Onurbi
Click to expand...
Click to collapse
Have you enabled Greenify in Device>Settings>Security>Device Administrator?
Do you have the donation pack?
Which version of android and what phone?
Normally, Greenify watches for apps waking up and hibernates them. There is no fixed interval for checking.
From your description I would guess that only manual hibernation is working and not automatic hibernation.
Thank you for your answer!
tnsmani said:
Have you enabled Greenify in Device>Settings>Security>Device Administrator?
Click to expand...
Click to collapse
Yes, there is a "Greenify Automator". This entry is there since Version 2.7 has been installed. It is ok for 2.8 Beta 8 also?
Do you have the donation pack?
Click to expand...
Click to collapse
Yes, I have.
Which version of android and what phone?
Click to expand...
Click to collapse
5.0.1 ,64 Bit, rooted, Huawei P8 Lite (ALE-21)
Normally, Greenify watches for apps waking up and hibernates them. There is no fixed interval for checking.
Click to expand...
Click to collapse
Ok. I could imagine, that a timer controlled action like I do it, would help.
When Greenify is not in "root" mode, it does an automated "Stop" of the Apps. With root mode it reports, that the found Apps are hibernated. When Greenify does this only once and another App will be waked up later, this now again running App will drain the battery anyway. That's not particular senseful I find. Therefore my question about regular checks.
From your description I would guess that only manual hibernation is working and not automatic hibernation.
Click to expand...
Click to collapse
I think so as well. But the Settings tell me that automatic hibernation is active (in German)!
The last 2 hours suddenly a process has been started named SUPL20Services. It will be reported by the 3C Toolbox analyser. This process caught my eyes several times already. The only context I found googling has to to with GPS. But when I disable GPS, this process comes up anyway. I tried to identify the parent process of it with "ps -t", but to no avail. There is no.
In this case Greenify can do nothing I believe.
Regards, Onurbi
onurbi said:
Thank you for your answer!
When Greenify is not in "root" mode, it does an automated "Stop" of the Apps. With root mode it reports, that the found Apps are hibernated. When Greenify does this only once and another App will be waked up later, this now again running App will drain the battery anyway. That's not particular senseful I find. Therefore my question about regular checks.
Click to expand...
Click to collapse
When an app is hibernated, it can not wake up again unless you specifically open it or another app/process wakes it up. So a hibernated app continuing to run does not happen unless you permit it.
If you find that a hibernated app is woken up again (not specifically by you), long press the app's name in Greenify and you will get a scissors icon on top. Clicking that icon will pop up a dialogue box which will tell you what woke up that app and if you don't want it to be woken up, click the appropriate button in the dialogue box.
If you find that a hibernated app is woken up again (not specifically by you), long press the app's name in Greenify and you will get a scissors icon on top. Clicking that icon will pop up a dialogue box which will tell you what woke up that app and if you don't want it to be woken up, click the appropriate button in the dialogue box.
Click to expand...
Click to collapse
Yes I understand this.
I think I tried this in the past and Google Services has been reported what has woken up, in this case, Hangouts. Hangouts is very "aggessive" I found and will very often be active again.
I'll have a look at the scissors next time a app will be active.
onurbi said:
Yes I understand this.
I think I tried this in the past and Google Services has been reported what has woken up, in this case, Hangouts. Hangouts is very "aggessive" I found and will very often be active again.
I'll have a look at the scissors next time a app will be active.
Click to expand...
Click to collapse
A word of caution: some apps require such wakeups to function properly. So if after using the scissors, you find that the app is not functioning correctly, you can again long press it and then click the three dot menu at top right in Greenify. You will get an option to reattach whatever you had cut earlier.
tnsmani said:
A word of caution: some apps require such wakeups to function properly. So if after using the scissors, you find that the app is not functioning correctly, you can again long press it and then click the three dot menu at top right in Greenify. You will get an option to reattach whatever you had cut earlier.
Click to expand...
Click to collapse
Thanx, I'll have a look at ths fact!
I lost magnify icon....im usin greenify 2.7.1 final stable with donation. Why??
Thankss
Can someone help?
hawkdown77 said:
I lost magnify icon....im usin greenify 2.7.1 final stable with donation. Why??
Thankss
Click to expand...
Click to collapse
Which magnify icon are you talking about?
tnsmani said:
Which magnify icon are you talking about?
Click to expand...
Click to collapse
When we are inside greenify, in up right corner there was a magnify icon to choice APP that we want to freenify. Now this icon disappear
hawkdown77 said:
When we are inside greenify, in up right corner there was a magnify icon to choice APP that we want to freenify. Now this icon disappear
Click to expand...
Click to collapse
I am on 2.8 beta9. There is no such icon. I have never used such an icon in Greenify and so I am not sure whether it was available in any version.
I am not saying that you are wrong but just that I don't remember. I also don't think that it is of much use unless you have hundreds of apps.
hawkdown77 said:
When we are inside greenify, in up right corner there was a magnify icon to choice APP that we want to freenify. Now this icon disappear
Click to expand...
Click to collapse
Due to restriction enforced by newer Android system, that selector could no longer work, thus was removed long ago.
oasisfeng said:
Due to restriction enforced by newer Android system, that selector could no longer work, thus was removed long ago.
Click to expand...
Click to collapse
But there some apps that i can not choose because it not show in the list of apps. How can i proceed to greenify them?
---------Update on 2017-12-10----------
I spent some time on this issue these days and made a little progress. Here is what I found:
I am using Island (com.oasisfeng.island), which is also an Oasis Feng's project, to manage some apps which ask too much permissions and do not use GCM as push serivce.
The progress listed in the quick action menu are actually installed in "island", but are also recognized as "mainland" apps. They were once installed in the "mainland" and added to the Greenify, but already been moved to "island". So Greenify could not stop an app that did not exist.
Steps to reproduce the issue:
1. Install Amap (com.autonavi.minimap) and Alipay (com.eg.android.AlipayGphone) into "mainland" and "island";
2. Add both of the four apps into Greenify;
3. Remove them from "mainland";
4. In Island app, freeze then unfreeze these two apps;
5. The quick action notification menu should look like this:
https://i.imgur.com/0weJIRj.png
As you can see, the apps that were installed in the "island" are tagged with "(in Island)", but there are also two apps, which should have already been removed from "mainland", listed in there. And "hibernate all" function would do nothing to them, because they were actually not exist.
I'm not sure it's a bug with Greenify or Island, or even both.
Temporary Fix:
1. Install the apps that can't be hibernated into "mainland";
2. Remove them from Greenify;
3. Uninstall these apps from "mainland".
-----------Original Post----------------
Device: BlackBerry PRIV (STV100-1)
System: Adroid 6.0.1
Greenify: 3.8.5
Island: 2.5.0/2.5.2
Issue
All apps that were added to Greenify were listed in the quick action notification menu, even if they were already been hibernated.
When did this issue came out?
Recent update.
What do you expect?
Is there a way to set this function to list running apps only like before?
-----------Original Post End-------------
Explorare said:
Device: BlackBerry PRIV (STV100-1)
System: Adroid 6.0.1
Greenify: 3.8.5
Issue
All apps that were added to Greenify were listed in the quick action notification menu, even if they were already been hibernated.
When did this issue came out?
Recent update.
What do you expect?
Is there a way to set this function to list running apps only like before?
Click to expand...
Click to collapse
Not seeing this; QAN working as before. Might be config/device/rom specific. Greenify 3.8.5 on Android 7.1.2 w/Xposed (official).
Davey126 said:
Not seeing this; QAN working as before. Might be config/device/rom specific. Greenify 3.8.5 on Android 7.1.2 w/Xposed (official).
Click to expand...
Click to collapse
Thanks for your reply. I have updated the post with more details. Would you like to have a try on reproducing the problem on your device? Thanks.
Explorare said:
Thanks for your reply. I have updated the post with more details. Would you like to have a try on reproducing the problem on your device? Thanks.
Click to expand...
Click to collapse
Thanks for the additional details. Island is "Early Access" with clear notations around potential instability. It's up to the developer to take note of this thread and address any issues he feels are pertinent. It looks like you have identified a workaround; hopefully that will benefit others while things get sorted.