Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
from what i can tell, waydroid has some translation layers libndk or libhoudini. however majority of android apps require some kind of java runtime. native apps you (the ndk build system) generally create a release for arm + x86 and its up to the release pipeline to build for each platform. i don't use waydroid much outside of playing around with it for a few minutes when i get bored. however I'm curious if a lot of the issues people have with waydroid is because of taking an arm version of the apk from their phone and not grabbing a x86 one?
Is there an x86 build of every app?
no but the dev controls it. if the dev is using the ndk and the dev is not doing the extra step of disabling/configuring it there should be in "fat" apk with each binary for each platform according to the docs. then the installer can figure out which version to use.
the x86(/_64) version is used for Chromebooks i believe. some devs will split the apk if they configured it to reduce size so you would need to specifically go get an x86 apk version.
the cases where a dev would disable it is if they only want to support specific instructions that might be platform specific or say a library they use doesn't support target ABIs