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?
Related
OK, not that much of a noob (or at least dont think I am!) have been playing with android for some time, and have decided to cook up my own rom based on DesireHD. After some failures I now have a good stockish rom that I like and will release once i can sort out a few problems that I have.
I want to go down the CWM .zip route so I can release updates easily, off to the forums I went with a few questions... hours and hours of searching and researching and a few test runs later... have even more questions!!!!
1. EuroHD2 (Leo512) has 512mb ROM > how much of that ROM is actually available?
2a. When does the kernel load the SD-Ext partition?
2b. With CMW Recovery do you have to set a "userdata" partition when using SD-Ext data, or can you get away with not setting one?
3. Does CMW support using SD-Ext userdata
4. Is the 400m CMW Recovery only for the Leo1024?
5. What is the maximum size for the "system" partition on Leo512?
6. What is with all the questions??????
As you can see, many questions. Most have come from searching the forums and becoming more and more confused with it all!!
Please help!
SquithyX said:
I want to go down the CWM .zip route so I can release updates easily, off to the forums I went with a few questions... hours and hours of searching and researching and a few test runs later... have even more questions!!!!
Click to expand...
Click to collapse
Good idea.
SquithyX said:
1. EuroHD2 (Leo512) has 512mb ROM > how much of that ROM is actually available?
Click to expand...
Click to collapse
All of it.
Partitions:
misc 1MB
recovery 5MB
boot 5MB
system 150MB to 350MB
cache (optional, but people like 10MB)
userdata (whatever that remains, 350MB system partition size = 50mb userdata)
SquithyX said:
2a. When does the kernel load the SD-Ext partition?
2b. With CMW Recovery do you have to set a "userdata" partition when using SD-Ext data, or can you get away with not setting one?
Click to expand...
Click to collapse
yes, sadly, you still need the userdata partition, you can go around it by creating another partition on the SD card, and call it userdata, I am assuming that works too. So now your SD has userdata, sd-ext, fat32 partitions.
SquithyX said:
3. Does CMW support using SD-Ext userdata
Click to expand...
Click to collapse
urm, that's not CMW's job, that's your job.
You can either use DATA2EXT method which puts all userdata in SD card, ext2/3/4 partition or A2SD+ which puts all your data on the SD card, minus I don't know what, because it keeps reducing and I never figure out what. I am lazy to use adb.exe to go check.
SquithyX said:
4. Is the 400m CMW Recovery only for the Leo1024?
Click to expand...
Click to collapse
Yes, because you really ran out of space. 350MB system partition, gives you less than 50MB of userdata partition provided you have 10MB of cache partition.
I was wondering that...
So if I create a "userdata" partition on the SD card the system should use that... meaning no userdata partition on the NAND... meaning SD-Ext and Data2SD features are not needed?
But then surly if it was that easy somebody else would have done it?!
The layout I am thinking is:
NAND/
--/misc (1mb)
--/boot (5mb)
--/recovery (5mb) *Is this needed? - Is this not for the recovery programs that we have on SD?
--/system (350-400mb) *theoretically upto 491mb as no userdata on NAND
--/cache (10mb)
SD/
--/userdata (1gb) *Could be bigger, but have read that it can cause corruption if over 2gb
-Fat32 (leftovers)
But all of this comes back to Q2a. When does the kernel load SD partitions?!
Other idea is to set the "userdata" in NAND to set size and grow the "system" partition and carry on using SD-Ext and Data2SD for internal storage, something like:
NAND/
--/misc (1mb)
--/boot (5mb)
--/recovery (5mb)
--/cache (10mb)
--/userdata (50mb)
--/system (leftovers) *441mb
SD/
--/Ext (1gb)
-Fat32
But then does the "system" partition have to be created 4th and wont work if created last???? And what about all the plastic trees, where do they go?! My head hurts, i'm cold and there are wolfs after me!
I am guessing that creating userdata on sd card might work, but I don't know how your build mounts partitions, so that is your job too.
but you should read up on data2sd, data2ext, a2sd+ and a2sd
No, you can move the partitions around, it worked for me.
Every android device configures a cache partition as far as I know. They are different sizes depending on which HBOOT/partitioning scheme is being used. For the device I use (HTC Desire) configurations range from a small 5MB to a quite significant 95MB (out of 512MB - http://alpharev.nl/ ); so I wanted to find out how I would go about choosing the "correct" one.
From what I gathered, the use of this partition entirely depends on what ROM you use. So the "best" partitioning scheme is ROM dependent. Nandroid backups can of course only be restored in partitioning schemes that accommodate enough space for each partition.
By default:
* It's used for Gmail attachment previews, browser DRM downloads, Market downloads and OTA updates.
** Cannot install apps from the market bigger than (remaining) cache size
* ClockWorkMod uses it during flashing.
* Some report a larger cache partition gave them better graphical performance (memory caching?)
Dalvik-cache is NOT stored in the cache partition but the userdata partition.
However, some ROMs define a particularly small cache partition (5MB/10MB for CM7/Oxygen for example). They supposedly work around above limitations by not using the cache partition at all and defining a location in the userdata partition for above functionality.
This still doesn't change the fact that ClockWorkMod requires a significant cache partition for full functionality (recovery mode is independent from ROM used) - more specifically, radio flashes are said not work in recovery mode with cache partitions sized 10MB or smaller.
http://forum.xda-developers.com/showpost.php?p=11900235&postcount=5
Any other things one should know before messing with the cache size? Does Amon-RA have the same requirement for the cache partition as ClockWorkMod? Are there other downsides to small cache partitions other than those mentioned, with a ROM that doesn't "use" it?
http://forum.cyanogenmod.com/topic/1095-why-several-partitions-at-all/page__view__findpost__p__10725
http://forum.cyanogenmod.com/topic/1095-why-several-partitions-at-all/page__view__findpost__p__10305
THC HD2 How 170MB system partition and at least 2MB cache partition with HD2ToolKit4.2.0.1?
Step bay step?
On left click 170, below that enter 2 in cache box, click repartition.
Cabron
Dasis said:
THC HD2 How 170MB system partition and at least 2MB cache partition with HD2ToolKit4.2.0.1?
Step bay step?
Click to expand...
Click to collapse
eiy seems like AOKP but using HD2Toolkit, min. for cache is 5mb, try the link below it could give you an idea
Installations:
Please use at least 170MB system partition and at least 2MB cache partition.
Please refer to ksubedi's HD2 NAND Toolkit and/or mskip's guide.
Cache partition (/dev/block/mtdblock4) is only mounted and 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.
If your HD2 has bad NAND blocks, you may need larger partitions.
Wipe
Wipe Data/Factory Reset while doing a fresh install. (Optional: also delete /sdcard/Android folder or format your SD card if you have any strange issue.)
Advanced -> Wipe Dalvik Cache while upgrading from an old version and wanting to retain data.
Flash this ROM.
I click custom and below that enter 2 in cache box, click repartition. Show new table "What do you want the custom partition size to be 5-445 MB allowed. I write 170 click OK.
I give table sorry chase size must be 5 to 45MB.
Where is I did mistake ?
samsamuel said:
On left click 170, below that enter 2 in cache box, click repartition.
Click to expand...
Click to collapse
raziel024 said:
Cabron
Click to expand...
Click to collapse
You haven't helped in any way, thats rude. Cabron.
Dasis said:
Installations:
Please use at least 170MB system partition and at least 2MB cache partition.
Please refer to ksubedi's HD2 NAND Toolkit and/or mskip's guide.
Cache partition (/dev/block/mtdblock4) is only mounted and 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.
If your HD2 has bad NAND blocks, you may need larger partitions.
Wipe
Wipe Data/Factory Reset while doing a fresh install. (Optional: also delete /sdcard/Android folder or format your SD card if you have any strange issue.)
Advanced -> Wipe Dalvik Cache while upgrading from an old version and wanting to retain data.
Flash this ROM.
I click custom and below that enter 2 in cache box, click repartition. Show new table "What do you want the custom partition size to be 5-445 MB allowed. I write 170 click OK.
I give table sorry chase size must be 5 to 45MB.
Where is I did mistake ?
Click to expand...
Click to collapse
1 -In the main HD2 android NAND toolkit window, look left for "Choose system partition size(MAGLDR)" and select "CUSTOM"
2 -Below this window change "cache size", but smallest possible is 5MB. It doesn't matter if it's bigger, won't give trouble.
3-after those step choose "Repartition" button below 'Functions' and type desired (4) system partition size.
Have fun.
Dasis said:
I click custom and below that enter 2 in cache box, click repartition. Show new table "What do you want the custom partition size to be 5-445 MB allowed. I write 170 click OK.
I give table sorry chase size must be 5 to 45MB.
Where is I did mistake ?
Click to expand...
Click to collapse
retsam88 said:
2 -Below this window change "cache size", but smallest possible is 5MB. It doesn't matter if it's bigger, won't give trouble.
Click to expand...
Click to collapse
as retsam88 said, it deoesnt matter the cache size, most people leave it at 5, some roms say 45, (but i haven't seen that for a while).
As far as i know, (i've read it once or twice) on most roms, only recovery uses the cache partition.
misc ya 1M
boot yboot|ro 5M or 6M // According to their Recovery
system ya 150M // Minimal Installation
system ya 240M // Full Installation
system ya 150M - 275M // Custom Installation
cache ya 2M
userdata ya|asize|hr allsize
if you have Bad Sectors, please add 5MB more, to System Partition
I like to do this partition. What do i have to make it work with hd2toolkit ? Thanks
saigon66 said:
What do i have to make it work with hd2toolkit ? Thanks
Click to expand...
Click to collapse
you cant because the toolkit writes a new flash.cfg each time when you choose custom, or uses an .nbh when you choose a preselected size.
You should find the daf.exe flash version of cwm, and when you extract it into a folder you will find one file called flash.cfg, , open that in notepad you will see a list like teh one you posted, , edit the numbers, save it, then run daf.exe with teh phone in usb flasher mode.
OK .. Im about to flash a new rom (ParanoidAndroid HD2) but i am a little confused on how to do all the partitioning requested.
Heres an example:
misc ya 1M
boot yboot|ro 5M
system ya 200M
cache ya 2M
userdata ya|asize|hr allsize
I understand that i can use HDToolkit to partition the system and cache, but what about partitioning "boot" and "misc". And what is userddata ya?
Everything in that list gets partitioned when you do the system partition, so don't worry about it.
Also, your thread title says SD partitioning, which is nothing to do with anything in your post,, totally different thing.
So basically all i want to do is make sure the system partitioning is as recommended or enough and the same with the cache. The other partitioning is done during the installation.
If thats the case, thank you very much for your input.
Noob Dude said:
So basically all i want to do is make sure the system partitioning is as recommended or enough and the same with the cache. The other partitioning is done during the installation.
If thats the case, thank you very much for your input.
Click to expand...
Click to collapse
Basically yeah, just select 200MB in the HD2 Toolkit and let it do it for you.
thank you so much
Noob Dude said:
thank you so much
Click to expand...
Click to collapse
1.misc is for android misc data and boot is for the linux kernel and ramdisk in order to let the rom boot
2.normally we set boot to 5 and cache to >=2 because roms now dont really use this partition for cache, it's just used by cwm
3.misc and recovery should normally be 1 and 5~6
4.userdata is for android to store your system and application data in your daily usage
5.usually you can find an instruction for partitions size in a rom thread
EDIT:userdata is usually auomatically sized becasue it spreads at the end of the nand,
following other partitions...
if this helped you and enlarged your knowledge please press the thanks button
. |
. |
.\ /
Hi,
Short / long story:
I have long time unused HTC HD2.
With Android (NexusHD2-KitKat-CM11.0_V4.5.zip is the file which I found in backup, so I assume this is what I install - sorry, it was long time ago.
Some time ago I need microSD card so I took it from my HD2, I did backup only windows FAT32 partition.
Now, I need to run my HD2 , I have install microSD 2 GB (800 MB FAT32 + 1GB Ext4) but is not working correctly.
It starting I can install Teamviewer, but when I need to install HTC module for teamviewer it's telling me that is not enough storage.
Quite often is restarting and after restart not keeping any settings (wi-fi) app installed (teamviewer) it's resetting each time to factory settings.
In Settings - Storage shows 'Total space' - Available 0.00 bytes
I did what is instructed on this webpage but it didn't help http://android.stackexchange.com/qu...mory-in-android-nand-roms-cannot-install-apps
Can anybody advise me which is the easiest way to make my HD2 working properly? Means have enough memory to do anything.
The purpose of restoring my HD2 is working as a router, tethering machine. I need to share internet from mobile network for smart TV and Tablet over wi-fi. It will be unattended so I need remote control access (team viewer host).
I'm open for a suggestion of changing the ROM if there is something reasonable easy and described (as I'm not big ROM expert). i've seen a ROM list for HD2, is too long.
Thanks in advance for your help.
it sounds like you are missing a data partition, perhaps the sdcard you used before had an ext4 partition which your new one does not have. Use recovery, in nand, to create an ext4 partition, then boot into rom, might work.
Robbie P said:
it sounds like you are missing a data partition, perhaps the sdcard you used before had an ext4 partition which your new one does not have. Use recovery, in nand, to create an ext4 partition, then boot into rom, might work.
Click to expand...
Click to collapse
Hi,
Thanks for your reply.
I did Ext4 by MiniTool Partition under Windows primarily.
And later in recovery, I have setup 1024MB and swap = 0 M.
It didn't help.
Should I mount it or so?
Update:
I have a look in log in nand - recovery and it's says that my second partition is Ext3 not Ext4.
And there is no way to change it.
What is your nand recovery? version?
Clk or magldr?
The recovery might say ext3 when it means ext4, but it does not seem right.
Robbie P said:
What is your nand recovery? version?
Clk or magldr?
The recovery might say ext3 when it means ext4, but it does not seem right.
Click to expand...
Click to collapse
It says on the top bar screen 'CWM-based on Recovery v5.0.2.6' but was install with ROM so should be fine.
try using the recovery to format the ext partition to ext2 or 3 then use it again to ext4
Robbie P said:
try using the recovery to format the ext partition to ext2 or 3 then use it again to ext4
Click to expand...
Click to collapse
As I said, I have created and formatted partitions under windows FAT32 & Ext4 and then under recovery, there was no choice of the file system file, I can only choose the size. And it was formatted to Ext3 - log saying.
badzi0r said:
As I said, I have created and formatted partitions under windows FAT32 & Ext4 and then under recovery, there was no choice of the file system file, I can only choose the size. And it was formatted to Ext3 - log saying.
Click to expand...
Click to collapse
Here's the solution:
http://forum.xda-developers.com/showpost.php?p=38956440&postcount=4
Thank you