I had really slow performance when using an a2sd ROM - (which redirected the /data/app, /data/app-private, and /data/dalvik-cache to /system/sd)
The issue was that clockwork recovery had formatted my sd card with a 1024 block size. Re-formatting it with a standard block size (4096) resulted in much better speeds for me..
(I re-formatted by running an ubuntu livecd, mounting and copying the contents of /dev/sda2, running mkfs.ext3 against /dev/sda2 (which was the second partition for my sd card..) - re-formatting it with a more standard block size of 4096, then copying the data back..)
Thought this might help somebody. You can see the block size of /system/sd (if you're using apps2sd with an external sd card partitioned..) by running 'adb df /system/sd' - if it shows (block size 4096) - you're good.. anything lower.. you might want to consider re-doing your setup..
-mark
PS - it might actually have been RA that formatted with the 1096 block size.. I honestly can't remember now which recovery I used to partition initially..
Ok Im having a few issues with my touch slide 3g -- according to app "partitions info lite" it seems that i have the following partitions:
--------------------------------
Partitions on PHONE:
/dev (209mb) [used 0mb]
/asec (209mb) [used 0mb]
/system (240mb) [used 97mb]
/data (145mb) [used 122mb]
/cache (80mb) [used 78mb)
Partitions on SDCARD:
/sd-ext (457mb) [used 41mb]
/sdcard (14671mb) [used 8387mb]
/com.froogloid.kring.google.zxing.client.android-1 (2mb) [used 0mb]
/fm.last.android-1 (2mb) [used 0mb]
--------------------------------
--------------------------------
I have a 16G sd card for music etc...
and was hoping to move all my apps to an sd-card (ext3 or ext4) partition as we all know the phone doesn't have much storage space, the things that puzzles me are:
1. why is the /cache partition so full and how do i clear it - tried a few "cache clearing apps" to no avail... (cachemate, HistoryEraser, etc..)
2. what are partitions /dev and /asec for?
3. can any partitions on phone be removed? Id really like to resize my /data partition so i dont get 'low space warnings" anymore
4. is there such a thing as "partition magic" for android (to resize the /data partition bigger) ?
5. why the 2 funky partitions on SD? I do have "last.fm" and "key-ring" on the phone and guess i can try un-installing and see if the partitions goes away, but a bit weird for both these apps to require their own partitions...
is there a way to remove the partitions from SD and recoup the space used?
6. Ideally id like to move the /cache partition to the sdcard, or offload my large "copy protected" paid apps to a ext3 partition on my large sdcard. I have heard about "Darktremor Apps2SD" but after i tried it all my apps were gone! - luckily i backed up my rom before hand... guess Im a bit lost and seeing guidance from a guru.
I know there are a lot of questions here, im hoping some kind soul can help, perhaps others might have similar problems.
-s
My device:
---------------------------
HTC Tmobile My touch Slide
S-off
Cyanogenmod 6.1.1 (2.6.29.6)
android 2.2.1
build# frg83
The app partition in this ION always running out of space.
Is there a way to resize it and get more space from the non-app partition which has so many GB left that never use?
I have a brand new G3 (D852) with Koodo that I just got 2 days ago. I've rooted, installed TWRP and flashed a few AOSP roms. Not a fan of any manufacturer UI, even though LG's is very minimal, so AOSP it is. I noticed that my system partition has more than 1GB of free space after everything is flashed and good to go. I also noticed that the latest TWRP (2.8.7.0) has a resize partition option inside the Wipe section. What I want to know is, how can I use this to resize the system and data partitions so that 1GB+ isn't being wasted and unused. I'd really like to get that 1GB+ added to my data partition for apps.
I've tried using it. The only time it didn't spit out an error was after I wiped the system partition. It succeeded in "resizing" it after that, but it didn't change anything. The system partition remained the same size.
ToYeD said:
I have a brand new G3 (D852) with Koodo that I just got 2 days ago. I've rooted, installed TWRP and flashed a few AOSP roms. Not a fan of any manufacturer UI, even though LG's is very minimal, so AOSP it is. I noticed that my system partition has more than 1GB of free space after everything is flashed and good to go. I also noticed that the latest TWRP (2.8.7.0) has a resize partition option inside the Wipe section. What I want to know is, how can I use this to resize the system and data partitions so that 1GB+ isn't being wasted and unused. I'd really like to get that 1GB+ added to my data partition for apps.
I've tried using it. The only time it didn't spit out an error was after I wiped the system partition. It succeeded in "resizing" it after that, but it didn't change anything. The system partition remained the same size.
Click to expand...
Click to collapse
This it why the option is there:
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
jeffrey268 said:
This it why the option is there:
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
Click to expand...
Click to collapse
Thank you for the reply
If I understand you correctly, the feature's original intent is to resize /data partitions in the event the rom/system image treats a larger storage capacity device as a lower capacity one, ie. 64GB device is treated like 32GB so /data will only reflect 32GB minus (system image install size), wasting 32GB and leaving it inaccessible to the user.
However, it also seemed like you were saying I also could use it to resize my /system partition to a smaller size so CM12.1 (with it's ~900MB install size after Full TK-Gapps) will only leave ~50MB to ~100MB on /system instead of ~1.5GB. However, the question remains. How do I do this and can I reallocate the ~1.5GB to the /data partition for apps and internal storage? If this can't be done then I see no point in resizing /system to begin with as it will still be inaccessible to me as the user.
ToYeD said:
Thank you for the reply
If I understand you correctly, the feature's original intent is to resize /data partitions in the event the rom/system image treats a larger storage capacity device as a lower capacity one, ie. 64GB device is treated like 32GB so /data will only reflect 32GB minus (system image install size), wasting 32GB and leaving it inaccessible to the user.
However, it also seemed like you were saying I also could use it to resize my /system partition to a smaller size so CM12.1 (with it's ~900MB install size after Full TK-Gapps) will only leave ~50MB to ~100MB on /system instead of ~1.5GB. However, the question remains. How do I do this and can I reallocate the ~1.5GB to the /data partition for apps and internal storage? If this can't be done then I see no point in resizing /system to begin with as it will still be inaccessible to me as the user.
Click to expand...
Click to collapse
I read a few things online and it seems you need aan unlocked bootlader, the G3 bootloader is not unlockable, so you are probily out of luck maby you can ask in the Q&A thread of the rom you are using.
how do you resize the system partition? i'd like to install gsi roms but it is exceeding the size limit