Android Filesystem Sync - 99% reliable

Operating system

Android

Joplin version

3.0.8

Desktop version info

3.0.15

Sync target

File system

What issue do you have?

having 4735 notes in 64 folders perfectly in sync at 2 windows computers...
..my android phone shows at sync status "Note: 4739/4737"

My usual strategy to get Android in sync with windows is:

  • copy all note-info manually from the missing note without changing anything to a new note
  • delete the original note
  • sync => done

Didn't check for a while - today I found out, that
a) some folders at android contained more notes than windows
=> sync android=>windows broken
b) other folders at android contained less notes than windows
=> sync android<=windows broken

So much more than "2 or 4" regarding how to read the android sync stats are missing sync.
...so about 50 notes have not been synched from android to windows and
54 different notes are missing in the other direction lead to a saldo of 4...

Any idea how to efficiently determine which notes are missing in which direction?

...right now I'm trying "caffeine"-Android App so the mobile might be able to synch at night.

[Battery optimizations for joplin are disabled anyway]

You may be affected by Sync silently ignores new files with old timestamps · Issue #6517 · laurent22/joplin · GitHub.

thank you for the quick reply!

I didn't mention it, but I discovered the issue yesterday as I made a new note at the Windows-Client and it didn't appear even after x* manual "syncronisations" at the Android Client...

After
a) installing "caffeine"-App keeping the phone active
b) starting the sync manual, one time it ran for 2 hours fetching thousands notes
=> still 31 notes not synched from windows to android and 49 notes not synched in the other direction => those could be issue 6517.

But, that (I assume) android 13 is making it impossible to fully synch since it - even without power-limitations for joplin - shuts Joplin down after some minutes
=> In the "old API"-Implementation with much quicker file-system-access this was no issue since Joplin easily could finish it's sync-jobs before getting shut down by Android...
=> Is there no chance to increase Joplins priority at the Android scheduler?