My update failed. So I re-flashed to the 4.3.x version from the download site, then updated to 4.4.0.58.
So this is a new install.
But update from 4.3 - I bet that’s the issue…
Become root, then can you share the file fpd-log.txt?
journalctl -u sailfish-fpd > /home/defaultuser/Documents/fpd-log.txt
I had the exact same problem with a fresh install of 4.4.0.58 on my single sim X. Tried twice, the same problem in both occasions. Solved by flashing 4.3.15 and then upgraded (via sfos_upgrade tool from openrepos) to 4.4.0.58.
2 Likes
Forgotten the CSD tool: it fails for FP sensor
( 4.4 flashed, no upgrade - upgrade from 4.2 to 4.3 was unusable)
Launching sailfish-fpd as root gives
#sailfish-fpd -v
[gbinder] ERROR: Can't open /dev/hwbinder: No such file or directory
Thanks for the bug report. All additional comments, logs etc. are very welcome in order to debug this further.
XA2 4.4 flashed.
I had 1 fingerprint recorded since days (some reboots for diverse reasons) and all was ok.
I tried to add a new one but it repeatedly failed.
After the 12 to 14th finger press, recording stopped saying it was not possible (I don’t remember text exactly alas).
journalctl -u sailfish-fpd
gave:
Apr 04 17:53:58 XperiaXA2-DualSIM fpslave[4284]: fpdevice_gatekeeper_verify: gatekeeper verify returned something which doesn’t look like an hw_auth_token_t
Apr 04 17:54:05 XperiaXA2-DualSIM sailfish-fpd[4280]: mrcontrol_set_fperror: error: FPERROR_NONE → FPERROR_UNABLE_TO_PROCESS
Apr 04 17:54:08 XperiaXA2-DualSIM sailfish-fpd[4280]: mrcontrol_fphal_timeout_cb: fp hal is stuck; terminating
Apr 04 17:54:08 XperiaXA2-DualSIM fpslave[4284]: fpcontrol_master_rd_cb: unexpected master wakeup: condition=0x10
Apr 04 17:54:08 XperiaXA2-DualSIM sailfish-fpd[4280]: *** SLAVE TERMINATE
Apr 04 17:54:08 XperiaXA2-DualSIM fpslave[4284]: fpcontrol_master_rd_cb: disabling master io watch
Apr 04 17:54:08 XperiaXA2-DualSIM sailfish-fpd[4280]: main: sailfish-fpd terminating with exit value 1
Apr 04 17:54:08 XperiaXA2-DualSIM systemd[1]: sailfish-fpd.service: Main process exited, code=exited, status=1/FAILURE
Apr 04 17:54:08 XperiaXA2-DualSIM systemd[1]: sailfish-fpd.service: Failed with result ‘exit-code’.
Apr 04 17:54:09 XperiaXA2-DualSIM systemd[1]: sailfish-fpd.service: Service hold-off time over, scheduling restart.
Apr 04 17:54:09 XperiaXA2-DualSIM systemd[1]: sailfish-fpd.service: Scheduled restart job, restart counter is at 1.
Apr 04 17:54:09 XperiaXA2-DualSIM systemd[1]: Stopped Fingerprint Daemon.
Apr 04 17:54:09 XperiaXA2-DualSIM systemd[1]: Starting Fingerprint Daemon…
Apr 04 17:54:09 XperiaXA2-DualSIM systemd[1]: Started Fingerprint Daemon.
Apr 04 17:54:09 XperiaXA2-DualSIM fpslave[20335]: fpsettings_scan_directory: /usr/lib/sailfish-fpd: can’t open directory: No such file or directory
Apr 04 17:54:10 XperiaXA2-DualSIM fpslave[20335]: fpdevice_gatekeeper_verify: gatekeeper verify returned something which doesn’t look like an hw_auth_token_t
Apr 04 17:54:22 XperiaXA2-DualSIM sailfish-fpd[20332]: mrcontrol_set_fperror: error: FPERROR_NONE → FPERROR_UNABLE_TO_PROCESS
Apr 04 17:54:25 XperiaXA2-DualSIM sailfish-fpd[20332]: mrcontrol_fphal_timeout_cb: fp hal is stuck; terminating
Apr 04 17:54:25 XperiaXA2-DualSIM fpslave[20335]: fpcontrol_master_rd_cb: unexpected master wakeup: condition=0x10
Apr 04 17:54:25 XperiaXA2-DualSIM sailfish-fpd[20332]: *** SLAVE TERMINATE
Apr 04 17:54:25 XperiaXA2-DualSIM fpslave[20335]: fpcontrol_master_rd_cb: disabling master io watch
Apr 04 17:54:25 XperiaXA2-DualSIM sailfish-fpd[20332]: main: sailfish-fpd terminating with exit value 1
Apr 04 17:54:25 XperiaXA2-DualSIM systemd[1]: sailfish-fpd.service: Main process exited, code=exited, status=1/FAILURE
Apr 04 17:54:25 XperiaXA2-DualSIM systemd[1]: sailfish-fpd.service: Failed with result ‘exit-code’.
Apr 04 17:54:26 XperiaXA2-DualSIM systemd[1]: sailfish-fpd.service: Service hold-off time over, scheduling restart.
Apr 04 17:54:26 XperiaXA2-DualSIM systemd[1]: sailfish-fpd.service: Scheduled restart job, restart counter is at 2.
Apr 04 17:54:26 XperiaXA2-DualSIM systemd[1]: Stopped Fingerprint Daemon.
Apr 04 17:54:26 XperiaXA2-DualSIM systemd[1]: Starting Fingerprint Daemon…
Apr 04 17:54:26 XperiaXA2-DualSIM systemd[1]: Started Fingerprint Daemon.
Apr 04 17:54:26 XperiaXA2-DualSIM fpslave[20479]: fpsettings_scan_directory: /usr/lib/sailfish-fpd: can’t open directory: No such file or directory
Apr 04 17:54:31 XperiaXA2-DualSIM fpslave[20479]: fpdevice_gatekeeper_verify: gatekeeper verify returned something which doesn’t look like an hw_auth_token_t
Apr 04 17:54:40 XperiaXA2-DualSIM sailfish-fpd[20476]: mrcontrol_set_fperror: error: FPERROR_NONE → FPERROR_UNABLE_TO_PROCESS
Apr 04 17:54:43 XperiaXA2-DualSIM sailfish-fpd[20476]: mrcontrol_fphal_timeout_cb: fp hal is stuck; terminating
Apr 04 17:54:43 XperiaXA2-DualSIM sailfish-fpd[20476]: *** SLAVE TERMINATE
Apr 04 17:54:43 XperiaXA2-DualSIM sailfish-fpd[20476]: main: sailfish-fpd terminating with exit value 1
Apr 04 17:54:43 XperiaXA2-DualSIM systemd[1]: sailfish-fpd.service: Main process exited, code=exited, status=1/FAILURE
Apr 04 17:54:43 XperiaXA2-DualSIM systemd[1]: sailfish-fpd.service: Failed with result ‘exit-code’.
Apr 04 17:54:44 XperiaXA2-DualSIM systemd[1]: sailfish-fpd.service: Service hold-off time over, scheduling restart.
Apr 04 17:54:44 XperiaXA2-DualSIM systemd[1]: sailfish-fpd.service: Scheduled restart job, restart counter is at 3.
Apr 04 17:54:44 XperiaXA2-DualSIM systemd[1]: Stopped Fingerprint Daemon.
Apr 04 17:54:44 XperiaXA2-DualSIM systemd[1]: Starting Fingerprint Daemon…
Apr 04 17:54:44 XperiaXA2-DualSIM systemd[1]: Started Fingerprint Daemon.
Apr 04 17:54:44 XperiaXA2-DualSIM fpslave[20693]: fpsettings_scan_directory: /usr/lib/sailfish-fpd: can’t open directory: No such file or directory
Apr 04 17:54:48 XperiaXA2-DualSIM fpslave[20693]: fpdevice_gatekeeper_verify: gatekeeper verify returned something which doesn’t look like an hw_auth_token_t
Apr 04 17:54:57 XperiaXA2-DualSIM sailfish-fpd[20686]: mrcontrol_set_fperror: error: FPERROR_NONE → FPERROR_UNABLE_TO_PROCESS
Apr 04 17:55:00 XperiaXA2-DualSIM sailfish-fpd[20686]: mrcontrol_fphal_timeout_cb: fp hal is stuck; terminating
Apr 04 17:55:00 XperiaXA2-DualSIM fpslave[20693]: fpcontrol_master_rd_cb: unexpected master wakeup: condition=0x10
Apr 04 17:55:00 XperiaXA2-DualSIM sailfish-fpd[20686]: *** SLAVE TERMINATE
Then (as root) I did a:
systemctl stop sailfish-fpd
/usr/libexec/sailfish-fpd/fpslave --remove-all
/usr/libexec/sailfish-fpd/fpslave --flush-cache
systemctl start sailfish-fpd
and
ln -s /usr/libexec/sailfish-fpd /usr/lib/sailfish-fpd
Then everythink was ok.
Then, I removed the link, just to see what happens:
rm -f /usr/lib/sailfish-fpd
And, very odd, I had no complaints of a missing /usr/lib/sailfish-fpd directoy, even after a reboot.
??? 
Now, I can record as much fp I want and journalctl -u sailfish-fpd does not show anything anymore.
1 Like
In my case /dev/hwbinder is missing. As a result sailfish-fpd fails to start.
# /usr/libexec/sailfish-fpd/fpslave
produces the same result:
[gbinder] ERROR: Can't open /dev/hwbinder: No such file or directory
I don’t know who was supposed to create the hwbinder device - it doesn’t exist in /dev.
Does it make sense to attempt force-reinstalling sailfish-fpd?
My two pence: I experienced recently several Xperia X crashes with bricked phone, so I had to re-flash it several times, using various methods including factory reset. EVERY time I flashed it WITH device encryption, I could not add any fingerprint. So I restarted from an old encryption-free SFOS release (nuuksio), the only known way to avoid device encryption.
Does anyone know what is /dev/hwbinder, what module backs it?
i have the same problem on 4.4.0.58 the FP is not working. Also the /dev/hwbinder is missing. Any idea how to solve it without flashing completely the phone?
I added a fingerprint to my X last night running 4.4.0.58 and it worked fine.
My $0.02
Also on my 2 devices (freshly installed 4.4.0.58) i cannot use finderprint and get the erorr /dev/hwbinder is missing.
does anyone know a workaround or solution?
is anyone within Sailfish team working on this ?
I had the very same error on 4.4.0.72.
According to this thread it could be solved by reinstalling the sailfish-fpd slave:
devel-su
systemctl stop sailfish-fpd.service
pkcon refresh
pkcon install sailfish-fpd-slave-f5121
exit
reboot
And indeed, the fingerprint reader is now working properly. 
There is still no /dev/hwbinder device, but the service doesn’t complain about it.
[root@sxx defaultuser]# systemctl status sailfish-fpd
● sailfish-fpd.service - Fingerprint Daemon
Loaded: loaded (/usr/lib/systemd/system/sailfish-fpd.service; disabled; vendor preset: enabled)
Active: active (running) since Fri 2022-10-07 20:48:56 CEST; 5s ago
Process: 5308 ExecStartPre=/bin/sh -c /usr/bin/test -f /run/systemd/boot-status/init-done || sleep 5 || : (code=exited, status=0/S
UCCESS)
Main PID: 5312 (sailfish-fpd)
Memory: 1.4M
CGroup: /system.slice/sailfish-fpd.service
├─5312 /usr/bin/sailfish-fpd --systemd
└─5314 /usr/libexec/sailfish-fpd/fpslave --log-to=syslog --log-level=4Oct 07 20:48:55 sxx systemd[1]: Starting Fingerprint Daemon…
Oct 07 20:48:56 sxx systemd[1]: Started Fingerprint Daemon.
Oct 07 20:48:56 sxx sailfish-fpd[5312]: mrcontrol_set_active_user_cb: delayed change to user 100000
Oct 07 20:48:56 sxx fpslave[5314]: fpenumerate_enter: QUIRK: skipping index validation
[root@sxx defaultuser]#
2 Likes
Reinstalled the fingerprint service with zypper and all is well 
Thx, tice_rex!
thanks, that worked
The next 4.6.0 update (after 4.6.0.13) will have a fix for this.
2 Likes
It is fixed in 4.6.0.15.