One feature that is being investigated and fixed is that when Sync is interrupted, files continue to be received and copied even after the interruption.
It is a bit large and will take some time.
It seems to be a bug created by the addition of Japanese language resources after I became the source maintainer.
In my view, this bug does not occur for people using in an English environment. It occurs only to those who use it in a Japanese environment.
If you are an experienced Android programmer, it would be faster to say that it is in R.string.
However, only the important part of the cancellation decision was written directly in English, without taking it from the resource.
Therefore, only when executing in a Japanese environment, the English and Japanese are compared, and the cancellation judgment is always false, and I could not break out of the Sync loop.
In this case, I reviewed all the resource strings in all the sources and corrected the direct writing so that they are properly taken from the resources.
The Sync interruption now succeeds even in Japanese environment.
Considering the volume of Japanese users, I will release it in the next beta release, but not immediately.
