<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for Ponystyle Industries</title>
	<atom:link href="http://ponystyle.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://ponystyle.com/blog</link>
	<description>Brian Hardy's Internet façade</description>
	<lastBuildDate>Mon, 12 Dec 2011 15:58:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>Comment on Dealing with Asset Compression in Android Apps by Evitar la compresión de los &#8220;assets&#8221; en Android &#124; Zadia Software · Android · iPhone · iPad · Blackberry · Desarrollo y diseño web</title>
		<link>http://ponystyle.com/blog/2010/03/26/dealing-with-asset-compression-in-android-apps/comment-page-1/#comment-376</link>
		<dc:creator>Evitar la compresión de los &#8220;assets&#8221; en Android &#124; Zadia Software · Android · iPhone · iPad · Blackberry · Desarrollo y diseño web</dc:creator>
		<pubDate>Mon, 12 Dec 2011 15:58:14 +0000</pubDate>
		<guid isPermaLink="false">http://ponystyle.com/blog/?p=34#comment-376</guid>
		<description>[...] &#124; Ponystyle Industries.   Entrada publicada en la categoría Programación, con las etiquetas android, assets, [...]</description>
		<content:encoded><![CDATA[<p>[...] | Ponystyle Industries.   Entrada publicada en la categoría Programación, con las etiquetas android, assets, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dealing with Asset Compression in Android Apps by Shibbs</title>
		<link>http://ponystyle.com/blog/2010/03/26/dealing-with-asset-compression-in-android-apps/comment-page-1/#comment-338</link>
		<dc:creator>Shibbs</dc:creator>
		<pubDate>Tue, 15 Nov 2011 20:11:16 +0000</pubDate>
		<guid isPermaLink="false">http://ponystyle.com/blog/?p=34#comment-338</guid>
		<description>Thanks Brian - We were shipping 6 MB of DB &amp; some device were able to show the contents but some where not. This post really helped us in figuring out what was the real problem. We went with the option-1 that you mentioned &amp; renamed our db as &#039;bible.db.png&#039; &amp; it worked. Just that the apk bloated back from 2.3 to close 6 MB, but I guess we can take that trade off. 
Kudos!</description>
		<content:encoded><![CDATA[<p>Thanks Brian &#8211; We were shipping 6 MB of DB &amp; some device were able to show the contents but some where not. This post really helped us in figuring out what was the real problem. We went with the option-1 that you mentioned &amp; renamed our db as &#8216;bible.db.png&#8217; &amp; it worked. Just that the apk bloated back from 2.3 to close 6 MB, but I guess we can take that trade off.<br />
Kudos!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dealing with Asset Compression in Android Apps by Shipping a Database with your App &#124;</title>
		<link>http://ponystyle.com/blog/2010/03/26/dealing-with-asset-compression-in-android-apps/comment-page-1/#comment-332</link>
		<dc:creator>Shipping a Database with your App &#124;</dc:creator>
		<pubDate>Sun, 23 Oct 2011 20:40:07 +0000</pubDate>
		<guid isPermaLink="false">http://ponystyle.com/blog/?p=34#comment-332</guid>
		<description>[...] need to change its file extension (for example to .png). See this post for a detailed explanation: http://ponystyle.com/blog/2010/03/26/dealing-with-asset-compression-in-android-apps/ . Which again, increases your APK size even [...]</description>
		<content:encoded><![CDATA[<p>[...] need to change its file extension (for example to .png). See this post for a detailed explanation: <a href="http://ponystyle.com/blog/2010/03/26/dealing-with-asset-compression-in-android-apps/" rel="nofollow">http://ponystyle.com/blog/2010/03/26/dealing-with-asset-compression-in-android-apps/</a> . Which again, increases your APK size even [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dealing with Asset Compression in Android Apps by Android资源文件的大小限制及解决方案 &#124; Gossip Coder</title>
		<link>http://ponystyle.com/blog/2010/03/26/dealing-with-asset-compression-in-android-apps/comment-page-1/#comment-322</link>
		<dc:creator>Android资源文件的大小限制及解决方案 &#124; Gossip Coder</dc:creator>
		<pubDate>Sat, 24 Sep 2011 13:49:24 +0000</pubDate>
		<guid isPermaLink="false">http://ponystyle.com/blog/?p=34#comment-322</guid>
		<description>[...] 中文社区中对此有这样的一篇广为转载的文章，《Asset限制文件大小UNCOMPRESS_DATA_MAX为1MB》，其中的结论是：  目前解决的方法只有将文件放入到sdcard，但这样除了microsd的读取IO效率和耗电量解决不是很好，同时sd卡移除时可能存在问题，解决的方法如果数据量大的化通过sqlite是一种解决方法，同时openFileOutput方式读取也是不错的选择，看来android操作系统中最安全控制的严格，但犯了一个不小的错误。  字体文件显然没办法塞到sqlite里面，要求所有的用户都有SD卡也不太友好。又翻到一篇相关的英文文章，Dealing with Asset Compression in Android Apps。从中可以看出，Android 2.3之前的版本只对压缩过的资源文件的原始大小做了限制，这种限制可能是出于计算性能的考虑。对于没有压缩的文件，是没有大小限制的。哪些文件不会压缩？图片、音频、视频，包括这些后缀：  &#8220;.jpg&#8221;, &#8220;.jpeg&#8221;, &#8220;.png&#8221;, &#8220;.gif&#8221;, &#8220;.wav&#8221;, &#8220;.mp2&#8243;, &#8220;.mp3&#8243;, &#8220;.ogg&#8221;, &#8220;.aac&#8221;, &#8220;.mpg&#8221;, &#8220;.mpeg&#8221;, &#8220;.mid&#8221;, &#8220;.midi&#8221;, &#8220;.smf&#8221;, &#8220;.jet&#8221;, &#8220;.rtttl&#8221;, &#8220;.imy&#8221;, &#8220;.xmf&#8221;, &#8220;.mp4&#8243;, &#8220;.m4a&#8221;, &#8220;.m4v&#8221;, &#8220;.3gp&#8221;, &#8220;.3gpp&#8221;, &#8220;.3g2&#8243;, &#8220;.3gpp2&#8243;, &#8220;.amr&#8221;, &#8220;.awb&#8221;, &#8220;.wma&#8221;, &#8220;.wmv&#8221;  从Android的源代码中可以知道，Android的打包工具是通过文件的后缀名来判断文件是否需要压缩的。如果文件的后缀名是上面这些后缀，文件就不会被压缩，大小也就没有限制；如果文件的后缀不是上面这些，就对其进行压缩，并且在Android 2.2上有1MB的大小限制。字体文件后缀通常是.ttf，属于要被压缩的，在Android 2.2之前的版本中就有了体积限制。不过，看到这里，解决方案也出来了，把字体文件的.ttf后缀改成上述任意一个后缀，然后修改相应的代码就可以。好猥琐的解决方案啊~~ [...]</description>
		<content:encoded><![CDATA[<p>[...] 中文社区中对此有这样的一篇广为转载的文章，《Asset限制文件大小UNCOMPRESS_DATA_MAX为1MB》，其中的结论是：  目前解决的方法只有将文件放入到sdcard，但这样除了microsd的读取IO效率和耗电量解决不是很好，同时sd卡移除时可能存在问题，解决的方法如果数据量大的化通过sqlite是一种解决方法，同时openFileOutput方式读取也是不错的选择，看来android操作系统中最安全控制的严格，但犯了一个不小的错误。  字体文件显然没办法塞到sqlite里面，要求所有的用户都有SD卡也不太友好。又翻到一篇相关的英文文章，Dealing with Asset Compression in Android Apps。从中可以看出，Android 2.3之前的版本只对压缩过的资源文件的原始大小做了限制，这种限制可能是出于计算性能的考虑。对于没有压缩的文件，是没有大小限制的。哪些文件不会压缩？图片、音频、视频，包括这些后缀：  &#8220;.jpg&#8221;, &#8220;.jpeg&#8221;, &#8220;.png&#8221;, &#8220;.gif&#8221;, &#8220;.wav&#8221;, &#8220;.mp2&#8243;, &#8220;.mp3&#8243;, &#8220;.ogg&#8221;, &#8220;.aac&#8221;, &#8220;.mpg&#8221;, &#8220;.mpeg&#8221;, &#8220;.mid&#8221;, &#8220;.midi&#8221;, &#8220;.smf&#8221;, &#8220;.jet&#8221;, &#8220;.rtttl&#8221;, &#8220;.imy&#8221;, &#8220;.xmf&#8221;, &#8220;.mp4&#8243;, &#8220;.m4a&#8221;, &#8220;.m4v&#8221;, &#8220;.3gp&#8221;, &#8220;.3gpp&#8221;, &#8220;.3g2&#8243;, &#8220;.3gpp2&#8243;, &#8220;.amr&#8221;, &#8220;.awb&#8221;, &#8220;.wma&#8221;, &#8220;.wmv&#8221;  从Android的源代码中可以知道，Android的打包工具是通过文件的后缀名来判断文件是否需要压缩的。如果文件的后缀名是上面这些后缀，文件就不会被压缩，大小也就没有限制；如果文件的后缀不是上面这些，就对其进行压缩，并且在Android 2.2上有1MB的大小限制。字体文件后缀通常是.ttf，属于要被压缩的，在Android 2.2之前的版本中就有了体积限制。不过，看到这里，解决方案也出来了，把字体文件的.ttf后缀改成上述任意一个后缀，然后修改相应的代码就可以。好猥琐的解决方案啊~~ [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dealing with Asset Compression in Android Apps by Brian Hardy</title>
		<link>http://ponystyle.com/blog/2010/03/26/dealing-with-asset-compression-in-android-apps/comment-page-1/#comment-81</link>
		<dc:creator>Brian Hardy</dc:creator>
		<pubDate>Tue, 01 Mar 2011 14:40:23 +0000</pubDate>
		<guid isPermaLink="false">http://ponystyle.com/blog/?p=34#comment-81</guid>
		<description>@tomgamer, I just went and verified the current status of this issue, and made a small update to the post. It appears that this limitation on compressed asset size was removed in Android 2.3.</description>
		<content:encoded><![CDATA[<p>@tomgamer, I just went and verified the current status of this issue, and made a small update to the post. It appears that this limitation on compressed asset size was removed in Android 2.3.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dealing with Asset Compression in Android Apps by tomgamer</title>
		<link>http://ponystyle.com/blog/2010/03/26/dealing-with-asset-compression-in-android-apps/comment-page-1/#comment-80</link>
		<dc:creator>tomgamer</dc:creator>
		<pubDate>Mon, 28 Feb 2011 22:26:44 +0000</pubDate>
		<guid isPermaLink="false">http://ponystyle.com/blog/?p=34#comment-80</guid>
		<description>This seemed to work for me.  On my Moto CLIQ and my (and wifes) Motorola Droid 2 and several other phones, along with the emulators, this seemed to work just fine.  But when I published, the complaints came streaming in.
Debugging on a friend LG Ally (android 2.1), I found that the inputstream.read was throwing an exception.
Maybe it was my code?  Not sure, since it did work fine on some phones.  But reducing the file size below the limit resolved the problem with the LG Ally.</description>
		<content:encoded><![CDATA[<p>This seemed to work for me.  On my Moto CLIQ and my (and wifes) Motorola Droid 2 and several other phones, along with the emulators, this seemed to work just fine.  But when I published, the complaints came streaming in.<br />
Debugging on a friend LG Ally (android 2.1), I found that the inputstream.read was throwing an exception.<br />
Maybe it was my code?  Not sure, since it did work fine on some phones.  But reducing the file size below the limit resolved the problem with the LG Ally.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dealing with Asset Compression in Android Apps by Error when copying to File.DirDefaultExternal</title>
		<link>http://ponystyle.com/blog/2010/03/26/dealing-with-asset-compression-in-android-apps/comment-page-1/#comment-78</link>
		<dc:creator>Error when copying to File.DirDefaultExternal</dc:creator>
		<pubDate>Sun, 23 Jan 2011 17:43:05 +0000</pubDate>
		<guid isPermaLink="false">http://ponystyle.com/blog/?p=34#comment-78</guid>
		<description>[...] at this link for the reason for the error Dealing with Asset Compression in Android Apps.   &quot;any compressed asset file with an uncompressed size of over 1 MB cannot be read from the [...]</description>
		<content:encoded><![CDATA[<p>[...] at this link for the reason for the error Dealing with Asset Compression in Android Apps.   &quot;any compressed asset file with an uncompressed size of over 1 MB cannot be read from the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dealing with Asset Compression in Android Apps by jscoobysnack</title>
		<link>http://ponystyle.com/blog/2010/03/26/dealing-with-asset-compression-in-android-apps/comment-page-1/#comment-77</link>
		<dc:creator>jscoobysnack</dc:creator>
		<pubDate>Wed, 03 Nov 2010 20:24:27 +0000</pubDate>
		<guid isPermaLink="false">http://ponystyle.com/blog/?p=34#comment-77</guid>
		<description>Sorry. Here is a link to the code:

I added this to my Build.xml before the opening “setup task” tag. 
http://warpedimage.com/codesample/code.txt

The comment makes me think this only affects Resources and not files in the Assets folder. I tried to add the arg -0 to this section:
http://warpedimage.com/codesample/code2.txt</description>
		<content:encoded><![CDATA[<p>Sorry. Here is a link to the code:</p>
<p>I added this to my Build.xml before the opening “setup task” tag.<br />
<a href="http://warpedimage.com/codesample/code.txt" rel="nofollow">http://warpedimage.com/codesample/code.txt</a></p>
<p>The comment makes me think this only affects Resources and not files in the Assets folder. I tried to add the arg -0 to this section:<br />
<a href="http://warpedimage.com/codesample/code2.txt" rel="nofollow">http://warpedimage.com/codesample/code2.txt</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dealing with Asset Compression in Android Apps by jscoobysnack</title>
		<link>http://ponystyle.com/blog/2010/03/26/dealing-with-asset-compression-in-android-apps/comment-page-1/#comment-76</link>
		<dc:creator>jscoobysnack</dc:creator>
		<pubDate>Wed, 03 Nov 2010 20:04:22 +0000</pubDate>
		<guid isPermaLink="false">http://ponystyle.com/blog/?p=34#comment-76</guid>
		<description>Hi Brian,
I am having the same issue of assets still being compressed. I added this to my Build.xml before the opening &quot;setup task&quot; tag. 

    &lt;!-- Generates the R.java file for this project&#039;s resources. --&gt;
    
        Generating R.java / Manifest.java from the resources Joe style...
        
            
            
			
            			
            			
            
            
            
            
            
            
            
        
    


The comment makes me think this only affects Resources and not files in the Assets folder. I tried to add the arg -0 to this section:

    
        Packaging resources
        
    

but I get errors that aaptexec does not support args. Any ideas?</description>
		<content:encoded><![CDATA[<p>Hi Brian,<br />
I am having the same issue of assets still being compressed. I added this to my Build.xml before the opening &#8220;setup task&#8221; tag. </p>
<p>    <!-- Generates the R.java file for this project's resources. --></p>
<p>        Generating R.java / Manifest.java from the resources Joe style&#8230;</p>
<p>The comment makes me think this only affects Resources and not files in the Assets folder. I tried to add the arg -0 to this section:</p>
<p>        Packaging resources</p>
<p>but I get errors that aaptexec does not support args. Any ideas?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dealing with Asset Compression in Android Apps by Brian Hardy</title>
		<link>http://ponystyle.com/blog/2010/03/26/dealing-with-asset-compression-in-android-apps/comment-page-1/#comment-64</link>
		<dc:creator>Brian Hardy</dc:creator>
		<pubDate>Fri, 25 Jun 2010 00:18:40 +0000</pubDate>
		<guid isPermaLink="false">http://ponystyle.com/blog/?p=34#comment-64</guid>
		<description>It looks as though some of your comment was eaten by Wordpress. Can you post the relevant pieces again?</description>
		<content:encoded><![CDATA[<p>It looks as though some of your comment was eaten by WordPress. Can you post the relevant pieces again?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

