Quote:
Originally Posted by nzer
With the lower memory you mentioned ~12 out of 128MB is there any issues using the boot animation later or is that simply the memory it uses on installation?
|
I believe that the unit has about 8GB of storage in total. This data gets partitioned into different sections for different uses. For example:
/cache = 50MB (too small for downloading large apps)
/system = 128MB (contents of system.img)
/sdcard/udisk = whatever you've plugged in via USB
/sdcard/extsd = whatever you've plugged in via MicroSD
Other locations use different sections. When you copy the bootanimation.zip file into /data/local, you are actually placing it in an alternate location - on a section with much more space. The 'normal' location for Android to find bootanimation.zip is somewhere else on /system, where things are a little more cramped.
Generally /system is a location that folks shouldn't be touching/changing - which is why superuser rights are required to access it. AFAIK, there is no trouble running /system in an almost-full state. The only time where it may be an issue is if the vendor provides a formal update - but I don't really see that happening, and if they do it will probably be in the form of a system.img that will just blow away the existing stuff anyway.
Having said that though, if the /system partition was full, then it becomes increasingly difficult for users like us to simply add a file here or there, so it's always a good idea to leave a little room for tinkerers. In our case, I could look at deleting some of the unused logos to free up space again if I think things are getting a bit tight.