Titanium Community Questions & Answer Archive

We felt that 6+ years of knowledge should not die so this is the Titanium Community Questions & Answer Archive


Ever since I updated to the latest Titanium SDK, I keep getting these insufficient storage errors. I only have the Kitchen Sink app on my Android Emulator and I have installed apps of 1mb - 30mb. No matter what the size, even 1mb, I get these errors while developing. This was supposedly fixed a couple of sdk's ago.

I don't know if this is an Android issue or a Titanium issue, but nonetheless, it is an issue.

The only solution I have found is to go into settings uninstall the most recent app and then reinstall it again via Titanium Developer. These is a very inefficient use of time and very frustrating to have to uninstall every time I want to test a single change in the app.js.

This happens every time I update an app unless I do the aforementioned.

On another note, I noticed that when the apps are being updated by relaunching from Titanium Developer after an update, the size of the app "almost" doubles even if only one word changes in the app.js file. I say "almost" because I noticed that its usually closer to 80-90% larger than the original file size.

Shouldn't it be "replacing" the app and not "adding" to it at the very least? Ideally, it would look for differences between the new app and the original and only update what has changed. Just my two cents.

— asked September 23rd 2010 by C Lee
  • 2.2
  • android
  • apis
  • error
  • failed
  • install
  • install_failed_insufficient_storage
  • mac
  • sdk

5 Answers

  • Use SD Card: android:installLocation="preferExternal". Read more: Installing android apps to the SD Card

    — answered August 14th 2011 by Chris Magnussen
    • Worked !

      — commented February 9th 2012 by JB Roux
    • if I add android:installLocation="preferExternal" I get another error:


      that issue is signaled here and the solution for that problem is to revert back the manifest to: <manifest android:installLocation="auto">.

      It seems like a vicious circle…

      — commented September 20th 2013 by Mihai Marginean
  • How I finally solved this thing is by increasing the internal storage of the emulator. Here is an article about how to do that. I have to mention that at first it didn't work only with the instructions from the article. What worked for me was opening the AVD Manager, selecting the android virtual device I was having problems with, Edit, then going to Harware,New, selecting Property Ideal size of data partition. Then adding 512MB (very important 512MB not 512) to its value.Edit AVD and launch the app on this emulator again. The internal storage of the emulator should be now 512MB.

    — answered September 20th 2013 by Mihai Marginean
    1 Comment
    • Thanks Mihai! I was looking all over for what I thought had to be a simple fix for this issue, and your instructions finally were it :)

      — commented November 2nd 2013 by Matthew Lieder
  • was an iPhone only release, it has none of the fixes and features since 1.4.0 for Android. Have you checked the settings area for the amount of free memory on the emulator?

    — answered September 23rd 2010 by Don Thorp
    • Yes. The internal phone storage is set at 73.49MB available.

      — commented September 23rd 2010 by C Lee
    • Is there some way to increase the storage on the device or store my apps directly to the sd card?

      — commented September 23rd 2010 by C Lee
  • Anyone fixed this? My app isn't that big but i need it to work in the emulator so i can debug it.

    — answered August 14th 2011 by Ben Palmer
    1 Comment
    • Hi Ben,

      I am getting an Out of Memory error when i load my app, I researched a bit, and found this to increase the internal storage memory -


      But Titanium doesnt have the "additional emulator command line options" in the Debug or Run configurations. I think you might have to do it using the AVD Manager (which is how I increased the SD Card storage).

      Hope this helps. If I find a way to do it in Titanium, I will repost it here.

      — commented October 27th 2011 by Sridevi Kolluri
  • Go to your android SDK location folder and go into folder "tools" type android avd to launch android virtual devices manager, then locate the emulator wich has the same name than the one you use when you have the error.
    Delete it and close avd.

    Clean then rebuild projet. You should be good now.

    — answered July 19th 2013 by Citrus Yiman
The ownership of individual contributions to this community generated content is retained by the authors of their contributions.
All trademarks remain the property of the respective owner.