Hi everybody.
I've just installed WIDGET LOCKER and I find it a very cool app.
But I've a problem: I've enabled the EASY WAKE UP mode, but it doesn't work......in fact I've always to use the button on the top of the cell, while the volume buttons or the trackball don't do the same (wake up the screen): why? It's a very helpful feature and I'd like to use it. I've a Htc Wildfire Buzz.
Hope someone can help me.
Thanks in advance.
I seem to have the same problem aswell (just tried it but I dont really like using volume buttons to unlock, although I can and like to use trackball to wake (Menu > Settings > Buttons & Inputs > 'Tick' Trackball Unlock). What version do you have?
seedy97 said:
I seem to have the same problem aswell (just tried it but I dont really like using volume buttons to unlock, although I can and like to use trackball to wake (Menu > Settings > Buttons & Inputs > 'Tick' Trackball Unlock). What version do you have?
Click to expand...
Click to collapse
The trackball works to unlock, but not to wake up the screen.
Anyway it's a problem of our phone, as told me by the developer of the app.
Ciauz.
Perhaps there is not (hardware) support for that. i had the same wish to do the same. there is a cool app called Tap Tap and it's using proximity sensor to on screen and off.
Popples said:
The trackball works to unlock, but not to wake up the screen.
Anyway it's a problem of our phone, as told me by the developer of the app.
Ciauz.
Click to expand...
Click to collapse
This version of Widget works well on Android 2.1 but it can't with android 2.2 or 2.2.1. It used to be very good on my wildfire 2.1 but I have the same problem with my 2.2.1 OTA. I think Widgetlocker still doesn't fully support android 2.2.1
In cyanogenmod 7 the trackball wake function works good. But there is another nice app. It wake and unlock the wildfire by the proximity sensor. Just hold your finger on the right side of the HTC logo to turn off and on the device. I am testing it now and it works very good. The app is called proximity screen off
Sent from my HTC Wildfire using XDA Premium App
Proximity sensor solution with widgetlocker and tasker
CoaBalboa said:
Perhaps there is not (hardware) support for that. i had the same wish to do the same. there is a cool app called Tap Tap and it's using proximity sensor to on screen and off.
Click to expand...
Click to collapse
Ok, I know this was from an old post, but I hadn't seen any mention of this functionality and thought I'd share.
I've found great success in running with widgetlocker completely disabled, then using tasker to lock the screen when power off via power button (but only when not on a phone call to avoid interference from prox sensor screen off in call) and unlocking widgetlocker only when the prox sensor is not engaged, after a 100ms pause.
It saves cpu cycles, as WL is not polling for screen off trigger (tasker is already running after all) and is extremely snappy in unlocking on my Note 2. Its also very good about detecting my pocket, as the prox sensor on the note 2 can be set to poll when the screen is off, something not available on my older phone. I had it pretty dialed in on my previous phone, a 1st generation sgs epic 4g running cm10, despite some sluggishness due to lack of system resources, especially onboard storage space.
Obviously, everyone will have their own take on lockscreens. I'm the type of user who just wants the lockscreen out of my way. Aside from the phantom media widget which appears/disappears when the music starts/stops, I am not much for widgets on my lockscreen. When I first purchased, I really just wanted a method of avoiding having to slide to unlock, as that seems like a wasted gesture. I originally set out to solve the prox sensor unlock solution on android with the old windows mobile app pocketshield in mind as my paragon. If you are like me and just want the lockscreen gone without having to reach for it, but don't want to worry about pocket unlocks, then you'll be happy to hear that this setup with widgetlocker and tasker is an infinitely better and cleaner solution than pocketshield ever was.
Just my 2 cents.
I have a case on my phone that makes using the hardware buttons a real pain. Has anyone found, or does anyone know of any custom kernels or roms released that allow a 'sweep glass to wake' feature? I'm using widgetlocker now which allows a wake by pressing the volume buttons - which are easier than the power key, but if anyone has any suggestions (other than removing the case), I'm all ears.
I'm running the unNamed 2.1.1 rom w/entropy's kernel btw.
Thanks!
Matt
Don't know of any. Don't think anyone would even want one, besides you. I leave my phone in my pocket and it would constantly turn on when walking, if it was just a swype gesture. IMO, it would be a massive pain.
I'm 99% certain there is no way to do this without increasing battery drain significantly. Having the touchscreen controller active while in sleep would increase drain a lot, and also it's about 50% likely the touchscreen controller is not even capable of waking the CPU from deep sleep.
It would require a MASSIVE amount of kernel hacking to make it possible, and the battery drain would be awful.
Check out "Tap Tap App" in the market. I've been using it. It's a little strange as it doesn't always work. It does most of the time. I don't know what it does to the battery. I haven't checked it yet.
You're closest bet would be to find something that allows the capacitive keys to wake the screen (I believe some HTC devices can do that, as can my gTablet).
It might be as simple as editing a keymap file.
Recently, when my phone is exposed to brightness, and the softkey light goes off, the vibrate on the softkeys become very weak. When my phone is in darker places, and the lights go on, the vibrate is solid and good.
I haven't made any changes on my phone that I can think of could cause this. I'm running 2.3.6 rooted. Only changes I've made are some CPU tweaks and overclock.
I found a similar thread about this problem on the Motorola forums, but no good answer. They thought it was a powersaving feature, but this is an issue that only happens for some.
Is there any tweak to always enable the lights when screen is on? That'd be better for me.
Bump!
Am I really alone about this? Id love a tweak that enables the lights all the time.
Thanks in advance
There is an app in Play Store called Lux. I believe it will let you have the buttons lit all the time. I find my Razr Maxx has weak vibration. I don't use the soft key or keyboard vibration but the notifications are weak.
Thanks for your reply. Unfortunately that didn't work, the app didn't have any feature to control the lights of the buttons.
Just to clarify thoygh, I'm talking about the 4 buttons on the bottom of the phone. I'm not sure anymore if these are the soft keys.
Anyone know another workaround? Thanks in advance.
i use screendim and theres an option in there to make the backlights to stay on all the time.
Sent from my DROID RAZR using xda premium
Screendim did the trick for me, however the buttons will now stay lit even when screen is off, which is a battery drainer. I'll just have to live with this, it's not that big of an issue I guess...
Thanks for your replies guys
I am noticing some problems with my s3 after the official jellybean update. It feels like it has been rushed to the phone. For example it doesn't have the quick reply feature in the notification window. It does for missed calls but not for messages. This is one the most anticipated features for me. Also when watching you tube and you don't want the screen to rotate it now does. I want to lock the rotation so I only get the small video at the top when my phone is on its side. It worked before jellybean update. Also auto brightness has changed. When auto brightness is selected you can manually turn it up with the slider in the notification window and it disables auto brightness and changes to what you set on the slider. Now on jellybean you have to uncheck the auto brightness box and then slide. Little features like this are starting to make me feel like it has been a massive rush to get jellybean on to the s3 which is ironic seen as though it took long enough. I have the international i9300 model s3. Is anybody else noticing the problems I have stated? Does anybody know a way of changing/getting the features? Thanks.
They were definitely to busy with the Note II, I mean come on at least give their flag ship the same/some of the features that a bigger version of the S3 has... That sexy multitasking should have been on the initial jelly bean update.
94% to 77 % in 7 hours.
WIFI : On , PSM off
Most power and wakelocks were by Kernal.
Normal?
I'm on LJ4, stock kernel?
I've not got a clue what you're on about?
Sent from my GT-I9300 using xda app-developers app
I know what you mean. The note got great features like the multi window. Apparently that's coming before the new year but I highly doubt that. Are you noticing the same problems I am? Another problem I found is when screen goes off after inactivity you used to be able to press the home button a moment after it goes off and it would turn the screen back on leaving you at the page you was. Now the home button takes you back to the home when you press it. It's annoying you have to go back to the app.
Sent from my GT-I9300 using xda app-developers app
eggman89 said:
94% to 77 % in 7 hours.
WIFI : On , PSM off
Most power and wakelocks were by Kernal.
Normal?
I'm on LJ4, stock kernel?
Click to expand...
Click to collapse
Me too, my problem is the battery with jb lj4
I think there is a few little niggles but overal its pretty much the same.
The autobrightness don't disable automatically now when you adjust the slider as you can now actually adjust the autobrightness brightness, Not sure why though.
Google Now - leaving it active at the mo, but not really found any usefullness from it as yet. The Time home feature is ok, would be good if it actually showed the route I take home - Via motorway, rather than the route through city center which i don't take!!
The new notifcation bar - its ok, nothing major. Expect a bit of all these features will improve over time as well once apps get proper updates. Some work but don't have full functionally - Songpop has no notifications now for example.
Battery Life - I did find that my normal phone use on ISC which included about 50/60 mins worth of calls etc wi-fi left on all the time but only actually connected to wi-fi at home (just 2G & 3G at work) i would have about 55/60% battery life left by the time i got home from work, on Jelly Bean - with the same useage i had about 40/45% left. I am now back to the same as before on ISC, but i didn't disable google now or anything just turned Wi-Fi off when left home and turn it back on when home - results was 55/60% battery remaining a as on ISC. Seems that the Wi-Fi drains when not connected - either it keeps on searching which it might not of done on ISC or its the Google Now doing something (Does say improve location by keeping wifi on - does this even if not connected!!) - Least this way i can still use google now and see how it improves its tags overtime.
I am now using a App called WiFi Timer to automatically switch Wifi on and off when i leave/get home.
Love that it now has voice downloaded so you can text etc with no data connection - find its more accurate now as well!
Never had the small vids on Youtube when rotated phone so not sure about that. Take it disabling autorotate doesn't do this?
Good and Bad
My experience is as follows:
Good:
Sheer speed, no perceivable lag.
A problem I had with only half the SMS notification tone being played (before it cut off) has gone away.
Bad:
Battery drain terrible even when idle. Turning off Google Now, Location Services and Samsung Push Notification fixed this.
When I activate Smart Stay, the screen does not want to turn off 80% of the time - even when I'm not looking at it.
When I wake the phone using the home key, it exits the app I was in. Previously, this would wake the device and return you to the current app (after unlocking). I have a partial work around using the PreHome app; this way the app is still visible underneath the PreHome dialogue box and I just need to press Back to get to my app again.
Widgets, seem to refresh less regularly, particularly Messaging and Gmail widgets which seem to hardly even refresh when I want them too.
Of No Consequence:
The red charging led is a little dimmer when charging.
Overall:
The speed benefits outweigh the niggles - just!
Dan
ohyesman said:
I am now using a App called WiFi Timer to automatically switch Wifi on and off when i leave/get home.
Click to expand...
Click to collapse
No need for an App. You can do it inbuilt.
Go to Wifi, Menu button and Advanced
eggman89 said:
No need for an App. You can do it inbuilt.
Go to Wifi, Menu button and Advanced
Click to expand...
Click to collapse
Yep i know, but this app is far better as it lets you setup different profiles for mornings, evenings & weekends etc which the inbuilt one don't. :good:
root?
i may just root my phone as i really am not happy with this jellybean update, nothing has really improved for me, if i root it and install a rom like codename all the features like quick reply would be there right?
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?