Any murena support for Data migration from Fairphone 3 to Fairphone 6? (both e/OS/ 3.0.4)

Is there any murana support to transfer all apps(!) and data besides contacts, calendar etc.?
But of course without a google account.
That would be great!
Would appreciate any ideas, solutions, tools, even effective manual approaches …

if it’s A14+ on the FP3 (check version string), then built-in Seedvault can help in migrating.

You can find it in Settings → System → Backup.

As said, in A14 and up it is more useful than older versions.

1 Like

Thanks, interesting. But I am running e/OS/'s latest version 3.0.4 which is still based on Android 13.
I do not know a way to update to a Google-free OS based on A14 or is there one?

the community branch offers those versions for the FP3. I read of the Backup option happens to be hidden in some devices (depending on upgrade path?).

You should give it a try, even if it’s still the old Seedvault version in A13 (I’m actually not sure what it ships, it can tell you in the upper right settings what version it has). At the very least it will transfer all apks to the FP6. How much settings are transfered you’ll need to find out.

1 Like

Hopefully Seedvault offers native backward compatibility for versions during backups and restores by default. However, some application APIs may be deprecated from one Android version to another. This is also why, for example, the ‘version upgrades’ offered by /e/OS are time-consuming and difficult to implement.

The greater the gap between the Android version of the backup and the version of the restore, the less complete the backup will be. Some (rare) applications may even stop working if their APIs and settings have been changed in a new Android version.

Ideally, a SeedVault backup should be restored to the same version of /e/OS AND the same version of AOSP, particularly in terms of system settings.

Please also note that saved Wi-Fi networks cannot be backed up with SeedVault (this is related to Android security and key encryption), in other words, the wpa_supplicant.conf file is not accessible outside of root mode. You will therefore need to re-share the saved Wi-Fi networks from the old device to the new device via QR code.

1 Like

Just for reference, here is Murena’s guide for migration without App dataHow to Backup and Restore your /e/OS phone

1 Like

Using Package Manager ist of very limited use, since

  1. app’s data ist not backuped which means it is like a new installation of the apps. All app specific configurations and data are lost.
  2. Import for more than one app at a time does not work, if one app is among the selected apps for restore is a splitted one (containing ‘sub’-apks).

An the murena workspace account does only help for contacts, calender etc…

My opinion:
murena should emphasize much more an easy to migrate from old to new phone support to make user more happy.

murena should emphasize much more an easy to migrate from old to new phone …

I agree, but this happened in a sense for Seedvault: for A14 and up they no longer interfere with upstream (and ship an old Seedvault version), but give you what Lineage updated to. They didn’t backport to A13 though afaik, but that is also due to how SV gets developed - older branches are not maintained.

There’s no other foss app that hooks into Android facilities for backup like Seedvault.

Hi. I am running into some problems going from FP3 with e/OS to FP 6 e/OS. My FP3 hasn’t had an update in years so it barely functions. Now I bought a FP 6 and have some issues with data transfer of my photos.

I somehow have 2 different gallery apps on my FP3. I don’t remember if I did that myself because maybe the gallery app was not really great. I do remember that the camera app was bad so I downloaded a different one based on some thread on the forum.

In the original gallery app of e/OS all the photos of my old FP2 and the new photo’s made with the FP3 are normal, they are chronological.
But in the other gallery app, there is one folder with DCIM, photos made with FP3, and one with Pictures, photos made with FP2 and older. They are separate, but within their folders still chronological.

Now when I want to transfer all the pictures to the new FP6, the DCIM pictures made with the FP6 is all normal. But the Picture folder with my FP2 and older photos, their date is read as the date I trandferred them to the FP2 and they are all mixed. Their date in the gallery app on FP6 is oct 4 2020, that would not be a problem, but they are completely mixed.

When I want to do the transfer and plug the phone to the computer, the FP3 has a folder with DCIM (photos made with FP3) and Pictures (older photos). I tried putting the pictures from Pictures in DCIM on the new phone, it doesn’t work. I even looked up an old back up from google and downloaded all the pics from Google that happen to be the same as in the Pictures folder, and put that in DCIM on the new phone, doesn’t work.
I tried putting both folder separately in the new phone, all the result is the same: the pics that are in the Picture folder all have the same date and mix all over the place. It’s a mess. I tried looking if there was a back-up on my Murena account, but there were only a few pics.
Does anyone know what I am doing wrong and if it can be fixed?
Thank you for reading.

folder juggling will not help. The native Gallery app uses modification date, not the exif date, this thread describes it too: I found a gallery app that organises photos by Exif dates! - the gist is, use Fossify or Aves that both offer sort by exif. I hope the native app will at some point introduce a switch for DCIM (or any folder) to use date taken.

If you're a tinkerer..

this app (download linked debug apk) can overwrite mtime with exif data. It needs custom exiftool flags: -overwrite_original "-FileModifyDate<CreateDate" or "-FileModifyDate<DateTimeOriginal" depending where the app did store the date taken. It can also readout the filename itself if exif fails. Caveat: it worked for me on individual files, but not folders

On a final note: why did your FP3 get no updates? it has A15 available. Worst case, a sideload away.

Thank you!!
Something had gone wrong with the FP3 and I wasn’t receiving any updates and had to reinstall e/OS after doing a factory reset. I postponed it so long (it was kinda good to have a phone that doesn’t quite function because then you only use is if necessary, I noticed I was never on my phone like other people). Now that there is a new phone, I finally decided to do all the back ups etc and also switch to the new one because the FP3 camera was not so good. I will still do the factory rest and reinstall e/OS and then use it as a back up phone.