5 ms·
what about the other way around? i'm aware about waydroid but it has too many problems with nvidia. also require wayland.
by tuananh 7mo ago
what about the other way around?
i'm aware about waydroid but it has too many problems with nvidia. also require wayland.
- unicornporn 7mo agoX86 builds of Android are stuck at many generations back of the OS. Running Android in a VM on X86 is basically dead AFAIK. :(
- yjftsjthsd-h 7mo agoI'm actually optimistic that this will improve. Google has apparently been working on replacing Chrome OS with android, which I have pretty strong opinions on but the upside is that if they want to go that route they're going to have to make Android officially work well on x86, at which point there's no reason that eg. LineageOS wouldn't be expected to follow suit.
- RobotToaster 7mo agoYou could run a windows VM and run windows subsystem for android.
- jansommer 7mo agoWindows subsystem for Android is deprecated. There's a community maintained alternative but it seems to have a few problems wrt. Windows updates.
- RobotToaster 7mo agoThe community maintained version seems to work okay most of the time, but you're correct a better solution is needed.
- Tajnymag 7mo agoThere's for example redroid (https://github.com/remote-android/redroid-doc https://github.com/remote-android/redroid-doc) which seems to be exactly that. Android inside a container.
- yjftsjthsd-h 7mo agoI can't help you with nvidia, but the Wayland thing can be worked around quite easily by running it under a nested compositor like cage. (This is how I run waydroid under Xorg)
- tuananh 7mo agothanks. good to hear that. i just have to wait for nvidia support now.
- yjftsjthsd-h 7mo agoHave you tried https://wiki.archlinux.org/title/Waydroid#Software_rendering https://wiki.archlinux.org/title/Waydroid#Software_rendering ? Obviously not ideal, but possibly functional.