• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

insufficient storage available

This phone is crap i have a handful of downloaded apps and between the updates and whatnot I have run out of phone storage you know I bet apple phones dont have this problem. why is it that they cant give enough storage for apps on a phone its like they dont have the technology or what the heck it is.
 
This phone is crap i have a handful of downloaded apps and between the updates and whatnot I have run out of phone storage you know I bet apple phones dont have this problem. why is it that they cant give enough storage for apps on a phone its like they dont have the technology or what the heck it is.

Lol, there are methods around that but it appears you haven't taken the time to come to know of these things. I recommend you do some reading ;-)
 
Download terminal emulator from the play store, run it and type logcat -c then enter. Type exit and try to install an app. It should give you more space to install more apps.

Btw, doing this, I went from 125 mb free to 1 gb free. YMMV

Could you explain what exactly this does?
 
Download terminal emulator from the play store, run it and type logcat -c then enter. Type exit and try to install an app. It should give you more space to install more apps.

Btw, doing this, I went from 125 mb free to 1 gb free. YMMV

Will it work if I swapped SD Memory with internal memory
 
I'm having this issue as well, for some reason my phone reports that I have 127MB of app storage out of 4GB for some reason when all my apps take up less than 1 GB total. It also shows me as having 4GB of internal storage, but gives me a warning when I try to install any app on play store "insufficient storage available". My SD is 32GB and not an issue.

I tried the logcat -c command in terminal and it did nothing, why is it reported as having less space than it actually does?
 
I'm having this issue as well, for some reason my phone reports that I have 127MB of app storage out of 4GB for some reason when all my apps take up less than 1 GB total. It also shows me as having 4GB of internal storage, but gives me a warning when I try to install any app on play store "insufficient storage available". My SD is 32GB and not an issue.

I tried the logcat -c command in terminal and it did nothing, why is it reported as having less space than it actually does?

This is because apps aren't stored on the 4gb of 'internal storage'. They are stored in the /data partition... Which is significantly smaller


The space for apps is just over 1gb
(in the screen shot, 'media' is the internal storage and 'internal' is the space for apps & app data)
 
I'm having this issue as well, for some reason my phone reports that I have 127MB of app storage out of 4GB for some reason when all my apps take up less than 1 GB total. It also shows me as having 4GB of internal storage, but gives me a warning when I try to install any app on play store "insufficient storage available". My SD is 32GB and not an issue.

I tried the logcat -c command in terminal and it did nothing, why is it reported as having less space than it actually does?

Why don't you try swapping internal with external memory. Here is link to the thread. This is assuming u have your phone rooted and have custom recovery installed. http://forum.xda-developers.com/showthread.php?t=2306841
 
How with a nandroid backup?

Yes you can do a nandroid backup. Or you can just go to the thread that I provided and they should have a flashable zip so you can restore the memory back to stock. But you should make a nandroid backup just in case something goes wrong when the flashing the zip
 
Yes you can do a nandroid backup. Or you can just go to the thread that I provided and they should have a flashable zip so you can restore the memory back to stock. But you should make a nandroid backup just in case something goes wrong when the flashing the zip

I heard you need to also backup your recovery, is that true too?
 
I heard you need to also backup your recovery, is that true too?

The stock recovery is mainly for allowing the ability to accept OTA's or any other possible updates that may need to use the recovery to be applied. Also, for the ability to simply return your device back to its original form if one later on chooses to not be rooted, S-Off, Bootloader unlocked, etc, etc. And for other simple reasons as well.
 
The stock recovery is mainly for allowing the ability to accept OTA's or any other possible updates that may need to use the recovery to be applied. Also, for the ability to simply return your device back to its original form if one later on chooses to not be rooted, S-Off, Bootloader unlocked, etc, etc. And for other simple reasons as well.

Oohh ok so if I do the memory swap thingy and something goes wrong, a nandroid backup will fix it?
 
Oohh ok so if I do the memory swap thingy and something goes wrong, a nandroid backup will fix it?

A nandroid backup will normally contain the following. A backup of your system partition, data partition, cache partition, boot partition, and depending on the recovery and/or the user, there may be other partitions included, but the ones I listed are the main focus.

The system partition is where you find all your system apps, frameworks, modules, etc, etc. Its basically every single file and subdirectory located in the /system folder if looking at it with a file manager like es file explorer. The data partition is the same thing, as well as the cache, and so forth. The boot.img is normally pulled by the custom recovery using the dd command and then simply renames it to something else like boot.emmc.win for example. They do that as a signature thing on their part but it is no different then renaming it to boot.img. The system.img from the system partition is pulled and then reformatted to usually a type of tar file depending upon the recovery being used to make the backup. For example, TWRP names it system.ext4.win (or something similar - going off the top of my head). Just rename it to system.img and it would basically be the same thing. It looks crazy, but it is simply a tar file and the following command will extract it:
Code:
 tar -xvf system.img

Anyways, yes, a backup will recover your device, but some things need to be considered. When you make changes on your phone, you need to determine what and where is actually being modified. Does it fall in the system partition, boot partition, data partition, etc, etc. If it does, then you will know your backup will restore and fix it. BUT, if its something pertaining outside of these known partitions that would normally be found in a backup then you may be required to pull that specific partition manually for safe keeping (but that is normally done so by more advanced users).
 
The only partition I have learned from our device that would literally wreck you by a hard brick is the HBoot. You screw that up and your phone is paperweight. Seriously lol.
 
The only partition I have learned from our device that would literally wreck you by a hard brick is the HBoot. You screw that up and your phone is paperweight. Seriously lol.

Damn :O pretty risky stuff, this is why I am kind of hesitating to do the memory swap stated earlier cuz it sounds too risky, well at least for me
 
Damn :O pretty risky stuff, this is why I am kind of hesitating to do the memory swap stated earlier cuz it sounds too risky, well at least for me

It isn't, lol. Worst case with that if done wrong, is a soft brick. A soft brick basically is no different than a bootloop, FC, and so forth. It means the phone won't boot up in some way, but you still have the ability to get access to the HBoot and thus, fix your phone ;-)
 
It isn't, lol. Worst case with that if done wrong, is a soft brick. A soft brick basically is no different than a bootloop, FC, and so forth. It means the phone won't boot up in some way, but you still have the ability to get access to the HBoot and thus, fix your phone ;-)

I'm still new with the hboot and stuff, I'm surprised I made it through rooting, bootloader unlock, and s-off lol
 
Back
Top Bottom