Insufficient storage available error

[StoneRyno]

The thing is it isn't a bug in the device it is a bug in google play store app. Can't exactly sue them since it is open source software. Someone just needs to find the bug and submit a code correction. It can be anyone inside or outside of google with the understanding of where to look for the bug and how to fix it. Us technical end users have identified the cause but those of us who identified the cause don't have the knowledge of where to look for what needs to be fixed to correct it and possibly even the coding knowledge to make the changes to the code. So what we have done is found a variety of workarounds that fix the issue for most everyone. To be honest the link2sd app is as easy to use to store apps on the SD cards as the built in move to SD feature of android. The only part is that a bit more work is needed as you need to partition the card with a 2nd partition. Which is pretty simple with many partition apps that have a wizard step by step that is as easy to do as installing something on your PC. It is by far the best workaround as it puts a stop to getting the error until you really are out of internal storage (less than 50MB). I believe this is an operating minimum much like how a PC performance degrades significantly if you leave too little of HD space left when you have only a single HD.

 

[suzet58]

I too have only a limited knowledge of many of the terms used in these messages, altho I do appreciate the info and at least I can try to learn. I had been unable to purchase any apps or update. I would either get a 907 error or insufficent memory. The main thing from everyones comments that I did pick up that worked, to a point, was uninstalling all app updates by just going thru the "my apps" listing with Play Store. At this point I am only having an issue with one app that first gives me the 907 error code and when I try again will then tell me I have insufficent amount of memory when that is bull. At this point I have only lost $.99, and I am still going to try for refund even tho it has been a couple of days.
Bottom line for some issues does seem to be the uninstalling of updates. A pain for sure but a partial answer until yet ANOTHER problem arises. At this point I am still only using the Droid 2 w/all recent updates.

 

[wharfwreath]

*FIX* Re: Insufficient storage available error

Hello,

I have posted the solution to this problem below, and the original link. Thanks to Jimmy @ jimmod.com for the fix. This should work on most or all phones and tablets. All you need is an Android terminal program (or Rom Toolbox already has one) and your phone to be rooted. Read below:

Today suddenly when I want to download an application from my Android tablet, I receiving this error : “Error Downloading xyzxyz. There is insufficient space on the device.”
It’s only displaying the error on downloading application with big size.

After browsing around, I found out that the cache folder (that I assume used by the market) is using small partition (around 20mb in my case).

So to solve this we need to change it to bigger partition.

Your gonna need Android Terminal Simulator or equivalent terminal app. This will also require your Android rooted.
Type ’su’ (root permission request will be showned, you need to approve it).
Type ‘cd /’
Type ‘umount /cache’
Type ‘mount -o rw,remount -t rootfs rootfs /’ (to set the folder access to rw – read write)
Type ‘rmdir /cache’ (delete cache folder)
I personally using root explorer to do point 5-6
Type ‘mkdir /sdcard/cache’
Type ‘ln -s /sdcard/cache /cache’ (to link cache folder to /sdcard/cache – which shoud have bigger partition size)

Done.
Try to rerun your Android Market and download big applications

The original link is here

There have been some reported issues that the problem resurfaces after a reboot. I have not found a fix for that as of yet. If you have any issues, go the main link above or search google and the xda or other forums.

 

[Ahorman]

I have GB and found a solution, at least on that platform. All I did was clear the data from the app that was updating, not uninstalled, just cleared it's cache. That worked for both apps that we're giving me trouble, they both updated without issue after.

 

[wsfulton]

I simply cleared the phone's cache. The 'App Cache Cleaner' app makes this very easy. If you don't have it already installed then you are unlikely to be able to install it while you have the 'Insufficient storage available' error. All is not lost as you can clear the cache for individual apps, manually, see Android 201: How (and when) to clear app cache or data | Android Central. You'll have to go through the apps one by one until you have cleared up enough cache.

 

[rando991]

Cache Clear is a good app too. Haven't yet tried Cache Cleaner

Sent from my SPH-D700 using Tapatalk 2

 

