I can confirm that 3.3.5 from F-Droid no longer has this issue. Thanks for the quick turnaround!