My son has a rooted stock Droid X2 and he pushes it/me to the limit with the number of bulky games he installs. As you've probably guessed, he often runs out of space. I've managed to alleviate the problem a few times by using Titanium Backup to integrate system app updates into the ROM, or by moving apps to the "media area". Having used those tricks to their fullest, and seeing that his 2GB external sdcard was not being used, I found a few threads indicating how easy it is to swap the internal and external sdcards with minor changes to vold.fstab, replaced the 2GB card with a 16GB card, and made the swap, copying EVERYTHING from the internal to the external immediately prior to the swap. The only app issue I observed was that Google Drive would crash when opened. Removing and re-installing the app fixed that issue. One other issue is that the phone reboots when connected to a PC in mass storage mode.
Subsequently trying to free up some space for installing yet more apps, I used Titanium Backup to identify the space hogs, and moved two of them to "SD card" (TiBu terminology, but I think it refers to /sdcard), only to have Android tell me that I'm running low on space on my "SD card" (Android terminology, but I think it refers to /sdcard_ext). Using the native Android application manager yielded the same results.
Contributing to my confusion are the multiple names by which these locations are referred, including "internal", "sd card", "media area", "sdcard", "sdcard_ext", etc. - enough to give me a headache.
To me it appears that moving apps to the "SD card" (TiBu) or "media area" (native app manager) actually moves the app (but not the data?) to the 4GB built-in memory, regardless of how it's mounted or what changes I've made to vold.fstab. Is that what's happening? Can anyone help explain further, or correct me?
Subsequently trying to free up some space for installing yet more apps, I used Titanium Backup to identify the space hogs, and moved two of them to "SD card" (TiBu terminology, but I think it refers to /sdcard), only to have Android tell me that I'm running low on space on my "SD card" (Android terminology, but I think it refers to /sdcard_ext). Using the native Android application manager yielded the same results.
Contributing to my confusion are the multiple names by which these locations are referred, including "internal", "sd card", "media area", "sdcard", "sdcard_ext", etc. - enough to give me a headache.
To me it appears that moving apps to the "SD card" (TiBu) or "media area" (native app manager) actually moves the app (but not the data?) to the 4GB built-in memory, regardless of how it's mounted or what changes I've made to vold.fstab. Is that what's happening? Can anyone help explain further, or correct me?