Android on linux situation

We use different technology merge it together above linux kernel
and call it a distribution,but google took a another approach it’s the android stack


It’s completely different steps were everything works together very well
however my point here how to run android on my arch linux distribution natively

I disgree if you said the waydroid :no_entry:
waydroid is poor cheap piece of unworthy software that fill a place it didn’t belong into
god, I hate waydroid to death

I disagree if you said qemu :no_entry:
qemu is excellent choice ofc but here what happens
I’ve tried android x86_64 last build but it never booted because
it has it’s own kernel build that has been emulated with no nvidia drivers
that never works on my system
another bootable android system is Bliss OS but my cpu doesn’t have avx support
The only option is to build android AOSP
google made it a nightmare even to compile that. and ran it above qemu+kvm

How, how that we have something smart like wine with it’s own prefix and environmental clever works
But not android that actually built above linux kernel, there is no single developer who thought
about build similar project to wine that sandbox android the right way
to run native on a standard linux distribution.

2 Likes

You’re right on the money about running Android natively on a standard Linux distro. Android’s stack is so tightly integrated with its runtime, HAL and kernel patches that it’s hard to decouple for general Linux systems.

Waydroid works for some but I get why you hate it—it’s not perfect, especially for NVIDIA setups. QEMU is solid but has its own limitations, especially with AOSP builds that require specific kernels and often lack desktop GPU support.

A Wine-like solution for Android would be awesome but it’s a huge challenge given Android relies on its own runtime (ART) and HAL to interact with hardware. Anbox tried to do something similar but never got mature enough to be useful.

You can try customizing an Android-x86 kernel for your hardware or looking into lightweight AOSP forks for non-AVX CPUs, but options are limited. If NVIDIA drivers are the issue, you can try kernel patches or alternative GPU configurations.

Unfortunately there’s no magic solution yet but if I find one I’ll post here.

1 Like