Develop Bugs

Cache Partition Size ?'s

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

Custom MTD Partions Query

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

Dalvik to system partition script ?

Is this possible with the HOX.. given the size of the system partition and the free space available with some roms, could help to free up.space on the internal storage (data) partition.
Is there a script available ?

Titanium Backup can do something like this if you're rooted.

That only does system dalvik, integrates into Rom, recreating odex files..
I'm talking about creating a script so all dalvik is stored on a system partition.
Symlnked or hard linked,..
ie rather that data/dalvik-cache
Have it as system/dalvik-cache
I had a script for my DHD that moved the dalvik to the cache partition, I suggested the system partition with the HOX because of its has so much free space that would be more than adequate to store it..
I might have a look at this script later tonight if I still have it, and see if I can modify it, to work on the HOX for the system partition..

Figured it out..
I have added a patch to the Sense version of the ncx-217_v4_1 Kernel that stores the Dalvik Cache on the System Partition, therefore freeing up some space on the internal storage..
The System Partition is set as Rewriteable on boot to allow this to work..
I know some people say for security reasons System Partition should be left as Read Only.. But then my argument against that is why go to the trouble to root the device in the first place then. ?
Before installing this makes sure you have wiped the Dalvik Cache in recovery..
to install..
Code:
fastboot flash boot ncx_217_v4_1_SENSE_D2S.img
fastboot erase cache
The modules for this kernel don't require to be re-flashed if you have done prior to this already... But I did anyway just to be on the safe side..
Bare in mind if you flash any other kernel after this.. your Dalvik cache will go back to the stock setting, so if you do not have enough space on your Data partition you could run into problems..
To get around this you could always unpack the new kernel, add the patch to the 'init.rc' file then re pack..
For information on how to unpack and repack Boot.img files refer to this thread HERE
For information on how to apply the patch, read the article HERE

[Q][UnofficialCM7.2] Resize Dalvik Cache Partition Memory

First time I rooted this phone I had to set the size for the dalvik. I don't remember how I did that but I'm pretty sure I've allocated 512 of space and I believe it is way too much.
Now the dalvik is taking up so system memory that I had to move it to Sd-ext and the phone had become laggy and unresponsive.
Is there a way I can reset the dalvik so it won't grow any larger than 100Mb?
Cheers

[Question] Resizing partitions with TWRP

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.