Related
EDIT: dkotoric has realised this is due to using the double tap to sleep function on some launchers. Locking your device with that prevents the fingerprint scanner from allowing access for some reason.
So today was my first full day with the 6P. It's a truly great device.
A whole bunch of times though when I've come to unlock the device I've had to put in my pattern because it won't accept the fingerprint scanner.
The icon at the bottom of the lock screen that should be a fingerprint is just a lock symbol. If I then lock the phone again and reunlock it works as expected.
Not sure if this is a software bug or some setting I've got wrong. Can't see a pattern for when it does it though. I've switched 'require pattern on restart' off which has made no difference.
Sent from my Nexus 6P using Tapatalk
Josh98 said:
So today was my first full day with the 6P. It's a truly great device.
A whole bunch of times though when I've come to unlock the device I've had to put in my pattern because it won't accept the fingerprint scanner.
The icon at the bottom of the lock screen that should be a fingerprint is just a lock symbol. If I then lock the phone again and reunlock it works as expected.
Not sure if this is a software bug or some setting I've got wrong. Can't see a pattern for when it does it though. I've switched 'require pattern on restart' off which has made no difference.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I've experienced that on one occasion today. That was after no occurrence in a full day's use yesterday. I put it down to slightly incorrect/incomplete/inaccurate finger print scans when it's set up.
Had no issues yet, used it for 2 days.
I have a pin set for after a reboot and it will ask for pin if I accidentally use pthe power button to switch on.
So far my finger print has not failed once o. My two index fingers.
I set up my finger print with a central / top end / bottom end / left edge / right edge and its worked fine
Been super accurate for me
Sent from my Nexus 6P using Tapatalk
I recommend using your main finger on different angles rather than using 5 different fingers when setting it up. ?
Sent from my HTC One_M8 using Tapatalk
I've setup each index finger once and it hasn't skippes a beat. I'd setup your finger again and this time move your finger around after every press to get different angles.
Sent from my Nexus 6P using Tapatalk
I haven't had any issues whatsoever. You could setup each index finger as 2-3 different fingers if you want to improve accuracy too.
Still waiting on my 6P, but I do have the 5X. Installed all of my usual apps when I received the phone. Set up fingerprint scanner. For the life of me couldn't figure out what the heck was going on. Every time I would unlock the phone it would go to PIN screen. I had read all of the reviews on how fantastic the FPS was. Started to get really annoyed. In fact I did a factory reset to see if this would help. This time I didnt install apps just set up FPS. Worked flawlessly. Installed apps again and what do you know stopped working again. Then it hit me, I have an app called ScreenOFF. Basically I could touch the screen and it would turn the screen off without hitting the power button. Uninstalled app and FPS worked perfectly. SO, be careful if you have any of these types of app as it seems it screws up the ability to bypass lock screen
It seems to have sorted itself over night. Hasn't done it so far today. Thanks guys.
Sent from my Nexus 6P using Tapatalk
what I notice is I use lock app and apex launcher so I have it set up to double tap on screen to lock the device. If I lock the device using this method I can no longer unlock the device with my fingerprint. I have to use the lock pattern. Then I have to lock the phone again via power button in order to use fingerprint scanner?
dkotoric said:
what I notice is I use lock app and apex launcher so I have it set up to double tap on screen to lock the device. If I lock the device using this method I can no longer unlock the device with my fingerprint. I have to use the lock pattern. Then I have to lock the phone again via power button in order to use fingerprint scanner?
Click to expand...
Click to collapse
Holy **** you're right yeah that's been my issue the whole time doing the same with Action Launcher. Been so used to using it it didn't occur to me that's the cause. That's annoying.
Sent from my Nexus 6P using Tapatalk
Josh98 said:
Holy **** you're right yeah that's been my issue the whole time doing the same with Action Launcher. Been so used to using it it didn't occur to me that's the cause. That's annoying.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I have your issue but I am not using any sort of double tap to lock apps. also I am using google now launcher.
Yea this happens when you use a third party app or launcher to lock the device via a double tap on the home screen. I set up a gesture in Nova Launcher to lock the device via a double tap on the homescreen and when I do I cannot unlock the phone via Imprint. There is just a lock symbol instead of the Imprint symbol and the only way to unlock it is using the pin. It seems that right now the only way to use Imprint to unlock the device is when you lock the device using the power/sleep button. Using any 3rd party software without root access to lock the device will only let you unlock the device via the pin instead of Imprint.
EDIT: Everything works fine with root access. If you grant the app performing the screen lock root access then you will be able to lock the screen with say a gesture like double tapping the home screen and then you will still be able to unlock the device via Imprint.
I had this issue as well where my 6P would ask for my pin after using the fingerprint scanner. It would do this many times per day.
What I have found to stop this from happening is removing the administrator rights from all the apps that uses it to lock the screen. It seems that the phone will ask for a pin when a 3rd party app locks the screen.
So I'll just rely on Android locking the screen on its own vs entering the pin so many times a day along with the fingerprint scanner.
guitar1238751 said:
Yea this happens when you use a third party app or launcher to lock the device via a double tap on the home screen. I set up a gesture in Nova Launcher to lock the device via a double tap on the homescreen and when I do I cannot unlock the phone via Imprint. There is just a lock symbol instead of the Imprint symbol and the only way to unlock it is using the pin. It seems that right now the only way to use Imprint to unlock the device is when you lock the device using the power/sleep button. Using any 3rd party software without root access to lock the device will only let you unlock the device via the pin instead of Imprint.
EDIT: Everything works fine with root access. If you grant the app performing the screen lock root access then you will be able to lock the screen with say a gesture like double tapping the home screen and then you will still be able to unlock the device via Imprint.
Click to expand...
Click to collapse
Are you just using nova as far as root access? I'm so used to just having greenify lock the screen, but I'm having this issue
Akomack said:
Are you just using nova as far as root access? I'm so used to just having greenify lock the screen, but I'm having this issue
Click to expand...
Click to collapse
I'm actually using loads of root apps including Greenify. (Though I'm not using greenify anymore) Everything is working fine. Are you having the issue when locking via a greenify gesture? I didn't even know Greenify had a screen locking gesture lol. Or do you mean the Imprint issue occurs after Greenify puts the device to sleep automatically?
guitar1238751 said:
I'm actually using loads of root apps including Greenify. (Though I'm not using greenify anymore) Everything is working fine. Are you having the issue when locking via a greenify gesture? I didn't even know Greenify had a screen locking gesture lol. Or do you mean the Imprint issue occurs after Greenify puts the device to sleep automatically?
Click to expand...
Click to collapse
Greenify has a widget that will hibernate and shut the screen off. I ended up finding this app that will shut the screen off and allow me to use the fingerprint to wake/unlock the device. :good:
So far, the only 3rd party app that I've found that can shut the screen off without root and without needing the pin again is Gravity Screen https://play.google.com/store/apps/details?id=com.plexnor.gravityscreenofffree&hl=en
It has a few widgets that you can link your double tap homescreen gesture to. Specifically, I'm using Lightning Launcher and link the double tap to the "Off" shortcut. The other shortcuts will lock the phone and then you'll need the pin again instead of just the fingerprint.
However, I think the way this app accomplishes this is to first blank the screen off with just a black overlay and then set the screen timeout to around 10seconds (it sets it right back to whatever you had before by the time you wake the screen again). So far, I haven't had a problem with this since the app also has "in pocket protection" in which it will keep the screen from turning back on if the proximity sensor is covered. So if you double tap to sleep but then put it in your pocket before the 10 seconds is up, it won't turn it back on. If you have it sitting on your desk, you can double tap to sleep, but then tap again on the black screen within the first 10 seconds to see the navigation keys again. This also has the weird side effect of not being able to use the fingerprint reader during those 10 seconds, because technically the screen is still on. This was a little unsettling at first since I couldn't figure out why the fingerprint reader wasn't vibrating when I thought the screen was "off". To me, it's not that big of a deal so it's fine with me.
My first phone was OnePlus One, second phone was LG G4, and LG V10 was my 3rd phone.
What do these phones have in common? They all have double tap to wake / sleep!
I can't believe this feature is not present in Nexus 6P and it is unbelievable how useful this feature is. For the first few days that I'm using Nexus 6P, my method of putting the phone to sleep is... WAITING FOR THE SCREEN TIMEOUT TO KICK IN. Can you believe that? I got so used to double tap that it never crossed my mind that you can wake or sleep the phone with the power button!
Anyway, enough of rant and I am actually here looking for assistance. I did some research and it seems like Nexus 6P has the tap to wake feature but it is disabled by default. If you root the phone you can enable this feature. However, I am not overly concerned with tap to wake since I use Nexus Imprint anyway. My main focus is the ability to sleep / lock without pressing the physical power button. Is the disabled feature tap to wake only or can it also do tap to sleep / lock?
Also, are there any methods of putting Nexus 6P to sleep / lock without using the physical power button? I tried couple apps but they seem to not work properly with Nexus Imprint (meaning that I have to enter PIN or password to unlock after waking up the phone with fingerprint).
If you want to double tap to lock you can set it up with gestures using Nova launcher. Believe you need prime version.
Sent from my Nexus 6P using XDA-Developers mobile app
https://play.google.com/store/apps/details?id=com.katecca.screenofflock
You could also download a custom ROM like Chroma or Pure Nexus. They are pretty close to stock but with other goodies like double tap to sleep. They also get updated very frequently and get great support from their developers.
I am looking for the same, prefer to keep stock ROM and just do a build.prop edit or flashable .Zip
Sent from my Nexus 6P using Tapatalk
Pretty sure there's a thread detailing how to enable this on the stock ROM in our apps/themes section.
GMD GestureControl (play store) works fine (root)
http://forum.xda-developers.com/android/apps-games/app-fingerprint-to-unlock-t3466549
dzlove98 said:
My first phone was OnePlus One, second phone was LG G4, and LG V10 was my 3rd phone.
What do these phones have in common? They all have double tap to wake / sleep!
I can't believe this feature is not present in Nexus 6P and it is unbelievable how useful this feature is. For the first few days that I'm using Nexus 6P, my method of putting the phone to sleep is... WAITING FOR THE SCREEN TIMEOUT TO KICK IN. Can you believe that? I got so used to double tap that it never crossed my mind that you can wake or sleep the phone with the power button!
Anyway, enough of rant and I am actually here looking for assistance. I did some research and it seems like Nexus 6P has the tap to wake feature but it is disabled by default. If you root the phone you can enable this feature. However, I am not overly concerned with tap to wake since I use Nexus Imprint anyway. My main focus is the ability to sleep / lock without pressing the physical power button. Is the disabled feature tap to wake only or can it also do tap to sleep / lock?
Also, are there any methods of putting Nexus 6P to sleep / lock without using the physical power button? I tried couple apps but they seem to not work properly with Nexus Imprint (meaning that I have to enter PIN or password to unlock after waking up the phone with fingerprint).
Click to expand...
Click to collapse
Nova with root and voilà! It's under the "gestures" section. Select "double tap" and tell it what to do. It is double tap on the home screen only though, fyi.
Sent from my Nexus 6P using Tapatalk
I'm running the stock UK version of MM on my N910F. I'm rooted and running xposed. I decided to set up the fingerprint scanner as my unlock method of choice and found the No Lock Home xposed module and set it up for my home broadband so I don't need to unlock the phone when I'm connected at home.
All works well apart from the fact that when I wake the phone, I have to swipe the screen. It's not a huge issue but it's a little annoying - I've used similar set ups to No Lock Home on my S3 and Note 3 and never had the swipe issue - is there a simple way to stop it? Am I missing something here?
hi, i'm looking for a stable rom (even stock) with double tap to wake, the power button is almost dead, and it's my mom phone, actually i'm using cm13 with quanta tweaks, but sometimes i have issue, like double tap not working on boot or touch freezing in the lockscreen, do you know a stable rom/kernel with this function? thanks
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.