This is a port of Ubuntu Touch for the Sony Xperia X (suzu/F5121 & F5122).

Sources:
Kernel:
https://github.com/fredldotme/device-kernel-loire

Device:
https://github.com/fredldotme/device-sony-common
https://github.com/fredldotme/device-sony-loire
https://github.com/fredldotme/device-sony-suzu

Halium:
https://github.com/Halium/halium-devices/blob/halium-7.1/manifests/sony_suzu.xml

Status:

Working:

• Audio
• Calling
• SMS
• Wifi (sometimes requires a reboot)
• Wifi hotspot
• Bluetooth (sometimes requires a reboot)
• GPS
• Vibration
• Orientation sensor
• LED
• USB/MTP
• USB/ADB
• Video decoding
• Photo camera
• MicroSD support
• Flash light
• Anbox
• Libertine

Missing:

• Video recording

Install:

• 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

• 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 (0.4.5-beta or onwards): https://github.com/ubports/ubports-installer/releases/tag/0.4.5-beta

Now that the port has reached a certain state I'd like to present the status of this project to a wider audience,

Current status:

• Full AppArmor support
• Adequate Mir performance
• Full ofono/rild support
• Passing most hybris tests

Known issues:

• Unable to enumerate rotation status and updates
• Calling doesn't work
• Audio doesn't work
• Camera doesn't work
• Click package support incomplete

The full build instructions are available on the Halium project management issue page.

Halium port project management, HAL port specific issues:
https://github.com/Halium/projectmanagement/issues/98

Calling now works (with caveats). For the time being you need a test version of telepathy-ofono on your device to enable calling:

sudo ubports-qa install xenial_-_haliumfixup

As we are approaching full support the build and flash instructions on https://github.com/Halium/projectmanagement/issues/98 have been updated.
This should get you a working image with audio support.

Remaining issues:

• Media player support (videos in Morph Browser work fine)
• Camera

Hey! I have something new to play around with for people on Halium 9 builds of Ubuntu Touch: you can now test your device for NFC functionality!
The only prerequisite is that your device needs to be on the devel-based rootfs, not the edge one.

To install:

sudo ubports-qa install xenial_-_android9_-_nfcd
sudo mount -o remount,rw /
sudo apt install nfcd nfcd-tools nfcd-binder-plugin nfcd-repowerd-plugin

To get console output from nfcd:

sudo stop nfcd
sudo /usr/sbin/nfcd -p /usr/lib/nfcd/plugins -v

App developers can try the QtNFC integration module to develop apps based on this technology. This requires the following change to be made to the rootfs before it can be used by (currently only unconfined) apps:

sudo mount -o remount,rw /
sudo apt install qml-module-qtnfc

The API documentation is located here: https://doc-snapshots.qt.io/qt5-5.9/qtnfc-qmlmodule.html

Please use this thread to share your experience with NFC enablement and even ask for help.

I've prepared a new image to test with working Audio.

Same installation instructions apply, you need halium-install to flash the current rootfs.

@chriswyatt Thanks for testing! I've noticed audio to be flaky as well and I assumed it had to do with not-yet-committed changes. Luckily that's not the case, so that's good for finding the bug.

Currently calling doesn't work for any Halium 7.1 based port using the default ofono shipped in Ubuntu Touch, so it might take some time until calling is fully fleshed out.

I've found a fix for the screen sometimes taking seconds to turn on, which is what I'll incorporate soon. In addition to sound I'll also take another look at the camera.

I've assembled an image for those who are interested in testing and contributing to Ubuntu Touch.

Downloads:
Current: https://drive.google.com/open?id=1a3JtU2TIFg7E53z2pHoveOtOj7LYxJyW
https://drive.google.com/open?id=1Pmp3sfOs3g5mAb4_W4780-pX4KPliy2F
https://drive.google.com/open?id=1ZmdXFDPDCDkYmVnHC1uf2dYZ8MH6bxwK
https://drive.google.com/open?id=1Ql84ucDlatauuXpqBU-k-jKzdqotYAaB
https://drive.google.com/open?id=1OJjTosp7jFaYhEYYkB9Mxf3lA0HPIXY6

Instructions (tested on Ubuntu 18.04):

