Vibration on sync


  • developer

    @der_Don Do you think there are steps to reproduce so that I can reliably reproduce the problem?



  • @rfc2822 I’ve tried several things but was not able to reproduce it.



  • Getting the same issue as @der_Don when completing tasks. Ghost notifications are back.

    @rfc2822 have you tried installing the previous version of DavDroid and OpenTasks, creating calendars and tasks, then updating DavDroid and OpenTasks to newest versions?

    EDIT: making sure to install latest DavDroid update and sync before updating OpenTasks.

    My install history from F-Droid says that DavDroid was updated, and then a couple days later (I believe because of other apps I installed in between, no timestamps), OpenTasks was updated. I run the privileged extension, so.

    This could ultimately be an issue with OpenTasks and not DavDroid.


  • developer

    @05nelsonm said in Vibration on sync:

    @rfc2822 have you tried installing the previous version of DavDroid and OpenTasks, creating calendars and tasks, then updating DavDroid and OpenTasks to newest versions?

    Not yet… I’d prefer to get steps to reproduce before, because I don’t have much time right now and we didn’t receive many reports until now (and it doesn’t happen on my device).

    Which exact OpenTasks version do you have? Play Store or F-Droid?


  • developer



  • @rfc2822 Fdroid



  • @rfc2822 that’s it! Not your problem anymore!

    Will follow their proposed solution and post over there.

    Ty for your help, much appreciated.



  • Thanks a lot.



  • In OpenTasks under Notifications --> Pinned Tasks. Disabling it and then reenabling it caused the option for vibrate to disappear and resolved my issue. Simply disabling the vibrate option did not work.



  • Hello, I’ve got the same symptoms since I guess last update. Each sync comes a vibration. Android 8.0.0 Samsung A3.
    Also found that an error “http 404 not found” appears, when just 4 out of six calendars are selected for sync. When all 6 are switched on, just the vibration thing. Here is the log of the last error described:

    — BEGIN DEBUG INFO —
    Account name: xxxxxx
    Authority: com.android.calendar

    HTTP REQUEST:
    Request{method=PROPFIND, url=, tags={}}
    <?xml version=‘1.0’ encoding=‘UTF-8’ ?><propfind xmlns=“DAV:” xmlns:CAL=“urn:ietf:params:xml:ns:caldav” xmlns:CARD=“urn:ietf:params:xml:ns:carddav”><prop><supported-report-set /><n0:getctag xmlns:n0="" /><sync-token /></prop></propfind>

    HTTP RESPONSE:
    Response{protocol=http/1.1, code=404, message=Not Found, url}
    <?xml version=“1.0” encoding=“utf-8”?>
    <d:error xmlns:d=“DAV:” xmlns:s="">
    <s:exception>Sabre\DAV\Exception\NotFound</s:exception>
    <s:message>Node with name ‘personal’ could not be found</s:message>
    </d:error>

    REMOTE RESOURCE:

    EXCEPTION:
    at.bitfire.dav4android.exception.NotFoundException: HTTP 404 Not Found
    at at.bitfire.dav4android.DavResource.checkStatus(DavResource.kt:356)
    at at.bitfire.dav4android.DavResource.checkStatus(DavResource.kt:338)
    at at.bitfire.dav4android.DavResource.processMultiStatus(DavResource.kt:432)
    at at.bitfire.dav4android.DavResource.propfind(DavResource.kt:325)
    at at.bitfire.davdroid.syncadapter.CalendarSyncManager$queryCapabilities$1.invoke(CalendarSyncManager.kt:64)
    at at.bitfire.davdroid.syncadapter.CalendarSyncManager$queryCapabilities$1.invoke(CalendarSyncManager.kt:41)
    at at.bitfire.davdroid.syncadapter.SyncManager.useRemote(SyncManager.kt:787)
    at at.bitfire.davdroid.syncadapter.SyncManager.useRemoteCollection(SyncManager.kt:808)
    at at.bitfire.davdroid.syncadapter.CalendarSyncManager.queryCapabilities(CalendarSyncManager.kt:62)
    at at.bitfire.davdroid.syncadapter.SyncManager$performSync$1.invoke(SyncManager.kt:117)
    at at.bitfire.davdroid.syncadapter.SyncManager$performSync$1.invoke(SyncManager.kt:55)
    at at.bitfire.davdroid.syncadapter.SyncManager.unwrapExceptions(SyncManager.kt:813)
    at at.bitfire.davdroid.syncadapter.SyncManager.performSync(SyncManager.kt:108)
    at at.bitfire.davdroid.syncadapter.CalendarsSyncAdapterService$CalendarsSyncAdapter.sync(CalendarsSyncAdapterService.kt:55)
    at at.bitfire.davdroid.syncadapter.SyncAdapterService$SyncAdapter.onPerformSync(SyncAdapterService.kt:73)
    at android.content.AbstractThreadedSyncAdapter$SyncThread.run(AbstractThreadedSyncAdapter.java:272)

    SOFTWARE INFORMATION

    • at.bitfire.davdroid 2.2.1-ose (262) from com.google.android.packageinstaller
    • com.android.providers.contacts 2.0.44 (204400000)
    • com.android.providers.calendar 1.0.00.35 (100000035)
    • com.samsung.android.contacts 3.8.20.9 (382000009)
    • com.simplemobiletools.contacts.pro 6.2.0 (40) from com.android.vending
    • com.samsung.android.calendar 4.4.04.7 (440400007) from com.sec.android.app.samsungapps
    • com.simplemobiletools.calendar.pro 6.2.1 (141) from com.android.vending

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

    CONFIGURATION
    Power saving disabled: yes
    android.permission.READ_CONTACTS permission: granted
    android.permission.WRITE_CONTACTS permission: granted
    android.permission.READ_CALENDAR permission: granted
    android.permission.WRITE_CALENDAR permission: granted
    org.dmfs.permission.READ_TASKS permission: denied
    org.dmfs.permission.WRITE_TASKS permission: denied
    System-wide synchronization: automatically
    Account:
    Address book sync. interval: 1440 min
    Calendar sync. interval: 1440 min
    OpenTasks sync. interval: —
    WiFi only: false
    [CardDAV] Contact group method: CATEGORIES
    [CalDAV] Time range (past days): 90
    Manage calendar colors: true
    Address book account: Kontakte ( PQ)
    Main account: Account {name=, type=bitfire.at.davdroid}
    URL:
    Sync automatically: true

    SQLITE DUMP
    android_metadata
    | locale |
    | de_DE |

    services
    | _id | accountName | service | principal |
    | 1 | | carddav | |
    | 2 | o.d | caldav | |

    sqlite_sequence
    | name | seq |
    | services | 2 |
    | homesets | 3 |
    | collections | 12 |

    homesets
    | _id | serviceID | url |
    | 2 | 1 | |
    | 3 | 2 | |

    collections
    | _id | serviceID | type | url | readOnly | forceReadOnly | displayName | description | color | timezone | supportsVEVENT | supportsVTODO | source | sync | privWriteContent | privUnbind |
    | 6 | 1 | ADDRESS_BOOK | | 0 | 0 | Kontakte | <null> | <null> | <null> | 0 | 0 | <null> | 1 | 1 | 1 |
    | 7 | 2 | CALENDAR | | 0 | 0 | ASH+ | <null> | -1593996 | <null> | 1 | 1 | <null> | 0 | 1 | 1 |
    | 8 | 2 | CALENDAR | | 0 | 0 | ASH | <null> | -531447 | <null> | 1 | 1 | <null> | 0 | 1 | 1 |
    | 9 | 2 | CALENDAR | | 0 | 0 | Erinnerungen | <null> | -4144960 | <null> | 1 | 1 | <null> | 1 | 1 | 1 |
    | 10 | 2 | CALENDAR | | 0 | 0 | Geburtstage | <null> | -8853644 | <null> | 1 | 1 | <null> | 1 | 1 | 1 |
    | 11 | 2 | CALENDAR | | 0 | 0 | Persönlich | <null> | -1 | <null> | 1 | 1 | <null> | 1 | 1 | 1 |
    | 12 | 2 | CALENDAR | | 0 | 0 | Dienstplan | <null> | -16744193 | <null> | 1 | 1 | <null> | 1 | 1 | 1 |

    SYSTEM INFORMATION
    Android version: 8.0.0 (R16NW.A320FLXXU3CRH2)
    Device: samsung SM-A320FL (a3y17lte)

    — END DEBUG INFO —


  • developer

    Updating OpenTasks and/or DAVx⁵ to the latest available version should always solve this problem. Can somebody confirm that?



  • @rfc2822 said in Vibration on sync:

    to the latest available version

    Which exactly?

    DAVx⁵ 2.1.1-ose, Tasks 1.1.15, both from F-Droid. The problem still present.


  • developer

    @sergio DAVx⁵ 2.1.x should work; but OpenTasks 1.1.16, as far as I know (or just use the workaround from above)



  • Looks like @der_Don 's workaround fixes this issue.



  • @sergio Workaround still works (using DAVx⁵ 2.2.1-ose and OpenTasks 1.1.15), however, once I check a task as done in OpenTasks the issue returns with the next sync.
    Now I’m using aCalendar+ as calendar app and OpenTasks to sync tasks. When I get a notification for a due task, I just check it as done in the aCalendar+ notification. Notifications from OpenTasks are deactivated. A sync thereafter does not trigger Vibration.
    So the Vibration only happens after checking within the OpenTasks notification.


 

Maybe you're interested in these topics?

  • 13
  • 8
  • 2
  • 1
  • 2