Wondering if theirs a baked kernel that has a raise to wake feature. Installing a 3rd party app might cost wake time. And I love the feature on my iOS10. Doubletap to wake is nice but raise to wake it a bit more convenient during a hang over.
nomadman said:
Wondering if theirs a baked kernel that has a raise to wake feature. Installing a 3rd party app might cost wake time. And I love the feature on my iOS10. Doubletap to wake is nice but raise to wake it a bit more convenient during a hang over.
Click to expand...
Click to collapse
What exactly did raise to wake? Please explain for non apple users [emoji5]
Sent from my Z1 using my hand
He means waking device using motion/proximity sensor..
Like moto display
You pick up the phone, display gets on for 2,3 sec... shows notification and time..
Not sure but maybe it is called ambient display.
Hey Guys. No problem strongst. Not everyone uses an idevice. yea its a upward motion sensor that lights up the screen. Exactly what Vikas mention on his 3rd line post. But I dont think its a proximity sensor or has anything to do with ambient.
Ive tried a few 3rd party apps and they didn't work very well. Also you have to pick it up in a angle, and what's annoying is when the screen is off you carry it and tilt it in an angle the screen lights up. 3rd party apps also have to be always whitelisted in my batt saving settings because it needs to be always active to work. I am getting 3 days on battery and would like to keep it that way
vikas966591 said:
He means waking device using motion/proximity sensor..
Like moto display
You pick up the phone, display gets on for 2,3 sec... shows notification and time..
Not sure but maybe it is called ambient display.
Click to expand...
Click to collapse
I'm sure you can make such things with Tasker,but it's wast of battery in my opinion to much false positives I think.
Sent from my Z1 using my hand
Related
Hi all,
i love the moto display feature but i have some issues that make it less usable for me.
- on certain conditions the moto display seems to react to fast, while on other i had to wave 3-4 times until the screen was woken up. Does anybody know what makes the display not recognize the wave sometimes?
- i hate the fact that the notifications are an all or nothing feature. i might have 10 notifications, and i can only dismiss them all at once. But i want to dismiss onlyspecific ones and keep the rest on my lockscreen. Is this possible somehow?
- as the moto display dismisses all notifications at once, and the regular android lockscreen doesn't, creates situations where there are notifications on the drawer (which need to be dismissed manualls) vs. the Moto screen that doesn't show any notification.
Is there any way to make the dismissing of notifications work as on stock android (possibility to either dismiss all, or only specific ones).
I'm pretty sure its a proximity and light sensor of some sort, but other than that, I'm having the same issues as you.
Sent from my XT1254 using XDA Free mobile app
I believe that only the sensors on the top of the phone fact to the wave. I don't know what the bottom sensors do.
Why is it impossible to find a diagram listing the location and function of all of the sensors?
If you have many notifications and want to do each individually, then instead of using the moto display just hit the power button to go to the normal lockscreen.
pizza_pablo said:
I believe that only the sensors on the top of the phone fact to the wave. I don't know what the bottom sensors do.
Why is it impossible to find a diagram listing the location and function of all of the sensors?
Click to expand...
Click to collapse
Top sensor is for waving (as you said). Bottom sensors are there for when you pick the phone up. If you go to pick the phone up, once your hand covers those two sensors, the display lights up. I found this out somewhere on XDA because I had no idea what they did either lol.
you can disable the sensor, and it will work like the first generation moto x.
Still, the sensor works fine for me, they just takes a little time to turn on after the screen lights on (about 1, 2 seconds) so it's not instant.
chris23445 said:
Top sensor is for waving (as you said). Bottom sensors are there for when you pick the phone up. If you go to pick the phone up, once your hand covers those two sensors, the display lights up. I found this out somewhere on XDA because I had no idea what they did either lol.
Click to expand...
Click to collapse
Thanks!
I checked out the bottom sensors, and it appears that they do respond only to touch, as opposed to waving over. :good:
Had this phone for about 5 days so far, and coming from an old HTC one X I'm amazed by the battery life! And generally really liking the phone, however..........
I cannot seem to find how to mute the phone's alerts by turning the phone over onto it's screen. i.e. in a meeting or restaurant, phone begins to ring... and I can just flip it quickly over to shut it up and know that it won't ring again whilst turned over.
I know I'm probably being stunningly dim, but any hints?
alex.mc said:
Had this phone for about 5 days so far, and coming from an old HTC one X I'm amazed by the battery life! And generally really liking the phone, however..........
I cannot seem to find how to mute the phone's alerts by turning the phone over onto it's screen. i.e. in a meeting or restaurant, phone begins to ring... and I can just flip it quickly over to shut it up and know that it won't ring again whilst turned over.
I know I'm probably being stunningly dim, but any hints?
Click to expand...
Click to collapse
I guess this isn't supported on x play.
alex.mc said:
Had this phone for about 5 days so far, and coming from an old HTC one X I'm amazed by the battery life! And generally really liking the phone, however..........
I cannot seem to find how to mute the phone's alerts by turning the phone over onto it's screen. i.e. in a meeting or restaurant, phone begins to ring... and I can just flip it quickly over to shut it up and know that it won't ring again whilst turned over.
I know I'm probably being stunningly dim, but any hints?
Click to expand...
Click to collapse
That's a handy feature to have... Someone should work on that.
abhish3k9 said:
That's a handy feature to have... Someone should work on that.
Click to expand...
Click to collapse
It's kernel related I think. You can tell the developers about it on kernel related thread.
K.khiladi said:
It's kernel related I think. You can tell the developers about it on kernel related thread.
Click to expand...
Click to collapse
I don't think so. I think, it's just using the proximity sensor to mute the device while receiving a call. An app for non-rooted phones will do. Though, it can be embedded in custom ROMs.
abhish3k9 said:
I don't think so. I think, it's just using the proximity sensor to mute the device while receiving a call. An app for non-rooted phones will do. Though, it can be embedded in custom ROMs.
Click to expand...
Click to collapse
Nope it isn't that easy that just an app would enable it. X play has notification led also but requires custom kernel to support it.
K.khiladi said:
Nope it isn't that easy that just an app would enable it. X play has notification led also but requires custom kernel to support it.
Click to expand...
Click to collapse
I might be wrong, but, enabling the notification LED i.e letting power into it or establishing a connection to it (hardware level) is different than using a (already working) sensor. The feature mentioned in this thread is just a cleaver use of sensors.
abhish3k9 said:
I might be wrong, but, enabling the notification LED i.e letting power into it or establishing a connection to it (hardware level) is different than using a (already working) sensor. The feature mentioned in this thread is just a cleaver use of sensors.
Click to expand...
Click to collapse
The sensors are working correctly but for that particular trick to work there has to be support from software level and that comes from kernel support. I haven't heard of any app that initiates this flip to mute thing. I could also be wrong. I ain't a developer but just reading stuffs everywhere.
You don't need special kernel support for this.
Any app (if you grant the permission) can mute the phone by setting RINGER_MODE_SILENT via Android Audiomanager.
http://developer.android.com/reference/android/media/AudioManager.html
And any app can choose to be notified on sensor data changes of a specific sensor (e.g. proximity semsor) if it registers a listener for this sensor.
http://developer.android.com/reference/android/hardware/SensorManager.html
If you combine both and put it as background service you have an app that mutes the phone based on sensor input. E.g. if proximity sensor if covered. Quite easy.
Though for flip to mute proximity sensor alone probably doesn't help as the sensor is a also covered if the phone is in your pocket. I guess gyroscope would be best, which X Play doesn't have...
But maybe you can detect the flip motion also via clever combination of magnetometer and accelerometer data?
But I would be very surprised if there were no apps in Google Play which offer flip to mute functionality
u42671 said:
You don't need special kernel support for this.
Any app (if you grant the permission) can mute the phone by setting RINGER_MODE_SILENT via Android Audiomanager.
http://developer.android.com/reference/android/media/AudioManager.html
And any app can choose to be notified on sensor data changes of a specific sensor (e.g. proximity semsor) if it registers a listener for this sensor.
http://developer.android.com/reference/android/hardware/SensorManager.html
If you combine both and put it as background service you have an app that mutes the phone based on sensor input. E.g. if proximity sensor if covered. Quite easy.
Though for flip to mute proximity sensor alone probably doesn't help as the sensor is a also covered if the phone is in your pocket. I guess gyroscope would be best, which X Play doesn't have...
But maybe you can detect the flip motion also via clever combination of magnetometer and accelerometer data?
But I would be very surprised if there were no apps in Google Play which offer flip to mute functionality
Click to expand...
Click to collapse
Thanks for correction and I haven't heard of any app with that feature.
I haven't seen a standalone app for this (but then I haven't really looked too hard) but if you have xposed installed you can use GravityBox which has "Flip action while ringing" under the "Phone Tweaks" section. Options are:
Do nothing (default)
Mute ringer
Dismiss call
The flip action is defined as "device is flipped face down while ringing".
Hey, guys. I'm a huge fan of this phone.. I can't get over what a good value it is for the money. I have almost zero issues with it. The one issue I do have is the inconsistency with tap to wake. It seems like after it has been in my pocket for a while, it just fails to work. This happens periodically throughout the day, to the point where I just can't rely on it. It drives me mad because that's kind of a must have feature for me. To be fair, the only device I have never had tap to wake issues with is LG phones. They just seem to work all the time.
I did raise the sensitivity following the guide found on these forums. It's something else, like the pocket protection is stuck on or something. Anyone else experience something similar? I don't want to use the fingerprint reader. Is there something I don't know? Some setting I'm not seeing? Or is this just how it is?
Still a great phone otherwise. I wish I could fix this one little thing.
Is your screen clean or dirty? Have you tried wiping it down with 70% isopropyl alcohol and seeing if that improves the responsiveness. Is the phone hot when it's not responding? Are your fingers dirty?
It's not very sensitive, you definitely need to give it a couple of thumps unlike the taps on an LG phone.
There's a learning curve with this phone. I nearly dislocated my shoulder trying to shake the flashlight awake before I realized you had to wake the screen first
ludovicien said:
It's not very sensitive, you definitely need to give it a couple of thumps unlike the taps on an LG phone.
There's a learning curve with this phone. I nearly dislocated my shoulder trying to shake the flashlight awake before I realized you had to wake the screen first
Click to expand...
Click to collapse
I mean, this only happens when I take it out of my pocket. Tap to wake works fine the rest of the time and my screen is definitely clean.
Sent from my ZTE A2017U using Tapatalk
greyhulk said:
I mean, this only happens when I take it out of my pocket. Tap to wake works fine the rest of the time and my screen is definitely clean.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I'm coming from an lg phone as well, I have found the taps must be slower. The pause between taps needs to be just a little longer and it works for me almost every time.
Double tap to wake doesn't work when the phone has gone into doze mode. ZTE knows about this issue and is working on a fix.
xxBrun0xx said:
Double tap to wake doesn't work when the phone has gone into doze mode. ZTE knows about this issue and is working on a fix.
Click to expand...
Click to collapse
That actually explains a lot. Thanks!
Doze seems to break a lot, including notifications on other phones.
Sent from my ZTE A2017U using Tapatalk
greyhulk said:
That actually explains a lot. Thanks!
Doze seems to break a lot, including notifications on other phones.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
The doze should not kick in if the phone is moving. One of the conditions is that phone should be static for a while. More likely it's something based on proximity sensor to prevent accidental turn ons. I found that i would have to tap several times to wake it up most time i have to do it twice. The force touch is buggy
Sent from my shieldtablet using XDA-Developers mobile app
peramikic said:
The doze should not kick in if the phone is moving. One of the conditions is that phone should be static for a while. More likely it's something based on proximity sensor to prevent accidental turn ons. I found that i would have to tap several times to wake it up most time i have to do it twice. The force touch is buggy
Sent from my shieldtablet using XDA-Developers mobile app
Click to expand...
Click to collapse
Well, I haven't had any issues since I disabled doze and I doubt that's a coincidence.
I agree that doze shouldn't kick on in your pocket, which is why I originally suspected the proximity sensor, but it could be a bug in ZTE's ROM.
My Mate 8 had a malfunctioning doze mode that would cause all notifications to stop as soon as the screen went off, even if the phone was moving. I fixed that by disabling doze also.
Sent from my ZTE A2017U using Tapatalk
The same issue I'm having on both colors I'm having .
Most of the time when picking the device from my jeans pocket refuses to open with double tap even after several attempts.
I have to unlock by pressing with power button and then when holding my phone it stating to work fine.
It's really annoying and frustrating.
Only double tap to sleep with nova prime or 3D next launcher working 100% perfect in all situations from home screen.
Also I'm using glimpse notification and enable the option to double tap to sleep from lock screen and works perfect all time.
Another feature having is it wakes up the screen automatically every time having notification alert and after screen being off continuous the led to be on as a reminder.
Sent from my iPad Air 2
So, I was wrong. Disabling doze didn't fix it. I went back to my OnePlus 3 for a day to get perspective. That phone pretty much never misses a tap-to-wake. It just works. Conversely, the Axon regularly "goes to sleep" when it's in my pocket and I can tap on the screen as many times as I want and it will never come on until I hit the power button. It's definitely not working like it should, at least not for me.
I'm not sure how anyone can say that it's working fine. I like everything else about the phone. This is just annoying because I can't rely on using tap-to-wake. I spend more time tapping on the screen when it's not working than I would if it just didn't have the feature and I had to use other methods. If ZTE could fix this to work as reliably as an LG or the OnePlus 3, I'd be in heaven.
greyhulk said:
So, I was wrong. Disabling doze didn't fix it. I went back to my OnePlus 3 for a day to get perspective. That phone pretty much never misses a tap-to-wake. It just works. Conversely, the Axon regularly "goes to sleep" when it's in my pocket and I can tap on the screen as many times as I want and it will never come on until I hit the power button. It's definitely not working like it should, at least not for me.
I'm not sure how anyone can say that it's working fine. I like everything else about the phone. This is just annoying because I can't rely on using tap-to-wake. I spend more time tapping on the screen when it's not working than I would if it just didn't have the feature and I had to use other methods. If ZTE could fix this to work as reliably as an LG or the OnePlus 3, I'd be in heaven.
Click to expand...
Click to collapse
Totally agree.
Hope ZTE makes improvements on that very useful feature to become just like LG.
Sent from my iPad Air 2
I'm hoping to get double tap to wake function working so that I don't have to pick up the phone when it's resting on a surface.
Anyone have double tap to wake feature working on their Pro 3?
Which Xposed module are you using?
Thanks.
Not Xposed module but this one works for me. Just a hiccup when combined with FP unlock.
Joms_US said:
Not Xposed module but this one works for me. Just a hiccup when combined with FP unlock.
Click to expand...
Click to collapse
any detrimental effect on battery life / wakelock?
Joms_US said:
Not Xposed module but this one works for me. Just a hiccup when combined with FP unlock.
Click to expand...
Click to collapse
Interesting, I always thought DT2W needed kernel support. Have you had any false wakes in your pocket? That was always what killed it for me on phones that didn't have it stock. They would randomly wake up in my pocket (not using light sensor clearly)
samjoandco said:
any detrimental effect on battery life / wakelock?
Click to expand...
Click to collapse
Well it definitely has effect on battery. I will do some test today and get back here.
benjmiester said:
Interesting, I always thought DT2W needed kernel support. Have you had any false wakes in your pocket? That was always what killed it for me on phones that didn't have it stock. They would randomly wake up in my pocket (not using light sensor clearly)
Click to expand...
Click to collapse
That's not a real double tap to wake. The app just runs an all black wall paper as 'off'. Since the Le pro 3 has an lcd rather than AMOLED screen, it would have a huge impact on battery life.
rocketJeff08 said:
That's not a real double tap to wake. The app just runs an all black wall paper as 'off'. Since the Le pro 3 has an lcd rather than AMOLED screen, it would have a huge impact on battery life.
Click to expand...
Click to collapse
Well as far as my eyes can see, it does wake and shut of screen. Try it first before making any wild guess.
--------------
I stand corrected, yes it does turn the screen blank only as soon as you turn of the screen via power button or the nifty (hold back) button.
So if you are not gonna use it like overnight doze or in your pocket, turn off the screen twice to make sure it is really turned off.
It is sad to see that gesture to wake up from theS9 was replaced in the S10 by Lift to wake, which is actually kinda useless, well we have double tap to wake, but gesture to wake was way more badass, you felt like a jedi waking up the screen of your phone.
I used to have it enabled too. I guess it's true there is no real proximity sensor anymore ?
latino147 said:
I used to have it enabled too. I guess it's true there is no real proximity sensor anymore ?
Click to expand...
Click to collapse
Furthermore the option to just call a contact by putting the phone against your ear is now gone too.... I hate when Samsung remove features from their flagships.... How hard is it for them to just use a normal proximity sensor inside or next to the speaker? Major disappointment.