Take the 2-minute tour ×
Android Enthusiasts Stack Exchange is a question and answer site for enthusiasts and power users of the Android operating system. It's 100% free, no registration required.

A while ago, I posted another question here when I had plenty of free internal storage but was getting the following warning:

Low on space: Phone storage space is getting low.

The problem was apparently a bug during the upgrade to Gingerbread, and following the steps in the accepted answer to get the hotfix resolved the issue for several months.

However, recently I've been getting that same message again. Even though it complains about low internal storage, clicking on the warning brings me to a screen that shows me:

Internal storage: 348MB used, 400MB free

I'm using a Verizon HTC Incredible running Gingerbread. I have followed the steps in the other question (clearing system cache) and rebooted the phone several times. I have moved many apps to the SD card which seems to resolve the issue for a few days, but then the warning comes back. It seems like 47% full should not be triggering a low space warning (which has other ramifications, like my email not refreshing).

Any ideas what's wrong this time?

share|improve this question
3  
This error could be from your /cache, /data, or /datadata partitions being almost full. Even though you have 400MB free total, these locations do not have access to all that space. YOu can try moving some of the larger apps to the SDCard, but if it is /cache or /datadata the only solution would be to remove some of the apps or deleting their data. –  Ryan Conrad Apr 2 '12 at 20:01
2  
@RyanConrad: Is there any way to figure out the used/available space on each of those partitions without being rooted? –  jrdioko Apr 2 '12 at 20:45
1  
@jrdioko - I don't believe I've ever run against that particular error - when mine has trouble I just get tons of force closes :-/. However, my app settings screen shows me what must be the /data usage (never close to full, numbers match /data size reported by DiskUsage) even though my apps are actually constrained by the much smaller /data/data (where I run out of room often). I think it's giving you an error because of /data/data but showing you details from /data instead. That's confusing as hell. –  Mr. Buster Apr 4 '12 at 22:23
1  
@jrdioko - My dinc's /data is 748 MB and my /data/data is 149 MB. Sounds like that should be the same for yours (and others'). –  Mr. Buster Apr 4 '12 at 22:33
1  
@jrdioko - FWIW I was just fighting again with this same issue and found that telling Dolphin (my browser of choice) to Cache to SD Card really helped free up some space. –  Mr. Buster Apr 11 '12 at 0:37
show 6 more comments

2 Answers

up vote 7 down vote accepted
+50

To consolidate comments:

I've found a fantastic guide to Android partitions and basics here via WIW's XDA post. /data is all your personal settings, messages, and information, while /data/data is specifically for your apps' private data. My guess is that wiping /cache as described above does not wipe /data or its child directories (otherwise you would've lost all your apps and settings).

I don't believe I've ever run against the particular error you're seeing - when mine has trouble I just get tons of force closes :-/. However, my app settings screen shows me what must be the /data usage (never close to full, numbers match /data size reported by DiskUsage) even though my apps are actually constrained by the much smaller /data/data (where I run out of room often). I think it's giving you an error because of /data/data but showing you details from /data instead. That's confusing as hell.

My dinc's /data is 748 MB and my /data/data is 149 MB. Sounds like that should be the same for yours (and others'). Until you give in to the dark side and root your Incredible (and are then able to see specific usage) you'll want to keep things below 149 MB (ish). FWIW, my biggest disk-hogs are Facebook and Dolphin Browser.

share|improve this answer
add comment

Check this answer to a similar problem. Basically delete from /data/log. Before you do, if you have the chance (phone still operational) then check the files to see what the errors being logged are.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.