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.
Dear all,
Does anyone here know how to use Tasker app to auto enable and disable the always on display (AOD) setting in a specific time?
I noticed that enabling AOD consumes lot of battery, the battery drained 15-20% when my phone was idle overnight from 12am-7am. After I turn off the AOD, the battery drains only 5% overnight.
I'm thinking to use Tasker to disable the AOD when I'm sleeping to reserve the battery, and turn it back on after 8am. Unfortunately I couldn't find anything in the Tasker app that allows me to do so. But I'm able to do this to my previous Samsung Galaxy s7 edge. Maybe I missed out something when I tried to do that for my LG G5?
Is there anything in the Secure Settings app that might help with this? Worth investigating - haven't rooted yet (just whilst I'm getting used to phone and working out pros and cons) so can't check for you.
For what it's worth I just turn phone over which switches off AOD, easy to turn back to check time in dark...
Yeah I didn't notice that my AOD would turn off when I turned it over till later and thought that was a smart implementation for it. Seems very intuitive.
I'll revive this thread, as I'm looking for a tasker solution too. Is there any way I can disable the AOD via Tasker? I've a H850, stock nougat, rooted.
Try this method:
https://www.reddit.com/r/GalaxyS7/comments/4knout/always_on_screen_only_while_charging/
But replace "aod_mode" to "enable_ext_display_on_lcd_off"
I may be a bit late to the party, but you really don't need the paid version of secure settings app to toggle this setting on Samsung. Just run the following shell commands from tasker (make sure you check the "use root" box):
To enable:
Code:
settings put system aod_mode 1
To disable:
Code:
settings put system aod_mode 0
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'm using CM13 and new to using Greenify as I just bought the donation package but have some questions that I'm not sure about.
1. I have instant messaging apps (Whatsapp and WeChat) and games on my phone, when I finish using the app, I press the home button and have them running in the background, does that uses more battery or do I need to add the apps to the hibernation list?
2. Should I use hibernate or shallow hibernation as I switched from iPhone to OnePlus 3 and on the iPhone when I reopen the app, it will return to where I left it.
3. I have enabled aggressive doze so that it will go to sleep mode when the screen is off, will I get delay Whatsapp and Wechat messages or do I need to add it to the whitelist so notifications comes instantly when I receive them?
Many thanks!
Lither said:
I'm using CM13 and new to using Greenify as I just bought the donation package but have some questions that I'm not sure about.
1. I have instant messaging apps (Whatsapp and WeChat) and games on my phone, when I finish using the app, I press the home button and have them running in the background, does that uses more battery or do I need to add the apps to the hibernation list?
2. Should I use hibernate or shallow hibernation as I switched from iPhone to OnePlus 3 and on the iPhone when I reopen the app, it will return to where I left it.
3. I have enabled aggressive doze so that it will go to sleep mode when the screen is off, will I get delay Whatsapp and Wechat messages or do I need to add it to the whitelist so notifications comes instantly when I receive them?
Many thanks!
Click to expand...
Click to collapse
1. Any app which is not greenified will run in the background once it is opened and then dismissed by the Home button. As far as the IM apps are concerned, the advice of the Dev is not to greenify them if you rely on them. However, some people have successfully greenified those IM apps which use GCM without issues but some others complain of delayed notifications. So it may be better not to greenify them if you rely on them. Of course they will consume more battery since they are running in the background.
2. If you want iPhone like behaviour, use shallow hibernation. Otherwise, the apps will start afresh.
3. It is better to add such apps to the white list.
i could be wrong.... but i noticed that most of the times aggressive doze does NOT exted the real battery life...... maybe it COULD extend it if you do not touch the phone for long periods like 2...4 hours at time, but if you make a normal usage of the phone i suspect that activating and deactivating doze is DRAINING more battery than it tries to save!!!
.........any other though?
realista87 said:
i could be wrong.... but i noticed that most of the times aggressive doze does NOT exted the real battery life...... maybe it COULD extend it if you do not touch the phone for long periods like 2...4 hours at time, but if you make a normal usage of the phone i suspect that activating and deactivating doze is DRAINING more battery than it tries to save!!!
.........any other though?
Click to expand...
Click to collapse
Similar observation on battery savings. In most cases any power related benefits of aggressive doze are wiped out when the device wakes from its comma and performs a bunch of 'catch up' tasks. Such behavior can lead to lag immediately after wake which is a common complaint associated with aggressive doze. That said, aggressive doze may have other situational benefits...especially over longer durations. As always YMMV.
yes, i think about a person who does pick up the phone just every 4...5 hour at day because it is not important (for him) to always check the latest messages, and in that condition it could be useful the aggressive doze.
i even noticed that to disable the movement sensors is NOT a great thing...... of course great if someone is in car or moving everytime but it has the CON of turning on/off the brightness sensor of the phone and at every display power on the phone lags for 1/2 seconds.
i must admit that in the last years i've always used aggressivedoze/ or naptime and greenified lots of apps but i should reconsider the fact to UNinstall all....... and see if the battery life is really worse or not.
realista87 said:
yes, i think about a person who does pick up the phone just every 4...5 hour at day because it is not important (for him) to always check the latest messages, and in that condition it could be useful the aggressive doze.
i even noticed that to disable the movement sensors is NOT a great thing...... of course great if someone is in car or moving everytime but it has the CON of turning on/off the brightness sensor of the phone and at every display power on the phone lags for 1/2 seconds.
i must admit that in the last years i've always used aggressivedoze/ or naptime and greenified lots of apps but i should reconsider the fact to UNinstall all....... and see if the battery life is really worse or not.
Click to expand...
Click to collapse
The sensor issue is device specific. I enable 'doze on the go' on all my devices and have yet to encounter the brightness glitch. However, I don't use the more aggressive sensor suppressions available in some apps. Note 'doze on the go' is enabled by default w/Android 7+.
After experimenting with countless apps/tools/techniques (ugh) my Android power management methodology has evolved to a 'lite touch' minimalist approach. I only take overt action when a specific drain can not be contained by other means. Greenify is the tool of choice with only a few bad actors in the explicit hibernation list. Android defaults handle everything else. My devices sleep soundly, behave predictably and score admirably low drain rates. App selection obviously plays into that. Big pigs like Facebook, Google everything and WhatsApp are not part of my portfolio as lighter alternatives exist. Good luck with your own adventures.
I'm new to greenify, so bear with me.
In the pro version, I enabled both shallow hibernation and aggressive doze, in addition to adding a number of apps manually.
However, I found that the proximity sensor became a bit wonky, waking the screen while still in a call, and occasionally failing to wake the screen on call end.
Is it possible that greenify is causing this, and if so, what would you suggest I change to fix it?
HTC 10 rooted, Xposed, Maximus HD (MM)
Sent from my HTC 10 using Tapatalk
BillTheCat said:
I'm new to greenify, so bear with me.
In the pro version, I enabled both shallow hibernation and aggressive doze, in addition to adding a number of apps manually.
However, I found that the proximity sensor became a bit wonky, waking the screen while still in a call, and occasionally failing to wake the screen on call end.
Is it possible that greenify is causing this, and if so, what would you suggest I change to fix it?
HTC 10 rooted, Xposed, Maximus HD (MM)
Click to expand...
Click to collapse
Absolutely! Disable aggressive doze and shallow hibernation as they generally offer no significant benefit on Android 6 (Marshmallow) and often trigger side effects similar to what you describe. I'd also remove ALL apps from Greenify's hibernation list unless they exhibit undesirable behavior.
Given MM based ROM be sure to enable 'Doze on the Go' in Greenify settings which will help your device enter doze more rapidly and remain there longer even when in motion.
Davey126 said:
Absolutely! Disable aggressive doze and shallow hibernation as they generally offer no significant benefit on Android 6 (Marshmallow) and often trigger side effects similar to what you describe. I'd also remove ALL apps from Greenify's hibernation list unless they exhibit undesirable behavior.
Given MM based ROM be sure to enable 'Doze on the Go' in Greenify settings which will help your device enter doze more rapidly and remain there longer even when in motion.
Click to expand...
Click to collapse
Done. Would you suggest a battery app to monitor wake locks, and if so, which one?
Also, a general question about lithium batteries should not be trickle-charged overnight, or left plugged in constantly because it stresses the battery. Just wondering if there's any truth to that, or if it's an urban legend.
Sent from my HTC 10 using Tapatalk
BillTheCat said:
Done. Would you suggest a battery app to monitor wake locks, and if so, which one?
Also, a general question about lithium batteries should not be trickle-charged overnight, or left plugged in constantly because it stresses the battery. Just wondering if there's any truth to that, or if it's an urban legend.
Click to expand...
Click to collapse
Not a fan of monitoring wakelocks which are broadly misunderstood and usually not the source of excess (operative word) battery drain. Android's native monitoring tools are generally adequate. Two well regarded alternatives are Better Battery Stats (BBS) and GSAM. Both can be found in the Play Store.
Leaving a Li-ion powered device on charge overnight is fine. Especially phones and other portable gizmos which are usually discharged the following day. However, Li-ion batteries should not be left in a fully charged or discharged state for an extended period as irrevocable damage can occur. That's why most Li-ion powered devices arrive partially charged which is the state they like best.
More detail: http://batteryuniversity.com
Davey126 said:
Not a fan of monitoring wakelocks which are broadly misunderstood and usually not the source of excess (operative word) battery drain. Android's native monitoring tools are generally adequate. Two well regarded alternatives are Better Battery Stats (BBS) and GSAM. Both can be found in the Play Store.
Leaving a Li-ion powered device on charge overnight is fine. Especially phones and other portable gizmos which are usually discharged the following day. However, Li-ion batteries should not be left in a fully charged or discharged state for an extended period as irrevocable damage can occur. That's why most Li-ion powered devices arrive partially charged which is the state they like best.
More detail: http://batteryuniversity.com
Click to expand...
Click to collapse
Thanks for that info. Very interesting site, but way above my pay grade. I guess by "extended period" that scenario would be a store demo unit that's constantly powered, or a home scenario of similar sort.
Here's what I took away from a brief overview, if anyone else is looking on:
(Sourced from 'How to Prolong Lithium Based Batteries' from Battery University)
From: Battery University:(emphasis mine)
Similar to a mechanical device that wears out faster with heavy use, the depth of discharge (DoD) determines the cycle count of the battery. The smaller the discharge (low DoD), the longer the battery will last. If at all possible, avoid full discharges and charge the battery more often between uses. Partial discharge on Li-ion is fine. There is no memory and the battery does not need periodic full discharge cycles to prolong life.
Environmental conditions, not cycling alone, govern the longevity of lithium-ion batteries. The worst situation is keeping a fully charged battery at elevated temperatures. [I'm reading this as a warning for those of us with quick charging cables]
The question is asked, “Should I disconnect my laptop from the power grid when not in use?” Under normal circumstances this should not be necessary because charging stops when the Li-ion battery is full. A topping charge is only applied when the battery voltage drops to a certain level. Most users do not remove the AC power, and this practice is safe.
Click to expand...
Click to collapse
Davey126 said:
Absolutely! Disable aggressive doze and shallow hibernation as they generally offer no significant benefit on Android 6 (Marshmallow) and often trigger side effects similar to what you describe. I'd also remove ALL apps from Greenify's hibernation list unless they exhibit undesirable behavior.
Given MM based ROM be sure to enable 'Doze on the Go' in Greenify settings which will help your device enter doze more rapidly and remain there longer even when in motion.
Click to expand...
Click to collapse
Still having some trouble from time to time with proximity sensor, screen wake (almost locks on or off) and fingerprint sensor when waking.
I wiped both dalvik/art and system cache which seemed to help for a bit and also seemed to make the phone a bit more responsive, but this afternoon, the above problems resurfaced.
Can you please recommend some settings to start with, since I'm a noob with greenify, and I'm not sure if I have everything set right. Also might app updates without a reboot have something to do with this?
HTC10
Maximus HD (MM)
Rooted (obviously)
Xposed
Thanks in advance!
Sent from my HTC 10 using Tapatalk
BillTheCat said:
Still having some trouble from time to time with proximity sensor, screen wake (almost locks on or off) and fingerprint sensor when waking.
I wiped both dalvik/art and system cache which seemed to help for a bit and also seemed to make the phone a bit more responsive, but this afternoon, the above problems resurfaced.
Can you please recommend some settings to start with, since I'm a noob with greenify, and I'm not sure if I have everything set right. Also might app updates without a reboot have something to do with this?
HTC10
Maximus HD (MM)
Rooted (obviously)
Xposed
Click to expand...
Click to collapse
With Aggressive and Shallow doze disabled the only other setting that might prove troublesome is 'doze on the go'. However, that one is important on MM as it prevents your device from waking and/or staying awake when in motion. Still, might be worth disabling to see if it makes a difference.
Rebooting after app updates is generally unnecessary unless recommended by the developer.
Additional thoughts:
- verify working mode is Root + Boost (Xposed)
- keep the list of apps to explicitly Greenify short (demonstrated bad actors); implicit doze will take care of the rest
While my preference leans towards Greenify (ease of use; flexibility; long term track record; community support) there are several other fine apps with similar functionality. Force Doze pops to the top of the list. Occationally a user will report issues with one while the other works fine. Another option to consider.
BillTheCat said:
Still having some trouble from time to time with proximity sensor, screen wake (almost locks on or off) and fingerprint sensor when waking.
I wiped both dalvik/art and system cache which seemed to help for a bit and also seemed to make the phone a bit more responsive, but this afternoon, the above problems resurfaced.
Can you please recommend some settings to start with, since I'm a noob with greenify, and I'm not sure if I have everything set right. Also might app updates without a reboot have something to do with this?
HTC10
Maximus HD (MM)
Rooted (obviously)
Xposed
Thanks in advance!
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
If you have greenified any system apps, please reconsider. One of them may be the culprit.
If nothing else works, ungreenify everything and start from scratch. Greenify one app at a time, observing the behavior for some time before greenifying the next. You may find the culprit. Laborious, but effective.
Davey126 said:
With Aggressive and Shallow doze disabled the only other setting that might prove troublesome is 'doze on the go'...
Click to expand...
Click to collapse
tnsmani said:
If you have greenified any system apps, please reconsider. One of them may be the culprit...
Click to expand...
Click to collapse
Hey, guys. I'm still having trouble with both the proximity sensor and fingerprint sensor. Could really use some expert advice here.
The phone screen often does not come back on - especially during a long call or when switching between calls, and frequently just "loses its mind" and I have to press the power button to get the screen back, or even to turn the phone off. Another problem is waking via the fingerprint sensor which is unreliable.
I don't know if it's the settings I've selected (my money is on this one) or if there's a rogue app that's hosing me. For example, I use OneBox for my business IP Telephony. Could it be that?
I did, in fact, manually select a couple system apps to greenify, but that's because the ROM developer put them into the system space, rather than the user space. So I'm not sure if that counts.
Here's what I have so far...
Greenified:
ES File Exlorer Pro
Facebook
Firefox
Instagram
Key Ring
SensorPush
Settings:
Working Mode: Root+Boost
Shallow Hibernation DISABLED
Aggressive Doze DISABLED
Wake-up Tracking and Cutoff DISABLED
Automated Hibernation: SELECTED
Xposed based features:
Doze on the go: SELECTED
Wakeup Timer Coalescing SELECTED
Telephone Wakeup SELECTED
Greenifying System Apps: SELECTED
BillTheCat said:
Hey, guys. I'm still having trouble with both the proximity sensor and fingerprint sensor. Could really use some expert advice here.
The phone screen often does not come back on - especially during a long call or when switching between calls, and frequently just "loses its mind" and I have to press the power button to get the screen back, or even to turn the phone off. Another problem is waking via the fingerprint sensor which is unreliable.
I don't know if it's the settings I've selected (my money is on this one) or if there's a rogue app that's hosing me. For example, I use OneBox for my business IP Telephony. Could it be that?
I did, in fact, manually select a couple system apps to greenify, but that's because the ROM developer put them into the system space, rather than the user space. So I'm not sure if that counts.
Here's what I have so far...
Greenified:
ES File Exlorer Pro
Facebook
Firefox
Instagram
Key Ring
SensorPush
Settings:
Working Mode: Root+Boost
Shallow Hibernation DISABLED
Aggressive Doze DISABLED
Wake-up Tracking and Cutoff DISABLED
Automated Hibernation: SELECTED
Xposed based features:
Doze on the go: SELECTED
Wakeup Timer Coalescing SELECTED
Telephone Wakeup SELECTED
Greenifying System Apps: SELECTED
Click to expand...
Click to collapse
Did you try the earlier suggestion of removing everything from hibernation and then hibernating one app at a time? If not, try that.
What is SensorPush? Is that the wireless thermometer thingy? Disable that and see.
tnsmani said:
Did you try the earlier suggestion of removing everything from hibernation and then hibernating one app at a time? If not, try that.
What is SensorPush? Is that the wireless thermometer thingy? Disable that and see.
Click to expand...
Click to collapse
Actually, I figured I'd start from scratch. Disabled the app in Xposed, used TiBu to wipe data and uninstall. I'm going to wipe all the caches and reboot to see what happens.
What I could use some help with is to understand what settings in the app you guys would recommend for my phone /rom:
HTC10
Maximus HD (Marshmallow)
Xposed
Once I'm OK with basic settings, I'll follow your suggestion of one app at a tim.
Yes, Sensor Push is the app for remote temperature / humidity sensors. But it's not this app, I've only had it installed for a couple days, the problem has persisted for weeks beforehand.
Sent from my HTC 10 using Tapatalk
BillTheCat said:
Actually, I figured I'd start from scratch. Disabled the app in Xposed, used TiBu to wipe data and uninstall. I'm going to wipe all the caches and reboot to see what happens.
What I could use some help with is to understand what settings in the app you guys would recommend for my phone /rom:
HTC10
Maximus HD (Marshmallow)
Xposed
Once I'm OK with basic settings, I'll follow your suggestion of one app at a tim.
Yes, Sensor Push is the app for remote temperature / humidity sensors. But it's not this app, I've only had it installed for a couple days, the problem has persisted for weeks beforehand.
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
No appwise recommendations can be made since the device, ROM, kernel, apps etc vary vastly not to speak of the the specific usage pattern of the individual.
What is recommended though is to greenify those apps which you don't use often but which keep running. Do not greenify apps which you often use.
As for system apps, be careful, but the same principle applies. Don't greenify something like PlayServices because its running is essential and it will continuously try to wake up draining battery.
Install BBS and monitor which apps drain battery and then greenify only those which drain but will not cause issues if greenified. Always greenify one app at a time to see the effects.
In general, greenify as less apps as possible.
I have a Moto G4 Play model number XT1600 (Moto G Paly in the US) and I am having some issues with the proximity sensor.
When answering a call, sometimes the screen goes dark and unresponsive to touch or by quickly pressing the power button. I have Greenify installed but I'm not sure if it is related.
After reading some posts here, I decided to understand the behavior of my phone when I make the calls and here is what I learned:
- after the proximity sensor turn the screen off when the phone is close to the ear, many times it will not detect when the phone is put away from the ear. But if you make a movement that leaves the phone in the horizontal position in your hand, the screen will be lit again (it takes a few seconds).
- if you put away the phone from the ear and leave it in a desk in the horizontal position, the screen will almost immediately be lit again. It seems that the proximity sensor works together with another sensor that detects the little bump when you put the phone on the desk.
- I did the movement to put the phone away from the ear, leaving it in the horizontal position in my hand; screen continued dark. Then with my finger I did a few taps in the back of the phone and the screen went on again.
- Another test I did when none of the above alternatives worked: in the settings there is an option to turn the camera on with a double press of the power button. When this option is set and the screen goes unresponsive while answering a call, I do the double click to activate the camera. The screen turns on with the camera app and then I am able to switch to the phone app.
Annoying but it is an alternative solution.
Not sure if this is the normal behavior but this is what I learned today
hjbuzzi said:
I have a Moto G4 Play model number XT1600 (Moto G Paly in the US) and I am having some issues with the proximity sensor.
When answering a call, sometimes the screen goes dark and unresponsive to touch or by quickly pressing the power button. I have Greenify installed but I'm not sure if it is related.
After reading some posts here, I decided to understand the behavior of my phone when I make the calls and here is what I learned:
- after the proximity sensor turn the screen off when the phone is close to the ear, many times it will not detect when the phone is put away from the ear. But if you make a movement that leaves the phone in the horizontal position in your hand, the screen will be lit again (it takes a few seconds).
- if you put away the phone from the ear and leave it in a desk in the horizontal position, the screen will almost immediately be lit again. It seems that the proximity sensor works together with another sensor that detects the little bump when you put the phone on the desk.
- I did the movement to put the phone away from the ear, leaving it in the horizontal position in my hand; screen continued dark. Then with my finger I did a few taps in the back of the phone and the screen went on again.
- Another test I did when none of the above alternatives worked: in the settings there is an option to turn the camera on with a double press of the power button. When this option is set and the screen goes unresponsive while answering a call, I do the double click to activate the camera. The screen turns on with the camera app and then I am able to switch to the phone app.
Annoying but it is an alternative solution.
Not sure if this is the normal behavior but this is what I learned today
Click to expand...
Click to collapse
I experienced this same issue on an older XT1030 which is the mini varient of a 2nd gen Moto X. Spent quite a bit of time trying to diagnose the issue (like you) and had devised various work-arounds that were never quite satiafsctory. Also rocking Greenify w/Xposed but ultimately determined that was not a direct factor with the proximity sensor glitch.
What fixed it (for me) was Gravity Screen which you can find in the Play Store. Takes a bit to get understand how to configure but very nice once everything is set up. One downside is you will probably want to disable Moto's active screen function - at least during initial configuration. Good luck.
Is there any reason why pending updates might have an effect on the proximity sensor?
Sent from my HTC 10 using Tapatalk
BillTheCat said:
Is there any reason why pending updates might have an effect on the proximity sensor?
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
I have noticed that if app updates are kept pending in PlayStore, it does affect various things, which seem totally unconnected.
tnsmani said:
I have noticed that if app updates are kept pending in PlayStore, it does affect various things, which seem totally unconnected.
Click to expand...
Click to collapse
Ah. So I'm not hallucinating after all...
Sent from my HTC 10 using Tapatalk
Well guys, it looks like I'm going to have to abandon Greenify. I just can't seem to find any combination of settings that won't interfere with the proximity sensor. Unfortunate, really, because it's a great app and I even bought the donation package, but it's just making my life miserable.
Anyway suggests for alternatives would be appreciated. I have one mention for 'force doze'. Anything else?
Sent from my HTC 10 using Tapatalk
I wish I had more technical skills to understand why my Moto G4 Play (XT1600) had its proximity sensor behaving erratically for several days. I uninstalled Greenify and installed it again. Settings are
Working mode NON ROOT, Agressive doze ON, Wake-up Tracking DISABLED, Auto Hibernation OFF, Alternative Screen Off Mode OFF, Quick Action Notification OFF, Long Press OFF, Don't Remove Notifications ON, Xposed Features (not available), Greenifying System Apps OFF, Extras for Geek OFF.
My proximity sensor is working fine with Greenify installed.
I keep all my apps and system up to date and I suspect that some recent update may have fixed the erratic behavior of the proximity sensor.
hjbuzzi said:
I wish I had more technical skills to understand why my Moto G4 Play (XT1600) had its proximity sensor behaving erratically for several days. I uninstalled Greenify and installed it again. Settings are
Working mode NON ROOT, Agressive doze ON, Wake-up Tracking DISABLED, Auto Hibernation OFF, Alternative Screen Off Mode OFF, Quick Action Notification OFF, Long Press OFF, Don't Remove Notifications ON, Xposed Features (not available), Greenifying System Apps OFF, Extras for Geek OFF.
My proximity sensor is working fine with Greenify installed.
I keep all my apps and system up to date and I suspect that some recent update may have fixed the erratic behavior of the proximity sensor.
Click to expand...
Click to collapse
Aggressive doze is neither needed nor beneficial on most configs. However, it can result in erratic app/device behavior. Suggest disabling and observe drain over several charge/discharge cycles. If only looking at at sleep performance be sure to include 1-2 min after waking as the device plays 'catch-up'. If there are no overall benefits to aggressive doze why introduce the potential for side-effects?