It may be the easiest way to get a functional asynchronous IM app that has E2E encryption.
gpg --recv-key 37D2C98789D8311948394E3E41E7044E1DBA2E89
scurl-download FDroid.apk https://f-droid.org/FDroid.apk
scurl-download FDroid.apk.asc https://f-droid.org/FDroid.apk.asc
gpg -v FDroid.apk.asc
sudo apt-get install anbox adb
adb install FDroid.apk
An Adnroid x86 image turns out to be needed at a certain location
scurl-download android_amd64.img https://build.anbox.io/android-images/2018/07/19/android_amd64.img
scurl-download android.img.sha256sum https://build.anbox.io/android-images/2018/07/19/android_amd64.img.sha256sum
Not signed but hashed. Server uses Let’s Encrypt which is better than nothing.
sudo mv /home/user/android_amd64.img /var/lib/anbox/android.img
sudo modprobe ashmem_linux
sudo modprobe binder_linux
sudo service anbox-container-manager start
anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity
Process stumbles at adb apk install step. Anbox doesn’t appear under the adb devices list. Launching it manually, a window opens and then it crashes.
FDroid apk signing key still uses SHA1 despite a SHATTERED 2 attack published recently. Someone needs to let them know. They already had a forum topic about it two years ago but it never went anywhere.
Some related bug reports.