i have a buzz wildfire with alpharevx HBOOT
is possible to resize partition with tools like this?
[HOW-TO] Easily resize system + data partitions!
http://forum.xda-developers.com/showthread.php?t=1171531
actually the /system partition is 250 mb and the nightly cyanogen mod use only circa 120 mb
and the /data is only 175mb
and /cache 40 mb!
on alpharev.nl there is the sample configuration of partiotions for cm7 for bravo devices
/system /cache /data
145 mb 5 mb 287 mb
i'm interested on a similar configuration for my wildfire
anyone can help me?
http://forum.xda-developers.com/showthread.php?t=1233340
Keep cache at 10MB, and remember, only keep a 145MB /system partition if you are using AOSP ROMs like CM7. It won't work on stock / sense based ROMs. (You are using CM7, but, just thought I would let you know)
thanks it is my solution!
you could also make an sd-ext partition on your SD card and move your apps completely to your SD-card. That way I now only use 35 mb of my internal memory for app data, all the apps itself are stored fully on SD card. Works great
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.
Hi all,
I'm coming from LeeDroid 3.0.7 with A2SD, and I would like to install a more modern rom perhaps with Sense 3.0.
I read the requirements for the latest InsertCoin with Sense 3.0
Requirements:
A2SD CM7 HBOOT - cm7 hboot from alpharev.nl - the one with 130 mB for /system
- 1 gB ext2/3/4 partition
A2SD+ STOCK HBOOT - stock hboot - the one with 250 mB for /system
- 1 gB ext2/3/4 partition
Click to expand...
Click to collapse
and I don't really understand them. Can anyone help me out? Does it mean I can have a Stock HBOOT (which mine is) but I have to have 250MB /system partition and a 1GB /ext3 partition?
At present according to system info app I have : 457MB A2SD storage, 148MB Internal storage, 250MB System storage, 40MB system cache, 405MB memory. Does this mean I need to increase the ext3 partition from 512MB to 1GB, and if so is that done by clockworkmod?
thanks, sorry for the long post.
With the stock hboot you already have 250MB /system. You can use Clockwork recovery (v3+) otherwise you would need to use a partition manager. Please bare in mind that to increase your ext partition, it will completely wipe your SD card so make sure you back it up.
thanks for the quick reply. If I manage to increase the ext3 partition to 1GB, am I right in thinking I need CM 3+ anyway in order to flash the rom?
cable_guy said:
thanks for the quick reply. If I manage to increase the ext3 partition to 1GB, am I right in thinking I need CM 3+ anyway in order to flash the rom?
Click to expand...
Click to collapse
No.. You dont need CM 3+ to flash the ROM. Meaple meant that u need CM 3+ to partition the SD card to 1 GB
hello, i am a newbie here. i just installed cooldroid v3 bravo in my HTC Desire. as told in this topic "http://forum.xda-developers.com/showthread.php?t=1279016"
after the ist reboot the installation was successfully done and i can see my home screen, the rom is cool and very fast but when i checked my internal memory it was shown as 130mb. how can i increase it to 1GB atleast? i have a made an ext4 partition. do i need any script? if it then what? please help me.
tanmoyrock said:
hello, i am a newbie here. i just installed cooldroid v3 bravo in my HTC Desire. as told in this topic "http://forum.xda-developers.com/showthread.php?t=1279016"
after the ist reboot the installation was successfully done and i can see my home screen, the rom is cool and very fast but when i checked my internal memory it was shown as 130mb. how can i increase it to 1GB atleast? i have a made an ext4 partition. do i need any script? if it then what? please help me.
Click to expand...
Click to collapse
The A2SD script should still be working as long as you created the partition correctly with 4EXT recovery or gparted. The rom has a built in script which will automatically move the apps and dalvik to sd-ext. Keep the apps on internal to trick the apps to sd-ext, do not 'move to SD'.
You won't see your internal memory as 'internal + sd-ext', but you will have plenty more space for apps. Use an app like 'diskusage' to browse all your partitions to see if sd-ext is working properly.
You are also still on stock hboot. s-off if you haven't already, and change to data++ hboot (search for guides). This will increase your actual internal memory slightly allowing for more space:
DATA++ Hboot 180MB System, 5MB Cache, 252MB Data. <---- a bit mroe space
STOCK Hboot 250MB System, 40MB Cache, 147MB Data. <---- what you have currently (stock hboot is wasteful, small internal memory /data partition)
Hi,
I've had to bring my Desire out of retirement until the end of my contract.
I am currently running Cyanogen Mod 10.0.0 but I am down to little space and apps don't update and I can't add new ones.
I have an SD card with 1 GB ext3 storage on it.
Which is the best configuration/ROM to allow me to have enough space to download all the apps I want without significant lag please?
Cheers
Do you understand current configuration first to understand why you're low on space?
- Have you run the A2SD commands from terminal emulator i.e. moved apps and dalvik to sd-ext?
- Is your /data (internal memory) partition full, or is it your 1GB sd-ext? Could you create a bigger partition?
- Check your /data partition with an app like 'DiskUsage', you may have some updated system apps like Play Store on /data which you could move back to /system.
If you have genuinely run out of space on that ROM, the limiting issue is stock hboot which I assume you are running. Even with apps and dalvik moved to sd-ext, you only have 147MB space for app data which can still run out.
Switch to a different hboot (requires s-off) with smaller system, and a ROM which moves apps and dalvik to sd-ext. I recommend one of Mildwild's, MW10 based on redux will fit onto OxygenR2 hboot with 332MB /data partition for instance.
I also recommend to repartition your sdcard with max 2GB ext4 partition if you have enough spare sd space. ext4 is also slightly faster than ext3.
eddiehk6 said:
Do you understand current configuration first to understand why you're low on space?
- Have you run the A2SD commands from terminal emulator i.e. moved apps and dalvik to sd-ext?
- Is your /data (internal memory) partition full, or is it your 1GB sd-ext? Could you create a bigger partition?
- Check your /data partition with an app like 'DiskUsage', you may have some updated system apps like Play Store on /data which you could move back to /system.
If you have genuinely run out of space on that ROM, the limiting issue is stock hboot which I assume you are running. Even with apps and dalvik moved to sd-ext, you only have 147MB space for app data which can still run out.
Switch to a different hboot (requires s-off) with smaller system, and a ROM which moves apps and dalvik to sd-ext. I recommend one of Mildwild's, MW10 based on redux will fit onto OxygenR2 hboot with 332MB /data partition for instance.
I also recommend to repartition your sdcard with max 2GB ext4 partition if you have enough spare sd space. ext4 is also slightly faster than ext3.
Click to expand...
Click to collapse
Thanks,
I'll try to deal with everything.
apps and dalvik have been moved using terminal emulator and yes, it's the 147MB that is the issue, not the ext3.
I have s-on
So if I have the s-off can I incorporate my ext3 or ext4 with internal storage to create a much bigger internal storage?
Cheers
PoshCat1 said:
Thanks,
I'll try to deal with everything.
apps and dalvik have been moved using terminal emulator and yes, it's the 147MB that is the issue, not the ext3.
I have s-on
So if I have the s-off can I incorporate my ext3 or ext4 with internal storage to create a much bigger internal storage?
Cheers
Click to expand...
Click to collapse
Not quite
S-OFF is merely an enabler, in this case it allows you to change hboot.
It has nothing to do with your sd-ext partition. This is handled by the A2SD script. Your internal memory still won't read 'internal + sd-ext' like it is currently, but the sd-ext is still doing its job.
What I would recommend:
- Titanium backup all user apps, backup contacts to Google, SMS with SMS backup and restore if you want
- Flash 2.3.3. RUU from here, put PB99IMG.zip on root of sd card and boot to bootloader, accept it when found
- Run Revolutionary to gain s-off (search for guides)
- Flash 4EXT recovery (see my sig, use fastboot or 4EXT app)
- Switch hboot using fastboot (to OxygenR2 if using Mildwild 10)
- Reboot to recovery, full wipe ("wipe all partitions except sd card" option)
- Flash ROM.zip
- Restore
eddiehk6 said:
Not quite
S-OFF is merely an enabler, in this case it allows you to change hboot.
It has nothing to do with your sd-ext partition. This is handled by the A2SD script. Your internal memory still won't read 'internal + sd-ext' like it is currently, but the sd-ext is still doing its job.
What I would recommend:
- Titanium backup all user apps, backup contacts to Google, SMS with SMS backup and restore if you want
- Flash 2.3.3. RUU from here, put PB99IMG.zip on root of sd card and boot to bootloader, accept it when found
- Run Revolutionary to gain s-off (search for guides)
- Flash 4EXT recovery (see my sig, use fastboot or 4EXT app)
- Switch hboot using fastboot (to OxygenR2 if using Mildwild 10)
- Reboot to recovery, full wipe ("wipe all partitions except sd card" option)
- Flash ROM.zip
- Restore
Click to expand...
Click to collapse
Thanks,
I will try that when I get some time.
I wanted to install p. vs z 2 but it has 168 MB. And our Desire 151MB system partitionn :crying:
Of cause i have an ext partition. There are 754 free Mb of 1,41 GB. (quick system info)
But my intern memory just have 33,44MB of 151 free.
So on the ext i could install it 4 times but the store first download to intern. Is there a way to install? Maybe if someone uploads the apk and i flash it in the recovery directly to ext4?
An other question. When i startet my phone there where just 5,6MB free. When moves the a2sd script things to the partition and when moves it it back?
HandyBesitzer said:
I wanted to install p. vs z 2 but it has 168 MB. And our Desire 151MB system partitionn :crying:
Of cause i have an ext partition. There are 754 free Mb of 1,41 GB. (quick system info)
But my intern memory just have 33,44MB of 151 free.
Click to expand...
Click to collapse
Your /data partition is 151MB, not your /system partition. Your /system partition is 250MB as you are on stock hboot.
So on the ext i could install it 4 times but the store first download to intern. Is there a way to install? Maybe if someone uploads the apk and i flash it in the recovery directly to ext4?
Click to expand...
Click to collapse
When installing apps, as far as I know it doesn't actually install it to internal (/data), and then move it to ext4. It should install it directly to ext4.
However, depending on the ROM, it needs to see the available space on the internal. The apk is then tricked to your ext4 partition.
One way to install it which might work (not tried it)
- Find and download the apk
- Copy and paste it to your /sd-ext partition using a file browser
- Change file permissions to match your other apps
- Reboot
An other question. When i startet my phone there where just 5,6MB free. When moves the a2sd script things to the partition and when moves it it back?
Click to expand...
Click to collapse
What ROM are you using, and are you using the built in A2SD script or something else? Any A2SD script should move apps (and maybe dalvik cache) automatically to your ext4 partition. I does not move it to internal and back to ext4.
It looks like your memory usage is not very efficient. You may benefit from changing hboot if your ROM /system size is a lot smaller than 250MB. Your dalvik cache might also be on internal, when you could move it to sd-ext where there is plenty of free space.
eddiehk6 said:
Your /data partition is 151MB, not your /system partition. Your /system partition is 250MB as you are on stock hboot.
When installing apps, as far as I know it doesn't actually install it to internal (/data), and then move it to ext4. It should install it directly to ext4.
However, depending on the ROM, it needs to see the available space on the internal. The apk is then tricked to your ext4 partition.
One way to install it which might work (not tried it)
- Find and download the apk
- Copy and paste it to your /sd-ext partition using a file browser
- Change file permissions to match your other apps
- Reboot
What ROM are you using, and are you using the built in A2SD script or something else? Any A2SD script should move apps (and maybe dalvik cache) automatically to your ext4 partition. I does not move it to internal and back to ext4.
It looks like your memory usage is not very efficient. You may benefit from changing hboot if your ROM /system size is a lot smaller than 250MB. Your dalvik cache might also be on internal, when you could move it to sd-ext where there is plenty of free space.
Click to expand...
Click to collapse
i'm using RSK Sattelite ROM.
but if the apps are installed to ext how comes that the data sometimes has about 10MB free and after i installed an update there are 15MB free??
HandyBesitzer said:
i'm using RSK Sattelite ROM.
but if the apps are installed to ext how comes that the data sometimes has about 10MB free and after i installed an update there are 15MB free??
Click to expand...
Click to collapse
It depends a bit on how your script works. Reading the ROM OP it has some sort of "a2sdx" built it, I'm not familiar with exactly how it works. You need to understand this script first before wondering about anything internal memory related.
Think about it logically though...the script is meant to move things to the ext. That's its purpose. Generally they move at least the whole app apk to ext.
So
- If you have an app installed, it should already be on the ext.
- When you update the app, it will overwrite the existing apk on ext.
- There are other things along with an app such as app libs, app data and dalvik cache, which may be on internal or ext depending on the script. These can change on app updates as well.
Have a look at an app like 'DiskUsage', use it to browse your /data partition. See what's using the space. Often you may have some stray /system apps on /data, and you need to move them back to /system.