Official LineageOS 17.1 for Fairphone 3/Fairphone 3+

I regularly copy /storage/emulated/0, which works fine for me

I have edited my previous message.

In WhatsApp, in the settings, do a backup of all messages.

Can one do it without Google Drive? Besides not having any Google-related app, and not having a Google account either, I am very reluctant about doing a GDrive backup since it would imply exporting all the chats unencrypted. I donā€™t really believe my whatsapp chats are not read by anyone besides me and the contact I chat to, but I would rather avoid that anyway.

Will try next time!

1 Like

Of course! You can store backups on the phone locally. Just that for some reason, I never managed to restore backups stored locally without the trick described in my post, WA tells me it didnā€™t succeedā€¦

WhatsApp backups are encrypted when stored locally, and decrypted when restored. So they are normally not stored as clear on your device. See e.g here:

Also, I think I did a mistake in my protocol, Iā€™ll edit my post. It still needs testing.

This is becoming annoying.
Today I was offered a new update for 17.1+microG. When I looked up the changelog, I was redirected to the ā€œofficialā€ LOS changelog. Of course there was a change by @dk1978 https://review.lineageos.org/310526 which (if I interpret it correctly) is about updated firmware. But although it is in the changelog they link to, it seems to be not included in their updateā€¦

I think I really have to find time to switch to official LOS.

1 Like

This is because official LineageOS adds those firmwareupdate to the OTA ZIP after the ROM was built. I would really like to know how they do it, so I could include the firmwares in my own builds and they could probably be added to Lineage+MicroGā€¦

That would be nice to know, indeed.
But what I wanted to say is that I think it is not good practice to link to a changelog which doesnā€™t apply to the software they deliver.
I admit that it might be difficult for them to do it another way, I guess they are building more or less automatically, donā€™t they? But nevertheless, if a changelog states a change, the change should be included in the product delivered.

Iā€™m also looking for a way to use the latest firmware in the LOS4MicroG builds.
I came across this post by @dk1978 Official LineageOS 17.1 for Fairphone 3/Fairphone 3+ - #540 by dk1978 and saw this

Migrate from the latest Fairphone release to Lineage4microG - thus you will already be using the latest partition images.

Iā€™m not sure I fully understand this method. Wouldnā€™t flashing the Lineage4microG wipe the latest Fairphone release partition images, and replace them with the (outdated) ones that come with the Lineage4microG build?

There are no firmware blobs within LOS4microG thus you wonā€™t downgrade those partitions with reflashing LOS4microG.
I did it myself as I am struggling with crashes while using VoIP. But the switch to official LOS didnā€™t changed anything in that relation. :see_no_evil:

1 Like

I thought LOS came with:

boot, dtbo, system, vbmeta, vendor, aboot, cmnlib64, cmnlib, devcfg, dsp, keymaster, lksecapp, mdtp, modem, rpm, sbl1, tz

And LOS4microG (after checking the payload.bin):

boot, dtbo, system, vbmeta, vendor

So therefore I was under the assumption that (when flashing LOS to LOS4microG), these LOS4microG firmware blobs would just wipe and replace the LOS ones. Am I mistaken?

Yes, but only the relevant ones, they will only wipe and replace boot, dtbo, system, vbmeta and vendor, the other partitions (aboot, cmnlib64, cmnlib, devcfg, dsp, keymaster, lksecapp, mdtp, modem, rpm, sbl1, tz) will remain as they were.

1 Like

Thatā€™s great to hear, so I can get LOS4microG running with the latest firmware blobs :smiley: .

Also, when doing a factory reset (after locking bootloader). These firmware blobs will stay/survive?

1 Like

Doing a factory reset just means wiping the data partition, nothing else, so yes.

4 Likes

@Alex.A @HolosericaCaligo thank you for the help :slightly_smiling_face:

2 Likes

I know asking ETAs and timings in open source world is different, but LOS4microG has not been updated for a while and now on June 26th and yesterday and itā€™s always the thrill wether the next update is one week or three months away :see_no_evil:

Yes, something needs to happen with microG. Right now I am busy with preparations for 18.1, but after release we can look for alternatives.

4 Likes

That was not meant to cause you any concerns, @dk1978. As I am not suffering any serious bugs, Iā€™m cool with just getting what Iā€™m given.
On the other hand, I would not complain to, at least, get some more info :wink:

Since I installed the current update on Tuesday my FP seems to interpret the WIFI connection as a mobile data connection. I frequently get alerts due to high mobile data usage. Usually I switch off mobile data when activating WIFI - just in case someone asks about that.

Anybody else with that problem?

When migrating to LOS4Microg, is it best to migrate from (Official) FP3 OS or LineageOS?

I understand LOS uses the (important) firmware blobs from (Official) FP3 OS, so essentially firmware wise they donā€™t differ?

I also read that thereā€™s a difference in ā€˜file names mapping to translate the file names into partition labels.ā€™ ( Official LineageOS 17.1 for Fairphone 3/Fairphone 3+ - #631 by dk1978 )

So I was wondering if it matters which to migrate from.

If you have a choice, then migrating between LOS4MicroG and official LineageOS is preferrable, because it should be possible without losing data.

Yes, I try to ensure that by staying up to date with the firmware.

That is just a detail about how we manage the firmware partitions internally when building official LOS. The final user - you - will not need to care, unless you are trying to extract firmware partitions from a LOS OTA zip and flashing them yourself.

3 Likes

Thanks so much, that clears thing up!

Hopefully soon I have time to do this migrate, always takes way longer than what I anticipated for :grinning_face_with_smiling_eyes:

1 Like