3 ms·

So how does the x86/ARM difference work with regard to apps? I know most Android apps are written in not-Java-no-really so presumably they're just compiled at r

So how does the x86/ARM difference work with regard to apps? I know most Android apps are written in not-Java-no-really so presumably they're just compiled at runtime, but isn't it possible to write Android apps using native code? How does the Android developer toolchain handle the different architectures?

njs12345 14y ago
Apart from games, there's no problem really. As for native code, you can compile a fat binary similiarly to as described here (if you're using the NDK): http://stackoverflow.com/questions/5089783/producing-optimised-ndk-code-for-multiple-architectures http://stackoverflow.com/questions/5089783/producing-optimis...
freehunter 14y ago
AnandTech's article mentioned that there was no problem running a wide variety of games, including GTA III. I don't know if GTA is the most intensive game that's been released, but I know it was (at least initially) only released for a handful of phones. Xolo could run it.
ConstantineXVI 14y ago
It sounds like if you (the developer) don't rebuild the native bits for x86, Intel rams your binary through some sort of ARM->x86 translator when you upload your app to Play. Appears the translator works fairly well, given that GTA3 was mentioned to work without issue (as the app hasn't been updated since January, I'm operating with the assumption that it wasn't built with x86 binaries)