For a while now I've been playing around with custom MTD partitions. I ran MIUI for several months with Caulkin's "stock" partition sizes (whatever the presets are that come with his mod) and then recently increased the size of my system partition (at the expense of some cache size) so that I could run a Sense 3.5 ROM. My questions are as follows:
A.) How does smaller/larger cache partition affect the overall performance of the system?
B.) If data partition size was to remain constant, would it behoove me to allot the excess internal space to my system partition or to my cache partition?
I have read that excess space on the system partition can increase ROM performance but I'm unclear as to whether sacrificing cache space for system space would be counter-productive...
Thanks in advance.
Anyone? Anyone? Bueller?...
Sent from my Pee-Cee Thirty-Six One-Hunnet
Last ditch effort at a bump. Sry.
Sent from my Pee-Cee Thirty-Six One-Hunnet
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.
Hey guys,
just set my partitions to system ~150, data ~305 and cache ~10 > which i've never done before (all went well) but i dont actually know that much about the pros/cons. I mean i have 100mb more internal storage *bonus* but....
....Is a 10mb cache to small? I monitored my cache for a week using su/dropbox df -h command and it never went over 5mb so i naturally thought that i would lower it as much i could to get the most space.
But (again lol) i've read posts saying will not be able to download files larger than the cache size (10mb). Is this true?
It will be a bit of a bummer if its true.
Cheers
If you are on CM7, you need not worry. It already includes a Script (06MountDL) which binds your cache partition to your data partition, so, all downloads greater than your cache size directly end up on your data partition.
(To verify this, you will see 4 partitions when you run the busybox df -h command. /cache, /system, /data and /data-cache or something like that)
i do yeah. i was wondering what that was about.
plus i've downloaded larger files than my previous cache size so pretty stupid question really.
been a long day at work
cheers...clears stuff up anyway
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.
I have a brand new G3 (D852) with Koodo that I just got 2 days ago. I've rooted, installed TWRP and flashed a few AOSP roms. Not a fan of any manufacturer UI, even though LG's is very minimal, so AOSP it is. I noticed that my system partition has more than 1GB of free space after everything is flashed and good to go. I also noticed that the latest TWRP (2.8.7.0) has a resize partition option inside the Wipe section. What I want to know is, how can I use this to resize the system and data partitions so that 1GB+ isn't being wasted and unused. I'd really like to get that 1GB+ added to my data partition for apps.
I've tried using it. The only time it didn't spit out an error was after I wiped the system partition. It succeeded in "resizing" it after that, but it didn't change anything. The system partition remained the same size.
ToYeD said:
I have a brand new G3 (D852) with Koodo that I just got 2 days ago. I've rooted, installed TWRP and flashed a few AOSP roms. Not a fan of any manufacturer UI, even though LG's is very minimal, so AOSP it is. I noticed that my system partition has more than 1GB of free space after everything is flashed and good to go. I also noticed that the latest TWRP (2.8.7.0) has a resize partition option inside the Wipe section. What I want to know is, how can I use this to resize the system and data partitions so that 1GB+ isn't being wasted and unused. I'd really like to get that 1GB+ added to my data partition for apps.
I've tried using it. The only time it didn't spit out an error was after I wiped the system partition. It succeeded in "resizing" it after that, but it didn't change anything. The system partition remained the same size.
Click to expand...
Click to collapse
This it why the option is there:
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
jeffrey268 said:
This it why the option is there:
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
Click to expand...
Click to collapse
Thank you for the reply
If I understand you correctly, the feature's original intent is to resize /data partitions in the event the rom/system image treats a larger storage capacity device as a lower capacity one, ie. 64GB device is treated like 32GB so /data will only reflect 32GB minus (system image install size), wasting 32GB and leaving it inaccessible to the user.
However, it also seemed like you were saying I also could use it to resize my /system partition to a smaller size so CM12.1 (with it's ~900MB install size after Full TK-Gapps) will only leave ~50MB to ~100MB on /system instead of ~1.5GB. However, the question remains. How do I do this and can I reallocate the ~1.5GB to the /data partition for apps and internal storage? If this can't be done then I see no point in resizing /system to begin with as it will still be inaccessible to me as the user.
ToYeD said:
Thank you for the reply
If I understand you correctly, the feature's original intent is to resize /data partitions in the event the rom/system image treats a larger storage capacity device as a lower capacity one, ie. 64GB device is treated like 32GB so /data will only reflect 32GB minus (system image install size), wasting 32GB and leaving it inaccessible to the user.
However, it also seemed like you were saying I also could use it to resize my /system partition to a smaller size so CM12.1 (with it's ~900MB install size after Full TK-Gapps) will only leave ~50MB to ~100MB on /system instead of ~1.5GB. However, the question remains. How do I do this and can I reallocate the ~1.5GB to the /data partition for apps and internal storage? If this can't be done then I see no point in resizing /system to begin with as it will still be inaccessible to me as the user.
Click to expand...
Click to collapse
I read a few things online and it seems you need aan unlocked bootlader, the G3 bootloader is not unlockable, so you are probily out of luck maby you can ask in the Q&A thread of the rom you are using.
hi, with the new marshmallow roms we have very few available system space, in my phone i have 96mb after gapps and xposed, but we have a huge cache partition, 800mb of wich i am using only 26mb, 800 is kind of a waste, even the nexus 6 has a 260mb cache partition, is there any way to resize the cache partition to like 200mb and use the rest for the system? 600mb more to the system will help us with future and heavier updates