Dealing with Asset Compression in Android Apps(避免asset目录下文件被压缩)

转载 2012年03月22日 22:53:54
When developing an Android app, any data file, image or XML file (that is, any Resource or Asset) you use is bundled into your application package (APK) for distribution. The Android Asset Packaging Tool, or aapt, is responsible for creating this bundle, which you can think of as a ZIP file with a particular layout that the Android OS can understand. When your application is installed, whether in development mode or by an end user, this APK file is simply dropped into a special location on the device’s (or emulator’s) filesystem.

As part of preparing your APK, aapt selectively compresses various assets to save space on the device. The way aapt determines which assets need compression is by their file extension. The following code, taken from Package.cpp in the aapt source code, sheds some light on which types of files are not compressed by default:

/* these formats are already compressed, or don't compress well */
static const char* kNoCompressExt[] = {
    ".jpg", ".jpeg", ".png", ".gif",
    ".wav", ".mp2", ".mp3", ".ogg", ".aac",
    ".mpg", ".mpeg", ".mid", ".midi", ".smf", ".jet",
    ".rtttl", ".imy", ".xmf", ".mp4", ".m4a",
    ".m4v", ".3gp", ".3gpp", ".3g2", ".3gpp2",
    ".amr", ".awb", ".wma", ".wmv"
};

The only way (that I’ve discovered, as of this writing) to control this behavior is by using the -0 (zero) flag to aapt on the command line. This flag, passed without any accompanying argument, will tell aapt to disable compression for all types of assets. Typically you will not want to use this exact option, because for most assets, compression is a desirable thing. Sometimes, however, you will have a specific type of asset (say, a database), that you do not want to apply compression to. In this case, you have two options.

First, you can give your asset file an extension in the list above. While this does not necessarily make sense, it can be an easy workaround if you don’t want to deal with aapt on the command line. The other option is to pass a specific extension to the -0 flag, such as -0 db, to disable compression for assets with that extension. You can pass the -0 flag multiple times, and each time with a separate extension, if you need more than one type to be uncompressed.

Currently, there is no way to pass these extra flags to aapt when using the ADT within Eclipse, so if you don’t want to sacrifice the ease of use of the GUI tools, you will have to go with the first option, and rename your file’s extension.
So, Why Disable Compression Anyway?

For most types of assets, you shouldn’t need to be concerned with how they are packaged. Given the list of extensions above, Android will do the right thing for a large subset of the files you’ll use. If you have a type of asset that is already compressed by nature of the file type, but doesn’t have one of the sanctioned extensions, you can typically ignore that inconsistency and just allow aapt to try to compress it. It will not be very much, if at all, smaller in the final APK, but the performance hit should be relatively minimal unless you just have tons of these files.

This begs the question, why even bother disabling compression? The not-so-obvious answer is that any compressed asset file with an uncompressed size of over 1 MB cannot be read from the APK. This could come into play if your asset needed to be copied out of the APK and into the app’s writable files area, for example to provide a pre-populated database in your app. When you try to use the various AssetManager or Resources classes’ methods to get an InputStream to the file, it will throw an exception and display a LogCat message like this:

DEBUG/asset(725): Data exceeds UNCOMPRESS_DATA_MAX (1662976 vs 1048576)

The only way around this type of issue is to disable compression for assets that exceed the 1 MB limit. If your file format supports it, you can choose to split the asset into several smaller files that have an uncompressed size of less than 1 MB each, but this can be a real annoyance.

Hopefully the knowledge in this post can help you avoid the headaches I went through to learn it!

相关文章推荐

Android复制asset目录的文件到SD卡下

我们在做android开发的时候,有时候会需要把asset目录的文件复制到SD卡里,然后直接从SD卡里面读取文件,资源文件放到SD卡里面后读取起来就很方便,不像在asset文件夹里面必须通过文件流的方...

Android复制asset目录的文件到SD卡下

package com.mufeng.toolproject.utils; import android.content.Context; import android.content.res.As...

Unity5 使用自带的字体导致BuildAssetbundle失败An asset is marked with HideFlags.DontSave but is included in the

今天打Bundle的时候Unity提示错误An asset is marked with HideFlags.DontSave but is included in the build: Asset:...

Unity 解决 An asset is marked with HideFlags.DontSave but is included in the build 问题。

找来找去发现是由于UILabel 引用了Library/unity editor resources中的字体引发的。 所以我写了个脚本,来check所有uilabel的字体名称 using Uni...

android 读取asset文件方法封装

android项目里面使用到了读取asset文件,所以在这里做了下封装。

android项目读取asset文件夹中的xml文件

1、xml文件放入asset文件夹,结构如: 易钊测试3内容一23 测试二3内容二23 2 、构建message类,解析xml类PullParseSe...

android 解决asset下面文件太大报错问题

Android 中对asset中存放文件 大小有一定限制,如果超过1M会报 Data exceeds UNCOMPRESS_DATA_MAX 这个错误 那么我们怎么解决这个问题呢 首先,我想到的...

Android文件资源(raw/data/asset)的存取

2012-03-12 09:36 Android文件资源(raw/data/asset)的存取 在android开发中,我们离不开资源文件的使用,从drawable到string,再到l...

ANDROID开发-ASSET中文件超过1M的解决方法

转自:http://www.cnblogs.com/thinkfeed/archive/2011/10/27/2226922.html res/raw和assets的相同点:   1...
内容举报
返回顶部
收藏助手
不良信息举报
您举报文章:深度学习:神经网络中的前向传播和反向传播算法推导
举报原因:
原因补充:

(最多只允许输入30个字)