magnus

@Metske I saw that you forked java-fs, any luck with updating from jnode master?

What happens if you remove the comment you added, and use the other FAT32 implementation? Maybe there are some recent fixes.

So the file is empty but has a chain? Not sure if that is correct ... Related to https://github.com/magnusja/libaums/issues/112 maybe?

Unfortunately not, I would need to prepare a test case for this first and see if I can reproduce this.

Do you think it could be related to https://github.com/magnusja/libaums/issues/298

You need to download libusb 1.0.25 and set `libusb.dir` to the path where you extracted the source tarball. See gitlab ci for more info. https://github.com/magnusja/libaums/blob/566a5a9c8dd64a32fc1627b5d7de383d79abe12d/.github/workflows/android.yml#L16-L19

1.0.25 is supported as well yes. So yeah what you are basically saying there is a bug in my fat32 implementation, that is what I suspected :D As it is...

This is 100% optional. With that you are including two LGPL libraries, namely JNode OS and libusb. The libaums core is apache only. This library is structured in modules, see...

As mentioned earlier, you are using the JNode OS file system implementation. This implementation does not have the same bug as my fat32 implementation has. I dont think using libusbcommunication...

Seems that there is no end marker in the cluster chain Might be related to #247