Is there a way to resize the MMC blocks? Right now /dev/block/mmcblk0p45 is /system and when running AOSP-based roms this partition is mostly empty (500 or so MB used of 2.2GB).
When flashing GPE-conversion this partition is resized (shrunk) to be smaller and thuss giving you more space on /data but making SENSE based roms unable to install unless you flash back the firmware.
So what part of firmware decides what size each block should be? And would it be possible to shrink /dev/block/mmcblk0p45 (ie, system) so that DATA gets more space, in some cases more then 1GB more.
No, sorry.
At the moment, it's only possible by using a RUU for your device.
Are you sure you have it the right way around? Isn't it 2.2GB used and 500M free? Is that what you get when you use df in terminal? For me it shows size as 2641M 2128M used and 513 free...
Just asking =o/
Related
Hi.. what is size defalut of system partition in NAND? i mean how big can be my rom to use it to nand all...
BTW i have usable froyo sense but still on ext4.. i want make it smaller to put it on NAND
sys/data - ext4/NAND.
maybe i will up it here 19-20/3 if it will be completed
Big thanks to jholtom
I believe it is 102 megabytes by default. (+/-5)
I usually for any sense rom except HTC tattoo 1.6 use atools and expand the system memory to about 168 megabytes
If you are going ext4 for /system and /data on NAND, just move the slider so that Data has the entire NAND drive (or leave about 16MB on /system), and if you use ext4 for /system, you'll have exactly 256MB for /system.
Need some reassurance...The Internal MB free is the space I need to worry about as the phone uses this as its memory. I have a few apps installed already, but was curious if I need to worry about the system Rom size.
Mine Reads:
System Rom: 367MB (9.94 MB free) (Kingsrom R 6.1)
Internal : 448 (323 MB free)
SD Card: 15.9 GB (10.2 GB Free)
Your running kings from it takes up slot of space if you want space flash another rom hehe
Sent from my PC36100 using XDA Premium App
The Internal space is what the Apps are installed to anyway correct?
Do a search for APS2SD.
It's very simple to partition your SDCard so you can run that.
Here's a good guide:
http://themikmik.com/forums/viewtopic.php?f=41&t=221
Unless you're adjusting your partition sizes (which I believe most people don't do), it really doesn't matter how big or small the ROM itself is, as long as it fits. It goes on a separate partition (/system), which is a fixed size. With few if any exceptions, files don't get written to /system during daily use of the ROM. Your apps and data get installed to /data, which is also a fixed size partition. Having space free in one doesn't help you with the other. So the extra data in /system just sits there unused.
There are ways you can adjust the partition size, but I think there are some downsides to doing that -- I don't know off the top of my head what, but there must be a reason it hasn't broadly caught on. You can also manually move apps into /system, but if they get updated you have to remember to move the updates back again.
Hey,
I've got Arconium ICS rom installed on my Xperia Arc. I'm running low on internal memory, and while trying to find more space on the device I've found this:
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock2 225.0M 1.1M 223.9M 1% /cache
So my question is - what is the cache partition used for on ICS? How big should it be? I found this in the description of some Nexus HD ICS rom:
Cache partition (/dev/block/mtdblock4) is only used by CWM.
Cache partition size is not important because the data partition (/dev/block/mtdblock5) is used as the cache space when running Android.
Click to expand...
Click to collapse
Of course partitions path varies, but the info seems to be relevant.
And a final question - fdisk doesn't seem to work (getting "fdisk: can't read from" error) - how do I go about changing partition table?
To my knowledge (based mostly on HTC phones), in normal use the cache partition is used for downloading apps prior to installing, and for downloading OTA updates (which is why it's so big).
If youre running custom ROMs then this partition doesnt need to be anything like this size, because youre not going to be installing OTA updates. HTC desire owners resize this down to as little as 5meg (though this seems low to me, IMO it should be at least as big as the biggest app youre ever likely to install, so i'd say 25-50 meg is a safer bet.
Now, i have no idea how CWM works, so if this is using the partition to perform installs or nandroid backups or something then your probably wouldnt want to make it much smaller.
There is also a lot of space which could be freed up on the system partition, particularly if youre using a stripped down ROM.
All of the above is all well and good, if there is a way of changing the Arc's partition table. I have no idea how this is done, or if it is even possible. So would love someone who knows about this stuff to respond. BUT: i very much doubt FDISK (you mean windows fdisk?!?!?) is the answer - at the very least i'd expect that you'd need a specially modified kernel in order to boot with a modified partition table. The fact that it fdisk with an error instead of giving it a try is probably the only reason your phone still boots.
Hello,
many users complain that since lollipop their system partition size doesn't reflect the actual system of the block device. Therefore, they can not install some extra in this partition( busybox, big gapps packages,etc.).
This is due to the system image size specified when building the rom:
One of the parameter of your system partition(which has been hardcoded in some config file, I.e. BoardConfig) is its size, but if the block device(i.e. the part of your internal storage that will be mounted for the system partition)'s size that is mounted is larger than the system partition's size than you will loose some space.
TWRP has included this feature into their recovery from 2.8.7.0 and onwards ! You don't need to get my flashable package if you got a newer version than this.
Fortunately resize2fs executable allows to modify an ext2,ext3,ext4 partition size:
linux man page said:
The resize2fs program will resize ext2, ext3, or ext4 file systems. It can be used to enlarge or shrink an unmounted file system located on device. If the filesystem is mounted, it can be used to expand the size of the mounted filesystem, assuming the kernel supports on-line resizing. (As of this writing, the Linux 2.6 kernel supports on-line resize for filesystems mounted using ext3 only.).
Click to expand...
Click to collapse
This package simply resizes your system size to match the size of your block device size.
It does not alter your partitions table just reclaim the unmounted space.
Instructions:
Boot on a twrp 2.8.x.y TWRP recovery
flash the package
Download :
https://drive.google.com/file/d/0B9kxrJw-dzUmNG12QkdaU3R4Ujg/view
Credits :
@m11kkaa from whom I took the idea
Lets see if I understood this correctly. Currently in Lollipop the system partition is smaller than the block where the partition resides? And if the partition size doesn't match the block size, you will loose the remaining space on the block? The remaining space on the block is not available to any other partition?
That's correct. Your system partition is mounted with am 800 mb allocated space. Depending on your ROM ypou might loose some space.
Here I got 437 mb of free space .
Sent from my nexus 10
Tried it and my system partition went from 643.7MB to 787.9MB in size on Lollipopalooza. That definetily helps with installing gapps as last time I had to leave off quite a few apps to get it to fit. So just to make sure, this extra space isn't taken from any other partition? It just made the system partition use the unallocated free space on the block?
Which app do you use to see partition sizes? How can I see what it is vs what it should be? Thanks.
CazeW said:
Tried it and my system partition went from 643.7MB to 787.9MB in size on Lollipopalooza. That definetily helps with installing gapps as last time I had to leave off quite a few apps to get it to fit. So just to make sure, this extra space isn't taken from any other partition? It just made the system partition use the unallocated free space on the block?
Click to expand...
Click to collapse
Exactly.it corrects some internal ext4's variables that represents the size of fs to match the block's
lepa71 said:
Which app do you use to see partition sizes? How can I see what it is vs what it should be? Thanks.
Click to expand...
Click to collapse
There are plenty out there . I use fx embedded filesystem's analysis
Excellent! I have one more question. As we know, modifying the system partition means that otas will fail. So if before I had to uninstall say Play Movies to make room for busybox, then I'd have had to reinstall it if I wanted to flash an OTA. With this method, the md5 signature of system isn't altered, and therefore otas wont fail, right?
You are on aosp ?
Khaon said:
You are on aosp ?
Click to expand...
Click to collapse
Stock factory image + root, uninstalled Play Movies to make room for busybox
Do I need to do anything?
You used my mod right ?
Best way is either issue
df in a terminal console or install this app
https://play.google.com/store/apps/details?id=com.cls.partition
It will display the actual filesystem size .disk info display the size of your ssd
Sent from my nexus 10.
Khaon said:
You used my mod right ?
Best way is either issue
df in a terminal console or install this app
https://play.google.com/store/apps/details?id=com.cls.partition
It will display the actual filesystem size .disk info display the size of your ssd
Sent from my nexus 10.
Click to expand...
Click to collapse
Thank you very much for your mod.
I want to try it but I'm a little bit afraid. Do I lose any data? Will this affect the installation of other ROMs? I'm on stock now but I want to try some custom ROMs to decide. Do I have to use your mod every time I install a new ROM?
Thanks in advance!
You won't loose any data it will adjust the size of ext4 fs to the actual physical size of your partition.
Flashing a new lollipop ROM flashes a new system image which specifies the image size.
Our device system image size is defined here https://github.com/CyanogenMod/android_device_samsung_manta/blob/cm-12.0/BoardConfig.mk#L64
685768704 is 654 megabyte but your mmcblk0p8 partition mounted on /system is 800 mb.
Until this is fixed. Will open a ticket to increase this value but there are maybe few reason google chose 654.
And yes you must reflash it each to flash
Sent from my nexus 10.
If you replying to my question then I didn't do anything. I'm asking I should do it.
Is this only for CM based roms?
Thanks
Khaon said:
You used my mod right ?
Best way is either issue
df in a terminal console or install this app
https://play.google.com/store/apps/details?id=com.cls.partition
It will display the actual filesystem size .disk info display the size of your ssd
Sent from my nexus 10.
Click to expand...
Click to collapse
lepa71 said:
If you replying to my question then I didn't do anything. I'm asking I should do it.
Is this only for CM based roms?
Thanks
Click to expand...
Click to collapse
any roms
Khaon said:
any roms
Click to expand...
Click to collapse
I installed the app you said, but I didn't see any unclaimed space. Is your mod for stock ROM as well? I seem to have 644MB of space on the /system partition.
Sent from my Nexus 10 using Tapatalk
_Raziel666 said:
I installed the app you said, but I didn't see any unclaimed space. Is your mod for stock ROM as well? I seem to have 644MB of space on the /system partition.
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
Well the maximum space you system partition can get is 800mb. The system of je partition number 8.
Thus you are looking space.
The resizes just fixes that
Read this post.
http://forum.xda-developers.com/showthread.php?p=59016220
Sent from my Xiaomi MI2s.
So mine shows 800 for system partition. Does this mean I don't have to do anything? Thanks
Khaon said:
You used my mod right ?
Best way is either issue
df in a terminal console or install this app
https://play.google.com/store/apps/details?id=com.cls.partition
It will display the actual filesystem size .disk info display the size of your ssd
Sent from my nexus 10.
Click to expand...
Click to collapse
Don't use disk info but rather one of tje two over here.
Sent from my Xiaomi MI2s.
lepa71 said:
So mine shows 800 for system partition. Does this mean I don't have to do anything? Thanks
Click to expand...
Click to collapse
Yes, if your system partition is already 800MB in size then you're already using the whole block.
I have a brand new G3 (D852) with Koodo that I just got 2 days ago. I've rooted, installed TWRP and flashed a few AOSP roms. Not a fan of any manufacturer UI, even though LG's is very minimal, so AOSP it is. I noticed that my system partition has more than 1GB of free space after everything is flashed and good to go. I also noticed that the latest TWRP (2.8.7.0) has a resize partition option inside the Wipe section. What I want to know is, how can I use this to resize the system and data partitions so that 1GB+ isn't being wasted and unused. I'd really like to get that 1GB+ added to my data partition for apps.
I've tried using it. The only time it didn't spit out an error was after I wiped the system partition. It succeeded in "resizing" it after that, but it didn't change anything. The system partition remained the same size.
ToYeD said:
I have a brand new G3 (D852) with Koodo that I just got 2 days ago. I've rooted, installed TWRP and flashed a few AOSP roms. Not a fan of any manufacturer UI, even though LG's is very minimal, so AOSP it is. I noticed that my system partition has more than 1GB of free space after everything is flashed and good to go. I also noticed that the latest TWRP (2.8.7.0) has a resize partition option inside the Wipe section. What I want to know is, how can I use this to resize the system and data partitions so that 1GB+ isn't being wasted and unused. I'd really like to get that 1GB+ added to my data partition for apps.
I've tried using it. The only time it didn't spit out an error was after I wiped the system partition. It succeeded in "resizing" it after that, but it didn't change anything. The system partition remained the same size.
Click to expand...
Click to collapse
This it why the option is there:
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
jeffrey268 said:
This it why the option is there:
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
Click to expand...
Click to collapse
Thank you for the reply
If I understand you correctly, the feature's original intent is to resize /data partitions in the event the rom/system image treats a larger storage capacity device as a lower capacity one, ie. 64GB device is treated like 32GB so /data will only reflect 32GB minus (system image install size), wasting 32GB and leaving it inaccessible to the user.
However, it also seemed like you were saying I also could use it to resize my /system partition to a smaller size so CM12.1 (with it's ~900MB install size after Full TK-Gapps) will only leave ~50MB to ~100MB on /system instead of ~1.5GB. However, the question remains. How do I do this and can I reallocate the ~1.5GB to the /data partition for apps and internal storage? If this can't be done then I see no point in resizing /system to begin with as it will still be inaccessible to me as the user.
ToYeD said:
Thank you for the reply
If I understand you correctly, the feature's original intent is to resize /data partitions in the event the rom/system image treats a larger storage capacity device as a lower capacity one, ie. 64GB device is treated like 32GB so /data will only reflect 32GB minus (system image install size), wasting 32GB and leaving it inaccessible to the user.
However, it also seemed like you were saying I also could use it to resize my /system partition to a smaller size so CM12.1 (with it's ~900MB install size after Full TK-Gapps) will only leave ~50MB to ~100MB on /system instead of ~1.5GB. However, the question remains. How do I do this and can I reallocate the ~1.5GB to the /data partition for apps and internal storage? If this can't be done then I see no point in resizing /system to begin with as it will still be inaccessible to me as the user.
Click to expand...
Click to collapse
I read a few things online and it seems you need aan unlocked bootlader, the G3 bootloader is not unlockable, so you are probily out of luck maby you can ask in the Q&A thread of the rom you are using.