Documents & Photos not Syncing from Fairphone 4

[Melinoe]

Hi there,

I have Pictures and videos sync enabled within e/OS on my Fairphone 4 as per this guide here:

https://doc.e.foundation/support-topics/edrive-sync-details.html

But within Murena Cloud, I am not seeing recent photos or files as having been backed up. Am I missing anything?

I also have Client Synchronization enabled within Murena Cloud:

File sync works just fine using Nextcloud Files app on computers (I use both Windows, Mac, and Linux) but not my phone for some reason?

It alarms me that my photos are not being backed up as this was part of the appeal of moving to Murena cloud and e/OS in the first place. If anything happens to my phone, I am a photographer and want my pictures specifically backed up. I am also paying for file storage that isn’t working how I assumed it would.

Would really appreciate any an all input on this. If I can’t find a fix, I might consider Proton Drive or secure file storage another alternative.

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services

[Melinoe]

I removed my Murena account from my phone early this morning then re-added it.

For reasons unbeknownst to me, it began syncing a few hours after I removed then readded the account. Looks to be working now! Will continue to monitor it to make sure everything comes through

[tcecyk]

what version are you on atm?

I wonder if it’s the same as an expired oauth token - but those users get an error message. A bugfix for this arrives afaik in v3.1 to not needing to remove / re-add the account manually.

(Certainly doesn’t help that the sync menu shows a recent “Last synced” for Files without an error)

[Melinoe]

See here:

I did at one point sign up for beta updates via the release channel but then disabled that when the next stable build came out. Not sure if that makes a difference.

[tcecyk]

if I’m not wrong putting you into that error bucket, by the time your newly issued token (by re-adding the account) could expire again you’ll be already on a v3.1

[tcecyk]

eDrive sync (still) not working with /e/OS v3.0.2

Sync was working, but now it has stopped again even after me removing then readding my account. Is anyone else still having issues with this?

if you’re into adb, there’s a few commands you can throw at eDrive “to do something” and see errors.

[Melinoe]

Oh neat I’ll give this a shot! Thank you!

[Melinoe]

Gave that force sync command a whirl. Here was the output:

Broadcasting: Intent { act=foundation.e.drive.action.FORCE_SCAN flg=0x1400000 }
Broadcast completed: result=0

Will give it a few and see if the sync decides to take. I noticed after removing then re-adding my account initially the sync would eventually kick on after about 1 - 2 hours. Probably will check the status in the AM.

Thanks for digging into this! I feel less crazy knowing it’s a known issue and someone is actively looking into it.

[tcecyk]

fyi, I’m not actively digging into this, but mossroy comments in the linked thread are instructionable, as in what other commands you can try and what you should see by the worker processes. Stubbornly I still think it’s session related, and things will be better in v3.1

[Melinoe]

So I’m now running the attached e/OS version and I’m getting a notification from Account Manger that says:

Soft Error (max retries reached)

I’ve tried syncing manually to no avail. Any thoughts?

[tcecyk]

@Melinoe

Soft Error (max retries reached)

originates here - a AM / davx5 sync task that failed too often. This is not eDrive directly. It should show which account entry it’s assigned to in the notification (setSubText(account.name)). I’d remove and re-add that account then.