1.4.3
2011.12.08
- updated builtin framework to SDK API14
- fixed some "Multiple substitutions (...)" errors ( Issue 254 )
1.4.2
2011.12.02
- added support for API14 (Android 4.0) resources
- updated smali to v1.3.0
- added --quiet option
- fixed decoding error when string ends with '%' ( Issue 169 )
- fixed decoding error when <plurals> contains a reference ( Issue 234 )
- fixed a broken res when decoding <array> with positional substitutions ( Issue 222 )
1.4.1
2011.05.15
- fixed builtin framework. See changelog and migration instructions of v1.4.0 below.
1.4.0
2011.05.15
Major changes:
- added Honeycomb support (3.1, API 12). See migration instructions below.
- support for mipmaps and xlarge, xhdpi resource qualifiers
- updated builtin framework to 3.1 (API 12) broken
- completely rewritten mechanism of enclosing/escaping strings in XML files:
- fixed legendary Issue 100
- fixed a lot of other bugs discovered when writting integration tests
- string format is simpler and more compact now: '" "' instead of '\u0020 ', '\"' instead of '\"', etc.
- fixed incompatibilities between newer aapt and apks built by older one. New aapt is more restrictive, some apps can't be built using it, even if you would have sources. Apktool tries to convert/fix these incompatibilities: it adds formatted="false" for <string /> tags and enumerates substitutions for plurals.
- updated smali to v1.2.6
- added automatic integration tests for resource decoding and building
- first official release of apktool built using Maven from open source
Minor changes
- sort framework ids before storing them in apktool.yml. aapt command requires you to include frameworks in order.
- zero-padding of MCC resource qualifier
- prefer to use raw values when decoding XML attrs. This could make decoded XMLs a little more similar to original ones.
- close apktool.yml file handler after generating it
- added error message about missing input file when decoding
- added more info messages during decoding.
- do not decode res-references as <item />. Now they're decoded as e.g. <string name="test">@android:string/ok</string> instead of <item type="string" name="test">@android:string/ok</item>.
- changed encoding of generated XML files from UTF-8 to utf-8 - it's more consistent with Android SDK.
- add new line at the end of generated XML files.
Migration to 1.4.0
In order to get full Honeycomb/Gingerbread (3.1, API 12) support you have to:
- update apktool to v1.4.0
- update install package to r04-brut1 or update your aapt manually
- then remove $HOME/apktool/framework/1.apk or install your own framework from Honeycomb/Gingerbread
1.3.2
2010.09.03
- contains critical bug: Issue 100 .
- updated smali to v1.2.4
- added support for API Level 8 resource qualifiers: night, car, etc. ( Issue 65 )
- added support for broken file-resources ( Issue 91 )
- don't generate sdkVersion ("-v") resource qualifiers if they're "natural" ( Issue 85 )
- always compress resources.arsc file (Issue 67)
- throw warnings instead of exceptions on unknown files inside smali dir ( Issue 77 )
- added support for resources using invalid/unknown config flags, e.g. from future APIs or added by manufacturer ( Issue 65 )
- added an option to keep broken resources to fix them manually ( Issue 65 )
- fixed case-sensitivity problems (Issue 86)
- fixed an issue when *.9.png doesn't have 9patch chunk in it ( Issue 59 )
- fixed NPE when there is a file without extension in drawable dir ( Issue 62 )
- fixed escaping of chars in XML style tags ( Issue 64 )
- fixed an error, when there are missing resources in a type, which does not have default config (http://forum.xda-developers.com/showthread.php?p=7949440#post7949440)
- try to use original value of XML attribute - instead of parsed one. Fixes an issue when apktool was decoding e.g. "01" as "1" ( Issue 76 )
- added more debugging info when omitting unknown config flags ("Config size > 32" message)
1.3.1
2010.06.14
1.3.0
2010.06.12
- added 9patch images (*.9.png) decoding (Issue 2)
- fixed support for apks lacking res dir or resources.arsc file (Issue 44, Issue 50)
- changed default name of built file from out.apk to <original_name.apk>
- added possibility to choose location of output apk when building
1.2.0
2010.06.03
- added feature for installing and using custom framework files - pulled from a device. See FrameworkFiles (Issue 27)
- Froyo support (Issue 37)
- updated Android framework to 2.2r1
- removed HTC framework
- no need to use -s/-r switch, when apk doesn't contain sources/resources
- added protection against accidental remove of important files when decoding (Issue 36)
- made outdir argument optional when decoding
- fix: adding dummy resources if some of them are missing (Issue 40)
- fix: better recognition of AXML files (Issue 41)
1.1.1
2010.04.29
- much better recognition of register types when debugging (Issue 24)
- fixed SIGSEGV error, which usually occured after several steps when debugging (Issue 26)
1.1.0
2010.04.28
- added smali debugging! For more info, see: SmaliDebugging
- added HTC resources (Issue 17)
- made all framework resources public (Issue 16)
- proper escaping of whitespaces in resource strings (Issue 14)
- updated (bak)smali to 1.2.2
- fixed "Building resources..." freeze bug (Issue 13)
1.0.0
2010.04.02
- it is now pure-Java, so should work on any platform
- added support for decoding and rebuilding framework-res.apk file
- added support for many new resources features and apks
- included automatic workaround for 9-patch images issue
- added possibility to decode sources or resources only
- automatic detecting, whether there is a need for rebuilding files
- added some info messages
- it is less invasive, cause res ids in built file are identical as in original apk
- it is much faster
- fixed a lot of bugs
0.9.2
2010.03.13
- many, many new apps supported. I've tested it on 85 random apps pulled from my device: 0.9.1 gave me 28 failures, 0.9.2 only 2. This does not mean all 83 apps are perfectly fine, but it is quite probably that they are.
- smali, baksmali and android resources are now builtin, so it is much simplier to install apktool. Still you need aapt in a PATH.
- much better error reporting
- added simple usage help
- new "bs" command
0.9.1
2010.03.02
- #1 fixed
- fixed support for many apps