I see a great many forum posts and blogs talking about the Insufficient Storage Available (ISA) problem when users have installed a new microSD card and they are bewildered why there can be such an error message with plenty of available space.
I just came into a new LG Opt F6. In asking me what I needed in a phone when I was buying it, I told the sales rep that I needed "long battery charge" and "room for apps and not so much media files." The sales rep laughed and said that the F6 was the last phone I wanted because it has no room for apps, and Android doesn't install apps on the external 32GB SD card I was buying. (He was trying to sell me his wife's year-old Galaxy S4 for $400 (!) as having room for apps; but he's a nice guy selling MetroPCS service.)
So to get back on topic, I set up the app install location using adb in the SDK toolkit just like everyone else reading the dozens of forum articles or blogs describing how to do it.
And naturally I ran into the ISA problem. I kept playing with it. And then I chanced to install the Adobe Reader app. Then the Walmart store app. I tried to install the Smartq (PDF) reader--what I really wanted to try as a PDF reader---and it kept giving the ISA problem.
I restored the set-install-location to "auto" (0) rather than external card (2).
The Smartq reader then installed. When I checked (System) Settings->Apps->Smartq Reader, I noticed that the Move to SD button was dimmed.
It suddenly becomes clear why the ISA message appears now when the system tries to forcibly install to the external SD card: it's because the app developer insists that the install location NOT be to anything but internal memory (location 1), and the ISA is apparently the means by which this exception is handled.
Now what I just posted above may not be news to anyone and what I described may be posted elsewhere, although I did not find it.
There should be an error message like "App cannot be installed to external storage. Reset install location to Auto" which removes a lot of confusion, and it informs the user that the developer insists (wrongly? accidentally?) on using phone storage.
I am going to write to the Smartq PDF app developer to ask why the app must be installed in internal phone storage (whereas the Adobe Reader does not insist). It could be just a case where it is useful/advisable to set an option in the app build not to insist on an install location.
I just came into a new LG Opt F6. In asking me what I needed in a phone when I was buying it, I told the sales rep that I needed "long battery charge" and "room for apps and not so much media files." The sales rep laughed and said that the F6 was the last phone I wanted because it has no room for apps, and Android doesn't install apps on the external 32GB SD card I was buying. (He was trying to sell me his wife's year-old Galaxy S4 for $400 (!) as having room for apps; but he's a nice guy selling MetroPCS service.)
So to get back on topic, I set up the app install location using adb in the SDK toolkit just like everyone else reading the dozens of forum articles or blogs describing how to do it.
And naturally I ran into the ISA problem. I kept playing with it. And then I chanced to install the Adobe Reader app. Then the Walmart store app. I tried to install the Smartq (PDF) reader--what I really wanted to try as a PDF reader---and it kept giving the ISA problem.
I restored the set-install-location to "auto" (0) rather than external card (2).
The Smartq reader then installed. When I checked (System) Settings->Apps->Smartq Reader, I noticed that the Move to SD button was dimmed.
It suddenly becomes clear why the ISA message appears now when the system tries to forcibly install to the external SD card: it's because the app developer insists that the install location NOT be to anything but internal memory (location 1), and the ISA is apparently the means by which this exception is handled.
Now what I just posted above may not be news to anyone and what I described may be posted elsewhere, although I did not find it.
There should be an error message like "App cannot be installed to external storage. Reset install location to Auto" which removes a lot of confusion, and it informs the user that the developer insists (wrongly? accidentally?) on using phone storage.
I am going to write to the Smartq PDF app developer to ask why the app must be installed in internal phone storage (whereas the Adobe Reader does not insist). It could be just a case where it is useful/advisable to set an option in the app build not to insist on an install location.