Doubts:
- Is it better/faster/more compatible than anbox?
- Runs on ARM?
- Does it allows me to watch DRM streaming services on my linux box?
- Can I install google play on it?
- Is it better/faster/more compatible than anbox?
- Runs on ARM?
- Does it allows me to watch DRM streaming services on my linux box?
- Can I install google play on it?
Should be able to still run them if you use binfmt_misc. Of course it will be slower but it's possible.
https://en.wikipedia.org/wiki/Binfmt_misc
> binfmt_misc can also be combined with QEMU to execute programs for other processor architectures as if they were native binaries.[9]
QEMU supported [ARM guest] machines: https://wiki.qemu.org/Documentation/Platforms/ARM#Supported_...
Edit: from "Running and Building ARM Docker Containers on x86" (which also describes how to get CUDA working) https://www.stereolabs.com/docs/docker/building-arm-containe... :
sudo apt-get install qemu binfmt-support qemu-user-static # Install the qemu packages
docker run --rm --privileged multiarch/qemu-user-static --reset -p yes # Execute the registering scripts
docker run --rm -t arm64v8/ubuntu uname -m # Test the emulation environment
> multiarch/qemu-user-static is to enable an execution of different multi-architecture containers by QEMU [1] and binfmt_misc [2]. Here are examples with Docker [3].
It's not a certified device, so.
There are a number of ways to build "multi-arch docker images" e.g. for both x86 and ARM: OCI, docker build, podman build, buildx, buildah.
Containers are testable.
Here's this re: whether the official OpenWRT container should run /sbin/init in order to run procd, ubusd,: https://github.com/docker-library/official-images/pull/7975#...
AFAIU, from a termux issue thread re: repackaging everything individually, latest Android requires binaries to be installed from APKs to get the SELinux context label necessary to run?
I think Intel has (or had?) a tool/library for translating ARM to x86 called Houdini. Can't seem to find it though, and it might require a license anyways.
What would have helped a lot more here is the default emulator in Android Studio is currently, and has been for a while now, x86. Since of course x86 to x86 virtualization is a lot faster than ARM to x86 virtualization.
ARM64 didn't do much to help with architecture-neutrality just like X86_64 didn't.
From the Anbox website:
> "We're reusing what Android implemented within the QEMU-based emulator for OpenGL ES accelerated rendering."
I'm not certain but I believe WayDroid more directly attempts to provide Android drawing subsystems on top of Wayland. This should be better/faster. Cross fingers.
Compatibility wise, I'm unsure. Anbox may be a more faithful Android platform perhaps. Waydroid feels like it's a closer integration to me, with less virtualized-machinery, which is a much wider support target since it's running directly atop a wide variety of hosts. But I for one am very glad we have a closer integrated option, one where Android apps are running more within the Linux desktop context.
There's probably a bunch wrong with my understandings here. Hoping some even better informed people can correct/supplement.
It's a container so the arch matches the host kernel.
In general on LineageOS it's possible to install gapps.
You won't be able to watch DRM streaming services that require Widevine higher than L3 support.
Netflix and prime and Pluto do, at least. That's all I use, so I am curious. I don't stream anything else, no Roku or Android-tv or whatever.
Admittedly, it's a bit cumbersome to do this, but it works very well. I've been watching Netflix on my Raspberry Pi 4 for over a year using it.
Also, according to this guy [0] you now seem to be able to just install libwidevine in Raspberry OS. I haven't tested this yet though.
[0]: https://lemariva.com/blog/2021/04/raspberry-pi-amazon-prime-...
It doesn't include a HSM, so if it does allow you to watch DRM content, it'll only be Widevine level 3 content, which most services restrict to 420p or sometimes 720p streaming.