There are plenty of smart devs for the Eris, but almost none have touched the /cache, /data, /system memory portion of our phones. XTR, I think was the first, did with his Cache2Cache programing, which is very cool. It is also currently limited to his nice ROMs. But this is only for cache usage from my understanding. Granted, messing with this MTD area may brick your phone (but so can rooting hehe).
Anyone want to port this over to the Eris?
http://forum.xda-developers.com/showthread.php?t=806321
Eris stock has roughly:
Cache @ 130MB (I dont think we need that much)
System @ 160MB
Data @ 170MB
basically I used this tool on my sisters Desire, and increased the amount of memory for the /data folder (for apps) reduced the cache, and system as follows:
OEM:
System @ 250MB
Cache @ 40Mb
Data @ 147MB
AFTER:
System @ 160MB
Cache @ 35MB
Data @ 242MB
anyone up for the challenge? IF you want more space for apps, and standard caching you should just vote yes here. If enough of us vote for this, maybe a dev will take the challenge to heart.
+1
Sent from my ERIS using XDA App
Here's my current space usage summary:
Code:
# df /system /data /cache
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mtdblock3 174080 103240 70840 59% /system
/dev/block/mtdblock5 163328 118560 44768 73% /data
/dev/block/mtdblock4 133120 38432 94688 29% /cache
This is a CELBFroyo 4.1 Eris, 40+ apps, no movement of anything to the SD card. I don't accumulate E-mails, SMS/MMS, or call logs. Nuke 'em every so often an move along.
So, judging from this single snapshot - I could stand to give up space in both /system and /cache to get a litte more (or a lot more!) /data. But I'm honestly not hurting for anything - I still have 44 MB free in /data.
Those three partitions (system-cache-data) are contiguous in the Eris:
http://forum.xda-developers.com/attachment.php?attachmentid=431912&d=1288689612
The methods described in the URLs you provided work for the Eris, but (obviously) the offsets and partition sizes need to be adjusted correctly to account for the Eris flash memory layout. The from-the-factory Flash memory layout can be found here
I have unpacked (split_bootimg.pl) and repacked (mkbootimg) Amon_RA's recovery, injecting up to 14 (yes, the Eris has 14 partitions) partition definitions in the kernel command line simultaneously, and everything boots up just fine (and /system, /data, and /cache) all mount just fine doing that.
e.g.
Code:
[ 2.845275] allocated dma buffer at ffa47000, dma_addr 2482b000
[ 2.845489] read CFG0 = aa5400c0, CFG1 = 8744a
[ 2.845520] CFG0 = e85408c0, CFG1 = 8744a
[ 2.845550] CFG0: cw/page=3 ud_sz=516 ecc_sz=10 spare_sz=0 num_addr_cycles=5
[ 2.845642] NAND_READ_ID = 5501bcec
[ 2.845855] status: c03120
[ 2.845855] nandid: 5501bcec maker ec device bc
[ 2.845947] CFG0: cw/page=3 ud_sz=512 ecc_sz=10 spare_sz=4
[ 2.846038] DEV_CMD1: f00f3000
[ 2.846130] <6>NAND_EBI2_ECC_BUF_CFG: 1ff
[ 2.846160] flash_id: 5501bcec size 20000000
[ 2.846282] 14 cmdlinepart partitions found on MTD device msm_nand
[ 2.846313] Creating 14 MTD partitions on "msm_nand":
[ 2.846343] 0x00001ff60000-0x000020000000 : "misc"
[ 2.848449] 0x000002c60000-0x000003160000 : "recovery"
[ 2.854888] 0x000003160000-0x0000033e0000 : "boot"
[ 2.859344] 0x0000033e0000-0x00000dde0000 : "system"
[ 3.054595] 0x00000dde0000-0x000015fe0000 : "cache"
[ 3.214691] 0x000015fe0000-0x00001ff60000 : "userdata"
[ 3.393402] 0x000000000000-0x000002980000 : "radio"
[ 3.440734] 0x000002980000-0x0000029a0000 : "gap"
[ 3.441955] 0x0000029a0000-0x000002a60000 : "hboot"
[ 3.443969] 0x000002a60000-0x000002aa0000 : "misc3"
[ 3.445556] 0x000002aa0000-0x000002ae0000 : "mfg"
[ 3.447021] 0x000002ae0000-0x000002ba0000 : "sp1"
[ 3.449096] 0x000002ba0000-0x000002c00000 : "misc2"
[ 3.450714] 0x000002c00000-0x000002c60000 : "mfg2"
The arguments to "mkbootimg" for the "standard" layout of the Eris can be found here - all you need to do is modify the sizes and offsets appropriately to get the desired sizes.
[SIZE=+4]BUT! ...[/SIZE] ( <- that'a a big but! )
...there is a problem that you need to be aware of.
This hack does not alter the actual partition table stored in Flash Memory. So, you could re-package a custom recovery (Amon_RA or ClockworkMod) so that it had your new (desired) sizes for /system, /cache, /data, and flash it to your recovery, and that would allow you to flash things to the newly sized partitions...
[SIZE=+2]...but you would also need to do this for the boot image of every ROM you wanted to use![/SIZE]
That is to say, you need to provide the same kernel command line to every bootable image on the phone - both the recovery partition image, and the boot partition image.
It would be a much easier go if the actual partition table was written, rather than overriding the "real" partition table with kernel command line arguments - then you would be free to use whatever recovery image and whatever ROM you wanted without hassle; doing it this way requires that for every ROM you might want to try, you:
1 unpack the ROM
2 split_bootimg.pl on the boot.img
3 mkbootimg (with the mtdparts=msm_nand: kernel command line arguments )
4 re-zip the ROM
5 re-sign the ROM.
This could all be automated with some scripting, but it is still a bit of a hassle for the average user.
Maybe to gauge relevancy we could have folks post up their results for
Code:
adb shell df /system /cache /data
to get a sense of how often people are really bumping in to memory problems.
bftb0
Thought I'd share haven't really ran into much storage space/memory issues since I've had my Eris.
Here's a df -h /system /cache /data for thought. I'm using FroShedYo Vanilla. Mainly use the new Gingerbread KB and a metamorph theme and a few games and Launcher Pro. Haven't really used the SD install apps either.
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock3 170.0M 109.1M 60.9M 64% /system
/dev/block/mtdblock4 130.0M 55.5M 74.5M 43% /cache
/dev/block/mtdblock5 159.5M 65.7M 93.8M 41% /data
Here's adb df:
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mtdblock3 174080 103796 70284 60% /system
/dev/block/mtdblock4 133120 51032 82088 38% /cache
/dev/block/mtdblock5 163328 33508 129820 21% /data
adb df -h:
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock3 170.0M 101.4M 68.6M 60% /system
/dev/block/mtdblock4 130.0M 49.8M 80.2M 38% /cache
/dev/block/mtdblock5 159.5M 32.7M 126.8M 21% /data
I'm always bumping into my memory usage no matter what rom I use. I'm always shifting downloaded apps from /data to /system, which is why I'm looking to realllocate the partition memory usage.
I'm running at around 15MB free space on /Data, but after work emails and maps and caching I get the fun low memory message. Granted I like to have a crap load of apps.... i'll get my memory allocation details later when I get a chance.
Izeltokatl said:
XTR, I think was the first, did with his Cache2Cache programing, which is very cool. It is also currently limited to his nice ROMs.
Click to expand...
Click to collapse
OT, but just wanted to clarify that Cache2Cache is not limited to xtr's ROMs. Besides some other ROMs that include it by default, you can also flash the old style Apps2SD even if you don't use it for the Ext3 Apps2SD function, and use it to enable Cache2Cache. I do on every CM6.x Froyo ROM that I flash that doesn't have Cache2Cache by default, and I don't use the Ext3 Apps2SD, instead using Froyo's native Apps2SD.
I'd like to ask you some questions
1)Which file system is the fastest?
2)How are the separate partitions tagged(I mean /data, /system etc.)?
My best (fastest) guess would be ext2. I'm using it and it looks the fastest for our device. You may try using ext4, but then it takes some space and time for keeping up the file system journal.
As for partitions:
/dev/block/stl6 /system
/dev/block/stl7 /data
/dev/block/stl8 /cache
/dev/block/stl4 /efs
Hi everyone,
I need help, I can't mount /system / data /cache on twrp 3.0.2
Any idea about that? Now, i can't use my phone
I've been having problem with Honor 4x(kirin 620) internal memory randomly filling without me even using phone. I realized it was dalvik-cache that was filling memory. It was taking like ~700MB after a month use.
I'm using ksrt12 rom AEX v4.6 for Honor 4X. There is a lot of free space in other partitions like /cust /cache /system so I did some searching and found similar discussion with an older/other device about moving dalvik-cache to /system partition and creating symlink to /data. This way you could free some space and put that wasted space in other partitions in some good use without re-partitioning your device.
Make dalvik-cache to take storage space form /cust and /cache
1. Make script like this and put it in /etc/init.d
Give it permissions 700 (rwx-------)
Code:
#!/system/bin/sh
mount -o remount,rw /cust
# If folders don't exist, create them
[ -d /cust/arm64 ] || mkdir /cust/arm64
[ -d /cache/arm ] || mkdir /cache/arm
# Making sure that dalvik-cache in /data is empty
rm -r /data/dalvik-cache/{arm64,arm}
mkdir /data/dalvik-cache/{arm64,arm}
# Set permissions
chmod 711 /cust/arm64 /cache/arm
# The part that actually does something useful
mount --bind,rw /cust/arm64 /data/dalvik-cache/arm64
mount --bind,rw /cache/arm /data/dalvik-cache/arm
2. Reboot to recovery and wipe dalvik-cache, cache and cust.
3. Reboot to system
4. Done!
If you want to wipe dalvik-cache you must wipe /cache and /cust
-deleted
updated thread to a bit easier solution
Anybody knows how to mount this partitions? i want to use a NFC software but it says that vendor couldn't mount.