@prog-amateur For me it's like this:

Actors:
Manual brightness (works)
Notification LED (works)
Torchlight (works)
Vibration (works)

Camera:
Flashlight (works, but*)
Photo (works, but*)
Video (works, but*)
Switching between cameras (works, but*)

*sometimes it does not work at all ("Cannot access camera") → reboot fixes this for me

Cellular:
Carrier info, signal strength (carrier info is sometimes incorrect, at least as far as I can tell, works otherwise)
Data connection (works)
Incoming, outgoing calls (works)
MMS in, out (untested)
PIN unlock (works)
SMS in, out (works)
Change audio routings (untested)
Voice in calls (not so sure, I've had issues with bad audio on the receiving end, not tested well enough though …)

Endurance:
24+ hours battery lifetime (nope, I charge it at least once a day)
7+ days stability (nope, sometimes crashes but not too often, see also the camera issue)

GPU:
Boot into UI (works)
Hardware video playback (not sure/untested)

Misc:
Anbox patches (deprecated) (untested)
AppArmor patches (untested)
Battery percentage (works, but no charge level graph/history)
Offline charging (does not work, when there is also a data connection (e.g. connected to PC))
Online charging (works)
Recovery image (untested)
Reset to factory defaults (untested)
RTC time (not sure)
Shutdown / Reboot (works, although I've had issues in the past, where the phone would not shut down properly (screen still on))
Wireless External monitor (not sure/untested)

Network:
Bluetooth (works, but maybe not the best connection, not well tested)
Flight mode (works)
Hotspot (untested)
NFC (untested, does not work afaik)
WiFi (works, but sometimes I need to turn WiFi off and on again; in the past sometimes I've also had to reboot, to make it work again)

Sensors:
Automatic brightness (works)
Fingerprint reader (untested)
GPS (works, but takes very long for the first connection, not well tested)
Proximity (works, not well tested)
Rotation (works)
Touchscreen (works)

Sound:
Earphones (works, but once didn't when I wanted to use earphones during a call, not well tested)
Loudspeaker (works, but sounds horrible on high volume (I believe that's specific to my device))
Microphone (works, as in calls, but I couldn't hear anything using a recording app, not well tested)
Volume control (works)

USB:
MTP access (works)
ADB access (not sure/untested)

@unrealb2 For Windows there is Sony's official Flash tool.

For Linux I found XperiFirm to download Sony firmware. But I didn't figure out how to flash it yet.

UPDATE
I got it fixed!

It seems to be very critical which version of Sony's OEM binaries you use:

Software binaries for AOSP Nougat (Android 7.1) – Kernel 4.4 – Loire
SW_binaries_for_Xperia_AOSP_N_MR1_5.7_r1_v08_loire.img
→ Ubuntu Touch works as expected

Software binaries for AOSP Oreo (Android 8.1) – Kernel 4.4 – Loire (v16)
SW_binaries_for_Xperia_Android_8.1.6.4_r1_v16_loire.img
→ Stuck on Sony boot screen

Software binaries for AOSP Oreo (Android 8.0) – Kernel 4.4 – Loire
SW_binaries_for_Xperia_Android_8.0.5.7_r1_v10_loire.img
→ All these issues, that I had …

The device port post mentions the first two versions as functional.
Personally I chose the 8.0 version, because it matched the installed Android version beautifully and also the installer asked for Android 8.0 being installed. Obviously I did not know, what I was doing …

Is this also true for you, @unrealb2?

@unrealb2 I use Ubuntu Touch now.
The extreme slowness was caused by the wrong OEM binaries I used. It really was unusable then.
Now it isn't completely smooth either, but it is unproblematic and fine by me.

Copied from Sony Xperia X (suzu/F5121 & F5122) it should be:

• Make sure to upgrade your device to the latest stock Android 8.0 before continuing.
  Windows: https://developer.sony.com/develop/open-devices/get-started/flash-tool/
  Linux: http://www.flashtool.net/downloads_linux.php (run with GTK_IM_MODULE=ibus ./FlashTool) and https://xperifirm.com/tutorial/install-xperifirm-linux/

• OEM unlock your device: https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/

• Boot your device into fastboot mode by shutting it down and keeping the Volume Up button pressed while plugging in a USB cable between your phone and PC. The LED should be on and blue.

• In case of flashing issues please wipe system, data & cache partitions using TWRP: https://twrp.me/sony/sonyxperiaxcompact.html

• Flash the OEM binaries from: https://developer.sony.com/file/download/software-binaries-for-aosp-nougat-android-7-1-kernel-4-4-loire/ using
  fastboot flash oem SW_binaries_for_Xperia_AOSP_N_MR1_5.7_r1_v08_loire.img

• Run the UBports Installer: https://ubuntu-touch.io/get-ubuntu-touch

@krang That's sad to hear …

Though, I wouldn't lose hope just yet … maybe @amartinz and @Flohack know more about SHIFTs stand on this? According to the device page they contributed to the port alongside SHIFT GmbH.

As a side note, there is also work done to bring up postmarketOS on SHIFT6mq in which @amartinz also seems to be involved! Although that might not be suitable for your daily use …

(I'm also interested in Shiftphones regarding non-Android-OS-support, which is why I was having an eye on this subforum ;))

Sorry for being late to the party, but as others also had booting issues, I felt encouraged to share:

Since the last updates on RC channel (currently 2023-W12/3) my Sony Xperia X Compact (F5321) more often than not won't boot up properly.
Especially when cold booting it often, but not always, shows like this:
Sony boot loader warning → Sony boot logo → Ubuntu Touch boot logo (< 1 s) → black screen
A forced reboot might then work or will also hang at different points (Sony boot logo, black screen, or automatic reboot).

I've had boot up issues in the past with this device, but it definitely has gotten worse for me since the new updates.

@prog-amateur For me it's like this:

Actors:
Manual brightness (works)
Notification LED (works)
Torchlight (works)
Vibration (works)

Camera:
Flashlight (works, but*)
Photo (works, but*)
Video (works, but*)
Switching between cameras (works, but*)

*sometimes it does not work at all ("Cannot access camera") → reboot fixes this for me

Cellular:
Carrier info, signal strength (carrier info is sometimes incorrect, at least as far as I can tell, works otherwise)
Data connection (works)
Incoming, outgoing calls (works)
MMS in, out (untested)
PIN unlock (works)
SMS in, out (works)
Change audio routings (untested)
Voice in calls (not so sure, I've had issues with bad audio on the receiving end, not tested well enough though …)

Endurance:
24+ hours battery lifetime (nope, I charge it at least once a day)
7+ days stability (nope, sometimes crashes but not too often, see also the camera issue)

GPU:
Boot into UI (works)
Hardware video playback (not sure/untested)

Misc:
Anbox patches (deprecated) (untested)
AppArmor patches (untested)
Battery percentage (works, but no charge level graph/history)
Offline charging (does not work, when there is also a data connection (e.g. connected to PC))
Online charging (works)
Recovery image (untested)
Reset to factory defaults (untested)
RTC time (not sure)
Shutdown / Reboot (works, although I've had issues in the past, where the phone would not shut down properly (screen still on))
Wireless External monitor (not sure/untested)

Network:
Bluetooth (works, but maybe not the best connection, not well tested)
Flight mode (works)
Hotspot (untested)
NFC (untested, does not work afaik)
WiFi (works, but sometimes I need to turn WiFi off and on again; in the past sometimes I've also had to reboot, to make it work again)

Sensors:
Automatic brightness (works)
Fingerprint reader (untested)
GPS (works, but takes very long for the first connection, not well tested)
Proximity (works, not well tested)
Rotation (works)
Touchscreen (works)

Sound:
Earphones (works, but once didn't when I wanted to use earphones during a call, not well tested)
Loudspeaker (works, but sounds horrible on high volume (I believe that's specific to my device))
Microphone (works, as in calls, but I couldn't hear anything using a recording app, not well tested)
Volume control (works)

USB:
MTP access (works)
ADB access (not sure/untested)

On a side note, there is also Hydrogen, a matrix web client developed by Element/New Vector.
It works suprisingly well in Morph Browser with the exception of notifications. It is somewhat bare-bones, but at least it supports E2EE and is in active development. I have been using it as a rudimentary web app created with Webber.
Maybe this could also be a good starting point for a sustainable matrix client on Ubuntu Touch?

In any case, thank you for working on this!

Copied from Sony Xperia X (suzu/F5121 & F5122) it should be:

• Make sure to upgrade your device to the latest stock Android 8.0 before continuing.
  Windows: https://developer.sony.com/develop/open-devices/get-started/flash-tool/
  Linux: http://www.flashtool.net/downloads_linux.php (run with GTK_IM_MODULE=ibus ./FlashTool) and https://xperifirm.com/tutorial/install-xperifirm-linux/

• OEM unlock your device: https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/

• Boot your device into fastboot mode by shutting it down and keeping the Volume Up button pressed while plugging in a USB cable between your phone and PC. The LED should be on and blue.

• In case of flashing issues please wipe system, data & cache partitions using TWRP: https://twrp.me/sony/sonyxperiaxcompact.html

• Flash the OEM binaries from: https://developer.sony.com/file/download/software-binaries-for-aosp-nougat-android-7-1-kernel-4-4-loire/ using
  fastboot flash oem SW_binaries_for_Xperia_AOSP_N_MR1_5.7_r1_v08_loire.img

• Run the UBports Installer: https://ubuntu-touch.io/get-ubuntu-touch

@unrealb2 I use Ubuntu Touch now.
The extreme slowness was caused by the wrong OEM binaries I used. It really was unusable then.
Now it isn't completely smooth either, but it is unproblematic and fine by me.

UPDATE
I got it fixed!

It seems to be very critical which version of Sony's OEM binaries you use:

Software binaries for AOSP Nougat (Android 7.1) – Kernel 4.4 – Loire
SW_binaries_for_Xperia_AOSP_N_MR1_5.7_r1_v08_loire.img
→ Ubuntu Touch works as expected

Software binaries for AOSP Oreo (Android 8.1) – Kernel 4.4 – Loire (v16)
SW_binaries_for_Xperia_Android_8.1.6.4_r1_v16_loire.img
→ Stuck on Sony boot screen

Software binaries for AOSP Oreo (Android 8.0) – Kernel 4.4 – Loire
SW_binaries_for_Xperia_Android_8.0.5.7_r1_v10_loire.img
→ All these issues, that I had …

The device port post mentions the first two versions as functional.
Personally I chose the 8.0 version, because it matched the installed Android version beautifully and also the installer asked for Android 8.0 being installed. Obviously I did not know, what I was doing …

Is this also true for you, @unrealb2?

@unrealb2 For Windows there is Sony's official Flash tool.

For Linux I found XperiFirm to download Sony firmware. But I didn't figure out how to flash it yet.

Hi everybody!
I'm new to Ubuntu Touch and got myself a used Xperia X Compact to install it on. I know it's not exactly the best supported device, but since I enthusiastically dislike any large smartphone I wanted to give it a try
As it turns out, I do need some help.

The device was running Android 8.0 and as it's secondhand I tested the fuctionality using the service menu. Everything worked!
I then followed Sonys guide to unlock the bootloader, enabled developer mode and plugged it into my PC running openSUSE Tumbleweed.
The UBports Installer (0.8.8-beta Appimage) detected it correctly, but during installation I ran into the bootloop, where the device always reboots after a few seconds in the "UBports Recovery" screen.
Following the old thread about the Xperia X, I fixed this by flashing TWRP, wiping system/data/cache and flashing these OEM binaries.

Now the installation runs through successfully without errors on all channels stable/rc/devel & edge. This is without a microSD card installed and both with/without a SIM card installed.

But:

• Unfortunately the freshly installed Ubuntu Touch runs extremely slow and repetitively hangs to the point, where it is hard to even get through the set-up process and the gesture introduction. To give you an idea: The UT boot logo stays up for 5 min, then the lock screen takes 30 seconds to build up and unlocking to home screen with the Ubuntu bar on the left takes another minute.
  Strangely though, on stable, rc and edge channel I've had it happen, that after some time and a lot of reboots this behavior vanishes and I'm then able to walk through the settings and launch/use/switch applications fluently!

• Bootup often fails, resulting in another reboot or a black screen. I get around the latter by holding [Volume up] + [Power] to force reboot.

• A lot does not work, most notably the cameras, WiFi and the cellular modem. My SIM card is not being detected. In System settings / About it says:
  IMEI: None (this entry periodically appears/disappears)
  Wi-Fi adress: FF:FF:FF:FF:FF:FF

Now, as the installation itself seems to work, is it safe to assume that my phone is correctly prepared Android-wise? Or could I have messed something up there?
Do you have any other idea or suggestion about what went wrong and how to fix it?
If I should report this as a bug somewhere, please let me know!

In any case, thank you!