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.

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

[Q] Q - no sdcard is mounted

Hi.
I had rooted (CF-Root-XW_XEN_JS5-v1.3) galaxy i9000 and I updated it with CF-Root-XW_XEE_JVB-v3.1-CWM3RFS. Odin said - successful, but phone after that never boot up successfully, just showed 'Galaxy S ...' on the screen.
Via recovery, using adb shell is see now:
$ busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 169.5M 0 169.5M 0% /dev
nodev 169.5M 8.0K 169.5M 0% /tmp
df: /mnt/.lfs: Function not implemented
tmpfs 169.5M 0 169.5M 0% /mnt/asec
/dev/block/stl9 275.8M 274.2M 1.6M 99% /system
/dev/block/stl3 5.9M 5.0M 933.0K 85% /efs
/dev/block/stl11 30.1M 4.0M 26.1M 13% /cache
Before update it showed:
tmpfs 169.5M 0 169.5M 0% /dev
df: /mnt/.lfs: Function not implemented
tmpfs 169.5M 0 169.5M 0% /mnt/asec
/dev/block/stl9 275.8M 274.2M 1.7M 99% /system
/dev/block/mmcblk0p2 1.9G 354.3M 1.5G 18% /data
/dev/block/stl10 127.2M 12.4M 114.8M 10% /dbdata
/dev/block/stl11 30.1M 4.0M 26.1M 13% /cache
/dev/block/stl3 5.9M 5.0M 935.0K 85% /efs
/dev/block/vold/179:1 13.4G 4.0G 9.4G 30% /mnt/sdcard
Any suggestions, how could I get my sdcard and data volumes again mounted? Somehow via adb mount or should I use Odin with repartition?

after i've installed ezgingerbread, problem with MTD

After i've installed ezgingerbread on my G1 (radio 2.22.28.25 SPL 1.33.0013d), I have problem restoring my nandroid backup of Gingerfroyo (Restore the rom, but lost all settings).
If i install Gingerfroyo rom again , I can't download apk larger than 2 MB from market.
How can I solve this problem?
Thanks and excuse me for my english.

ezGingerbread doesn't touch the partitions, it takes the standard layout of the 1.33.0013(d) SPL. I am not sure if GingerFroyo touches the partition map, I've never installed it.
If your market downloads are not working, probably removing the folder ".android_secure" from your /sdcard will help you.

If i delete .android_secure, it recreate again. The market have the same problem.
I can't download .Apk larger than 2 MB from market.
Gingerfroyo don't touch the partitions.
00040000 00020000 misc
00500000 00020000 recovery
00280000 00020000 boot
05b00000 00020000 system
01b00000 00020000 cache
05bc0000 00020000 userdata

If that didn't work, do you have an ext partition? Is your cache bind mounted to /sd-ext? Can you post the output of the
df -h
command? I suspect your cache is not bind mounted.
Sent from my Gingerbread on Dream using XDA App

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 70.5M 20.5M 78% /system
/dev/block/mtdblock5 91.8M 37.8M 54.0M 41% /data
/dev/block/loop0 2.5M 2.5M 0 100% /system/xbin
/dev/block/mtdblock4 27.0M 13.7M 13.3M 51% /cache
/dev/block/vold/179:2
457.4M 34.2M 398.8M 8% /sd-ext
/dev/block/vold/179:2
457.4M 34.2M 398.8M 8% /data/data
/dev/block/vold/179:1
3.1G 416.0M 2.7G 13% /mnt/sdcard
/dev/block/vold/179:1
3.1G 416.0M 2.7G 13% /mnt/secure/asec

