Related
Hello
I want to modify my partition table, I've read users get better 3D performance (in games) with a bigger Cache partition.
3D performance aside, what's the recommended minimum size I should set it to without compromising overall performance?
I'm using a Sense based rom if it matters.
Thanks!
Not sure... I'm running an AOSP ROM with the N1 table. No performance lag for me.
Android uses the cache partition, to cache memory, giving it much faster access to it, so obviously the bigger your cache, the more cached ram your device has access too, also the market uses the cache for downloads, so if you have a 10mb cache partition you cant download a 14mb app off the market ect...
Sent from my HTC Desire using Tapatalk
AndroHero said:
Android uses the cache partition, to cache memory, giving it much faster access to it, so obviously the bigger your cache, the more cached ram your device has access too, also the market uses the cache for downloads, so if you have a 10mb cache partition you cant download a 14mb app off the market ect...
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
but how to modify the cache partition, or how to know the exact size of it?
Thanks,
williepeng said:
but how to modify the cache partition, or how to know the exact size of it?
Thanks,
Click to expand...
Click to collapse
This thread is nearly 3 years old and a bit redundant now.
You can modify the cache partition by using what is known as a custom hboot.
An hboot has 3 partitions: /system /data and /cache. Assuming you have not changed it, you are still on 'stock hboot' and your cache partition is 40MB. Your /system is 250MB, and your /data (internal memory) is only 147MB
However, nowadays we use custom hboots to change these sizes. We reduce /system and /cache in order to increase /data (-> more space for apps).
The /cache argument above is basically redundant because it is just used for temporary files. Most custom hboots actually reduce this cache partition from 40MB to 5MB.
Basically there is no real need to change the cache partition, certainly no need to make it bigger.
Also, you need to be "S-OFF" to achieve any of this. As this is your first post I'm not sure what other reading you've done and what your ultimate goal is.
Just got a notification for a thread about a device i havent even had for 3 years lol
Sent from my HTC One X+ using Tapatalk
eddiehk6 said:
This thread is nearly 3 years old and a bit redundant now.
You can modify the cache partition by using what is known as a custom hboot.
An hboot has 3 partitions: /system /data and /cache. Assuming you have not changed it, you are still on 'stock hboot' and your cache partition is 40MB. Your /system is 250MB, and your /data (internal memory) is only 147MB
However, nowadays we use custom hboots to change these sizes. We reduce /system and /cache in order to increase /data (-> more space for apps).
The /cache argument above is basically redundant because it is just used for temporary files. Most custom hboots actually reduce this cache partition from 40MB to 5MB.
Basically there is no real need to change the cache partition, certainly no need to make it bigger.
Also, you need to be "S-OFF" to achieve any of this. As this is your first post I'm not sure what other reading you've done and what your ultimate goal is.
Click to expand...
Click to collapse
Thanks you for your answer. Yes, I'm a beginner and only know the basic about Android system.
Actually I'm make a cache.img that can be flashed into a Samsung device with the recovery.img, but I don't know whether it would destroy the system if the one I made is bigger or smaller than the one in stock ROM.
williepeng said:
Thanks you for your answer. Yes, I'm a beginner and only know the basic about Android system.
Actually I'm make a cache.img that can be flashed into a Samsung device with the recovery.img, but I don't know whether it would destroy the system if the one I made is bigger or smaller than the one in stock ROM.
Click to expand...
Click to collapse
Well welcome to the Android world
Each device is different, so Samsung root methods are also different.
DO NOT flash any cache.img for this phone. You don't need to adjust any cache sizes...and you'll more than likely brick your phone if you manage to somehow flash it.
For this device, I always recommend you start here, read it many times
eddiehk6 said:
Well welcome to the Android world
Each device is different, so Samsung root methods are also different.
DO NOT flash any cache.img for this phone. You don't need to adjust any cache sizes...and you'll more than likely brick your phone if you manage to somehow flash it.
Click to expand...
Click to collapse
Actually flashing cache partition cannot brick the phone since it doesn't carry any unique content. For the same reason you don't need to flash it at all, system will create all necessary files by itself.
dean15 said:
Actually flashing cache partition cannot brick the phone since it doesn't carry any unique content. For the same reason you don't need to flash it at all, system will create all necessary files by itself.
Click to expand...
Click to collapse
Actually eddie was on bout flashing the samsung cache.img the guy had so yh u could/would brick ur phone. And the desire's internal memory layout is divided into 3 partitions, system (250mb) cache (40mb) data (147mb) totally size is 437mb, soo if the guy flashed just the cache.img it would probably **** up the phone's memory leaving u with a paper weight
dean15 said:
Actually flashing cache partition cannot brick the phone since it doesn't carry any unique content. For the same reason you don't need to flash it at all, system will create all necessary files by itself.
Click to expand...
Click to collapse
All I can say is I don't recommend it at all...I also really hope you're not thinking about flashing something meant for a Samsung phone.
The cache partition may not carry any unique content, but flashing an hboot is a critical part of the phone. A corrupted hboot flash = brick
Even if you somehow successfully managed to flash a cache separately...ultimately you won't actually gain anything by doing so.
Choice is yours, but don't say we didn't warn you
eddiehk6 said:
All I can say is I don't recommend it at all...I also really hope you're not thinking about flashing something meant for a Samsung phone.
The cache partition may not carry any unique content, but flashing an hboot is a critical part of the phone. A corrupted hboot flash = brick
Even if you somehow successfully managed to flash a cache separately...ultimately you won't actually gain anything by doing so.
Choice is yours, but don't say we didn't warn you
Click to expand...
Click to collapse
)))
OK, we're talking about the same thing in different words.
Hi,
Since a little while i ditched sense roms for gingerbread aosp roms (Oxygen 2.0 not to name it) which take a lot less space on the internal memory, especially on /system. I know it is possible to change partition table with s-off phones to optimize this free space but i'm s-on and i don't really want to change this.
But the result is i that i end up having something like 160mb free on /system partition and i have to move the dalvik cache from /data to have enough free space from apps. (Once the dalvik is moved /data is large enough even with a lot of apps for those who use a2sd)
i currently use AdamG script in "dalvik-cache2SD-signed.zip" to move the dalvik to sd-card, but i was wondering if it was possible to move it to /system instead (since with sense-table there is a lot free space in it). Could-it result better performances or battery life ?
What do you think about this ?
No don't think so and definitively not when you are S-on since you don't have write access to the system partition while booted.
Lol. No, since you're S-ON. So, if you unlock the system write, you can easily put another HBOOT layout anyway.
Oops yes i forgot /system was read-only >_< well at least i got my answer, thanks ! xD
maybe i will try this s-off thing after all...
It's not a big deal, just read the instructions carefully, make sure you have the proper drivers for fastboot before flashing hboot instead (you can find the instructions on www.unrevoked.com) and you're good to go.
I haven't found really good explanation on forum and most of post on this seems not to be answered so I'm posting to see if I can get this sorted.
I used Leedroid, InsertCoin, and now on GingerVillian now. All of them had same setting of 500MB ext partition. Problem is I always seems to get low internal memory no matter what ROM I use. Currently I have 394MB free SD-EXT and 16MB Internal.
I moved adobe flash to SD card which seems to free up space and Dalvik Cache is on SD-Ext.
So question is why even though I have lot of EXT space left is it not being used and is there way to make it use it more instead of internal memory?
jinius said:
I haven't found really good explanation on forum and most of post on this seems not to be answered so I'm posting to see if I can get this sorted.
I used Leedroid, InsertCoin, and now on GingerVillian now. All of them had same setting of 500MB ext partition. Problem is I always seems to get low internal memory no matter what ROM I use. Currently I have 394MB free SD-EXT and 16MB Internal.
I moved adobe flash to SD card which seems to free up space and Dalvik Cache is on SD-Ext.
So question is why even though I have lot of EXT space left is it not being used and is there way to make it use it more instead of internal memory?
Click to expand...
Click to collapse
App2SD is flawed because of this, say you have an app 20mb, 15mb would be put on to the SD card and the rest go's to internal, so you will still use up space and in the end will have to start uninstalling.
Best way is to use a Rom with data2SD witch give's you 2gb internal memory.
Sent from my HTC Desire using XDA App
I have the same problem... I hate it , i have 1 gb for sd-ext3 and i cant enjoy it !
Any ideas ?
wska said:
I have the same problem... I hate it , i have 1 gb for sd-ext3 and i cant enjoy it !
Any ideas ?
Click to expand...
Click to collapse
Data2SD RoM problems solved
One could also flash a new hboot which increases the size of the /data-partition. However you need s-off for this and it's imho riskier than flashing a rom with data2sd. Whereas i work with a2sd + cm7 hboot and i am very happy it.
Desire with Cool Sensation v7
Hi,
I have this problem too. but it is not our choice to choose the data2sd instead of app2sd because it depend on what the ROM support.
Previously I use App2sd+ from ModaCo ROM. I have 200+ apps and it take the internal memory nearly full but sd-ext space just half.
I tried the Data2sd for Desire is only SuperNova with HTC Sense and it work in 1Gb sd-ext. BUT it uses Sense 2.1.
I just try Sense 3 from Cool Sensation v7 ROM. I love it and dont want to revert back to previous Sense It have 3D home screen, cool weather animation, SMS secure lock. However this ROM still use app2sd. I cannot post to the thread, I dont have enought post count.
I try some other way to apply Data2sd into this ROM but I got boot loop.
After few days I use this ROM, my internal memory almost full (15mb free) for only 57 apps even the app2sd symlink-ed /data/app, /data/app-private, /data/dalvik-cache and /system/app into sd-ext!
Expert please help me and give me some idea.
Do I need to symlink /data/data into sd-ext manually?
Is it possible to remove app2sd in the ROM and install Data2sd? How?
Data2sd require busybox, init.d and ext4 kernel support. I think this ROM have all this thing.
HTC Desire
Hboot S-Off with Revolutionary
4ExtRecovery
Cool Sensation v7 ROM
8Gb Class 2 sd card with Fat32 + 1Gb ext4
And have some basic in Linux shell
I can 100% get my head around this either, although i did install some apps and i could really tell if it was on Internal or EXT4.
From my understanding, as far as the phone os, it thinks apps are on Internal and will decrease the size counter, but apps are on EXT4 if you use a file manager etc.. but even if all goes to EXT4, we still get that annoying LowDisk message was it get to 15megs...
I still was convinced, but i accidently decided i wanted to format my FAT32 partition, mainly to get rid of all the junk that on there since STOCK Rom. I used the Phone own Format SD Card option.
Well that was fun (NOT!!) it instead formatted the EXT4 and not the FAT32, when i rebooted all the loaded apps that were on EXT4 were now gone.
Phone still works, but one side effect of this is now i have like 270megs free....lol, granted no wallpaper, lockscreens etc,
anyway seeing as i screwed up and that im already S-OFF, im going to just go with CM7r2 HBoot.
Similar issue - I think?
Hi all, my first post here
So I have been working my way through all the error messages and guides and finally have InsertCoin set up. All is looking good except after Titanium Backup restored all my apps my internal memory is as full as before I rooted the phone, so I think I can safely say that the 2gb I partitioned off on my SD is not getting ay use at all? Is there a way I can check?
For the record I am running with AmonRa, and I used Revolutionary to get s-Off. The guide I followed to set up A2SD did not have me using any Terminal commands, so I am guessing that is an area for me to explore in solving this, here is the guide I used (near the end)
/myhtcdesire.com/modding/how-to-install-a-custom-rom-on-your-htc-desire
I used that method as i am on a borrowed mac and it just seemed easier. I
I am hoping there is an easy fix that someone can suggest.
hoads1234 said:
Hi all, my first post here
So I have been working my way through all the error messages and guides and finally have InsertCoin set up. All is looking good except after Titanium Backup restored all my apps my internal memory is as full as before I rooted the phone, so I think I can safely say that the 2gb I partitioned off on my SD is not getting ay use at all? Is there a way I can check?
For the record I am running with AmonRa, and I used Revolutionary to get s-Off. The guide I followed to set up A2SD did not have me using any Terminal commands, so I am guessing that is an area for me to explore in solving this, here is the guide I used (near the end)
/myhtcdesire.com/modding/how-to-install-a-custom-rom-on-your-htc-desire
I used that method as i am on a borrowed mac and it just seemed easier. I
I am hoping there is an easy fix that someone can suggest.
Click to expand...
Click to collapse
To check if a2sd is working, open terminal emulator and type
Code:
su
ls -l /data
Output should say (for a2sd):
Code:
app -> /sd-ext/app
app-private -> /sd-ext/app-private
Additionally for a2sd+:
Code:
dalvik-cache -> /sd-ext/dalvik-cache
If it does not show this, a2sd is not working. So make sure you partitioned sd card correctly (fat32 + ext; both primary).
CallMeLaNN said:
Hi,
I have this problem too. but it is not our choice to choose the data2sd instead of app2sd because it depend on what the ROM support.
Previously I use App2sd+ from ModaCo ROM. I have 200+ apps and it take the internal memory nearly full but sd-ext space just half.
I tried the Data2sd for Desire is only SuperNova with HTC Sense and it work in 1Gb sd-ext. BUT it uses Sense 2.1.
I just try Sense 3 from Cool Sensation v7 ROM. I love it and dont want to revert back to previous Sense It have 3D home screen, cool weather animation, SMS secure lock. However this ROM still use app2sd. I cannot post to the thread, I dont have enought post count.
I try some other way to apply Data2sd into this ROM but I got boot loop.
After few days I use this ROM, my internal memory almost full (15mb free) for only 57 apps even the app2sd symlink-ed /data/app, /data/app-private, /data/dalvik-cache and /system/app into sd-ext!
Click to expand...
Click to collapse
I used Cool Sensation v7 but didn't have this problem until I flashed the newer v9 (just noticed v10 has been posted today though). My internal memory was very low but I then flashed the Dalvik to sdext.zip from the Cool Sensation thread and then had 180MB internal free. Try that and see if it works. If it doesn't, have you aligned your SD ext using the .zip on the same thread? if not this could be why your having problems, though it didn't work for me.
Thanks for the ideas, I was a bit out of my depth with the Mac SU functions, so although i didn't get the desired feedback you suggested, but it could have been me. So anyway I found a Ubuntu machine and plugged in the SD card in an adapter and can see that there is a successful partition, and that the EXT partition seems to have some files and folders in it.
I have also just noticed that the SD cards partitions also appear in the Titanium Backup overview screen.
So i guess my problem is that the memory is just full! Maybe my expectations of extra memory after rooting were unrealistic. ?
For the Record, just to make sure my situation is normal, in Titanium I see
System ROM - 262MB (129MB free)
Internal - 158MB (15MB free) - is this just a section of system ROM above?
SD CARD - 13.8GB (11GB free)
SD Card (a2sd) - 1.9GB (1.5GB free)
@xybadog this is my update,
@hoads1234 just want to share with you,
I use Cool Sensation v7, the internal memory full can be solved by flashing the additional zip for stock hboot but I flash non stock hboot. Why?
After some studying, now I know why expert keep asking for my hboot. Hboot define the data partition. On the phone memory, it divided into system, cache and data partition. the hboot define the partition size. For stock hboot, you will only have 147Mb for HTC Desire. Whatever the custom ROM symlink'ed some data partition, we stuck on 147Mb. If you flash like CM7r2 hboot, you will get more room (300+Mb) on data but just enough for system. "Internal memory" is referring to data partition.
Now I still have 130Mb free internal memory after installing 90 apps without wiping any cache for about 2 weeks.
I dont have Ubuntu even I know how to use it. No time to install or make virtual machine. To partition your sdcard easily without linux, use 4ExtRecovery. It is CWM based recovery plus support for Ext4 and some features like partitioning, check for aligned sd-ext and mount as disk drive.
To check for your current internal partition. boot into recovery, and use ADB to run command "df -h". The /system /data and /cache is the thing you need to look for.
You could use the cyanogenmod rom, then install s2e app from market. That app is designed purely for use with cyanogenmod. I use this combo, I have a huge amount of apps installed and still 50mb of internal space free. No need for changing your hboot or using data2sd rom. Very simple fix
Sent from my CM7.1 Desire using XDA Premium App
okay thanks, I am still happy having a go with InsertCoin, so I will have a look at the hboot.
I think i read somewhere that i could do it just like adding a new ROM and copying a zip file across, so time for some more forum reading to work my way through this next step.
http://forum.xda-developers.com/showthread.php?t=1110921
okay here is my update, since in have revolutionary hboot, i tried to change to alpharev, so i could use their modified partition tables (found no reference of being able to do this in Revolutionary) - the folks on alpharev irc said not to, but didn't say why.
I did try and use the unrevoked tool to flash AmonRa across again, but this had a waiting for reboot error and may have failed. I have also reflashed my ROM again after a full wipe a couple of times. Not finding any improvements in memory, so will keep fiddling.
okay next question!
I tried the terminal emulator commands (once i worked out this was an app, and not the Mac terminal..) and got the following responses
app -> /system/sd/app
app-private ->
dalvik-cache ->
so am i guessing correctly that none of the apps i download are being sent to the SD partition.
Any advice to get app-private directed to my sd card?
hoads1234 said:
okay next question!
I tried the terminal emulator commands (once i worked out this was an app, and not the Mac terminal..) and got the following responses
app -> /system/sd/app
app-private ->
dalvik-cache ->
so am i guessing correctly that none of the apps i download are being sent to the SD partition.
Any advice to get app-private directed to my sd card?
Click to expand...
Click to collapse
I suggest you use ADB instead of terminal emulator because easy to type in PC.
Install Android SDK make ADB shell to work and connected to your device. The shell is just the same what you need to do in terminal emulator.
To move app private and dalvik cache simply make symlink like this:
Code:
busybox cp -a /data/dalvik-cache /system/sd/
rm -rf /data/dalvik-cache
ln -s /system/sd/dalvik-cache /data/dalvik-cache
The first will move all contents, the second will remove the existing original dalvik-cache folder. and the third one will make symlink to point from original location to the sd partition.
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.
Hi I've downgraded HBOOT to s-off (also giving new HBOOT), flashed new HBOOT compatible with all roms and flashed roms o plenty on my desire s (saga) but my desire (bravo) has been a little more complicated to say the least!
The roms for the desire 1 all go on about having xxx Mb HBOOT and all the various partition sizes needed, nether of these seem to apply on the desire s and dispute having read guides over and over, I cant seem to get the partitions right (1.5mb main mem left after clean rom flash) im wondering if its to do with the hboot instead.
Before AND after partitioning the device, the gingerbread rom iused to get from hboot 1.03 to one compatible with revolutionary works fine, I am currently on the HBOOT version revolutionary planted on the phone ( HBOOT-6.93.1002, RADIO-5.17.05.23 )
The custom rom I tried booted a couple of times but as I said, with only 1.5mb of mem left and lagged like a Pentium 4 pc trying to play battlefield 4 lol.
That rom has not booted since but restoring via recovery to the gingerbread rom, all works fine.
The custom rom I installed was omni-4.4.2-20140518-bravo-homemade, i want to try others but this was just a starting ground.
Please can someone point me in the right direction, as i said, I've followed guides for partitioning the SD card and I've gone wrong somewhere and can't figure out what.
Thanks Steve.
steve_htc_wizard said:
Hi I've downgraded HBOOT to s-off (also giving new HBOOT), flashed new HBOOT compatible with all roms and flashed roms o plenty on my desire s (saga) but my desire (bravo) has been a little more complicated to say the least!
The roms for the desire 1 all go on about having xxx Mb HBOOT and all the various partition sizes needed, nether of these seem to apply on the desire s and dispute having read guides over and over, I cant seem to get the partitions right (1.5mb main mem left after clean rom flash) im wondering if its to do with the hboot instead.
Before AND after partitioning the device, the gingerbread rom iused to get from hboot 1.03 to one compatible with revolutionary works fine, I am currently on the HBOOT version revolutionary planted on the phone ( HBOOT-6.93.1002, RADIO-5.17.05.23 )
The custom rom I tried booted a couple of times but as I said, with only 1.5mb of mem left and lagged like a Pentium 4 pc trying to play battlefield 4 lol.
That rom has not booted since but restoring via recovery to the gingerbread rom, all works fine.
The custom rom I installed was omni-4.4.2-20140518-bravo-homemade, i want to try others but this was just a starting ground.
Please can someone point me in the right direction, as i said, I've followed guides for partitioning the SD card and I've gone wrong somewhere and can't figure out what.
Thanks Steve.
Click to expand...
Click to collapse
How much size partition have u made?
Sent from my HTC Desire using XDA Free mobile app
So the initial 'hboots' you have been seeing are merely version numbers relating to official ROMs
e.g.
0.93 is for a Froyo ROM
1.02 is for the Gingerbread ROM
1.03 is HTC dev unlocked ROM I believe
Your version number now doesn't really mean much, but the fact that you are S-OFF now means you can change your hboot. When custom ROMs refer to hboots in this sense, they are merely talking about your internal nand partition sizes.
So going back to before you gained s-off, you were on stock hboot, with the following sizes:
250MB /system
40MB /cache
147MB /data
You are still technically on stock hboot, so your sizes internal nand memory still looks like this. The /data partition is your internal memory, which as you can see is tiny.
S-OFF gained the ability to change your hboot if you so wish. You can find the different hboot partition tables at alpharev.nl. You can flash a different hboot with both smaller /system and /cache sizes, hence much larger /data (internal memory) using fastboot. More /data = more internal memory = more space for apps :good:
You need to flash a compatible custom ROM with a /system size just smaller than the corresponding hboot to optimise your space.
So for instance, cm7r2 hboot has a /system size of 145MB. You need to flash a ROM with say a 140MB extracted system size to fit (it will usually just say in the first post).
Some ROMs will still only fit into stock hboot, but you can still gain space by A2SD whereby apps are moved to the sd-ext partition. You may have to manually activate it, instructions are normally given in each ROM thread.
You also need a correctly partitioned sd card (using 4EXT recovery or gparted only) along with the custom ROM to optimise app space. Which guide did you use? And how big is your partition?
lilsafbig said:
How much size partition have u made?
Sent from my HTC Desire using XDA Free mobile app
Click to expand...
Click to collapse
these are the stats quoted in the info page of 4EXT RECOVERY-
SYSTEM- mtd3 250mb- 14.2mb free
DATA- mtd5 147mb-100.9 free
CACHE- mtd4 40mb- 33.4mb free
SDCARD- fat32 6.4gb-5.6gb free
SD-ext- ext4 513mb-487.9 free
SWAP- swap 513mb - -
eddiehk6 said:
So the initial 'hboots' you have been seeing are merely version numbers relating to official ROMs
e.g.
0.93 is for a Froyo ROM
1.02 is for the Gingerbread ROM
1.03 is HTC dev unlocked ROM I believe
Your version number now doesn't really mean much, but the fact that you are S-OFF now means you can change your hboot. When custom ROMs refer to hboots in this sense, they are merely talking about your internal nand partition sizes.
So going back to before you gained s-off, you were on stock hboot, with the following sizes:
250MB /system
40MB /cache
147MB /data
You are still technically on stock hboot, so your sizes internal nand memory still looks like this. The /data partition is your internal memory, which as you can see is tiny.
S-OFF gained the ability to change your hboot if you so wish. You can find the different hboot partition tables at alpharev.nl. You can flash a different hboot with both smaller /system and /cache sizes, hence much larger /data (internal memory) using fastboot. More /data = more internal memory = more space for apps :good:
You need to flash a compatible custom ROM with a /system size just smaller than the corresponding hboot to optimise your space.
So for instance, cm7r2 hboot has a /system size of 145MB. You need to flash a ROM with say a 140MB extracted system size to fit (it will usually just say in the first post).
Some ROMs will still only fit into stock hboot, but you can still gain space by A2SD whereby apps are moved to the sd-ext partition. You may have to manually activate it, instructions are normally given in each ROM thread.
You also need a correctly partitioned sd card (using 4EXT recovery or gparted only) along with the custom ROM to optimise app space. Which guide did you use? And how big is your partition?
Click to expand...
Click to collapse
you posted this as I was leaving my last post so I did not see it till I posted my partition info, I can't remember off the top of my head what the guide was called but will try and find it and post the link, what you have written has explained a lot and it very very helpfull thankyou for your detailed post, I will get back to you when I have had a chance to read over it again and have a play, the misses is watching a film with me at the moment and I can't mess with the phone till its finished of im in trouble lol
steve_htc_wizard said:
these are the stats quoted in the info page of 4EXT RECOVERY-
SYSTEM- mtd3 250mb- 14.2mb free
DATA- mtd5 147mb-100.9 free
CACHE- mtd4 40mb- 33.4mb free
SDCARD- fat32 6.4gb-5.6gb free
SD-ext- ext4 513mb-487.9 free
SWAP- swap 513mb - -
Click to expand...
Click to collapse
You should have made atleast 1gb partition because them apps will fill up quickly and there's no need for a swap partition.
Sent from my HTC Desire using XDA Free mobile app
eddiehk6 said:
Which guide did you use? And how big is your partition?
Click to expand...
Click to collapse
Ok,found the guide this is what I followed.
http://forum.xda-developers.com/showthread.php?t=2125513
I think it must be the hboot that's the issue but can't look into it properly yet
Thanks again and I will report back
steve_htc_wizard said:
you posted this as I was leaving my last post so I did not see it till I posted my partition info, I can't remember off the top of my head what the guide was called but will try and find it and post the link, what you have written has explained a lot and it very very helpfull thankyou for your detailed post, I will get back to you when I have had a chance to read over it again and have a play, the misses is watching a film with me at the moment and I can't mess with the phone till its finished of im in trouble lol
Click to expand...
Click to collapse
Lol no matter how addictive these forums can be...the misses always takes priority...always
As above, @lilsafbig is correct
lilsafbig said:
You should have made atleast 1gb partition because them apps will fill up quickly and there's no need for a swap partition.
Sent from my HTC Desire using XDA Free mobile app
Click to expand...
Click to collapse
Did not see your post till after my last again, will def make it 1gb or bigger when I re partition it, misses is tired and has abandoned film, yay!
I will get playing around and reading everything you have all written again so im clear son things, I appreciate your help everyong and will post back when ive made some changes.
Steve.
re formatted the sd card how advised to, flashed rom and nothing, re wiped, installed the hboot sugeseted on the roms page but still nothing, just stuck on the htc splash.
Installed a ics rom and everything is working great, the other has issues with this phone lol
Which method did you use to partition, 4ext recovery or gparted?
Stock hboot or the Alpha Jelly hboot will work, as both have 250MB /system size. Are you using fastboot to flash them?
How are you performing the wipe before installation? 'wipe all partitions except sdcard' option within 4ext should be sufficient.
eddiehk6 said:
Which method did you use to partition, 4ext recovery or gparted?
Stock hboot or the Alpha Jelly hboot will work, as both have 250MB /system size. Are you using fastboot to flash them?
How are you performing the wipe before installation? 'wipe all partitions except sdcard' option within 4ext should be sufficient.
Click to expand...
Click to collapse
yes im using the PB99IMG method for flashing them, I partitioned using 4EXT.
I realised stock shouldent be a problem by the numbers explained to me but thought it couldent do any harm to flash a specific hboot reccomended by the rom cheff, it also slightly changed the install process for some reason if you were running a hboot other than it so I shought in the name of compatibility I would give it a try but nope lol, HTC slash screen again ha ha.
I will try another 4.4 rom to see what happen but it is a little strange as it did boot and run poorly before
All the help I have had on thhis topic has been great and has really helped me, I hope someone else who is confused see this and is helpers also
How are you performing the wipe before installation? 'wipe all partitions except sdcard' option within 4ext should be sufficient.
Click to expand...
Click to collapse
You may have corrupted the ROM.zip download. Try again, and verify the md5 sum if it has one.
You may need to activate a2sd first then flash the gapps package straight after, check instructions
Like you said, if that still doesn't work, get any ROM booting as a first step (along with corresponding hboot beforehand if you want to optimise space).