@JPC So, I could solve my latest connection issues by doing a waydroid init -f.

@Kutzi its nothing to worry about, if not all mounts work in recovery, but the relevant (userdata) should be mounted still.

Now just have a look at /data/backups ls -la /data/backups

@JPC lately I've had the same issue. I found that there was set a private DNS in network settings. Unsetting it and resetting the network-connection fixed it for the moment.
But now I have the issue again and there is no other DNS set, so... no idea.

@fair the FP4 does not seem to use the ofono binder plugin yet... Maybe thats the reason.
It also enables voLTE.
See:
https://gitlab.com/ubports/porting/reference-device-ports/android11/fairphone-5/fairphone-fp5/-/commit/0c61fce9afe9d3f99cff4a8edfd4fa9e6a56bb7b

and

https://gitlab.com/ubports/porting/reference-device-ports/android11/fairphone-5/fairphone-fp5/-/commit/3f32f4fa4145acd1cf16ddf3d9abd4eec9079652

@peat_psuwit they get written to /userdata/backups.

@peat_psuwit maybe it should be mentioned somewhere, that there is a backup-job running, the first time, when "migrating" into 24.04.

1. It's a nice feature
2. It may slow down the UI on older devices (e.g. FP3, not sure how it feels on more performant devices) while running.
3. When switching between 20.04 and 24.04 back and forth (for testing), you may run into storage-issues, because every first time 24.04 is booted, it creates a new backup.

@Kutzi everytime, when you switch from 20.04 to 24.04, after booting, the system creates a backup of your user-config-data.
That's also the reason, why the system feels a bit more slow, directly after the first boot of 24.04.
I am not sure if also backups are created, when switching to 20.04 again.

Have a look at /userdata/backups and clean it up.
Maybe do it from recovery: Boot to recovery, connect through adb, mount -a, and then check user-data backups folder.

Everytime you switch, there will be changes in your /home/phablet/.config and other dot-folders, because there is always something that needs to be migrated e.g. regarding system-apps.
So I won't recommend switching back and forth.

@Alain regarding installing:

You need to unlock the bootloader, there are plenty of how to's for that.
For that you will need a PC where the little tool fastboot is installed.
Then you might need to downgrade the device to the appropriate Android version. Usually the ubports installer gives short instructions where to download the right firmware.

After you unlocked the bootloader and the device is running the right Android version, you just use the ubports installer to flash Ubuntu Touch onto the device.

Thats it.

@Moem The thing is... we currently have one port (official one), based on the "full-system-image" build, and a second one based one the "standalone-kernel" method.
The second one, is the one we want to support further. But we somehow need to do a migration, from the first to the second port...

Currently, the plan is to make it available with UT 24.04.
But I am still not sure, how that will work.

@messayisto both ports are targeting both device version, so the OPO5 is still part of the show.

@MrT10001 I remember that it worked by flashing it via fastboot.
Installer was never working because it was not possible to create a working ut recovery for it.

Tomorrow, the installer should work again for focal.

@MrT10001 Yes, I was testing a rootfs.img on data partition, instead of systempartition and found that it boots more stable. But it seems that, when installing it using ubports installer, something doesn't work yet.

I will rollback the change, for now.

@Scofus you can use the UT Tweak Tool from openstore.
There you need to select "apps" in the menu and then search for the gallery app.
There you can clear cache and other data of that app.

@Scofus did you already try, to clear your gallery app cache folder?

@castpixel no, the M11 is a totally different tablet.

@arcaege sure, can you please post a link here to that point in the guide?

@arcaege it is uncommon to name a defconfig file with an extension *.config.
Maybe try to rename it to "halium_defconfig" or whatever.

To make it short: the OP5T will still be supported in the future, since I am involved in the port.
Just need to figure out, why it was removed in the list of supported devices, maybe because of inactivity/no progress in the last year...

@peat_psuwit

I overlayed touch.pa for two reasons:

1. to make bluetooth calls work more reliable.
   So this one maybe get fixed by the MR.
2. to make wired headphones work. For this it was needed to explicitly add the rate=48000 parameter to the load-module command:
   https://gitlab.com/ubports/porting/community-ports/android10/fairphone/fairphone_fp3/-/blame/halium-10.0-focal/overlay/system/etc/pulse/touch.pa?ref_type=heads#L55

@Kjetil you can't browse it. You need to access it through ADB using the terminal.
Connect, mount data, transfer data using adb pull.

There are some instructions for backups with ADB here in the forum somewhere.