Sony Xperia X (suzu/F5121 & F5122)

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.

c4pp4

@fredldotme
/etc/pulse/daemon.conf

default-sample-rate = 44100
alternate-sample-rate = 48000

/etc/pulse/touch.pa

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

syslog

May 15 03:06:10 ubuntu-phablet pulseaudio[6939]: [pulseaudio] droid-util.c: Requested sample rate 44100 but got 48000 instead.
May 15 03:06:10 ubuntu-phablet pulseaudio[6939]: [pulseaudio] sink.c: Default and alternate sample rates are the same.

It always falls to 48kHz. It's weird.

c4pp4

This post is deleted!

jro

@c4pp4 It is strange though, that there is no documented way of getting the ubports version of android to use rootfs-overlay, just as the snap version does. Indeed, repacking the squshfs isn't such a big deal (although I wouldn't have known of the parameters you used, but still, just dropping a file into the overlay directory tree would make things so much easier!
BTW, the sound that you get from android apps after completing this step is quite choppy, not really suitable for real use, more a proof of concept.

jro

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

@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

There is no directory /system/var/lib in recovery mode, I also cannot find a system.img anywhere. Has this changed recently?

Edit the Halium override file to your liking: nano /tmp/halium/etc/pulse/touch.pa

Wouldn't this be the file /system/halium/etc/pulse/touch.pa?

EDIT: losetup -a says that /dev/loop0 is pointing to /halium-system/var/lib/lxc/android/system.img, yet there is no directory /halium-system. How can I access it?