Ok, now im wondering, is the cache directory in system supposed to be connected to the cache partition that gets flashed in some roms?
For example, say i look at my root dir on my phone, i go to data and it lists the used and free which combined, is the auto sized amount of my data partition, if i go to system,the used and free combined is tha size of teh system partition i have (i used cwm and in my case its 410M) now i flashed a cache partition (of 10M) so i had assumed that the cache dir in root was linked to my cache partition, so the amount used/free combined would be 10M, but instead its the same size as of my data partition.. so i know that its using that partition instead..
is it supposed to be like that?
what use is the cache partition?
also, does anyone think there would be a benefit if the system partition was in ext3 format instead of yaffs? i know that most oem roms come with the system partition set in ext3 format, would that ever be possible with magldr?
thanks.
Anybody got 2 cents they can throw in?
cmon, any answer at all would be nice from anyone..
It looks normal to me. Most sense builds i saw here, dont use the cache partition, instead the data partition is used. So basically you could flash a 1mb cache partition and it will work and you get some more space for system.
btw, on nand there is allways yaffs used for system, not ext(X).
Use of cache partition are depended on the Android Builds. Most builds do not use cache partition at all. /cache is redirected to /data/cachemnt on the userdata partition. However cache partition is required for CWM. It will compliant if cache partition is missing.
ext2/3/4 are not suitable for NAND Flash. YAFFS2 is develop for and more suitable for NAND Fash Device. However, there are ways to use ext2/3/4 though other methods. (one of them being loop device mount) and for Read Only. Each method has its pros and cons. it really depend if the benefits outweights its drawbacks.
greg17477 said:
It looks normal to me. Most sense builds i saw here, dont use the cache partition, instead the data partition is used. So basically you could flash a 1mb cache partition and it will work and you get some more space for system.
btw, on nand there is allways yaffs used for system, not ext(X).
Click to expand...
Click to collapse
hey first, THANK YOU for commenting. ok, thats interesting, i have always seen it suggested to use a 10 -40 mb cache partition, ive also heard that market can have some weird effects such as not being able to download if the cache partition was too small.. thats why i assumed that it was used by the system in some way
nightcraw said:
Use of cache partition are depended on the Android Builds. Most builds do not use cache partition at all. /cache is redirected to /data/cachemnt on the userdata partition. However cache partition is required for CWM. It will compliant if cache partition is missing.
ext2/3/4 are not suitable for NAND Flash. YAFFS2 is develop for and more suitable for NAND Fash Device. However, there are ways to use ext2/3/4 though other methods. (one of them being loop device mount). Each method has its pros and cons. it really depend if the benefits outweights its drawbacks.
Click to expand...
Click to collapse
i asked that since i have seen most of the oem roms using ext3 and assumed it offered some benefit speed-wise. all phones use nand of the same type yeah? so whats the benefit of using ext3 when yaffs2 preforms much better on it?
Hello everyone,
is it possible to partition the MAIN memory (I mean the phone memory, not sd card) to fit the build I'm using perfectly? Like setting best size for boot partition, for system partition etc..., in order to have more space available for data internal partition?
I've found http://www.enfeuman.com/2011/06/01/how-to-fix-abnormal-internal-storage-space-on-htc-hd2/
but I really couldn't find an option in CMR to partition main memory.
If this is possible, can anyone tell me how? (I'd like it for my NAND ACA GB2.3.7 build)
And is it necessary to wipe the whole phone and do (flash) everything over again?
matoflash said:
Hello everyone,
is it possible to partition the MAIN memory (I mean the phone memory, not sd card) to fit the build I'm using perfectly? Like setting best size for boot partition, for system partition etc..., in order to have more space available for data internal partition?
I've found http://www.enfeuman.com/2011/06/01/how-to-fix-abnormal-internal-storage-space-on-htc-hd2/
but I really couldn't find an option in CMR to partition main memory.
If this is possible, can anyone tell me how? (I'd like it for my NAND ACA GB2.3.7 build)
And is it necessary to wipe the whole phone and do (flash) everything over again?
Click to expand...
Click to collapse
Wipe data
to set the partition sizes, try clk 1.6 and use fastboot commands to resize the partitions.
When you do this, you will have to re flash the rom.
Thanks, ill try that.
-----------------------------------
HTC HD2
ACA GB 237 CM7
kernel 2.6.32.15
NAND Android ROCKS!
There is a huge thread on how to move data from the System partition to the SD, but I think it is still not very clear (at least to me) why the system partition gets so full when installing new modern ROMs on the HD2. Every installation guide starts with partitioning in clk or magldr. For instance, the HexusHD2 ICS ROM has to have at least 170mb system partition. I made it 300 just to be sure and android says I have a total of 105mb internal storage. (I barely have place to install new apps, since android takes around 75mb of those 105mb)
My question is what is what is the relation between the system partitioning in clk and the size I get after the ROM is flashed. Will i have more storage if I partition clk to a greater figure- 450mb? ...or will it be vice versa?
thanks
archibrid said:
There is a huge thread on how to move data from the System partition to the SD, but I think it is still not very clear (at least to me) why the system partition gets so full when installing new modern ROMs on the HD2. Every installation guide starts with partitioning in clk or magldr. For instance, the HexusHD2 ICS ROM has to have at least 170mb system partition. I made it 300 just to be sure and android says I have a total of 105mb internal storage. (I barely have place to install new apps, since android takes around 75mb of those 105mb)
My question is what is what is the relation between the system partitioning in clk and the size I get after the ROM is flashed. Will i have more storage if I partition clk to a greater figure- 450mb? ...or will it be vice versa?
thanks
Click to expand...
Click to collapse
You've got it completely the wrong way around, the /system partition is where the actual OS is installed, so the smaller the /system partition, the greater the internal storage which remains, which is thus usable for apps.
Smaller partition = more storage.
Any way to add more space in system partiton
Because i dont know why its FULL
I am just curios is it posible to repartition out NAND memory to make our system smaller and our data bigger because custom roms for our phone are lot smaller in size then our factory rom.So we have 1gb trapped in system partition so is it posible to partition it like that so we transfer that gb to data?