Issue with Internal Phone Storage

Discussion in 'Android Hacks and Help' started by HarleyDad09, Oct 11, 2010.

  1. HarleyDad09

    HarleyDad09 Member

    Joined:
    Nov 12, 2009
    Messages:
    265
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
    Good evening,
    I have had an issue twice now with my internal phone storage. I flashed BB .5 and got the phone storage running low error and got it again today when I flashed UD 1.0. I have all my apps on my SD card and I still have only:

    29.42 of free space

    I wipe Cache/Data 5 times prior to any flash. Does anyone have any idea why my storage is so maxed out?

    Has anyone else had this issue?

    Any recommended solutions?

    Thanks in advance!
     
  2. _jroid

    _jroid New Member

    Joined:
    Sep 12, 2010
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    My /system storage is 6.45MB/140MB free. I was wondering why it was so low as well. Have yet to get any warnings, but would like to free up some space as well.

    My other ones seem fine,|
    /data is 187MB/262MB free;
    /cache is 50.86MB/92.62MB free; and
    sd card is 12.42GB/14.83GB free.
     
  3. Se7enLC

    Se7enLC Active Member

    Joined:
    Nov 16, 2009
    Messages:
    1,262
    Likes Received:
    0
    Trophy Points:
    36
    Ratings:
    +0
    /system can be full and it doesn't cause any problems. Apps are moved into /system intentionally to give you extra space on /data for downloaded apps. Android won't warn you about /system getting full, because no apps write to /system, and in normal use, /system won't change (In fact, it's mounted as read-only, so you can't write to it unless you are intentionally doing so using root access).

    You will get warnings about /data being full, however. That's where your downloaded apps install to. For the OP - After you install, Google starts downloading all the apps you had installed and installs them on /data. Try removing a couple apps (or moving them to SD) and you should see the warning go away as soon as you get past around 30-32MB free or so.
     
  4. _jroid

    _jroid New Member

    Joined:
    Sep 12, 2010
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    Awesome, Thank you. That makes more sense. I'm good then. :icon_ banana:
     
  5. HarleyDad09

    HarleyDad09 Member

    Joined:
    Nov 12, 2009
    Messages:
    265
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
    All of my apps are already on my SD card...what else could be eating up so much space?!
     
  6. Se7enLC

    Se7enLC Active Member

    Joined:
    Nov 16, 2009
    Messages:
    1,262
    Likes Received:
    0
    Trophy Points:
    36
    Ratings:
    +0
    With the Froyo method of apps to sd (apps2fat is a good name for it, I guess?) the apps are only PARTLY stored on the SD card. They still can take up quite a bit of space on the /data partition. Flash for example is 12MB, but when stored on SD still takes up 8MB of /data.

    To check how much space you are using, open up Terminal Emulator (install from market if you don't have it).
    Code:
    cd /data
    du -d 1 -h
    
    That will list how much space is being taken up by each directory under /data. You should expect to see a lot in app, data, and dalvik-cache

    app is where the apk files are physically stored. data is where applications store their data. (emails, text messages, etc). dalvik-cache is where android stores an optimized version of the package for fast execution. This directory is auto-generated on boot.

    You can go into any of those directories to see what space is being taken up by what application by a similar method:
    Code:
    cd /data/app
    du -d1 -a -h
    
    Or you can look at the list of apk files in order of ascending size. You'll see the largest packages at the bottom:
    Code:
    ls -trsSh
    
    Now for the /data/data directory:
    Code:
    cd /data/data
    du -d 1 -h
    
    Most applications don't store more than a mb, but if you have a lot of apps, it adds up. On my droid:

    Browser uses 10mb
    Adobe Air uses 11mb
    Google Earth uses 15mb
    Tango uses 8mb
    Adobe Flash Player uses 8mb
    Facebook uses 5mb

    Droid is VERY limited on /data space (268mb total). If my system is any indication, the dalvik-cache directory will be around 30% of the size of the installed apks and the associated data will be around 50%. When the free space drops to below 30mb, you get that warning. Doing the quick estimate, that means 268 = X + 0.5X + 0.3X + 30 -> X ~= 120mb

    Until apps2sdext becomes more mainstream in Froyo roms, you're pretty much stuck with "install fewer apps". as the only option for clearing up space.

    apps2sdext uses a second partition on your SD card to actually replace /data with a larger storage space. It is not currently very mature on Froyo ROMs, so I wouldn't recommend trying it, yet, until the bugs are worked out.
    (using a partition on the SD card to ACTUALLY replace the /data partition)
     
  7. Bear in NM

    Bear in NM Active Member

    Joined:
    Nov 12, 2009
    Messages:
    1,389
    Likes Received:
    1
    Trophy Points:
    38
    Ratings:
    +1
    Great post 7, and I would only add that to use the coomands on my terminal I had to SU first. Perhaps obvious.

    I have followed your other thread on your memory exploits with ext, and I think the term "mature" might be generous on your part.....

    Thanks again,

    Craig
     
  8. Se7enLC

    Se7enLC Active Member

    Joined:
    Nov 16, 2009
    Messages:
    1,262
    Likes Received:
    0
    Trophy Points:
    36
    Ratings:
    +0
    Oh, right. I set up my Terminal Emulator to start up with root. I just changed "System Shell" in the preferences to be "/system/xbin/su -c /system/xbin/bash".

    Haha, yeah, it's been a bit of a headache, but I suspect that when it makes it into CM, it'll be more robust. It really does work well (fast, functional), it just sometimes needs a bit of a kick to get it to mount /sd-ext and load the apps. I currently have 204MB of apps installed (plus 105MB of data, 60mb of cache) and I couldn't be happier not having to decide what to delete every time another large app comes out that I want to play with.
     
  9. Bear in NM

    Bear in NM Active Member

    Joined:
    Nov 12, 2009
    Messages:
    1,389
    Likes Received:
    1
    Trophy Points:
    38
    Ratings:
    +1
    7,

    It would be nice to know CM is working on this. While I had to dump CM for other reasons, I keep checking back on their progress. While running it, I did manage to muddle through compcache, and found that it was pretty nice for dealing with redraws, etc. Your other exploits to get it working in CM looked a "tad" more complex than compcache. I am not quite to out of memory problems yet, but if I keep my phone much longer it is only a question of when not if.

    Craig
     
Search tags for this page

android phone storage is read only

,
how to fix read only internal storage error on android terminal emulator
,
motorola droid m internal storage issue?
,
which one cell phone is good with storage issue