this post was submitted on 17 Sep 2026
273 points (99.6% liked)

Linux

19659 readers
22 users here now

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:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] artyom@piefed.social 13 points 1 month ago (1 children)

Lepton = Android --> Linux

FEX = x86 --> ARM

[–] warmaster@lemmy.world 2 points 1 month ago (2 children)

So, there's no ARM -> X86 translation layer baked in?

[–] artyom@piefed.social 4 points 1 month ago (1 children)

I mean this is a fork of Waydroid, which runs Android apps directly on x86, so I don't think it should be necessary.

[–] Ghoelian@piefed.social 2 points 1 month ago (1 children)

I think waydroid only supports running apks compiled for x86, there is no translation layer. So if the app you wany to run only has arm builds, which is likely, it won't work with waydroid.

[–] artyom@piefed.social 1 points 1 month ago* (last edited 1 month ago) (2 children)

Huh? No APKs are compiled for x86. Why would they be? Have you ever used Waydroid?

[–] Linearity@piefed.zip 3 points 1 month ago* (last edited 1 month ago)

You’re both wrong 😑
There are some APKs compiled for x86.
Waydroid supports 2 different ARM to x86 emulation layers.

[–] kewjo@lemmy.world 2 points 1 month ago

not building x86 is up to the developer, the default according to the native sdk

The default behavior of the build system is to include the binaries for each ABI in a single APK, also known as a fat APK. A fat APK is significantly larger than one containing only the binaries for a single ABI; the tradeoff is gaining wider compatibility, but at the expense of a larger APK. It is strongly recommended that you take advantage of either App Bundles or APK Splits to reduce the size of your APKs while still maintaining maximum device compatibility.

At installation time, the package manager unpacks only the most appropriate machine code for the target device. For details, see Automatic extraction of native code at install time.

so if you use the apk from your phone it may or may not contain an x86 compatible binary.

[–] kewjo@lemmy.world 1 points 1 month ago (1 children)

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?

[–] warmaster@lemmy.world 1 points 1 month ago (1 children)

Is there an x86 build of every app?

[–] kewjo@lemmy.world 1 points 1 month ago

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