• Linux PC with adb and fastboot properly set up
• Recent UBPorts rootfs image from the edge devel channel (tested with build #88):
  https://ci.ubports.com/job/xenial-rootfs-armhf/lastSuccessfulBuild/artifact/out/ubports-touch.rootfs-xenial-armhf.tar.gz
• TWRP Recovery (tested with version 3.2.3-0)
• Android 7.1 (Kernel 4.4) Loire OEM binaries
• Flash script: halium-install

After successfully flashing the recovery image the OEM binaries need to be flashed onto the oem partition:

unzip SW_binaries_for_Xperia_AOSP_N_MR1_5.7_r1_v08_loire.zip
fastboot flash oem SW_binaries_for_Xperia_AOSP_N_MR1_5.7_r1_v08_loire.img

System images:

./halium-install -p ut ubports-touch.rootfs-xenial-armhf.tar.gz system.img
adb reboot bootloader
fastboot flash boot halium-boot.img
fastboot reboot

Post-installation steps

Either make sure to properly set up the USB-Ethernet connection OR enter the commands in the Terminal app.

USB Ethernet:

SSH shell connection:

ssh phablet@10.15.19.82

Enable audio in calls

# Mount rootfs read-write
sudo mount -o remount,rw /

# Install updated packages
# When asked to override maintainer files just answer with Y
sudo ubports-qa install xenial_-_haliumfixup
sudo apt install pulseaudio-modules-droid-24 pulseaudio-modules-droid-glue-24

# Mount rootfs read-only and reboot
sync && sudo mount -o remount,ro / && sudo reboot

This is a port of Ubuntu Touch for the Google Pixel 3a (sargo).

Sources:
Kernel:
https://github.com/fredldotme/android_kernel_google_bonito

Device:
https://github.com/fredldotme/android_device_google_bonito

Status:

Working:

• Audio
• Calling
• Wifi
• Wifi hotspot
• Bluetooth
• Vibration
• Sensors
• Video decoding
• Photo camera & video recording
• Gallery previews
• Flash light
• Fingerprint reader
• GPS
• USB/MTP
• USB/ADB

Missing:

• Anbox
• Libertine

Known issues:

• During installation finding the device in recovery mode takes some time. Use the "Try again" button frequently until it is found by the UBports Installer.
• Under active investigation: Sometimes the device loses data signal without indication. In this case the device needs a reboot.
• Even though GPS should work it might take a long time to get a GPS fix on location requests.
• Bluetooth calls miss working microphone routing.
• WIFI usage drains the battery.

Install:

• Make sure to revert to factory image PQ3B.190801.002 before continuing: https://developers.google.com/android/images#sargo

• Install using the UBports installer (version 0.6.0-beta and up): https://github.com/ubports/ubports-installer/releases/tag/0.6.0-beta

I'll release a new version of the images with functional hardware-accelerated video decoding & partial camera support (no videos, no flash) soon.

EDIT: New version now available here: https://forums.ubports.com/post/14061

I'd also like to know how many have tried the images on their device. May I ask you to raise your hands quickly?

@dieharddan @dsimmons our super secret guy has verified that SMS work with a certain set of changes. I will post a method on how to add testing repos soon after I've created them!

Or, if you feel adventurous and can't wait for it:

• Download all files from here: https://drive.google.com/drive/folders/1PuDBL2v9VKeKWlfrNbxxIDDOsqUH-056?usp=sharing
• Copy them to your phone's "Downloads" folder
• Enter an adb shell and run the following commands:

sudo mount -o remount,rw /
sudo apt install ./Downloads/libgbinder-radio_1.0.11+ubports1_arm64.deb ./Downloads/libgbinder_1.0.47_arm64.deb
sudo cp ./Downloads/libgrilio-binder.so.1.0.15 /usr/lib/aarch64-linux-gnu/libgrilio-binder.so.1.0.13
sudo cp ./Downloads/rilbinderplugin.so /usr/lib/aarch64-linux-gnu/ofono/plugins/rilbinderplugin.so
sync
sudo reboot

In case your device doesn't show your carriers name in the indicator, just switch between 3G and 4G.

@dsimmons @dieharddan No, I'm not seeing those issues on my phone (T-Mobile/Magenta, Austria). What I've noticed is a different issue where ofono (UT-side) and rild (Android-side) don't communicate with each other anymore because rild runs out of IPC memory. Hard to fix since it's the proprietary blob acting up.

Your problem, it could be either differences in operators, but also there are specific models with different modem settings. In the case it's the modem settings, could you please post the output of getprop ro.boot.hardware.sku? Mine is G020F.

We have one known US citizen getting his compatible device soon, so at least we can verify and potentially fix those issues.

What I would propose for now, since it's your daily driver, is to revert to Android until we have a solution. Those issues are harder to fix than expected because most developers/porters who get into contact with ofono live in Europe. We will surely ping you in the thread as soon as we have something for ya.

@dsimmons that's interesting, thanks for finding that! I have built updated versions of some components and would like to see if they work for your use case:

• Download: https://drive.google.com/file/d/1HIZkTBRqypqeFz-p-AfDoqogFo7ukYsa/view?usp=sharing
• Download: https://drive.google.com/file/d/1G-WQNpbNLTsmaptDw4HaFC1GcwXfq9VO/view?usp=sharing
• Copy the two files to your phone's Downloads folder
• Run an adb shell and enter:

sudo mount -o remount,rw /
sudo cp ~/Downloads/libgbinder-radio.so.1.0.11 /usr/lib/libgbinder-radio.so.1.0.8
sudo cp ~/Downloads/libgbinder.so.1.0.47 /usr/lib/libgbinder.so.1.0.37
sudo reboot

It's certainly interesting that the rilmodem would just disappear from binder, so I'm eager to find out if that somewhat fixes your issue.

EDIT: Also, could you please verify with dmesg -w | grep -i binder in a separate terminal window if there are binder transaction failures coming up when your issue appears?

@Louie What you could do too is make ofono run in debug mode and figure out what is hanging here, or send me the log in private (it will contain dialed numbers and such):

Connect to the phone via adb shell, then run

sudo mount -o remount,rw /
sudo nano /etc/init/ofono.override

And append -n -d to ofonod's launch flags.
After a reboot you can obtain the log file from /var/log/upstart/ofono.log.

@Nathan123 I'm sorry but this is not a support forum for Magisk and rooting. Installing Magisk is not a prerequisite so please follow the instructions on how to install UT.

@Nathan123 rooting is not required but you need to unlock the bootloader. Follow this guide to unlock it: https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-3a-0198625/

After that follow the guide, including reverting to the last Android 9.0 factory image and installing via the UBports Installer.

@Louie Could you please try the following:

• Download https://drive.google.com/file/d/1T_00cBUyWrB3V-QLFxWPbmguYQ-gEdOn/view?usp=sharing
• Copy the file to the Downloads folder on your phone
• Open a terminal with adb shell
• Run:

sudo mount -o remount,rw /
sudo cp /home/phablet/Downloads/libgbinder.so.1.0.47 /usr/lib/libgbinder.so.1.0.37
sudo reboot

Also interesting for you, please try to replicate the change here:
https://gitlab.com/ubports/core/rootfs-builder-debos/-/merge_requests/18/diffs

In case you don't know how to do this:

sudo mount -o remount,rw /
sudo nano /etc/init/ofono.override

Remove the provision, from the file and save (Ctrl+o and enter, then Ctrl+x to exit) and sudo reboot for good measure.

Please make sure to try the combinations separately, if any of the changes fixes it it would be interesting to know which combination it was, so please remember that and let me know!

@Duhjoker the Pixel 3a is now officially in the installer, should be easy to get going now! Make sure to downgrade your phone as per instructions first.

@Duhjoker it's not officially in the installer yet. What you can do instead is follow this mini guide right here to force the installer: https://mobile.twitter.com/fredldotme/status/1322714885076275201

@dieharddan What you might also want to try is the two properties ro.ril.power_collapse & ro.ril.disable.power.collapse, these might change the behavior of the power savings mode.

• Reboot into recovery
• Connect phone to PC
• Open an adb shell with adb shell
• Enter the following commands:

mount /system_root
mount /system_root/var/lib/lxc/android/android-rootfs.img /tmp
busybox vi /tmp/system/etc/init/on-post-fs.rc

• In vi enter edit mode by pressing 'i' on your keyboard once
• Paste the following content at the end:

on init
    setprop ro.ril.power_collapse 0
    setprop ro.ril.disable.power.collapse 1

• Save and exit by pressing ESC + entering :wq
• Run umount /tmp
• Reboot