Mariusz Ciszewski | 4 Apr 07:32 2014
Picon

Fwd: Raspberry Pi - Raspbian - to slow for fprint_demo ?

Different version of fprintd in some Linux distributions (who is sesponsible for it and who can / is able to change it in oficial repositories?) 

1. In Debian repository is currently: 0.4.1-5

Confirmed on Raspbian on raspberry Pi: 

root <at> raspberrypi:/home/pi# dpkg -l fprintd
Wybór:U=nieznany/I=instalacja/R=usunięcie/P=wyczyszczenie/H=zatrzymanie
| Stan:N=brak/I=zainstalowany/C=skonfigurowany/U=rozpakowany/
|/  F=częśc. skonfigurowany/H=częśc. zainstalowany/W=wyzw. czek./T=wyzw. zapl.
|| Błędy?=(brak)/R-do pon. inst. (duże litery w "Stan" i "Błędy"=problemy)
||/ Nazwa                             Wersja                Architektura          Opis
+++-=================================-=====================-=====================-=======================================================================
ii  fprintd                           0.4.1-5-g73edad0-3    armhf                 D-Bus daemon for fingerprint reader access
root <at> raspberrypi:/home/pi#


2. In Xubuntu repository is currently: 0.5.0-1

Confirmed on Xubuntu:

root <at> home:/home/mariusz# dpkg -l fprintd
Wybór:U=nieznany/I=instalacja/R=usunięcie/P=wyczyszczenie/H=zatrzymanie
| Stan:N=brak/I=zainstalowany/C=skonfigurowany/U=rozpakowany/
|/  F=częśc. skonfigurowany/H=częśc. zainstalowany/W=wyzw. czek./T=wyzw. zapl.
|| Błędy?=(brak)/R-do pon. inst. (duże litery w "Stan" i "Błędy"=problemy)
||/ Nazwa          Wersja       Architektura Opis
+++-==============-============-============-=================================
ii  fprintd        0.5.0-1      i386         D-Bus daemon for fingerprint read
root <at> home:/home/mariusz# 






2014-04-01 23:25 GMT+02:00 Mariusz Ciszewski <mariusz.ciszewski <at> gmail.com>:

Hello Vasily

I checked the version and I see:

root <at> raspberrypi:/home/pi# apt-get upgrade
Czytanie list pakietów... Gotowe
Budowanie drzewa zależności
Odczyt informacji o stanie... Gotowe
0 aktualizowanych, 0 nowo instalowanych, 0 usuwanych i 0 nieaktualizowanych.
root <at> raspberrypi:/home/pi# apt-get update
Pobieranie:1 http://mirrordirector.raspbian.org wheezy Release.gpg [490 B]
Pobieranie:2 http://archive.raspberrypi.org wheezy Release.gpg [490 B]
Pobieranie:3 http://mirrordirector.raspbian.org wheezy Release [14,4 kB]
Pobieranie:4 http://archive.raspberrypi.org wheezy Release [7227 B]
Pobieranie:5 http://archive.raspberrypi.org wheezy/main armhf Packages [17,2 kB]
Pobieranie:6 http://mirrordirector.raspbian.org wheezy/main armhf Packages [7426 kB]
Ign.  http://archive.raspberrypi.org wheezy/main Translation-pl_PL
Ign.  http://archive.raspberrypi.org wheezy/main Translation-pl
Ign.  http://archive.raspberrypi.org wheezy/main Translation-en
Stary http://mirrordirector.raspbian.org wheezy/contrib armhf Packages
Stary http://mirrordirector.raspbian.org wheezy/non-free armhf Packages
Stary http://mirrordirector.raspbian.org wheezy/rpi armhf Packages
Ign.  http://mirrordirector.raspbian.org wheezy/contrib Translation-pl_PL
Ign.  http://mirrordirector.raspbian.org wheezy/contrib Translation-pl
Ign.  http://mirrordirector.raspbian.org wheezy/contrib Translation-en
Ign.  http://mirrordirector.raspbian.org wheezy/main Translation-pl_PL
Ign.  http://mirrordirector.raspbian.org wheezy/main Translation-pl
Ign.  http://mirrordirector.raspbian.org wheezy/main Translation-en
Ign.  http://mirrordirector.raspbian.org wheezy/non-free Translation-pl_PL
Ign.  http://mirrordirector.raspbian.org wheezy/non-free Translation-pl
Ign.  http://mirrordirector.raspbian.org wheezy/non-free Translation-en
Ign.  http://mirrordirector.raspbian.org wheezy/rpi Translation-pl_PL
Ign.  http://mirrordirector.raspbian.org wheezy/rpi Translation-pl
Ign.  http://mirrordirector.raspbian.org wheezy/rpi Translation-en
Pobrano 7466 kB w 2min 11s (56,7 kB/s)
Czytanie list pakietów... Gotowe
root <at> raspberrypi:/home/pi# dpkg -l fprintd
Wybór:U=nieznany/I=instalacja/R=usunięcie/P=wyczyszczenie/H=zatrzymanie
| Stan:N=brak/I=zainstalowany/C=skonfigurowany/U=rozpakowany/
|/  F=częśc. skonfigurowany/H=częśc. zainstalowany/W=wyzw. czek./T=wyzw. zapl.
|| Błędy?=(brak)/R-do pon. inst. (duże litery w "Stan" i "Błędy"=problemy)
||/ Nazwa                             Wersja                Architektura          Opis
+++-=================================-=====================-=====================-=======================================================================
ii  fprintd                           0.4.1-5-g73edad0-3    armhf                 D-Bus daemon for fingerprint reader access
root <at> raspberrypi:/home/pi#

