[WDX/WLX] APK-wdx - Android application packages

[milo1012]

2PolyWon
Yes, I'm already planning to make the mapping of
SDK Numbers <-> Android version string
configurable via ini file entries.
I can't say when I'll have time to work on it, though.

[DrShark]

Is it possible to add "Architecture" field which could show all instruction sets supported by application (like ARMv6, ARMv7, ARM64, X86, X86-64,
MIPS etc. or Universal)?

[milo1012]

Is it possible to add "Architecture" field which could show all instruction sets supported by application (like ARMv6, ARMv7, ARM64, X86, X86-64,
MIPS etc. or Universal)?

(sorry for the late reply)
You mean if (and only if) there is native code in the apk?
Sure: from my understanding you can identify it by checking the
/lib/<<architecture>>/*.so
paths in the archive. I could add some code for that.
I don't think there is something like an "universal" assumption, since the supported native code depends on the Android version (Android dropped support for some architectures AFAIK). The only assumption you could probably make is that an app w/o the mentioned paths has Java-only bytecode and therefore should run on any architecture.

[DrShark]

from my understanding you can identify it by checking the
/lib/<<architecture>>/*.so
paths in the archive. [...] The only assumption you could probably make is that an app w/o the mentioned paths has Java-only bytecode and therefore should run on any architecture.

I also think it's more or less good way to detect architectures support. But TC, which can use native libraries on all architectures, can also be installed (as apk version) and run e.g. in Android VM on BlackBerry devices with QNX, where AFAIK native code is not supported... Maybe Christian Ghisler can clarify how TC is donig this, and whether it's possible to detect it by analyzing app's apk.