Sony Xperia X (suzu/F5121 & F5122)
-
@fredldotme These are very good news ! Thanks to you all !
-
@fredldotme Many thanks for answer. Are you going to implement working video recording and flashlight directly to your builds ? Thank you.
-
@ab2x2 no, the suzu images are built straight from the devel (or edge on arm64) channel. The gst-droid work will land when it's ready, for now you'll have to follow the guide until it is merged and part of the normal repo.
-
Hi guys,
I'm the only one where many apps did not work anymore. They display a white page and that's it.
Someone told me it may come from : "I guess thats due to the removal of oxide.(?) People need to update their (web)apps to use Morph.Web or something instead.", is that confirmed?
Thanks -
Also changed my F5122 from Sailfish to UT to see how everything works and I must say pretty well so big thanks for the dev!
As I see that Anbox should work in X is there any instructions how to install it? It's not on "supported devices" list yet.
-
Falshed today UT to suzu: works amazing. Unfortunatly no "donate" button here. Had to donate on xda to u. Thank u! I appreciate your work very much: to have a mobile working privacy friendly alternative more to android is important. Thanks!
-
Hi guys,
now my apps are working again :). But I have another problem.
I've downloaded the Ubuntu Touch version 250 but when I click on install, it ask me to click on intall and restart, and when I click on this ... nothing happens.I've tried apt-get update but it failed saying some reference are missing or replaced.
Any hints ?
Thanks
Mathieu -
@mousse04 said in Sony Xperia X (suzu/F5121 & F5122):
on install, it ask me to click on intall and restart, and when I click on this ... nothing happens.
Did you download on 2 days but not install on the first day?
-
@Flohack Exact
-
@mousse04 This is a known bug, you need to clean out the cache of system-settings with the UT tweak-tool then it will work again. Or use the installer...
-
Thanks @Flohack
-
This post is deleted! -
@fredldotme Thank you for your great work. Except of the fingerprint reader everything is working.
I have I have two things to comment.
First of all. It was really pain to update to android 8 first. But it is nessecary. I tried to install without updating from 6 to 8 because the Android won't update and I was to lazy using Flashtool.
Second. The power consumption is really high. The System sucks 70% in idle mode overnight. What is your experience? Is there a possibility to reduce energy? I installed sim, telegram, mail, nexcloud sync for calendar, files and contacts. But that should not need much energy.
-
@RubbelDeCatc
Hello
Little bit unrelated but just something that crossed my mind reading your comment and maybe getting myself Xperia X later for Ub.Touch.- Updating to Android 8.0 isnยดt that something you can do with Sony Emma Tool easily?
- After I installed Lineage OS on my Xperia X Compact I had much more battery drainage than before.
-
@ToxyPoxy said in Sony Xperia X (suzu/F5121 & F5122):
- Updating to Android 8.0 isnยดt that something you can do with Sony Emma Tool easily?
Well... I was optimistic and tried it without updating. I don't have windows installed.
- After I installed Lineage OS on my Xperia X Compact I had much more battery drainage than before.
So how long last a full battery in idle mode wifi and mobile on?
-
Without updating to android 8.0 it will not work, because the bootloader is not suitable.
-
@RubbelDeCatc Aha I understand, well I installed a sim card and charged it to 100% last night and now 13 hours later in Idle the battery is down to 61%.
-
@japsi said in Sony Xperia X (suzu/F5121 & F5122):
As I see that Anbox should work in X is there any instructions how to install it? It's not on "supported devices" list yet.
Just follow http://docs.ubports.com/en/latest/userguide/dailyuse/anbox.html and skip "flash a specific boot image" step.
In my case (F5122) it works. I used UT Terminal app:
sudo mount -o rw,remount / sudo apt update sudo apt install anbox-ubuntu-touch anbox-tool install sudo apt install android-tools-adb sudo mount -o ro,remount / cd /home/phablet/Downloads wget https://f-droid.org/FDroid.apk adb install FDroid.apk
and reboot... (not sure if it's needed)
There is no sound by default, see https://github.com/anbox/anbox/issues/904. You need to override system/etc/media_codecs.xml file. I was trying to figure it out via rootfs-overlay (https://docs.anbox.io/userguide/advanced/rootfs_overlay.html) with no luck. I repacked android.img with fixed media_codecs.xml file and now there is a sound and even choppy video via NewPipe app. I used this fixed media_codecs.xml file: http://dpaste.com/2H2CP58, it's all in one from these files: https://github.com/anbox/anbox/tree/master/android/media because "Include" and "Included" tags don't work yet.
Is there a way to apply anbox rootfs-overlay?
-
@c4pp4 Thanks a lot for this !! Just installed anbox and it works great !
For the audio issue I've tried to modify /system/etc/media_codecs.xml without success despite having mounted with write permissions. It made me ask myself, is the /system/etc/media_codect.xml file for ubuntu touch system or the android system ?
Could you post your modified android image or just tell us how to repack the image and how to upload it. Not sure where to start. Thanks in advance ! -
@henri2h You can't modify the file directly, it's Squashfs filesystem (see https://en.wikipedia.org/wiki/SquashFS). The best way to override it is via rootfs-overlay as I wrote.
To repack the image, you need some linux distro. Download the right android filesystem image from https://cdimage.ubports.com/anbox-images/. According to https://cdimage.ubports.com/anbox-images/devices.json it's android-armhf-64binder.img. You also need to have installed squashfs-tools package.
Uncompress the filesystem as root to keep uid and gid identities:
sudo unsquashfs android-armhf-64binder.img
you will see something like this:
Parallel unsquashfs: Using 4 processors 1429 inodes (5270 blocks) to write [=================================-] 5270/5270 100% created 1239 files created 274 directories created 190 symlinks created 0 devices created 0 fifos
it creates squashfs-root folder, locate squashfs-root/system/etc/media_codecs.xml file, rewrite it (as root) by the fixed one (http://dpaste.com/2H2CP58) and set the right owner:
sudo chown 100000:100000 media_codecs.xml
compress the filesystem into android.img:
sudo mksquashfs squashfs-root/ android.img -noappend -no-xattrs -comp xz
you will see something like this:
Parallel mksquashfs: Using 4 processors Creating 4.0 filesystem on android.img, block size 131072. [=================================\] 5080/5080 100% Exportable Squashfs 4.0 filesystem, xz compressed, data block size 131072 compressed data, compressed metadata, compressed fragments, no xattrs, compressed ids duplicates are removed Filesystem size 212128.35 Kbytes (207.16 Mbytes) 39.95% of uncompressed filesystem size (531034.87 Kbytes) Inode table size 23934 bytes (23.37 Kbytes) 33.61% of uncompressed inode table size (71204 bytes) Directory table size 16322 bytes (15.94 Kbytes) 43.33% of uncompressed directory table size (37666 bytes) Number of duplicate files found 38 Number of inodes 1703 Number of files 1239 Number of fragments 229 Number of symbolic links 190 Number of device nodes 0 Number of fifo nodes 0 Number of socket nodes 0 Number of directories 274 Number of ids (unique uids + gids) 4 Number of uids 2 unknown (100000) unknown (101000) Number of gids 4 unknown (100000) unknown (102000) unknown (101000) unknown (101003)
Copy the new created android.img file into the phone's home folder into anbox-data and rewrite the original one.