Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Skip to content

murena.io account synchronization quietly fails

  • /e/OS version: 2.9-a14-20250321478214-official-FP4
  • Device model(s): FP4
  • Impacted Application: /e/OS Account Manager
  • Affected application/URL: N/A
  • Browser/client and version: N/a

The problem

After some time using the phone with the Murena.io account for synchronization, the phone stopped synchronizing my data. Even if I go to the account sync settings (Settings>Accounts>###@murena.io>Account sync) and I click to refresh the individual options, it just spins the refresh icon for a while, then updates the date of the last synch to the current date. But then logging into https://murena.io shows that all the synchronized files are from last month - none of the newer files are there!

Steps to reproduce

  1. In the phone, go to the account sync settings (Settings>Accounts>###@murena.io>Account sync)
  2. Click twice to refresh the individual options (e.g. Pictures and videos)
  3. After the refresh icon stops spinning, log in to https://murena.io
  4. Check files, specifically directories where I know to be new files in my phone
  5. Fail to see new files.

Technical details

Paste any relevant logs (adb logcat) in the codeblock below if you have any

Excerpt from logcat around the synchronization (username scrubbed)

05-21 18:58:48.527  1887  2600 W InputReader: Received unexpected event (0x35, 0x362) for slot 0 with tracking id 19488
05-21 18:58:48.527  1887  2600 W InputReader: Received unexpected event (0x36, 0x7a0) for slot 0 with tracking id 19488
05-21 18:58:48.530  1149  1149 E QTI PowerHAL: Failed process_boost for boost_handle
05-21 18:58:49.189  1887  2600 W InputReader: Received unexpected event (0x35, 0x382) for slot 0 with tracking id 19489
05-21 18:58:49.189  1887  2600 W InputReader: Received unexpected event (0x36, 0x7ab) for slot 0 with tracking id 19489
05-21 18:58:49.192  1149  1149 E QTI PowerHAL: Failed process_boost for boost_handle
05-21 18:58:49.324  1887 10834 D ActivityManager: sync unfroze 30410 foundation.e.drive for 7
05-21 18:58:49.327 32308  3486 I davx5   : [syncadapter.SyncAdapterService] Sync request via sync framework (upload=false)
05-21 18:58:49.331 32308  3486 I davx5   : [syncadapter.SyncWorker] Enqueueing unique worker: sync foundation.e.drive.providers.MediasSyncProvider e.foundation.webdav.eelo/[SCRUBBED]@murena.io, with tags: [at.bitfire.davdroid.syncadapter.SyncWorker, sync foundation.e.drive.providers.MediasSyncProvider e.foundation.webdav.eelo/[SCRUBBED]@murena.io]
05-21 18:58:49.358 32308 32366 I WM-GreedyScheduler: Ignoring schedule request in a secondary process
05-21 18:58:49.370 14312 30138 I davx5   : [syncadapter.SyncWorker] Running sync worker: account=Account {name=[SCRUBBED]@murena.io, type=e.foundation.webdav.eelo}, authority=foundation.e.drive.providers.MediasSyncProvider
05-21 18:58:49.375 14312 30138 I davx5   : [syncadapter.SyncWorker] Starting onPerformSync for Account {name=[SCRUBBED]@murena.io, type=e.foundation.webdav.eelo}
05-21 18:58:49.376 14312 30138 I davx5   : [syncadapter.Syncer] foundation.e.drive.providers.MediasSyncProvider sync of Account {name=[SCRUBBED]@murena.io, type=e.foundation.webdav.eelo} initiated
05-21 18:58:49.376 14312 30138 I davx5   :      PARAMETER #0 =
05-21 18:58:49.376 14312 30138 I davx5   : [syncadapter.Syncer] foundation.e.drive.providers.MediasSyncProvider sync of Account {name=[SCRUBBED]@murena.io, type=e.foundation.webdav.eelo} finished
05-21 18:58:49.376 14312 30138 I davx5   :      PARAMETER #0 =
05-21 18:58:49.394 14312 30138 I davx5   : [syncadapter.SyncWorker] Sync completed successfully
05-21 18:58:49.395 14312 16360 I WM-WorkerWrapper: Worker result SUCCESS for Work [ id=5f7b2c14-2437-453e-8668-66213422748e, tags={ at.bitfire.davdroid.syncadapter.SyncWorker, sync foundation.e.drive.providers.MediasSyncProvider e.foundation.webdav.eelo/[SCRUBBED]@murena.io } ]
05-21 18:58:50.670  1150  1390 E sensors-hal: handle_sns_std_sensor_event:298, front_handle_sns_std_sensor_event upload hal_event.u.data[0] = 33.678787
05-21 18:58:50.671  1150  1390 E sensors-hal: handle_sns_std_sensor_event:298, front_handle_sns_std_sensor_event upload hal_event.u.data[1] = 446.520233
05-21 18:58:50.671  1150  1390 E sensors-hal: handle_sns_std_sensor_event:298, front_handle_sns_std_sensor_event upload hal_event.u.data[2] = 205.735718
05-21 18:58:50.671  1150  1390 E sensors-hal: handle_sns_std_sensor_event:298, front_handle_sns_std_sensor_event upload hal_event.u.data[3] = 160.975220