@allesaufhorst yes, I was affected myself on my production device about a year ago, however when I excluded it from battery saving of Samsung the problem started to disappear, and now I can’t reproduce it anymore…
I think adb logs would maybe help a little bit. Personally I think this is a bug in Android, but maybe we can workaround it by putting a hard-coded “wait” time before every sync is processed - however that would be very dirty…