I should mention that I’m trying this on Manjaro ARM. I don’t have snap installed and I think anbox snaps are for x86_64 only.
@Strit, do you think you can build a 5.8.10-2 with CONFIG_SQUASHFS_DECOMP_MULTI=y? Currently, the single threaded squashfs decompressor seems to slow everything down. Thanks
Is it possible to run anbox on RPI4 arm64 using the image from manjaro repo? How do you edit the kernel? After installing anbox through the repo, anbox will load but not open.
You would need to recompile the kernel, enabling some ANDROID, ASHMEM and BINDER stuff in the config. I don’t think those are enabled in our rpi4 kernel. @darksky can confirm for me.
I apologise, I am new to manjaro. I searched on google and found that there was a GUI tool to manjaro system manager. Though I did not see the kernel option in it. Does the KDE for Rpi4 not include those settings in the GUI? Is there another way?
I compiled our linux-rpi-4-mainline kernel 5.8.9-2 with all of the modules that was referred to in above arch anbox wiki and what @nightmare-2021 has here:
I wanted to test it but I have no clue how to go about it. I am not even sure the package in the repo anbox-image-aarch64 is the right image as I believe it is for the pinephone from looking at the image that gets mounted and it’s contents.
It would be extremely helpful if some one gave some steps in this thread for others on how they got it working on the aarch64 other than saying they got it to work.
Kernel I compiled with it’s headers (I am not going to push it to the repo until I know it works):
UPDATED:
Link has been removed. I push all new kernels for the pi4 with kernel version bump and android modules enabled to the unstable branch.
I can confirm that the kernel I compiled and gave a link above for the pi4 does work. My main obstacle was I did not know how to start anbox. I was trying to do it from the command line with out knowing there was pre-configured commands associated with anbox in it’s link in the Menu’s.
In testing I installed a lot of programs and most would crash so I am not very impressed with it so far. Maybe things will get better down the road.
No. That kernel was for the RPi. (It is now in the unstable branch as a side note).
I believe the latest kernel for the pbp in the testing branch has the android modules enabled. It will have the same kernal name you are using but higher version. @Strit can correct me if I am wrong.
@nightmare-2021 Not working on 5.9 Kernel for me. Has it not been implemented yet?
anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity
[ 2020-10-22 17:26:07] [daemon.cpp:61@Run] [org.freedesktop.DBus.Error.ServiceUnknown] The name org.anbox was not provided by any .service files
So I have to recompile the Kernel every time? I don’t really understand what to make of this
CONFIG_ASHMEM=y
# CONFIG_ION is not set
CONFIG_ANDROID=y
CONFIG_ANDROID_BINDER_IPC=y
CONFIG_ANDROID_BINDERFS=y
CONFIG_ANDROID_BINDER_DEVICES="binder,hwbinder,vndbinder"
# CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set
When I looks at the PKGBUILD, I see that config.anbox is already included. So everything should already be set, but it doesn’t work for me. With kernel 5.6 it does