Database Users

Fingerprint misbehaviour

Hi,
I've recently updated my N910F to Marshmallow (official). It's not the latest version but I wasn't able to download that one yet.
I made a fresh install with it (factory reset via TWRP, flashed it through ODIN, rooted via CF Autoroot, installed TWRP 3.0.2-0 and XPosed v84, restored Apps trough Titanium) and even reflashed it with a wipe of system, cache and dalvik cache before because of problems with auto rotate.
But the Fingerprint API or something like that seems to be not working how it should. I can't set screen lock to Fingerprint (I get asked "Enter a backup password.", wenn I enter one, it just says "Sorry, try again" without saying why it failed), even after going to security settings and deleting the credeintially, which fixed such problems on 5.1.1 it doesn't work.
I also had read, that you could use your Fingerprint for authentication in PlayStore, but at least in version 6.7.12.E I can't see that option.
PlayStore should use the API of Nexus Imprint for that and I thought that this is required by any OEM that want's to get a license for M, so I don't really see why it doesn't show up.
The sensor itself seems to be working, I was able to register my fingers and with FingerLock, an app locker designed for Samsungs proprietary Fingerprint API form earlier versions, I also have no problems.
I think, Samsungs own implementation is working (accept for Lock screen but they´could have changed it here for the official one), only apps for Googles standardized one are failing. But I can't really prove it. An app, that should be using the official API in M is failing, but the developer says it's a problem only with the Note 4 and he hopes he can publish a fix later this month.
The app locker MaxLock, which I thought would use fingerprint authentication with the official API doesn't show up an option for that but maybe through problems with the implementation.
Is there any way to test what's going wrong?
PS: sorry for the long text

I now have this..... Any solution?

Get a (non-TW based) custom ROM. It's the only thing that's works since Samsung most have screwed up the whole API. Their own is only useable partially and the standard one by Marshmallow is completely messed up and not worrying at all.
I was so pissed off of Samsung's incompetence that I switched to emotion ROM. It's a bit tricky to set up the fingerprint reader, but once it's done, everything using the official API is writing flawlessly. Never gonna switch back.

Can't disable lock screen pin in Marshmallow

Before the noob alarm goes off I've already attempted disable credentials multiple times, disabled all adminstration, and I have never used any encryption on my phone.
The issue occurred after I updated from lollipop to marshmallow.
I am using he heavily skinned EMUI 4.0 on the huawei P8 lite, could this be the issue?
Thanks in advance

Galaxy S7 FingerPrint error after update.

