bigsupersquid, what's the difference between os2sd and f2fs (I hope it's apparent I don't belong here tech wise after my handful of posts haha)? I grabbed the recent os2sd build yesterday, but I've been wondering if I should go with the f2fs one instead for performance? all I do is install gapps, install my half a dozen apps to make sure they're up to date then back it all up with titanium and reflash the again without gapps. i just check my voicemail now and again and read books with an ebook reader.
First...
f2fs is a filesystem type, like ext4.
F2FS Put to the Test Against EXT4
f2fs uses a lot of free space for its own upkeep. /system needs at least 384MB or so even though it's really under 256 with gapps.
it's supposed to be more stable than ext4 on sd but, I read horror stories of both. Needs fsck.f2fs run for checking, I'll make an init script for that.
fsck.f2fs is built into the ROM and recovery already.
adb shell said:
255|root@thunderc:/ # fsck.f2fs /dev/block/mmcblk0p2
F2FS-tools: fsck.f2fs Ver: 1.3.0 (2014-02-06)
Info: sector size = 512
Info: total sectors = 1500000 (in 512bytes)
[FSCK] Unreachable nat entries [Ok..] [0x0]
[FSCK] SIT valid block bitmap checking [Ok..]
[FSCK] Hard link checking for regular file [Ok..] [0x0]
[FSCK] valid_block_count matching with CP [Ok..] [0x0]
[FSCK] valid_node_count matcing with CP (de lookup) [Ok..] [0xab1]
[FSCK] valid_node_count matcing with CP (nat lookup) [Ok..] [0xab1]
[FSCK] valid_inode_count matched with CP [Ok..] [0x550]
Done.
root@thunderc:/ # fsck.f2fs /dev/block/mmcblk0p4
F2FS-tools: fsck.f2fs Ver: 1.3.0 (2014-02-06)
Info: sector size = 512
Info: total sectors = 2001380 (in 512bytes)
[FSCK] Unreachable nat entries [Ok..] [0x0]
[FSCK] SIT valid block bitmap checking [Ok..]
[FSCK] Hard link checking for regular file [Ok..] [0x0]
[FSCK] valid_block_count matching with CP [Ok..] [0x0]
[FSCK] valid_node_count matcing with CP (de lookup) [Ok..] [0x7f4]
[FSCK] valid_node_count matcing with CP (nat lookup) [Ok..] [0x7f4]
[FSCK] valid_inode_count matched with CP [Ok..] [0x3f7]
Done.
If you get rid of the gapps, I have a suggestion.
Titanium likes to cause problems sometimes. It backs up more than just the apps themselves, and some of the other bits of /data it grabs may not need to be for what you're doing.
You can install everything in Play, and instead of backing up with TiBu, back up just your /data/app directory. If you put that one directory back after a clean install, it'll re-extract data/app-lib and make the rest of /data up fresh.
Of course, you'd have to redo your app settings without using TiBu. Might be worth trying though.