Hi, I have a fingerprint problem.
Since I installed lineage os I can no longer set up the fingerprint, because when I go into the settings there is no more fingerprint. What should I do to solve this problem?
Roshiz said:
Hi, I have a fingerprint problem.
Since I installed lineage os I can no longer set up the fingerprint, because when I go into the settings there is no more fingerprint. What should I do to solve this problem?
Click to expand...
Click to collapse
Is your phone encrypted?
same problem
i have same problem, phone is encrypted, someone said fingerprint will be available after adding pattern lock, pin lock tried but it doesn't work
Related
I found the smart lock did not work after root, no matter using beta magisk 14.5 or stable 14. I would like to make sure if this is a problem of my own, or a general case, so that I can decide whether to report this to the developers. Thank you.
I'm using beta 14.5 and when I open smart lock it asks for a pin and then shows a blank white screen. No options to add devices. I've been using face unlock so I didn't notice until I checked after seeing this.
Try this.
Oneplus forums
It worked for me.
shadeau said:
I'm using beta 14.5 and when I open smart lock it asks for a pin and then shows a blank white screen. No options to add devices. I've been using face unlock so I didn't notice until I checked after seeing this.
Click to expand...
Click to collapse
Exactly the problem I have, so this should be a problem of magisk. I guess magisk is not compatible with 5t now, some other people report they have problem with their wifi after root (I also found wifi is slower).
I tried supersu as well, but it can cause a battery drain. So there is no perfect root for 5t till now.
Beaster said:
Try this.
Oneplus forums
It worked for me.
Click to expand...
Click to collapse
It will become blank again after reboot... It's perfect if I uninstall magisk or use supersu instead.
simonand said:
It will become blank again after reboot... It's perfect if I uninstall magisk or use supersu instead.
Click to expand...
Click to collapse
I second that, it turns blank again after reboot. or sometime during use. So irritating.
I just found out that Magisk itself doesn't seem to be the problem.
I did a fresh install, installed magisk without any problem. The problem started after installing a module from within Magisk...
After that Smart Lock blanked out and removing the module doesn't change anything.
Bart1981 said:
I just found out that Magisk itself doesn't seem to be the problem.
I did a fresh install, installed magisk without any problem. The problem started after installing a module from within Magisk...
After that Smart Lock blanked out and removing the module doesn't change anything.
Click to expand...
Click to collapse
What module did you install? I seem to get this problem even with out magisk. Maybe twrp is the cause?
tyrone1 said:
What module did you install? I seem to get this problem even with out magisk. Maybe twrp is the cause?
Click to expand...
Click to collapse
I guess I was mistaken... A later attempt I also got a blank screen after a while.
Not shure why. In the beginning it seems all ok also after a couple of reboots, but then after a certain time and a reboot it's there. again.
As the title states lately I have been having fingerprint issues. Setting up fingerprint to unlock my phone works perfectly with the phone itself. When it's comes to apps Chase, Cinemark , TMobile setting up fingerprint verification goes through correctly. Now opening the apps and using my fingerprint to verify does not unlock the app. Apps just keep telling me to put my assigned fingerprint in again. Anyone noticing issues lately? Is there any way to troubleshoot this? I have reflashed the OTA (8.1 Oreo - March update) multiple times- no change.
Running stock 8.1 Oreo March update
Any other suggestions?
LubbocksFall said:
As the title states lately I have been having fingerprint issues. Setting up fingerprint to unlock my phone works perfectly with the phone itself. When it's comes to apps Chase, Cinemark , TMobile setting up fingerprint verification goes through correctly. Now opening the apps and using my fingerprint to verify does not unlock the app. Apps just keep telling me to put my assigned fingerprint in again. Anyone noticing issues lately? Is there any way to troubleshoot this? I have reflashed the OTA (8.1 Oreo - March update) multiple times- no change.
Running stock 8.1 Oreo March update
Any other suggestions?
Click to expand...
Click to collapse
I have not had any issues with apps that rely on / give the option of fingerprint authentication. I also have Chase installed and I just tested it and it works fine. I also have Amex, Bank of America, alarm.com, ADT Pulse and fingerprint access seems to be working fine on all of them. I am also running stock 8.1 Oreo / March update- but I am unlocked and rooted with Magisk. One suggestion based on some Fingerprint related struggles I had recently (when TWRP couldn't decrypt and I had to remove Fingerprint/pattern security during the update process and then add back after updating/rooting)....I found that some apps that had already had Fingerprint access enabled, didn't behave well when Fingerprints were removed then added back on the phone. The best workaround I found in those cases was to uninstall the app completely, fully setup Fingerprint security on the phone, then install the apps again. This definitely was the case with Amex, Chase, and Bank of America. Just something to try...good luck.
So using the OTA multiple times via fastboot wouldn't have cleared the apps?
LubbocksFall said:
So using the OTA multiple times via fastboot wouldn't have cleared the apps?
Click to expand...
Click to collapse
Sideloading or taking the OTA natively doesn't typically wipe app data in my experience. Flashing the factory image (without removing the -w) would wipe your data (and most everything else)...but that creates alot of work in setting up your phone again. I found uninstalling the troublesome apps, setting up fingerprint security/pattern, then reinstalling and setting up the apps relying on fingerprints worked the best for me - but the situations are a bit different as my troubles always were related to adding new fingerprints to the phone and apps that had the "old" fingerprint information already....for me - uninstalling / reinstalling the apps solved my issue.. YMMV
OG Pixel XL 32GB on Project Fi, rooted with Magisk 17.1, previously on Android Pie 9.0.0 August security update.
Just sideloaded to September security update via the usual method. Upon booting, fingerprint sign-in was disabled, and in "Settings," it appeared that my fingerprints had been cleared. Tried enrolling fingerprints via "Pixel Imprint," but while it registers reads properly, enrollment fails at the last step with the message "Enrollment was not completed. Fingerprint enrollment didn't work. Try again or use a different finger." No luck with other fingers. Gestures (notification shade pulldown) still works. Tried flashing back to August update, but same issue persisted.
Anyone else have this issue, or know of a solution? Thanks!
davidrqli said:
OG Pixel XL 32GB on Project Fi, rooted with Magisk 17.1, previously on Android Pie 9.0.0 August security update.
Just sideloaded to September security update via the usual method. Upon booting, fingerprint sign-in was disabled, and in "Settings," it appeared that my fingerprints had been cleared. Tried enrolling fingerprints via "Pixel Imprint," but while it registers reads properly, enrollment fails at the last step with the message "Enrollment was not completed. Fingerprint enrollment didn't work. Try again or use a different finger." No luck with other fingers. Gestures (notification shade pulldown) still works. Tried flashing back to August update, but same issue persisted.
Anyone else have this issue, or know of a solution? Thanks!
Click to expand...
Click to collapse
I didn't not have that issue this upgrade or any others. The only time I have lost Fingerprints is when I have had to disable security when TWRP is unable to decrypt. But that was not the case for September update. You might try disabling security completely. Rebooting. Then reenabling security and Pixel Imprint. Maybe something didn't get cleared all the way when your Pixel Imprint got disabled or partially cleared...
sb1893 said:
I didn't not have that issue this upgrade or any others. The only time I have lost Fingerprints is when I have had to disable security when TWRP is unable to decrypt. But that was not the case for September update. You might try disabling security completely. Rebooting. Then reenabling security and Pixel Imprint. Maybe something didn't get cleared all the way when your Pixel Imprint got disabled or partially cleared...
Click to expand...
Click to collapse
Thanks for the tip. Just tried this and no dice, however. Have never had any issues with any previous updates, including with Oreo when a lot of other people were having fingerprint reader problems.
davidrqli said:
Thanks for the tip. Just tried this and no dice, however. Have never had any issues with any previous updates, including with Oreo when a lot of other people were having fingerprint reader problems.
Click to expand...
Click to collapse
Any progress on this? Were you able to get it working?
sb1893 said:
Any progress on this? Were you able to get it working?
Click to expand...
Click to collapse
Nope, still the exact same. Issues also persist in Safe Mode.
Had this issue with DP4. Had to do a factory reset. Sorry.
jaytv said:
Had this issue with DP4. Had to do a factory reset. Sorry.
Click to expand...
Click to collapse
Gotcha... thanks. Not in a position to do a factory reset now, but maybe in a week or so when I'm back from a trip. Anyone else have any luck fixing this without a factory reset?
Update: Did a full factory reset, which fixed the problem. Not an ideal situation, but at least it worked.
davidrqli said:
Update: Did a full factory reset, which fixed the problem. Not an ideal situation, but at least it worked.
Click to expand...
Click to collapse
Glad you got it sorted. That normally does the trick but it does suck if you don't have everything backed up.
Hello everyone,
I have a problem with my device:
- Samsung Galaxy S7
- rooted
- Magisk 20.4
- Magisk Manager 8.0.3
Everytime when I go to Samsung Pay, PayPal or my banking app (Sparkasse) and give my fingerprint it does not register, stuck or crash.
Unlocking my phone with fingerprint works but not with other applications mentioned above.
I have hidden all these applications in Magisk Hide and enabled the Magisk biometrics authentification but still not working.
Does or did anyone have this problem and also a solution how to register myself with fingerprint in these applications?
Thanks everyone.
Hi, I've got this exact problem, did you ever find a solution?
Sorry to bump an old thread
I'm struggling with the exact same problem, my banking app tells me to go enable it as if I don't have it configured, but I have and I have others apps that are accepting my fingerprint access like outlook and teams. Would be great if someone has a fix for this.
I have the same issues. All Banking Apps crash if i register my fingerprints, Iris or Face.. someone can help solving this issues?
Same issue..not able to register my fingerprint after rooting with magisk..
OnePlus 9 Pro LE2123.
After the Oxygen 11.2.9.9 update, fingerprint does not work.
Does not read the enrolled fingerprint. Reads a new fingerprint, but also does not read it.
I was cleaning the cache, qualcom biosensoric. It didn't help.
I am looking to downgrade to Oxygen 11.2.8.8
Alex_H_H said:
OnePlus 9 Pro LE2123.
After the Oxygen 11.2.9.9 update, fingerprint does not work.
Does not read the enrolled fingerprint. Reads a new fingerprint, but also does not read it.
I was cleaning the cache, qualcom biosensoric. It didn't help.
I am looking to downgrade to Oxygen 11.2.8.8
Click to expand...
Click to collapse
FP is working properly here with 11.2.9.9. Try applying the update once more time
angelmakumbe said:
FP is working properly here with 11.2.9.9. Try applying the update once more time
Click to expand...
Click to collapse
I did a 3x update. Nothing helped.
Alex_H_H said:
OnePlus 9 Pro LE2123.
After the Oxygen 11.2.9.9 update, fingerprint does not work.
Does not read the enrolled fingerprint. Reads a new fingerprint, but also does not read it.
I was cleaning the cache, qualcom biosensoric. It didn't help.
I am looking to downgrade to Oxygen 11.2.8.8
Click to expand...
Click to collapse
You single, mate? just kidding! If you're rooted, try disabling magisk modules and re enable it. If you're not using, kill the service via adb and restart
angelmakumbe said:
FP is working properly here with 11.2.9.9. Try applying the update once more time
Click to expand...
Click to collapse
same here. fp is working like a charm after 11.2.9.9. no problem
PKkeys said:
You single, mate? just kidding! If you're rooted, try disabling magisk modules and re enable it. If you're not using, kill the service via adb and restart
Click to expand...
Click to collapse
Thanks for the hints!
I'm not single I have no root.
The problem occurred yesterday, after update 11.2.9.9
Is your device 100% stock, if not can you list out all the changes you've made.
This is weird, I haven't updated anything on my phone and fingerprint today just stopped working. Deleted all fingerprints, cleared storage on the app to no avail. I can register a fingerprint but on any app, if I try to use it, it says it hasn't been recognised.
PKkeys said:
You single, mate? just kidding! If you're rooted, try disabling magisk modules and re enable it. If you're not using, kill the service via adb and restart
Click to expand...
Click to collapse
Thanks a lot, mate. Your solution helped. LE2123 EU version here.
Well, my joy was premature. Disabling modules helps but enabling them brings the problem back.
[edit]
After removing for good EDS magisk module (part of EDS app from sovworks), everything's been working ok so far. I will keep experimenting as I need EDS in my everyday life.