What to conclude when account settings do not list "frequency of calendar/contacts sync"?

[TheOtherDoctor]

I have two phones with identical DAVx5 settings, both importing the same two accounts. One one of these accounts, in the settings under sync I see only “frequency of task sync”, while all other (that is, the other account on same phone and both accounts on other phone) show all three, contacts & calendar & tasks frequency settings.

In addition, also the settings for history time limit and support for calendar colors etc are missing then, which I think is a consequence - the settings tab does not realize that this account has a calendar? Which is has, and the CALDAV tab shows them (and all three tabs, CARDDAV, CALDAV, and WEBCAL, are available).

Should I conclude that something is broken when the calendar settings are missing? The account clearly has plenty of entries. And the client (aCalendar+ on this device) also shows these entries.
The effect was reproduced on two Android 6 devices, and does not happen on Lineage 14 (Android 7). Sorry, no other devices to test.
DAVx5 3.1.1-gplay from june 14th.

Just would like to know: is something seriously stuck when the settings behave like the calendar is missing? Or is this just some known effect? Could not find any hint in the FAQs.

[rfc2822]

Please provide the debug infos. They probably contain worthful information to answer these questions.

[rfc2822]

I can reproduce the problem. Sync intervals are missing, which should not be the case.

[rfc2822]

The problem is only reproducible on my private phone, and I don’t have any idea how sync could be set to -1.

On other phones, everything works.

Do you have any idea how to cause this problem?

[TheOtherDoctor]

@rfc2822 That means you have now reproduced it and do not need additional debug info anymore? Else I’d have to ask which you specifically need … just the debug info text block or also generate a detailed run protocol …

For the relevant account, the debug dump reports, for both data groups which go to the android storage (address+calendar), the sync. interval as “-”, while the OpenTasks storage gets “60 min”;
and a bit down a corresponding:

getIsSyncable(CalendarContract): -1
getIsSyncable(OpenTasks): 1

[TheOtherDoctor]

@rfc2822 I just realized that working Lineage device has v 3.1-beta5-ose, while the stock android with the lost settings is v 3.1.1-gplay as mentioned above. Sorry, my fault, should have checked all versions in the beginning. Seems like fdroid update got stuck on the one which had the beta, just recovered and now installed 3.1-ose from 6.6.2020 there, which (for similar (but not totally identical) account setup) is still ok.
I had the vague feeling before it hasn’t been like this before. As consequence from the version difference, I now just speculate that this came with the 3.1.1?

[rfc2822]

Did you try uninstalling DAVx5 and installing it again?

[TheOtherDoctor]

@rfc2822 Not yet, simply because on one of the devices,I freshly installed DAVx5 for the 1st time yesterday… I took this as nearly-fresh-install - but if you think this has a chance, I’d try. Now I just regret having chosen hard passwords for my accounts.
If fails, another cross check idea would be uninstall via gplay and install the (older) version from fdroid…

Possibly worth noting: on these devices the global sync is off (as I have yet no clear idea how to activate it without big brother grabbing all my data, as mentioned elsewhere).
Another observation: Today I have seen at last on one of the phone a big google update from the play store. Did they do evil?

And just to be sure: Do I understand correctly that the missing setup means the scheduled sync will actually not work, thus I can stop for now trying with battery settings and the like?

[devvv4ever]

And just to be sure: Do I understand correctly that the missing setup means the scheduled sync will actually not work, thus I can stop for now trying with battery settings and the like?

Just for this questions: No, you should always disable any power saving feature for DAVx5, because all the syncs (also the one launched inside the account in DAVx5) are performed as background processes that could be killed by system controled power managemet “features”. A “Sync” will be handed over to the sync framework of Android which will then itself decide when the sync will really be performed - and this then launches DAVx5’s actual sync procedure.

[devvv4ever]

@TheOtherDoctor said in What to conclude when account settings do not list "frequency of calendar/contacts sync"?:

@rfc2822 That means you have now reproduced it and do not need additional debug info anymore? Else I’d have to ask which you specifically need … just the debug info text block or also generate a detailed run protocol …

The debug info would be useful for now, yes! Could you attach it here?

[TheOtherDoctor]

