Package Details: anbox-modules-dkms-git 1:r702.3cf7d60-1

Git Clone URL: https://aur.archlinux.org/anbox-git.git (read-only)
Package Base: anbox-git
Description: Required kernel module sources for Android
Upstream URL: http://anbox.io/
Licenses: GPL3
Submitter: irtimmer
Maintainer: irtimmer
Last Packager: irtimmer
Votes: 58
Popularity: 10.413718
First Submitted: 2017-04-12 21:41
Last Updated: 2017-09-01 09:35

Latest Comments

HotblackDesiato commented on 2017-09-16 12:01

I tried to start anbox again today. It seems that the session manager can be started (I don't know why it didn't work yesterday). But now I get another error: "Android hasn't fully booted yet. Waiting a bit ..". Any advice ?

-------------------------
$ systemctl --user start anbox-session-manager.service
$ systemctl --user status anbox-session-manager.service
anbox-session-manager.service - Anbox Session Manager
Loaded: loaded (/usr/lib/systemd/user/anbox-session-manager.service; disabled; vendor preset: enabled)
Active: active (running) since Sat 2017-09-16 19:53:17 +08; 13s ago
Main PID: 2015 (anbox)
CGroup: /user.slice/user-1000.slice/user@1000.service/anbox-session-manager.service
└─2015 /usr/bin/anbox session-manager

Sep 16 19:53:17 stefan systemd[897]: Started Anbox Session Manager.
$ ANBOX_LOG_LEVEL=debug anbox launch --package=org.abox.appmgr --component=org.anbox.appmgr.AppViewActivity --gles-driver=host
[ 2017-09-16 11:56:01] [launch.cpp:220@operator()] Android hasn't fully booted yet. Waiting a bit ..
[ 2017-09-16 12:00:01] [launch.cpp:234@operator()] Stopped waiting as we've already waited for too long. Something
[ 2017-09-16 12:00:01] [launch.cpp:235@operator()] is wrong with your setup or the container has failed to boot.
[ 2017-09-16 12:00:01] [launch.cpp:236@operator()] If you think you found a bug please don't hesitate to file on
[ 2017-09-16 12:00:01] [launch.cpp:237@operator()] at https://github.com/anbox/anbox/issues/new
Attempted to unregister path (path[0] = null path[1] = null) which isn't registered

HotblackDesiato commented on 2017-09-15 11:55

