Anbox for Debian

[a-wai]

Looks like you have to add contrib to /etc/apt/sources.list for apt install to work but there appears to be a further problem with modprobe failing to find binder or ashmem in the kernel modules directory. I'm guessing there's a further step beyond enabling them in the kernel?

They're not modules anymore, so no need for modprobe now.

[nas]

They're not modules anymore, so no need for modprobe now.

Seems the anbox container manager service tries to modprobe ashmem and then stops in error state.

This issue might give some clues, eg binderfs appears unset in current kernel config.

[User 18618]

Note: These instructions may be outdated, use them at your own discretion.

See below the updated instructions for installing Anbox, as of kernel version 5.7.

Derived from the original post. Thanks, @nas 

---

• Consider installing SSH to ease installation
  

Code:

sudo apt -y install openssh-server

• The client may refuse to connect, if so...
  

Code:

sudo systemctl enable ssh.service && sudo systemctl start ssh.service

• Determine the PinePhone's IP address
  

Code:

ip a s dev wlan0 | grep -oP 'inet .*' | cut -d ' ' -f 2

• Connect from the client, optionally entering the PinePhone's IP address to the hosts file and copying the client's public cryptographic key
  

Code:

printf '%b' '\n192.168.0.10\tmobian\n' | sudo tee -a /etc/hosts
ssh-copy-id mobian@mobian

ssh mobian@mobian

Influenced by  LINMOBnet's video on Anbox.

---

• Download anbox-image-working.tar.gz from the browser, optionally transferring from the client
  

Code:

rsync --progress ~/Downloads/anbox-image-working.tar.gz mobian@mobian:/home/mobian/Downloads

• Append contrib to the default SourcesList
  

Code:

printf '%b' 'deb http://deb.debian.org/debian bullseye main contrib\n' | sudo tee /etc/apt/sources.list

• Install the requisite packages
  

Code:

sudo apt -y install anbox adb

• Unpack the Android archive
  

Code:

tar xf ~/Downloads/anbox-image-working.tar.gz

sudo mv ~/Download/anbox-image/android.img /var/lib/anbox

• Create a unit file for binderfs
  

Code:

printf '%b' "[Unit]\nDescription=binderfs\n\n[Mount]\nWhat=binder\nWhere=/dev/binderfs\nType=binder\n\n[Install]\n" \
"WantedBy=anbox-container-manager.service\n" | sudo tee /etc/systemd/system/dev-binderfs.mount

• Edit the anbox-container-manager.service unit file
  

Code:

sudo sed -i 's/After=network.target/After=network.target dev-binderfs.mount/' /lib/systemd/system/anbox-container-manager.service
sudo sed -i '6i Requires=dev-binderfs.mount' /lib/systemd/system/anbox-container-manager.service
sudo sed -i '\_^ExecStartPre=/sbin/modprobe_s_^_#_' /lib/systemd/system/anbox-container-manager.service

• Reload the service
  

Code:

sudo systemctl daemon-reload
sudo systemctl restart anbox-container-manager.service && systemctl --user restart anbox-session-manager.service

The Anbox workaround originates from Mobian Issue #63. Thanks Djhg2000

---

• Anbox must be open to allow installation of APKs via adb
  

Code:

anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity

• Download and install an APK - APKMirror is a trustworthy source
  

Code:

adb install InsertAppName.apk

Android applications can be launched from the Phosh launcher (as .desktop files), or from the Anbox Application Manager.

---

Experimental: Implementing IP routing (for internet connectivity) and installation of MicroG is covered in the original post.

[Transistor4acpu]

I followed the guide but anbox session-manager still tries to load binder/ashmem kernel drivers.
Error:
[session_manager.cpp:136@operator()] Failed to start as either binder or ashmem kernel drivers are not loaded

But the anbox container manager is running.

[User 18618]

LINMOBnet uploaded a video about Anbox on Mobian.

Interestingly, Android's soft keyboards appear to be functional, but do not render.

[User 18618]

@Transistor4acpu Please try the updated instructions with the new workaround.

Apologies for the gratuitous whitespace - the WYSIWYG editor hates code fencing.

[vanja]

Hi,
anynbody tested anbox recently? is the keyboard still not working? I mean its working but it's invisible

I wonder which will become usable first, anbox or glodroid. whatever happens first will be my daily driver as I need whatsapp (for work). My current phone is in a desperate need for replacement, and it feels stupid buying another 150$ phone right now when pinephone is so close of being a usable device

[User 18618]

I believe postmarketOS recently got Anbox working 'out of the box'.

I've not tried Anbox since updating the instructions above, so I'll add an edit to make it apparent that it may not be 'state of the art'.

[nas]

anynbody tested anbox recently? is the keyboard still not working? I mean its working but it's invisible

I wonder which will become usable first, anbox or glodroid. whatever happens first will be my daily driver as I need whatsapp (for work).

I wouldn't rely on anbox+whatsapp as a solution for work.

Better off waiting for a glodroid release which enables the modem - in the meanwhile, whatsapp works fine over wifi.

[rik-shaw]

anynbody tested anbox recently? is the keyboard still not working? I mean its working but it's invisible

I'm trying to get Anbox running in Mobian but am having trouble finding adb or android-tools-adb in the repositories. What repo is it in? I have bullseye main contrib enabled, but not found.

Code:

deb http://deb.debian.org/debian bullseye main contrib non-free

For keyboard, it seems that using virtboard instead of squeekboard should work??