@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.

@danfro I already did some tests with FP3 and OP5T and on both, something seems to be missing still, for VoLTE to work.
So I would just wait for now, until someone comes up with a solution for devices, which are not the FP5.
I know that it is not working on the P3A too, but work is going on to get that fixed.

@mariogrip could you please explain a bit, the different settings in qti.conf, for porters of other devices?

For example the "radioInterface" number, what is it and is that device specific?
How is the syntax for two slots in "ExpectSlots", slot1,slot2?

Then, for activating, I suspect OfonoPlugin: binder must be set in deviceinfo file.
What about OfonoImplementsIms? Is that needed in any way? From the MR, I understand, that it activates/displays the VoLTE switch in SIM-settings, but at least, it already gets displayed without the deviceinfo setting.

And, what are the first places to have a look, when using the ofono-binder-plugin and nothing works?

Thanks and best regards,
Lukas

@ghazouani
Enable developer mode in system-settings.
Then connect your device with USB to a PC where ADB is installed.
Open a terminal/cmd and check whether ADB is able to see your device using adb devices.
If that's the case, type adb shell and you should now be in a terminal-session on your device.

Any idea whats wrong here:

phablet@ubuntu-phablet:~$ sudo system-image-cli -v --progress=dots --switch=devel/arm64/android9plus/daily            
[sudo] password for phablet:                               
[systemimage] Sep 21 00:06:09 2024 (5770) running state machine [devel/arm64/android9plus/daily/FP3]
[systemimage] Sep 21 00:06:09 2024 (5770) Looking for blacklist: https://system-image.ubports.com/gpg/blacklist.tar.xz
[systemimage] Sep 21 00:06:09 2024 (5770) [0x7fa66efe80] Requesting group download:
        https://system-image.ubports.com/gpg/blacklist.tar.xz -> /var/lib/system-image/keyring.tar.xz
        https://system-image.ubports.com/gpg/blacklist.tar.xz.asc -> /var/lib/system-image/keyring.tar.xz.asc

[systemimage] Sep 21 00:06:09 2024 (5770) Allow GSM? Yes
[systemimage] Sep 21 00:06:09 2024 (5770) [/com/lomiri/applications/download/terminal_2eubports_5fterminal_5f2_2e0_2e2/d61afa275e8c4c6dbe0cc6abcfee7bd9] Running group download reactor
[systemimage] Sep 21 00:06:09 2024 (5770) self: <LDMDownloadManager at 0x7fa66efe80>, self._iface: <Interface <ProxyObject wrapping <dbus._dbus.SystemBus (system) at 0x7fa6072900> :1.154 /com/lomiri/applications/download/terminal_2eubports_5fterminal_5f2_2e0_2e2/d61afa275e8c4c6dbe0cc6abcfee7bd9 at 0x7fa618a5e0> implementing 'com.lomiri.applications.GroupDownload' at 0x7fa618a7f0>
[systemimage] Sep 21 00:06:10 2024 (5770) [/com/lomiri/applications/download/terminal_2eubports_5fterminal_5f2_2e0_2e2/d61afa275e8c4c6dbe0cc6abcfee7bd9] Group download reactor done
[systemimage] Sep 21 00:06:10 2024 (5770) uncaught exception in state machine
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/systemimage/state.py", line 133, in __next__
    step()
  File "/usr/lib/python3/dist-packages/systemimage/state.py", line 219, in _get_blacklist_1
    get_keyring('blacklist', url, 'image-master')
  File "/usr/lib/python3/dist-packages/systemimage/keyring.py", line 105, in get_keyring
    get_download_manager().get_files([
  File "/usr/lib/python3/dist-packages/systemimage/download.py", line 203, in get_files
    self._get_files(records, pausable, signal_started)
  File "/usr/lib/python3/dist-packages/systemimage/ldm.py", line 187, in _get_files
    raise AssertionError(
AssertionError: Missing destination files: ['/var/lib/system-image/keyring.tar.xz', '/var/lib/system-image/keyring.tar.xz.asc']
local_paths: [dbus.String('/tmp/blacklist (2).tar.xz'), dbus.String('/tmp/blacklist (2).tar.xz.asc')]
Exception occurred during update; see log file for details
[systemimage] Sep 21 00:06:10 2024 (5770) system-image-cli exception
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/systemimage/main.py", line 403, in main
    list(state)
  File "/usr/lib/python3/dist-packages/systemimage/state.py", line 133, in __next__
    step()
  File "/usr/lib/python3/dist-packages/systemimage/state.py", line 219, in _get_blacklist_1
    get_keyring('blacklist', url, 'image-master')
  File "/usr/lib/python3/dist-packages/systemimage/keyring.py", line 105, in get_keyring
    get_download_manager().get_files([
  File "/usr/lib/python3/dist-packages/systemimage/download.py", line 203, in get_files
    self._get_files(records, pausable, signal_started)
  File "/usr/lib/python3/dist-packages/systemimage/ldm.py", line 187, in _get_files
    raise AssertionError(
AssertionError: Missing destination files: ['/var/lib/system-image/keyring.tar.xz', '/var/lib/system-image/keyring.tar.xz.asc']
local_paths: [dbus.String('/tmp/blacklist (2).tar.xz'), dbus.String('/tmp/blacklist (2).tar.xz.asc')]
[systemimage] Sep 21 00:06:10 2024 (5770) state machine finished
             

?

Edit:

Ok, never mind, I just executed the command through ADB and it now downloads the files.
My previous error was from the UT terminal directly.

@danfro since the system itself can already "hold" the wireguard connections, the better way would be, to modify the settings app and network indicator, to just display the wireguard connection-type, and make it at least switchable.

But I did not have the time to look into it.

@Dunbrokin Fdroid is within waydroid... But there is a Garmin Connect webapp in the OpenStore.

@Plarde maybe have a look here:
https://forums.ubports.com/post/80411