Anbox runs Android apps on Linux using a trimmed down version of Android in a container. Anbox allows one to use Android applications sandboxed, running alongside the native Linux programs. It can be very handy to help people switch from Android to an operating that respects their privacy.
See milestone#7 for current progress.
postmarketos-anbox package. Launch using
anbox-launch or the icon launcher.
If Anbox have never been working on you device, you may have to add kernel support for it. Use
pmbootstrap kconfig check --anbox (from
!1916) to check.
I don't have access to the internet
Anbox require an anbox0 bridge interface to access the internet.
ip link should report an anbox0 interface for the network to work. There seem to be some kind of kernel requirement too, see pmaports#480 (contains workaround) for the investigation about that.
When I start Anbox, it complains about DBus
[daemon.cpp:61@Run] Failed to request DBus service name means dbus isn't running, or that you launched it incorrectly (check environment variables are set with
env). Ensure you start dbus with your session and that you are not starting Anbox with ssh.
If you never see the application manager, there can be plenty of problems. The first step to debug this is knowing roughly where it fails.
Check the openRC service
rc-service anbox-container-manager status will give you the state of the container manager. If it reports to be stopped despite your attempts to start it, then the container manager exited. Tell me that the container manager doesn't run in a bug report and include
Check if the container is up
If the container manager runs, it doesn't necessarily means the container android runs in is started. To check if the container is up and running, you can try two things can give interesting clues:
- check what it answers when you run it.
Failed to start containeris a pretty obvious way to tell the container doesn't run; but sometimes the session manager will segfault instead. You usually can still tell if container is started.
- the file will (hopefully) contain a non-empty log. Look for
Received container state "ABORTING" instead of "RUNNING"or
Set container state to "STOPPED".
In this case, tell me in a bug report that the container itself doesn't run and include
adb shell. If you do have a shell, that's great, Android at least started to start. If adb answers you that no devices/emulators are found and the container is running, then tell me in a bug report that adb couldn't find the device and include
adb install works
Download an apk, for example the F-Droid one and try to install it. For example,
adb install Dowloads/FDroid.apk. If this doesn't work, then Zygote probably didn't start. If you can get a shell, but can't install an app with adb, tell me in a bug report that adb install doesn't work and include
adb install works, congratulations, we have only got Anbox to run that far once or twice so far. Please still open an issue if you don't get the anbox application manager to show up, including