DAVX5 + aCalendar + sync immediately

[wehkah]

Hello,

I am using Davx5 to synch aCalendar on my phone and my Nextcloud. My phone is a OnePlus 8Pro running LineageOS 22.2 (Android 16). Periodical synching works fine. The only thing that does not work is the option to sync immediately when local changes are made. To my understanding this means: I can create a new meeting in aCalendar on my phone and Davx5 will not wait till the next periodical sync is due, it will instead sync this change immediately to my Nextcloud.

This is the one thing that does not work. The new meeting will only be synched when the next "chron job" is due, or if I tell aCalendar to sync now.

Does anyone experience the same issue?

I checked and double checked all settings related to battery usage and priorities I could find. But maybe I forgot some settings. Because my phone is not running the stock ROM, I don't think the misbehaviour is caused by quirks done by OnePlus. I may be wrong, though!

Does immediate synching work with other calendar apps? Maybe there's some "misunderstanding" between the two apps, preventing Davx5 to fire up an immediate synchronisation?

I's be thankful to hear some experiences by other users.

[rfc2822]

Did you try with 4.5.18? There was a bug that could cause sutble problems with starting syncs.

[wehkah]

The app says it's version 4.5.18-gplay.

[rfc2822]

The only thing that does not work is the option to sync immediately when local changes are made. To my understanding this means: I can create a new meeting in aCalendar on my phone and Davx5 will not wait till the next periodical sync is due, it will instead sync this change immediately to my Nextcloud.

True, however "immediately" means "within a minute or so". The sync framework (the intermediate layer that receives the changes from the calendar provider/apps and triggers the DAVx5 sync) usually takes a minute or so until it schedules the next sync, so that you can do further changes in the calendar, edit the event again etc without spamming synchronizations.

How long did you wait? Normally it shouldn't take longer than one or two minutes. (Just tested here [also using aCalendar+, but shouldn't matter] and it took ~ 1 min).

How long did you wait?

Note that the sync framework may impose additional restrictions: when global sync is not active in Android settings, when data saver/energy saving is active and when "storage is low" (which can actually mean there are a few GB left, it's hardcoded in the sync framework). You can check the DAVx5 debug info and look for "storage left" and whether there's a "low on storage!" warning or something like that.

[wehkah]

I waited for several minutes, before I initiated a synchronisation manually. I'm also using aCalendar+, I just forgot the "+" above.

[wehkah]

Which OS or which Android version are you using?

[rfc2822]

Did you check the debug info for "low storage"?

If that doesn't help, please:

1. Enable verbose logging in DAVx5
2. Create/edit an event in a davx5-synced calendar in aCalendar+ (maybe you choose a non-davx5-account by accident?)
3. Leave aCalendar+
4. Wait 5 min
5. Send the verbose logs to https://www.davx5.com/support

[schmitzkr]

I think I've hit the same underlying issue, with a bit more evidence that might help narrow it down.

Device: OnePlus CPH2583, stock OxygenOS, Android 16
DAVx5: 4.5.18-ose (F-Droid)

Same symptom as OP: periodic sync (every 4h) and DAVx5's own in-app "Sync now" both work fine (tested directly), but anything that's supposed to trigger a sync sooner via the sync framework, like a third-party app's own "refresh" action or Tasks.org's manual sync, does nothing. Not "takes a minute or so longer," but genuinely nothing, confirmed over an hour+ of waiting.

What I checked, since global-sync-off and low-storage were the two things suggested above:

• System-wide sync is on ("Automatically sync data" enabled)
• 293GB free internal storage, no "low on storage" warning anywhere in DAVx5's own debug info export
• App standby bucket: exempted; battery optimization: exempted; not in power-save mode

Reproduction, isolating it from any single app:

1. My default calendar app has a "refresh CalDAV" menu action. Used it, then immediately pulled DAVx5's debug info (Settings > Debug info) and checked the syncstats table (has real per-collection lastSync epoch timestamps). No new rows; identical dump to one pulled before the refresh, down to the same sqlite_sequence counter.
2. Separately, added a new task with a due date directly in Tasks.org (registered as its own OpenTasks-compatible provider under authority org.tasks.opentasks, confirmed via preferred_tasks_provider in DAVx5's debug info; I don't have the separate standalone OpenTasks app installed). Got the "Created event / Open" snackbar, tapped Open, and the calendar app said "Event not found. Please enable CalDAV sync for the appropriate calendar." So Tasks.org's own manual-sync trigger produced the identical no-op.

Since two independent, unrelated apps using the sync framework the intended way both fail identically, while DAVx5's own internal sync paths (periodic and manual) work fine, this doesn't look like an app-specific integration bug. It looks more like the sync framework itself isn't dispatching to DAVx5's sync adapter on this device at all when triggered by anything other than DAVx5's own scheduled/manual sync paths (which go through WorkManager directly, not the classic sync-adapter callback).

Also checked for an OnePlus-specific "Autostart"/"Allow auto-launch" toggle beyond the standard battery-optimization exemption, but couldn't find one on this OxygenOS build, so if that's the actual cause, it may not be user-toggleable here.

Happy to pull more from the debug-info export or try anything else that would help narrow this down. This looks like the exact same bug, just with a slightly different device (OnePlus CPH2583 stock OxygenOS vs. OP's OnePlus 8 Pro on LineageOS), so it doesn't seem tied to a specific ROM either.

[Benjamin-Loison]

Figuring out an Android setting for the synchronization on local change to be immediate and not unknown waiting duration would help investigating this bug (Fairphone 4 LineageOS 23.2 Etar here).