![]() ![]() I wonder if there's been any changes since then. This means that unless another matching algo is found/implemented, these readers will not work as good with libfprint as they do with vendor drivers. There's just not enough minutiae (recognizable print-specific points) on them for a reliable match. The algorithm which libfprint uses to match fingerprints doesn't like small images like the ones these drivers produce. I have successfully built it on my more powerful dev machine.Īny idea how to move the modified driver to the target machine? Or must I redo the steps on the target machine? I've managed to pull the libprintf source from github, put in modification to use FP_SCAN_TYPE_PRESS instead of FP_SCAN_TYPE_SWIPE. Product Id 0x0c26 and 0x0c28 are not whitelisted in the fprint-list hardwaredb declaration. \returns the scan type */ API_EXPORTED enum fp_scan_type fp_driver_get_scan_type(struct fp_driver *drv) ,!p' */ Retrieves the scan type for the devices associated with the driver. This function in the libfprint calls the vendor driver to get supported functions /** \ingroup drv Let me see where I can find the enroll code. I think the default driver or Ubuntu User fingerprint code is not setting this right for the Elan fingerprint reader 0x04f3::0x0c28 The scan type of the device, either "press" if you place your finger on the device, or "swipe" if you have to swipe your finger. ![]() I believe this is what causes the accuracy to be abysmally poor.Īny idea where I can read up to find out about configuration? The fingerprint reader works perfectly in Windows as a touch biometric reader, but in Ubuntu/Linux, it seem to be configured as a swipe biometric reader. Got the reader recognised in Ubuntu 22.10 but it tries to enroll fingerprint by swiping when it is a new "touch/press" version fingerprinter reader.ĭid some investigating and found the following: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |