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

Good news! Over the last few days we enabled initial support for SMS & MMS on the Pixel 3a & 3a XL on US carriers. A bunch of other fixes made it into the current release candidate to perfect it but this is the big one.

SMS work reliably on 4G now and MMS partially work (lacking proper Group MMS support right now). The phone doesn't trip off the carrier with its incomplete IMS support too.

If you want to make sure you can reliably receive MMS please make sure your APN settings are compatible, either by changing the settings or, if the system-settings GUI doesn't work, by editing the /var/lib/ofono/<number>/gprs file manually, or by disabling the Internet APN completely. Staying off WIFI is also reported to work reliably.

EDIT April 3rd 2021: NFC support is now in the devel channel and will be released with OTA-17
Please use this thread as a place to exchange ideas regarding our NFC implementation.

Original post:

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.

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

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'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

As the maintainer of the Pixel 3a port I support this. I would really like to see more involvement from US developers to fix the remaining cellular issues. I would also throw in $100 into the mix.

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

@attah I'd be more than happy to work together and keep the name SeaPrint for sure. It needs some massive changes to building the thing and its dependencies though, so I thought at first that a hard-fork would be justified. Let's have a chat here in DMs if you want.

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

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

The ability to stream the virtual display in desktop mode to a Chromecast receiver would first of all imply additional development resources and donations for me to consider it, and secondly probably some kind of NDA shenanigans to not open up the Chromecast implementation to the public (since none of the "blessed" implementations are open source).

Miracast is an open standard, Chromecast is not.

Regarding maintenance of the port: I'm still working on it as the community found a way to finance development for a short period of time.

Regarding GPS: do you have a SIM inserted? Usually a location fix comes faster with a SIM card inserted.

Regarding other channels: don't let the selection fool you, there is no way to switch to a different channel. Also we don't quite know yet why it's showing multiple devel channels.

@chriswyatt a software tester with the skills to build an image alone is highly appreciated I'll update the thread in case of new developments.

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

@chriswyatt when unplugging headphones during a call it switches the output to speakerphones. Generally the headset detection is something I'd like to fix next.

If you checked my GitHub repo recently (or watched one of the last Q&As) I did precisely that: backporting Wireguard.

It's just that the app in the OpenStore is completely dysfunctional for anyone with a sudo password.

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?

@domubpkm If you understood the workload involved to update Qt and it's submodules for an old version you would probably also understand that this is more than one should ask for in the first place.

The short answer is no, the long answer is: there is no sane point in keeping unsupported things around if nobody cares for (not "cares about") them. In other words: Suppose I care about pudding, I don't care for it, hence I want to consume pudding, not watch it grow mold.

In the end people need to move on, and as long as people stick with xenial just because they believe there is a point (that includes port maintainers, system integrators, app developers, and users) the resources will be spread too thin and the result for focal and what's beyond will look poor. The only real solution is to move on fast, period.