I’m running owncloud 10.0.0.4 on a slow system and requesting a contact sync >450 entries (with pictures).
As far as i’m able to judge the client is requesting the whole addressbook and after timeout exception it want to retry a request of 10 entries. At this time the server is still running at 100% cpu duty collecting the previous request.
That leads to a bunch of apache instances on server-side which freezes the system for a couple of minutes and the client isn’t getting it’s requests within it’s (too short and unconfigurable) timeout.
For reference: setting the timeout to 180sec would very likely fix this problem
Small glitch in 22.214.171.124-gplay / Sync Schedule
There is a small glitch at least in 126.96.36.199-gplay Version. If you change the Sync Schedule for a Account from for example 120 Minutes to 240 Minutes, the Dropdown closes, but the old Sync Schedule remains as Description in the Overview. However if you leave the screen and you come back, you can see that the new Sync Schedule is successfully set.
No big problem, only a cosmetic thing.
Thanks for the reminder, I have already noticed that and thought https://gitlab.com/bitfireAT/davdroid/commit/712467d933edb012ad476449187d85f5b0e92522 would fix it. But it seems like it doesn’t, and now I don’t have further ideas anymore. Merge requests are welcome.
Maybe fixed with https://gitlab.com/bitfireAT/davdroid/commit/e767dcbf381573d7e10d7e28cf8dc59d06ede23c. It seems to work in the emulator, but I can’t tell it anymore, because Android behaves very randomly since Android 7 (i.e. the ContentResolver status change listener is not called when the sync interval is changed).
Wow thats fast. Could you please send me a compiled *.apk, since i didn’t have a SDK installed. Or will this be released in some given timeframe?
@Sout1983 Will be included in the next release, but I have sent an APK too. Does it work on your device?
Thx. for the APK. After installing it, it works as expected. Thx for the fast Fix.