Related
Every time I turn the screen off, the phone vibrates 2 times with about 5 seconds delay. I have tracked this vibration down to fingerprint scanner. Its seems to be an indication of it going to sleep. When you turn the screen off, you can place your finger on the scanner and it will wake the screen up. This function is active for few seconds, and then the scanner goes to sleep (signalized by the vibration).
Anyone know how to turn this notification off? Or even better, how to disable this whole function entirely so the scanner sleeps immediately after screen goes off?
Additional information
the Vibration occurs even if you turn the screen on after turning it off but before the vibration (seems irregular though)
the time of the vibration changes with the lock time setting
turning off notification vibrations entirely helps, but I dont want to do that
not using the fingerprint unlock helps too, but I would prefer to keep using it
KowboyBebop said:
Every time I turn the screen off, the phone vibrates 2 times with about 5 seconds delay. I have tracked this vibration down to fingerprint scanner. Its seems to be an indication of it going to sleep. When you turn the screen off, you can place your finger on the scanner and it will wake the screen up. This function is active for few seconds, and then the scanner goes to sleep (signalized by the vibration).
Anyone know how to turn this notification off? Or even better, how to disable this whole function entirely so the scanner sleeps immediately after screen goes off?
Additional information
the Vibration occurs even if you turn the screen on after turning it off but before the vibration (seems irregular though)
the time of the vibration changes with the lock time setting
turning off notification vibrations entirely helps, but I dont want to do that
not using the fingerprint unlock helps too, but I would prefer to keep using it
Click to expand...
Click to collapse
Hey. My g928c is runnin on custom rom/kernel. Not sure that could be the same or not but when I turn off the screen, it doesnt wake without pressing home or power button. Maybe you use easyHome app or kind of app which uses fingerprint sensor. My device doesnt wake up after turned the screen off and placing a finger on the scanner or etc. As I remember, easyHome app has got that wake up option but in one of older versions. I hope you solve it..
Oh, I was sure this behavior was caused by the sensor, but now that I actually switched back default locker, it doesnt do it. So the issue is entirely in the Hi Locker I am using. I should have checked that in the first place. So thank you. Now my question changes. Are there any more locker options that use fingerprint scanners other than the default and hi locker?
KowboyBebop said:
Oh, I was sure this behavior was caused by the sensor, but now that I actually switched back default locker, it doesnt do it. So the issue is entirely in the Hi Locker I am using. I should have checked that in the first place. So thank you. Now my question changes. Are there any more locker options that use fingerprint scanners other than the default and hi locker?
Click to expand...
Click to collapse
Glad to know you solved it. Im using default lockscreen and never wondered any others lol. Maybe you try{if didnt} Go launcher's go locker etc. Dont know anything more in this case sorry, good luck.
I tried few other alternatives and honestly they were way too cumbersome and bloated. For now I revoked Hi Locker's permission to make notifications, which got rid of the vibration. I hope nothing broke with this modification. Thanks for getting me on track.
There is an issue I have been facing with all CM13 based roms for the OP2. If Dt2W is active it causes sudden vibrations when am on call. To troubleshoot the issue I did the following.
1. Wipe everything except sd card.
2. Flash Rom (Any with CM13 base)
3. Flash Gapps (Tried Open Full and TBO)
4. After first boot set up everything and let the phone settee
5. Make a few calls.
My Observations.
1. The vibrations are not intermittent i.e. they don't happen on every call just few of them.
2. It mainly happens when I am moving and talking eg when I am calling someone and walking. If my hand is still it mostly doesn't happen.
3. NO apps or specific Setup is causing this since I tried to reproduce the issue without any apps or setting changes (just ROM and Gapps)
4. Back in April '16 at some point Dt2W was broken on CM 13 roms the issue seems to have started right after that(I may be mistaken though)
I have spent a lot of time on the custom rom forums but no one seems to mention this as a bug. The reply mostly I got was disable Dt2W and that is really not a solution. It makes me wonder if am the only one facing the issue.
Can anyone who is NOT facing the bug post steps they followed to setup their rom may be I can try and trouble shoot further.
Thanks
AshDroidG said:
There is an issue I have been facing with all CM13 based roms for the OP2. If Dt2W is active it causes sudden vibrations when am on call. To troubleshoot the issue I did the following.
1. Wipe everything except sd card.
2. Flash Rom (Any with CM13 base)
3. Flash Gapps (Tried Open Full and TBO)
4. After first boot set up everything and let the phone settee
5. Make a few calls.
My Observations.
1. The vibrations are not intermittent i.e. they don't happen on every call just few of them.
2. It mainly happens when I am moving and talking eg when I am calling someone and walking. If my hand is still it mostly doesn't happen.
3. NO apps or specific Setup is causing this since I tried to reproduce the issue without any apps or setting changes (just ROM and Gapps)
4. Back in April '16 at some point Dt2W was broken on CM 13 roms the issue seems to have started right after that(I may be mistaken though)
I have spent a lot of time on the custom rom forums but no one seems to mention this as a bug. The reply mostly I got was disable Dt2W and that is really not a solution. It makes me wonder if am the only one facing the issue.
Can anyone who is NOT facing the bug post steps they followed to setup their rom may be I can try and trouble shoot further.
Thanks
Click to expand...
Click to collapse
Just a shot in the dark , did u try enabling prevent accidental wake-up ? Could be possible that when you are on a call you end up tapping the screen to trigger the vibration (Double tap).
When the prevent accidental wake-up is enabled this wont happen.
Hope it helps.
mdaamir1989 said:
Just a shot in the dark , did u try enabling prevent accidental wake-up ? Could be possible that when you are on a call you end up tapping the screen to trigger the vibration (Double tap).
When the prevent accidental wake-up is enabled this wont happen.
Hope it helps.
Click to expand...
Click to collapse
Yup tried that too but still bug persist.
I did flash an AOSP and CAF based rom (Exodus) to test it and found that it does not have the bug (Have to mention that they have disabled vibrations for dt2w meaning when it is active and used to wake the screen there is no vibration) . I think my hunch of something being wrong with CM13 base is correct.
Are you using CM13?
Thnx for replying
AshDroidG said:
Yup tried that too but still bug persist.
I did flash an AOSP and CAF based rom (Exodus) to test it and found that it does not have the bug (Have to mention that they have disabled vibrations for dt2w meaning when it is active and used to wake the screen there is no vibration) . I think my hunch of something being wrong with CM13 base is correct.
Are you using CM13?
Thnx for replying
Click to expand...
Click to collapse
I was , but i am on Exodus now. Maybe the next time i flash CM13 i will try to reproduce the problem.
Sent from my ONE A2003 using XDA-Developers mobile app
mdaamir1989 said:
I was , but i am on Exodus now. Maybe the next time i flash CM13 i will try to reproduce the problem.
Click to expand...
Click to collapse
Sure:good: thank you for your time.
Update
So I went back and flashed OOS to check why these vibrations don't happen on OOS. Turns out this has nothing got to do withe Dt2W or dialer as such. This behavior happens because the Prevent Accidental Wake up disables the Screen Wake up but allows Dt2W inputs. This is what I found
On OOS.
a. Double tap screen normally and you will feel haptic feedback and screen will turn on.
b. Cover the proximity sensor and double tap, the screen will remain off and there will be NO haptic feedback. Which is how prevent accidental wakeup should actually work.
On CM13 Based Roms.
a. Cover the proximity sensor and double tap the screen the screen remain OFF but the phone register's the double tap to wake gesture. Ideally prevent accidental wakeup should not allow the gesture input as well.
This behavior is may be because prevent accidental wake has not been integrated the properly. I say this because when the phone rings and you cover the proximity sensor (Prevent Accidental Wakeup Active) the screen goes off, this is not the correct behavior. The Prevent accidental wake up option should actually ignore proximity sensor when there is a phone call.
As of now I am on RR 5.7.1 and have disabled Vibrate on touch (Meaning even if the gesture happens the phone wont vibrate) I find this a better workaround rather than disabling Dt2W. Disabling Vibrate on touch means no vibrations for button press and long press and stuff like that which is ok with me (this option could also be the reason why some user say they have not felt any vibrations when making calls.)
AshDroidG said:
So I went back and flashed OOS to check why these vibrations don't happen on OOS. Turns out this has nothing got to do withe Dt2W or dialer as such. This behavior happens because the Prevent Accidental Wake up disables the Screen Wake up but allows Dt2W inputs. This is what I found
On OOS.
a. Double tap screen normally and you will feel haptic feedback and screen will turn on.
b. Cover the proximity sensor and double tap, the screen will remain off and there will be NO haptic feedback. Which is how prevent accidental wakeup should actually work.
On CM13 Based Roms.
a. Cover the proximity sensor and double tap the screen the screen remain OFF but the phone register's the double tap to wake gesture. Ideally prevent accidental wakeup should not allow the gesture input as well.
This behavior is may be because prevent accidental wake has not been integrated the properly. I say this because when the phone rings and you cover the proximity sensor (Prevent Accidental Wakeup Active) the screen goes off, this is not the correct behavior. The Prevent accidental wake up option should actually ignore proximity sensor when there is a phone call.
As of now I am on RR 5.7.1 and have disabled Vibrate on touch (Meaning even if the gesture happens the phone wont vibrate) I find this a better workaround rather than disabling Dt2W. Disabling Vibrate on touch means no vibrations for button press and long press and stuff like that which is ok with me (this option could also be the reason why some user say they have not felt any vibrations when making calls.)
Click to expand...
Click to collapse
Actually I face similar issue on cm based Roms , this issue is from day one . Also on OOS , sometimes screen is being pressed and notification bar slides down and buttons are being pressed while on call. Disabling dt2w solves temporarily.
kunalshah912 said:
Actually I face similar issue on cm based Roms , this issue is from day one . Also on OOS , sometimes screen is being pressed and notification bar slides down and buttons are being pressed while on call. Disabling dt2w solves temporarily.
Click to expand...
Click to collapse
Its a problem with CM13 base. So any rom using CM 13 will have this behavior. I believe the people who say they don't face this behavior have disabled vibrate on touch like I have now. I never had an issue with OOS though.
Can you let me know does your screen goes off when ringing on CM 13 (when you cover the proximity sensor with prevent accidental wake enabled)
AshDroidG said:
Its a problem with CM13 base. So any rom using CM 13 will have this behavior. I believe the people who say they don't face this behavior have disabled vibrate on touch like I have now. I never had an issue with OOS though.
Can you let me know does your screen goes off when ringing on CM 13 (when you cover the proximity sensor with prevent accidental wake enabled)
Click to expand...
Click to collapse
i am on OOS , flashing cm13 soon , will let u know.
Hey,
Last couple days I realized my fingerprint security sensor stopped working, sometimes. It wouldn't seem to see any fingerprint attempts, unless I did a reboot, then would only work for a short time.I realized i made one adjustment recently, i turned on 'finger sensor gestures' from settings, advanced features(so wasn't worth it ).
Once I turned this feature off again, the security sensor worked, instantly. Can someone else try this? You might have to wait a bit for the sensor to stop working. I don't think it was automatic, only when turning the feature off.
I noticed this question/issue on another forum with no solution, but I didn't have an account.
I swear I didnt click the camera (well, maybe once or twice, who can't help it)!
Sent from my SM-G950W using Tapatalk
Fingerprint scanner was not working for 3 hours. I read your post and turned off the advanced gesture feature add the scanner worked instantly without a reboot or anything.
I'd say problem solved
This worked for me!
Quick recap:
-Pull down the notification panel and tap the Settings icon
-Type Finger Sensor Gestures in the search option and tap the only result
-Turn this feature off
Thanks!
I've had this same issue per https://forum.xda-developers.com/galaxy-s8/help/fingerprint-sensor-stops-fixed-reboot-t3596851
Will try disabling gestures next time. Thanks!
Worked for me! Didn't need to reboot. THANKS!
I have the same issue and realized what the issue was. I was wondering if anyone knows of a permanent fix where I can enable finger gesture as I grown accustomed to it coming from the Pixel. Thanks!
I have not found a permanent fix for this problem, however I have found a solution that allows the fingerprint scanner to work again WITHOUT having to reboot the device. This can be accomplished by following the steps:
juss2nuff said:
I have not found a permanent fix for this problem, however I have found a solution that allows the fingerprint scanner to work again WITHOUT having to reboot the device. This can be accomplished by following the steps:
Click to expand...
Click to collapse
Assjole
Here was my fix:
Settings/Lock Screen and security/Secure Lock Settings/Secure lock time
Choose: "Instantly with the power key or when the screen times out"
When I changed it to the setting above, the fingerprint and facial recognition worked.
I have noticed that fingerprint reading does not work when the phone is plugged in the charger. It works again when I unplug it.
Edit: this error occurs when you try to add a new fingerprint
A couple of times since I've had the 6T, when I tapped the screen to bring up the ambient display or lock screen the fingerprint sensor wouldn't be active. The fingerprint icon would be white and putting a finger on it did nothing. The first time it happened, I was using the single tap to ambient display. When the fingerprint sensor didn't work, I hit the power button to bring up the lock screen and the sensor activated and I was able to unlock using a fingerprint.
I've switched to using double tap to lock screen with both face & fingerprint unlock. Tonight when I tapped the screen the lock screen came up but again the fingerprint icon was white, not active, and face unlock didn't even work. I had to swipe up to unlock with my PIN. After doing so, both fingerprint & face unlock have worked as normal.
Any ideas on why this could be happening? Just a random software glitch? Or does device security require unlocking with a PIN/Password/Pattern after so many fingerprint/face unlocks or after a given amount of time?
yes, it happened to me as well.
but i dont think this is a bug/glitch. This happened to me on other android phones as well.
i think this is a security thing where your fingerprint sensor/ face id is disabled once in a while and you can only sign in with your pin/password.
Hello everyone.
My Moto e4 sometimes gets stuck on lockscreen while I'm unlocking it. I swipe up, I insert the unlock pattern and the phone doesn't unlock. I am able to do an emergency call or go back to lock screen, but it doesn't do anymore, so I'm forced to reboot the phone. It happens with digit code too. If I enable the fingerprint sensor to unlock, It often has the same problem, except that I can read a strange message under the lockscreen's clock saying something that sounds like "fingerprint sensor not detected". As always, I need to reboot the phone to unlock it. Does someone else had this kind of problem?
Thanks in advance!