Hi all, as title states, recently I found out Greenify hibernate apps are very slow. (I still have old v1.95 apk) And I compare with it to close / hibernate 10 apps at once, surprisingly the old version only took 2 secs with the shortcut to hibernate all apps previously opened but the new one v2.5 hibernate very slowly. Took a bout 7-8 secs to close everything. I am using boost mode by the way.
It appears to be Boost Mode but its not.
FIX: just open Experimental feature and tap on Boost mode again (even if it is already on Boost) Phone will freeze and crash. Then it will boot back up. Reboot your device. It will be back to Instant Hibernation.
Related
Pressing the home button is supposed to close the app to the background and store it in memory, but not use any CPU since it's idling in the back ground right?
I happened to open the stock task manager and find that my stock browser was still consuming CPU power even though it has been "home-buttoned" to the background. Does this have anything to do with the fact that browser was at my Facebook page when it was idling?
Makes me wonder if Android storing the app in memory and not using CPU while it is idle is true, since it seems that the stock browser DOES use abit of power while in the background.
Tempted to get an auto task killer
It should only finish its active page load then go to a frozen state. So test it by checking the CPU usage 5 minutes later or so, should be dead stopped.
Nexus 6 and Moto X (2014), rooted, no Xposed. Both on Android 6.0. Full version of Greenify set to automatically hibernate select apps (Facebook and Amazon being the top offenders). Symptoms:
- When the device is charged, the screen would turn on intermittently every 1-3 minutes.
I was going crazy, trying to identify what app is responsible for this. Reboot in safe mode, charging quietly. Then I started disabling root apps one after another. This behavior stopped when I disabled Greenify.
Then I was trying which setting in Greenify was responsible for this behavior. I discovered that when Automatic Hibernation was off in Greenify (with other features such as Aggressive Doze still active), the phone would not wake while being charged. Then I watched closely what happens when Greenify hibernates apps, and discovered that it displays a toast message - which, in both Nexus 6 and Moto X, is enough to wake the display. After that, the apps would probably wake up, and Greenify will attempt to greenify them again on next cycle. This goes on and on without an end.
Two issues here.
1. Greenify should NOT attempt to hibernate apps while charging - and yet, it does.
2. At least there should be an option for Greenify to NOT display a toast message, in which case the phone will not be awake.
3. Final observation. This behavior does NOT occur on other phones (and tablets!) in my possession. Most probably it's a Moto thing that has something to do with Ambient Display.
Suggested fix:
1. Either remove toast notifications or add an option to disable them.
2. Only greenify apps after some time the phone is NOT on a charger (that is, treat "charger connected" the same way as you treat "display on", resetting the countdown timer before hibernation should occur).
aoleg said:
Nexus 6 and Moto X (2014), rooted, no Xposed. Both on Android 6.0. Full version of Greenify set to automatically hibernate select apps (Facebook and Amazon being the top offenders). Symptoms:
- When the device is charged, the screen would turn on intermittently every 1-3 minutes.
I was going crazy, trying to identify what app is responsible for this. Reboot in safe mode, charging quietly. Then I started disabling root apps one after another. This behavior stopped when I disabled Greenify.
Then I was trying which setting in Greenify was responsible for this behavior. I discovered that when Automatic Hibernation was off in Greenify (with other features such as Aggressive Doze still active), the phone would not wake while being charged. Then I watched closely what happens when Greenify hibernates apps, and discovered that it displays a toast message - which, in both Nexus 6 and Moto X, is enough to wake the display. After that, the apps would probably wake up, and Greenify will attempt to greenify them again on next cycle. This goes on and on without an end.
Two issues here.
1. Greenify should NOT attempt to hibernate apps while charging - and yet, it does.
2. At least there should be an option for Greenify to NOT display a toast message, in which case the phone will not be awake.
3. Final observation. This behavior does NOT occur on other phones (and tablets!) in my possession. Most probably it's a Moto thing that has something to do with Ambient Display.
Suggested fix:
1. Either remove toast notifications or add an option to disable them.
2. Only greenify apps after some time the phone is NOT on a charger (that is, treat "charger connected" the same way as you treat "display on", resetting the countdown timer before hibernation should occur).
Click to expand...
Click to collapse
On my phone Greenify does not attempt hibernation while charging. In fact if I open Greenify while charging, I get the whole list of all the apps chosen by me for hibernation with a text on top saying something like hibernation will take place after the charging is over.
It may have something to do with the way these Moto phones charge. They may, from time to time, report that the charger has been disconnected (while in fact continuing charging). This by itself does not turn on the screen; Greenify does.
aoleg said:
It may have something to do with the way these Moto phones charge. They may, from time to time, report that the charger has been disconnected (while in fact continuing charging). This by itself does not turn on the screen; Greenify does.
Click to expand...
Click to collapse
As a data point my 2013 Moto X does not exhibit this behavior. v2.7.1, rooted, Xposed, boost mode. Only time I have observed a non-interactive toast is in non-root mode; the screen wakes momentarily when apps are hibernated. You can squelch this behavior by disabling Greenify permissions under Accessibility (not needed in root or boost modes).
This was happening for me as well, Nexus 6P on Android 6.0, Greenify 2.8 beta 3. Not only did it wake up the screen during the charge, but it actually stopped the phone from charging and the toast message seemed to include every single app I had Greenified. It was present in both boost and root modes and was the main reason I uninstalled the app.
Symthic said:
This was happening for me as well, Nexus 6P on Android 6.0, Greenify 2.8 beta 3. Not only did it wake up the screen during the charge, but it actually stopped the phone from charging and the toast message seemed to include every single app I had Greenified. It was present in both boost and root modes and was the main reason I uninstalled the app.
Click to expand...
Click to collapse
Same behavior on my 6P on 6.0.1. with the same Greenify version. I disabled automatic hibernate and now the screen stays off during charging.
I get the same with my xperia Z3c running concept rom, except I don't get a toast messsage. I thought I was going crazy when I first noticed this strange behaviour. Found this thread from a Google search by the way.
Which version of Greenify do you noticed this behavior in? It is supposed to be fixed in the recent beta version.
oasisfeng said:
Which version of Greenify do you noticed this behavior in? It is supposed to be fixed in the recent beta version.
Click to expand...
Click to collapse
version 2.8 beta 3 with paid unlocker through play store and xposed. My bad, realised I'm a few beta releases behind. Updated to latest and all is well so far.
*edit: I apologize for the thread title, I didn't notice that I went beyond the character limit while typing.
I seem to have noticed that when using apps that download and sync things in the background (Spotify, Messenger, etc.) while Power Saver is enabled, they stop updating once the screen is turned off or when multitasking. I can tell they stop transferring data and performing tasks once I switch apps because they vanish from the notification shade.
I've never had any problems like this before on Lollipop even with the power saving mode active. I usually have my phone on Power Saver all the time, and it's frustrating me to an extent seeing as to how Marshmallow is forcing me to have it turned off just so I can use my apps properly. I've tried checking app optimization and the apps I mentioned have been turned off for optimization. All my applications are updated as well.
Is this a common issue? Any help with fixing this would be great.
I use Greenify for a long time with donation package, beta tester also.
At the moment I'm using it on a non-rooted Samsung Note 5
I add most of the programs be "greenified" except a few important for me.
The BIG PROBLEM is that in most of the times when there is an ACTIVE CALL, Greenify strart "working" and I can not do aniting. The phone is "black" and I can not even close/finish the call, just waiting Greenify to "hibernate" a.k.a. "force stop" all apps.
Sometime with 5 to 10 "power button" presses I'm able to interupt "hibernation" and to close my call.
Please, add an option to DISSABLE hiberation during a CALL!!!
Somebody else having this problem?
Best regards to all developers!
ChoSmile said:
I use Greenify for a long time with donation package, beta tester also.
At the moment I'm using it on a non-rooted Samsung Note 5
I add most of the programs be "greenified" except a few important for me.
The BIG PROBLEM is that in most of the times when there is an ACTIVE CALL, Greenify strart "working" and I can not do aniting. The phone is "black" and I can not even close/finish the call, just waiting Greenify to "hibernate" a.k.a. "force stop" all apps.
Sometime with 5 to 10 "power button" presses I'm able to interupt "hibernation" and to close my call.
Please, add an option to DISSABLE hiberation during a CALL!!!
Somebody else having this problem?
Best regards to all developers!
Click to expand...
Click to collapse
Have you greenified anything related to phone calls? Can you post a screenshot of what all you have greenified? Do you also use Amplify?
This is not the normal behaviour unless you greenified or limited something which you ought not have.
Nothing related to Call or Phone or other system realated apps are in Greenify list (178 apps).
Normal behaviour of Greenify is to start hibertatiing apps when screen goes off.
(In root or boost (xposed) mode this operation is very fast, it closes many apps at once.)
But in NON-root mode it use standart automated [Force close] dialog or every app, so it takes a second or two per app to close it.
When I make (or receive) a call, I put the phone near to my ear, the proximity sensor turns off the display.
After a while, Greenify starts hibernation process.
There is no problem with the CALL itself, it is not interrupted or disturbed and qualiry is excellent.
The problem is when I take off my phone from my head, proximity sensor "realesed" and display have to goes on (rise) again but this NOT happens.
At this moment Greenify closes apps one by one and screen is OFF.
Call conversation remains active and I can NOT hang up (close) my call.
No reaction if I press [Home] or [Power] buttons.
By pressing many times (5+) [Power] button I'm able to interupt the Greenify hibernation process, display goes on and I see the force close app's dialog.
Now I use drop down menu and press (red earphone icon) to hang up (close) my active call.
That's why I think that settings option in Greenify for "temporary disable of hibernation" during an active call will be very useful especialy for "non-root mode" users.
Do you think it is worth to add such option?
@ChoSmile
When you are on a call, it will hold a wakelock so that the screen going off doesn't affect it. The proximity sensor senses your face near it and switches off the screen. When the phone is held away from the face, the proximity sensor should sense it and switch on the screen. This is the normal behavior.
Greenify starting to hibernate the apps should not affect the proximity sensor sensing. Check the functioning of your proximity sensor because no one else seems to have reported this problem, as far as I know.
I don't think that Greenify hibernates apps during a call ie. while the screen is off during a call. Atleast for me, it doesn't.
ChoSmile said:
I use Greenify for a long time with donation package, beta tester also.
At the moment I'm using it on a non-rooted Samsung Note 5
I add most of the programs be "greenified" except a few important for me.
The BIG PROBLEM is that in most of the times when there is an ACTIVE CALL, Greenify strart "working" and I can not do aniting. The phone is "black" and I can not even close/finish the call, just waiting Greenify to "hibernate" a.k.a. "force stop" all apps.
Sometime with 5 to 10 "power button" presses I'm able to interupt "hibernation" and to close my call.
Please, add an option to DISSABLE hiberation during a CALL!!!
Somebody else having this problem?
Best regards to all developers!
Click to expand...
Click to collapse
By any chance do you have aggressive doze enabled in greenify? I started having about the same issue, i would receive a call and screen would never wake up. I had done a lot of tweaks and wasn't sure what exactly what was causing this. So I did a fresh install and started a little bit at a time doing my tweaks and never got to install greenify yet. So far, phone has been working properly. So maybe this had something to do with aggressive doze or the fact that I had two apps setting aggressive doze, greenify and force doze.
kenboyles72 said:
By any chance do you have aggressive doze enabled in greenify? I started having about the same issue, i would receive a call and screen would never wake up. I had done a lot of tweaks and wasn't sure what exactly what was causing this. So I did a fresh install and started a little bit at a time doing my tweaks and never got to install greenify yet. So far, phone has been working properly. So maybe this had something to do with aggressive doze or the fact that I had two apps setting aggressive doze, greenify and force doze.
Click to expand...
Click to collapse
I disable Aggressive Doze (experimental) but issue happens again, might be no so offen like before I disabled it.
@tnsmani
Do you use Greenify on NON rooted device?
Because on rooted devices, you probably use it "Root" or "Boost" working mode where hiberanating is "at once" for many apps.
ChoSmile said:
I disable Aggressive Doze (experimental) but issue happens again, might be no so offen like before I disabled it.
@tnsmani
Do you use Greenify on NON rooted device?
Because on rooted devices, you probably use it "Root" or "Boost" working mode where hiberanating is "at once" for many apps.
Click to expand...
Click to collapse
Normally I use Greenify in root/boost mode since my phone is rooted.
But to investigate your issue, I ran it in non-root mode (phone is still rooted). Still my screen behaves normally.
I have the same issues exactly non root greenify kicks in during calls and everything goes south. Any solution to disable greenify during calls
Sent from my ONE A2003 using Tapatalk
Guys. Anyine found a solution here? This is a real issue for me. I am using non root and everytime a call starts, screen goes dark, greenify starts and doesn't capture the right screens probably but rather initiates clicks on the task bar on the top. This way I see the WiFi starting or Hotspot being disabled or data being turned off.
All I need is for greenify to not work during calls!
Sent from my ONE A2003 using Tapatalk
ofird said:
Guys. Anyine found a solution here? This is a real issue for me. I am using non root and everytime a call starts, screen goes dark, greenify starts and doesn't capture the right screens probably but rather initiates clicks on the task bar on the top. This way I see the WiFi starting or Hotspot being disabled or data being turned off.
All I need is for greenify to not work during calls!
Click to expand...
Click to collapse
Seems to be a persistent, unresolved issue on some non-rooted devices with stock ROMs. You'll probably have to abandon Greenify.
My worst issues with battery drain is when the phone is on and not off. Maube screen brightness. I don't know but it drains like crazy
Sent from my ONE A2003 using Tapatalk
ofird said:
My worst issues with battery drain is when the phone is on and not off. Maube screen brightness. I don't know but it drains like crazy
Click to expand...
Click to collapse
Your ROMs built in battery stats may (likely will) provide clues to that type of drain. For a more comprehensive assessment try GSAM which is a available in the Play Store. BBS can also help but it's a little more difficult to interpret IMHO. Good luck.
I know that a lot of folk use apps like Greenify, Power Nap, Amplify, Force Doze, etc along with things like Pixel Filter, Smart Pixel feature in some roms etc, but are all these really necessary with current phones?
I have used all of the above together for years but curious about if I really need to now and if they are just impacting my battery more than they save? Do I really need them all now? I'm not using ForceDoze currently as Havoc OS has it's own doze settings and aggressive profile, but I'm wondering if Power Nap is even needed if I have Greenify and Amplify.
Just trying to reduce the apps I need without compromising my standby drain as I am running into odd issues like Magisk failing to grant root after a few minutes or so uptime unless I restart the phone and quickly open the app I need to grant root (once in the allowed list, they work flawlessly. It's just the initial prompt), messages like Whatsapp/Facebook not coming through even though they are exempt from battery optimisations and whitelisted in all the above apps and fingerprint/double tap to wake not working after 10 minutes unless I hit the power button first. I feel there are conflicts going on here which I have only had since having my OnePlus 6 this month. Not an issue with my S5 with this exact setup which was running for years and all my issues are non-existent if I leave the phone stock.
I am obviously going wrong somewhere and need to figure out where.
Also, if I run pixel filter or the smart pixel feature built into Havoc OS, am I better doing that or just turning it off and lowering the brightness? Smart pixel dims the screen slightly which I have to counter by raising the brightness. That's the one thing that has me confused as to which is actually using more juice.
Just in case I am doing something wrong, I have written down what I do in order after installing a new ROM in the attempt of maximising battery life. Doesn't seem tied to Havoc OS, but to my OnePlus 6 as I never had these issue with my previous S5.
Below is after the usual TWRP, Magisk, ROM and setting up settings etc
-Install Greenify (donation package), Amplify, Power Nap, EdXposed, Riru Core, Riru Yahfa, NFS, Better Battery Stats.
-After enabling all of them in EdXposed and restarting, I fire up Greenify and turn on all Xposed features and donation features but leave smart hibernation, ignore background free and aggressive doze off.
-Greenify all games, apps I use rarely and system apps like Camera, Print Spooler and Bookmark Provider
-Open Power Nap, select Endurance mode and whitelist Magisk, EdXposed, Greenify, Tasker, Messages, Phone, WhatsApp, BBS and LastPass (Power Nap seemed to disable it's autofill service)
-Start up Amplify so it does it's checks and exit
-Set up BBS
-Remove all these apps from OS battery optimisation
-Reboot to recovery and copy over the Amplify settings file to it's folder within data/data/Amplify folder/shared prefs and restart to system. (basic Google and app specific wakelocks you will find in all Amplify guides on XDA and nothing else)
-Add Play Store, Services, Framework, Google Pay and my banking app to Magisk Hide list and EdXposed blacklist to pass SafetyNet.
And this is where my problems start happening. This is what I have done for years and I never had issues. I suppose I could do these one at a time until I hit that wall where things go wrong, but thought I would ask here in case any of you can spot the mistake. Thanks in advance for the help or roasting lol
*Edit*
If anyone has any other ideas to reduce battery drain, you can tell me. I'm trying to maximise both screen on and screen off time without compromising too much.