Hi list,
I've written a driver for Elan 0x0907 fp scanner. I don't know which
model it is but it's marketed under various names for ex. Cobo C2
https://hardzone.es/app/uploads/2017/04/Cobo-C2-01.jpg. You can get it
on AliExpress for about $25.
https://github.com/iafilatov/libfprint/commit/e19f7e3
Hi Konata,
The commands your reader uses look similar to the ones from an Elan
reader 0x04f3:0x0907
that I wrote a driver for some time ago.
https://lists.freedesktop.org/archives/fprint/2017-October/000892.html
https://github.com/iafilatov/libfprint/blob/elan/libfprint/drivers/elan.h
https://git
o
read data and 4024 to save (names mine). Without it wait for finger
(403f) doesn't work correctly.
2017-11-08 16:39 GMT+02:00 Sebastien Bechet :
> Hello,
>
> I just discover Konata Izumi and Igor Filatov work
>
> Igor Filatov : 0x04f3:0x0907 (144x64 16 bits)
> Konata Izum
> 1. windows boot (000c*1, 0009*2, then 403f)
Those 009's could be the calibration. Could you send me your traces?
Also pls do one where you wait a few seconds after the led goes on
before putting the finger on the sensor.
> 2. record a fingerprint
> Windows driver do multiple cmd 9, then, 403f,
try tomorrow.
>
>
> ___
> fprint mailing list
> fprint@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/fprint
--
Igor Filatov
ia.fila...@gmail.com
___
fprint mailing list
fprint@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/fprint
> Maybe driver authors use device with [Focus > stacking](
https://en.wikipedia.org/wiki/Focus_stacking) ?
> Can it help to have more minutiae?
With these devices the scanned area is so small that not many minutiae can
be found there. I got like 5 o so with my finger and that's what I can
visuall
;
> Timo
>
>
>
>
> ___
> fprint mailing list
> fprint@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/fprint
>
--
Igor Filatov
ia.fila...@gmail.com
___
fprint mailing list
fprint@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/fprint
fore. Some help would be very much appreciated here.
>
> Cheers
>
> Timo
>
> -Original Message-
> From: Igor Filatov [mailto:ia.fila...@gmail.com]
> Sent: Monday, 8 January 2018 18:02
> To: TeEmZe
> Cc: fprint@lists.freedesktop.org
> Subject: Re: [fprint] Libfprint
framesup30.diff) and a small typo
> (typo.diff).
>
> Thank you.
>
>
>
> ___
> fprint mailing list
> fprint@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/fprint
>
--
Igor Filatov
ia.fila...@gmail.com
___
llo Igor,
>
> On 2018-01-15 17:38, Igor Filatov wrote:
>>
>> I don't quite understand what happens though. You've replaced a number
>> of stages by plain image read commands (CALIBRATE, CAPTURE_START,
>> DEACTIVATE) which don't seem to do anything but rea
the ADC value, not offset value)
> Please refer to Pre_Scan_flow.pdf for more information.
>
> Sébastien, question, are you using yours in swipe mode, like Igor is?
>
> Regards,
>
> Hans
>
>
>
> On 16-01-18 17:09, Igor Filatov wrote:
> > Hi Sebastien,
>
x0903
> 0x04f3,0x0907
> 0x04f3,0x0C03
> 0x04f3,0x0C16
>
> Please try it.
>
--
Igor Filatov
ia.fila...@gmail.com
___
fprint mailing list
fprint@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/fprint
b! With this one small
> change the program works for me.
>
> Regards,
>
> Hans
>
>
> > CMD STATUS sent
> > Status: 0x1
> > CMD Get Calibration Mean sent
> > calibration mean value: 256 (0x100)
> > CMD Wait For Finger sent
> > Received 0x55
>
>
> Regards,
>
> Timo
>
> -Original Message-
> From: fprint [mailto:fprint-boun...@lists.freedesktop.org] On Behalf Of
> Hans de Goede
> Sent: Wednesday, 17 January 2018 16:26
> To: Igor Filatov
> Cc: fprint@lists.freedesktop.org; Sébastien Béchet <
> sebastien.
> square and seems to contain the image 3 times
Could be because convert is hardcoded at 96x96.
On Thu, 18 Jan 2018, 12:04 Hans de Goede, wrote:
> Hi,
>
> On 18-01-18 10:48, Sébastien Béchet wrote:
> > On 17-01-18 19:21, Igor Filatov wrote:
> >> We didn't have
e-
> From: Hans de Goede [mailto:hdego...@redhat.com]
> Sent: Thursday, 18 January 2018 16:14
> To: Sebastien Bechet ; Igor Filatov <
> ia.fila...@gmail.com>
> Cc: TeEmZe ; konachan@gmail.com;
> fprint@lists.freedesktop.org
> Subject: Re: [fprint] elan patch + poc 0x90
I have a feeling that for 0903 commands 4023 and 4024 mean something
different. I-byte mean is weird. given 2-byte "pixels".
On Wed, 24 Jan 2018, 11:59 Sébastien Béchet,
wrote:
> Hello Igor,
>
> This hack for firmware <= 0x0153 working.
>
>
___
fprint
4024 access for 0903).
>
>
> On 2018-01-24 11:03, Igor Filatov wrote:
> > I have a feeling that for 0903 commands 4023 and 4024 mean something
> > different. I-byte mean is weird. given 2-byte "pixels".
>
___
I updated the questions with
> our latest comments. Maybe you can ask directly kt@elan?
>
> see
> [questions](
> https://github.com/sbechet/elanfp/#preparation-of-questions-for-ktelan).
>
>
> On 2018-01-24 13:50, Igor Filatov wrote:
> > Sebastien,
> >
> > Ar
> I’d love to test the current state of the driver, but I’ll need some
> advice here.
>
>
>
> Regards,
>
>
>
> Timo
>
>
>
> *From:* Igor Filatov [mailto:ia.fila...@gmail.com]
> *Sent:* Tuesday, 23 January 2018 22:59
> *To:* Hans de Goede ; konac
t;
> <- ? 1.3.2
>
> ...
>
> -> 4031
>
> -> 403F
>
> <- 55 1.3.3
>
> ...
>
> -> 4031
>
> -> 0009
>
> <- ?
>
> -> 000b
>
> -> 0009
>
> <- ?
>
> ->
Yes, this time it worked. First of all, you should be able to open
finger.pgm in the same directory with an image viewer and see your finger.
Then you can try exmaples/enroll and examples/verify to enroll and verify
your fingerprint. If everything seems ok, install the driver with `sudo
make instal
es take some practice...
On Sun, Jan 28, 2018 at 2:25 AM wp12880529-timo wp12880529-timo <
t...@teemze.de> wrote:
> Hi,
>
>
> the enroll process seems to work. However, when verifying it detects my
> finger in about 1 out of 10 tries. Is this a bug or is it normal?
>
>
&
re's a driver for a 64x64 device (
https://www.freedesktop.org/wiki/Software/fprint/libfprint/aes4000/) so why
not?
On Mon, Jan 29, 2018 at 5:38 PM Hans de Goede wrote:
> Hi,
>
> On 23-01-18 22:58, Igor Filatov wrote:
> > I've updated the driver to support the devices know
good in C and I don’t think that C is the perfect language for algorithmic)?
> And would I have to rewrite the existing code or could I just replace a
> library?
>
>
>
> Kind regards,
>
>
>
> Timo
>
>
>
> *From:* Igor Filatov [mailto:ia.fila...@gmail.com]
&g
; I suggest improving enrollment procedure. It should stitch big image
> from several small images and use it later for comparison (using
> whatever algorithm - minutiae algo also may work).
>
> On Mon, Jan 29, 2018 at 7:38 AM, Hans de Goede
> wrote:
> > Hi,
> >
> > On 2
; help including it into the main project.
>
>
>
>
>
> Kind regards,
>
>
>
> Timo
>
>
>
> -Original Message-
> From: Hans de Goede [mailto:hdego...@redhat.com]
> Sent: Tuesday, 30 January 2018 10:39
> To: TeEmZe ; 'Igor Filatov'
>
now works better/same/worse for you. I think verification
is now slightly better on my device but I need to use it for a couple of
days to know.
On Tue, Jan 30, 2018 at 8:31 PM Igor Filatov wrote:
> Hi Timo,
>
> Sure, give it a shot! And as I said earlier, remember that you don&#
now the way you’re currently assembling the joined fingerprint
>> image, so maybe someone who does could give this a try?
>> I’ll be happy to test it afterwards.
>>
>>
>>
>>
>>
>> Kind regards
>>
>>
>>
>> Timo
>>
>>
>>
&g
t;
> *From:* fprint [mailto:fprint-boun...@lists.freedesktop.org] *On Behalf
> Of *TeEmZe
> *Sent:* Friday, 9 February 2018 23:48
> *To:* 'Igor Filatov' ; fprint@lists.freedesktop.org
>
>
> *Subject:* Re: [fprint] elan patch + poc 0x903 and 0x0C03
>
>
>
> H
Hi,
1. You need to find out the correct format of returned data. By correct I
mean the one that allows to decode an image of a fingerprint. This is
necessary for the matching algorithm to work. The .pgm files in your repo
don't look like fingerprints, right? They look like noise because the
dimens
e my scanner as a swipe-type one?
> That's exactly what you did with your Elan driver, right?
> The scan area is indeed very small.
> And i am curious why does it return several images instead of one?
> Isn't it simplier to process in any case, especially when it is press-type
>
I think it would be better if libfprint simply called dev_activate each
time it needed an image, including each enroll step, and then called
dev_deactivate when it's done. Drivers should know whether they need to
reactivate or not. But this will require changes to all the drivers of the
devices tha
r call dev_deactivate. I think
the drivers should already handle dev_deactivate properly on any stage. The
changes to the drivers should be minimal this way.
On Fri, Feb 16, 2018 at 3:08 PM Marco Trevisan (Treviño)
wrote:
> Hi Igor,
>
> 2018-02-16 8:58 GMT+01:00 Igor Filatov :
> > I
I confirm that this improves stitching. Especially with tall frames.
On Sat, Mar 3, 2018 at 12:07 AM Vasily Khoruzhick
wrote:
> Hi Timur,
>
> On Wed, Feb 28, 2018 at 12:41 PM, Timur Celik wrote:
> > Hello everybody,
> >
> > I have already discussed this with Igor. There are two different bugs i
I don't think it's possible. jlibfprint depends on libfprint which is
written for linux (posix?): libusb, glib etc.
On Tue, Mar 6, 2018 at 11:04 AM enock tum wrote:
> I have implemented the libfprint on my linux and it is working perfectly.
> The problem comes when i want to transfer the project
Hi Mark,
There are no high-level docs, unfortunately. There's some valuable info in
comments in drv.c, sync.c, async.c, img.c etc. but it only covers specific
parts, not how they should interact.
There are 6 drivers for press-type sensors: aes3500.c, aes4000.c,
fdu2000.c, upektc.c, uru4000.c, vco
process? asynchronity means that it'll only be used in a later function
> * call. */static int dev_activate(struct fp_img_dev *dev, enum
> fp_imgdev_state state)
> {
>
> Thanks,
>
> Mark
>
> On Fri, Mar 9, 2018 at 10:43 AM, Igor Filatov
> wrote:
>
> Hi Mark
failed -5 errno=22
> Wrote scanned image to enrolled.pgm
> Didn't quite catch that. Please try again.
>
> What is:
>
> libusb: warning [handle_timeout] async cancel failed -5 errno=22
>
> Help would be appreciated, though I know it is difficult to debug other
> p
Mine seems ok. The docs could use a short build&install guide though. I've
updated the readme in my repo https://github.com/iafilatov/libfprint. Meson
is great but from a user's perspective it doesn't beat `./configure &&
make`. And actually there's quite a few ones who want to try it out but
don't
> On Thu, 2018-05-17 at 23:40 +0300, Igor Filatov wrote:
> > Mine seems ok. The docs could use a short build&install guide though.
> > I've updated the readme in my
> > repo https://github.com/iafilatov/libfprint. Meson is great but from
> > a user's perspe
Sorry for a bit of off-topic but it looks like the new ms keyborad as a
small touch sensor which is unreliable with the current matching algo.
That's the problem we really need competent people and/or sponsorship for
first. Even if someone writes a driver for that kb, the experience will
still be s
Looks like G_DEBUG_HERE is only available in glib >= 2.50. Might set the
bar too high. For ex. latest Mint has 2.48 and the oldest Ubuntu LTS
(14.04) only has 2.40. I think the latter could be a good baseline.
On Tue, May 29, 2018 at 2:59 PM Bastien Nocera wrote:
> Hey,
>
> In the process of wri
1 +0100, Sébastien Béchet wrote:
> > On 2018-01-17 12:12, Igor Filatov wrote:
> > > Looks like o1ca as well https://github.com/iafilatov/libfprint/pull
> > > /4
> >
> > Not o1ca but 0x0C1A. I create repository for POC:
> >
> > http://github.com/sbechet/el
Ok, I'll try to find some time to prepare a patch against upstream in the
coming days.
On Mon, Jun 18, 2018 at 4:22 PM Hans de Goede wrote:
> Hi,
>
> On 18-06-18 15:03, Bastien Nocera wrote:
> > On Mon, 2018-06-18 at 15:01 +0200, Hans de Goede wrote:
> >> Hi,
>
Not sure I understand what you're trying to do, but if you want a cli tool
to compare fingerprint images, you could write one using some functions in
img.c. But you might need to normalize your images first.
On Tue, 19 Jun 2018, 16:08 Bastien Nocera, wrote:
> On Tue, 2018-06-19 at 12:49 +0200,
Bastien,
I've incorporated latest upstream changes so I could open a merge request
but it looks like on gitlab I need a permission to do it. Or should I just
send a patch?
___
fprint mailing list
fprint@lists.freedesktop.org
https://lists.freedesktop.org
and everything seems
fine now.
On Sun, Jun 24, 2018 at 2:52 PM Bastien Nocera wrote:
> On Sun, 2018-06-24 at 14:25 +0300, Igor Filatov wrote:
> > Bastien,
> >
> > I've incorporated latest upstream changes so I could open a merge
> > request but it looks like on
https://lists.freedesktop.org/mailman/options/fprint
On Mon, Aug 27, 2018 at 4:25 PM Владислав Зелёный
wrote:
> Пожалуйста, не пишите на эту почту. Как отписаться от рассылки?
>
>
> 27.08.2018, 19:54, "Bastien Nocera" :
>
> On Mon, 2018-08-27 at 18:33 +0300, Timo Teras wrote:
>
> Hi
>
> On Mon
Hi,
This is fprint mailing list for the fprint and libpfprint projets. I'm
guessing you need
https://lists.freedesktop.org/mailman/listinfo/pulseaudio-bugs
On Wed, Sep 19, 2018 at 7:44 PM Vámos Balázs
wrote:
> Hi.
>
> Today we spoke from linux in a Live what is our experience, problems
> etc. I
I think Dave means that the scanner would capture the print when the device
is powered on. Not as instructed by a userspace driver, but as a "hardware
feature" of the button/sensor itself. It would store a single image until
asked by libfrint to perform a scan, at which point it would just submit
t
Hello Rick,
If you want fingerprint login, sudo etc. then you're almost set. You should
only need `apt install libpam-fprintd` and then `sudo pam-auth-update`
where you enable "Fingerprint authentication".
On Sun, Feb 17, 2019 at 2:04 AM Rick Kamp wrote:
> Hello all,
>
>
>
> Just yesterday I de
Hi Brian,
> how long does it take to identify a fingerprint (setting new fingerprint for
> user) ? Speed is essential as it needs to happen fresh every bootup.
5 distinct images need to be captured, so I'd say no longer than 15
seconds if the scanner works well. But it's best to set up and see f
> Is this a small sensor problem and is there really too little minutiae?
See https://cedar.buffalo.edu/~srihari/papers/RRP-full.pdf page 7 fig 3 e,f
where it says 20 and 15 minutiae. A 114x57 scan is roughly 1/3 of that
area. In my experience there's usually <5 minutiae on a 144x64 image.
That's
54 matches
Mail list logo
