Related
"Aggressive Doze" is one of the new experimental features exclusive for Android 6.0 Marshmallow. The best part is that it works on non-rooted device!
Once enabled in settings, your device will enter Doze Mode in minutes (instead of hours stationary normally) after the screen goes off if not charging, to improve its power-saving efforts.
Doze mode is a new power saving mechanism introduced in Android 6.0. In this mode, background behaviors of all apps (except white-listed ones) are strictly prohibited, until next user interaction or charging. The device will also periodically (in hours) exit doze mode briefly.
This is not the complete solution for a better Doze, currently it still cannot keep your device rest in doze if you are carrying it around. It is expected to maximize the power-saving effect of the stock Doze mode. (UPDATE: This "interruption by motion" behavior can be completely prevented in the newest version 2.9 beta, see FAQ.1 for details) Also it may break some background functionality of your daily apps if they are not developed with Android Doze in mind.
FAQ
When I'm moving around, the Aggressive Doze is not working?
Android system uses a low power "Significant Motion Sensor" to track movement and exits Doze Mode if significant movement is detected. Aggressive Doze will not try to enter Doze after that, to avoid constantly entering and exiting Doze. Since the stock Doze is designed for battery-saving in stationary state, Android still wants to keep your apps in sync with fresh state if you are carrying it around.
In the new version 2.9 beta, this "interruption by motion" behavior can be prevented completely if "DUMP" permission is granted manually via USB-connected computer.
Click to expand...
Click to collapse
Why is my device very lagging when wake from sleep after a few hours.
This seems like a bad consequence of Android Doze Mode itself if too many apps are installed. Because Doze Mode effectively postpone all the background behaviors during the doze. The longer doze lasts, the more tasks to do when exiting. Consider greenifying more background-itchy apps to reduce the lag, because hibernation is still the essential solution for them.
Click to expand...
Click to collapse
Aggressive Doze is not working sometimes, but again working later.
Check whether there's a alarm clock in less than an hour, by looking for an alarm icon in the status bar. But the icon won't tell you the time of the alarm. You may click the DND tile in the quick launch panel to find out the actual time of the alarm (in the entry with "until next alarm"). This is because Android system refuses to enter doze mode if an scheduled alarm is in less than an hour.
Click to expand...
Click to collapse
Why I can't find this option in settings? My device is on Android 6.0.
Aggressive Doze in Greenify v2.8 should work on all devices with Android 6+, unless the Doze Mode is explicitly disabled by the ROM. If you are using a custom ROM made by community, ask the
ROM modder to enable this flag in the ROM:
Code:
com.android.internal.R.bool.config_enableAutoPowerModes
UPDATE: Since 2.9 beta 1, even if doze is disabled in ROM, Greenify can still activate doze mode after DUMP permission is granted manually via USB-connected computer. Beware, this may break things since the ROM is not made to be compatible with Doze.
Click to expand...
Click to collapse
oasisfeng said:
Within the new version 2.8 beta (rolling out), there's an early attempt for better Doze mode in control. It currently activate doze mode as early as the screen goes off, and deactivate it when the screen is back on or the charger is connected.
It is surely not the complete solution for a better Doze mode. It is expected to maximize the power-saving effect of Doze mode, but may also break some background functionality of your apps. So I'm listening to all your feedback and opinions, to build a smarter and finer-tweaked Doze mode in Android 6.0.
Together with the "Shallow Hibernation" released in version 2.7, let's start a new adventure of Greenify with Android Marshmallow.
Click to expand...
Click to collapse
Thanks buddy! Lets start again
Hi Oasis, I tried to perform the steps you gave but I am getting the following error
/system/bin/sh: grant: not found
this happens when I try to run the first command to grant DUMP permissions. My Nexus 5 is not rooted and ADB is running and fully up to date.
Edit: for anyone experiencing this issue try the following
1. After checking "adb devices" run "adb shell"
2. Type "pm grant com.oasisfeng.greenfiy android.permission.DUMP"
3. Type "pm grant com.oasisfeng.greenify android.permission.READ_LOGS"
Hello,
First of all, i'm happy with the donation version!
With this new feature there's a thing I've noticed right away. Apparently doze works with all the apps, including whatsapp, which is the app i use the most.
When doze it's activated messages arrive in intervals and it's not that reliable. Anyways, when doze activates by itself, i'm ok with the messages getting delayed, because i'm actually not using the phone. The thing with the integration through greenify, is that messages stop arriving right away.
Do you think there could be a way to kind of "bypass" certain applications? If it's possible it would work like stamina mode from Sony.
Anyways, it's just a comment... I like the instant doze since doze really helps with battery!
blanco2701 said:
Hello,
First of all, i'm happy with the donation version!
With this new feature there's a thing I've noticed right away. Apparently doze works with all the apps, including whatsapp, which is the app i use the most.
When doze it's activated messages arrive in intervals and it's not that reliable. Anyways, when doze activates by itself, i'm ok with the messages getting delayed, because i'm actually not using the phone. The thing with the integration through greenify, is that messages stop arriving right away.
Do you think there could be a way to kind of "bypass" certain applications? If it's possible it would work like stamina mode from Sony.
Anyways, it's just a comment... I like the instant doze since doze really helps with battery!
Click to expand...
Click to collapse
+1
In the developer preview of 6.0 you could exclude apps from being doze'd. Such an option would be great in Greenify as well, since messages don't wake up the phone with activated aggressive doze
shakuyi said:
Hi Oasis, I tried to perform the steps you gave but I am getting the following error
/system/bin/sh: grant: not found
this happens when I try to run the first command to grant DUMP permissions. My Nexus 5 is not rooted and ADB is running and fully up to date.
Edit: for anyone experiencing this issue try the following
1. After checking "adb devices" run "adb shell"
2. Type "pm grant com.oasisfeng.greenfiy android.permission.DUMP"
3. Type "pm grant com.oasisfeng.greenify android.permission.READ_LOGS"
Click to expand...
Click to collapse
Sorry for the typo, I just corrected it in the online guide. Thanks for the report.
blanco2701 said:
Hello,
First of all, i'm happy with the donation version!
With this new feature there's a thing I've noticed right away. Apparently doze works with all the apps, including whatsapp, which is the app i use the most.
When doze it's activated messages arrive in intervals and it's not that reliable. Anyways, when doze activates by itself, i'm ok with the messages getting delayed, because i'm actually not using the phone. The thing with the integration through greenify, is that messages stop arriving right away.
Do you think there could be a way to kind of "bypass" certain applications? If it's possible it would work like stamina mode from Sony.
Anyways, it's just a comment... I like the instant doze since doze really helps with battery!
Click to expand...
Click to collapse
If WhatsApp uses GCM for instant message push, then maybe the developer has not yet adopted for the priority GCM push which goes through in the Doze mode. This is what Google suggests all IM message to use.
I'll try to work around this issue, maybe allow all GCM push to exit doze mode for a while.
MrMarques01 said:
+1
In the developer preview of 6.0 you could exclude apps from being doze'd. Such an option would be great in Greenify as well, since messages don't wake up the phone with activated aggressive doze
Click to expand...
Click to collapse
You can still do that in Android 6.0 final version, but highly discouraged.
Today I got Greenify 2.8 beta 1, but still my apps aren't greenified.
Edit: I reinstalled Greenify and su asked me for permission, now it works, thank you.
Best regards
Matthias
If we are rooted does it still require the one-time procedure or can we just install as normal?
oasisfeng said:
Within the new version 2.8 beta (rolling out), there's an early attempt for better Doze mode in control. It currently activate doze mode as early as the screen goes off, and deactivate it when the screen is back on or the charger is connected.
The best part of this feature - NO ROOT REQUIRED! Still you need to perform a one-time procedure with USB-cable and a connected computer, which is surely familiar to many of you XDA members.
This is not the complete solution for a better Doze mode. It is expected to maximize the power-saving effect of Doze mode, but may also break some background functionality of your apps. So I'm listening to all your feedback and opinions, to build a smarter and finer-tweaked Doze mode in Android 6.0.
Together with the "Shallow Hibernation" released in version 2.7, let's start a new adventure of Greenify with Android Marshmallow.
Click to expand...
Click to collapse
Oasisfeng, what's the normal amount of time before doze activates? Would it perhaps be better to have an option to set the amount of minutes after screen off to start the aggresive Doze?
I just test greenify beta, and battery seems like always for now... Tomorrow I'll see better how new greenify works...
No root really ? It would be useful
@oasisfeng
mine is rooted but still the Doze feature is not activated.
Is it only for 6.0 devices?
atulclassic said:
@oasisfeng
mine is rooted but still the Doze feature is not activated.
Is it only for 6.0 devices?
Click to expand...
Click to collapse
Yes.
atulclassic said:
@oasisfeng
mine is rooted but still the Doze feature is not activated.
Is it only for 6.0 devices?
Click to expand...
Click to collapse
*Clears throat* "Aggressive Doze" is a new experimental feature for Android 6.0
Smultie said:
Oasisfeng, what's the normal amount of time before doze activates? Would it perhaps be better to have an option to set the amount of minutes after screen off to start the aggresive Doze?
Click to expand...
Click to collapse
I‘m thinking about the same thing.It'd be great to have an option to set the time to start the doze mode. It'd be so damn perfect!
Do applications which are set to bypass Doze still work?
randy6644 said:
I‘m thinking about the same time. It'd be great to have an option to set the time to start the doze mode. It'd be so damn perfect!
Click to expand...
Click to collapse
Great minds think alike!
Smultie said:
Oasisfeng, what's the normal amount of time before doze activates? Would it perhaps be better to have an option to set the amount of minutes after screen off to start the aggresive Doze?
Click to expand...
Click to collapse
Currently zero. I'm planning for a smarter delay before doze (probably the same as the delay before greenified apps hibernate). But for now, I'd like to push the benefit to the limit for a test run and find the actual drawback of 0 delay.
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.
This thread is served as a general discussion and feedback for recent beta versions. It will be updated with newest version in title and change log in the first post.
Changelog:
v2.95 beta 3
Aggressive Doze now works in non-root mode on Android 7. (Manual privilege granting via USB required)
Improved GCM Wake-up (Xposed) for some misbehaving apps. (e.g. WeChat)
Improved the stability of accessibility service.
Fixed Wake-up Cut-off on Android 6+.
Fixed Shallow Hibernation (Android 6+) in boost mode (Xposed).
Fixed alarm analysis on Android 6+.
Fixed the false "Root privilege not granted" notification.
Fixed the verification failure in a short time after donation package is installed.
v2.95 beta 2
Wake-up cut-off now works on Android 7.0 (root).
Improved the overall stability and smoothness of non-root auto-hibernation.
v2.95 beta 1
Auto-hibernation in non-root mode is now compatible with secured key-guard. No more compromise for device security!
Screen-off by Greenify no longer invalidates fingerprint unlock and Smart Lock. Be sure to enable "Alternative Screen Off" in settings.
Aggressive Doze and doze notification is now compatible with Android 7.0 in root and boost mode. (support for non-root mode on the way)
Tasker plug-ins for toggling Auto-Hibernation and Aggressive Doze.
Improved app state detection on Android 6.0+.
Click to expand...
Click to collapse
Known issues
Doze on the Go is not yet compatible with Android 7.0 in non-root mode. We are seeking for a proper solution.
Get beta versions
Opt-in to beta channel or download the apk file.
oasisfeng said:
This thread is served as a general discussion and feedback for recent beta versions. It will be updated with newest version in title and change log in the first post.
Changelog:
Known issues
None.
Get beta versions
Opt-in to beta channel or download the apk file.
Click to expand...
Click to collapse
Works on my Nexus 6! awesome stuff!
italia0101 said:
Tried the aggressive doze on my Nexus 6 ,,
Had it plugged into my PC with a logcat running . i used the " battery unplug " command .
I can see it go into Doze on screen off . a new notification says " entered doze mode" , but with a bit of shaking a movement it wakes up , so on the Nexus 6 at least it still gets awoken with motion
Click to expand...
Click to collapse
Have you granted the DUMP permission manually?
oasisfeng said:
Have you granted the DUMP permission manually?
Click to expand...
Click to collapse
No i have root, but with your suggestion from the other thread it seems to work! so thanks for that, i've edited my post above
Problem with galaxy S6 G920f Android 5.1.1 xposed and rooted.
Problem in open setting, FC App in bêta 9.1
naudmick said:
Problem with galaxy S6 G920f Android 5.1.1 xposed and rooted.
Problem in open setting, FC App in bêta 9.1
Click to expand...
Click to collapse
Sorry, I messed up with Android 4.x & 5.x in beta 1, a fix is pushing out.
I have a concept to offer for a new beta build.
Is it possible to make a hybrid engine, where we can choose per app the ones we want to be hibernated with the normal mode and what apps we want to use shallow hibernation?
So for example i can set whatsapp for shallow hibernation and fb messenger to normal hibernation mode
@oasisfeng Just curious if you have any idea how to fix this problem: one of the recent updates of Greenify made my fingerprint sensor during sleep no longer work; I have to wake up my device (turn the screen on) for it to respond again. Any ideas? (I am fairly certain it is Greenify as 1) nothing recently has changed, 2) somebody on the Nexus 5X subreddit also had this problem)
Pupet_Master said:
I have a concept to offer for a new beta build.
Is it possible to make a hybrid engine, where we can choose per app the ones we want to be hibernated with the normal mode and what apps we want to use shallow hibernation?
So for example i can set whatsapp for shallow hibernation and fb messenger to normal hibernation mode
Click to expand...
Click to collapse
Ye, that's the plan in the next major version (3.0 probably), which needs a completely redesign of the UI.
oasisfeng said:
Ye, that's the plan in the next major version (3.0 probably), which needs a completely redesign of the UI.
Click to expand...
Click to collapse
Thanks, i can't wait for it
draggehn said:
@oasisfeng Just curious if you have any idea how to fix this problem: one of the recent updates of Greenify made my fingerprint sensor during sleep no longer work; I have to wake up my device (turn the screen on) for it to respond again. Any ideas? (I am fairly certain it is Greenify as 1) nothing recently has changed, 2) somebody on the Nexus 5X subreddit also had this problem)
Click to expand...
Click to collapse
I've never had this issue on my daily Nexus 5X. Do you use nav-bar gesture to hibernate apps and turn off the screen?
Please try disabling some of the features (Aggressive Doze, Shallow Hibernation for example) in Greenify and try again to narrow down the cause.
oasisfeng said:
I've never had this issue on my daily Nexus 5X. Do you use nav-bar gesture to hibernate apps and turn off the screen?
Please try disabling some of the features (Aggressive Doze, Shallow Hibernation for example) in Greenify and try again to narrow down the cause.
Click to expand...
Click to collapse
Disabling aggressive doze right now, I'll report back.
I updated from 2.9 Beta 1 to Beta 2 and now doze seems to be gone. Doze was working in Beta 1. My phone is rooted.
It's a Dream. 3 percent in 8 hours. Calls and WhatsApp messages arrive anyway. I don't need more.
arunkafley said:
I updated from 2.9 Beta 1 to Beta 2 and now doze seems to be gone. Doze was working in Beta 1. My phone is rooted.
Click to expand...
Click to collapse
Is your device running Android 6.x? Be sure to grant the DUMP permission manually as suggested in the first post.
lusto170859 said:
It's a Dream. 3 percent in 8 hours. Calls and WhatsApp messages arrive anyway. I don't need more.
Click to expand...
Click to collapse
It's usually inaccurate for the first a few percentages from 100% downwards.
I'm going to prepare for and celebrate the Chinese New Year in the following two weeks. The next beta release is probably not going to be released soon.
I'll check and reply to posts here occasionally during the holiday.
oasisfeng said:
Is your device running Android 6.x? Be sure to grant the DUMP permission manually as suggested in the first post.
Click to expand...
Click to collapse
even if i have root ?
thanks for the hard work
oasisfeng said:
Is your device running Android 6.x? Be sure to grant the DUMP permission manually as suggested in the first post.
Click to expand...
Click to collapse
Yeah I did that. But before without granting the DUMP permission it was working fine
oasisfeng said:
It's usually inaccurate for the first a few percentages from 100% downwards.
Click to expand...
Click to collapse
Yes I know. But without Aggressive Doze I lost 12% in this period. Normal Doze does not work with my device. (Samsung Galaxy S2plus CM13)
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 have installed several apps that need Accessibility set to On in order for them to keep working. 3 of those keep getting disabled by I guess the system and I have to go in and toggle that permission switch to Off and then back On again. It happens randomly, sometimes after a few days and sometimes after a few hours but when it happens it alway affects those 3 apps together.
The 3 apps are Super Status Bar, Power Shade Premium and Energy Ring. Others like Button Mapper or Nova (for doubletap to sleep) are unaffected.
Those apps are excluded from battery optimization, I'm not rooted (yet) and I don't have any "app killer" running. Googling was no help so I'm hoping someone here has an idea. I'm guessing A12 is doing something shady here, but how do I stop it from happening?
Nimueh said:
I have installed several apps that need Accessibility set to On in order for them to keep working. 3 of those keep getting disabled by I guess the system and I have to go in and toggle that permission switch to Off and then back On again. It happens randomly, sometimes after a few days and sometimes after a few hours but when it happens it alway affects those 3 apps together.
The 3 apps are Super Status Bar, Power Shade Premium and Energy Ring. Others like Button Mapper or Nova (for doubletap to sleep) are unaffected.
Those apps are excluded from battery optimization, I'm not rooted (yet) and I don't have any "app killer" running. Googling was no help so I'm hoping someone here has an idea. I'm guessing A12 is doing something shady here, but how do I stop it from happening?
Click to expand...
Click to collapse
I'm wondering if you've entered Power Saving Mode before this problem occurs? At least 2 of these apps will be killed when Power Saving Mode is entered and you have to restart your device to get it going again. Maybe it also kills the Accessibility service? Not really sure, just throwing it out there.
Lughnasadh said:
I'm wondering if you've entered Power Saving Mode before this problem occurs? At least 2 of these apps will be killed when Power Saving Mode is entered and you have to restart your device to get it going again. Maybe it also kills the Accessibility service? Not really sure, just throwing it out there.
Click to expand...
Click to collapse
No, Power Saving Mode is disabled and the battery wasn't low enough for it to even have kicked in. When it happened (twice!) yesterday the battery was 40-50% both times. Adaptive battery is disabled too so battery "shouldn't" be causing it in any way.
Thanks for replying though
Just a small update:
Oddly enough since I started this thread it hasn't happened again
I did sideload that mid-month update right around the same time of my post, maybe that fixed it ... no idea really, I'm just glad it's not happening any more