New Post: Anbox on the Librem 5

You’re expected to download a deb package from there (https://source.puri.sm/Librem5/debs/anbox/-/jobs/364593/artifacts/file/debian/output/anbox_0.0~git20210625-1pureos0+librem5ci70654.0afc1e8_arm64.deb). The repository’s README comes from upstream project and isn’t relevant to this package (you’re not expected to follow it and you’ll miss some important patches if you do).

1 Like

well that’s good …I could not find the link to the deb before… the container-manager can run and I have a icon which will give me a while screen for a while before exiting… so when I ran it from a shell to get more data it said [daemon.cpp:61@Run] [org.freedesktop.DBus.Error.ServiceUnknown] The name org.anbox was not provided by any .service files … so then since I see the container manager service is running I tried this…

$ /usr/local/bin/anbox session-manager
[ 2022-03-03 07:56:32] [Renderer.cpp:104@initialize] Failed to initialize EGL
[ 2022-03-03 07:56:34] [client.cpp:
48@start] Failed to start container: Failed to start container: Failed to create node for device /dev/tun: Operation not permitted
[ 2022-03-03 07:56:34] [session_manager.cpp:164@operator()] Lost connection to container manager, terminating.
[ 2022-03-03 07:56:34] [daemon.cpp:61@Run] Container is not running
[ 2022-03-03 07:56:34] [session_manager.cpp:164@operator()] Lost connection to container manager, terminating.
Stack trace (most recent call last) in thread 2854:
but I can see I have no anbox-session-manager.service… only the anbox-container-manager.service…

copying and enabling the service of course still gave No runtime directory specified I saw it mentioned adding a variable would set that… so I tried…

Environment=“XDG_RUNTIME_DIR=/run/user/$(id -u)”
Environment=“DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/$(id -u)/bus”
ExecStart=/usr/bin/anbox session-manager

which just changed the error from No runtime directory specified to Failed to initialize SDL: x11 not available

any idea what could be missing to allow the anbox-session-manager.service to work?

If I have not forgot something, that all services and stuff has been in place and after unpacking image in /usr/share/anbox I have to start the service (in the fact LXC setup)
sudo systemctl start anbox-container-manager
and then run graphics icon for Anbox and after longer time when ART recompiles Dalvik packages and libraries into AArch64 native code I have Android home screen running with icons for applications. Calculator and even F-droid has been working. If you do not succeed I can try to debug more my setup and we can compare the logs.

But Librem 5 is on hold for me now, we are switching course to our RISC-V simulator and that is heavy work. We have over gigabyte of data to process from our ESA project. As for the GNSS, the Eltvor board (on which production my company cooperated) for ESA with space grade FPGA which can be base for future GNSS satellites signal generation has been bring up by Marek Peca. As for Librem 5 GNSS, my colleague does not dare to replace 201 components (he has experience with 403 soldering and considers risk to damage board when 201 are used too high) so I am in negotiation with company producing ESA and other our professional stuff to do the correction and I pay for it from company budget. It is great that Purism provided components placements thanks to @dcz help but even that Marek is a person who is able to start any Gallileo satellite signal generation even on his home equipment (if I do not count his option to use real satellite test-bed at ESA) we still do not know what was Purism intention with antenna and no response for another questions about warranty etc. has arrived… So I pay for repair according some changes which have not been not described etc. and about which person working on future of Galileo has doubts that are correct.

And no response to warranty questions either. I understand that it is problematic… but silence is worst of possible replies.

Sorry but I am still lost… how does the anbox-session-manager.service get started?
my container starts but
all I can get from session manager is either No runtime directory specified or Failed to initialize SDL: x11 not available (if I add the previous environment variables I mentioned)

Why do you try to run anbox-session-manager? The only service that needs to run is anbox-container-manager, then the Anbox launcher icon (which runs anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity) should work, provided that everything is configured properly (which it should be if you installed the deb package and put the image into correct place).

1 Like

all I get is a white screen for a while if I try the gui icon (provided the container is running) I tried both a image from 2017 I found, and also one I built myself and they only showed white… and then exited so I figured the anbox-session-manager was likely to be what was missing

White? Are you sure you’re using the packaged version, and not some leftovers from when you tried to make install it?

strange… I did the make uninstall…and then installed the .deb file and it showed a white screen for a minute or two before exiting … I did it again and found some things left over… now when it launched it after a install from the .deb … it had a doid logo on a white screen saying it was starting up… then it exited (so almost the same… Adroid logo withStarting … but on a white screen)

wait I stopped the service again and restarted it… now it works

1 Like

Exactly. I have apps that control other hardware that I need to work on my L5 in order to stop carrying around a cheap android I still have just to adjust settings on my electric unicycle and use a bluetooth satellite messenger in wilderness areas.

1 Like