Sony Xperia X (suzu/F5121 & F5122)

kugiigi

Is there a way to make sure the Xperia X we will get is the correct version?
Perhaps in the about page on Android we can see the model?

Nikfrager

Yes, you can see it.

sahirul

@fredldotme oke thank

hsabun

@fredldotme Sir i have xperia x f5122, can i install on it?

UniSuperBox

@Hsabun
No, F5122 is not F5121

extraymond

Nice!!! Does this support anbox? I'm still deciding to get a oneplus 3 or xperia x to help testing. Any suggestion?

fredldotme

@extraymond It should as all the necessary kernel changes are in, but the installation will fail for now. I'll ask if it's possible to whitelist the Xperia X to gain Anbox support.

extraymond

@fredldotme Thx! Looking forward to use this as my n5 replacement.

henri2h

Thanks for this port !! Having a great time using Ubuntu touch for the first time !
Using the last release in the development branch I am not able to pair with any device using bluetooth. (I have tried to connect to a bluetooth headset and a speaker). Trying using the terminal with bluetoothctl doesn't work neither. Is it something specific to this branch or I have missed something.

tuxus

Hi Guys, there is an error connecting the Xperia X via USB cable under KDE Desktop.
I fixed the bug by adjusting the following file:

/lib/udev/rules.d/69-libmtp.rules

The entry:

ACTION! = "Add", GOTO = "libmtp_rules_end"

must be changed to:

ACTION! = "Bind", ACTION! = "Add", GOTO = "libmtp_rules_end"

It is important for the time being that the developer mode is deactivated on the Xperia X and in the UTtweaktool in the ADB settings RNDIS is activated.

Thus, in the file manager via USB to the phone memory can be accessed.

This works for me.

Best regards

hxa5e

I also encountered

Cache formatting was not succesful, flashing may fail, check your partitions on deviceFailed to enter Recovery

with the old instructions. With the new instructions with the installer, the installer is stuck at Flashing firmware forever.
I am not sure if I followed the instructions correctly.

Even though the output looks correct, the OS looks the same after booting, not like AOSP:

[root@localhost platform-tools]# ./fastboot flash oem ./SW_binaries_for_Xperia_AOSP_N_MR1_5.7_r1_v08_loire.img
Sending 'oem' (220783 KB)                          OKAY [  6.926s]
Writing 'oem'                                      OKAY [  3.553s]
Finished. Total time: 10.536s

It says Make sure to upgrade your device to the latest stock Android 8.0 before continuing. The Xperia X does not support Android 8, does it? Does it matter which service I choose in the Emma flash tool?

tuxus

@hxa5e Xperia X support Android 8

makeixo

This post is deleted!

makeixo

@hxa5e

Make sure to upgrade your device to the latest stock Android 8.0 before continuing:

Nikfrager

This post is deleted!

PjsP

I'm using a Nexus 5 with Ubuntu Touch (with no problems) and I'm about to buy a Sony Xperia X 5" 3/32gb Black F5121P.
I read than its fine with the F5121, can you tell me if UT works well with the F5121P?

extraymond

@fredldotme Hi! I accidentally tried installing F5122 using the F5121 option in the ubport installer, and it went on installing successfully. It even let me booted one time before failing to boot again.

If you need to test anything to get ubport on F5122 as well. I'm willing to help.
Thx again. Awesome stuff you're doing.

fredldotme

@PjsP I wasn't aware of there being a F5121P model. It looks the same as F5121 but don't take my word for it.

Lioh

Halium recovery does not clear the cache completly. For a new device it is necessary to install TWRP first after unlocking the device. It can be downloaded from here: https://dl.twrp.me/suzu/twrp-3.3.1-0-suzu.img.html and flashed in Fastboot Mode (Power on + VolumeUp = Blue LED) using:

fastboot flash recovery Downloads/twrp-3.3.1-0-suzu.img

Afterwards boot into TWRP and select Wipe / data, system & cache partitionen. Continue with the installation (OEM Binaries / UBports installer)

Lioh

On my device the location service is not working at all. Neither in the Weather app, nor in apps like puremaps or uNav. Does anyone else experience this issue?