"Move deleted items to recycle bin" is actually a copy process

[Nerdoholic]

Checklist

• I can reproduce the bug with the latest version given here.
• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Affected app version

1.13.1

Affected Android/Custom ROM version

Android stock Aug 2026, CP2A.260805.005

Affected device model

Pixel 8a

How did you install the app?

Google Play Store

Steps to reproduce the bug

Activate "move deleted items to recycle bin".
Delete a huge amount of files.
During the process, your phone will use [item batch size] x 2 storage, because the process is actually a copy.

Expected behavior

Move is move.
Copy is copy.
I do not expect my phone to use twice the storage of the item batch that I am currently deleting just for moving it to the recycle bin.

Actual behavior

The app bloats the storage used during the process to 2 x [batch size].

Screenshots/Screen recordings

No response

Additional information

If this is an Android limitation (quick search sounds like the OS moves stuff to the app's recycle bin itself??) then you need to do asynchronous work as to not bloat the storage.

E.g. in my case I had 2GB left for total storage, deleted 6GB... well that didn't happen :)
There never came an error message (progress is not implemented FossifyOrg/General-Discussion#120 I got that).

If there are no benefits/unwanted side effects with having to hand over to the OS in regards to recycle bin, maybe it even makes sense to just create your own recycle bin where you can then move (data kept within app vFS). You'll know more about that than I do :)

The bigger the operation becomes this is a complete performance mess (by design with copying not by your fault), not even counting the completely useless wear on the flash.