Related
I'm just trying to narrow down why randomly the fingerprint scanner does not wake the phone. It might happen once a day or not for a couple of days, but it seems to always come back. Not a huge deal since the power button will always work, but it is disconcerting when it happens. I'm not using any power widget or lock program although I do use Nova Launcher Pro. Does this happen to anyone else and if so have you narrowed it down?
Mine always wakes my phone, although every now and then it doesn't recognize my print. However, I believe it's because of how my finger lays on the sensor so I think it's user error in my case.
I've registered 4 prints, 2 from each index finger and all in different positions on the sensor to get the least reading errors.
Are you saying that you get no vibration as in it doesn't even register at times therefore you HAVE to use the power button to wake it?
I use nova pro too.
jbdan said:
Mine always wakes my phone, although every now and then it doesn't recognize my print. However, I believe it's because of how my finger lays on the sensor so I think it's user error in my case.
I've registered 4 prints, 2 from each index finger and all in different positions on the sensor to get the least reading errors.
Are you saying that you get no vibration as in it doesn't even register at times therefore you HAVE to use the power button to wake it?
I use nova pro too.
Click to expand...
Click to collapse
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
bobby janow said:
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
Click to expand...
Click to collapse
I get this occasionally when charging but that occurred on stock everything, can't say I've noticed it in any other capacity. Are you using smart lock or an app to lock your screen?
Edit: I should read your post before replying, disregard my app question. Still asking about smart lock though.
Sent from my Nexus 5X using Tapatalk
bobby janow said:
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
Click to expand...
Click to collapse
And I meant to include the "big" question in my original reply. Big being "what mods are you using"
Best way to trial and error issues as you well know? I'd test it on all stock (for a day or 2) and see what that gets you then you can narrow down to if it's the kernel or not. I'm not a kernel dev, but an educated guess would point to that imo
SlimSnoopOS said:
I get this occasionally when charging but that occurred on stock everything, can't say I've noticed it in any other capacity. Are you using smart lock or an app to lock your screen?
Edit: I should read your post before replying, disregard my app question. Still asking about smart lock though.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Smart lock, yes. Well smart unlock isn't it? I have a couple of BT unlock devices, Mi Band and car BT radio but that's it.
jbdan said:
And I meant to include the "big" question in my original reply. Big being "what mods are you using"
Best way to trial and error issues as you well know? I'd test it on all stock (for a day or 2) and see what that gets you then you can narrow down to if it's the kernel or not. I'm not a kernel dev, but an educated guess would point to that imo
Click to expand...
Click to collapse
No mods.. well let me rephrase that. I have a bunch of programs running naturally, but the only "mod" I have is Cataclysm and systemless root along with Elemental X kernel. Cataclysm is considered a mod these days as it's just an overlay on stock 6.01. I know I'd have to go full stock to test for a few days but I'm so so trying to avoid that as I'm sure you know. Thanks for all the input guys, I know this can't just be me right? Hey wait a sec.. I do have a BT smart band unlock running. I'm going to take that off and see if that makes a difference. Maybe that is interfering with the fingerprint requirement.
Edit..nope not it. Gonna run stock kernel next.
The exact same thing is happening to me. Same symptoms but I am on fully stock. I'm also using nova pro. Been searching around for an answer but haven't found anything.
tofuwrice said:
The exact same thing is happening to me. Same symptoms but I am on fully stock. I'm also using nova pro. Been searching around for an answer but haven't found anything.
Click to expand...
Click to collapse
Too many people on Nova Pro for it to be an undocumented issue. I know it's been said that it is not the kernel, however, yesterday morning I flashed this one http://forum.xda-developers.com/nexus-5x/orig-development/jolla-kernelbullhead-t3271530 and I've not had the issue since. I usually have it at least once / day and none so far. That doesn't mean it's not going to happen in 5 minutes though. I went with stock kernel values if you're rooted and feel like giving it a try.
I was having this issue randomly when running custom hotplugging. Currently no issues with default cpu hotplug settings and ElementalX.
For me I have a case on my 5x. There are two cutouts - one for fingerprint sensor and one for camera. They're both about the same size. Every once in awhile I find myself reaching for the camera instead of the fingerprint sensor. When I first got the phone I thought my fingerprint wasn't working at times. Turns out I was just putting my finger on the camera instead of the fingerprint sensor. Any chance this is what's going on?
jgummeson said:
For me I have a case on my 5x. There are two cutouts - one for fingerprint sensor and one for camera. They're both about the same size. Every once in awhile I find myself reaching for the camera instead of the fingerprint sensor. When I first got the phone I thought my fingerprint wasn't working at times. Turns out I was just putting my finger on the camera instead of the fingerprint sensor. Any chance this is what's going on?
Click to expand...
Click to collapse
Don't make me question my own sanity! hehe. I did the same thing at the outset but quickly realized my error. This is not what happens here, however. I even put it back in my pocket once to make sure it wasn't some aberration. It just wouldn't recognize there was even a finger there. Almost thought the phone had shut down but power button got it working again. Haven't had the issue in well over a day now with this kernel but I'm not sure that's what it is.
bobby janow said:
Don't make me question my own sanity! hehe. I did the same thing at the outset but quickly realized my error. This is not what happens here, however. I even put it back in my pocket once to make sure it wasn't some aberration. It just wouldn't recognize there was even a finger there. Almost thought the phone had shut down but power button got it working again. Haven't had the issue in well over a day now with this kernel but I'm not sure that's what it is.
Click to expand...
Click to collapse
This has happened to me twice. Both times while charging. Has not happened any other time. (stock everything/not rooted)
morenoa48 said:
This has happened to me twice. Both times while charging. Has not happened any other time. (stock everything/not rooted)
Click to expand...
Click to collapse
Happened to me not charging, rooted with custom kernel. So it's across the board hit or miss. I have a feeling it will be fixed in an update or OTA. Not a deal breaker just odd is all. Oh well, if we didn't have a power button it would be major.
After 3 years of usage my Nexus 5X fingerprint scanner stopped working at all and i can't do anything about it apparently. The issues started when i sent the phone to LG to fix the bootloop
PROBLEM
After flashing to AOSP 6 I have problems with waking the screen up.
1. After or during the call
2. After longer sleep
It can take up to a minute to wake up. Usualy around 10-20 seconds after multiple presses (single press can sometimes doesn't wake the phone).
NO PROBLEMS WHEN:
1. I manualy sleep the screen, and press power again after a moment - I can bring it to a wake up state without any problems.
2. If the phone is connected through USB - there is also no problem to instantly bring the wakeup screen.
3. There is also no problem to bring the wakeup screen with adb
Code:
adb shell input keyevent 26
I was expecting it to be some sort of sensor problem, as it persists to other roms, even coming back to 5.1.1 which previously worked flawlessly in this department.
I've tried this: http://forum.xda-developers.com/opt...mpting-to-fix-broken-sensors-mm-e975-t3297566 without any results. I've also tried restoring factory settings.
Any ideas?
ZPZG said:
PROBLEM
I was expecting it to be some sort of sensor problem, as it persists to other roms, even coming back to 5.1.1 which previously worked flawlessly in this department.
Click to expand...
Click to collapse
What does CPU-Z think of your sensor data? it's being represented correctly?
blackbird5308 said:
What does CPU-Z think of your sensor data? it's being represented correctly?
Click to expand...
Click to collapse
The sensor as far as I know is binary, so either something is in proximity or not, and as that it works correctly under any system.
After reverting to stock 4.4.2 the problem does not appear.
Installing AOSP 6 again - the problem returns.
ZPZG said:
The sensor as far as I know is binary, so either something is in proximity or not, and as that it works correctly under any system.
After reverting to stock 4.4.2 the problem does not appear.
Installing AOSP 6 again - the problem returns.
Click to expand...
Click to collapse
well, i don't really know, my proximity sensor has been working well since first time i went 6.0 AOSP, even when no other sensor was working at all
blackbird5308 said:
well, i don't really know, my proximity sensor has been working well since first time i went 6.0 AOSP, even when no other sensor was working at all
Click to expand...
Click to collapse
Honestly I don't know what is the problem, but in every thread concerning wakup issues and E975 the sensors are blamed. The physical sensor is working properly as I am not having any problems running stock 4.4.2.
Out of random, usually when I take it out of my pocket, my OnePlus 3 (Soft Gold) doesn't register that my finger is touching the fingerprint scanner. It doesn't vibrate or anything. It's quite random and dont know why it's doing it. When it doesn't do it, it works perfectly fine. Fast as ever! Has anyone else experienced this issue with their OP3?
connorhiller said:
Out of random, usually when I take it out of my pocket, my OnePlus 3 (Soft Gold) doesn't register that my finger is touching the fingerprint scanner. It doesn't vibrate or anything. It's quite random and dont know why it's doing it. When it doesn't do it, it works perfectly fine. Fast as ever! Has anyone else experienced this issue with their OP3?
Click to expand...
Click to collapse
And I would say it does it only 5% of the time.
When the proximity sensor is triggered, opt goes into pocket mode which disables the fps. Check if you are covering the proximity sensor
Sent from my OnePlus 3 using XDA Labs
connorhiller said:
And I would say it does it only 5% of the time.
Click to expand...
Click to collapse
Hi Connor,
i'm experiencing the same issue but it seems to be more like 20 percent of the time, depending on how long I keep it pressed there. Did you figure out what was wrong?
-Bob
The same exact things also happen with my OP3 A3000 Soft Gold, sometimes when I put it in the pocket for a long time (probably around 20-45 minutes), it doesn't instantly recognize my fingerprint anymore.
But it only happened on random occasions and not so often, so I don't' really mind it. My workaround for this is just pressing the power button to light up the screen and put my finger on the fingerprint scanner and it will be unlocked as usual.
BTW, I'm on OOS 4.0.2 and Franco R10 kernel.
Happens to me too, but rarely. When the phone is left untouched for a long time. I have the graphite one.
geekmax said:
Happens to me too, but rarely. When the phone is left untouched for a long time. I have the graphite one.
Click to expand...
Click to collapse
This can be due to the doze which deactivate the sensor and hence makes it slow or unresponsive
Sent from my OnePlus3 using XDA Labs
Prattham said:
This can be due to the doze which deactivate the sensor and hence makes it slow or unresponsive
Click to expand...
Click to collapse
Doze is supposed to leave the sensors alone , right ?
geekmax said:
Doze is supposed to leave the sensors alone , right ?
Click to expand...
Click to collapse
Well there are two doze
Normal and advanced
You will be familiar if you have used apps like naptime force doze etc
Sent from my OnePlus3 using XDA Labs
I too have the same model but it hasn't happened with me ever.
I would suggest you to record several fingerprints of the same finger...
But if the problem persists try factory reset:good:
Actually, I have the same issue. I guess I swipe my finger too quickly sometimes
Ever since i flashed new 11.15. firmware, my home button is acting weird. I can hardly register fp at any rom and when i try to unlock it never succeeds in first try, it vibrates by itself like i'm touching it even tho im not and somethimes phone unlocks itself (with pin + fp) with me touching either usb c bottom part (clearly not touching fp sensor) or not touching it at all...Could this be hardware or software prob...I tried flashing number of different firmwares and roms and no luck, idk what to do...
Same happened to my phone. It's software related, obviously, but maybe our fp sensor is now gone.
Happened once ,just open the back cover and clear the flexi port area gently, use soft material (toothbrush) ,re-connect tye flexible port,try if this work for me hope its also fix your problems.
SH1M4BD3 said:
Happened once ,just open the back cover and clear the flexi port area gently, use soft material (toothbrush) ,re-connect tye flexible port,try if this work for me hope its also fix your problems.
Click to expand...
Click to collapse
You mean I should unscrew it? I'm afraid I'll scratch it or worse
KrecimStanove said:
You mean I should unscrew it? I'm afraid I'll scratch it or worse
Click to expand...
Click to collapse
Yup remove the back cover..thats the only option to reach the port, just see youtube videos on how-to do that
KrecimStanove said:
You mean I should unscrew it? I'm afraid I'll scratch it or worse
Click to expand...
Click to collapse
Happened to me once. I fix it with downgrading firmware to 7.0, reboot to system then boot TWRP and install 11.15 Oreo firmware.
UPDATE : After reinstalling some different roms (8.0, 9.0 etc.) and flashing different firmwares, now I get no response from fp sensor (when i try to set fp unlock), else, homebutton works great and doesn't vibrate on its own although i can't use fp unlock... Some advice?
KrecimStanove said:
UPDATE : After reinstalling some different roms (8.0, 9.0 etc.) and flashing different firmwares, now I get no response from fp sensor (when i try to set fp unlock), else, homebutton works great and doesn't vibrate on its own although i can't use fp unlock... Some advice?
Click to expand...
Click to collapse
+1
i recently tested custom roms... and rooted my p6p but somehow the fingerprint reader doesb't sense my finger when it's in lockscreen and only work after i wake the phone up... anyone has ideas what's causing it?
Restarting your device can fix some minor issues like unstable Wi-Fi, a frozen program, or a faulty fingerprint sensor. So the best solution for your fingerprint sensor might be to reset it.
jack lamters said:
Restarting your device can fix some minor issues like unstable Wi-Fi, a frozen program, or a faulty fingerprint sensor. So the best solution for your fingerprint sensor might be to reset it.
Click to expand...
Click to collapse
by resetting, you mean restarting my device? i tried... but still giving me issue,,,
godlyitem said:
i recently tested custom roms... and rooted my p6p but somehow the fingerprint reader doesb't sense my finger when it's in lockscreen and only work after i wake the phone up... anyone has ideas what's causing it?
Click to expand...
Click to collapse
Since you are running a custom ROM, the best person to ask is the creator of that ROM. See if maybe other people running the ROM have the same issue. Since you are not running Stock and haven't even mentioned which ROM you use, it's hard to help you here in any way.
godlyitem said:
i recently tested custom roms... and rooted my p6p but somehow the fingerprint reader doesb't sense my finger when it's in lockscreen and only work after i wake the phone up... anyone has ideas what's causing it?
Click to expand...
Click to collapse
I am not running custom rom but that fingerprint reader problem is on mine too and its sporadic. The reader would work fine after a reset/flash, days later it would bug out. I have to tap once or lift the phone to activate the screen for the reader to work. Rebooting the phone a few times would get it to work again but its random.
I've noticed on AOD the fingerprint reader doesn't respond while in a smartlock area and i have to press power to get to lockscreen then fpr works (or it shows me unlocked by smartlock depending if it's been 4 hours) . Can others confirm/rebut that theirs only does this in smartlock zones and not in the wild (or if you bt smartlock whether or not being connected causes this)
so i rooted and went back to stock OS. It didn't work in AOD. After several reboots, it started to work again..... this is crazy
godlyitem said:
so i rooted and went back to stock OS. It didn't work in AOD. After several reboots, it started to work again..... this is crazy
Click to expand...
Click to collapse
Yeah, its a crapshoot if it will remain working the next time you restart.