Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)DR
Posts
0
Comments
465
Joined
2 yr. ago

  • I don't think there is any doubt that avis is artem lol his profile even says banned in it as a joke. as long as his behavior is better, which it has been even if only marginal, there won't be an issue. even if he does nearly single handedly cause most of the 5+ page... debates

  • There is some, but unless it gets really uncivilized no action really gets taken. a couple users have been banned

    IMO I prefer it that way myself though. you either learn something neat, or engage in a class shittery. lots of other more polite forums such as this if phoronix forums isn't to taste

  • Virtualization is a specialization of emulation. to emulate something merely means to imitate. virtualization is still emulating a secondary PC environment. Saying virtualisation is not emulation is just fudging terms because people don't like the implication that the term "emulation" has. I recommend reading WINE's FAQ where even they admit that it would be more accurate to say "wine is not just an emulator". Virtualization is just a subclass of emulation.

    most virtualisation software use API forwarding for 3D acceleration APIs

    this is a common misconception Most VMMs emulate GPU. virtualbox, vmware, wsa, and qemu all emulate GPU (or rather, technically a gallium driver) for opengl support on linux and even windows. as windows guests under virtualbox actually uses gallium nine/dxvk under the hood (perf is still crap somehow though). the technical breakdown for qemu would be [ host gpu <--> gallium <--> opengl <--> qemu pipe <--> virgl <--> gallium calls <--> opengl <--> application ]

    vmware/vbox are slightly different as it's an accelerated backend to vmgfx but that too emulates a gallium backend on linux meaning it's doing ogl -> gallium -> ogl etc.... Hyper-v/wsa is the exact same situation as both. I don't believe that bluestacks and memuplay deviates from this greatly. though it's not something I have looked in depth into.

    it wasn't until recently with virglrenderer venus for qemu/crosvm and hyper-v gpu-pv that we have gotten real API forwarding for VMs (technically android's cuttlefish also had it IIRC, but preformance was terrible when I played with it, hyper-v also had something but it was really bad too).

    as for other forms of api forwarding, qemu-3dfx is a prime example of real "api forwarding" to an extent, rather it forwards 3dfx and opengl calls to the host. and you can have d3d support via wined3d.

  • 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 shit on waydroid project.

  • The only hard requirement is wayland, Thats not a hard sell, works perfectly fine on xfce when using a nested wayland compositor.

    Waydroid also has matrix and discord available.

    If you weren't willing to at least put a modicum of effort into reporting your issues properly, don't complain about open source software, go use Windows.

    You're getting a free product, for free what a surprise. you can complain all you want, but in this case yes, it is your fault. If you're not willing to try and help yourself a little bit, then yes it's your fault.

    we can't fix magical problems we can't replicate. I know that might be a little hard to believe, but it is true.

    The fact of the matter is on The more popular distros, waydroid is more or less an out-of-box experience now. If you're not willing to help your specific use case get fixed, then it won't get fixed.

    stop complaining.

  • nearly every single emulator, for Windows is a VM pretty much. Blue stacks, memuplay, WSA, Google Play games.

    no, there is no difference between virtualization and emulation. virtualizations just hardware accelerated emulation. That's it. If you use blue stacks and call it emulation, because it's emulation, all the sudden it's not emulation because it's virtualization?

    If that is the bar, then there are incredibly few Android emulators. Yes some Android emulators, or rather virtualizers, do implement some custom GPU acceleration stuff. but not all, Google Play games uses CrossVM with vulkan cereal, WSA uses their weird stack. genymotion IIRC uses virgl, so does qemu.

    EDIT: by the way, with VirtualBox VMware so and so forth, you are still emulating. you are emulating NICs, oftentimes you are emulating GPU, you are emulating storage controllers, you are emulating PCI controllers, so on and so forth.

  • Yes. Many. Blisslabs has partnerd with EIDU to work on tablets for low income countries. I personally have sold android boxes with Bliss. Ax86 has a large number of sponsors that are/were casinos. There are people working on using it in cars. 2-In-1s. ETC.

    VMs are the minority use case...

  • whatever hardware acceleration you have or it will run like dogshit.

    and? vbox, qemu, hyperv and vmware, all have gpu acceleration to a degree. Qemu will also be getting vulkan acceleration soon

    EDIT: forgot crosvm (google play games) which does too

  • again, it will work on pretty much any wayland environment, if you need it to work on x11, it can work there too, just use a nested compositor like cage. I have personally verified that you can use waydroid via cage on top of xfce.