Database Develop

Need Some More Help Partitioned and loaded rom but internal mem is still under 32 sho

i used amon ra v1,5,2 because it is stable but i checked my internal mem and it says 32mb which is still regular phone mem
do i need ap2sd to get my 96mb or do i need to convert ex3 to ex4 or is there something im missing

What spl are you using?
Also, type
Code:
busybox df -h
in terminal and let us know the output.

I don't know how to tell which spl
But this is the output
My busy box kmoo sd Details $ su# busybox df -h Filesystem*************** Size***** Used Available Use% Mounted on tmpfs******************* 47.8M**** 12.0K**** 47.8M** 0% /dev tmpfs******************** 4.0M******** 0***** 4.0M** 0% /sqlite_stmt_journals/dev/block/mtdblock3 AO
So what do I do next

DroidFreek said:
I don't know how to tell which spl
But this is the output
My busy box kmoo sd Details $ su# busybox df -h Filesystem*************** Size***** Used Available Use% Mounted on tmpfs******************* 47.8M**** 12.0K**** 47.8M** 0% /dev tmpfs******************** 4.0M******** 0***** 4.0M** 0% /sqlite_stmt_journals/dev/block/mtdblock3 AO
So what do I do next
Click to expand...
Click to collapse
Doesn't look right . Your df -h output should look something like this
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 47.9M 12.0K 47.8M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_st
/dev/block/mtdblock3 90.0M 66.4M 23.6M 74% /system
/dev/block/loop0 512.0K 512.0K 0 100% /system/modules
/dev/block/loop1 2.8M 2.8M 0 100% /system/xb
/dev/block/mtdblock5 89.8M 27.4M 62.4M 30% /data
/dev/block/mtdblock4 30.0M 24.1M 5.9M 80% /cache
/dev/block/mmcblk0p2 457.3M 33.0M 400.0M 8% /system/sd
/dev/block/mmcblk0p2 457.3M 33.0M 400.0M 8% /data/dalv
/dev/block//vold/179:1
6.9G 6.3G 670.3M 91% /sdcard
where /system/sd is your apps2sd partition (if you have it) and /data is your internal storage.
I have 62megs free in my data, I'm not sure where you hear 96 megs but its complete unnecessary to have that much space free. I've yet to experience any slowdowns or low mem warnings. Also remember.... some devs put parts of their rom on /data partition and that will decrease your available space.
Also, there's absolutely NO WAY you should be getting low mem warning with 34 megs free. That only happens when you have less then 10 megs available. Apps2sd is the obvious choice if you want to have as much phone mem available as possible.

Your a real geniuos ty I got it to work but what is the secondary sd for what does it store and how can I access it I am currently using estrongs explorer

