Development testers for Anbox

So anbox is slowly maturing, it has now come to the point where we need tests to verify that anbox works on all supported devices before we update docs and set anbox as "ready to test". So this is really really early testing so do expect failure. This is so called "development test" where many parts has not even been tested by the developer, in this case not all devices has been tested by me.

NOTE! If you don't know how to recover from failure, please wait for a "ready to test" version!

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).

@mariogrip Come on Marius, throw us a bone! Update the Anbox image for Pro 5. You said long time ago, that you have a anbox that works with Mobile network and while you uploaded the anbox images for other devices, you did not update the one for Pro 5. So we can't test it as there us nothing new to test.
Thank you.

This happens when the backend container session daemon is not running, so this is anbox trying to start a container session as user but failing, there is no "error" messages so it just get stuck (or crashes) here. So what we want here is to display an error message instead of this, but not implemented yet.