Hi,
To support the project and make a further step towards the abandonment of mainstream software services, I subscribe for the Murena workspace paid plan. The problem is I’m not understanding how it works.
Apart from the contacts in the address book, in relation to which, by the way, I lost some contacts when switching to the paid plan, the files I see in my device are different from those I see when accessing via the browser. My question is: where do I find the settings for deciding which folders to synchronise and how do I synchronise them?
How does eDrive sync work? → the second heading explains where the general sync settings are. But upfront: you can’t decide what is synced outside the static folders given in the help article. If your web based view has more files outsides those folders - those won’t be synced with the default (“eDrive”) sync app.
I haven’t found a help article easily that shows the basic account onboarding process when it’s done at a later time than first-time-setup.
It’s in Settings → Accounts → Add Account … and choose the Murena.io type - I was unsure if you got to that point.
make a backup of your devices contacts in a .vcf file in any case, Android contacts management is too advanced for its own good.
It can conflict (for the uninitiated) with “device-local” contacts, so worst case you reimport the .vcf created prior and converge on what is in the synced murena.io-addressbook.
Based on the link you provide me maybe the sync is not working. The files I have on the Device locations “/storage/emulated/0/Documents” and “/storage/emulated/0/Pictures” are not the same I have on the Cloud locations “/Documents” and “/Pictures”. To give an example
I have a similar problem. When I recently updated to /e/OS 2.9, my phone, for the first time since the Murena cloud issues started many months ago, started syncing to Murena cloud.
I did a cursory check of notes and photos and notes from the default notes app do sync correctly.
But photo sync from the default photo folder is still broken. With default folder I mean internal storage/DCIM/Camera/ on the phone and on the cloud it is All files > Photos > Camera. What I tried is on the phone I went to my /e/ account sync settings and synced manually (tapped three dots button, then “Sync now”), but this did not help. I also turned off syncing for “Pictures and videos”, then synced manually, then turned it back on and synced manually again, but this also didn’t help. I also just took new photos, synced manually, and they didn’t get synced.
What I never received from Murena is an e-mail or a news article about the cloud issues being solved. I only got the compensation refund. So @Manoj could you please shed some light on the status of the cloud issues and how to make sure that sync works again? Maybe delete/deactivate the /e/ account on the phone and reactivate it somehow?
Client Synchronization
Log in your murena account. In dashboard >> Your profile (top right )>> Settings >> Client Synchronization (left side menu) enable checkbox.
are you permanently connected through a VPN or mobile connection that is deemed “metered” by the system (even if wrongly so)? this could keep eDrive from using the connection for file sync.
what version of /e/OS are you on? that checkmark should enable sync with any client version afaik, but still good to know.
please excuse the naive question: you’re using the same user-id in the phone and for web login?
if so I’d probably re-onboard the account on the device, as in - remove account, re-attach. But before, as said, have a .vcf backup from the Contacts app and make sure Notes use the cloud synced account, not device-local, then there’s no risk of loosing anything.
One can debug the log output of eDrive to understand what’s going on under the hood if it’s still a mystery.
no, I am not connected through a VPN or mobile connection that is deemed “metered” by the system. In any case, even with wi-fi connection the situation remain the same;
I have the last e/os version available: /e/os 2.9-t-20250321478215-official-panther, Android 13, 21 march 2025.
Thanks for the tip, even though it was not meant for me (I know, it’s not my thread). Just for reference: This was disabled for me. I have enabled it, synced manually again and still don’t have photo sync.
@tcecyk 1-2 days ago my phone suddenly started another large sync job (1000+ files) and now cloud looks like phone (have only checked default camera and screenshots folder).
I am nearly 100% certain the phone also downloaded old files from before the outage from the cloud, so I now have to delete hundreds of files on phone or cloud or on both. But before that I first have to understand how syncing behavior really works (both ways or one way and if so, which way). So I have deleted one picture on the cloud and one on my phone and will see what happens. While notes sync immediately, photos apparently take a day or so? Of course this is a mystery left to be figured out by the user! I am still furious that as a paying customer I have to tinker and research this stuff because Murena can’t be bothered to update its years-old documentation How does eDrive sync work?
I understand user frustration, but I think it’s sealioning to vent in every sync related thread on the lack of documentation. Make it a dedicated thread then.
anyway, here's what I know on eDrive
deletions will not propagate from either side - that code got neutered.
The sync mechanism is “additive” from and to both sides, but with “a memory of files” device-side.
Device-side record keeping of ETag (a hash basically) and last-modified-date are used to decide what side wins on same-name but ETag difference: the more current file wins. There’s some risk to this (independent edits to both files outside a sync window or wrong modified timestamps on the remote after a backup restore).
If you get rid of the tallied database app side (eDrive app storage reset or re-adding account): it will reupload or redownload files it tracked their state of before (I think that is what you experience). That is: device-side deleted files by user choice but formerly uploaded will be downloaded to the device again.
Since the outage there is code in v2.9 that will do the described eDrive reset itself and force a file push from the device to cloud and re-establish the sync. Can’t say if the users opening these threads are below v2.9 or if the code didn’t land yet. I use eDrive only minimally to know from experience.
Notes and eDrive are fundamentally different apps and mechanisms (API vs WebDAV). Android itself schedules what the App requests.
Inside eDrive there’s a periodic/full scan and a file observer service. They use the same functions internally when comparing remote to device local service. ScanWorker is said to be a third mechanism with the same properties in behaviour - haven’t read that code yet.
There’s at least a 30min interval to the periodic one, fullscan triggers on boot and I think on plugging a charging cable. They all need an unmetered network to transfer files.
Thank you very much for the explanation! This is very helpful and aligns with my “research results”: Photos deleted on the device won’t get deleted in the cloud and vice-versa, even when the user manually syncs via settings.
It seems to me this approach has one advantage and two disadvantages. Advantage: A maximum of files is backed-up in the cloud in case the device is inaccessible or suffers unwanted data deletion.
Disadvantages: Cloud storage will fill very quickly, which nudges users to pay for more (conversely, an advantage for Murena. I seriously hope this wasn’t the main intention behind setting up this process). In order to rectify this situation (and avoid having user-deleted files synced back to his device) the user has to periodically wipe his cloud - but has to remember not to wipe the Notes folder (plus maybe other folders if these apps also use API, which the user has to research first of course) - and then reestablish sync by resetting the tallied database app-side. Or am I wrong?
This seems extremely cumbersome to me and, while I have been successful in avoiding Google Drive, OneDrive and others so far and therefore haven’t much experience with them, I can’t imagine them doing things in a way that’s even close to this in terms of complexity. I believe Murena should switch to a (casual) user-friendly process asap.
To address the “sealioning”: I understand this term in a more strict definition, i.e. a relentless request for evidence, not a general voicing of grievances on an increased scale (“spam” would be closer to this, I’d say). The reason I’m not holding back anymore after having been overly civil to the company for years is that we did in fact, like you suggested, discuss this in a thread and I myself opened one more, all with zero informative feedback from Murena. From my experience with other companies I know that only massive voicing of user concerns, bad press or decreased sales can force a company to right its course. I don’t wish the latter two on Murena, but I do think they need more UX(-minded) staff and get rid of their developer/pro user mindset asap if they want to grow. Plus users should speak up instead of clapping like seals for every breadcrumb thrown to them, hiding their feelings, quietly suffering and some leaving the project. I have actually watched most of the /e/OS 3.0 unveiling and when /e/OS was presented as a super-duper user-friendly system there I felt similarly cynical as when I hear Google talk about privacy being of high importance to them. Sorry for the OT paragraph, but I wanted to explain. I’ll refrain from this in threads with you in the future.
The eDrive code used to be able to delete, but it seems to have lead to dataloss and it got neutered. The only intent there is caution - not to baloon the remote storage.
I haven’t seen you give FolderSync a try, it productized what you want. Syncthing is also technically superior to any webdav syncer and allows control of sync behaviour on a folder-to-folder basis, is free + opensource.
I think your entitlement is abusive. Software can be lacking, but it’s an offer, especially to freeloaders - not an obligation.
Thanks for your information and sorry if I’ve come across the wrong way. Just want to say the “entitlement” comes from being a paying Murena customer and is directed solely at them. I’d never be harsh with volunteer developers (who may also work on /e/OS, I don’t know).
Sure, but does it work to write to your gas and electricity supplier like this?
Maybe yes … I never tried.
In the forum you just talk to the others in a similar position to you … it is a forum … ah but, I see, you think the governor (Zeus, perhaps) is listening … us mere mortals should just stand by and marvel at your oration?
Actually I am keen to find out some of the same answers …
The best place to continually ask for something is in manojs weekly development threads. Yes sync mechanics need better documenting. But this alone will not give you what you really want asap: control of sync behaviour. The limits as-is won’t change dramatically on the short term, there are alternative sync clients that you can try today that have more advanced sync mechanisms.
