Wednesday, June 26, 2013

Another Progress report for up coming 1.0.12

Here is some more changes to the up coming release

Added support to Xperia devices given the ability to install the dependencies
Added SemcGenericUxpRes pull support
Fixed the issue with changes not happening when compiling the scripts using the wrong resources.arsc
Fixed broken zipalign scripts
Added the options to allow you to choose  to use the original AndroidManifest.xml when not using the keep folder options when compiling apk files.
Added the options to allow you to choose  to use the original AndroidManifest.xml when not using the keep folder options when compiling system apk files.
Added the ability to open the project after decompiling the apk files
Added support for Jar files
NEW Splash Screen
Rewritten the system pull scripts to make dynamic installation of the dependencies more robust.
Added support for pulling the needed files to install the dependencies for the Xnote.
Added Support for pulling the needed files to install the dependencies for all mediatek chipset Devices.
Added Support for pulling the system/framework/framework-miui.apk file to install for All MIUI ROMs that may require it.
Minor changes to the UI in the setup.bat to make room for  more in the future releases.

To see the complete list of changes you can see the change log over on github at APK-Multi-Tool Experimental-RELEASE CHANGELOG You can also check out the active Support Thread over at XDA Developer [Windows][UTILITY][TOOL] APK Multi-Tool there is download links in this XDA Thread for stable test and the experimental builds so you can test out the changes done so far the always check the github page you can think of them as Nightly Builds like roms.  

2 comments:

  1. Firstly, the tool is pretty cool.

    My question is that I am de-compiling Candy Crush and compiling it and then signing the new APK. file.
    I can install the new APK file, it starts but then crashes, do you know why this would be?

    I am missing a step here?

    Regards
    Paul.

    ReplyDelete
  2. There seems to be a problem with batch optimizing, using the latest 1.0.11. No matter how many apk's I have in the batch optimize folder, I choose option 17, then (for me) "zp", it will optimize only the first apk, then completely exit APK Tool. I have to restart it, choose option 17, and zp again, and it will do, again, only the first one, then quit. Makes batch optimize kind of a waste. I would like to do all 172 apks I have at once, but I have to restart APK Tool EACH time its time for another apk.

    ReplyDelete