How do you think, why this old revision are included in Raspbian repositories?
Should it be reported in some place / to someone?

Best regards
Mariusz Ciszewski


2014-03-31 22:42 GMT+02:00 Vasily Khoruzhick <anarsoul <at> gmail.com>:

Hi Mariusz,

"** (fprintd-verify:3531): CRITICAL **: dbus_set_g_error: assertion
`gerror == NULL || *gerror == NULL' failed" means fprintd (not
libfprint) version is too old (several years or so)

Regards
Vasily

On Mon, Mar 31, 2014 at 11:07 PM, Mariusz Ciszewski
<mariusz.ciszewski <at> gmail.com> wrote:
> Dear Vasily
>
> I decided to check again this strange behavior of fprint-demo on Raspberry
> Pi (fprintd, fprint-demo, fprint-gui form original Raspbian repositories
> included by default).
>
> I decided to check its behavior in text console (using fprintd-enroll and
> then fprintd-verify.
>
> And just look - normally (on Ubuntu) after fprint-enroll system ask be 5
> times to repeat fingerprint scan.
>
> And here on Raspberry Pi it looks:
>
> root <at> raspberrypi:/home/pi# fprintd-enroll
> Using device /net/reactivated/Fprint/Device/0
> Enrolling right index finger.
> Enroll result: enroll-completed
> root <at> raspberrypi:/home/pi# fprintd-enroll
> Using device /net/reactivated/Fprint/Device/0
> Enrolling right index finger.
> Enroll result: enroll-completed
> root <at> raspberrypi:/home/pi#
>
>
> And then:
>
> root <at> raspberrypi:/home/pi# fprintd-verify
> Using device /net/reactivated/Fprint/Device/0
> Listing enrolled fingers:
>  - #0: right-index-finger
> Verify result: verify-no-match (done)
> root <at> raspberrypi:/home/pi# fprintd-verify
> Using device /net/reactivated/Fprint/Device/0
> Listing enrolled fingers:
>  - #0: right-index-finger
>
> ** (fprintd-verify:3531): CRITICAL **: dbus_set_g_error: assertion `gerror
> == NULL || *gerror == NULL' failed
> VerifyStart failed:
> root <at> raspberrypi:/home/pi# fprintd-verify
> Using device /net/reactivated/Fprint/Device/0
> Listing enrolled fingers:
>  - #0: right-index-finger
> Verify result: verify-no-match (done)
> root <at> raspberrypi:/home/pi#
>
>
> Any ideas why fingerprint devices cannot work on Raspberry Pi properly?
>
> Vasily I didn't try your repositories yet. Maybe I should...
>
>
>
>
>
>
> 2014-03-26 9:24 GMT+01:00 Vasily Khoruzhick <anarsoul <at> gmail.com>:
>>
>> Hi Mariusz,
>>
>>
>> What type of scanner do you use?
>>
>> Regards
>> Vasily
>>
>> On Wed, Mar 26, 2014 at 11:17 AM, Mariusz Ciszewski
>> <mariusz.ciszewski <at> gmail.com> wrote:
>> > Hello
>> >
>> > I tried fprint_demo many times but when I tried it on Raspberry Pi (ARM
>> > based copmuter) I discovered It's much much harder to verify
>> > (succesfully
>> > done) a fingerprint.
>> > For example using a notebook with Ubuntu the verification was
>> > succesfully
>> > almost every time.
>> >
>> > On Raspbbery Pi - Raspbian (based on Debian OS) the rerification errers
>> > are
>> > alboms 80%. About 20% (or less) is succesfully done.
>> >
>> > What can be a reason?
>> > How can I found a real reason?
>> >
>> > Please help me.
>> >
>> > Thank you very much.
>> >
>> > Best regards
>> > Mariusz Ciszewski
>> >
>> > _______________________________________________
>> > fprint mailing list
>> > fprint <at> lists.freedesktop.org
>> > http://lists.freedesktop.org/mailman/listinfo/fprint
>> >
>
>



