Root Froyo Cache2Cache increase useable space

[IzelTokatl]

all you early adopters here is something you want to play with:

Froyo Cache2Cache
[SCRIPT][1/22/2011] BETA Simple Froyo Cache2Cache - xda-developers

in a nut shell this script will work on just about any Froyo rom. It moves the cache from /data/ to /cache/, all internal memory. What does this mean? It means you will have more space for downloadable apps. I went from 25MB of free space to now 65MB of free space in /Data/.

If you have no memory issues, this isn't that big of a deal, but if you do like me, its a GREAT deal. This also allows you not have to deal with apps2SD in most cases.

 

[doogald]

I love this as well (as I posted on xda). Just be aware that if you install this, everytime that you flash an update the ROM that you are running you will need to re-flash the cache2cache .zip file before you restart the phone.

 

[jae_63]

This looks very cool and helpful since I'm extremely memory-starved (even with Apps2SD), but I'm puzzled since there are two different dalvik-cache directories on my rooted KaosFroyo 37 Eris on which I've not yet attempted cache2cache:

# df -h /cache
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock4 130.0M 90.4M 39.6M 60% /cache


# df -h /data
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock5 159.5M 135.5M 24.0M 85% /data

# du -sh /cache/dalvik-cache
39.6M /cache/dalvik-cache

# du -sh /data/dalvik-cache
53.4M /cache/dalvik-cache
​

Why are there two different dalvik-cache directories on my system? And which one is really being used? And is it a coincidence that the amount of free space reported on /cache corresponds exactly to the size of /cache/dalvik-cache?

Could I safely make this cache2cache migration? It looks a bit dicey to me.


Thanks ...

 

[doogald]

I'm not sure how this would work on Kaos. But basically what the script does is it checks to see if there is a /cache/dalvik-cache folder and creates one, and sets proper permissions, if there is not; it then copies all of /data/dalvik-cache to /cache/dalvik-cache; it then deletes /data/dalvik-cache; and it then creates a symbolic link to /cache/dalvik-cache in /data/dalvik-cache, so any app looking to place caches in /data/dalvik-cache will find files (which happen to be in /cache/dalvik-cache instead).

I do know that it works fine on CELB and GingerShedBread. I'd make a Nandroid backup and try it out to see what happens on Kaos.

 

[cmajpwc]

I do know that it works fine on CELB and GingerShedBread. I'd make a Nandroid backup and try it out to see what happens on Kaos.

It didn't work for me on GSB. I flashed it, and got the same space I had before. Not a single mb gained. Oh well.

 

[IzelTokatl]

It didn't work for me on GSB. I flashed it, and got the same space I had before. Not a single mb gained. Oh well.

This does work on GSB, 1.2 and 1.3, you may want to try again? it's been running fine for me and several others.

 

[IzelTokatl]

This looks very cool and helpful since I'm extremely memory-starved (even with Apps2SD), but I'm puzzled since there are two different dalvik-cache directories on my rooted KaosFroyo 37 Eris on which I've not yet attempted cache2cache:

# df -h /cache
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock4 130.0M 90.4M 39.6M 60% /cache


# df -h /data
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock5 159.5M 135.5M 24.0M 85% /data

# du -sh /cache/dalvik-cache
39.6M /cache/dalvik-cache

# du -sh /data/dalvik-cache
53.4M /cache/dalvik-cache
​

Why are there two different dalvik-cache directories on my system? And which one is really being used? And is it a coincidence that the amount of free space reported on /cache corresponds exactly to the size of /cache/dalvik-cache?

Could I safely make this cache2cache migration? It looks a bit dicey to me.


Thanks ...

this will not currently work on KaosFroyo, the reason is due to him not having the boot import call in his builds. This is the reason the batt tweak wont work either as well as one other script. I sent him a message about it with the fixes to implement, kaos said he wasn't aware and apparently nobody bothered to tell him that they cared either. He said he would try and get the import call working on the next release, so we'll see.