the one thing linux really hasnt been made on par with winblows yet is the dreadful amount of options for android simulation -the most popular choice seems to be Waydroid, but its such an unneeded hassle to set up at all -genymotion is just slow -and than you have things like android x86 which entirely defeat the point of an emulator
how would you know how much effort i put into trying to fix things on linux? how would you know i spend days if not weeks in total trying to make garbage run that should have worked out the box.
yes, you cant fix it, cause you are not willing to make the actual piece of software work, clearly.
waydroid, literally, for a fact, is not an out of the box experience or it wouldnt have silly requirements as gpu, de/wm.
I am long past trying to fix things that shouldnt need fixing in the first place, if it doesnt work in under 30 minutes max, than whatever software it was is defacto broken and doesnt need to be used.
And you actually are right, well with one thing, you are free to tell me to stop complaining, and i am free to continue. neither of us has any power to make the other stop.
But we are clearly going in circle for a while, so as per my own rules on software, ill use them here as well.
I don’t care how much effort you spent, I care about what is reported to waydroid devs. maybe instead of bashing your head against a wall, try reporting the issue. could be a lot more productive, waydroid works on intel and amd gpus, and will automatically fall back to software rendering on nvidia gpus.
there are a couple known issues around multi-gpu that are being worked on, but doesn’t seem to be your issue. wayland works fine, X11+wayland works fine. xfce, lxqt, etc work fine when using a nested compositor. at this point, I can only assume the issues you have are made up in your head to try and removed on waydroid project.