@devvv4ever yes, of course, here you are:

--- BEGIN DEBUG INFO ---

SOFTWARE INFORMATION
* at.bitfire.davdroid 3.1.1-gplay (301010002) from com.android.vending
* org.dmfs.tasks 1.2.3 (77600) from com.android.vending
* com.android.providers.contacts 6.0-XT1700_S143_190315_ROW (23)
* com.android.providers.calendar 6.0-XT1700_S143_190315_ROW (23)
* com.android.contacts 6.0-XT1700_S143_190315_ROW (23)
* cz.psencik.com.android.contacts 6.0.1p (37) from com.android.vending
* com.simplemobiletools.contacts.pro 6.12.0 (68)
* com.google.android.calendar 2020.18.5-313192754-release (2016607548) from com.android.vending
* ws.xsoh.etar 1.0.21 (23)
* org.withouthat.acalendarplus 2.3.4 (2003403) from com.android.vending

CONNECTIVITY (at the moment)
- [ Transports: WIFI Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&VALIDATED LinkUpBandwidth>=1048576Kbps LinkDnBandwidth>=1048576Kbps SignalStrength: -66]

CONFIGURATION
Power saving disabled: yes
Notifications (not blocked):
Permissions:
  READ_CONTACTS: granted
  WRITE_CONTACTS: granted
  READ_CALENDAR: granted
  WRITE_CALENDAR: granted
  READ_TASKS: granted
  WRITE_TASKS: granted
  ACCESS_COARSE_LOCATION: denied
System-wide synchronization: manually

APP SETTINGS
Distrust system certs: false
Override system proxy: false

ACCOUNTS
Account: userccc
  Address book sync. interval: 240 min
  Calendar     sync. interval: 30 min
  OpenTasks    sync. interval: 60 min
  WiFi only: true
  getIsSyncable(CalendarContract): 1
  getIsSyncable(OpenTasks): 1
  [CardDAV] Contact group method: GROUP_VCARDS
  [CalDAV] Time range (past days): 90
           Default alarm (min before): null
           Manage calendar colors: false
           Use event colors: false
Account: familie
  Address book sync. interval: —
  Calendar     sync. interval: —
  OpenTasks    sync. interval: 60 min
  WiFi only: true
  getIsSyncable(CalendarContract): -1
  getIsSyncable(OpenTasks): 1
  [CardDAV] Contact group method: GROUP_VCARDS
  [CalDAV] Time range (past days): 90
           Default alarm (min before): null
           Manage calendar colors: false
           Use event colors: false
Address book account: Kontakte (userccc lA)
  Main account: Account {name=userccc, type=bitfire.at.davdroid}
  URL: http://192.168.1.198:5232/userccc/c-memo.ics/
  Sync automatically: true
Address book account: FamilienAdressBuch (familie Rw)
  Main account: Account {name=familie, type=bitfire.at.davdroid}
  URL: http://192.168.1.198:5232/familie/alle.ics/
  Sync automatically: true

SQLITE DUMP
android_metadata
	|  locale |
	|  de_DE |
----------
settings
	|  setting | value |
	|  distrustSystemCerts | 1 |
----------
sqlite_sequence
	|  name | seq |
	|  service | 20 |
	|  homeset | 38 |
	|  collection | 27 |
----------
service
	|  id | accountName | type | principal |
	|  17 | familie | carddav | http://192.168.1.198:5232/familie/ |
	|  18 | familie | caldav | http://192.168.1.198:5232/familie/ |
	|  19 | userccc | carddav | http://192.168.1.198:5232/userccc/ |
	|  20 | userccc | caldav | http://192.168.1.198:5232/userccc/ |
----------
homeset
	|  id | serviceId | url | privBind | displayName |
	|  35 | 17 | http://192.168.1.198:5232/familie/ | 1 | familie |
	|  36 | 18 | http://192.168.1.198:5232/familie/ | 1 | familie |
	|  37 | 19 | http://192.168.1.198:5232/userccc/ | 1 | userccc |
	|  38 | 20 | http://192.168.1.198:5232/userccc/ | 1 | userccc |