[KarelDeVries]

@Ahorman: I made an account just to thank you. Solution works like a charm!

 

[wemetzger]

I was having this problem in Cynogen. I upgraded to version 9.1 last week, and since then, the problem has disappeared.

 

[Robbie Doo]

Seems like this problem only happens under JB, and since no stable JB's are available yet I assume things like these should be expected.

 

[StoneRyno]

Seems like this problem only happens under JB, and since no stable JB's are available yet I assume things like these should be expected.

Unfortunately you would be wrong. It has happened to many on GB and ICS. This thread was started when I was still using GB based roms and progressively got worse. The only thing that solved it for me was to use link2sd. I still only keep about 70MB of internal storage free space but the error occured regardless of free space since I'd get the error when I had as much as 150 or 200MB free. Of course now that I'm on JB I'm having a whole other issue that I'll be posting about in another thread after posting this reply.

 

[Ian Murphy]

Thanks. Clearing data on the apps causing problems sorted it.
Appreciate you sharing as this bug was getting annoying.

 

[StoneRyno]

The problem crept back in on CM10 (JB) even with link2sd I get the error when space gets below about 90MB (15% free). So far keeping free space above 100MB seems to prevent the error. Before on CM9 I could let free space get below 50MB so that only the big apps that really didn't have enough space to store the download to perform an update to the app being updated would generate the error. So I kept it above 50MB. Some apps I can't store on the SD card even with link2sd as there is a loss in performance for those apps. So far that's not a problem as long as I don't find more apps that work better on internal storage despite the class 10 SD card I have being slightly better performance specs that the internal storage of the epic.

 

[devnullius]

I'm having the exact some problem on HTC amaze running stock HTC sense. Google play support is recommending a factory reset but there has to be an actual solution. I found a similar post where a guy resolved it by using Log Collector or a similar tool to find the error being thrown by the install package then manually correcting it. In has case I believe a temporary file existed in a folder that the install didn't like so he manually deleted the file and the problem was solved. I captured the log of a failed install and found an error but wasn't able to determine how to resolve it. Is anyone out there willing to look at the log to see if they can figure it out?

[solved] android updating apps gives insufficient free space

I had the same problem as the Stoned Ryno: android updating apps gives insufficient free space error.

For me it was not random, all that couldn't install stayed non-installable. But removing it in Google Play in re-installing worked. Also not a space problem here!

