tdm 2,322 Posted August 4, 2020 Author Share Posted August 4, 2020 5 hours ago, DieBruine said: @tdm Did you add the rm /persist/data/fingerprint tot the new nightly? I ask because I'm having the same issues with my fingerprints being forgotten. I tried rm /persist/data/fingerprint via ADB. Permission denied is what I got. So just to be sure I sideloaded SU-arm64 and searched for /persist/data/fingerprint.... Nowhere to be found. Which is why I'm hoping you added your script. Otherwise I have no idea what's happening here. I will add my fingerprints and reboot again, see what happens. After a reboot my fingerprints are gone again. Unable to find nor delete /persist/data/fingerprint. Yessir, I certainly did. But I don't think it does what you expect. I have no way to correlate the system fingerprints with the vendor fingerprints. All the script does is check if the system data has been wiped. If so, it wipes the persist data. Note that removing all fingerprints does not (currently) count -- the script only checks for the presence of the system fingerprint file, not that it is empty. But you still have the issue of the vendor HAL never deleting fingerprints. So, if you enroll more than ten fingerprints without deleting the persist data, you will always run into this issue. There is one improvement that I can think to make: I could add a check to see if the system fingerprint file is empty and delete the persist data in that case. That would allow the persist data to be deleted without a data wipe. But really, how many people enroll more than ten fingerprints? And how many of those are not aware of this issue enough to erase the persist data themselves? 1 Quote Link to post Share on other sites
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.