Code:
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 70.5M 20.5M 78% /system
/dev/block/mtdblock5 91.8M 37.8M 54.0M 41% /data
/dev/block/loop0 2.5M 2.5M 0 100% /system/xbin
/dev/block/mtdblock4 27.0M 13.7M 13.3M 51% /cache
/dev/block/vold/179:2 457.4M 34.2M 398.8M 8% /sd-ext
/dev/block/vold/179:2 457.4M 34.2M 398.8M 8% /data/data
/dev/block/vold/179:1 3.1G 416.0M 2.7G 13% /mnt/sdcard
/dev/block/vold/179:1 3.1G 416.0M 2.7G 13% /mnt/secure/asec
Thanks for help

I have re-flashed the rom and the problkem seems to be solved. Thanks for help.
P.S: add rotary lockscreen to ADS_magpie?

gorneman said:
Thanks for help.
Click to expand...
Click to collapse
Prego.
gorneman said:
P.S: add rotary lockscreen to ADS_magpie?
Click to expand...
Click to collapse
Sorry, I tried it already some time ago, but there are too many dependencies to other parts of the CM sources. At the moment I don't think that I will invest the time to port it to ADS_Magpie, but we will see.

/sbin/.magisk/mirror/system at 100%?

Hi all,
I just did an update on my OnePlus 3T from Android 8 to Android 9 that went wrong so that I had to do a factory reset. Well, damn. So here I am with a freshly installed Android 9 / OOS 9.0.3.
Magisk 19.3 is installed and I wanted to configure Adaway but Adaway told me upon activation of the new hosts file that there's no space on the device left.
That's what it looks like:
Code:
OnePlus3T:/ $ df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 2.7G 9.2M 2.7G 1% /
tmpfs 2.7G 1.4M 2.7G 1% /sbin
tmpfs 2.7G 804K 2.7G 1% /dev
tmpfs 2.7G 0 2.7G 0% /mnt
/dev/block/sde20 2.8G 2.8G 0 100% /system
none 2.7G 0 2.7G 0% /sys/fs/cgroup
/dev/block/sda3 248M 4.3M 238M 2% /cache
/dev/block/sde12 12M 4.1M 7.2M 37% /system/vendor/dsp
/dev/block/sda2 27M 776K 26M 3% /mnt/vendor/persist
/dev/block/dm-0 113G 16G 97G 15% /data
/data/media 113G 16G 97G 15% /storage/emulated
OnePlus3T:/ $ su -
OnePlus3T:/ # df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 2.7G 9.2M 2.7G 1% /
tmpfs 2.7G 1.4M 2.7G 1% /sbin
tmpfs 2.7G 804K 2.7G 1% /dev
tmpfs 2.7G 0 2.7G 0% /mnt
none 2.7G 0 2.7G 0% /sys/fs/cgroup
/dev/block/sda3 248M 4.3M 244M 2% /cache
/dev/block/sde12 12M 4.1M 7.5M 36% /system/vendor/dsp
/dev/block/sde11 95M 82M 13M 87% /system/vendor/firmware_mnt
/dev/block/sde23 1.0G 128K 1.0G 1% /system/vendor/bt_firmware
/dev/block/sda2 27M 776K 27M 3% /mnt/vendor/persist
/sbin/.magisk/block/system 2.8G 2.8G 4.0M 100% /sbin/.magisk/mirror/system
/sbin/.magisk/block/data 113G 16G 97G 15% /sbin/.magisk/mirror/data
/data/media 113G 16G 97G 15% /mnt/runtime/default/emulated
Where does /sbin/.magisk/mirror/system come from and is there any way to resize that partition? Or does anyone have a clue on how to resolve this without removing system/vendor apps (as they're getting reinstalled on the next update)?

If OnePlus decided to fill up the system partition, then the Magisk system mirror will be full as well.
What you want to look at though is /system, not /sbin/.magisk/mirror/system. The latter is simply the real system partition and the former is Magisk's systemless mask.
Since it's full you're going to have to do some workarounds... Like creating a Magisk module to mount the hosts file of your choice directly.

Well, that's pretty unfortunate from OnePlus. As suggested I did it with the systemless hosts and it works fine. Thanks a lot!