@xray2000 The method I have used to install apps is

$ sudo mv $APP ~/anbox-data/data
$ sudo lxc-console -ndefault -P /home/phablet/anbox-data/container -t0
$ cd data && pm install "app.apk"

substitute "app.apk" for the name of the apk you are installing and $APP for it's path outside anbox

EDIT: sorry, I miss typed the sudo command.

was anyone able to update FDroid's repos? Because I can't.

I just tested the new anbox update and yes, both the keyboard and network is working. I even made a whatsapp call to my father, for shits and giggles. It doesn't have sound as expected, but it did connect.

this is a screenshot of a msg, but I also made a call with no sound.
If we get the sound server working, we would be able to start making whatsapp calls! That would be awesome.
Anyway, it is already a great achievement.

Also, I noticed that sometimes, if you already have a anbox app window opened, anbox won't open another app

@xray2000 The method I have used to install apps is

$ sudo mv $APP ~/anbox-data/data
$ sudo lxc-console -ndefault -P /home/phablet/anbox-data/container -t0
$ cd data && pm install "app.apk"

substitute "app.apk" for the name of the apk you are installing and $APP for it's path outside anbox

EDIT: sorry, I miss typed the sudo command.

usually when I anbox is not starting, I just restart the ubuntu. It works most of the time. Is there a better way to make anbox run again? Also, for those not doing this, if you are connected to anbox through adb shell and lxc-console you can see debugging msgs of anbox in realtime on your PC. This helps a lot to understand what anbox is doing, since it includes error msgs.

"does is work in 'other phones'?"

The only thing specific to each phone, I belive is the modification in the "boot image" to include the requeried kernel modules (for ashmen and binder nodes in /dev). Modifications in the anbox.img are the same for everyone, I believe.

Hey mario, if you are going to confirm this, are there other modifications to the kernel or the boot img that you do?

I tested with nexus 5 and had similar results as the others. I was able to open the stock apps, including settings. One thing to note is that it has no internet device, so it was not possible to connect to the internet from withing the container. I was able to install and open whatsapp. But couldn't do much more than that without keyboard or internet.

I also installed FDroid, but again, no internet. I tryed to install aosp stock keyboard, but after that, I wasn't able to open any app. To be more precise, anbox doesn't initiate anymore for some reason. I'll try to reinstall and see if I can reproduce this problem to be sure it was the keyboard app that caused anbox to not initiate anymore.

That is it for now: all stock apps open, no internet, no keyboard. Kinda of slow too. Most important, flashing the modified boot didn't brick my phone (it happened once with another phone).