Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
L
libfprint
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 44
    • Issues 44
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 9
    • Merge Requests 9
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • libfprint
  • libfprint
  • Issues
  • #299

Closed
Open
Opened Aug 25, 2020 by Piotr Masłowski@mPiotrek

False-negatives occur unmanageably often for 147e:2016 Upek

I have a ThinkPad T520 with 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor running Manjaro. The libfprint version is 1.90.2.

After installing and enrolling, I tried to fprind-verify. The result was verify-no-match. I've tried enrolling and verifying at different speeds, angles, etc. and the next few days the result always stayed the same – verify-no-match. After digging through old bug reports, outdated workarounds and legacy tools, I tried with the left hand. To my surprise it worked! To be honest, my right index and middle fingers have a bit damaged skin but all 10 fingers are still perfectly recognized by my phone. That being said, right now only my left middle finger works more or less consistently with libfprint – about every other time. Other than that my left ring and left index fingers and left thumb kind of work.

I understand that it's an older hardware and it may be quite less capable then the reader in my phone but the levels of false-negatives here are through the roof so I'm pretty sure something is really wrong here. Maybe the acceptance thresholds are too high? How could I better troubleshoot it or somehow inspect the issue?

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: libfprint/libfprint#299