Database Develop

apps2sd working, but /data size increasing?

In short: When I install a new app, the app gets installed in /system/sd just fine (/data/app and /data/app-private symlinks work just fine) , but /data increases a little too.
before installing seesmic and pandora df shows:
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 197584 0 197584 0% /dev
tmpfs 4096 0 4096 0% /sqlite_stmt_journals
/dev/block/mtdblock3 148480 110484 37996 74% /system
/dev/block/mtdblock5 200960 [B][COLOR="Blue"]62260[/COLOR][/B] 138700 31% [B]/data[/B]
/dev/block/mtdblock4 97280 39952 57328 41% /cache
/dev/block/mmcblk0p2 702873 [B]97721 [/B]567652 15% [B]/system/sd[/B]
/dev/block/mmcblk0p2 702873 97721 567652 15% /data/dalvik-cache
/dev/block//vold/179:1
14898512 827680 14070832 6% /sdcard
After installing seesmic and pandora df shows:
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 197584 0 197584 0% /dev
tmpfs 4096 0 4096 0% /sqlite_stmt_journals
/dev/block/mtdblock3 148480 110484 37996 74% /system
/dev/block/mtdblock5 200960 [B][COLOR="Red"]62544 [/COLOR][/B] 138416 31% [B]/data[/B]
/dev/block/mtdblock4 97280 41280 56000 42% /cache
/dev/block/mmcblk0p2 702873 [B]100347 [/B]565026 15%[B] /system/sd[/B]
/dev/block/mmcblk0p2 702873 100347 565026 15% /data/dalvik-cache
/dev/block//vold/179:1
14898512 827680 14070832 6% /sdcard
Notice that /data increased by 300KB. Anyone know why?
why is my /data partition 31% used?

Yes, the size of the /data partition does increase even with apps2sd enabled... and from a quick analysis of the /data partition (with apps2sd enabled), I noticed this...
1. the applications are installed on the sd card and the /app & /app-private are symlinked
2. the application information is stored in /data/system/packages.xml (kinda like the windows registry)
3. some application data like shared prefs, extra libs (if any) are stored in /data/data
i guess this accounts for the usage size increase!!!

It looks like the apps are getting is installed to the sd card fine, but the app data still gets stored in the internal ROM
/data/data has 157 folders and is 52MB
/system/sd/app-private has 0 files and is 1K
Therefore it looks like either the apps2sd implementation is incomplete, or didnt get installed correctly.
Anyone tried moving /data/data to /system/sd/app-data and creating a symlink for it? (trying this now...)

darn it. after a reboot the OS removed my symlink, created a new /data/data folder, and apps are still writing to this folder now. lucky i made a backup.
... maybe while booting it saw that the /system/sd/app-data link was invalid (not mounted yet), and hence re-created the folder.

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.

A2SD Error?

Been searching tons of forums for answer, seems like no ones problem is quite like mine though, so...Time to ask you guys
I'm running newest RA-Amon Recovery
I'm running Damage Control 2.09.01
I have been TRYING to get A2SD working correctly for a few days now with no luck....
I've formatted my card, wiped my phone, partitioned SD as follows:
Swap 32mb
Ext 2 512mb (Changed to Ext 3)
Fat32 Remainder
Not sure if it matters, but I have a 32GB SD card...
When I run busybox df -h this is what I get:
C:\AndroidSDK\tools>adb shell
# busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 95.5M 0 95.5M 0% /dev
tmpfs 4.0M 4.0K 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 170.0M 141.6M 28.4M 83% /system
/dev/block/mtdblock5 159.5M 67.1M 92.4M 42% /data
/dev/block/mtdblock4 130.0M 1.1M 128.9M 1% /cache
/dev/block/mmcblk0p2 457.4M 5.0K 433.0M 0% /system/sd
/dev/block//vold/179:1
30.7G 31.5M 30.7G 0% /sdcard
Also, if I try to install a program from Market, it downloads fine, but Fails to Install due to Insufficient Storage
If anyone has any ideas or would like me to try something else, I'm all ears. Phone starting to frustrate me

