Thanks -- that article was helpful, even if it didn't really provide a good answer besides "cheat". Silly thing is, there's really no need for the limitation -- a larger file could easily be compressed/ decompressed in chunks, and still be seamlessly readable as a sequential file. You probably wouldn't be able to do random access, but I suspect that's a rare requirement. (And of course, they could provide a way to set the options for aapt under Eclipse.)
On Sep 29, 5:32 pm, mkellner <m.kin...@gmail.com> wrote: > > The issue has nothing to do with speed. The issue is getting a large > > file to be readable AT ALL. When you open a compressed file larger > > than 1M you get an exception: Data exceeds UNCOMPRESS_DATA_MAX > > I called my 3MB .zip file a .jet file to get it to be added to > the .apk uncompressed. > > I figured that calling it a ".zip" file would imply that it's > compressed and figured that it would be added uncompressed. Imagine my > surprised to find otherwise. ".jet" is currently set up not to be > compressed. > > Here is an article which contains a list of the other uncompressible > filetypes. > > http://ponystyle.com/blog/2010/03/26/dealing-with-asset-compression-i... > > -mk -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