Don't know about estrongs... never used it. Rule of thumb, if it asks for SU access the first time you run it - then it will be able to access it.
I'll break it down for ya
Internal memory:
/system - your rom
/system/app - system files (google apps, dialer, contacts etc)
/system/**** - extra stuff that our devs include (thanks to them)
/data/app - non-protected apps
/data/app-private - protected apps
/data/dalvik-cache - working files for all apps
/data/data - your settings
/system/sd - aka your secondary partition, aka apps2sd is a part of your sdcard. Only accessible in Linux or in terminal. When you have apps2sd set up, your phone will bypass /data/app, data/app-private and /data/dalvik-cache and forward those files to /system/sd/app, /system/sd/app-private and /system/sd/dalvik-cache. It will still use /data/data for all of your settings. I know it's a lot of slashes there but it will start making sense as you progress with Android hacking.
If you want to see what's on secondary sd just type this in terminal
Code:
ls /system/sd
This will give you a print-out of the apps that are on your sd.
Anything else I'm forgeting?

Ok this is the new output
$ su# busybox df -h Filesystem*************** Size***** Used Available Use% Mounted on tmpfs******************* 47.8M**** 12.0K**** 47.8M** 0% /dev tmpfs******************** 4.0M******** 0***** 4.0M** 0% /sqlite_stmt_journals/dev/block/mtdblock3**** 67.5M**** 61.8M***** 5.7M* 92% /system/dev/block/loop0

Is it possible you can give me a list of all the commands for terminal

http://www.droidforums.net/forum/droid-hacks/26036-linux-commands-android.html
Try this, some basics.

want to make exact image of my whole os and all apps in it
Is it possible to make an exact image of of my whole os including the apps web bookmarks and etc

sort of like the program iamgeburn does for pc

yea a nandroid back up. check your recovery for a back up option

So i just head to recovery and choose nanodroid then choose backup right
after soing so where does it save to and how can i retrieve it after a complete wipe of sd and system

saved on your sdcard under nandroid.
To use it, in recovery select restore and choose the nadroid that you want to recover. Your now back to exactly where you were when you created it.
easy peasy.

[Q] How to release space in /system [JPK]

So... I've been messing around with framework-res.apk. To migrate the file onto the i9000 i rm the original, then cp the new version in. It looks like everytime I do this though, the filesystem never releases free space.
"du -ks /system/*" totals to 260552k, but "df -k /system" shows:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/stl9 282432 281316 1116 100% /system
So it appears like the last 3 or so framework-res.apk's haven't had their space released. I've had to move out some apps from /system/apps to copy in the last couple of framework-res.apk's.
Any suggestions as to how to release the free space?
(My guess is that I remount as rw before copying the file, but there are many processes with handles on the old file so the filesystem cant release the space until reboot, and with the reboot the filesystem is mounted as ro so it can't release the free space?)
** SOLVED **
followed bilboa1's advice on RFS errors in this thread : forum.xda-developers.com/showthread.php?t=797650&highlight=mount+%2Fsystem , fsck_msdos'd the /system partition, did a reboot and regained the free space:
/dev/block/stl9 275.8M 273.7M 2.2M 99% /system
# /system/bin/fsck_msdos -p -f /dev/block/stl9
# reboot
/dev/block/stl9 275.8M 267.2M 8.7M 97% /system

*** solution bump ***

Low Space / Memory even after a hard reset

Hi
I recently acquired a Nexus One that I'm having memory issues with. I'm running Gingerbread 2.3.4 (GRJ22). I've tried all sorts of options in erasing / clearing memory. After each of these attempts, it always only shows 13MB free. No extra applications are even installed!
I've done the following:
* Factory Data Reset
* Clear Storage during HBOOT
* Wipe data/factory reset during RECOVERY
* Wipe cache partition during RECOVERY
Any other ideas? I've recently rooted it too.

What does it read if you do
Code:
df -h | grep /data
in the terminal? (The line is called a pipe and on the computer is located on the backslash key '\' and comes up when you use shift. I don't know where it is on the stock keyboard, but on swype, it is under the 'D' key if you use shift and long press on 'D'.

There is a possibility that your internal memory is filled with bad sectors.
As noted above, please post the output of the "df -h" command, so it'll be more clear.

I have 19.45kb free with CM7 + gapps only (edit - that is for /system and that too only 40KB free).
when I give that df command in terminal I get
/dev/block/mtdblock5 196.3M 41.1M 155.2M 21% /data
what does that mean?

munchy_cool said:
I have 19.45kb free with CM7 + gapps only
when I give that df command in terminal I get
/dev/block/mtdblock5 196.3M 41.1M 155.2M 21% /data
what does that mean?
Click to expand...
Click to collapse
Just do
df -h
and you'll see the headings...

filesystem size used available use% mounted
/dev/block/mtdblock5 196.3M 41.1M 155.2M 21% /data
so that means I have 155.2M free on /data.
that's good but my /system is only 40.0k free (cm 7 +gapps) only ..bad sectors?

bassmadrigal said:
What does it read if you do
Code:
df -h | grep /data
in the terminal? (The line is called a pipe and on the computer is located on the backslash key '\' and comes up when you use shift. I don't know where it is on the stock keyboard, but on swype, it is under the 'D' key if you use shift and long press on 'D'.
Click to expand...
Click to collapse
I can't seem to install terminal thru the marketplace. I think the low memory is preventing any additional application installs. Is that possible?
Is there another method to access a shell prompt on the device?

im sure you can use adb so plug it in!

daftsynth said:
I can't seem to install terminal thru the marketplace. I think the low memory is preventing any additional application installs. Is that possible?
Is there another method to access a shell prompt on the device?
Click to expand...
Click to collapse
Doesn't CM7 already come with Terminal installed...check your app drawer.

What gapps are you using? Because CM7 on mine has 8.56MB free after having gapps installed and DarkTremor's a2sd. If you are using one of the gapps that adds gmail, maps, facebook, etc... then that is probably your problem. That is why we have the smaller gapps (and to have gapps that are independent of the screen resolution). All those separate apps can be downloaded from the market. The tiny gapps gives you all the apps and framework needed to get onto the market so you can download the other apps.
And yes, Terminal is normally included with CM7...
You should definitely have more free on /system on a CM7 install with gapps.

bassmadrigal said:
You should definitely have more free on /system on a CM7 install with gapps.
Click to expand...
Click to collapse
How much is CM 7 + gapps from CM team on the /system (coz I use gapps which has gmail etc).

I don't know as I also have DarkTremor's a2sd installed, but I still have over 8.5MB available... so I would guess just over 10MB free.

I had low space problems on my old Eris. I just rooted & installed GingerShedBread (CM7) & have over 100MB free after installing 45 apps to internal storage.
GSB also supports moving all apps to sd including system.
Sent from my Vortex using XDA App

bassmadrigal said:
What does it read if you do
Code:
df -h | grep /data
in the terminal? (The line is called a pipe and on the computer is located on the backslash key '\' and comes up when you use shift. I don't know where it is on the stock keyboard, but on swype, it is under the 'D' key if you use shift and long press on 'D'.
Click to expand...
Click to collapse
running df, I get this:
Filesystem Size Used Free Blksize
/dev 192M 32K 192M 4096
/mnt/asec 192M 0K 192M 4096
/mnt/obb 192M 0K 192M 4096
/system 145M 128M 16M 4096
/data 196M 183M 12M 4096
/cache 95M 2M 92M 4096
/mnt/sdcard 1G 536K 1G 4096
/mnt/secure/asec 1G 536K 1G 4096
I can't seem to run "df -h". I get this error:
-h: No such file or directory

tsaxda said:
I had low space problems on my old Eris. I just rooted & installed GingerShedBread (CM7) & have over 100MB free after installing 45 apps to internal storage.
GSB also supports moving all apps to sd including system.
Sent from my Vortex using XDA App
Click to expand...
Click to collapse
I've just done some partition tweaks and now have 200+ apps with 118 mb free... xD

daftsynth said:
running df, I get this:
Filesystem Size Used Free Blksize
/dev 192M 32K 192M 4096
/mnt/asec 192M 0K 192M 4096
/mnt/obb 192M 0K 192M 4096
/system 145M 128M 16M 4096
/data 196M 183M 12M 4096
/cache 95M 2M 92M 4096
/mnt/sdcard 1G 536K 1G 4096
/mnt/secure/asec 1G 536K 1G 4096
I can't seem to run "df -h". I get this error:
-h: No such file or directory
Click to expand...
Click to collapse
That is weird that the -h option isn't working. It works on mine. Anyway, I guess it is the default with the df command (designed to show things in MB or GB instead of just bytes).
Now we will figure out what is using all the space in your /data directory.
Code:
su
cd /data
du -hd 1
This will show a listing of your data directory with sizes next to each folder. Normally the data and app directories will be your largest (maybe app-private if you have a lot of private apps installed). You can cd into each of the directories and run the same command and if you add "| grep M" it will only show items that have a capital 'M' in it which will show you all the files that are rated in MB vs KB.
So the command would read
Code:
du -hd 1 | grep M
Hopefully you can then figure out what is taking up all your space.

bassmadrigal said:
That is weird that the -h option isn't working. It works on mine. Anyway, I guess it is the default with the df command (designed to show things in MB or GB instead of just bytes).
Now we will figure out what is using all the space in your /data directory.
Code:
su
cd /data
du -hd 1
This will show a listing of your data directory with sizes next to each folder. Normally the data and app directories will be your largest (maybe app-private if you have a lot of private apps installed). You can cd into each of the directories and run the same command and if you add "| grep M" it will only show items that have a capital 'M' in it which will show you all the files that are rated in MB vs KB.
So the command would read
Code:
du -hd 1 | grep M
Hopefully you can then figure out what is taking up all your space.
Click to expand...
Click to collapse
It appears that I have bad sectors. The actual total size of /data is less than what shows up in "df". Any ideas on how I would repair the bad blocks?
I was able to run Ubuntu and get my Nexus One recognized by it. How do I fix the nexus one /data partition from Ubuntu? I'm assuming I would need to mount it.
I'm able to mount the /sd partition but can't see the other partitions. GParted only sees the SD partition as well when its attached with USB Storage turned on.

I don't have my Ubuntu box to confirm, but you should be able to mount /data as rw through adb (you only need the Linux adb, not the whole sdk).
Should look something like:
$ adb-linux shell
$ su
# mount /dev/block/mtdblock5 /data yaffs2 rw
...I'm sure someone will correct me if I'm wrong.

danger-rat said:
I don't have my Ubuntu box to confirm, but you should be able to mount /data as rw through adb (you only need the Linux adb, not the whole sdk).
Should look something like:
$ adb-linux shell
$ su
# mount /dev/block/mtdblock5 /data yaffs2 rw
...I'm sure someone will correct me if I'm wrong.
Click to expand...
Click to collapse
I will try this when I get home. But when you execute the mount cmd above, wouldnt that just mount the partition locally on the nexus one?

daftsynth said:
I will try this when I get home. But when you execute the mount cmd above, wouldnt that just mount the partition locally on the nexus one?
Click to expand...
Click to collapse
Yes it would mount it locally. I don't know if you would be able to mount the data partition onto the computer due to it not passing any disc info other than the sdcard. But, while in adb, you could try and run an e2fsck. I am not sure on the exactness of these commands, but I think it would be something like this in adb while in recovery.
Code:
adb-linux shell
mount system
e2fsck -pcfv /dev/block/mtdblock5
You may need to issue an 'su' command, but I think when you use adb it automatically logs in as root.

[Q] How to increase internal phone storage?

I know this is a total noob thing to be asking, but I have researched and tried out various solutions and am still running out of space on my internal phone storage. I've installed the CM6.1 Magpie on a partitioned 8GB SD card with all apps set to install to sd-ext. I partitioned off 1GB for sd-ext, which seems to have worked as I can see some apps installed there.
I think I must have it set up incorrectly or incompletely despite my best efforts, as from what I understand I should be seeing my internal phone storage as being larger than 91.75MB. It's a problem as I now only have 15MB free, and it seems to be causing phone crashes.
I followed my_former_self's cm6.1.0 ds guide with magpie successfully, as far as I can tell. I am not certain if I also need to be using Firerat's customMTD... Can anyone offer some advice? I've done a lot of searching, but the info is so fragmented that I'm at a bit of a loss. (fr'instance, on the customMTD page the version is 1.5.6., but in the download area I see there's a 1.5.8 version too...)
Thanks for any help or pointers to any threads!
Phone: T-Mobile G1
ROM: Magpie-DS-CM6.1
Recovery: Amon-Ra

Can you please go into a terminal session
(or use
Code:
adb shell
) and type
Code:
df -h
and send the output here?
Probably you have done right everything, but your internal space is used by data ...
Sent from my Gingerbread on Dream using XDA App

df -h
AndDiSa said:
Can you please go into a terminal session
(or use
Code:
adb shell
) and type
Code:
df -h
and send the output here?
Probably you have done right everything, but your internal space is used by data ...
Sent from my Gingerbread on Dream using XDA App
Click to expand...
Click to collapse
I managed to free up some space last night by using Titanium's "integrate updates into ROM". That resulted in me having to reinstall Google Maps, but it did free up some space.
Here's my disk space usage:
Code:
$ adb -s HT94PGZ05646 shell
# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 55.0M 0 55.0M 0% /dev
tmpfs 55.0M 0 55.0M 0% /mnt/asec
/dev/block/mtdblock3 91.0M 90.8M 200.0K 100% /system
/dev/block/mtdblock5 91.8M 57.1M 34.7M 62% /data
/dev/block/loop0 4.0M 4.0M 0 100% /system/xbin
/dev/block/mmcblk0p2 915.1M 79.9M 786.4M 9% /sd-ext
/dev/block/mmcblk0p2 915.1M 79.9M 786.4M 9% /cache
/dev/block/mtdblock4 27.0M 1.1M 25.9M 4% /dev/cache
/dev/block/vold/179:1
6.5G 404.6M 6.1G 6% /mnt/sdcard
/dev/block/vold/179:1
6.5G 404.6M 6.1G 6% /mnt/secure/asec
"SD card & phone storage" shows internal phone storage available space as 34.67MB now, which seems to match /data.
I'm pretty sure I have all the pieces, I just can't put them together So if I *have* done things right, how do I get the system to mount /data elsewhere?

Custom MTD is not applied correctly, you have still a cache device with a size of 27 MB, which is unused at the moment.
To apply Custom MTD you should
Code:
echo "mtd 90 2" > /sdcard/mtdpartmap.txt
(probably mtd 91 2 would be better for you, because there are only 200kb free on /system)
then boot into recovery, do a nandroid+sd-ext or bart backup
then apply the recovery-v1.5.8-CustomMTD_S.zip
reboot to fastboot and do a
Code:
fastboot erase system -w
fastboot reboot recovery
then do a nandroid / bart restore
then flash the boot-v1.5.8-CustomMTD_S.zip
then reboot and you should be fine.

ah so!
AndDiSa said:
Custom MTD is not applied correctly, you have still a cache device with a size of 27 MB, which is unused at the moment.
To apply Custom MTD you should
Code:
echo "mtd 90 2" > /sdcard/mtdpartmap.txt
(probably mtd 91 2 would be better for you, because there are only 200kb free on /system)
then boot into recovery, do a nandroid+sd-ext or bart backup
then apply the recovery-v1.5.8-CustomMTD_S.zip
reboot to fastboot and do a
Code:
fastboot erase system -w
fastboot reboot recovery
then do a nandroid / bart restore
then flash the boot-v1.5.8-CustomMTD_S.zip
then reboot and you should be fine.
Click to expand...
Click to collapse
That's reassuring, your solutions reads like the general instructions I found on the firerat customMTD thread. That thread was a bit confusing and I was worried about mixing & matching things, especially given that the latest versions didn't match the versions in the thread. I shall report back!

Definitely an improvement!
AndDiSa said:
Custom MTD is not applied correctly, you have still a cache device with a size of 27 MB, which is unused at the moment.
To apply Custom MTD you should
Code:
echo "mtd 90 2" > /sdcard/mtdpartmap.txt
(probably mtd 91 2 would be better for you, because there are only 200kb free on /system)
then boot into recovery, do a nandroid+sd-ext or bart backup
then apply the recovery-v1.5.8-CustomMTD_S.zip
reboot to fastboot and do a
Code:
fastboot erase system -w
fastboot reboot recovery
then do a nandroid / bart restore
then flash the boot-v1.5.8-CustomMTD_S.zip
then reboot and you should be fine.
Click to expand...
Click to collapse
Excellent! I am now seeing 117MB for total space and 59.66MB free. However, I worry that this won't be enough in the future. Can you advise me on how to create more space? Or will it do so automagically?

mtdpartmap.txt not read?
AndDiSa said:
Custom MTD is not applied correctly, you have still a cache device with a size of 27 MB, which is unused at the moment.
To apply Custom MTD you should
Code:
echo "mtd 90 2" > /sdcard/mtdpartmap.txt
(probably mtd 91 2 would be better for you, because there are only 200kb free on /system)
then boot into recovery, do a nandroid+sd-ext or bart backup
then apply the recovery-v1.5.8-CustomMTD_S.zip
reboot to fastboot and do a
Code:
fastboot erase system -w
fastboot reboot recovery
then do a nandroid / bart restore
then flash the boot-v1.5.8-CustomMTD_S.zip
then reboot and you should be fine.
Click to expand...
Click to collapse
Hm... I am not sure it is reading mtdpartmap.txt, as the /system partition seems to be the same size:
Code:
# cat /sdcard/mtdpartmap.txt
mtd 91 2
# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 55.0M 0 55.0M 0% /dev
tmpfs 55.0M 0 55.0M 0% /mnt/asec
/dev/block/mtdblock3 91.0M 90.8M 200.0K 100% /system
/dev/block/mtdblock5 116.8M 57.1M 59.6M 49% /data
/dev/block/loop0 4.0M 4.0M 0 100% /system/xbin
/dev/block/mmcblk0p2 915.1M 79.9M 786.4M 9% /sd-ext
/dev/block/mmcblk0p2 915.1M 79.9M 786.4M 9% /cache
/dev/block/mtdblock4 2.0M 776.0K 1.2M 38% /dev/cache
/dev/block/vold/179:1
6.5G 807.9M 5.7G 12% /mnt/sdcard
/dev/block/vold/179:1
6.5G 807.9M 5.7G 12% /mnt/secure/asec
Any thoughts on that?

Hmm ... creating more internal space will be difficult, because the G1 has only 196MB
The only chance you have, if this isn't sufficient for you: use a2ext, i.e. put all applications to sd card and keep only the data ofthe applications on internal memory. I am doing so (~100 application installed) and normally I've still around 30MB free.
If that is still not sufficient for you, you can use data2sd. Firerat's all in one patch should work with your rom. Choosing the ddb option will move app data to sd-ext and will free internal space. Disadvantage of this option: if you have a slow sd card you will notice a performance decrease.

AndDiSa said:
Hmm ... creating more internal space will be difficult, because the G1 has only 196MB
The only chance you have, if this isn't sufficient for you: use a2ext, i.e. put all applications to sd card and keep only the data ofthe applications on internal memory. I am doing so (~100 application installed) and normally I've still around 30MB free.
If that is still not sufficient for you, you can use data2sd. Firerat's all in one patch should work with your rom. Choosing the ddb option will move app data to sd-ext and will free internal space. Disadvantage of this option: if you have a slow sd card you will notice a performance decrease.
Click to expand...
Click to collapse
Thanks for the info. I'm already using a2ext, as it's built into Magpie and I've locked app installations to ext in the cyanogen mod settings. However, if you're running 100+ apps and having no probs, I doubt I will either. Thanks again!

[THINK TANK] Extending the CM7/MIUI /datadata partition/folder/storage

I like CM7 and would like to use it but the number of apps I have is probably greater than most of you guys......the /datadata folder only has like 150mb of app data storage and once I install like 100 apps it gets full and starts forceclosing....I know the Vibrant has 2gb of app storage but only in TouchWiz ROMs you can use the 2GBs not in AOSP....
Is there anyway to extend it? or atleast move the app folders somewhere to whe I can install all my apps and still have like 1GB left over...like I do in TW ROMs?
This isn't a Q and A ..it's sorta a discussion.

I've been doing a bunch of searching on this and it seems like all Galaxy S's on CM are having this problem. I'm assuming the fix is just as simple as editing a file somewhere but even that is too hard for me. Any help on this issue would be much appreciated.
Sent from my SGH-T959 using XDA App

It's the only thing keeping me from switching to it

data2sd script...

t1h5ta3 said:
data2sd script...
Click to expand...
Click to collapse
Well has anyone ever implemented it on CM for Galaxy S? From what I was reading this might fix a bunch of problems, but I have no idea how to actually use it to suit our needs.
Sent from my SGH-T959 using XDA App

Yea data2sd is necessary!
I can't seem to know how to apply this.....

Isn't there an option under "applications", that lets you install the apps on SD??

you can manually move apps to the sd or set it to just have it always download to the sd, I dont even have an external sd card and have 5 gb of space left

No that's not it......the APP partition is enough....the app data folder isnt and it is the problem..
basically in cm7, the 2gbs arent even used nor will ever

vinnydakid said:
I've been doing a bunch of searching on this and it seems like all Galaxy S's on CM are having this problem. I'm assuming the fix is just as simple as editing a file somewhere but even that is too hard for me. Any help on this issue would be much appreciated.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Without actually checking out the source code for cyanogenmod + android, I wouldn't exactly know. It is most likely a issue of partitioning. This would be changed at the source code level, not at the user end.

Because this thread has been stale, I've been digging into the reasoning of why samsung based phones have so ittle space in /data/data (i.e. /datadata). The most obvious way to compare this is through the command df -h.
Here is the output of df -h for the samsung vibrant (on CM7 nightly):
Code:
# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 165.0M 32.0K 165.0M 0% /dev
tmpfs 165.0M 0 165.0M 0% /mnt/asec
tmpfs 165.0M 0 165.0M 0% /mnt/obb
/dev/block/mtdblock2 187.5M 142.3M 45.2M 76% /system
/dev/block/mtdblock3 80.0M 36.3M 43.7M 45% /cache
/dev/block/mtdblock5 16.0M 14.3M 1.7M 89% /radio
/dev/block/mmcblk0p2 1.8G 591.4M 1.3G 31% /data
/dev/block/mtdblock6 172.0M 121.5M 50.5M 71% /datadata
/dev/block/mtdblock4 12.5M 6.6M 5.9M 53% /efs
/dev/block/vold/179:1
13.0G 4.2G 8.8G 32% /mnt/sdcard
/dev/block/vold/179:1
13.0G 4.2G 8.8G 32% /mnt/secure/asec
/dev/block/vold/179:9
3.7G 1.8G 1.9G 49% /mnt/emmc
Here is df -h for the HTC g2 (vision; CM7 Nightly):
Code:
# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 184.0M 32.0K 183.9M 0% /dev
tmpfs 184.0M 0 184.0M 0% /mnt/asec
tmpfs 184.0M 0 184.0M 0% /mnt/obb
/dev/block/mmcblk0p25
409.2M 147.4M 261.9M 36% /system
/dev/block/mmcblk0p26
1.3G 217.7M 1.0G 18% /data
/dev/block/mmcblk0p27
198.3M 39.5M 148.5M 21% /cache
/dev/block/mmcblk0p28
19.9M 14.7M 5.2M 74% /devlog
/dev/block/vold/179:65
14.9G 2.3G 12.6G 15% /mnt/sdcard
/dev/block/vold/179:65
14.9G 2.3G 12.6G 15% /mnt/secure/asec
Notice the difference? Apparently on samsung branded phones, the /data/data folder is on its *own partition*, formatted YAFFS2. On HTC based phones, the /data/data folder is not on its own partition, but apart of the /data mount. For some reason, the developers decided to put it in its own partition, vs. the standard convention.
Also, here is a comparision of mount points for the Vision (init.vision.rc) and Aries-common (shared device config; is the same in the init.vibrantmtd.rc):
Vision:
Code:
mkdir /system
mkdir /data 0771 system system
mkdir /cache 0770 system cache
mkdir /devlog 0700 root root
mount ext4 /dev/block/mmcblk0p25 /system wait ro barrier=1
mount ext4 /dev/block/mmcblk0p26 /data wait noatime nosuid nodev barrier=1 noauto_da_alloc
mount ext4 /dev/block/mmcblk0p27 /cache wait noatime nosuid nodev barrier=1
mount ext4 /dev/block/mmcblk0p28 /devlog wait noatime nosuid nodev barrier=1
Vibrantmtd:
Code:
mkdir /radio 0775 radio radio
mount yaffs2 [email protected] /system
mount yaffs2 [email protected] /system ro remount
mount yaffs2 [email protected] /cache
mount yaffs2 [email protected] /radio
mount ext4 /dev/block/mmcblk0p2 /data wait nosuid nodev noatime nodiratime noauto_da_alloc
mount yaffs2 [email protected] /datadata
Honestly, what I'm wondering, is why is /data/data not apart of the /data partition?

compuguy1088 said:
Because this thread has been stale, I've been digging into the reasoning of why samsung based phones have so ittle space in /data/data (i.e. /datadata). The most obvious way to compare this is through the command df -h.
Here is the output of df -h for the samsung vibrant (on CM7 nightly):
Code:
# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 165.0M 32.0K 165.0M 0% /dev
tmpfs 165.0M 0 165.0M 0% /mnt/asec
tmpfs 165.0M 0 165.0M 0% /mnt/obb
/dev/block/mtdblock2 187.5M 142.3M 45.2M 76% /system
/dev/block/mtdblock3 80.0M 36.3M 43.7M 45% /cache
/dev/block/mtdblock5 16.0M 14.3M 1.7M 89% /radio
/dev/block/mmcblk0p2 1.8G 591.4M 1.3G 31% /data
/dev/block/mtdblock6 172.0M 121.5M 50.5M 71% /datadata
/dev/block/mtdblock4 12.5M 6.6M 5.9M 53% /efs
/dev/block/vold/179:1
13.0G 4.2G 8.8G 32% /mnt/sdcard
/dev/block/vold/179:1
13.0G 4.2G 8.8G 32% /mnt/secure/asec
/dev/block/vold/179:9
3.7G 1.8G 1.9G 49% /mnt/emmc
Here is df -h for the HTC g2 (vision; CM7 Nightly):
Code:
# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 184.0M 32.0K 183.9M 0% /dev
tmpfs 184.0M 0 184.0M 0% /mnt/asec
tmpfs 184.0M 0 184.0M 0% /mnt/obb
/dev/block/mmcblk0p25
409.2M 147.4M 261.9M 36% /system
/dev/block/mmcblk0p26
1.3G 217.7M 1.0G 18% /data
/dev/block/mmcblk0p27
198.3M 39.5M 148.5M 21% /cache
/dev/block/mmcblk0p28
19.9M 14.7M 5.2M 74% /devlog
/dev/block/vold/179:65
14.9G 2.3G 12.6G 15% /mnt/sdcard
/dev/block/vold/179:65
14.9G 2.3G 12.6G 15% /mnt/secure/asec
Notice the difference? Apparently on samsung branded phones, the /data/data folder is on its *own partition*, formatted YAFFS2. On HTC based phones, the /data/data folder is not on its own partition, but apart of the /data mount. For some reason, the developers decided to put it in its own partition, vs. the standard convention.
Also, here is a comparision of mount points for the Vision (init.vision.rc) and Aries-common (shared device config; is the same in the init.vibrantmtd.rc):
Vision:
Code:
mkdir /system
mkdir /data 0771 system system
mkdir /cache 0770 system cache
mkdir /devlog 0700 root root
mount ext4 /dev/block/mmcblk0p25 /system wait ro barrier=1
mount ext4 /dev/block/mmcblk0p26 /data wait noatime nosuid nodev barrier=1 noauto_da_alloc
mount ext4 /dev/block/mmcblk0p27 /cache wait noatime nosuid nodev barrier=1
mount ext4 /dev/block/mmcblk0p28 /devlog wait noatime nosuid nodev barrier=1
Vibrantmtd:
Code:
mkdir /radio 0775 radio radio
mount yaffs2 [email protected] /system
mount yaffs2 [email protected] /system ro remount
mount yaffs2 [email protected] /cache
mount yaffs2 [email protected] /radio
mount ext4 /dev/block/mmcblk0p2 /data wait nosuid nodev noatime nodiratime noauto_da_alloc
mount yaffs2 [email protected] /datadata
Honestly, what I'm wondering, is why is /data/data not apart of the /data partition?
Click to expand...
Click to collapse
because leaving it on the moviNAND chip (even on ext4) is ****ing slow as balls. If you want, you can go back to stock Samsung ROM's where it's inside the /data partition and watch your phone crawl to a halt after a few days, even with voodoo lagfix (or any number of file systems). The choice becomes, do you want something fast and a good user experience and hope users actually think about what they're installing instead of being brain-dead "install ALL THE APPS" people... or have a miserable user experience for everyone to protect the few people who feel the need to install 150 apps on a phone (and then claim all are necessary)

Kaik541 said:
because leaving it on the moviNAND chip (even on ext4) is ****ing slow as balls. If you want, you can go back to stock Samsung ROM's where it's inside the /data partition and watch your phone crawl to a halt after a few days, even with voodoo lagfix (or any number of file systems). The choice becomes, do you want something fast and a good user experience and hope users actually think about what they're installing instead of being brain-dead "install ALL THE APPS" people... or have a miserable user experience for everyone to protect the few people who feel the need to install 150 apps on a phone (and then claim all are necessary)
Click to expand...
Click to collapse
That clarifies that reasoning. If there is that limitation, something needs to be implemented in code preventing applications from going outside of the max /datadata space (i.e. automated cleaning of app caches). Having the phone repeatedly crash over and over because of a lack of space in /datadata, isn't the best way to handle the situation.
Edit:
Doing df -h | grep -i datadata, works for many people (like me), but not everyone is command line savvy.
Edit2: I do not have 150 apps installed...but there are applications that store a decent ammount of data in the /datadata partition (youtube, facebook). This results in a juggling act just to have ~50 applications on the phone at one time. In my opinion, if you think that it should not be on the moviNAND, then the data partition should be mounted as well to the [email protected] partition. Like any other android device, this would work properly, and would prevent the severe strings of app crashes from the lack of space in /data/data.

compuguy1088 said:
That clarifies that reasoning. If there is that limitation, something needs to be implemented in code preventing applications from going outside of the max /datadata space (i.e. automated cleaning of app caches). Having the phone repeatedly crash over and over because of a lack of space in /datadata, isn't the best way to handle the situation.
Edit:
Doing df -h | grep -i datadata, works for many people (like me), but not everyone is command line savvy.
Edit2: I do not have 150 apps installed...but there are applications that store a decent ammount of data in the /datadata partition (youtube, facebook). This results in a juggling act just to have ~50 applications on the phone at one time. In my opinion, if you think that it should not be on the moviNAND, then the data partition should be mounted as well to the [email protected] partition. Like any other android device, this would work properly, and would prevent the severe strings of app crashes from the lack of space in /data/data.
Click to expand...
Click to collapse
except the slowest part of loading an application is what's pulled from /data/data, not from /data/app (or app-private). On top of that, it would limit our /data partition to ~170 MB for both /data/app(-private) and /data/data, which would mean like 15 apps total for everyone... again, creating a miserable user experience for all. Then what? we relegate mmcblk0p1 to...? /sdcard? /emmc? /wastedinternalstorage? it can't simply be "merged" into the other things. if you don't know how to manage your apps/space, then that's on you. every partition will have this same failing, android has no way of verifying "out of space" besides the /cache and /data partitions (and even then, it only goes "oops out of space" when it already fails). Putting /data/data on a faster partition (that other phones don't HAVE to make this decision like we did) over putting it inside /data is monumentally different on our phone. we're the only device in CyanogenMod history that went from one partition layout format (BML) to another (MTD). Sure, others have resized their MTD partitions (HardSPL on Dream/Sapphire fore example), but they were already on MTD. Ours required re-working the way the phone even *exists*, on top of that, there are partitions and spaces we are literally incapable of editing or modifying.
basically, while it's easy to say "meh, I don't like this way because it makes my life harder", for 95% of users, it's the far more optimal choice and leads to a far superior user experience. if you are technical enough to install CM, you should be technical enough to know how to run a simple command from terminal emulator (which is included in CM by default).

Kaik541 said:
except the slowest part of loading an application is what's pulled from /data/data, not from /data/app (or app-private). On top of that, it would limit our /data partition to ~170 MB for both /data/app(-private) and /data/data, which would mean like 15 apps total for everyone... again, creating a miserable user experience for all. Then what? we relegate mmcblk0p1 to...? /sdcard? /emmc? /wastedinternalstorage? it can't simply be "merged" into the other things. if you don't know how to manage your apps/space, then that's on you. every partition will have this same failing, android has no way of verifying "out of space" besides the /cache and /data partitions (and even then, it only goes "oops out of space" when it already fails). Putting /data/data on a faster partition (that other phones don't HAVE to make this decision like we did) over putting it inside /data is monumentally different on our phone. we're the only device in CyanogenMod history that went from one partition layout format (BML) to another (MTD). Sure, others have resized their MTD partitions (HardSPL on Dream/Sapphire fore example), but they were already on MTD. Ours required re-working the way the phone even *exists*, on top of that, there are partitions and spaces we are literally incapable of editing or modifying.
basically, while it's easy to say "meh, I don't like this way because it makes my life harder", for 95% of users, it's the far more optimal choice and leads to a far superior user experience. if you are technical enough to install CM, you should be technical enough to know how to run a simple command from terminal emulator (which is included in CM by default).
Click to expand...
Click to collapse
It was a crazy shot in the dark. I was actually thinking of the possiblity of having a service clear the caches of all programs on boot. I *have* been managing my space that way. For some apps (*cough* facebook), they decide to use 20+ megabytes of space that is not cache. I understand your justification, but If this is the way things are going to be for Aries based phones (Galaxy S, Fascinate, Vibrant, etc), this should be mentioned in the OT. People should know before flashing this rom, that manual management is a necessary.

Ive been on simply honey for about 2 weeks and have shortened to 273 apps and it is still fast....I don't notice lag....maybe I'm crazy I don't notice the difference between full of apps and newly flashed simply honey.....am I crazy?
Sent from my SGH-T959 using XDA Premium App

Alanrocks15 said:
Ive been on simply honey for about 2 weeks and have shortened to 273 apps and it is still fast....I don't notice lag....maybe I'm crazy I don't notice the difference between full of apps and newly flashed simply honey.....am I crazy?
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
Unless Simply Honey is based on Cyanogen 7, this issue does not apply to you. What is being discussed is the nightlies for the upcoming CM 7.1 relating to a partitioning decision. Based on what I've read and seen in the source code, is a dirty hack. It allows for faster performance, at the cost of the need to micro manage applications use of a limited /datadata. If this is going to reach an actual stable realase, this needs to be reverted. The mass majority of people do not have the time, nor the desire to every so often manually clean out data and caches of "/datadata" hogs. Most people who are still using the galaxy s line of phones have gotten use to the slow read and write speeds of the moviNAND by now....
Kaik541 said:
basically, while it's easy to say "meh, I don't like this way because it makes my life harder", for 95% of users, it's the far more optimal choice and leads to a far superior user experience. if you are technical enough to install CM, you should be technical enough to know how to run a simple command from terminal emulator (which is included in CM by default).
Click to expand...
Click to collapse
For many phones, including the galaxy S line, it is *very* easy to install CM (no command line use needed). I understand your (and the CM maintainers) decision to do this. I also see the reasons *not to*, in the eyes of average users. I think the performance penalties for more space in /datadata, are worth more than the need to have users digging around the phone system every other week. This is my opinion, based on my educational background and experience.

nah I read how the other Guy said how it is slow even with lagfix if you get a bunch of apps .....
Sent from my SGH-T959 using XDA Premium App

Alanrocks15 said:
nah I read how the other Guy said how it is slow even with lagfix if you get a bunch of apps .....
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
That is true on any normal vibrant rom. For cm7.1 based roms, they basically moved the most heavily read and written directory to high speed flash. The cm developers solved one problem (slowness), and created a completely new issue (lack of space in /datadata). This is what he was trying to say, in a nutshell.
Sent from my SGH-T959 using Tapatalk

Okay i didn't really understand the part where you put all those values and things so what will happen? Is this problem going to remain?