piggz
commented
4 years ago Can you get logcat logs too please..anything to do with your fp hal
Open 0312birdzhang opened 4 years ago
piggz
commented
4 years ago Can you get logcat logs too please..anything to do with your fp hal
rinigus
commented
4 years ago I presume it will be the same result if you check with the -test app https://github.com/piggz/sailfish-fpd-community-test . But maybe you could try that and see if it works via that - enroll fingers via it and check if it works after reboot
0312birdzhang
commented
4 years ago Can you get logcat logs too please..anything to do with your fp hal
0312birdzhang
commented
4 years ago I presume it will be the same result if you check with the
-testapp https://github.com/piggz/sailfish-fpd-community-test . But maybe you could try that and see if it works via that - enroll fingers via it and check if it works after reboot
Yeah, same result.
Kabouik
commented
4 years ago I have the same issue on Pro¹ too, fingerprints are lost after reboot, but unlike @0312birdzhang unlocking with fingerprint does not work, so it might be best if I post my logs in a different issue to keep things tidy.
Kabouik
commented
4 years ago Can you try to reboot in bootloader mode and run ./fastboot erase persist? This worked for me (no data loss to expect).
Kabouik
commented
4 years ago Okay, do not do the above. While it did fix my issues with sailfish-fpd-community, it broke other things, including all sensors, which in turn broke cameras and video applications. I had to reflash the persist partition to fix it, and fortunately the filesystem was in the image file; else I was probably screwed since fastboot format doesn't work on raw partitions. I'm posting a new message instead of editing the previous message just in case someone would just read email notifications and run the command.
However, since persist is mounted in /mnt/vendor/persist, the files that cause the issue with sailfis-fpd-community can probably be removed selectively instead of erasing the whole partition.
calebccff
commented
4 years ago I had a very similar issue on OnePlus 6, sailfish 3.3.0.16.
Fingerprint records still show up in settings after reboot but the sensor is unresponsive, opening the fingerprint test in CSD tool fails the first time but works the seconds time, at which point the fingerprint records are lost from settings. Fingers that were already added can't be added again, but adding a different one then allows all fingers that were previously registered to work as well.
piggz
commented
4 years ago The official fpd support has the following known quirks https://github.com/mer-hybris/droid-config-sony-ganges-pie/blob/master/sparse/etc/sailfish-fpd/50-settings-ganges.ini
It may be that we need to implement some of these for certain devices. More than happy to accept PRs if people can work out what the quirks do, some are obvious from the name.
former-n900user
commented
4 years ago Hello I also have had those fingerprint problems.
History.
I support the proposal to mention that in the readme file, including a link to the persist.img file.
An additional question just to understand. Where does the persist.img file came from? I thought the vendor.img file contains the persist data. But obviously this isnt the case.
calebccff
commented
4 years ago @former-n900user from what I can tell persist contains important configuration data, like how all of the sensors are connected to your device, and perhaps camera calibration data etc.
It's working well before reboot, but after reboot there is no fingerprint record in Settings.
Logs after reboot, enter password, readd fingerprint and unlock
``` [root@Redmi5Plus nemo]# systemctl status sailfish-fpd-community.service ● sailfish-fpd-community.service - Community Fingerprint Daemon Loaded: loaded (/lib/systemd/system/sailfish-fpd-community.service; disabled; vendor preset: enabled) Active: active (running) since Tue 2020-04-21 22:00:42 EEST; 18s ago Process: 3149 ExecStartPre=/bin/sh -c /usr/bin/test -f /run/systemd/boot-status/init-done || sleep 5 || : (code=exited, status=0/SUCCESS) Main PID: 5237 (sailfish-fpd-co) CGroup: /system.slice/sailfish-fpd-community.service └─5237 /usr/bin/sailfish-fpd-community Apr 21 22:00:42 Redmi5Plus sailfish-fpd-community[5237]: void FPDCommunity::loadFingers() Apr 21 22:00:42 Redmi5Plus sailfish-fpd-community[5237]: QList