265
Lepton from Valve to run Android games on Linux is now open source (www.gamingonlinux.com)
submitted 1 day ago by to c/linux@lemmy.world
33 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 1 day ago (7 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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 2 points 1 day ago (6 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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 1 point 1 day ago* (last edited 1 day ago) (5 children)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 1 point 6 hours ago (2 children)

    Of course there are, mostly for Chromebooks.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 6 hours ago (1 child)

    I didn't think Chromebooks ran Android apps? It's just a browser-based OS?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 5 hours ago* (last edited 5 hours ago)

    They do, but that's not even the primary reason for x86 Android apps. Android developers on e.g. Windows will test their apps during development, so the app will normally get compiled for x86 to use on an emulator on their PC. The ARM version is only required for the final published release, or testing on a real ARM device. But since x86 is the "default" in the development process, there is little reason not to send both to Google Play, since you are making x86 builds anyway for your own use during development.

    Nowadays this process is mostly transparent for developers, they just write an app and Google Play handles splitting it by architecture, so most apps have an x86 version even if the developer didn't do anything.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 1 day 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.

  • permalink
  • fedilink
  • source
  • parent