Nexus 6 and Moto X (2014), rooted, no Xposed. Both on Android 6.0. Full version of Greenify set to automatically hibernate select apps (Facebook and Amazon being the top offenders). Symptoms:
- When the device is charged, the screen would turn on intermittently every 1-3 minutes.
I was going crazy, trying to identify what app is responsible for this. Reboot in safe mode, charging quietly. Then I started disabling root apps one after another. This behavior stopped when I disabled Greenify.
Then I was trying which setting in Greenify was responsible for this behavior. I discovered that when Automatic Hibernation was off in Greenify (with other features such as Aggressive Doze still active), the phone would not wake while being charged. Then I watched closely what happens when Greenify hibernates apps, and discovered that it displays a toast message - which, in both Nexus 6 and Moto X, is enough to wake the display. After that, the apps would probably wake up, and Greenify will attempt to greenify them again on next cycle. This goes on and on without an end.
Two issues here.
1. Greenify should NOT attempt to hibernate apps while charging - and yet, it does.
2. At least there should be an option for Greenify to NOT display a toast message, in which case the phone will not be awake.
3. Final observation. This behavior does NOT occur on other phones (and tablets!) in my possession. Most probably it's a Moto thing that has something to do with Ambient Display.
Suggested fix:
1. Either remove toast notifications or add an option to disable them.
2. Only greenify apps after some time the phone is NOT on a charger (that is, treat "charger connected" the same way as you treat "display on", resetting the countdown timer before hibernation should occur).
aoleg said:
Nexus 6 and Moto X (2014), rooted, no Xposed. Both on Android 6.0. Full version of Greenify set to automatically hibernate select apps (Facebook and Amazon being the top offenders). Symptoms:
- When the device is charged, the screen would turn on intermittently every 1-3 minutes.
I was going crazy, trying to identify what app is responsible for this. Reboot in safe mode, charging quietly. Then I started disabling root apps one after another. This behavior stopped when I disabled Greenify.
Then I was trying which setting in Greenify was responsible for this behavior. I discovered that when Automatic Hibernation was off in Greenify (with other features such as Aggressive Doze still active), the phone would not wake while being charged. Then I watched closely what happens when Greenify hibernates apps, and discovered that it displays a toast message - which, in both Nexus 6 and Moto X, is enough to wake the display. After that, the apps would probably wake up, and Greenify will attempt to greenify them again on next cycle. This goes on and on without an end.
Two issues here.
1. Greenify should NOT attempt to hibernate apps while charging - and yet, it does.
2. At least there should be an option for Greenify to NOT display a toast message, in which case the phone will not be awake.
3. Final observation. This behavior does NOT occur on other phones (and tablets!) in my possession. Most probably it's a Moto thing that has something to do with Ambient Display.
Suggested fix:
1. Either remove toast notifications or add an option to disable them.
2. Only greenify apps after some time the phone is NOT on a charger (that is, treat "charger connected" the same way as you treat "display on", resetting the countdown timer before hibernation should occur).
Click to expand...
Click to collapse
On my phone Greenify does not attempt hibernation while charging. In fact if I open Greenify while charging, I get the whole list of all the apps chosen by me for hibernation with a text on top saying something like hibernation will take place after the charging is over.
It may have something to do with the way these Moto phones charge. They may, from time to time, report that the charger has been disconnected (while in fact continuing charging). This by itself does not turn on the screen; Greenify does.
aoleg said:
It may have something to do with the way these Moto phones charge. They may, from time to time, report that the charger has been disconnected (while in fact continuing charging). This by itself does not turn on the screen; Greenify does.
Click to expand...
Click to collapse
As a data point my 2013 Moto X does not exhibit this behavior. v2.7.1, rooted, Xposed, boost mode. Only time I have observed a non-interactive toast is in non-root mode; the screen wakes momentarily when apps are hibernated. You can squelch this behavior by disabling Greenify permissions under Accessibility (not needed in root or boost modes).
This was happening for me as well, Nexus 6P on Android 6.0, Greenify 2.8 beta 3. Not only did it wake up the screen during the charge, but it actually stopped the phone from charging and the toast message seemed to include every single app I had Greenified. It was present in both boost and root modes and was the main reason I uninstalled the app.
Symthic said:
This was happening for me as well, Nexus 6P on Android 6.0, Greenify 2.8 beta 3. Not only did it wake up the screen during the charge, but it actually stopped the phone from charging and the toast message seemed to include every single app I had Greenified. It was present in both boost and root modes and was the main reason I uninstalled the app.
Click to expand...
Click to collapse
Same behavior on my 6P on 6.0.1. with the same Greenify version. I disabled automatic hibernate and now the screen stays off during charging.
I get the same with my xperia Z3c running concept rom, except I don't get a toast messsage. I thought I was going crazy when I first noticed this strange behaviour. Found this thread from a Google search by the way.
Which version of Greenify do you noticed this behavior in? It is supposed to be fixed in the recent beta version.
oasisfeng said:
Which version of Greenify do you noticed this behavior in? It is supposed to be fixed in the recent beta version.
Click to expand...
Click to collapse
version 2.8 beta 3 with paid unlocker through play store and xposed. My bad, realised I'm a few beta releases behind. Updated to latest and all is well so far.
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'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?
I have installed several apps that need Accessibility set to On in order for them to keep working. 3 of those keep getting disabled by I guess the system and I have to go in and toggle that permission switch to Off and then back On again. It happens randomly, sometimes after a few days and sometimes after a few hours but when it happens it alway affects those 3 apps together.
The 3 apps are Super Status Bar, Power Shade Premium and Energy Ring. Others like Button Mapper or Nova (for doubletap to sleep) are unaffected.
Those apps are excluded from battery optimization, I'm not rooted (yet) and I don't have any "app killer" running. Googling was no help so I'm hoping someone here has an idea. I'm guessing A12 is doing something shady here, but how do I stop it from happening?
Nimueh said:
I have installed several apps that need Accessibility set to On in order for them to keep working. 3 of those keep getting disabled by I guess the system and I have to go in and toggle that permission switch to Off and then back On again. It happens randomly, sometimes after a few days and sometimes after a few hours but when it happens it alway affects those 3 apps together.
The 3 apps are Super Status Bar, Power Shade Premium and Energy Ring. Others like Button Mapper or Nova (for doubletap to sleep) are unaffected.
Those apps are excluded from battery optimization, I'm not rooted (yet) and I don't have any "app killer" running. Googling was no help so I'm hoping someone here has an idea. I'm guessing A12 is doing something shady here, but how do I stop it from happening?
Click to expand...
Click to collapse
I'm wondering if you've entered Power Saving Mode before this problem occurs? At least 2 of these apps will be killed when Power Saving Mode is entered and you have to restart your device to get it going again. Maybe it also kills the Accessibility service? Not really sure, just throwing it out there.
Lughnasadh said:
I'm wondering if you've entered Power Saving Mode before this problem occurs? At least 2 of these apps will be killed when Power Saving Mode is entered and you have to restart your device to get it going again. Maybe it also kills the Accessibility service? Not really sure, just throwing it out there.
Click to expand...
Click to collapse
No, Power Saving Mode is disabled and the battery wasn't low enough for it to even have kicked in. When it happened (twice!) yesterday the battery was 40-50% both times. Adaptive battery is disabled too so battery "shouldn't" be causing it in any way.
Thanks for replying though
Just a small update:
Oddly enough since I started this thread it hasn't happened again
I did sideload that mid-month update right around the same time of my post, maybe that fixed it ... no idea really, I'm just glad it's not happening any more