Your remark about a stubborn temp file led me to the following solution: I installed Advanced Mobile Care (IObit) ( https://forums.androidcentral.com/e...bilecare&feature=search_result&token=thBPQNAW. ).

I left tasks alone and cleaned cache related items. After this, Google Play would not give errors any more while updating most apps.

Thank you all!

Devvie


Cuisvis hominis est errare, nullius nisi insipientis in errore persevare
��
All spelling mistakes are my own and may only be distributed under the GNU General Public License! � (� 95-1 by Coredump; 2-012 by DevNullius)

 

[FatMixG]

Just based upon the # of complaints I've see, there are enough people to constitute a class. Regarding damages, there are several ways to prove damages. Like having to replace your phone. Some people actually have business apps on their phones which can't be updated/used causing loss of productivity etc...HTC and TMobile should be ashamed and sued!

 

[ratsttam]

Just based upon the # of complaints I've see, there are enough people to constitute a class. Regarding damages, there are several ways to prove damages. Like having to replace your phone. Some people actually have business apps on their phones which can't be updated/used causing loss of productivity etc...HTC and TMobile should be ashamed and sued!

It is a Cache issue. One that can be resolved pretty easilly once one knows what the issue was in the first place. It's just the way it is.
To become a class, there would have to be proof that a very specific issue affected a certain number of people, and cost them a certain amount in damages. A couple non-updated apps on a smartphone would not make this cut. Any businessman relying THAT much on their phone, and losing that much because of an app install issue, probably won't be in business for very long. Also the license agreements, and your contract, explicitely state that they are not responsible for any losses due to the use or misuse of the device... So that throws it right out the window.

And now the second part of your complaint, about how HTC and TMobile should be ashamed of themselves. Perhaps they should, but you posted your rant in the Epic 4g forum, which is a SAMSUNG device on SPRINT !

 

[StoneRyno]

It is a Cache issue. One that can be resolved pretty easilly once one knows what the issue was in the first place. It's just the way it is.

What is the best way to go about clearing up the cache for this issue? I've tried using My Backup root (wipe cache) and link2sd (clear all app cache) and still run into the insufficient storage available error after doing so more times than not. In fact what is really strange on my tablet with CM9 I can have 250MB+ free space and get the error. Even after trying the same cache clearing things on it and what not other troubleshoots for android phone. I don't have an ext4 sd card partition on the tablet since it technically doesn't have an sd card but a fat 32 partition on the same storage device as the internal storage which acts as an sd card.

 

[Eyal Levy]

Quick and dirty solution, expanded from someone else's post in some forum I bumped into:

The Insufficient storage available error seems to be related to Android's failed attempt to install software directly to the phone's internal SD card. If you get the error, try the following (example taken from Samsung menus):
1. Do Settings -> SD card and phone storage -> Unmount SD card
2. Re-try to install the software that produced the error message. Android will scratch its head, say hmm, no SD card, and successfully install in phone memory (as long as there's enough free).
3. Go to Settings and re-mount the SD card
4. Go to Settings -> Applications -> Manage applications -> "On SD Card" tab
5. Find the software you just installed and move it to the SD card manually. Sometimes it fails first time around, but works OK afterwards.

It's a pain in the backside to do this rather lengthy procedure, but it appears to work, and you don't need root, additional software or rummaging around in the system innards. But it gets ever worse:

Sometimes the message appears when trying to apply an update to existing software. This I haven't yet tried since learning the unmount/mount trick, but I assume you need to do the following:
1. Try to apply all the updates currently waiting. Some may succeed and some may fail. Make a note of the failed ones.
2. Go to Settings -> Applications -> Manage applications -> "On SD Card" tab
3. Move the failed update apps back to the phone.
4. Do Settings -> SD card and phone storage -> Unmount SD card
5. Apply the updates. Hopefully the same trick should work here, too.
6. Re-mount the SD card and move the software back onto it as described above.

It is preferable not to make the mistake of installing software to phone memory when it's already installed on the SD card. This causes a mess.
Did I already mention the pain the backside? Oh well... But at least it works, and that's better than cursing the phone and putting up with its bugs.

 

[Verttex]

With the small internal storage you have on the Epic 4g, it is easy to fill it up. I suggest moving apps that are able to be moved, over to the SD card. (get a big one if you love apps, I have a 32g) Apps that are unable to be moved, check out Link2SD.

For cleaning the SD card, use SD Maid
For cleaning cache in general, I use Clean Master.

 

[fwuts]

I had the same problem on my Galaxy Tab 2 (rooted). I think it happened after I tried Link2SD.
Any way the solution was to download and enter "Terminal Emulator", execute 'su', execute "pm set-install-location 0". This sets it up as 'auto'. It was set to '2' (external).
I believe the problem is that the GT2 has an internal 'SDCard' and an external "extSDCard" and there is some kind of confusion between them in the OS (4.1.1 Ice Creme Sandwich)

 

[Appthief]

I had the same problem on my Galaxy Tab 2 (rooted). I think it happened after I tried Link2SD.
Any way the solution was to download and enter "Terminal Emulator", execute 'su', execute "pm set-install-location 0". This sets it up as 'auto'. It was set to '2' (external).
I believe the problem is that the GT2 has an internal 'SDCard' and an external "extSDCard" and there is some kind of confusion between them in the OS (4.1.1 Ice Creme Sandwich)

Thank you so much! My situation was exactly the same as yours, right down to the device (rooted) and firmware. Link2SD can kiss my a**. Again, thank you this solved the problem immediately. I was not looking forward to a full restore.