An easy “wakelock” solution is to use Tasker with a simple profile that keeps the screen on for “24/hrs”, or however long you want to set it for. I have a “screen on” task setup for a handful of apps that I don’t want timing out the minute I set the tablet down.
this was really just an idea to make icsdroid even more attractive and because I didn’t know about etag support in icsdroid. I just checked and most of my feeds do, I just wrote to teamup.com support to ask if they could add it
And it came to mind for the other use-case I described (respecting the cache-timeout header if the server sends one) because per-collection sync would be a prerequisite.
Honestly, icsdroid works great for me, this is just to foster it’s position as the best tool available 8-)
The problem vanished
I think it was related to an OwnCloud problem that also lead to degrading contact pictures in my case. After updating OwnCloud from 7.0 to 7.0.1, the issue with the contact pictures is gone and since then no speed dial assignment got reset. I also updated DAVdroid to the current version in between.
I don’t think this is a good idea, especially because it breaks the whole sync logic and is a dirty hack and creates behavior which can’t be understood by users.
no problem - our users (corporate users connecting to openCRX) are actually more disturbed by the fact that the sync process breaks because of the various 403-Forbidden messages - as long as an address book (or it’s contacts, respectively) cannot be locked down properly if a collection is marked as read-only, it’s just a matter of time until the client doesn’t sync anymore because the user (or some other app running on the device) has made changes to a contact…
anyway, we have adapted the behavior on the server-side such that DAVdroid does not receive 403-Forbidden anymore - the server claims to accept the create- or update-request but actually ignores it and ensures that any (forbidden) changes on the Android devices are simply undone with the next sync (from the admin’s perspective it’s much better to annoy/educate the user than to break the sync account)
and ideally Android gets it’s act together and supports read-only contacts and/or address books