Running with multiarch/qemu-user-static

[Megver83]

First thing to say: I've got ashmem and binder working and the amd64 docker image works as expected.

Now, I'm trying to run the arm64 image with qemu. My host OS is Parabola (Arch-based) and tried to run the arm64 image by using multiarch/qemu-user-static. It partially works, I can start the container, adb shell into it, but when trying to start scrcpy or install an apk, I get:

Binder driver '/dev/binder' could not be opened.  Terminating.

I noticed that /dev/binder is a symlink to /dev/binderfs/binder. However, /dev/binderfs/binder does not exist in the arm64 container.

What am I missing? or should I ask, what's the best way to run the arm64 container in x86_64?

[Megver83]

Maybe this is related? But happening to Redroid in this case.

(...)
Waydroid depends on the binder and ashmem drivers from your host kernel, they might not be cross-architecture compatible
(...)

[zhouziyang]

try to get Native Bridge support for x86_64 redroid images. And you can run arm APPs after that.
you can create arm64 VMs on public cloud (AWS / Azure / Oracle / Aliyun etc.), then run arm64 redroid images there.

BTW, it's possible to create native bridge based on QEMU.

[Megver83]

BTW, it's possible to create native bridge based on QEMU.

That sounds much more attractive to me. I'd like to avoid proprietary implementations like houdini and libndk. How do I proceed?

[zhouziyang]

not particular sure about he implementation details.
maybe look at this: https://android.googlesource.com/platform/frameworks/libs/native_bridge_support/+/refs/heads/master

[Megver83]

Just for the record, regarding QEMU as a Houdini alternative:
https://groups.google.com/g/android-x86/c/GZ3tQ0mUIdU
https://github.com/goffioul/ax86-nb-qemu

But looks like it's an unfinished work... will continue investigating

[zhouziyang]

how about use arm servers directly? bunch of providers :)

[zhouziyang]

stale