Anbox + Plasma Mobile on a Pinephone?

ARM Plasma Mobile
6

A few other things:

  • If you need to completely remove anbox, you need to do the following, assuming that you didn’t mess with the services too much:

    $ sudo systemctl stop anbox-container-manager
$ sudo rm -rf /var/lib/anbox/
$ sudo pacman -R anbox anbox-image-aarch64

  • Upon a fresh install of anbox, consider making a backup of /var/lib/anbox/, or at least the data, rootfs, and android.img folders/files within. If you nuke the anbox folder and restore those 3 entities then it’s like re-installing anbox. The container manager service should be stopped of course.

  • I’ve never seen gles2 extensions populated when I run anbox system-info on my pinephone. Anbox runs fine without it, for me at least.

  • According to this post, the binder module is already included in the Manjaro kernel. I followed the advice in this post to see if the binder module was loaded. for me I get:

    $  ls -1 /dev/{ashmem,binderfs} 
/dev/ashmem

/dev/binderfs:
binder
binder1
binder-control
hwbinder
vndbinder

  • In any case, as long as those devices were present above, anbox runs fine even if it shows binder: false under anbox system-info. I think it’s something related to this issue. Also, this unit in the anbox-manjaro PKGBUILD seems to mount the expected binderfs device, but honestly I didn’t dig too far into it.

  • There is a lot of troubleshooting info out there for anbox that is no longer relevant to current versions, or is only relevant to the snap build–be careful with it.

  • Anbox just worked for me on the latest updated manjaro plasma-mobile image for pinephone. I did not have to mess with any other services or mounts like in this thread. It just worked for me, provided that I launch from the active desktop session NOT {over SSH OR over tmux/screen}.