----------
collection
	|  id | serviceId | type | url | privWriteContent | privUnbind | forceReadOnly | displayName | description | color | timezone | supportsVEVENT | supportsVTODO | supportsVJOURNAL | source | sync |
	|  15 | 18 | CALENDAR | http://192.168.1.198:5232/familie/ | 1 | 1 | 0 | familie | <null> | -7237283 | <null> | 1 | 1 | 1 | <null> | 0 |
	|  16 | 17 | ADDRESS_BOOK | http://192.168.1.198:5232/familie/alle.ics/ | 1 | 1 | 0 | addressen | ... | <null> | <null> | <null> | <null> | <null> | <null> | 1 |
	|  17 | 18 | CALENDAR | http://192.168.1.198:5232/familie/alle.icf/ | 1 | 1 | 0 | familie/alle.icf | <null> | -12434391 | <null> | 1 | 1 | 1 | <null> | 1 |
	|  18 | 18 | CALENDAR | http://192.168.1.198:5232/familie/usermmm.icf/ | 1 | 1 | 0 | familie/usermmm.icf | <null> | -1406150 | <null> | 1 | 1 | 1 | <null> | 1 |
	|  19 | 18 | CALENDAR | http://192.168.1.198:5232/familie/userjjj.icf/ | 1 | 1 | 0 | familie/userjjj.icf | <null> | -4588991 | <null> | 1 | 1 | 1 | <null> | 1 |
	|  20 | 18 | CALENDAR | http://192.168.1.198:5232/familie/userccc.icf/ | 1 | 1 | 0 | familie/userccc.icf | <null> | -8976807 | <null> | 1 | 1 | 1 | <null> | 1 |
	|  21 | 18 | CALENDAR | http://192.168.1.198:5232/familie/userfff.icf/ | 1 | 1 | 0 | familie/userfff.icf | <null> | -12937695 | <null> | 1 | 1 | 1 | <null> | 1 |
	|  22 | 18 | CALENDAR | http://192.168.1.198:5232/familie/info.icf/ | 1 | 1 | 0 | familie/info.icf | <null> | <null> | <null> | 1 | 1 | 1 | <null> | 1 |
	|  23 | 20 | CALENDAR | http://192.168.1.198:5232/userccc/ | 1 | 1 | 0 | userccc | <null> | -14729275 | <null> | 1 | 1 | 1 | <null> | 0 |
	|  24 | 19 | ADDRESS_BOOK | http://192.168.1.198:5232/userccc/c-memo.ics/ | 1 | 1 | 0 | Kontakte | <null> | <null> | <null> | <null> | <null> | <null> | <null> | 1 |
	|  25 | 19 | ADDRESS_BOOK | http://192.168.1.198:5232/userccc/c-archiv.ics/ | 1 | 1 | 0 | mehr addressen | ... | <null> | <null> | <null> | <null> | <null> | <null> | 0 |
	|  26 | 20 | CALENDAR | http://192.168.1.198:5232/userccc/c-archiv.icf/ | 1 | 1 | 0 | userccc/c-archiv.icf | <null> | -11915616 | <null> | 1 | 1 | 1 | <null> | 1 |
	|  27 | 20 | CALENDAR | http://192.168.1.198:5232/userccc/c-memo.icf/ | 1 | 1 | 0 | userccc/c-memo.icf | <null> | -3304124 | <null> | 1 | 1 | 1 | <null> | 1 |
----------
room_master_table
	|  id | identity_hash |
	|  42 | a7554d1ebc5ecfe0c7aefe271485d63c |
----------

SYSTEM INFORMATION
Android version: 6.0 (XT1700_S143_190315_ROW)
Device: motorola XT1700 (taidos_row)

--- END DEBUG INFO ---

Hope that helps… if this is just server side setup stupidity on my side, please excuse in advance…

[TheOtherDoctor]

@devvv4ever I am aware that I should disable any power saving things (if I could only ever be sure I didn’t skip over the relevant one - different story); with the question I just meant that, when I encounter sync issues on that device with this specific topic, any changes to those appkiller settings currently will now help as long as the issue described above is not solved. That is, I understand by now that the missing sync setting items is not just a minor layout issue but actually reflects a disabled sync.