Sorry, I saw your posts and links after scrubbing the phone tonight. Long story short, Moto Camera (from Play Store) works with 0104 but not 0113. But I discovered a new problem with Termux on both builds.Don't clean flash. Try this flashable version of Moto Camera. Its working.
Before deciding to start clean, the first and easiest thing to try was Props Config and a different fingerprint, but Termux wouldn't start and crashed the same way as Moto Camera. This put me in the mood to clean so I formatted and flashed 0113 along with Open Gapps and Magisk. Termux and Moto Camera were the next apps installed and neither would start.
Next I did the same with 0104, etc. Moto Camera started and works normally but Termux still crashes. With earlier AOSiP builds there were problems with Termux although it was running fine for me at the time. Dig back a few months in this thread and you'll find comments about it.
No, Keepass2Android never hung the phone before until build 0113. Normally jumping to the password field is the next step if biometric access doesn't work for whatever reason. It doesn't take much to interfere with print reading but I've always considered that normal. So fingerprint auth is never guaranteed but it seemed extra peculiar with this latest build.So, you had problems with Keepass2Android in previous builds?
I'm really pleased about performance and stability with both January builds. And both easily pass SafetyNet and certify with Play Store without Props Config. I saw that Snap came with both releases so I beg your pardon for saying earlier today that "no camera at all" was bundled.