Anbox on Nexus 5
I noticed that the Inbox is missing for the Nexus 5...
Please suggest, is there any support for this device and is it possible to use one of the existing instances?
As well as whether it is possible to assemble yourself under the device?
Anbox will be implemented in 16.04. The current release of 16.04 is only intended for development/testing, as it is a work in progress. If you take a look at the FAQ on ubports.com, there is an entry on this when you scroll down a bit.
Will there be an easy way for us to upgrade to 16.04 ?
Flohack last edited by
@fred Yes it will be just to start the UBports Installer and switch the channel. Actually thats alreaddy working quite well now.
I know 16.04 is in development but I upgraded to it anyway. I am still using my blackberry as my main phone anyway. I would love to see ubports on blackberry leap as it seems to have a better battery life then my oneplus one. Anyway keep up the good work.
te-online last edited by te-online
I was wondering: What's blocking anbox from running on the Nexus 5. Is this something ubuntu touch needs to address or is it a cpu architecture that anbox needs to support first?
I'd be happy to help with anything I can, but would have no clue where to start
Edit: I guess it's that one:
In order to support the mandatory kernel subsystems ashmem and binder for the Android container you have to install two DKMS based kernel modules. The source for the kernel modules is maintained by the Anbox project here.
Edit 2: So, I followed this manual https://github.com/anbox/anbox/blob/master/docs/install.md and came pretty far.
I had to resize the root partition with this script https://askubuntu.com/a/721296/717375 and mount it writable
sudo mount -o rw,remount /to install the new kernel modules (of which I have no idea whether they work on ubuntu touch as well...)
Then I realized that
snapdoesn't seem to be included in this ubuntu touch image (at least for the Nexus 5 on 16.04). That's why I can't continue with installing anbox through the snap mechanism.
I guess the kernel needs to be adjusted to support snaps?
Now I'm hooked, but still can't see what could be a next step...
But there is a new answer by @advocatux below – let's see
advocatux last edited by advocatux
te-online last edited by
@advocatux Thanks, indeed I should stop and wait for Marius to release an image!