_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
Mariusz Ciszewski | 1 Apr 22:51 2014
Picon

How to compile fprintd-enroll and fprintd-verify from source code?

Hello.

I would like to compile fprintd-enroll and fprintd-verify from repositories:

I would like to use them instead of out of date and not working properly packages fprintd-enroll and fprintd-verify from Raspbian (Raspberry Pi) repositories.

What / how should I proceed to replace old fprintd-enroll and fprintd-verify  packets and then use newest (compiled from sources) ?

Thank you very much for any help

Best regards
Mariusz Ciszewski
_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
Vasily Khoruzhick | 26 Mar 10:11 2014
Picon

Re: Raspberry Pi - Raspbian - to slow for fprint_demo ?

On Wed, Mar 26, 2014 at 11:30 AM, Mariusz Ciszewski
<mariusz.ciszewski <at> gmail.com> wrote:
> Medion/Tevion Authentec AES2501
>
> http://www.bromba.com/tevions.jpg

That one can suffer from insufficient performance.

You can try libfprint from my github repo-
https://github.com/anarsoul/libfprint, I've improved frame assembly
routines for AES scanners recently.

Btw, please keep mailing list in CC, since it's not a private
conversation and questions/answers can be usefull for someone in
future.

Regards
Vasily

>
> 2014-03-26 9:24 GMT+01:00 Vasily Khoruzhick <anarsoul <at> gmail.com>:
>
>> Hi Mariusz,
>>
>> What type of scanner do you use?
>>
>> Regards
>> Vasily
>>
>> On Wed, Mar 26, 2014 at 11:17 AM, Mariusz Ciszewski
>> <mariusz.ciszewski <at> gmail.com> wrote:
>> > Hello
>> >
>> > I tried fprint_demo many times but when I tried it on Raspberry Pi (ARM
>> > based copmuter) I discovered It's much much harder to verify
>> > (succesfully
>> > done) a fingerprint.
>> > For example using a notebook with Ubuntu the verification was
>> > succesfully
>> > almost every time.
>> >
>> > On Raspbbery Pi - Raspbian (based on Debian OS) the rerification errers
>> > are
>> > alboms 80%. About 20% (or less) is succesfully done.
>> >
>> > What can be a reason?
>> > How can I found a real reason?
>> >
>> > Please help me.
>> >
>> > Thank you very much.
>> >
>> > Best regards
>> > Mariusz Ciszewski
>> >
>> > _______________________________________________
>> > fprint mailing list
>> > fprint <at> lists.freedesktop.org
>> > http://lists.freedesktop.org/mailman/listinfo/fprint
>> >
>
>
Mariusz Ciszewski | 26 Mar 09:17 2014
Picon

Raspberry Pi - Raspbian - to slow for fprint_demo ?

Hello

I tried fprint_demo many times but when I tried it on Raspberry Pi (ARM based copmuter) I discovered It's much much harder to verify (succesfully done) a fingerprint. 
For example using a notebook with Ubuntu the verification was succesfully almost every time.

