Hi guys,
Before I get started, I read all posts about low storage issues, none of them gave a solution to my problem. I've also read a lot of forums (either spanish or english) and many people have this problem, with indeed no solution yet
Two days ago I installed AirDroid (a friend of mine suggested me to) to check from my desktop pc my cellphone. Today, I opened it again and saw that my system memory had 1,1Gb free. I logged off and started listening to music. 30 minutes later, my internal memory dropped to only 110Mb free, and I hadn't downloaded anything. I double checked from AirDroid and my memory was low, no idea how
I'm on a Defy, CM7, Gingerbread 2.3.4
Help is much appreciated! As you may have noticed, I'm as dumb as wood regarding this, hehe
P.S. Sorry if this lacks of information, or it's even in the wrong place! Just ask and I'll give you as much details as possible
Well, now to proove myself that it's a Defy error, I made the summary of Mb used by the apps in the internal memory -> they just use 120Mb! It's impossible that it has reached 1.1Gb
Can someone help me?
Recently I had a similar problem with my defy. I installed the app DiskUsage and found out that the problem was in the folder /data/tombstones where android saves the crash logs, I had a file there that was taking over 700 MB. I removed the folder (it's safe to do so) using rootexplorer and everything went back to normal..
The Thanks button is not nearly enough to thank you. I had the same problem, a tombstone file was taking 1.1Gb!. Deleted the folder, and memory went back to normal values
Again, thank you
staarbreaker said:
Recently I had a similar problem with my defy. I installed the app DiskUsage and found out that the problem was in the folder /data/tombstones where android saves the crash logs, I had a file there that was taking over 700 MB. I removed the folder (it's safe to do so) using rootexplorer and everything went back to normal..
Click to expand...
Click to collapse
Thanks for sharing this wonderful App.
This is same as we have Windows .... Space Sniffer.
This what I was looking for Thanks Again!!
staarbreaker said:
Recently I had a similar problem with my defy. I installed the app DiskUsage and found out that the problem was in the folder /data/tombstones where android saves the crash logs, I had a file there that was taking over 700 MB. I removed the folder (it's safe to do so) using rootexplorer and everything went back to normal..
Click to expand...
Click to collapse
Did you know what 's generate this
"Huge" problem?
Because I met it on minui and cm7
Sent from my MB525 using XDA
hbexpar
vaserbanix said:
Did you know what 's generate this
"Huge" problem?
Because I met it on minui and cm7
Sent from my MB525 using XDA
Click to expand...
Click to collapse
I've absolutely no idea of what caused it, it happened to me just once, and the phone was running normally when it happened
I am using wiui stable btw..
staarbreaker said:
Recently I had a similar problem with my defy. I installed the app DiskUsage and found out that the problem was in the folder /data/tombstones where android saves the crash logs, I had a file there that was taking over 700 MB. I removed the folder (it's safe to do so) using rootexplorer and everything went back to normal..
Click to expand...
Click to collapse
Same problem for me (CM7.2-Maniac builds) resolved by removing the files (~600MB) into /data/tombstones!
I was near to wipe data/factory reset
Thank you !
Hey guys. How do I delete my tombstones? The disk usage app gives me an error when I try to delete them... It reports my tombstones folder to be 850mb, but when I go to the data folder in file manager, it's empty. Do I need another app or something to get access?
thanks heaps
nvm, ES File Explorer did the job...
Thanks i also had this issue on my Defy with cm7.2rc2.
Now i have uppdated to rc3
Same here, none of the root managers show /data/tombstones, I can only see it in DiscUsage, but it won't let me delete it. Any help?
lobie81 said:
Hey guys. How do I delete my tombstones? The disk usage app gives me an error when I try to delete them... It reports my tombstones folder to be 850mb, but when I go to the data folder in file manager, it's empty. Do I need another app or something to get access?
thanks heaps
nvm, ES File Explorer did the job...
Click to expand...
Click to collapse
Had the same problems.
The root browser in rom toolbox lite worked fine for me.
viktorassan said:
Same here, none of the root managers show /data/tombstones, I can only see it in DiscUsage, but it won't let me delete it. Any help?
Click to expand...
Click to collapse
Me occured this too.
I think it was caused by dolphin browser...
It's caused by Adobe Flash Player. Latest official builds and Maniac's latest nightly have a fix for this bug.
can't find folder
I can't find that folder
HybridRain said:
I can't find that folder
Click to expand...
Click to collapse
use rootexplorer to see and delete that
DEFYred ://cm10JB.Quarx powered by JellyX kernel
Where's the other 1.1Gb of my internal storage gone?
Ever since I rooted my phone and installed CM7.2, I've had my /data partition reduced to 128Mb. Running a df command on the phone, it appears that only 890Mb of the nominal 2Gb internal storage is actually mapped to any partitions. So what happened to the rest of it? And no, I have no tombstones I can find (looked in /data then did "cd /; find . -name tombstones -print" at # prompt). My "df -h" results for internal storage below. How does this differ (in "Size" column) from what other people see for their partitions?
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 238.6M 32.0K 238.5M 0% /dev
/dev/block/mmcblk1p21
326.2M 177.3M 148.9M 54% /system
tmpfs 238.6M 32.0K 238.5M 0% /dev
tmpfs 238.6M 0 238.6M 0% /mnt/asec
tmpfs 238.6M 0 238.6M 0% /mnt/obb
/dev/block/mmcblk1p24
193.7M 5.6M 178.1M 3% /cache
/dev/block/mmcblk1p25
127.8M 105.8M 22.0M 83% /data
/dev/block/loop7 3.9M 1.1M 2.8M 28% /pds
Thanks,
Richard
Isn't the rest allotted to internal memory for installing apps, etc?
Sent from my MB526 using xda app-developers app
1 Gb being used by tmpfs is somewhat excessive, no?
OK - so (having installed DiskInfo app) I realise that my calculation assumptions are somewhat wrong - each "tmpfs" partition shown in df command is a different one (even though all the same size), so that accounts for where the 2GB is going. However, having 238Mb almost all of which is (currently) unused in each of dev,dev(again),asec,obb seems excessive, particularly as it leaves only 128MB for /data. This surely can't be the normal set-up? And how would I go about changing it?
(Hotdog125 - not sure what you are getting at - perhaps you could be more specific?)
RichardT-UK said:
Ever since I rooted my phone and installed CM7.2, I've had my /data partition reduced to 128Mb. Running a df command on the phone, it appears that only 890Mb of the nominal 2Gb internal storage is actually mapped to any partitions. So what happened to the rest of it? And no, I have no tombstones I can find (looked in /data then did "cd /; find . -name tombstones -print" at # prompt). My "df -h" results for internal storage below. How does this differ (in "Size" column) from what other people see for their partitions?
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 238.6M 32.0K 238.5M 0% /dev
/dev/block/mmcblk1p21
326.2M 177.3M 148.9M 54% /system
tmpfs 238.6M 32.0K 238.5M 0% /dev
tmpfs 238.6M 0 238.6M 0% /mnt/asec
tmpfs 238.6M 0 238.6M 0% /mnt/obb
/dev/block/mmcblk1p24
193.7M 5.6M 178.1M 3% /cache
/dev/block/mmcblk1p25
127.8M 105.8M 22.0M 83% /data
/dev/block/loop7 3.9M 1.1M 2.8M 28% /pds
Thanks,
Richard
Click to expand...
Click to collapse
RichardT-UK said:
OK - so (having installed DiskInfo app) I realise that my calculation assumptions are somewhat wrong - each "tmpfs" partition shown in df command is a different one (even though all the same size), so that accounts for where the 2GB is going. However, having 238Mb almost all of which is (currently) unused in each of dev,dev(again),asec,obb seems excessive, particularly as it leaves only 128MB for /data. This surely can't be the normal set-up? And how would I go about changing it?
(Hotdog125 - not sure what you are getting at - perhaps you could be more specific?)
Click to expand...
Click to collapse
Not read it fully, but partition table cannot be altered by anyone or anything, on the defy. The partition table signature verification will simply break in such a event
Also, I have checked your partition table info, and as it is identical to mine, it is infact normal
Sent from my Nexus 7 using Tapatalk 2
Related
Ok, so I was rocking Thedude's 1.1a and new a2sd method on a 1 gig SD card. I recieved my 16 gig card in the mail yesterday, so I backed up my /system/sd/app and /system/sd/app-private, rebooted the phone with the new card in, partitioned it (500MB ext2), copied the directories back over to the SD and everything worked dandy.
Until, that is, I needed to install an application. First, it was LatinIME.apk. The app was acting goofy for my beforehand, but I was waiting until I got the new SD card to try fixing it. I removed the apk from /system/sd/app but the app still worked, so I had to uninstall it from the settings menu. I then tried installing it from the apk using appsintaller, but got the error message:
"Android Keyboard could not be installed on this phone."
Great.. I tried reboot etc, but nothing. So I try to ADB install it:
"INSUFFICIENT_SPACE_AVAILABLE" (or something to that extent, didn't write it down)
Alright, whatever. I physically copied the apk into /system/sd/app and it worked out beautifully.
Now, when I try to install an app from the market, I get an error:
"Installation error: Insufficient storage available"
which is complete BS because I can (using adb shell) put any file I want into /system/sd/app and there's 470 MB remaining.
I searched for this problem, but all I found were people with the same problem on A2SD old method, and they had to symlink app-private to their SD card too. I have app-private and app in /system/sd, so I'm not too sure what the problem is. When I remove my new card and use the old card, same problem. When I remove my card and try to have it install to /system/intmem, same problem. Does anyone have any ideas?
Ooglez said:
Ok, so I was rocking Thedude's 1.1a and new a2sd method on a 1 gig SD card. I recieved my 16 gig card in the mail yesterday, so I backed up my /system/sd/app and /system/sd/app-private, rebooted the phone with the new card in, partitioned it (500MB ext2), copied the directories back over to the SD and everything worked dandy.
Until, that is, I needed to install an application. First, it was LatinIME.apk. The app was acting goofy for my beforehand, but I was waiting until I got the new SD card to try fixing it. I removed the apk from /system/sd/app but the app still worked, so I had to uninstall it from the settings menu. I then tried installing it from the apk using appsintaller, but got the error message:
"Android Keyboard could not be installed on this phone."
Great.. I tried reboot etc, but nothing. So I try to ADB install it:
"INSUFFICIENT_SPACE_AVAILABLE" (or something to that extent, didn't write it down)
Alright, whatever. I physically copied the apk into /system/sd/app and it worked out beautifully.
Now, when I try to install an app from the market, I get an error:
"Installation error: Insufficient storage available"
which is complete BS because I can (using adb shell) put any file I want into /system/sd/app and there's 470 MB remaining.
I searched for this problem, but all I found were people with the same problem on A2SD old method, and they had to symlink app-private to their SD card too. I have app-private and app in /system/sd, so I'm not too sure what the problem is. When I remove my new card and use the old card, same problem. When I remove my card and try to have it install to /system/intmem, same problem. Does anyone have any ideas?
Click to expand...
Click to collapse
I hate to be devil's advocate here but do you know how much space is available on /system/sd/intmem? Could be that it's seeing that there isn't enough space there and so won't let you install.
[email protected] said:
I hate to be devil's advocate here but do you know how much space is available on /system/sd/intmem? Could be that it's seeing that there isn't enough space there and so won't let you install.
Click to expand...
Click to collapse
busybox df -h: (or at least the relevant parts)
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock5 74.8M 28.6M 46.2M 38% /system/intmem
/dev/block/mmcblk0p2 535.5M 27.8M 480.4M 5% /system/sd/
unionfs 535.5M 27.8M 480.4M 5% /data/app
unionfs 535.5M 27.8M 480.4M 5% /data/app-private
Also, I have tried wiping and reflashing the phone, then reinstalling the latest a2sd method (replacing both init.rc and a2sd.sh).. so I'm really at a loss :-/
i think there might be two explanations
one is that there is some other file system error, but the app installer is not designed to cope with that, so it mistakenly reports no space.
or the installer is hardcoded to check the /data partition instead of the mount point /data/app is in.
billc.cn said:
i think there might be two explanations
one is that there is some other file system error, but the app installer is not designed to cope with that, so it mistakenly reports no space.
or the installer is hardcoded to check the /data partition instead of the mount point /data/app is in.
Click to expand...
Click to collapse
I think it may be the first one. When I connect my SDcard to the computer using the pull down menu and mount (which worked on the 1 gig,) upon disconnecting, the phone crashes trying to "prepare the SD card" and will reboot. What's goin on, eh?
For troubleshooting purposes, this is what I get from
busybox df -h:
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 48.2M 0 48.2M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 90.0M 64.4M 25.6M 72% /system/
/dev/block/loop0 836.0K 836.0K 0 100% /system/modules
/dev/block/loop1 3.5M 3.5M 0 100% /system/xbin
/dev/block/mtdblock5 89.8M 29.8M 59.9M 33% /data
/dev/block/mtdblock4 30.0M 1.1M 28.9M 4% /cache
/dev/block//vold/179:1
7.4G 3.5G 3.9G 47% /sdcar
Using Dude's 1.2, I DO NOT want apps2sd, so do not have ext2 partition on my SD card. I like to just be able to install apps to internal memory.
Ooglez said:
I think it may be the first one. When I connect my SDcard to the computer using the pull down menu and mount (which worked on the 1 gig,) upon disconnecting, the phone crashes trying to "prepare the SD card" and will reboot. What's goin on, eh?
Click to expand...
Click to collapse
Sorry, wasn't concentrated enough the first time. I saw that using the unionfs method, you mounted the internal data partition on /system/intmem , so what is data now? Is it mounted at all? Because if it's not mounted, it is just a directory of the ramdisk image, which is read-only and indeed has no free space. Could you explain to my why it is necessary to mount mtdblock5 this way?
what is the output of :
ls -l /system/sd
It's a permission issue I think .
try
chown -r 1000:1000 /system/sd
chmod -r 755 /system/sd
I really do believe poeple need to read that sticky. Please people do a search before posting.
maybe the 2 100%'s in the chart?
Haven't tried ADB on my pc but trying to install from market gets me same from above, " insuffcient storage space available. This is what I get from busybox
$ busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 48.2M 0 48.2M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock. 367.5M 64.4M 3.1M 95% /system
/dev/block/loop0 836.0K 836.0K 0 100% /system/modules
/dev/block/loop1 3.5M 3.5M 0 100% /system/xbin
/dev/block/mtdblock5 74.8M 34.3M 40.5M 46% /data
/dev/block/mtdblock4 67.5M 1.5M 66.0M 2% /cache
/dev/block//vold/179:1
3.8G 3.4G 412.7M 89% /sdcard
I do not have A2SD mainly because I don't care for it. I am well aware that 1.2 of dude's bill carries bugs and I would revert back to 1.1 or something of similar likes but being unable to install a file manager and not being able to access a pc has left me with an eternally stock g1...
reverted to dude 1.1
That solved it now I'm on cyanogen's build works great. I'm ditching dude till he fixes it...
What DID WORK on the other hand was removing the entire app directory under /data/data.
So for instance for "Network Discovery" app that would not update due to
"insufficient storage available" i did:
cd /data/data
rm -rf info.lamatricexiste.network
The app would then install from Market as usuall.
apider said:
cd /data/data
rm -rf info.lamatricexiste.network
Click to expand...
Click to collapse
That's strange, I have this issue from time to time, developing from eclipse, when pushing update of my app to the device (N1).
Network Discovery does not have any special thing that could end to this behavior, using only the sdk..
Let me know martindjr88 if you are using "Network Discovery" too.
Hello all, I was wondering if anyone can help me. I recently installed JF 1.51US and was working on lucidrem's scripts. I installed the new SPL and everything went ok but now my EXT2 will not allow me to move apps and such. It is saying thismkdir failed for /system/sd/lost+found, read-only file system EXT2 Not Mounted Can anyone tell me how to remount EXT2? I spent the last hour searching and couldnt find an answer to my question.
Does anyone know by chance?
chrisrj28 said:
Hello all, I was wondering if anyone can help me. I recently installed JF 1.51US and was working on lucidrem's scripts. I installed the new SPL and everything went ok but now my EXT2 will not allow me to move apps and such. It is saying thismkdir failed for /system/sd/lost+found, read-only file system EXT2 Not Mounted Can anyone tell me how to remount EXT2? I spent the last hour searching and couldnt find an answer to my question.
Click to expand...
Click to collapse
on the JF1.51 it will mount the EXT2 automatically if it exists
Oh really. So then something must be wrong with my [email protected] then. I guess I will reformat and see. It's funny b/c it worked at first when I first rooted and then I did the spl update and went into bootloader, I had to wipe and re root and that's when it started saying the it wasn't mounted. Oh well, thanks for the info. Hopefully the format will work
Please let us know what happens
It would be useful info. thanks.
Can you post the output of
Code:
ls -l /dev/block/mmc*
from either an adb shell or terminal?
From what you've said it sounds like your ext2 partition is corrupt and that the format will fix this. Or if you're running linux, run e2fsck (or fsck.ext2) on the appropriate partition to repair it.
Kinslayer81 said:
Can you post the output of
Code:
ls -l /dev/block/mmc*
from either an adb shell or terminal?
From what you've said it sounds like your ext2 partition is corrupt and that the format will fix this. Or if you're running linux, run e2fsck (or fsck.ext2) on the appropriate partition to repair it.
Click to expand...
Click to collapse
I am having the same problem as chrisrj28, and my output is:
ls -l /dev/block/mmc*
brw------- 1 0 0 179, 0 May 26 20:39 /dev/block/mmcblk0
brw------- 1 0 0 179, 1 May 26 20:39 /dev/block/mmcblk0p1
brw------- 1 0 0 179, 2 May 26 20:39 /dev/block/mmcblk0p2
Click to expand...
Click to collapse
I think the filesystem just isn't set up (I had to manually format my fat partition after running sdsplit).
Sorry if this isn't the same problem chrisrj28.
Yeah I just manually formatted the ext partition in Paragon Partition Manager.
Works fine now. I guess I didn't run the make filesystem switch in sdsplit.
Yeah thanks for everyone that tried to help. I was able to get to a cpu and just formatted my EXT2 and it worked like a charm. Something I did when rooting must have made it read only. For anyone else with that issue just reformat your partition
Recently i read on this forums that alot of rom support app2sd.
I follow the instruction but was not able to get the app2sd working.
As the 2nd partition of the sdcard is not mounted on /system/sd.I would be able to use the 2nd partition if i mount it manually thru adb.
Is there a way how to auto mount the partition after every reboot of the phone.
Below are the what is the partition mounted
Filesystem Size Used Available Use% Mounted on
tmpfs 96.3M 12.0k 96.3M 0% /dev
tmpfs 4.0M 8.0k 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 90.0M 83.3M 6.7M 93% /system
/dev/block/mtdblock5 295.8M 74.6M 221.2M 25% /data
/dev/block/mtdblock4 80.0M 1.1M 78.9M 1% /cache
/dev/block//vold/179:1 6.7G 85.3M 6.6G 1% /sdcard
For your information i am using HTC Magic 32A
I can't help you out as I really can't see the need, but curiosity got the best of me. Why do you think you need Apps2sd? I can see it with the G1 as it was limited in space for apps, but the Magic has 512MB of internal storage. This should give you more than 500 apps, do you think you'll actually install that many or more? I have no idea what your doing with the phone or what your needs are but I can hardly see the need.
Clinton
Correct. For Magic and Hero users there's really no point in Apps2SD
a) you have plenty of space for apps (usually around 295MB of which the rom apps will take 40-60MB)
b) It will probably slow your apps down as it's thrashing the sd more - even if you have a class 6
c) you'll reduce the life of your sd card
d) you won't be able to remove your SD card/mount it on your pc if you wanted to without your phone crashing/apps dying/hanging/etc.
e) if your SD card is dodgy in the slightest then it will also cause the above.. crashing/hanging/random coredumps, etc - and you'll probably just blame the rom you're using.
f) compcache/swap/Cache2SD/Swapper, etc is just as silly if you're a 32A/Hero owner. Even on the G1/32B's it offers very dubious performance improvement - and there's no need with the 32A/Hero as you have plenty of ram.
g) if you're still reading this point then you really haven't learnt from any of the above and you'll do it anyway
If you want to purchase a big application (such as GPS navigation software with HUGE map - 1GB+), can I still install and use it without Apps2SD? I have Rogers Magic (32A)...
I just switched from WinMo HTC Diamond and currently plowing through a lot of reading material for Android...
Thanks!
Radix999 said:
Correct. For Magic and Hero users there's really no point in Apps2SD
a) you have plenty of space for apps (usually around 295MB of which the rom apps will take 40-60MB)
b) It will probably slow your apps down as it's thrashing the sd more - even if you have a class 6
c) you'll reduce the life of your sd card
d) you won't be able to remove your SD card/mount it on your pc if you wanted to without your phone crashing/apps dying/hanging/etc.
e) if your SD card is dodgy in the slightest then it will also cause the above.. crashing/hanging/random coredumps, etc - and you'll probably just blame the rom you're using.
f) compcache/swap/Cache2SD/Swapper, etc is just as silly if you're a 32A/Hero owner. Even on the G1/32B's it offers very dubious performance improvement - and there's no need with the 32A/Hero as you have plenty of ram.
g) if you're still reading this point then you really haven't learnt from any of the above and you'll do it anyway
Click to expand...
Click to collapse
I have the MyTouch and don't want to install apps2sd for the space, I want to install it because wiping before switching roms and some themes can be quite tenacious, having to re-download all of my apps over and over. Wouldn't having apps2sd take care of this?
Since when I have updated to official ICS I get now & then warning messages telling me there's not enough space left (i.e. 'ROM is full', '/system has not enough space left', etc., etc.) and this with the same apps installed as before and with plenty of room left in both the internal and external SD.
Running dp /system I get:
Code:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ df /system
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mmcblk0p9 858724 857736 988 100% /system
ics is probably heavier on apps and system settings than gingerbread, if you have root access you can always remove some app that arent used to gain more space
I had an issue on GB where the media scanner was eating up ~1GB of the system partition. Force close and clear cache sorted it.
No idea if it could be the same issue for you but worth checking...
Maskell said:
I had an issue on GB where the media scanner was eating up ~1GB of the system partition. Force close and clear cache sorted it.
No idea if it could be the same issue for you but worth checking...
Click to expand...
Click to collapse
impossible, the system partition is only 1gb in size for the rom, unless you mean the 2gb data partition for apps
Yep, you're right. My bad
Hello everyone and thank you for having me on your wonderful forum. I have learned so much in such a short time by reading everything I could whether I was intending to use it or not.
I got my 16gb Nexus on Monday and immediately prepped it for ROMs, settling on CM10.1 RC2, Prior to that I had an Optimus V running CM7. On my Optimus, after flashing CM7 for the long haul I was able to move all excess /system space back into /data using terminal emulator and the fdisk command, but I followed a guide of some sort that is long lost now.
Everything is fantastic so far except one thing, there seems to be quite a lot of space reserved in the /system and /cache partitions, and I am not sure if I am able to re-partition this space back to /data or how exactly to do this.
right now /system is reading at 395.8 / 827.8 MB used, and /cache is at 68.4 / 551.7 MB. I would like to repartition 200 MB away from /system and 300-400 MB away from /cache, and put it back into /data. This will leave me some space to integrate or convert a few apps to system apps, and enough cache space to be safe (why does it need 550 MB to begin with?) and give back another half gig of storage that I paid so much to have.
I have three issues with this, one being that I can find almost no information on this topic directly mentioning the NExus 4, and any relatable information from other devices talking about device specific toolkits to do the job.
The only thread I found on XDA about this is below, and it only gave me a vague "this is not possible"
http://forum.xda-developers.com/showthread.php?t=2248400
The second issue is I do not recall the command switches/flags that go with the fdisk command, only that I had to use some things to set file permissions or remount the partition or some such (I know, i'm a noob, forgive me).
Lastly, I am rather confused by the multiple partitions of /data and /storage/emulated all showing a partition size of 13231.8 MB. Obviously they are all the same physical space, but I am afraid to mess with the partitions and break what I assume are a ton of symlinks that trick apps into believing there is an external SD card in play. Can any of you shed some light on this for me?
I3ig Al said:
Hello everyone and thank you for having me on your wonderful forum. I have learned so much in such a short time by reading everything I could whether I was intending to use it or not.
I got my 16gb Nexus on Monday and immediately prepped it for ROMs, settling on CM10.1 RC2, Prior to that I had an Optimus V running CM7. On my Optimus, after flashing CM7 for the long haul I was able to move all excess /system space back into /data using terminal emulator and the fdisk command, but I followed a guide of some sort that is long lost now.
Everything is fantastic so far except one thing, there seems to be quite a lot of space reserved in the /system and /cache partitions, and I am not sure if I am able to re-partition this space back to /data or how exactly to do this.
right now /system is reading at 395.8 / 827.8 MB used, and /cache is at 68.4 / 551.7 MB. I would like to repartition 200 MB away from /system and 300-400 MB away from /cache, and put it back into /data. This will leave me some space to integrate or convert a few apps to system apps, and enough cache space to be safe (why does it need 550 MB to begin with?) and give back another half gig of storage that I paid so much to have.
I have three issues with this, one being that I can find almost no information on this topic directly mentioning the NExus 4, and any relatable information from other devices talking about device specific toolkits to do the job.
The only thread I found on XDA about this is below, and it only gave me a vague "this is not possible"
http://forum.xda-developers.com/showthread.php?t=2248400
The second issue is I do not recall the command switches/flags that go with the fdisk command, only that I had to use some things to set file permissions or remount the partition or some such (I know, i'm a noob, forgive me).
Lastly, I am rather confused by the multiple partitions of /data and /storage/emulated all showing a partition size of 13231.8 MB. Obviously they are all the same physical space, but I am afraid to mess with the partitions and break what I assume are a ton of symlinks that trick apps into believing there is an external SD card in play. Can any of you shed some light on this for me?
Click to expand...
Click to collapse
nexus4 doesn´t have a fix size for partitions, you can use the whole memory for everything... no need to re-partition anything
75markus said:
nexus4 doesn´t have a fix size for partitions, you can use the whole memory for everything... no need to re-partition anything
Click to expand...
Click to collapse
I'm not sure if you are misunderstanding or not reading my whole post, or if I am not understanding you or the situation I am posting about, so please don't take offense to this reply.
It appears to me that the /system partition is reserving 827 MB space for the ROM, and CM10.1 is only using 400 MB of it
It also appears that 552 MB is reserved for the /cache partition, and only 70 MB is being currently used.
This is ~900 MB of storage space that is reserved and unused. I would like to know if it is possible to reallocate ~500-600 MB of this back into the /data partition for user space.
Please explain to me how this space is part of the whole memory that can be used for anything.
After posting I have thought some more about it and decided to NOT mess with the partition sizes, mainly because I do not know what effect it would have if I were to flash another ROM in the future, which is almost a given when Key Lime Pie is released. However I would still like to understand what I have asked about in case I do want to do this in the future, and also just for the sake of expanding my knowledge.
I like this. The only "issue" is that if more space were ever to be reallocated to /system or /cache, it'd require wiping /data obviously. Small price to pay. 500MB isn't too small a chunk for 8GB users.
75markus said:
nexus4 doesn´t have a fix size for partitions, you can use the whole memory for everything... no need to re-partition anything
Click to expand...
Click to collapse
Actually it does. System data cache and boot, plus like 30 other ones, same as any other phone with no micro SD card
Sent from my Nexus 7 @1.60 GHz on Stock 4.2.2
I3ig Al said:
I'm not sure if you are misunderstanding or not reading my whole post, or if I am not understanding you or the situation I am posting about, so please don't take offense to this reply.
It appears to me that the /system partition is reserving 827 MB space for the ROM, and CM10.1 is only using 400 MB of it
It also appears that 552 MB is reserved for the /cache partition, and only 70 MB is being currently used.
This is ~900 MB of storage space that is reserved and unused. I would like to know if it is possible to reallocate ~500-600 MB of this back into the /data partition for user space.
Please explain to me how this space is part of the whole memory that can be used for anything.
After posting I have thought some more about it and decided to NOT mess with the partition sizes, mainly because I do not know what effect it would have if I were to flash another ROM in the future, which is almost a given when Key Lime Pie is released. However I would still like to understand what I have asked about in case I do want to do this in the future, and also just for the sake of expanding my knowledge.
Click to expand...
Click to collapse
i think N4 uses FUSE (Filesystem in Userspace) file system
noobdeagle said:
isnt this what they were saying was the reason for no SD card and use of MTP ?; basically if i recall correctly the nexus devices do not truly assign partitions instead there is a storage 'pool' that anything can use dynamically.
so i guess there is no partitions its just all 1 volume.
source: http://www.androidcentral.com/why-nexus-devices-have-no-sd-card
Click to expand...
Click to collapse
That is for the sdcard.
The other partitions such as /system still have fixed amounts of space allocated
Sent from my Nexus 4 using xda app-developers app