3. DAVx5 tries to sync even if set to manual

DAVx5 tries to sync even if set to manual

  • J

    I’ve set DAVx5 to manual sync. But DAVx5 synchronizes anyway. As I are usuall not connected to the right network (VPN), it failes.
    How can I forve DAVx5 to honour the manual sync setting?

    0 1 Reply
  • R
    developer

    Which calendar app do you use? When does DAVx⁵ synchronize?

    0
    J
     1 Reply

  • @jochen Do you use any other apps that control system sync? Can you post your DAVx⁵ debug info please (found in the DAVx⁵ app settings at the top).

    0
    J
     1 Reply
  • J

    @rfc2822 I’m using aCalendar+. The sync events are tried every 1 or 2 hours. If it’s important I’ll log it.

    0
    R
     1 Reply
  • J

    @devvv4ever

    1. Not that I know about.
    2. debug log follows. I have replaced personal information by “[removed1]” and “[removed2]” for URLs of server1 and server2.
      — BEGIN DEBUG INFO —

    SOFTWARE INFORMATION

    • at.bitfire.davdroid 2.5.1-gplay (291) from com.android.vending
    • org.dmfs.tasks 1.1.18 (74800) from com.android.vending
    • com.android.providers.contacts 4.70.49 (470004900)
    • com.android.providers.calendar 4.4.7 (404007000)
    • com.android.contacts 4.70.49 (470004900)
    • org.openintents.filemanager 2.2.3 (40) from com.google.android.feedback
    • org.withouthat.acalendarplus 2.1.5 (2000215) from com.android.vending

    CONNECTIVITY (at the moment)
    Active connection: WiFi, CONNECTED

    CONFIGURATION
    Power saving disabled: no
    android.permission.READ_CONTACTS: granted
    android.permission.WRITE_CONTACTS: granted
    android.permission.READ_CALENDAR: granted
    android.permission.WRITE_CALENDAR: granted
    org.dmfs.permission.READ_TASKS: granted
    org.dmfs.permission.WRITE_TASKS: granted
    android.permission.ACCESS_COARSE_LOCATION: denied
    System-wide synchronization: automatically
    Account: xxx@yyy.zzz
    Address book sync. interval: manually
    Calendar sync. interval: manually
    OpenTasks sync. interval: manually
    WiFi only: false
    [CardDAV] Contact group method: CATEGORIES
    [CalDAV] Time range (past days): 30
    Manage calendar colors: true
    Use event colors: true
    Account: aaa@bbb.ccc
    Address book sync. interval: manually
    Calendar sync. interval: manually
    OpenTasks sync. interval: manually
    WiFi only: true
    [CardDAV] Contact group method: CATEGORIES
    [CalDAV] Time range (past days): 30
    Manage calendar colors: true
    Use event colors: false
    Address book account: Kontakte (removed2)
    Main account: Account {name=xxx@yyy.zzz, type=bitfire.at.davdroid}
    URL: https://[removed2]
    Sync automatically: true
    Address book account: gemeinsam (xxx@yyy.zzz)
    Main account: Account {name=xxx@yyy.zzz, type=bitfire.at.davdroid}
    URL: https://[removed2]
    Sync automatically: true
    Address book account: Kontakte (aaa@bbb.ccc)
    Main account: Account {name=aaa@bbb.ccc, type=bitfire.at.davdroid}
    URL: https://[removed1]
    Sync automatically: true
    Address book account: Contacts (aaa@bbb.ccc)
    Main account: Account {name=aaa@bbb.ccc, type=bitfire.at.davdroid}
    URL: https://[removed2]
    Sync automatically: true

    SQLITE DUMP
    android_metadata
    | locale |
    | de_DE |

    sqlite_sequence
    | name | seq |
    | service | 57 |
    | homeset | 1577 |
    | collection | 1495 |

    service
    | id | accountName | type | principal |
    | 32 | xxx@yyy.zzz | carddav | https://[removed2]/ |
    | 33 | xxx@yyy.zzz | caldav | https://[removed2]/ |
    | 56 | aaa@bbb.ccc | carddav | https://[removed1]/ |
    | 57 | aaa@bbb.ccc | caldav | https://[removed1]/ |

    homeset
    | id | serviceId | url |
    | 797 | 32 | https://[removed2]/ |
    | 1559 | 56 | https://[removed1]/ |
    | 1560 | 57 | https://[removed1]/ |
    | 1561 | 57 | https://[removed1]/ |
    | 1562 | 57 | https://[removed1]/ |
    | 1563 | 57 | https://[removed1]/ |
    | 1564 | 57 | https://[removed1]/ |
    | 1565 | 57 | https://[removed1]/ |
    | 1566 | 57 | https://[removed1]/ |
    | 1567 | 57 | https://[removed1]/ |
    | 1568 | 57 | https://[removed1]/ |
    | 1569 | 57 | https://[removed1]/ |
    | 1570 | 57 | https://[removed1]/ |
    | 1571 | 57 | https://[removed1]/ |
    | 1572 | 57 | https://[removed1]/ |
    | 1573 | 57 | https://[removed1]/ |
    | 1574 | 57 | https://[removed1]/ |
    | 1576 | 33 | https://[removed2]/ |
    | 1577 | 57 | https://[removed1]/ |

    collection
    | id | serviceId | type | url | privWriteContent | privUnbind | forceReadOnly | displayName | description | color | timezone | supportsVEVENT | supportsVTODO | supportsVJOURNAL | source | sync |
    | 1045 | 32 | ADDRESS_BOOK | https://[removed2]/ | 1 | 1 | 0 | Kontakte | <null> | <null> | <null> | 0 | 0 | <null> | <null> | 1 |
    | 1046 | 32 | ADDRESS_BOOK | https://[removed2]/ | 1 | 1 | 0 | xxx | <null> | <null> | <null> | 0 | 0 | <null> | <null> | 1 |
    | 1465 | 56 | ADDRESS_BOOK | https://[removed1]/ | 1 | 1 | 1 | Contacts | <null> | <null> | <null> | 0 | 0 | <null> | <null> | 1 |
    | 1466 | 56 | ADDRESS_BOOK | https://[removed1]/ | 1 | 0 | 0 | Kontakte | <null> | <null> | <null> | 0 | 0 | <null> | <null> | 1 |
    | 1467 | 56 | ADDRESS_BOOK | https://[removed1] | 1 | 0 | 0 | Resources | <null> | <null> | <null> | 0 | 0 | <null> | <null> | 0 |
    | 1468 | 57 | CALENDAR | https://[removed1]/ | 1 | 0 | 0 | Kalender | <null> | <null> | <null> | 1 | 0 | 0 | <null> | 1 |
    | 1469 | 57 | CALENDAR | https://[removed1]/ | 1 | 0 | 0 | Aufgaben | <null> | <null> | <null> | 0 | 1 | 0 | <null> | 1 |
    | 1470 | 57 | CALENDAR | https://[removed1]/ | 1 | 0 | 0 | Journal | <null> | <null> | <null> | 0 | 0 | 1 | <null> | 0 |
    | 1475 | 57 | CALENDAR | https://[removed1]/ | 0 | 0 | 0 | Calendar | <null> | <null> | <null> | 1 | 0 | 0 | <null> | 0 |
    | 1476 | 57 | CALENDAR | https://[removed1]/ | 0 | 0 | 0 | Kalender | <null> | <null> | <null> | 1 | 0 | 0 | <null> | 0 |
    | 1477 | 57 | CALENDAR | https://[removed1]/ | 1 | 0 | 0 | Calendar | <null> | <null> | <null> | 1 | 0 | 0 | <null> | 0 |
    | 1478 | 57 | CALENDAR | https://[removed1]/ | 1 | 0 | 0 | Journal | <null> | <null> | <null> | 0 | 0 | 1 | <null> | 0 |
    | 1479 | 57 | CALENDAR | https://[removed1]/ | 1 | 0 | 0 | Tasks | <null> | <null> | <null> | 0 | 1 | 0 | <null> | 0 |
    | 1487 | 33 | CALENDAR | https://[removed2]/ | 0 | 0 | 0 | Geburtstage von Kontakten | <null> | -54 | <null> | 1 | 0 | <null> | <null> | 0 |
    | 1488 | 33 | CALENDAR | https://[removed2]/ | 1 | 1 | 0 | Feiertage | <null> | -65536 | <null> | 1 | 1 | <null> | <null> | 1 |
    | 1489 | 33 | CALENDAR | https://[removed2]/ | 1 | 1 | 0 | Ferien | <null> | -3486771 | <null> | 1 | 1 | <null> | <null> | 1 |
    | 1490 | 33 | CALENDAR | https://[removed2]/ | 1 | 1 | 0 | xxx.ics | <null> | -8035041 | <null> | 1 | 1 | <null> | <null> | 1 |
    | 1491 | 33 | CALENDAR | https://[removed2]/ | 0 | 0 | 0 | yyy.ics | <null> | -37165 | <null> | 1 | 1 | <null> | <null> | 1 |
    | 1492 | 33 | CALENDAR | https://[removed2]/ | 1 | 1 | 0 | Jahrestage | <null> | -4259780 | <null> | 1 | 1 | <null> | <null> | 1 |
    | 1493 | 33 | CALENDAR | https://[removed2]/ | 1 | 1 | 0 | zzz.ics | <null> | -15463486 | <null> | 1 | 1 | <null> | <null> | 1 |
    | 1494 | 57 | CALENDAR | https://[removed1]/ | 0 | 0 | 0 | Calendar | <null> | <null> | <null> | 1 | 0 | 0 | <null> | 0 |
    | 1495 | 57 | CALENDAR | https://[removed1]/ | 0 | 0 | 0 | Calendar | <null> | <null> | <null> | 1 | 0 | 0 | <null> | 0 |

    room_master_table
    | id | identity_hash |
    | 42 | 646131aecfaa7b0c69893e2374fb2da3 |

    SYSTEM INFORMATION
    Android version: 6.0 (MRA58K)
    Device: LGE LG-H815 (p1)

    — END DEBUG INFO —

    0
  • R
    developer

    @jochen said in DAVx5 tries to sync even if set to manual:

    @rfc2822 I’m using aCalendar+. The sync events are tried every 1 or 2 hours. If it’s important I’ll log it.

    Yes, would be important. In the logs, we can see the sync flags which may be helpful in seeing what forced the sync.

    Please note that DAVx⁵ doesn’t manage syncs by its own, but relies on the Android sync framework, where every app can request/force-request a sync of any account.

    0
    J
     1 Reply
  • J

    @rfc2822 Here are a few sync times. As newer messages replaces the previous it’s not a complete list:

    09:17 Contacts [removed1]
    09:21 Contacts [removed1]
    12:23 Kontakte [removed1]
    06:48 Kontakte [removed1]
    08:09 Contacts [removed1]

    I only get messages for one account as it’s the account without server connection (only VPN on demand).

    0
  • R
    developer

    Can you enable verbose DAVx⁵ logging? There should be a line like that: $authority sync of $account has been initiated + the sync flags, which might indicate the reason of sync

    0
    J
     1 Reply
  • J

    @rfc2822 I enabled “Ausführliche Protokollierung” in DAVx5 settings now.
    Where can I later see the logs?

    0
    R
     1 Reply
  • R
    developer

    @jochen You can send it from the notification: https://forums.bitfire.at/post/10773

    0
    J
     1 Reply
  • J

    @rfc2822 Here is the log file. Again I had to anonymize it a bit.
    davx5-log.txt

    0
    R
     1 Reply
  • R
    developer

    @jochen Thanks.

    2019-07-04 12:09:57 2 [syncadapter.SyncAdapterService] com.android.contacts sync of Account {name=Contacts (aaa@bbb.ccc.de 2A), type=at.bitfire.davdroid.address_book} has been initiated
    PARAMETER #0 =

    There was no “manual” or “forced” sync argument, so this sync has been initiated normally. Unfortunately, I can’t say why. Note that DAVx⁵ doesn’t call synchronization itself, but is called by the Android sync manager. Setting a sync interval to “manually (+ immediately after local changes)” means that automatic sync is disabled for this account in the Android sync manager, but any app can still initiate a sync. So, I think your syncs are initiated

    • either because of local changes – are you sure that you (or any apps) didn’t change a contact before the syn was initiated?
    • by some other app (any app can initiate a sync – for instance, your contacts app could do that when you open it to get an up-to-date contact list; automation apps, or something else)
    0
    J
     1 Reply
  • J

    @rfc2822 said in DAVx5 tries to sync even if set to manual:
    So, I think your syncs are initiated

    • either because of local changes – are you sure that you (or any apps) didn’t change a contact before the syn was initiated?

    Yes, I am sure for that.

    • by some other app (any app can initiate a sync – for instance, your contacts app could do that when you open it to get an up-to-date contact list; automation apps, or something else)

    I automatically disable serveral auto sync settings of Google. Shall I include DAVx5?
    (Tasker; SecureTask; disable sync; i.e. com.google.android.gms.auth.accountstate).

    0
    J
     1 Reply
  • J

    I said in DAVx5 tries to sync even if set to manual:

    I automatically disable serveral auto sync settings of Google. Shall I include DAVx5?
    (Tasker; SecureTask; disable sync; i.e. com.google.android.gms.auth.accountstate).

    Disabled it, did not help. Even without that I get these sync messages.

    0
    R
     1 Reply
  • R
    developer

    @jochen I see. Maybe you can find something in the system adb logs…

    0
    J
     1 Reply
  • J

    @rfc2822 I assume something like

    command_bus: in onInput(o)  > davx5.l

    is not helpful? The system log is too big to record it one hour.

    0
    R
     1 Reply
  • R
    developer

    @jochen I have no idea what that means

    0
Log in to reply
 

Similar topics