CRITICAL: Introduce some means of completely uninstalling Anbox for hobbled installations, and starting from fresh

[TartanSpartan]

• Device: Arale
• Channel: Devel
• Build: Any recent ones

Steps to reproduce

Following the standard guide to install Anbox, with the bespoke Arale image shared in this forum thread:

https://forums.ubports.com/topic/1679/how-to-anbox-for-meizu-mx4-arale

This was working fine initially. I installed APKs for stores including FDroid and Yalp and a few random apps. I then tried to install Amazon Kindle*. This was evidently a bad idea because it destabilised Anbox and therefore Ubuntu Touch. Android apps would not run, and on every boot, I would have about 1-2 minutes before a restart was forced. My only recourse was to rush to run anbox-tool disable. This stopped the problem, but of course also stopped Anbox and did not allow for full triage of the problem. I tried to do a full rm -rf *indle* to purge the APK and all of it's installed folders; this did not help. Today, I attempted a reflash of the 16.04 devel image (no wipe) to try to purge Anbox, and also ran sudo apt remove anbox-tool && sudo apt purge anbox-tool. I then repeated the kernel flash and installation procedure.

*Note: Just today, I installed the snap-based Anbox on Ubuntu 18.04 on a laptop for testing. I tried to install Amazon Kindle here too via Yalp (spoofing the laptop as a Fairphone 2), but it said it was not compatible for my (emulated) phone. Now I'm not sure if that means for Anbox on an x86-64 snap-based system, or for Anbox on any system, but given it completely hobbled Anbox on my MX4, I suspect it might be the latter.

Expected behaviour

After a (presumably) full purge of all things Anbox, reflash of Ubports, Anbox kernel flash and Anbox reinstallation, the former problem would vanish at some point and Anbox would no longer be non-functional as the assumption is that the system is starting from fresh with regards to the program.

Actual behaviour

The expected behaviour does not occur. At no point does the critical problem of a hobbled Anbox installation become undone. Surprisingly, not even with the Anbox kernel flash. Therefore, it is imperative for Ubports to either document ways from a system admin perspective or via some uninstaller tool to entirely wipe all traces of Anbox from the phablet, at all levels, including kernel. This should permit a fresh installation to be done exactly as the original first installation was done, and then the user can continue using Anbox (armed with the knowledge and experience to avoid installing certain APKs, in this case Amazon Kindle) without issues. This is especially important for when Anbox is intended to be entirely stable and becomes a part of the system image for a future UT OTA. If this cannot be done, the only remaining option is to completely wipe and reinstall Ubuntu Touch, which for obvious reasons is very undesirable.

Logfiles and additional information

Where would I find relevant logfiles for this issue? And remember, if I need to have Anbox enabled to obtain these files, the short time the OS can run whilst it is enabled might even prevent me from being able to obtain them in time.