wait, the fingerprint reader is working now? How do I enable it?

edit: also, not exactly a SFOS feature but OKBoard support is still missing on the Pro1

Fingerprint was introduced ~3 weeks ago to devel.

If you are on testing branch and did not update in last 2 weeks, a dist-upgrade should pull the changes.

There are few reports however of the settings option not being available in Jolla Settings. So you might already have sailfish-fpd-community package installed but not seeing UI options to configure.

In that case there is a testing app attached to this post to at least test the hardware.
But how to get it to working to unlock if settings options are missing is beyond me.

I cannot zypper dup, apparently; I get a bunch of "missing package" errors, mainly about "nothing provides libstdc++.so.6(CXXABI_1.3.9)"

Can you double check that you are currently running SFOS 3.3.0.16?

It smells like you are on sfos 3.2 still?
In that case update to 3.3.0.16 first.

Also you might check if you are in safe "testing" waters since on devel things changed frequently and our testing-user advise might not apply.
To change to testing see here

Thanks! I suppose that's what I was asking on the last page about how to update to the latest SFOS version. And thanks for the tip, I was indeed in devel and have now switched to testing.

I do note that after switching to testing, my Pebble stopped connecting. Have the bluetooth fixes not made it there yet?

I'm a complete idiot. My Pro1 is in a bootloop after I updated. I should have switched to testing. Especially, because I sacrificed my backup on my SD card for more Space for photos, while I was on holiday.

So I decided to reflash.
Unfortunately It seems like I totally killed my device.
When I try I get
(fastboot devices lists my device)

Any suggestions???

Had that issue when initially trying to flash SFOS onto the F(x)tec Pro1. Nothing to do but try multiple times and with different cables. Ended up working with a cable going from a USB-C port to a USB-A adapter to a USB-A to USB-C cable. Maybe a straight, proper, standards compliant USB-C 3.1 cable would work.

Have not been able to replicate it, so could have just been a fluke.

That behaviour has been reported before.
All reported flashing issues involved usb3 in some form and the advise to either use usb2 port or a usb2 hub solved all cases i know off.

@Fellfrosch,
Either it is usb3 problem, or if you got deeper trouble from the devel-update, revert to factory state using the Factory-Restore Tool maintained by tdm.

Viel Erfolg!

@taixzo,
Sorry to hear and it will not help you when i tell you that pebble connection should be possible in testing...
EDIT, just tested and it works on my end, but:
I had to restart the rockpool service from within rockpool dev-tools while it was connected shortly to not let it disconnect after some seconds. After that first hickup it connects reliably now "even" after reboot.