Oh, I thought that "broken" files might also make their way to that folder, like videos that weren't finalized (like mentioned here:
How To Recover Deleted Media Files From LOST.Dir on External SD Card.
Nothing in there about "videos that weren't finalized". If you're streaming video to storage, there will be a partial "file" streamed, and if the phone gets restarted during the recording, what happens depends on the app. If it was allocating space as it needed it, there
will be allocated space not associated with a file, and that
can be recovered (but not with their software - PhotoRec
would do that kind of recovery). But if the video is in RAM when the phone restarted, it will be gone. In neither case will it be "recovered" to LOST.DIR
"Broken" files, those that are corrupted, are just not what the app that's trying to open them expects. Rename an .mp4 file to .mp3, and open it in a file manager, and you have a broken file.
It's not a sound file, even though "mp3" says it should be. As far as he
file system is concerned, there's nothing wring with a file like that. It really starts where the directory says it does, it really exists in all the inodes (or clusters in exFAT) that the table says it does, it's the size the directory says it is ... it's just that the app that
should be able to open it can't.
Files that end up in LOST.DIR are usually 2 types - when the phone glitches and you suddenly lose a lot of files, they may end up there - with sequential numbers for names. Or if you remove the SD card before all files have been written to it - files in the process of being written aren't complete. Either the last inode or two isn't written, or the directory entry isn't finished - something is still left to be done. A file in that state may become a "lost" file.
Contrary to all the articles, files being
readwon't cause that. When they say "read/write state", read "being written". Reading a file doesn't change anything.