Related
If I've understood correctly there's no need to hibernate anything in order to user aggressive doze. So I don't use hibernation at all, but instead would like to user aggressive doze.
I'm rooted and have checked the on-the-go mode. I have also enabled the notification.
But there's no doze notification after the screen has been off for few minutes. How do I know if it is dozing or not?
thanks
tofu said:
If I've understood correctly there's no need to hibernate anything in order to user aggressive doze. So I don't use hibernation at all, but instead would like to user aggressive doze.
I'm rooted and have checked the on-the-go mode. I have also enabled the notification.
But there's no doze notification after the screen has been off for few minutes. How do I know if it is dozing or not?
thanks
Click to expand...
Click to collapse
I use Automagic (same idea as Tasker, but I find it much easier to understand and use). It has a trigger for when the phone enters doze mode (and another for when it exits). I can use these triggers to perform conditional actions like enable/disable Bluetooth/WiFi etc., or, say, make a sound, send a message to my Pebble watch, etc. In my case (unrooted phone) I have it make sounds. Using Automagic to do this kind of stuff does not seem to mess up the phone going into/coming out of doze mode.
You can also enable a Greenify notification that shows when the phone goes in/out of aggressive doze...
WibblyW said:
I use Automagic (same idea as Tasker, but I find it much easier to understand and use). It has a trigger for when the phone enters doze mode (and another for when it exits). I can use these triggers to perform conditional actions like enable/disable Bluetooth/WiFi etc., or, say, make a sound, send a message to my Pebble watch, etc. In my case (unrooted phone) I have it make sounds. Using Automagic to do this kind of stuff does not seem to mess up the phone going into/coming out of doze mode.
You can also enable a Greenify notification that shows when the phone goes in/out of aggressive doze...
Click to expand...
Click to collapse
Thanks. It seems that it works now. I just needed to wait for a longer time.
Just remember that doze is not a full replacement for hybernation. It may prevent wakelocks but bad apps can still run background processes loading CPU and consuming battery when phone periodically wakes up from doze as well as every time you are using your phone.
Sent from my OnePlus 2 using Tapatalk
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 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?
I'm used to having my Android phones use apps like KinScreen or Gravity Screen to keep my screen on by motion. On my new Mate 10 (ALP-L29 8.0.0.119 (C636) I'm finding that no matter what I do, the phone's setting for display on time always control, even though I've excepted out both apps from battery optimization and from automatic control of their launch (manually set to run in the background). Anyone experience the same issue or have any thoughts? I don't know if this is an Oreo problem or a Miui one. Thx.
I am having the same issues, no matter what, with persistent notification active, the screen does not stay awake with kinscreen. Installed Wakey, seems to be working at least sometimes... Should be based on your eyes watching the screen...
According to TecTiq, the maker of KinScreen, it's a Miui problem. I'm not the only one to report it. Oh well....
One other possibility is to set your default screen timeout to something long, and then install Proximity Service, which seems to work well on the Mate 10 and turns on and off your screen by covering the proximity sensor. Creates a permanent notification, but installing AutoNotification cures that (as well as the other running notifications, like background Android processes, that you don't want).
EDIT: Nope, belay that! Once the phone sleeps, Proximity Service is still killed (even if excepted from Launch and Battery Optimization). Back to the drawing board....
With my Note 4, it would wake up from Android Doze, or simply not enter that state if there was movement of the phone. I felt stupid needing to pick up my phone every 10 min to give it a small shake, but at least it seemed to work. I keep my phone in my pocket when I'm working outside and that always kept the Note 4 from falling into Doze mode. Not so with the S9+. It drops into Doze even in my pocket. Anyway to stop that from happening? Like others here, I feel frustrated needing to activate my screen to find out if there are notifications.
Brokk said:
With my Note 4, it would wake up from Android Doze, or simply not enter that state if there was movement of the phone. I felt stupid needing to pick up my phone every 10 min to give it a small shake, but at least it seemed to work. I keep my phone in my pocket when I'm working outside and that always kept the Note 4 from falling into Doze mode. Not so with the S9+. It drops into Doze even in my pocket. Anyway to stop that from happening? Like others here, I feel frustrated needing to activate my screen to find out if there are notifications.
Click to expand...
Click to collapse
That's not Doze mode. Doze is when Android puts apps to sleep that are in memory not being used. This is done to save battery (and processing time?).
So what is happening here, if I understand, is that your phone display is going blank when you pull it from your pocket?
Scott said:
That's not Doze mode. Doze is when Android puts apps to sleep that are in memory not being used. This is done to save battery (and processing time?).
Click to expand...
Click to collapse
Doze was originally described as putting your phone into a power saving sleep mode after 20 min of "inactivity". The issue that caused me problems back then was not about the apps, but that notifications pushed to the device were queued up by the system until your phone "woke up", then the notifications would come rolling through. This happened at the system level regardless of app.
Perhaps in the latest version of Android they have changed the definition of Doze, but another poster was having a lot of issues with notifications (mostly email) and the culprit was deemed to be Doze.
Scott said:
So what is happening here, if I understand, is that your phone display is going blank when you pull it from your pocket?
Click to expand...
Click to collapse
No. My display is blank (as it should be) when I put it into my pocket, as well as when I pull it out. I always shut the screen off before putting my phone down, or in my pocket.
If I put my phone in my pocket, and 5-10 min later I get a notification, it comes through loud and clear and I pull my phone out and check it. If 20+ min has gone by without me having a reason to turn the screen on, then I stop getting notifications. When I pull it out to check the time or send a message, suddenly the notifications come rolling through.
Again, I was used to this if the Note 4 was put down, but this behavior is new to me if the phone is moving about.
Brokk said:
Doze was originally described as putting your phone into a power saving sleep mode after 20 min of "inactivity". The issue that caused me problems back then was not about the apps, but that notifications pushed to the device were queued up by the system until your phone "woke up", then the notifications would come rolling through. This happened at the system level regardless of app.
Perhaps in the latest version of Android they have changed the definition of Doze, but another poster was having a lot of issues with notifications (mostly email) and the culprit was deemed to be Doze.
No. My display is blank (as it should be) when I put it into my pocket, as well as when I pull it out. I always shut the screen off before putting my phone down, or in my pocket.
If I put my phone in my pocket, and 5-10 min later I get a notification, it comes through loud and clear and I pull my phone out and check it. If 20+ min has gone by without me having a reason to turn the screen on, then I stop getting notifications. When I pull it out to check the time or send a message, suddenly the notifications come rolling through.
Again, I was used to this if the Note 4 was put down, but this behavior is new to me if the phone is moving about.
Click to expand...
Click to collapse
I concur. Same happens to me.
I don't have this issue at all. I have my phone in my pocket most of the day and don't need to "wake" the phone up for notifications. I can leave my phone unattended for hour or 3 and it still receives the notifications without issues. I don't know if I have turned on a setting that mine works different, but I must say that my battery life isn't that great....as if the phone never sleeps/doze at all
termdj said:
I don't have this issue at all. I have my phone in my pocket most of the day and don't need to "wake" the phone up for notifications. I can leave my phone unattended for hour or 3 and it still receives the notifications without issues. I don't know if I have turned on a setting that mine works different, but I must say that my battery life isn't that great....as if the phone never sleeps/doze at all
Click to expand...
Click to collapse
I'm curious. Do you have any of the power saving modes turned on? Do you use "always on display"?
I never use the power save modes. Aod is on from 5 in the morning till 8 at night
termdj said:
I never use the power save modes. Aod is on from 5 in the morning till 8 at night
Click to expand...
Click to collapse
AoD could be keeping your phone awake, preventing Doze. The power saving features talks about putting apps to sleep, so unless you use them, that could also be disabling Doze. I could try changing the power saving settings, though it seems like a shame. I have zero interesting in AoD for multiple reasons, so it's not worth it for me to use that to solve my problems.
Thanks for the information!
Doze changed in Nougat, I believe, so that motion no longer prevented Doze from working. Since most men, at least, carry their phone in their pocket Doze hardly ever kicked in, greatly limiting its power saving capability.
You can exempt specific apps from Doze if you want to get notifications from them even when dozing.
Settings / Apps / 3 dot menu / special access / Optimize battery usage. Select All Apps from the drop down. Turn off the toggle for any apps you don't want to Doze.
Brokk said:
Doze was originally described as putting your phone into a power saving sleep mode after 20 min of "inactivity". The issue that caused me problems back then was not about the apps, but that notifications pushed to the device were queued up by the system until your phone "woke up", then the notifications would come rolling through. This happened at the system level regardless of app.
Perhaps in the latest version of Android they have changed the definition of Doze, but another poster was having a lot of issues with notifications (mostly email) and the culprit was deemed to be Doze.
No. My display is blank (as it should be) when I put it into my pocket, as well as when I pull it out. I always shut the screen off before putting my phone down, or in my pocket.
If I put my phone in my pocket, and 5-10 min later I get a notification, it comes through loud and clear and I pull my phone out and check it. If 20+ min has gone by without me having a reason to turn the screen on, then I stop getting notifications. When I pull it out to check the time or send a message, suddenly the notifications come rolling through.
Again, I was used to this if the Note 4 was put down, but this behavior is new to me if the phone is moving about.
Click to expand...
Click to collapse
Yes, I am confusing Doze with the Samsung power saving options. Blah!
I know the battery life will decrease with aod, but I have noticed that even without aod on my battery drop 2% per hour, so I leave it on...There are days that I can go 1 day and 8 hours before charging, but then my sot is only 2 hours....In general I'm happy with the battery life
meyerweb said:
You can exempt specific apps from Doze if you want to get notifications from them even when dozing.
Settings / Apps / 3 dot menu / special access / Optimize battery usage. Select All Apps from the drop down. Turn off the toggle for any apps you don't want to Doze.
Click to expand...
Click to collapse
Thanks!
It seems oddly redundant needing to do essentially the same thing in two places. One well advertised under the battery settings, and the other one hidden under settings/apps/special access.
Hopefully this will fix my problems. Glad to know there is a work around.
Brokk said:
Thanks!
It seems oddly redundant needing to do essentially the same thing in two places. One well advertised under the battery settings, and the other one hidden under settings/apps/special access.
Hopefully this will fix my problems. Glad to know there is a work around.
Click to expand...
Click to collapse
The two settings really are doing different things. Samsung's (in the battery settings), puts apps to sleep after 3 to 7 days (depending on your settings). The won't wake up again until you use them. Doze (the pretty much hidden option in Apps), lets the apps wake up on their own, when you start using the phone, even if you don't access those particular apps.
I'm not sure why the Doze setup is buried so deep in settings, though. I guess Google (or Samsung?) really doesn't want you interfering with it.
meyerweb said:
The two settings really are doing different things. Samsung's (in the battery settings), puts apps to sleep after 3 to 7 days (depending on your settings). The won't wake up again until you use them.
Click to expand...
Click to collapse
I made a mistake of putting an app to sleep that I use to keep my screen awake. It uses a widget to toggle it on/off, but will shut off along with the screen if you intentionally shut your screen off. After putting that app to sleep, the widget stopped working. I had to go find the actual app, start it, then quickly flip back to my home screen and click on the widget. I couldn't undo my "sleep" action on that app. I changed it to "unmonitored", so that the S9+ would never put it to sleep. I rebooted. I shut off the power saving options. Nothing worked. Everytime I would go to the widget (unless I just started the actual app), it wouldn't react to clicking on the widget.
I finally gave up and uninstalled the app from my phone. Rebooted. Reinstalled it and now it works fine. So I'm not sure I agree with "puts the app to sleep in 3 to 7 days". Maybe 3-7 minutes...
Well, 3 to 7 days is what Samsung says, and the optional range you can set in the app. Don't know what specifically happened with that widget, though.
meyerweb said:
Well, 3 to 7 days is what Samsung says, and the optional range you can set in the app. Don't know what specifically happened with that widget, though.
Click to expand...
Click to collapse
Where is the setting(s) for optimal range? I don't remember specifying that. I thought it was more of an on/off thing. White listed (unmonitored resource consumption) or black listed (never let it run in the background). Then apps in neither list it reports to you and you can force them to sleep or not.
Brokk said:
Where is the setting(s) for optimal range? I don't remember specifying that. I thought it was more of an on/off thing. White listed (unmonitored resource consumption) or black listed (never let it run in the background). Then apps in neither list it reports to you and you can force them to sleep or not.
Click to expand...
Click to collapse
Samsung does bury things....
Settings / Device maintenance, click Battery at the bottom.
Then click the 3 dot menu at the top, and Advanced Settings.
Tap App power monitor (the text, not the toggle).
Tap Put unused apps to sleep (again, the text).
You can set the slider anywhere between 3 days and 7.
I spent several days just wandering through every settings option I could find after I setup the phone. Discovered all kinds of hidden things. Sometimes I can even remember where I saw them.