@stefano Chrome doesn't work. Opera mini neither...

@stefano Whatsapp and Viber work for me...

@mariogrip Thank you for all the help! Yes, I installed WhatsApp and Viber. Do you thing the battery drainage might be because of these two apps?

Yes, anbox-tool disable stops the battery drainage so is definitely not the kernel's fault.

I was misled by the situations when android apps would not start (thinking this is because of the container not running) but the battery drainage being still constant. Later I discovered that the services can be stopped with anbox-tool disable and then battery drainage stops.

There is still this question: sometimes the android apps would not start and I cannot login into the container and then my only solution is to restart the device. Is there a command to restart the android services or the container or something?

Again, thank you!

@brywilson anbox-tool disable does the trick! Thanks! The battery consumption is now back to normal...

"To change the app order in the Apps scope, just long press and drag." - if I long press an app icon, it goes to the option of uninstalling it. I cannot order apps in Apps scope...

There is a constant battery drainage which occurs now after installing anbox. @mariogrip Could it be something related to the kernel? - like maybe it doesn't know how to go into standby or something... It is not related to using the phone or having the android apps on or even the android container on - it is the same drainage even when the container is not on and I cannot start the android apps.

@matteo I wrote in that github issue as well: IMEI, SIM and Camera work. I still have to check GPS. There is a battery drain which I will detail bellow.

@tricky In my very poor understanding, somehow the anbox-tool does not reflect the state of the android container. So, the android apps can still work even though anbox-tool status says that is not running. For me, the true way to find if the android container is not running is to try to login into it with sudo lxc-console -ndefault -P /home/phablet/anbox-data/containers -t0 - when it's running I can login and when it's not then it says so. Why would I need that? - because if an android app does not start then I need to find if it's because of the android container not running, in which case I don't know how to start it except by a reboot of the phone :(

Maybe @mariogrip could help us with the command to start the android container? :)

@brywilson I only did what is recommended on this page, using the anbox-boot-turbo-test.img. I had previously tried to install anbox and it didn't work (the previous anbox-boot-turbo.img kernel) so an anbox android image was already on my device so anbox-tool install didn't work. I then used anbox-tool upgrade and then everything worked. Regarding logging into the container, yes, I use the sudo way. Yes, there are a lot of debugging messages flooding the screen but in spite of that I type the commands (thanks @Alkis for the code above)and then I hit enter and this is how I got the apk(s) installed.

I can confirm that the turbo-test img works on the Pro 5. I also installed WhatsApp and it works. I am so very glad and delighted about all this work!!!