Bug 82779 - second enrollment doesn't work
Summary: second enrollment doesn't work
Status: RESOLVED MOVED
Alias: None
Product: libfprint
Classification: Unclassified
Component: libfprint (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: libfprint-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-18 18:04 UTC by andreas.angerer89
Modified: 2018-05-31 08:56 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
output of fprintd_demo using --enable-debug-log (235.81 KB, text/plain)
2014-08-18 18:04 UTC, andreas.angerer89
Details

Note You need to log in before you can comment on or make changes to this bug.
Description andreas.angerer89 2014-08-18 18:04:28 UTC
Created attachment 104839 [details]
output of fprintd_demo using --enable-debug-log

There seems to be similar problems for other users (see for example 77678), but I thought I file a new bug report. 

I'm using libfprint-0.5.1 from source, Ubuntu 14.04 and have a fingerprint reader ES603. I have compiled libfprint with the flag --enable-debug-log and attached the output in the terminal.

The problem is: first enrollment in fprint_demo works fine, but after the first enrollment the device goes into the idle-state and no subsequent enrollments are made. Can someone help?
Comment 1 Patrick Marlier 2014-10-08 06:49:23 UTC
Dear Andreas,

Thanks for reporting the problem. The problem in 77678 seems a bit different but you can try the patch from here:
https://bugs.freedesktop.org/show_bug.cgi?id=84734

From the log they are few interesting things:
etes603:warning [msg_check_cmd20] unexpected answer CMD_20 from device(05 FF FF)
etes603:warning [msg_check_cmd25] unexpected answer for CMD_25 (FF)
> I never figured out what are those commands and your device did not answer the same way as mine.

etes603:debug [m_tunedc_state] -> DCoffset=0x34 Gain=0x23
> The value 0x34 seems high and not even tested in the tuning process. I guess there is a bug in the tuning phase (need to investigate).

etes603:debug [process_remove_fp_end] Removing 492 empty lines from image
etes603:debug [process_remove_fp_end] Removing 0 empty lines from image
etes603:debug [m_capture_state] Sending the raw fingerprint image (0x502)
fp:debug [fpi_img_detect_minutiae] minutiae scan completed in 0,042624 secs
fp:debug [fpi_img_detect_minutiae] detected 28 minutiae
> Only 28 minutiae... How was the quality of the fingerprint?

fp:debug [fpi_imgdev_report_finger_status] finger on sensor
etes603:debug [process_remove_fp_end] Removing 498 empty lines from image
etes603:debug [process_remove_fp_end] Removing 496 empty lines from image
> The driver seems to find that the finger is still on the sensor but the scan seems black.

Can you try to force the value of DCoffset to 0x32 and check the scan result?

	case TUNEDC_FINAL_SET_REG2122_REQ:
+		dev->dcoffset = 0x32;
		fp_dbg("-> DCoffset=0x%02X Gain=0x%02X", dev->dcoffset,
			dev->gain);
		/* ??? how reg21 / reg22 are calculated */
		msg_set_regs(dev, 4, REG_21, 0x23, REG_22, 0x21);
		if (async_tx(idev, EP_OUT, async_tx_cb, ssm))
			goto err;
		break;
Comment 2 GitLab Migration User 2018-05-31 08:56:03 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/libfprint/libfprint/issues/46.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.