Remark for those of us who use custom kernels: make sure that you include squashfs support in your kernel. Otherwise you would get the following error (systemctl says "OK" during boot, but it isn't):
-----------------
# systemctl status anbox-container-manager.service
anbox-container-manager.service - Anbox Container Manager
Loaded: loaded (/usr/lib/systemd/system/anbox-container-manager.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2017-09-15 19:17:00 +08; 7min ago
Process: 2105 ExecStart=/usr/bin/anbox container-manager --daemon --privileged --data-path=/var/lib/anbox (code=exited, status=1/FAILURE)
Main PID: 2105 (code=exited, status=1/FAILURE)

Sep 15 19:17:00 stefan systemd[1]: Started Anbox Container Manager.
Sep 15 19:17:00 stefan anbox[2105]: Failed to mount Android rootfs
Sep 15 19:17:00 stefan systemd[1]: anbox-container-manager.service: Main process exited, code=exited, status=1/FAILURE
Sep 15 19:17:00 stefan systemd[1]: anbox-container-manager.service: Unit entered failed state.
Sep 15 19:17:00 stefan systemd[1]: anbox-container-manager.service: Failed with result 'exit-code'.
--------------------

My container manager is now running, but I get the following error message from the session-manager:
----------------
$ anbox session-manager
[ 2017-09-15 11:54:41] [session_manager.cpp:162@operator()] Lost connection to container manager, terminating.
[ 2017-09-15 11:54:41] [client.cpp:49@start] Failed to start container: write: Broken pipe
[ 2017-09-15 11:54:41] [session_manager.cpp:162@operator()] Lost connection to container manager, terminating.
[ 2017-09-15 11:54:41] [daemon.cpp:58@Run] write: Broken pipe
-----------------

Any ideas ?

'anbox system-info ' segfaults.

timofonic commented on 2017-09-08 14:22

I can't make it work, it seems because binder doesn't work on my custom kernel (linux-drm-tip-git in AUR that I adopted because it was orphan and needed it) I need because of Intel GPU driver bugs.

Issue here: https://github.com/anbox/anbox/issues/453

Relevant part:

$ sudo modprobe binder_linux
modprobe: ERROR: could not insert 'binder_linux': Unknown symbol in module, or unknown parameter (see dmesg)

The other module works, as you can see in the github issue.

$ dmesg | grep binder
[ 3256.450766] binder_linux: Unknown symbol task_tgid_nr_ns (err 0)
[ 3303.761444] binder_linux: Unknown symbol task_tgid_nr_ns (err 0)

twa022 commented on 2017-09-01 02:28

Could you please add:

sed -i 's:#!.*python$:&2:' scripts/*py at the end of the prepare function.

ailick commented on 2017-08-20 13:36

Hi,good friend,emmmm...something is so terrible,look that:
[ailick@Ailick_Mj ~]$ sudo modprobe binder_linux
[ailick@Ailick_Mj ~]$ sudo modprobe ashmem_linux
[ailick@Ailick_Mj ~]$ sudo systemctl start anbox-container-manager.service
[ailick@Ailick_Mj ~]$ systemctl --user start anbox-session-manager.service
[ailick@Ailick_Mj ~]$ ANBOX_LOG_LEVEL=debug anbox session-manager --gles-driver=host
[EE 2017-08-20 13:18:21] [Renderer.cpp:104@initialize] Failed to initialize EGL
segmentation fault (core dumped)
[ailick@Ailick_Mj ~]$ ANBOX_LOG_LEVEL=debug anbox session-manager
[EE 2017-08-20 13:18:57] [Renderer.cpp:104@initialize] Failed to initialize EGL
segmentation fault (core dumped)
[ailick@Ailick_Mj ~]$ anbox system-info[ailick@Ailick_Mj ~]$ ANBOX_LOG_LEVEL=debug anbox system-info
segmentation fault (core dumped)

I'm useing IntelHD4600 and NvidiaGTX 760M with bumblebee..But look that:

[ailick@Ailick_Mj ~]$ ANBOX_LOG_LEVEL=debug primusrun anbox session-manager --gles-driver=host
[EE 2017-08-20 13:22:39] [Renderer.cpp:104@initialize] Failed to initialize EGL
segmentation fault (core dumped)
[ailick@Ailick_Mj ~]$ ANBOX_LOG_LEVEL=debug primusrun anbox system-info
segmentation fault (core dumped)

So,what shuold I do? Please help me

nobicycle commented on 2017-08-12 04:22

The latest post of sergey.orloff describing how to run anbox worked for me when running video-ati open source drivers but when I switched to video-catalyst I got:
$ ANBOX_LOG_LEVEL=debug anbox session-manager --gles-driver=host
libEGL warning: DRI2: failed to authenticate
[DD 2017-08-12 04:17:16] [Renderer.cpp:165@initialize] Using a surfaceless EGL context
[EE 2017-08-12 04:17:16] [Renderer.cpp:190@initialize] Failed: Missing egl_image related extension(s)
Segmentation fault (core dumped)

sergey.orloff commented on 2017-08-09 12:11

[sergey@p43es3g ~]$ sudo modprobe binder_linux
[sergey@p43es3g ~]$ sudo modprobe ashmem_linux
[sergey@p43es3g ~]$ sudo systemctl start anbox-container-manager.service
[sergey@p43es3g ~]$ anbox session-manager --gles-driver=host &
[sergey@p43es3g ~]$ anbox: error while loading shared libraries: libboost_filesystem.so.1.63.0: cannot open shared object file: No such file or directory
[sergey@p43es3g ~]$ pkgfile libboost_filesystem.so
extra/boost-libs
[sergey@p43es3g ~]$ yaourt -Ss boost-libs
extra/boost-libs 1.64.0-4 [installed]
Free peer-reviewed portable C++ source libraries - runtime libraries
aur/lib32-boost-libs 1.64.0-1 (7) (0,66)
Free peer-reviewed portable C++ source libraries - Runtime (32 bit)

mohan226 commented on 2017-08-07 17:21

When I run it, I get the error "error while loading shared libraries: libboost_filesystem.so.1.63.0". So, I downgraded boost and boost-libs to 1.63. But then I get the error "error while loading shared libraries: libboost_log.so.1.64.0". What should I do? We can't have 2 versions of the same package installed.

marcown commented on 2017-08-05 16:53

@hailbreno:

So how do/did you get anbox running on arch?

Regards,
marcown

hailbreno commented on 2017-08-04 18:45

Looks like the issue related to binder and kernel 4.11 > is now solved.

All comments