1. It does have to be writen in a vag... wait java... which can do anything... ahh the freedom of java... except manage memory correctly :/ anyways, you can't tell how much free memory a system has in a vaj, but you might be able to chain a few lines of code out, to ease the memory consuption, and trick the a vaj runtime garbage, garbage collector (not a typo :p) into freeing some memory for the next operation.
2. it is not.said it's decompiling for a few minutes, phone temp rised like hell and then the app crashedit starts ok then hangs and eventually crashessometimes it doesn't workIt couldn't decompiled class files :/bla bla hang my deviceoom while decompileAs some have said already, tends to run out of memory on medium sized tasks.
3. I don't need android.*, or other Android or Java libs decompiled, just the app specific classes.does what is says... but seems to run out of memory on a 11mb dex file with v7 and v13 support.
4. cannot browse my device for file and crashes everytime i try to access parent or root folder (aka ”/” or ”../").jadx is the best apk decompiler but this is not a good adaptation of it for android.
5. This likely would improve if there was an option to select classes to be decompiled and/or excluded from compilation.