Don't know if this will work, but try this:
Go into an adb shell. Type this:
cd /data/data/com.android.vending/cache
rm -f *
reboot
This will clear the market cache and reboot your phone.
Let me know if that works.
kronik03 said:
Been searching tons of forums for answer, seems like no ones problem is quite like mine though, so...Time to ask you guys
I'm running newest RA-Amon Recovery
I'm running Damage Control 2.09.01
I have been TRYING to get A2SD working correctly for a few days now with no luck....
I've formatted my card, wiped my phone, partitioned SD as follows:
Swap 32mb
Ext 2 512mb (Changed to Ext 3)
Fat32 Remainder
Not sure if it matters, but I have a 32GB SD card...
When I run busybox df -h this is what I get:
C:\AndroidSDK\tools>adb shell
# busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 95.5M 0 95.5M 0% /dev
tmpfs 4.0M 4.0K 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 170.0M 141.6M 28.4M 83% /system
/dev/block/mtdblock5 159.5M 67.1M 92.4M 42% /data
/dev/block/mtdblock4 130.0M 1.1M 128.9M 1% /cache
/dev/block/mmcblk0p2 457.4M 5.0K 433.0M 0% /system/sd
/dev/block//vold/179:1
30.7G 31.5M 30.7G 0% /sdcard
Also, if I try to install a program from Market, it downloads fine, but Fails to Install due to Insufficient Storage
If anyone has any ideas or would like me to try something else, I'm all ears. Phone starting to frustrate me
Click to expand...
Click to collapse

help needed please - JP3 problem...?

i just flashed to JP3 followind the useful guide from this forum. it all went well, seems verry snappy, bu i have one problem... if i try to install fifa 10 it says i`m out of space "clean up some space and try again". also, if i try to install NOVA for example, it goes thru with the installation but when it starts it says "an SD card with at least 7mb is needed to download" even after i preveously copied the game cache to the SD card....
i forgot to mention some things :
1. i dont have a "lag fix"
2. the external SD, the internal Sd and the phone memory, all have at least 2 GB of free space!
I cannot find a fix anywhere on he internet even know i tried to ...
thank you in advance and excuse my english

hm. make a
busybox df -h
please ...

I am also having problem installing game w update. anyone know why we having this problem?

same here. What I heard is that the 2.2 rom mount phone memory to /internal_sd instead of /sdcard and it causes the problem....

evermick said:
same here. What I heard is that the 2.2 rom mount phone memory to /internal_sd instead of /sdcard and it causes the problem....
Click to expand...
Click to collapse
that may be the case but i also have about 2GB of unused disk space on the internal sd, so it should work ...

jodue said:
hm. make a
busybox df -h
please ...
Click to expand...
Click to collapse
i have the same problem. just installed busybox + rooted
$ su
su
# busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 152.4M 0 152.4M 0% /dev
df: /mnt/.lfs: Function not implemented
tmpfs 152.4M 0 152.4M 0% /mnt/asec
/dev/block/stl9 275.8M 271.8M 4.0M 99% /system
/dev/block/mmcblk0p2 1.9G 68.1M 1.8G 4% /data
/dev/block/stl10 127.2M 10.9M 116.3M 9% /dbdata
/dev/block/stl11 30.1M 32.0K 30.0M 0% /cache
/dev/block/stl3 5.9M 4.0M 1.9M 68% /efs
/dev/block/vold/179:1
5.8G 1012.9M 4.8G 17% /mnt/internal_sd
/dev/block/vold/179:9
7.6G 259.4M 7.3G 3% /mnt/internal_sd/externa
l_sd
/dev/block/vold/179:9
7.6G 259.4M 7.3G 3% /mnt/secure/asec
#
please help!

It is only the most reported bug in froyo.... Have you even tried to read the forum?
And no, there is no fix f for it.
Sent from my GT-I9000 using XDA App

[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!