@dobey said in Anbox in OTA-16 Release Candidate:
@antidroid said in Anbox in OTA-16 Release Candidate:
I hope the devs have solved the battery drain issues that Anbox is reported to cause or that just another reason Anbox should not be installed by default.
No, the battery issues are not solved. But again what is installed by default is only the components necessary for people to install and enable anbox. The anbox image and apps are not installed nor enabled by default.
You are 100% correct. I just had to run one more test to confirm for myself.
I ran
apt list anbox*
and got
anbox/now 8+........... armhf [installed,local]
anbox-common/now 8+........... all [installed,local]
anbox-ubuntu-touch/now 8+........... all [installed,local]
then I tried
anbox-tool disable
to which it says you need to run install
So it looks like the only step you have to take to install a container with the Anbox system image is
anbox-tool install
Which should install a container with a minimal android system inside of it. As to why it saw my old Anbox .desktop files is still a mystery. I did not have any other components of Anbox installed on stable and the container and all of it's config files had been wiped. I should have tried running them before deleting them, it would have been obvious they were not linked to any programs.
Conclusion :
Everything required to install an instance of Anbox in a container on a OnePlus One Bacon (and a few other devices) is now installed but not active. It only appeared to be active for me because of residual .desktop files from previous Anbox tests.
