Android Emulator on 4.1

User Support General
21

Ok, that what I did then.

well, I did follow your step, but didn’t succeeded.

adb didn’t listed any devices.

After running:

$ sudo modprobe ashmem_linux
$ sudo modprobe binder_linux

I could see the emulator listed by adb, but still anbox wouldn’t launch.

Anbox seems to be totally broken generaly speaking , but it’s weird that I can’t reproduce on my machine. The only difference is that I downloaded the img from a mirror ( the link from the post is broken ) and that debian template is a bit more up to date since your post.

Any idea what I could also try ?

22

Did you start anbox-container-manger.service before starting anbox?

23

not manually but I can see it with ps -aux

When anbox start, it pop a window with an android logo ( I thing its loading ) and then break

24

If you start anbox from the command line, do you get an error when it fails to start?

25

So I start my anbox standalone VM, this is my full prompt:

user@anbox:~$ ps -aux | grep anbox
root         760  0.0  1.6 113168  5552 ?        Ssl  18:12   0:00 /usr/bin/anbox container-manager --daemon --privileged --data-path=/var/lib/anbox
user        1342  0.0  0.2   6320   704 pts/0    S+   18:12   0:00 grep anbox
user@anbox:~$ adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached

user@anbox:~$ sudo modprobe ashmem_linux
user@anbox:~$ sudo modprobe binder_linux
user@anbox:~$ adb devices
List of devices attached

user@anbox:~$ anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity
[ 2023-04-10 16:16:00] [launch.cpp:202@operator()] Session manager failed to become ready
user@anbox:~$ adb devices
List of devices attached
emulator-5558	device
26

Don’t know why you are loading the kernel modules.

Just follow this guide, for me it works, but you need to manually start the service

1 Like
27

How do you manually start the server ?

28

sudo systemctl start anbox-container-manager.service

I just need to run that command before it start anbox.

29

sudo systemctl stus anbox-container-manager.service
show me that the status is already active.

I still get the same error :confused:

30

Bravo. This works today and is to-date the best method I’ve come across. The performance is blazing.
Thanks for sharing!

Unfortunately the anbox.io .img’s are no longer being officially served. Grab it from a mirror:

(probably a good idea to check the SHA actually matches, thus a legit mirror file. I only used it to test install so wasn’t worried)

2 Likes
31 
user@anbox:~$ sudo modprobe ashmem_linux
user@anbox:~$ sudo modprobe binder_linux
user@anbox:~$ sudo systemctl restart anbox-container-manager.service
user@anbox:~$ sudo systemctl status anbox-container-manager.service
● anbox-container-manager.service - Anbox Container Manager
     Loaded: loaded (/lib/systemd/system/anbox-container-manager.service; enabl>
     Active: active (running) since Mon 2023-08-07 08:28:23 EDT; 1s ago
       Docs: man:anbox(1)
.............
Ctrl+C
user@anbox:~$ adb devices && anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity
1 Like
32

I am able to install everything but cannot run anbox. I also get the session manager error:

$ anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity
[ 2023-08-30 18:32:13] [launch.cpp:202@operator()] Session manager failed to become ready

Sometimes a window opens with the android logo, but it closes and then the error is printed.
I do have the anbox-container-manager.service systemd service active.

1 Like