I managed to "solve" this problem!
What I did:
- Export everything in Linux to JEX-file
- Open that archive and list all *.MDs and resource -files what are bigger then 50MiB
- Remove those notes at Joplin-desktop
- Export (again) everything in Linux to JEX-file
- Delete local (.config/joplin*) storage
- Delete server (Joplin server) storage
- Delete Android Joplin data from phone
- Import that exported JEX back to Joplin-destop application
- Start to sync all documents to Joplin server
- Start Android synchronization and let it run multiple sync rounds
The main problem is of course "revisions". If you add a document, that "breaks" Android sync (like file size >50 MiB), and even if you remove it a few seconds later, the system tries to "replicate" it indefinitely.
The only way to solve the problem is to reset to whole revision history after you have managed to remove the breaking document.
Would it be "possible" to change that max resource size from 50 MiB to something (much) bigger?
OR change the code that way that if the replication system "sees" revision (add/modify) which resource size is bigger than it can handle, it would skip it or handle the situation some other way. (And alerting user that there is such problem --> user could try to fix it, or at least person knows that such document is missing in the Android phone)