uunicorn

Firmware is a file with .xpfwext extension, which comes from your windows driver. Try using innoextract to extract everything from your diver installer .exe file and look for .xpfwext files.

Hi, can you share the `systemctl status` for `open-fprintd-suspend.service` and `open-fprintd-resume.service` services?

I don't know where `open-fprintd-restart-after-resume.service` and `python3-validity-restart-after-resume.service` came from. `open-fprintd-suspend.service` and `open-fprintd-resume.service` on the other hand are supposed to be a part of `open-fprintd` package. They are not designed to...

Hi Darren, > I applied "fix 3" from the other thread on this forum This is not a fix, it's a workaround. As someone mentioned, it is not how things...

Some devices are reported to be very similar, but I know nothing about this device in particular. Is it a match-on-chip device?

Then it is probably worth a shot. `python-validity` only supports match-on-chip devices at the moment. 0094 is not one of them, but if you have heaps of time, you can...

> When I rebooted to windows, it recognized I had fingerprints configured but would not accept them I guess that is intended. SIDs are no secret. Do you really want...

Looking at the .inf file, it appears that the driver GUID is the same as for `0097` and `009a` (`96710705-B080-4B29-A3EC-B16935AE663A`), which means that [synaWudfBioUsb-sandbox](https://github.com/uunicorn/synaWudfBioUsb-sandbox) approach might just work. Have you...

> There is no such file. Well, fwext is just an overlay on top of firmware in ROM. Perhaps it is not needed for this device. The .inf file has...

> What do you think of this? I think we can definitely try. Probably worth raising another issue with a correct usb id.