I have given a try (OSM Scout Server icon):
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?
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.
Not sure if it's the right place to ask but can someone please rework OSM Scout Server icon to be a regular square? I think it's pretty ugly now.
a) I open the Clock App when I want: alarm
b) I normally open the Clock App from: indicator-datetime
c) I think Clock App misses: alarm volume fade in
d) Clock (the time): 1
e) World Clock (more than 1 city clock): 1
f) Alarm (wake me up): 4
g) Chronometer (timer with laps): 2
h) Timer (count down): 2
i) I have been using Ubuntu touch as my main device since: April 2020
This Halium abstraction uses a 4.4 kernel provided by Sony and CodeAurora,
thus has the benefit of taking advantage of upstream kernel patches
and follows Ubuntu's Xenial kernel series for AppArmor updates.
This opens the door for potentially decade-long support of kernel patches.
The Halium suzu device platform is determined to support Snap packages
and is well positioned to do so long term.
You can add your comment but I think they don't care about it. @UniSuperBox moved it from QA to Done regardless the problem.
@wvi OK just for sure, when your device is booting, do you see the message "Your device has been unlocked"?
You can try booting Ubuntu 20.04 live from flash drive and using snap ubports-installer to exclude some kind of your system environment problem.