So i have been using Double Tap To Sleep since I got my phone. And i am sure there wasnt this issue on Android 9.
So sometimes when I use DTTS, the screen would turn off and immediately turn on again. Straight to my home screen. Bypassing the FP Scanner and Password.
Anyone have this issue as well?
Do you have any wakelocks blocked through custom kernel?
TikiThePug said:
Do you have any wakelocks blocked through custom kernel?
Click to expand...
Click to collapse
Im using official ROM...
Related
I've tried a couple of ROMs with double tap to wake. I honestly love the feature, but I've had too many issues with wake locks in my pocket, so I've decided it's not worth it and I'll turn it off. The problem is, it doesn't actually turn off. I'll hit that off switch, tap my screen a few times, and it's awake again. This is frustrating because then it wakes up in my pocket still. Is there any way to permanently remove it from the ROM? Maybe something I can flash or something I can change to completely disable this feature?
Grab /system/lib/hw/power.shamu.so from a pre-rooted (untouched) stock rom or a rom that hasn't enabled it
WyldOne91 said:
I've tried a couple of ROMs with double tap to wake. I honestly love the feature, but I've had too many issues with wake locks in my pocket, so I've decided it's not worth it and I'll turn it off. The problem is, it doesn't actually turn off. I'll hit that off switch, tap my screen a few times, and it's awake again. This is frustrating because then it wakes up in my pocket still. Is there any way to permanently remove it from the ROM? Maybe something I can flash or something I can change to completely disable this feature?
Click to expand...
Click to collapse
FWIW, Exodus and I'm sure some other ROMs, have a setting to prevent pocket wake ups by using the proximity sensor.
WyldOne91 said:
I've tried a couple of ROMs with double tap to wake. I honestly love the feature, but I've had too many issues with wake locks in my pocket, so I've decided it's not worth it and I'll turn it off. The problem is, it doesn't actually turn off. I'll hit that off switch, tap my screen a few times, and it's awake again. This is frustrating because then it wakes up in my pocket still. Is there any way to permanently remove it from the ROM? Maybe something I can flash or something I can change to completely disable this feature?
Click to expand...
Click to collapse
Are you sure it's not ambient display waking your phone?
Eh... "ambient display" doesn't wake your phone. Ambient display just shows WHEN your phone is awoken by... tap to wake, shake to wake, incoming notification.
OP: Some people confuse tap to wake and shake to wake. Nexus 6 implements shake to wake by default. Problem is that tapping on the screen can.... shake the phone.
This generally should NOT be going off in your pocket. Either, that is. Reason is that it is *supposed* to use the state of the proximity sensor as a CONDITION on whether or not it should start up ambient display. The proximity sensor will read as "near" when the phone is in your pocket, thus prevent tap or shake to wake from triggering ambient display.
So sounds like you probably tried a couple of different sysimages that both contain a bug that stops it from taking the proximity sensor into account. My guess would be something that is based on cyanogenmod (aka "the buggiest android ever conceived"). Try stock and see if the problem goes away.
Personally, I prefer to use a custom ROM with native LED control and disable ambient display.
danarama said:
Grab /system/lib/hw/power.shamu.so from a pre-rooted (untouched) stock rom or a rom that hasn't enabled it
Click to expand...
Click to collapse
what do you even mean?
slamsal said:
what do you even mean?
Click to expand...
Click to collapse
What part don't you understand?
If you haven't got a modified Nexus 6 with this problem, then this isn't relevant to you.
Ok I'm feeling a little dumb lol. On thr AT&T variant, the fingerprint sensor is not waking up the device when locked and screen off. Am I just missing a setting somewhere?
The international version works just fine to wake up and unlock screen, but the AT&T version doesn't.
Any input?
Works for me
apascual89 said:
Ok I'm feeling a little dumb lol. On thr AT&T variant, the fingerprint sensor is not waking up the device when locked and screen off. Am I just missing a setting somewhere?
The international version works just fine to wake up and unlock screen, but the AT&T version doesn't.
Any input?
Click to expand...
Click to collapse
My att note 8 works as expected with this. Maybe a setting i forgot about enabling. Perhaps power save more disables this ? Are you using power save?
Edit- tested with power save. This doesn't seem to be the culprit.
Ok there's a setting where you scan in your prints. It's a toggle you must enable. That should do the trick.
forumcreeper said:
My att note 8 works as expected with this. Maybe a setting i forgot about enabling. Perhaps power save more disables this ? Are you using power save?
Edit- tested with power save. This doesn't seem to be the culprit.
Click to expand...
Click to collapse
No power save and I factory reset just to see..... No change not really sure.
apascual89 said:
No power save and I factory reset just to see..... No change not really sure.
Click to expand...
Click to collapse
There's a toggle in the settings where you scan your prints in. That should fix it
forumcreeper said:
There's a toggle in the settings where you scan your prints in. That should fix it
Click to expand...
Click to collapse
I just removed all my fingerprints and added them back and it still doesn't turn on screen.
https://ibb.co/RL]
Heres a sreenshot of my screen
Do you have this option ?
forumcreeper said:
There's a toggle in the settings where you scan your prints in. That should fix it
Click to expand...
Click to collapse
Yup it's under lock screen and security then smart Lock. You wanna select the first option and it should automatically unlock to home screen when using your fingerprint.
Composed on the Galaxy Note8
forumcreeper said:
<img src="https://preview.ibb.co/ih3kdk/Screenshot_20170915_213334.jpg" alt="Screenshot_20170915_213334" border="0">
Do you have this option ?
Click to expand...
Click to collapse
Screenshot didn't come through, but if you mean the fingerprint unlock toggle, yes I have it on.
Could you fix the problem?
Could you fix the problem? I bought Galaxy S9+ AT&T version and it seems has the same problem.
apascual89 said:
Screenshot didn't come through, but if you mean the fingerprint unlock toggle, yes I have it on.
Click to expand...
Click to collapse
Mohannakattan said:
Could you fix the problem? I bought Galaxy S9+ AT&T version and it seems has the same problem.
Click to expand...
Click to collapse
The only way I could get it to work was to set screen to lock immediately with power button. Can't remember the exact setting title, but I think it's Settings/secure lock settings
Basically if you set the screen to lock as soon as it turns off it'll trigger the fingerprint to turn on screen immediately.
It worked!!! Thank you very very much. Really appreciate it. I was one step farther to return the phone.
apascual89 said:
The only way I could get it to work was to set screen to lock immediately with power button. Can't remember the exact setting title, but I think it's Settings/secure lock settings
Basically if you set the screen to lock as soon as it turns off it'll trigger the fingerprint to turn on screen immediately.
Click to expand...
Click to collapse
Mohannakattan said:
It worked!!! Thank you very very much. Really appreciate it. I was one step farther to return the phone.
Click to expand...
Click to collapse
It drive me crazy as well.... After numerous searches I found that suggestion somewhere. Glad it helped!
apascual89 said:
The only way I could get it to work was to set screen to lock immediately with power button. Can't remember the exact setting title, but I think it's Settings/secure lock settings
Basically if you set the screen to lock as soon as it turns off it'll trigger the fingerprint to turn on screen immediately.
Click to expand...
Click to collapse
I just wanted to say thanks. I flashed my unlocked Note8 with the AT&T firmware to see if it is worth the bloat. On the unlocked firmware I never had to make that change, it was always on. I don't know why I didn't think to check that setting and I don't know why AT&T would set it to ten minutes, there are so many things that can happen in ten minutes. Thanks!
I use a widget called screen tap to lock or something or another for the double tap to sleep on any launcher. Have been using it for a while across a few phones. However when I got the S10 I just started using face unlock due to this slow and clunky FP sensor.....but I've discovered this issue where double tap to sleep with face unlock on makes the phone immediately wake back up to the lock screen for a second unlike pressing the power button which acts correctly. I tested it out on nova's built in settings without the widget (which I was using on one UI launcher) and it does the same thing so obviously it's some sort of conflict with face unlock and double tap to sleep. Anyone know why?
carnivalrejectq said:
I just started using face unlock due to this slow and clunky FP sensor.....
Click to expand...
Click to collapse
Wait, slow and clunky? Maybe off topic but mine is extremely consistent after they fixed it like 4 months ago. Maybe relearn prints and make sure you get the whole thumb scanned.
Also I have double tap to sleep setup on Nova using accessibility as screen lock method and tried your scenario with face unlock enabled, but did not encounter your issue on Android 10
Ripthulhu said:
Wait, slow and clunky? Maybe off topic but mine is extremely consistent after they fixed it like 4 months ago. Maybe relearn prints and make sure you get the whole thumb scanned.
Also I have double tap to sleep setup on Nova using accessibility as screen lock method and tried your scenario with face unlock enabled, but did not encounter your issue on Android 10
Click to expand...
Click to collapse
Oh, I'm on cricket in the US , so still stuck on 9 (with no hope in sight for 10 lol). I've deleted them and reset them a few times now and idk it's just not as fast as I'm used to with capacitive ones, there's an extra second, even compared to the one in the OnePlus 7t I was using for a few days , it cannot compete. It works a lot better if you press hard and firm I guess, but again I'm not used to that. But yeah idk why it's doing that, did it to me on Nova too if I use double tap to sleep at all it immediately opens back up to the lock screen. I don't think it's looking for my face in that scenario either because it doesn't face unlock when it does it, but it definitely IS happening because of the face unlock because it doesn't happen if I turn it off altogether and use the double tap to sleep......if I press the power button to turn the screen off this does not happen.
Anyone else having this issue? I have to either tap phone or tap power button to get screen to turn on, then face unlock will work. Previously I would be able to just hold it up to my face with screen off and it would just unlock. After most recent update it no longer does this. Very frustrating.
Check maybe lift to wake phone is turned off in the settings.
cwburns32 said:
Anyone else having this issue? I have to either tap phone or tap power button to get screen to turn on, then face unlock will work. Previously I would be able to just hold it up to my face with screen off and it would just unlock. After most recent update it no longer does this. Very frustrating.
Click to expand...
Click to collapse
Mine was doing that too...along with auto brightness stuck and the proximity sensor wasn't turning the screen on and off during calls. As a last resort before sending it back (since I had to wipe it anyway) I tried the first android 11 beta (not 1.5). It almost completely fixed everything but the proximity sensor. Still had to occasionally tap the phone or power it on to face unlock though. Google replaced it because of the proximity sensor. The replacement phone is working fine on latest update of 10
redskykiter said:
Mine was doing that too...along with auto brightness stuck and the proximity sensor wasn't turning the screen on and off during calls. As a last resort before sending it back (since I had to wipe it anyway) I tried the first android 11 beta (not 1.5). It almost completely fixed everything but the proximity sensor. Still had to occasionally tap the phone or power it on to face unlock though. Google replaced it because of the proximity sensor. The replacement phone is working fine on latest update of 10
Click to expand...
Click to collapse
Good to know. Haven't wiped just yet, may do what you did there.
cwburns32 said:
Good to know. Haven't wiped just yet, may do what you did there.
Click to expand...
Click to collapse
I really didn't have ANY bugs that I found with beta 1....read 1.5 has some issues. Is your proximity sensor working? I used androsensor to confirm
edit I did wipe face data before erasing
redskykiter said:
I really didn't have ANY bugs that I found with beta 1....read 1.5 has some issues. Is your proximity sensor working? I used androsensor to confirm
Click to expand...
Click to collapse
My prox sensor is working fine. It just won't face unlock with screen off. Turned on lift to check phone and now screen wakes without me having to do anything but still, there was a time where I had that feature off and face unlock would unlock with screen off
cwburns32 said:
My prox sensor is working fine. It just won't face unlock with screen off. Turned on lift to check phone and now screen wakes without me having to do anything but still, there was a time where I had that feature off and face unlock would unlock with screen off
Click to expand...
Click to collapse
I never had lift to wake off. That sounds like a solution to me
redskykiter said:
I never had lift to wake off. That sounds like a solution to me
Click to expand...
Click to collapse
Yah maybe I am just imaging things idk hahah lift to wake works, along with various other setting so not a huge issue. Thanks
Does anybody else have this issue where if you turn on always on display in AOSP ROMs like Pixel Experience, after a few seconds you can't double tap to wake the screen (the screen becomes unresponsive)
Is this an issue related to kernel?
Thomas_Chesterson said:
Does anybody else have this issue where if you turn on always on display in AOSP ROMs like Pixel Experience, after a few seconds you can't double tap to wake the screen (the screen becomes unresponsive)
Is this an issue related to kernel?
Click to expand...
Click to collapse
The same on stock rom, for me.
I'm on MIUI 13 with Android 11 (I had too much trouble with the A12 version) and I have AoD disabled. Still sometimes the double tap to wake feature stops working. I have to unlock it with the fingerprint and then turn the screen off to make it work again.
TapaSte said:
The same on stock rom, for me.
Click to expand...
Click to collapse
As far as I know, in MIUI there's an option at the bottom of the developer options, something about MI Optimization. Turning it off fixes the problem
Thomas_Chesterson said:
As far as I know, in MIUI there's an option at the bottom of the developer options, something about MI Optimization. Turning it off fixes the problem
Click to expand...
Click to collapse
On redmi note 11 no such option is present, under "developer options".
TapaSte said:
On redmi note 11 no such option is present, under "developer options".
Click to expand...
Click to collapse
Try this
Thomas_Chesterson said:
Try this
Click to expand...
Click to collapse
Thanks for the video. I'll give a try. I wish that under this aspect there is no difference among China and EU ROM.
Tried but unfortunately it only solves the aod issue
Double tap to wake does not work again both with AOD on and off.