Sony Xperia X (suzu/F5121 & F5122)

makeixo

@RubbelDeCatc Did you walk around outside a little like @fredldotme has stated above?

kos366

@RubbelDeCatc Have you read this article?

It seems you have to keep the display active and the GPS app in foreground to get a GPS fix.

That made ist working for me.

christophe14

Hi,

Just wanted to share that I managed to install successfully Ubuntu Touch on my Xperia X which was running SFOS before.

Here are the steps performed :

flash using Emma tool "F5121 34.4.A.2.107 Customized_FR 1302-3046 R4E User-Live COM" (Android 8.0) : kernel was not upgraded and mobile wanted to shutdown all the time
flash in fastboot mode twrp-3.3.1-0-suzu.img for recovery
boot in recovery mode and from twrp : wipe Cache, System and Data
reboot (oops can't boot, stalled with Sony image)
boot in fastboot mode and run UBports Installer 0.4.18-beta
select channel 16.04/community/fredldotme/devel, Wipe Userdata and Bootstrap
let the installation process run and discard any display on mobile
and it worked !

OK. I have to admit I stressed a lot while performing the different steps :anguished_face:.

Now, I am discovering UT on Xperia X and I am impressed by the work done on this phone :grinning_face: !

For the moment, I have noticed following issues :

front and back camera zoom are not working
back camera autofocus is not working

Congrats @fredldotme !

cybershaman

First off: big thanks for the efforts in porting Ubuntu Touch towards the Xperia X - gave the device a brand new life for me! (after unused Sailfish OS installation)

Secondly: I seem to be confused about the possibility to have Anbox on the Xperia X. Seems I do not have any repository that contains the "anbox-ubuntu-touch" binaries, no is there the "anbox-tool" binary preinstalled on the image.
If I read @c4pp4 's reply right, however, anbox-ubuntu-touch should be able to install via apt.
I have the ubports repo added via /etc/apt/source.list.d and apparantly am on the devel update channel fredldotme and receive updates, latest 2020-04-28/2.

Thanks in advance for any pointers!

eichenbast

@c4pp4 : Thank u very much: got Anbox working on my X !

eichenbast

@c4pp4 : Thanks again ! Now I have audio in Anbox ...! Can I ask u one question? Is it possible to port/fork the fm-radio App from unofficial lineageos X for anbox working?

jro

I unlocked the bootloader, ran the UBPorts installer but it only installed the Ubuntu recovery, not the actual system. How can I manually install ubuntu touch? the ubports installer always wants to reboot into fastboot mode, but the devices always ends up in ubuntu recovery.

Keneda

@jro said in Sony Xperia X (suzu/F5121 & F5122):

the ubports installer always wants to reboot into fastboot mode, but the devices always ends up in ubuntu recovery.

That sounds like an ADB driver issue, that happened to me with MX4 on windows with ubports, i had to link ADB driver to MX4 device three time, one time after booted normally (!with dev mod on!), another one when booted in fastboot, and a third when in recovery...

After doing that, i booted in normal mode, plugged in when asked by UBP istaller, that auto-detected device and then did all process in full auto mode.

Before that, process was not full-auto (had to reboot in fastboot) and i ended with recovery flashed but not UBports OS (difference is my device is canonical uTouch from beginning).

Here my full "story" : https://forums.ubports.com/topic/4026/solved-problem-upgrading-mx4-from-ota15-to-ubport/13

jro

@Keneda The actual issue is that Ubuntu Recovery reboots every 30 seconds or so. So before the Ubports installer gets anything done, the connection is lost. I found another owner of the same phone in the telegram chat who experienced exactly the same. I have pulled the /tmp/recovery.log from the device, I hope that it contains anything of use.

Keneda

@jro said in Sony Xperia X (suzu/F5121 & F5122):

the ubports installer always wants to reboot into fastboot mode, but the devices always ends up in ubuntu recovery.

With that i though you where ending in getting stuck with recovery, not a recovery reboot loop.

jro

@Keneda Yes, it took me a while to understand that. Unfortunately, there seems to be no way to get a log showing as to why it keeps rebooting. I am not sure as to how I am supposed to submit a useful issue on github.

jro

@jro Fixed it now, the key was to first install the OEM binaries for AOSP, as explained on XDA Developers. Great! Again, however, this has shown that vendor-locked devices are a nightmare, and as long as this is the case, one click installs will more often than not fail...

Keneda

@jro said in Sony Xperia X (suzu/F5121 & F5122):

as explained on XDA Developers.

Stated here in original poster first post from beginning...
https://forums.ubports.com/topic/3229/sony-xperia-x-suzu-f5121-f5122/1

c4pp4

@cybershaman said in Sony Xperia X (suzu/F5121 & F5122):

Secondly: I seem to be confused about the possibility to have Anbox on the Xperia X. Seems I do not have any repository that contains the "anbox-ubuntu-touch" binaries, no is there the "anbox-tool" binary preinstalled on the image.
If I read @c4pp4 's reply right, however, anbox-ubuntu-touch should be able to install via apt.
I have the ubports repo added via /etc/apt/source.list.d and apparantly am on the devel update channel fredldotme and receive updates, latest 2020-04-28/2.

Launch UT Terminal app and try to simulate an installation:

apt-get -s install anbox-ubuntu-touch

Submit a report of the command.

c4pp4

Audio is crackling... speakers, headphones... doesn't matter. Is it only in my case?

christophe14

@c4pp4
No, same for me.

cybershaman

@c4pp4 Thank you for the reply!
The anbox-ubuntu-touch package was available all of a sudden a week or so ago. Got everything installed and running.
Perhaps this was all related to the OTA updates.

c4pp4

@christophe14
I think I got something. I've tried some audio files with sampling frequency 48kHz and the output was clear. If you don't have some you can convert any via ffmpeg:

ffmpeg -i "original.mp3" -ar 48000 "new.mp3"

Maybe it has something to do with rate=48000 in /etc/pulse/touch.pa file:

.ifexists module-droid-card-24.so
load-module module-droid-card-24 rate=48000 quirks=+unload_call_exit
.endif

I'm not sure how to change the rate and test it. Maybe @fredldotme could help.

fredldotme

@c4pp4 nice catch!

What you can do to test small modifications to the Halium portion (where this file is from):

Reboot into recovery
Connect to the device via ADB
Mount the Halium system image: mount /system/var/lib/lxc/android/system.img /tmp
Edit the Halium override file to your liking: nano /tmp/halium/etc/pulse/touch.pa
Unmount the Halium image again: umount /tmp

I'd say you can then go ahead and make a pull request on GitHub with your changes if you manage to find a fix for your issues.

c4pp4

@fredldotme
Thank you. Unfortunately changing touch.pa has no effect on quality.