Is there a way to change the size of the partitions?
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock3 250.0M 96.4M 153.6M 39% /system
/dev/block/mtdblock5 147.6M 127.0M 20.7M 86% /data
Wouldn't it make more sense if system was smaller and data bigger?
Yes it would make Sense, on the HTC-Dream it's already possible. I think we should ask Firerat if he could make his Patch compatible to the Desire. In his Post he wrote that it would be universal... but i'm to anxious to Brick it...
Edit. I've asked him, hope there would be an positive answer....
http://forum.xda-developers.com/showthread.php?t=717874&page=60
Related
I use the barebone, stripped down roms and have more than 120MB free space on /system partition. It would be nice to change the size and free space for more apps installs (and skip the a2sd).
Is it possible?
Somebody said it's done in the kernel.... A LONG TIME AGO. Nobody seems to want or can.
eViL D: said:
Somebody said it's done in the kernel.... A LONG TIME AGO. Nobody seems to want or can.
Click to expand...
Click to collapse
Its a pity, would be a nice way to solve desires apps storage problems
htc have taken more space from data and cache to put their apps (and ****)
desire
/dev/block/mtdblock3 250.0M 97.6M 152.4M 39% /system
/dev/block/mtdblock5 147.6M 116.3M 31.3M 79% /data
/dev/block/mtdblock4 40.0M 33.3M 6.7M 83% /cache
N1
/dev/block/mtdblock3 145.0M 109.5M 35.5M 76% /system
/dev/block/mtdblock5 196.3M 166.0M 30.3M 85% /data
/dev/block/mtdblock4 95.0M 38.2M 56.8M 40% /cache
Kali- said:
htc have taken more space from data and cache to put their apps (and ****)
desire
/dev/block/mtdblock3 250.0M 97.6M 152.4M 39% /system
/dev/block/mtdblock5 147.6M 116.3M 31.3M 79% /data
/dev/block/mtdblock4 40.0M 33.3M 6.7M 83% /cache
N1
/dev/block/mtdblock3 145.0M 109.5M 35.5M 76% /system
/dev/block/mtdblock5 196.3M 166.0M 30.3M 85% /data
/dev/block/mtdblock4 95.0M 38.2M 56.8M 40% /cache
Click to expand...
Click to collapse
Yeah, alot of wasted space, even with a fully odexed sense rom.
Wow I'm using Evil's barebone rom and just checked my free space. I got 150 MB free in /system just doing nothing! What a shame we can't repartition the internal memory.
i believe desire has 512 Mo of rom
desire
/dev/block/mtdblock3 250.0M 97.6M 152.4M 39% /system
/dev/block/mtdblock5 147.6M 116.3M 31.3M 79% /data
/dev/block/mtdblock4 40.0M 33.3M 6.7M 83% /cache
250+147+40<512
why this difference ?
radio recovery fastboot
SENSAATION said:
i believe desire has 512 Mo of rom
desire
/dev/block/mtdblock3 250.0M 97.6M 152.4M 39% /system
/dev/block/mtdblock5 147.6M 116.3M 31.3M 79% /data
/dev/block/mtdblock4 40.0M 33.3M 6.7M 83% /cache
250+147+40<512
why this difference ?
Click to expand...
Click to collapse
The difference in case of the nexus one is, that you can use 196.3MB for "your" stuff (not absolutely true - i know) instead of 147,6MB.
Currently my partitions look like this:
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 206.5M 0 206.5M 0% /dev
/dev/block/mtdblock4 40.0M 8.5M 31.5M 21% /cache
/dev/block/mtdblock3 250.0M 120.9M 129.1M 48% /system
/dev/block/mtdblock5 147.6M 70.7M 76.9M 48% /data
But when I next boot, /data/dalvik-cache will balloon to ~60MB so I'll be stuck with 15MB left of my data partition.
I was thinking, if I could take 100MB or so from my system partition and add it to my data partition, this would make everything much more awesome. I'm prepared to reformat my phone (currently using CM7-RC3) to do this, but have no idea how I'd go about it.
Also it'd be great if my /system partition mounted RW on boot (I've got Alpharev, etc)
Have you visited this?
http://forum.xda-developers.com/showthread.php?t=806321 <<< Custom MTD partitions
I was just wondering why there is a new version
Sent From My HTC sensation (desire with rcmix s )
@ topic
same question here I know the sizes of the partitions changes a bit but - why?
Sent From My HTC sensation (desire with rcmix s )
Click to expand...
Click to collapse
RCMIX S is an port from Desire S not from Sensation ...
Because the actual version got updated so if you use an RUU the hboot won't be overwritten by the one in the RUU. Secondly, Oxygen and CM7 rom devs were finding it hard to keep to the same amount of /system space available. As software updates, the size of it grows. Eventually, your going to have to change the size of the partition so you can fit the new updates on.
Meaple said:
Because the actual version got updated so if you use an RUU the hboot won't be overwritten by the one in the RUU. Secondly, Oxygen and CM7 rom devs were finding it hard to keep to the same amount of /system space available. As software updates, the size of it grows. Eventually, your going to have to change the size of the partition so you can fit the new updates on.
Click to expand...
Click to collapse
Thanks for that
Sent From My HTC sensation (desire with rcmix s )
Are CM7 ROMs also run on CM7r2?
Yes, since the the CM7r2 hboot tables are bigger for /system.
Don't think I'll be using the newer hboot myself...
Code:
# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 202.8M 32.0K 202.7M 0% /dev
tmpfs 202.8M 0 202.8M 0% /mnt/asec
tmpfs 202.8M 0 202.8M 0% /mnt/obb
/dev/block/mtdblock3 130.0M 115.2M 14.8M 89% /system
/dev/block/mtdblock5 302.6M 153.5M 149.1M 51% /data
/dev/block/mtdblock4 5.0M 2.1M 2.9M 42% /cache
/dev/block/mtdblock5 302.6M 153.5M 149.1M 51% /cache/download
/dev/block/vold/179:1 7.6G 5.4G 2.2G 71% /mnt/sdcard
Plenty of room Although this is on my own AOSP-built CM7-based affair...
I'll probably switch soon since the newer roms will ne using it (sense)
Sent From My HTC sensation (desire with rcmix s )
PaulW21781 said:
Don't think I'll be using the newer hboot myself...
Code:
# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 202.8M 32.0K 202.7M 0% /dev
tmpfs 202.8M 0 202.8M 0% /mnt/asec
tmpfs 202.8M 0 202.8M 0% /mnt/obb
/dev/block/mtdblock3 130.0M 115.2M 14.8M 89% /system
/dev/block/mtdblock5 302.6M 153.5M 149.1M 51% /data
/dev/block/mtdblock4 5.0M 2.1M 2.9M 42% /cache
/dev/block/mtdblock5 302.6M 153.5M 149.1M 51% /cache/download
/dev/block/vold/179:1 7.6G 5.4G 2.2G 71% /mnt/sdcard
Plenty of room Although this is on my own AOSP-built CM7-based affair...
Click to expand...
Click to collapse
The new Hboot CM7r2 was made for original CM7 beacuse the ROM is a bit larger.
You are on some kind of tweaked(selfmade) version of CM7 so you have a lot of space remaining.
Maybe we will have a ODEXed cm7, else i don't see why they need 145 MB on /system, clearly a over kill.
As I explained software gets bigger in size and it gets harder to shrink it down when you have more data to deal with
Swyped...
Too little space.
It's quite annoying, but something we have to live with. The ROM devs still do a great job, though, considering they try to satisfy as many users as possible.
You can bung on r2. Just as long as you don't go over the r2's max /data capacity you should be fine. You might have to reflash the rom and wipe cache and dalvik, but not do a full wipe.
i've got CM7 hboot currently installed and i'm trying to flash r2 over it but it won't allow me to flash it in fastboot, it just says stuck on "sending..." then once I disconnect the USB, it says "error, too many links".
I've tried flashing it the alternative way via PB99IMG but it comes up with an invalid CID error.
Any reasons why it might be doing this, I flashed the original CM7 hboot (and oxygen hboot before that) with out any problems
p5x said:
i've got CM7 hboot currently installed and i'm trying to flash r2 over it but it won't allow me to flash it in fastboot, it just says stuck on "sending..." then once I disconnect the USB, it says "error, too many links".
I've tried flashing it the alternative way via PB99IMG but it comes up with an invalid CID error.
Any reasons why it might be doing this, I flashed the original CM7 hboot (and oxygen hboot before that) with out any problems
Click to expand...
Click to collapse
Maybe faulty download, try downloading again
tried that, checked MD5 as well
sorted it, seems it was a dodgy usb cable.
thanks
Apologies if this has already been asked elsewhere, but I got no search results on it...
I was checking partition sizes using Root Explorer yesterday, and the following is what I was seeing:
Data: 380MB, 65.11MB free
System: 312.5MB, 83.02MB free
Cache: 225MB, 1.31MB used
This works out at around 1GB of internal storage, and on my phone, over 300MB wasted between system and cache partitions. Is the large cache partition there for downloading all that extra game data, because it seems needlessly large otherwise?
The big question though - is there any way to repartition the internal storage?
Yes there is but you would need some way to instruct s1 boot to use the new partition table, even with an unlocked bootloader we can't do this. Also in the 2.3.4 update /cache/ has been reduced to 100mb.
Sent from my R800i using Tapatalk
AndroHero said:
Yes there is but you would need some way to instruct s1 boot to use the new partition table, even with an unlocked bootloader we can't do this. Also in the 2.3.4 update /cache/ has been reduced to 100mb.
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
Thanks So if I flash any of the 2.3.4 ROMs, I'll have an extra 100MB on my data partition? I'd be happy enough with that...
As for instructing s1 boot to use the new partition table, do you mean there's no way to do this, full stop, or no way to do it YET? Because obviously the 2.3.4 ROMs can do it, so just wondering if it's something the devs may be able to figure out and do in future...
drunkenfcuk said:
Thanks So if I flash any of the 2.3.4 ROMs, I'll have an extra 100MB on my data partition? I'd be happy enough with that...
As for instructing s1 boot to use the new partition table, do you mean there's no way to do this, full stop, or no way to do it YET? Because obviously the 2.3.4 ROMs can do it, so just wondering if it's something the devs may be able to figure out and do in future...
Click to expand...
Click to collapse
Thats the thing, it's just disapeared this other 100mb, they didnt add it to /data/ or /system/ just hid it on a seperate partiton
Afaik there is no way full stop, although we have unlocked bootloaders, we dont have s-off like HTC devices, were unable to modify bootloader Sony on the other hand add diffrent bootloader versions to there stock roms, so it's the latest bootloader that comes with the 2.3.4 roms that has repartitioned /cache/
If you want to free up some space, you may want to try link2sd on the market, it works simlar to apps2sd+ i have over 300 apps on my phone and still have 235mb free thanks to link2sd
https://market.android.com/details?id=com.buak.Link2SD&hl=en
AndroHero said:
Thats the thing, it's just disapeared this other 100mb, they didnt add it to /data/ or /system/ just hid it on a seperate partiton
Afaik there is no way full stop, although we have unlocked bootloaders, we dont have s-off like HTC devices, were unable to modify bootloader Sony on the other hand add diffrent bootloader versions to there stock roms, so it's the latest bootloader that comes with the 2.3.4 roms that has repartitioned /cache/
If you want to free up some space, you may want to try link2sd on the market, it works simlar to apps2sd+ i have over 300 apps on my phone and still have 235mb free thanks to link2sd
https://market.android.com/details?id=com.buak.Link2SD&hl=en
Click to expand...
Click to collapse
maybe they added it into an ext recovery, so maybe we could use CWM with 2.3.4?
AndroHero said:
Thats the thing, it's just disapeared this other 100mb, they didnt add it to /data/ or /system/ just hid it on a seperate partiton
Afaik there is no way full stop, although we have unlocked bootloaders, we dont have s-off like HTC devices, were unable to modify bootloader Sony on the other hand add diffrent bootloader versions to there stock roms, so it's the latest bootloader that comes with the 2.3.4 roms that has repartitioned /cache/
If you want to free up some space, you may want to try link2sd on the market, it works simlar to apps2sd+ i have over 300 apps on my phone and still have 235mb free thanks to link2sd
https://market.android.com/details?id=com.buak.Link2SD&hl=en
Click to expand...
Click to collapse
Thanks, I'll take a look
Do you have 2.3.4? You can use ADB to list the partitions, so you might be able to see where that 100MB has gone...
adb shell
df -h
I get the following:
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 199.0M 76.0K 198.9M 0% /dev
tmpfs 199.0M 0 199.0M 0% /mnt/asec
tmpfs 199.0M 0 199.0M 0% /mnt/obb
/dev/block/mtdblock0 312.5M 190.8M 121.7M 61% /system
/dev/block/mtdblock3 380.0M 296.4M 83.6M 78% /data
/dev/block/mtdblock2 225.0M 1.3M 223.7M 1% /cache
/dev/block/mtdblock1 10.0M 1.5M 8.5M 15% /data/idd
Or just 'df -h' from a terminal window on your phone...
Code:
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 177.3M 44.0K 177.3M 0% /dev
tmpfs 177.3M 0 177.3M 0% /mnt/asec
tmpfs 177.3M 0 177.3M 0% /mnt/obb
/dev/block/mtdblock0 312.5M 137.4M 175.1M 44% /system
/dev/block/mtdblock2 380.0M 123.3M 256.7M 32% /data
/dev/block/mtdblock1 101.5M 18.0M 83.5M 18% /cache
/dev/block/vold/179:1
1.9G 1.1G 773.4M 59% /mnt/sdcard
/dev/block/vold/179:1
1.9G 1.1G 773.4M 59% /mnt/secure/asec
/dev/block/dm-0 5.1M 3.6M 1.4M 71% /mnt/asec/com.mojang.miecraftpe.demo-1
This is from my phone running the latest CM.
I cant find the 100 MB here
Azeazezar said:
Code:
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 177.3M 44.0K 177.3M 0% /dev
tmpfs 177.3M 0 177.3M 0% /mnt/asec
tmpfs 177.3M 0 177.3M 0% /mnt/obb
/dev/block/mtdblock0 312.5M 137.4M 175.1M 44% /system
/dev/block/mtdblock2 380.0M 123.3M 256.7M 32% /data
/dev/block/mtdblock1 101.5M 18.0M 83.5M 18% /cache
/dev/block/vold/179:1
1.9G 1.1G 773.4M 59% /mnt/sdcard
/dev/block/vold/179:1
1.9G 1.1G 773.4M 59% /mnt/secure/asec
/dev/block/dm-0 5.1M 3.6M 1.4M 71% /mnt/asec/com.mojang.miecraftpe.demo-1
This is from my phone running the latest CM.
I cant find the 100 MB here
Click to expand...
Click to collapse
I suppose if it's hidden from Android, then ADB wouldn't see it anyway. And it's actually more than 100MB. More like 123.5MB. Would love to know where it's gone!
S-on, unlocked users,cannot modify partition table, but can write anything to this partitons, or maybe it is just my way of thinking ;p Correct me if im wrong.
Partitions on my WFS are:
$ df -h
size used available mounted
/dev/block/mtdblock3 260M 137M 122,2M /system
/dev/block/mtdblock5 150M 127M 23M /data
/dev/block/mtdblock4 35M 2,3M 32,7M /cache
/dev/block/mtdblock5 150M 127M 23M /cache/download
The Question is:
Can /dev/block/mtdblock3 be mounted as /data ?
And /dev/block/mtdblock5 be mounted as /system ?
Can boot.img be patched to boot from /dev/block/mtdblock5 ?
This would give 150M for CM7 which is more then enough ,and 260M for data !
xys007 said:
S-on, unlocked users,cannot modify partition table, but can write anything to this partitons, or maybe it is just my way of thinking ;p Correct me if im wrong.
Partitions on my WFS are:
$ df -h
size used available mounted
/dev/block/mtdblock3 260M 137M 122,2M /system
/dev/block/mtdblock5 150M 127M 23M /data
/dev/block/mtdblock4 35M 2,3M 32,7M /cache
/dev/block/mtdblock5 150M 127M 23M /cache/download
The Question is:
Can /dev/block/mtdblock3 be mounted as /data ?
And /dev/block/mtdblock5 be mounted as /system ?
Can boot.img be patched to boot from /dev/block/mtdblock5 ?
This would give 150M for CM7 which is more then enough ,and 260M for data !
Click to expand...
Click to collapse
I don't think its possible. Even if you mount /data as /system and /system as /data it might result in force close of these apps
You'd need s-off to play with internal partitions.