So i have recently updated my phone to the latest 7.0 software on my galaxy s7. ever since the update, my fingerprint scanner doesn't work. When i go into the system settings to try and setup new fingerprints it gives me the error "An error has occurred with the fingerprint sensor. If this message appears repeatedly, restart your device." I tried restarting the device, clearing the app's cache and data, as well as clearing the system cache in the boot menu. When i go into the FingerPrint test under the HwModuleTest(*#0*#) and perform a normal scan, everything comes back as failed. Is my only option to backup my phone and do a complete reinstall?

sandman817 said:
So i have recently updated my phone to the latest 7.0 software on my galaxy s7. ever since the update, my fingerprint scanner doesn't work. When i go into the system settings to try and setup new fingerprints it gives me the error "An error has occurred with the fingerprint sensor. If this message appears repeatedly, restart your device." I tried restarting the device, clearing the app's cache and data, as well as clearing the system cache in the boot menu. When i go into the FingerPrint test under the HwModuleTest(*#0*#) and perform a normal scan, everything comes back as failed. Is my only option to backup my phone and do a complete reinstall?
Click to expand...
Click to collapse
Try completely reinstalling QA6. I highly doubt the update caused the fingerprint scanner to start working though since it works perfectly fine on my phone.

VenomMOD said:
Try completely reinstalling QA6. I highly doubt the update caused the fingerprint scanner to start working though since it works perfectly fine on my phone.
Click to expand...
Click to collapse
How do i go about reinstalling the latest android version on my phone?

sandman817 said:
How do i go about reinstalling the latest android version on my phone?
Click to expand...
Click to collapse
Flash PK1 with Odin and take the ota again. When the ota is done, factory reset the phone to make sure any software issues are gone.

Should I be using smart switch to backup my contacts/messages/etc to my computer?

I recently updated my phone and am having the same problem. Have you found a solution for you that worked (I also tried wiping my cache partition and a soft reset)

aizq29 said:
I recently updated my phone and am having the same problem. Have you found a solution for you that worked (I also tried wiping my cache partition and a soft reset)
Click to expand...
Click to collapse
I also just updated my SM-G935FD via OTA to Android version 7.0.
Since then, fingerprint scanner is not working. Like for OP, all tests fail under HwModuleTest.
I tried to remove all fingerprints, but it is impossible to add new fingerprints - the error message is "Make sure that the Home key is clean and dry, then try again." Obviously, the fingerprint sensor is as dry and clean as it was before the update (when it worked perfectly).
Since then I tried, unsuccessfully:
- removing old fingerprints and adding new fingerprints (does not work, cf. above)
- formatting cache partition
- performing a hardware reset
Please advice, thanks.
P.S. I do not have access to Odin, since I do not have a Microsoft OS.

I had constant issues with the ATT firmware's fingerprint reader performance (6.x) -- wouldn't recognize my fingerprint when I tried to unlock and would often get the forced timeout.
It works flawlessly for me on the u firmware (still 6.x unfortunately). Night and day.

Same issue with me here in the UK. Just did the Nougat OTA update, having no end of issues, including the "dry home button" stuff with the fingerprint scanner. Also, the stock browser seems to have lost it's secret / incognito mode.... why can't they just leave stuff alone? Seems like my only option at this point is to downgrade back to marshmallow and put up with the annoying update notification.

Same here what do we have to do ?

Wildarmtins said:
Same issue with me here in the UK. Just did the Nougat OTA update, having no end of issues, including the "dry home button" stuff with the fingerprint scanner. Also, the stock browser seems to have lost it's secret / incognito mode.... why can't they just leave stuff alone? Seems like my only option at this point is to downgrade back to marshmallow and put up with the annoying update notification.
Click to expand...
Click to collapse
Downgrade doesn't help

https://forum.xda-developers.com/tm...t-s7-edge-g935t-t3567502/page120#post72332585
CHECK OUT MY POSTS BETWEEN PAGES 116 AND 120.

Has anyone had, conversely, an *overactive* fingerprint sensor?
While the phone is unlocked, at times when my finger is only resting on the scanner, I'm taken to the accessibility settings with an alert asking "Grant Permission: Please, grant permission to allow this feature".

No fingerprint auth in Google Play

I have no fingerprint auth option in Google Play. Also in my banking app, that specific option doesn't show up.
It worked fine in the past, I'm literally out of ideas what could've caused it to disappear... It used to work back when I was using SuperSU and SafetyNet wasn't passing for me, then it still worked when I moved to Magisk then after some time it just disappeared.
Fingerprint sensor is working, already tried removing all fingerprints and pattern locks (then rebooting) and re-adding them, tried also a method with removing few specific files from data (that remove any locks and saved patterns/fingerprints) partition from within TWRP - still no luck. However when I uninstall updates of Google Play the option is back up, but once the store updates it disappears again...
Redmi 3S with latest xiaomi.eu 7.9.21 + Magisk, SafetyNet passes, Google Play certified.

kwski43 said:
I have no fingerprint auth option in Google Play. Also in my banking app, that specific option doesn't show up.
It worked fine in the past, I'm literally out of ideas what could've caused it to disappear... It used to work back when I was using SuperSU and SafetyNet wasn't passing for me, then it still worked when I moved to Magisk then after some time it just disappeared.
Fingerprint sensor is working, already tried removing all fingerprints and pattern locks (then rebooting) and re-adding them, tried also a method with removing few specific files from data (that remove any locks and saved patterns/fingerprints) partition from within TWRP - still no luck. However when I uninstall updates of Google Play the option is back up, but once the store updates it disappears again...
Redmi 3S with latest xiaomi.eu 7.9.21 + Magisk, SafetyNet passes, Google Play certified.
Click to expand...
Click to collapse
This might be problem with the rooted ROM
Better flash the stock ROM once again and lock the bootloader

Oneplus 5 with OxygenOS 5.0.1 Use Full Disk Encryption

I have searched all over and I cannot seem to find a working solution to what I am looking for. I want to use full disk encryption with my Oneplus 5. All posts say you can disable encryption totally. I can do that, no problem. I cannot get it to turn on full disk encryption. I do not want file based. Is there any way of doing this with Android Oreo? Did google remove all possibilities?
Does anyone know how to enable full disk encryption on Oreo and the Oneplus 5? This is all stock except root.

Something like this?

So far as I'm aware the phone when in nougat was encrypted, it's only through choice and the obvious data format that decryption had been possible and it's been more of a requirement for newer ROM's.
If it's a ROM you're flashing then just choose encrypted.

maikvitesse said:
Something like this?
Click to expand...
Click to collapse
That worked great for Android 7. That zip no longer works on Android 8. I have found updated zips for 8. I have verified that it changes the fstab file like it should, but upon format and reboot it is either back in FBE or no encryption and fails/does nothing to FDE.
Sent from my OnePlus 5 using XDA Labs

dladz said:
So far as I'm aware the phone when in nougat was encrypted, it's only through choice and the obvious data format that decryption had been possible and it's been more of a requirement for newer ROM's.
If it's a ROM you're flashing then just choose encrypted.
Click to expand...
Click to collapse
Yes, in 7 it was FBE stock. I was able to disable forced encryption (and format data). I than went and turned on FDE. Everything was grand!
Now in 8, I can disable it but it either still has FBE on or all encryption off (does show in settings and allows to attempt to turn on) and not allowing me to turn on FDE.
I am only flashing stock OxygenOS 5.0.1 and Magisk. I just want to turn off encryption and format data and be able to turn on FDE. I do not want any of FBE.
Sent from my OnePlus 5 using XDA Labs

dl200010 said:
Yes, in 7 it was FBE stock. I was able to disable forced encryption (and format data). I than went and turned on FDE. Everything was grand!
Now in 8, I can disable it but it either still has FBE on or all encryption off (does show in settings and allows to attempt to turn on) and not allowing me to turn on FDE.
I am only flashing stock OxygenOS 5.0.1 and Magisk. I just want to turn off encryption and format data and be able to turn on FDE. I do not want any of FBE.
Click to expand...
Click to collapse
I think things have changed since nougat mate. Didn't the beta require decryption ? Might be a knock on effect of that, personally I don't care for encryption, unless every dev is using it as it causes issues between ROM changes.
Is there a reason why you have to have encryption Vs decrypted ??

dladz said:
I think things have changed since nougat mate. Didn't the beta require decryption ? Might be a knock on effect of that, personally I don't care for encryption, unless every dev is using it as it causes issues between ROM changes.
Click to expand...
Click to collapse
I did not install the beta. This is my only phone and I do need it to run right. I know when the Nexus 6P got 8 it could still use FDE. I actually updated from 7 to 8 on the 6P with FDE on. Just had to flash Magisk and let it turn of forced encryption.
I just want to have FDE over FBE.
Sent from my OnePlus 5 using XDA Labs