Anbox in OTA-16 Release Candidate

AntiDroid

@dobey Thank you. I just ran

grep -r -H anbox

and the .desktop files for all the anbox stuff were still in the applicatuons folder. I have removed them now. Hopefully that was the only reason they showed up after the update.

Now the only thing left are records of me removing them in bash-history and zeitgeist enteries. I still have to wait before retesting the release candidate again.

I also tried to grep the root folder for anbox stuff but that caused the phone to reboot.

kugiigi

@antidroid I think your purged the anbox tools that are used for installing actual anbox. Try Rodney's suggestion. To be fair, anbox documentation needs to be updated. Other stuffs there are not needed anymore like kernel installation.

AntiDroid

I had a chance to quickly test the release candidate again and on this boot the icons were gone so that seems to confirm they were left behind from the previous install.

On stable when i try and remove anbox-ubuntu-touch it says it is not installed. But when i try on RC i get

Which you can see would remove ubuntu-touch, ubuntu-touch-core and ubnutu-touch-hybris which to me means it is deeply integrated in to the core of UT now and can not be removed.

When I have enough time to run the RC channel (be without a stable phone) for more than a few minutes I will see if disabling anbox works.

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.

TL;DR OTA-16 for certain devices does indeed include Anbox by default but it is not enabled. I only noticed because of residual .desktop files from a previous Anbox install.

This is confirmed in the OTA-16 announcement,
"Anbox packages are now included with Ubuntu Touch by default. This means that supported Anbox devices can use Anbox without installing more packages, and Anbox installations will no longer break with every Ubuntu Touch update."

dobey

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

AntiDroid

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

UdenGoogle

I might comment in here that I cant see the point of getting the installation of Anbox and suddenly to get preinstalled so many useless apps from Android. Whats the point of it? It miught be a point, but I cant see it, sorry. It will be more awesome if we can decide by ourselves which apps we want, cause maybe we dont want any preinstalled?

arubislander

@udengoogle said in Anbox in OTA-16 Release Candidate:

I cant see the point of getting the installation of Anbox and suddenly to get preinstalled so many useless apps from Android.

A point might be to make it clear that Anbox has been installed correctly and to have a set of apps for a minimal test of what works and what doesn't in the particular installation.

It might also simply be that a minimal image of android always has that set of applications included.

It might be possible to modify this in the UT Anbox repos. But that just adds to the maintainance burden. So I would propose that questions about which apps are or are not included in a fresh install be raised in the upstream anbox project

Moem

@dobey said in Anbox in OTA-16 Release Candidate:

all you need to do is run sudo anbox-tool disable and then remove the ~/anbox-data/ directory and ~/.local/share/applications/anbox/ directories, and then the anbox apps and image should be gone from your device.

I'm having trouble with this. When I try to remove ~/anbox-data/ I get 'permission denied'. Any pointers please?

stanwood

@Moem The right key is:

sudo rm -rf ~/anbox-data/ ~/.local/share/applications/anbox/

Then, there are desktop files named anbox* at ~/.local/share/applications which you can delete the apps on the drawer

Maybe try that way

Moem

@stanwood said in Anbox in OTA-16 Release Candidate:

Maybe try that way

THANK you! I feel a lot happier now!

stanwood

@moem You're welcome!