OS: Bullseye (stable)
GPU: Nouveau
Kernel: 5.10.0-8-amd64
Anbox was installed from Bullseye's repo.
1) I enabled Android Modules:
$ sudo modprobe ashmem_linux
$ sudo modprobe binder_linux
---
2) I checked if they were enabled:
$ ls -alh /dev/binder /dev/ashmem
Output:
crw------- 1 root root 10, 61 Sep 27 04:40 /dev/ashmem
crw------- 1 root root 10, 60 Sep 27 04:40 /dev/binder
---
3) I installed Anbox's official Android Image from their repo to:
/var/lib/anbox/android_amd64.img
---
4) I restarted Anbox Container:
$ sudo service anbox-container-manager restart
---
5) I launched Anbox:
$ anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity
6) It get's stuck at "starting" and quits
7) On SystemD's logs I get:
anbox-session-manager.service failed to start
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
[SOLVED] Anbox won't launch on Bullseye
- Xeno Idaltu
- Posts: 47
- Joined: 2019-08-15 05:36
- Location: Free-Source Technocracy
- Xeno Idaltu
- Posts: 47
- Joined: 2019-08-15 05:36
- Location: Free-Source Technocracy
Re: [SOLVED] Anbox won't launch on Bullseye
The problem was that we need to rename /var/lib/anbox/android_amd64.img to /var/lib/anbox/android.img
anbox-container-manager.service is active and running
But I'm still getting:
anbox-session-manager.service failed to start
This is the Unit File, it wants to use /usr/bin/anbox but the package came with no configuration or symlink..
[Unit]
Description=Anbox Session Manager
Documentation=man:anbox(1)
[Service]
ExecStart=/usr/bin/anbox session-manager
[Install]
WantedBy=default.target
anbox-container-manager.service is active and running
But I'm still getting:
anbox-session-manager.service failed to start
This is the Unit File, it wants to use /usr/bin/anbox but the package came with no configuration or symlink..
[Unit]
Description=Anbox Session Manager
Documentation=man:anbox(1)
[Service]
ExecStart=/usr/bin/anbox session-manager
[Install]
WantedBy=default.target
Re: [SOLVED] Anbox won't launch on Bullseye
Hi!
I have a question:
you were able to install Anbox by doing apt-get instal anbox?
I tried it and it does not work
Thanks
I have a question:
you were able to install Anbox by doing apt-get instal anbox?
I tried it and it does not work
Thanks
Re: [SOLVED] Anbox won't launch on Bullseye
I too tried to install with those directions. I got the same results. Then I tried systemctl --user restart anbox-session-manager.service and then got a window which did not fit the display screen and was much bigger off the edge. Further there was no menu bar or any way to maximize the screen.
I see that this states that the problem is Solved, but the text of the OP's issue does not show any solution at all and in fact ends with problems. In fact, the bug report at https://bugs.debian.org/cgi-bin/bugrepo ... bug=943654 does not show a solution either.
I see that this states that the problem is Solved, but the text of the OP's issue does not show any solution at all and in fact ends with problems. In fact, the bug report at https://bugs.debian.org/cgi-bin/bugrepo ... bug=943654 does not show a solution either.
Re: [SOLVED] Anbox won't launch on Bullseye
So here might be a solution for the next guy. I am using I am using Debian 11 with Xfce 4.16 on an AMD Ryzen 3 2200G with Radeon Vega Graphics. Here are the basic steps to complete to get it working:
sudo apt install anbox
ls -1 /dev/{ashmem,binder}
If there is nothing there, then:
sudo modprobe ashmem_linux
sudo modprobe binder_linux
Go to https://build.anbox.io/android-images/ and download the image file.
Then install it with the following command if you downloaded it to your local Downloads directory:
sudo mv ~/Downloads/android_amd64.img /var/lib/anbox/android.img
Once done, I ran these commands as a double-check as requested in the bug report, and I show the responses:
ls /var/lib/anbox/android.img
/var/lib/anbox/android.img
systemctl status anbox-container-manager.service
● anbox-container-manager.service - Anbox Container Manager
Loaded: loaded (/lib/systemd/system/anbox-container-manager.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2022-03-16 12:26:34 EDT; 2h 29min ago
Docs: man:anbox(1)
Process: 1078 ExecStartPre=/sbin/modprobe ashmem_linux (code=exited, status=0/SUCCESS)
Process: 1093 ExecStartPre=/sbin/modprobe binder_linux (code=exited, status=0/SUCCESS)
Process: 1139 ExecStartPre=/usr/share/anbox/anbox-bridge.sh start (code=exited, status=0/SUCCESS)
Main PID: 1338 (anbox)
Tasks: 0 (limit: 16632)
Memory: 12.7M
CPU: 53ms
CGroup: /system.slice/anbox-container-manager.service <http://system.slice/anbox-container-manager.service>
‣ 1338 /usr/bin/anbox container-manager --daemon --privileged --data-path=/var/lib/anbox
Mar 16 12:26:33 User systemd[1]: Starting Anbox Container Manager...
Mar 16 12:26:34 User systemd[1]: Started Anbox Container Manager.
systemctl --user status anbox-session-manager.service
● anbox-session-manager.service - Anbox Session Manager
Loaded: loaded (/usr/lib/systemd/user/anbox-session-manager.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2022-03-16 14:51:42 EDT; 5min ago
Docs: man:anbox(1)
Main PID: 12597 (anbox)
Tasks: 61 (limit: 16632)
Memory: 167.8M
CPU: 5.933s
CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/anbox-session-manager.service <http://user.slice/user-1000.slice/user@ ... er.service>
└─12597 /usr/bin/anbox session-manager
Mar 16 14:51:42 User systemd[1571]: Started Anbox Session Manager.
I double-checked the readme file and found that just by running the commands:
sudo systemctl start anbox-container-manager.service
systemctl --user start anbox-session-manager.service
sudo systemctl restart anbox-container-manager.service
I was able to get the program to open and display in a decent manner.
So there you have it. I would only called tentatively solved, because it worked for me. And that does not guarantee I can do anything with it We will see.
sudo apt install anbox
ls -1 /dev/{ashmem,binder}
If there is nothing there, then:
sudo modprobe ashmem_linux
sudo modprobe binder_linux
Go to https://build.anbox.io/android-images/ and download the image file.
Then install it with the following command if you downloaded it to your local Downloads directory:
sudo mv ~/Downloads/android_amd64.img /var/lib/anbox/android.img
Once done, I ran these commands as a double-check as requested in the bug report, and I show the responses:
ls /var/lib/anbox/android.img
/var/lib/anbox/android.img
systemctl status anbox-container-manager.service
● anbox-container-manager.service - Anbox Container Manager
Loaded: loaded (/lib/systemd/system/anbox-container-manager.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2022-03-16 12:26:34 EDT; 2h 29min ago
Docs: man:anbox(1)
Process: 1078 ExecStartPre=/sbin/modprobe ashmem_linux (code=exited, status=0/SUCCESS)
Process: 1093 ExecStartPre=/sbin/modprobe binder_linux (code=exited, status=0/SUCCESS)
Process: 1139 ExecStartPre=/usr/share/anbox/anbox-bridge.sh start (code=exited, status=0/SUCCESS)
Main PID: 1338 (anbox)
Tasks: 0 (limit: 16632)
Memory: 12.7M
CPU: 53ms
CGroup: /system.slice/anbox-container-manager.service <http://system.slice/anbox-container-manager.service>
‣ 1338 /usr/bin/anbox container-manager --daemon --privileged --data-path=/var/lib/anbox
Mar 16 12:26:33 User systemd[1]: Starting Anbox Container Manager...
Mar 16 12:26:34 User systemd[1]: Started Anbox Container Manager.
systemctl --user status anbox-session-manager.service
● anbox-session-manager.service - Anbox Session Manager
Loaded: loaded (/usr/lib/systemd/user/anbox-session-manager.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2022-03-16 14:51:42 EDT; 5min ago
Docs: man:anbox(1)
Main PID: 12597 (anbox)
Tasks: 61 (limit: 16632)
Memory: 167.8M
CPU: 5.933s
CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/anbox-session-manager.service <http://user.slice/user-1000.slice/user@ ... er.service>
└─12597 /usr/bin/anbox session-manager
Mar 16 14:51:42 User systemd[1571]: Started Anbox Session Manager.
I double-checked the readme file and found that just by running the commands:
sudo systemctl start anbox-container-manager.service
systemctl --user start anbox-session-manager.service
sudo systemctl restart anbox-container-manager.service
I was able to get the program to open and display in a decent manner.
So there you have it. I would only called tentatively solved, because it worked for me. And that does not guarantee I can do anything with it We will see.