I'm curious if the double tap to wake and initial swipe to unlock functions are working consistently for other users.
My double tap to wake success rate is about 60%. It doesn't seem really tied to length asleep, either.
On the lock screen, it rarely registers the first swipe to unlock. I've tried waiting a second to make certain I'm not swiping too soon, but that doesn't seem to matter.
I'm not sure if this is a hardware or software issue. I'm still on the L release and haven't manually updated to Q since I don't want to jeopardize my return ability at Best Buy.
Any feedback is appreciated.
Same issue 100%. I assume it's something linked to the drivers, as if the touch sensors are taking longer to wake than the screen.
Sent from my Nexus 5 using XDA Premium HD app
Thanks for the quick reply. When you said "Same issue 100%" do you mean that you have both issues or is it just the double tap to wake?
Thanks again!
Both.
Sent from my Nexus 9 using XDA Premium HD app
100% functional here on Q - clean install. L, for me was crap. Lagging and losing touch registering.
same
I gotta hit like 30 times hard to wake up. But it works fine if screen wasn't turned off for long time.
Related
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.
Now that we have root is there a fix for lock screen lag?
The current root procedure breaks more things so its not worth it even if it did
Sent from my SCH-I605 using xda app-developers app
thejron said:
The current root procedure breaks more things so its not worth it even if it did
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
No check again last night at 2am EST on IRC we finally got shipped OS with root.
jellydroid13 said:
No check again last night at 2am EST on IRC we finally got shipped OS with root.
Click to expand...
Click to collapse
yes and all works great. love xda
On my Note it appears to be a TouchWiz problem. I do not have the lock screen enabled as my phone never leaves my side. From sleep it takes approx. 1 second to wake if i press the power button when using TouchWiz. It wakes in less than half a second when i use SSLauncher or Nova!
Not using touchwiz. Nova launcher instead. Still get crazy lag. Seems its across all Note 2. Hoping for a fix.
I was browsing the n7100 forums and someone there asked the same question. A lot of people said that the lag was because of the phone coming out of deep sleep so the only way to fix the lag would be to keep some app running in the background that keeps the phone from sleeping. The only problem with that is that your battery life won't be as good.
why not just download voltage control or similar app and raise the minimum clock speed?
I have no lag at all. My note 2 is faster then my g3
Sent from my SCH-I605 using Tapatalk 2
mzimand said:
I have no lag at all.
Click to expand...
Click to collapse
It's not lag so much as it is a delay. On my Razr, there's no delay between pushing the power button and the screen coming on. There is a delay on the Note 2 of around a second between pushing the button and the screen coming on.
I don't think it's the lockscreen. I don't see a difference when I turn it off. My guess is the little bit of lag is for hardware reasons.
I've read that this is due to S-Voice waiting for input before the screen completely wakes up. Go into S-Voice and find the setting to wait for input on wake or something similar and turn that off. Lag should be fixed...dont have the phone yet and already giving advice, lol.
ElephantGlue said:
I've read that this is due to S-Voice waiting for input before the screen completely wakes up. Go into S-Voice and find the setting to wait for input on wake or something similar and turn that off. Lag should be fixed...dont have the phone yet and already giving advice, lol.
Click to expand...
Click to collapse
No such option at all.
There is a setting within S-Voice, just google it...im too lazy but there's even a video on YouTube of someone explaining it...
http://www.youtube.com/watch?v=AT5mEUlyMk4
ElephantGlue said:
There is a setting within S-Voice, just google it...im too lazy but there's even a video on YouTube of someone explaining it...
Click to expand...
Click to collapse
Went into s voice and there was nothing about that in there. Just wake on command and thats all.
ElephantGlue said:
There is a setting within S-Voice, just google it...im too lazy but there's even a video on YouTube of someone explaining it...
http://www.youtube.com/watch?v=AT5mEUlyMk4
Click to expand...
Click to collapse
This video is for home button lag not lockscreen lag. Plu my s voice was all ready disable by home button. This thread is for lockscreen lag/delay not home button.
The Fix for me
Here is what i found turn off s-voice this what i found to fix the lag i think it is running waiting for the wake voice command
do turn it off if you dont use it did and it did the trick it is in the apps drawer so dont look for it in the settings
I thought this was generally accepted to be due to the phone entering a deep sleep and shutting off the CPU cores, thus the delay in waking up the processor and thus the display.
Will do further testing around forced wake locks and hold cpu states.
i disabled the lock screen...so much better! this phone does not pocket dial, so its not needed anyway imo.
As above really!!
Is anyone one having issues with buttons been pressed whilst you are on the phone?
I have had mine cut out a few times and all sorts!!
stu_tls said:
As above really!!
Is anyone one having issues with buttons been pressed whilst you are on the phone?
I have had mine cut out a few times and all sorts!!
Click to expand...
Click to collapse
Are you saying the vibrations stop working all together?
Sent from my D6503 using XDA Premium 4 mobile app
I never mentioned vibrations!!!
I should have explained it a little better though
when you make or receive a call and you are on the phone the screen turns off and disables all button presses because the proximity sensor is covered
but even though the display is off and the sensor is covered you can still press buttons whilst on the phone
so far I have tried sending a text
cut people off
muted the phone
put the phone in to airplane mode
added events to my calendar
and more
all this with the side of my face while in a call
stu_tls said:
I never mentioned vibrations!!!
I should have explained it a little better though
when you make or receive a call and you are on the phone the screen turns off and disables all button presses because the proximity sensor is covered
but even though the display is off and the sensor is covered you can still press buttons whilst on the phone
so far I have tried sending a text
cut people off
muted the phone
put the phone in to airplane mode
added events to my calendar
and more
all this with the side of my face while in a call
Click to expand...
Click to collapse
Thats odd, what firmware are you on
This feature should usualy disable screen touch
Sent from my D6503 using XDA Premium 4 mobile app
on .55 at the min
there is a few with the same problem over on the sonymobile forum
I was wondering if the double tap to wake feature was causing the issue so I have just turned that off and see how it goes over the next few days
stu_tls said:
on .55 at the min
there is a few with the same problem over on the sonymobile forum
I was wondering if the double tap to wake feature was causing the issue so I have just turned that off and see how it goes over the next few days
Click to expand...
Click to collapse
Experiment with some posible things
Perhaps even try to update to a new firmware
Sent from my D6503 using XDA Premium 4 mobile app
I will see what its like with the update once its available I'm not going root!!
Yes have this issue once, when in a call, tone of number presses even though screen off.
Sent from my D6503 using Tapatalk
Happens to me too
For me it's sounds like Proximity sensor of Your Xperia Z2 isn't working. You can test it with apps, https://play.google.com/store/apps/details?id=imoblife.androidsensorbox&hl=ja like this
Proximity sensor works fine the first thing I did was test it
Well.... I can't think about any other reason.... As soon as I find infos I will share
Sent from my D6503 using XDA Free mobile app
I haven't had it happen since disabling the double tap to wake feature
i don't have double tap enabled and i have the same issue :S
I have tried it with and without double tap to wake and it makes no difference! It's really annoying me now!
stu_tls said:
on .55 at the min
there is a few with the same problem over on the sonymobile forum
I was wondering if the double tap to wake feature was causing the issue so I have just turned that off and see how it goes over the next few days
Click to expand...
Click to collapse
I have the same annoying fault. I can not find double tap to wake feature tu disable on XA2. How did You find it ?
Is there any way to make the fingerprint scanner with the screen off ?? I know in iphones they have a mod in cydia to do it.... Is it possible to get the same thing here ?
gdmlaz said:
Is there any way to make the fingerprint scanner with the screen off ?? I know in iphones they have a mod in cydia to do it.... Is it possible to get the same thing here ?
Click to expand...
Click to collapse
Why on earth would you want that ?
And if it's possible, I guess it will drain your battery faster...
speedme said:
Why on earth would you want that ?
And if it's possible, I guess it will drain your battery faster...
Click to expand...
Click to collapse
when you swipe it unlocks, No need to turn the screen on, Works fine on iphones my gf has hers rooted and works perfectly
gdmlaz said:
when you swipe it unlocks, No need to turn the screen on, Works fine on iphones my gf has hers rooted and works perfectly
Click to expand...
Click to collapse
As said, if it would be possible...the battery will drain a lot faster as the screen will always be active/the system will perform wakelocks all the time.
But it's a good idea
Sent from my SM-G900F using XDA Premium 4 mobile app
speedme said:
As said, if it would be possible...the battery will drain a lot faster as the screen will always be active/the system will perform wakelocks all the time.
Click to expand...
Click to collapse
That's what was generally said about double tap to wake, yet the phones that have this implemented, don't have drastically increased battery consumption because of it.
On the other hand, Samsungs half second delay after pressing home button, to wake after deep sleep (formerly just a "feature" of exynos devices, now with snapdragons as well) , is extremely annoying.
Don't see how would the screen always be active? Rather, the fingerprint sensor would be.
Sent from my SM-G900W8
Idan73 said:
That's what was generally said about double tap to wake, yet the phones that have this implemented, don't have drastically increased battery consumption because of it.
On the other hand, Samsungs half second delay after pressing home button, to wake after deep sleep (formerly just a "feature" of exynos devices, now with snapdragons as well) , is extremely annoying.
Don't see how would the screen always be active? Rather, the fingerprint sensor would be.
Sent from my SM-G900W8
Click to expand...
Click to collapse
That's what I was thinking if iphones are doing it without any problem and lg is using their knock why can't samsung
I don't believe battery drain would be an issue, but how would you keep the phone in a state to be read?
With double tap to wake and swipe to wake surely the waiting for action state is already developed.
Other possibility could be pressing the home button and sweeping the fi gerprint scanner at the same time to unlock in one motion.
sent from SGS5 running NeatRom 0X1
Up up up
Sent from my SM-G900T using Tapatalk
Prof Peach said:
Other possibility could be pressing the home button and sweeping the fi gerprint scanner at the same time to unlock in one motion.
sent from SGS5 running NeatRom 0X1
Click to expand...
Click to collapse
This is already working.. I scanned 3 times the same finger, and now working like this..
sosimple said:
This is already working.. I scanned 3 times the same finger, and now working like this..
Click to expand...
Click to collapse
if the screen is off the fingerprint won't unlock and turn the screen off at the moment...... you have to press the home key wait for screen to turn on then swipe
Prof Peach said:
With double tap to wake and swipe to wake surely the waiting for action state is already developed.
Other possibility could be pressing the home button and sweeping the fi gerprint scanner at the same time to unlock in one motion.
sent from SGS5 running NeatRom 0X1
Click to expand...
Click to collapse
gdmlaz said:
if the screen is off the fingerprint won't unlock and turn the screen off at the moment...... you have to press the home key wait for screen to turn on then swipe
Click to expand...
Click to collapse
I know. I talk about press (so the screen turns on) AND sweeping the finger at the same time.. This is working for me. I have to do a longer sweepe though.. And i have used all 3 finger setting to the same finger, probably a bit different portion of the finger every time..
Try it.. It works for me. Always unlock with one sweeping and pressing at the same time..
The disadvantage, i can unlock only with one finger.
The problem for me is that i have the home button to wake switched off using wanam exposed module. The phone was active in pocket way too many times.
sent from my Galaxy S5 running NeatRom v2.3
how?????
you can't
This seemingly small embellishment is just so darn useful it would be great if Xioami got around to incorporating it. I was using my old LG phone the other day to keep track of time while working on a dirty project, and the ability to double-tap to wake the screen with whatever portion of my fingers/knuckles which were clean at the moment was a real lifesaver. I forgot how truly useful it is, and I definitely miss it on the RN2!
try this en.miui.com/thread-125331-1-1 worked for me
socolino said:
try this en.miui.com/thread-125331-1-1 worked for me
Click to expand...
Click to collapse
Thanks, socolino, for the suggestion about the Knockr app (https://play.google.com/store/apps/details?id=tecnology.angs.knockr). I've taken a look, and, of course, while this app does its best to mimic DT2W, it is pretty much a kludge. It basically just turns the screen black to simulate it being shut off, but it actually keeps the phone awake. So this means a massive hit on battery life. And there is other collateral, too, because the phone doesn't actually go to sleep. For example, the notification LED does not get activated because the phone is not actually sleeping. And supposedly the power button doesn't turn the screen on as expected (i.e. get rid of the black mask).
Anyway, thanks again for the suggestion.
this feature is disabled in kernel, unless we will have source codes or xiaomi will anable this feature, there will be no dt2w
Yoni1581 said:
how?????
Click to expand...
Click to collapse
As a workaround, I use the WakeUp Touch L Free app. With the correct settings, it wakes the screen virtually every time by double tapping the proximity sensor. I haven't noticed any battery drain using it. Here are screenshots of the WakeUp Touch settings I use. Another couple of settings that are useful to modify: long press on WakeUp Touch in Notifications & assign it High Priority; lock WakeUp Touch in Recent Apps by dragging it down.
To turn the screen off via double tap, I use the Screen Off and Lock app in conjunction with Apex Launcher's double tap gesture [Nova & other launchers also have this gesture].