On Raspbbery Pi - Raspbian (based on Debian OS) the rerification errers are alboms 80%. About 20% (or less) is succesfully done.

What can be a reason? 
How can I found a real reason?

Please help me.

Thank you very much.

Best regards
Mariusz Ciszewski
_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
Mariusz Ciszewski | 26 Mar 09:10 2014
Picon

Replacement for linux fprintd-verify command - identify user in database

Hello

Please let me know it there is existing replacement for linux fprintd-verify command giving possibility of identify user in database.

fprintd-verify [-f finger] [usename] 

can be used for verify known user only (declaerd before checking: [usename])

I need to have command taht will be able to find user in database based on fingerprint of "unknown" person.

If it do not existing yet: 

- is it hard to write such application using libfprint ? (is it possible using this library only?)
- where can I find a person that could be write some code for open source project ( http://rasp485berry.wordpress.com/ )

Best regards
Mariusz Ciszewski

_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
Mariusz Ciszewski | 23 Mar 13:07 2014
Picon

MiniPC e.g. Raspberry Pi with USB fingerprint as logging on terminal for smart home

Dear All

After my previous experiences I think you are my last chance to find sollution in my topic:

http://ubuntuforums.org/showthread.php?t=2212639&p=12964496#post12964496

http://darkblue.homeip.net/fingerprint/Forum/topic.php?TopicId=376&Posts=0

I'm searching for sollution to check the person after she or he came into home. I found it would be simplest for me using any mini PC and linux logon using fingerprint action (USB fingerprint reader connected). Then - script placed in autostart (executed if user logged succesfully). After script is executed then logged out uotomatically. And fingerprint system is ready again for check next person coming into home.

Please help, or please let me know who should I ask for help.

It strange but as I experienced - to find programist knowing fingerprint issues for linux is almost impossible.

For more details please check:
http://darkblue.homeip.net/fingerprint/Forum/topic.php?TopicId=376&Posts=0

or please contact me here or directly.

Thank you very much.
Best regards

Mariusz Ciszewski

_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
Mariusz Ciszewski | 23 Mar 12:43 2014
Picon

Fwd: MiniPC with USB fingerprint as logging on terminal for smart home

Dear All

After my previous experiences I think you are my last chance to find sollution in my topic:

http://ubuntuforums.org/showthread.php?t=2212639&p=12964496#post12964496

http://darkblue.homeip.net/fingerprint/Forum/topic.php?TopicId=376&Posts=0

I'm searching for sollution to check the person after she or he came into home. I found it would be simplest for me using any mini PC and linux logon using fingerprint action (USB fingerprint reader connected). Then - script placed in autostart (executed if user logged succesfully). After script is executed then logged out uotomatically. And fingerprint system is ready again for check next person coming into home.

Please help, or please let me know who should I ask for help.

It strange but as I experienced - to find programist knowing fingerprint issues for linux is almost impossible.

For more details please check:
http://darkblue.homeip.net/fingerprint/Forum/topic.php?TopicId=376&Posts=0

or please contact me here or directly.

Thank you very much.
Best regards

Mariusz Ciszewski

_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
Martin Hejnfelt | 20 Mar 21:52 2014
Picon

EgisTec ES603 Error -22

Hi,

I'm working with a EgisTec ES603 (1c7a:0603). I am using the current
HEAD from anarsoul git repository.

When I try to enroll or identify (with async methods), sometimes it
works, but most of the time I get a result of -22 (EINVAL) in the
callback. I tried debugging it, and it seems the error comes in the
sanitize_img function (imgdev.c line 93) from a check of the image
height (line 106-111, error comes in 110). By enabling logging, I can
see that during an enroll sequence, my callback function is called twice
from one call. The first call is good, where I get an FP_ENROLL_PASS
swipe and the function exits as it should. It then immediately gets
called again, however this is the one that fails with error -22.

I then enabled logging in the library, and it seems that it detects the
finger twice or something, and then removes some empty lines that end up
with a blank image. Here's some debug output to gaze upon:

drv:debug [__ssm_call_handler] 0x7fbae0000910 entering state 13
drv:debug [__ssm_call_handler] 0x7fbae0000910 entering state 12
drv:debug [__ssm_call_handler] 0x7fbae0000910 entering state 13
fp:debug [fpi_imgdev_report_finger_status] finger on sensor
drv:debug [fpi_ssm_mark_completed] 0x7fbae0000910 completed with status
0
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 0
etes603:debug [m_capture_state] Capturing a fingerprint...
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 1
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 2
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 3
etes603:debug [m_capture_state] Capturing a 1st frame...
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 4
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 5
etes603:debug [m_capture_state] Capturing a 2nd frame...
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 4
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 5
etes603:debug [process_remove_fp_end] Removing 354 empty lines from
image
etes603:debug [process_remove_fp_end] Removing 0 empty lines from image
fp:debug [fpi_img_new] length=163840
etes603:debug [m_capture_state] Sending the raw fingerprint image
(0x640)
fp:debug [fpi_imgdev_image_captured] 
fp:debug [fpi_img_detect_minutiae] minutiae scan completed in 0.057886
secs
fp:debug [fpi_img_detect_minutiae] detected 97 minutiae
fp:debug [print_data_new] driver=12 devtype=0000
fp:debug [print_data_new] driver=12 devtype=0000
fp:debug [fpi_imgdev_report_finger_status] finger removed
fp:debug [fpi_imgdev_report_finger_status] reporting enroll result
async:debug [fpi_drvcb_enroll_stage_completed] result 3
Enroll stage callback
Enrolling 41EB2014-617A-4953-8283-0B9DD01653FB
System output: Accepted, scan finger again... (1/5)
drv:debug [fpi_ssm_mark_completed] 0x7fbae0000a10 completed with status
0
etes603:debug [m_capture_complete] Device is still active, restarting
finger detection
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 0
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 1
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 2
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 3
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 4
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 5
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 6
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 7
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 8
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 9
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 10
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 11
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 12
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 13
fp:debug [fpi_imgdev_report_finger_status] finger on sensor
drv:debug [fpi_ssm_mark_completed] 0x7fbae0000a10 completed with status
0
drv:debug [__ssm_call_handler] 0x7fbae000afc0 entering state 0
etes603:debug [m_capture_state] Capturing a fingerprint...
drv:debug [__ssm_call_handler] 0x7fbae000afc0 entering state 1
drv:debug [__ssm_call_handler] 0x7fbae000afc0 entering state 2
drv:debug [__ssm_call_handler] 0x7fbae000afc0 entering state 3
etes603:debug [m_capture_state] Capturing a 1st frame...
drv:debug [__ssm_call_handler] 0x7fbae000afc0 entering state 4
drv:debug [__ssm_call_handler] 0x7fbae000afc0 entering state 5
etes603:debug [m_capture_state] Capturing a 2nd frame...
drv:debug [__ssm_call_handler] 0x7fbae000afc0 entering state 4
drv:debug [__ssm_call_handler] 0x7fbae000afc0 entering state 5
etes603:debug [process_remove_fp_end] Removing 498 empty lines from
image
etes603:debug [process_remove_fp_end] Removing 496 empty lines from
image
fp:debug [fpi_img_new] length=0
etes603:debug [m_capture_state] Sending the raw fingerprint image (0x0)
fp:debug [fpi_imgdev_image_captured] 
fp:error [sanitize_image] no image height assigned
fp:debug [fpi_imgdev_report_finger_status] finger removed
fp:debug [fpi_imgdev_report_finger_status] reporting enroll result
async:debug [fpi_drvcb_enroll_stage_completed] result -22
Enroll stage callback
Enrolling 41EB2014-617A-4953-8283-0B9DD01653FB
Enroll failed with error -22
System output: Enroll error!
async:debug [fp_async_enroll_stop] 
etes603:debug [dev_deactivate] deactivating
etes603:debug [m_exit_start] Switching device to idle mode
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 0
drv:debug [fpi_ssm_mark_completed] 0x7fbae000afc0 completed with status
0
etes603:debug [m_capture_complete] And it's over.
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 1
drv:debug [fpi_ssm_mark_completed] 0x7fbae0000a10 completed with status
0
etes603:debug [m_exit_complete] The device is now in idle state
fp:debug [fpi_imgdev_deactivate_complete] 
async:debug [fpi_drvcb_enroll_stopped] 

This comes from a single swipe...

Enroll stage callback
Enrolling 41EB2014-617A-4953-8283-0B9DD01653FB
System output: Accepted, scan finger again... (1/5)

is the output from my callback function, and as you can see it gets
called twice from a single scan:

Enroll stage callback
Enrolling 41EB2014-617A-4953-8283-0B9DD01653FB
Enroll failed with error -22
System output: Enroll error!

Now the code works fine with the integrated UPEK (147e:2016) in my
laptop, so any clues here?

Thanks in advance!

Kind regards,
Martin Hejnfelt
Vasily Khoruzhick | 20 Mar 09:04 2014
Picon

Re: Call for testing: UPEK 147e:1001, AES1660, AES1610, AES2501, AES2550, AES2810, AES2660

Hi Julian,

According to log, it looks like one control transfer (write reg) of
deinit sequence timed out. Does it happen all the time?

Please note, that with latest changes all imaging devices do 5 scans
for enrollment.

Regards
Vasily

On Thu, Mar 20, 2014 at 9:13 AM, Julian Sikorski <belegdol <at> gmail.com> wrote:
> W dniu 16.03.2014 11:45, Vasily Khoruzhick pisze:
>> Hi to all fingerprint scanner users,
>>
>> It's another call for libfprint testing.
>>
>> Good news to all UPEK 147e:1001 users - I've added support for that
>> device into upeksonly driver - so it worth testing. It also may work
>> for 147e:1002 device - just try to add its USB IDs into upeksonly.c
>> and use UPEKSONLY_1001 variant for it.
>>
>> Also I've improved image assembling utilities for all AuthenTec
>> scanners, so now match rate is a bit better for AES1660 scanner - so
>> all AES1660 are encouraged to test my changes as well.
>>
>> All changes are pushed into master branch of
>> git://github.com/anarsoul/libfprint.git repo.
>>
>> To obtain the code do:
>>
>> git clone git://github.com/anarsoul/libfprint.git
>>
>> Use instructions from [1] to compile and test it. Thanks!
>>
>> Regards,
>> Vasily
>>
>> P.S. PLEASE KEEP FPRINT MAILLIST IN CC!
>>
>> [1] http://lists.freedesktop.org/archives/fprint/2012-November/000330.html
>>
> Hello,
>
> 147e:1001 does not seem to be working here. When I open fprint_demo and
> pick a finger to enroll, the child window shows nothing for a while.
> When I scan my finger regardless, a scan will appear at some point, but
> with a message "enrollment failed due to bad scan data, press cancel to
> continue". Logs attached.
>
> Best regards,
> Julian
Vasily Khoruzhick | 16 Mar 11:45 2014
Picon

Call for testing: UPEK 147e:1001, AES1660, AES1610, AES2501, AES2550, AES2810, AES2660

Hi to all fingerprint scanner users,

It's another call for libfprint testing.

Good news to all UPEK 147e:1001 users - I've added support for that
device into upeksonly driver - so it worth testing. It also may work
for 147e:1002 device - just try to add its USB IDs into upeksonly.c
and use UPEKSONLY_1001 variant for it.

Also I've improved image assembling utilities for all AuthenTec
scanners, so now match rate is a bit better for AES1660 scanner - so
all AES1660 are encouraged to test my changes as well.

All changes are pushed into master branch of
git://github.com/anarsoul/libfprint.git repo.

To obtain the code do:

git clone git://github.com/anarsoul/libfprint.git

Use instructions from [1] to compile and test it. Thanks!

Regards,
Vasily

P.S. PLEASE KEEP FPRINT MAILLIST IN CC!

[1] http://lists.freedesktop.org/archives/fprint/2012-November/000330.html
Anatoly Thernytskyi | 21 Feb 13:13 2014
Picon

(no subject)

Hello, I have this problem http://lists.freedesktop.org/archives/fprint/2012-April/000137.html
with fingeprint digitalPersona  U.are.U 4000B. Please, help me. I don't have any ideas how fix this bug. Thank you very much.
_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint

Gmane