So I've spent the better part of a week attempting to upgrade my tablet to KK and F2FS-ALL. (I was on 4.3.1, didn't want to touch KK, but Lollipop is a non-starter because I use Xposed, and I need the security updates in KK.)
I originally tried USBhost's build of Carbon, and that seemed OK, except for mysterious lags waking up ... and the fact that it can't run one of my favorite games, which makes me wonder what else it breaks. I also tried SlimKat, Dirty Unicorns, and Liquid Smooth, which I sort of liked, disliked, and couldn't boot (plus LS formats /system as EXT4, despite claiming F2FS support).
I'm totally sold on the performance gains in F2FS. The lags I saw on EXT4 are gone, even with F2FS being mounted as discard by default in M-Kernel. (I need to find more documentation as to whether this is necessary or not for F2FS, because it doesn't seem like it should be.) I wonder if there's enough of a gain with F2FS that it would make device encryption actually tolerable, but I don't have time to play with that right now.
I settled on flashing CM 11 M12 using poo706's script hack and MultiRom's hacked TWRP, with M-Kernel a69, current Busybox and SuperSU. I'm not a fan of CM, but I can't be screwing around with ROMs that aren't stable right now as I'm about to travel.
More importantly: CM 11 was one of the only ROMs that had f2fs-tools 1.40 binaries in /system/bin. (The others were Carbon and Liquid Smooth. This is simple enough to check; just look at the binaries in the ZIP file before flashing.) All the others either had no fsck at all, or had old versions of fsck.f2fs.
That completely mystifies me, because F2FS is a bleeding edge filesystem, which didn't even have the *possibility* of repairing corruption until f2fs-tools 1.40 released in September. (Does it work? Who knows; AFAIK the filesystem is still in active development.) Why would you claim support for F2FS, and not include any utilities to check and fix it? Have ROM builders just not gotten the memo that fsck.f2fs got that update in September?
There's almost no information out there about F2FS on Android in general, so I'm going to throw this out there: can anyone build f2fs-tools 1.40 as universal, statically-linked binaries which can be dropped into any KK ROM via flash scripting or an installer app? Y'know, something like Stericson's Busybox installer, but just for f2fs-tools? Is that even possible? (Would it be better to use the fork in the current Lollipop master? I have no idea; all I know is that said fork is in active development. I don't know if CM is doing their own work on this, or just pulling from master.) It just seems like the sort of thing that should be part and parcel of an F2FS implementation, as opposed to the bare minimum hacks which are still being used.
If I already knew how to build a ROM, I would've already done this. I don't, and I'm about to travel, so I don't have time to attempt it right now. (Also: do you really want someone who hasn't done this before throwing out builds?)
-XCN-
I originally tried USBhost's build of Carbon, and that seemed OK, except for mysterious lags waking up ... and the fact that it can't run one of my favorite games, which makes me wonder what else it breaks. I also tried SlimKat, Dirty Unicorns, and Liquid Smooth, which I sort of liked, disliked, and couldn't boot (plus LS formats /system as EXT4, despite claiming F2FS support).
I'm totally sold on the performance gains in F2FS. The lags I saw on EXT4 are gone, even with F2FS being mounted as discard by default in M-Kernel. (I need to find more documentation as to whether this is necessary or not for F2FS, because it doesn't seem like it should be.) I wonder if there's enough of a gain with F2FS that it would make device encryption actually tolerable, but I don't have time to play with that right now.
I settled on flashing CM 11 M12 using poo706's script hack and MultiRom's hacked TWRP, with M-Kernel a69, current Busybox and SuperSU. I'm not a fan of CM, but I can't be screwing around with ROMs that aren't stable right now as I'm about to travel.
More importantly: CM 11 was one of the only ROMs that had f2fs-tools 1.40 binaries in /system/bin. (The others were Carbon and Liquid Smooth. This is simple enough to check; just look at the binaries in the ZIP file before flashing.) All the others either had no fsck at all, or had old versions of fsck.f2fs.
That completely mystifies me, because F2FS is a bleeding edge filesystem, which didn't even have the *possibility* of repairing corruption until f2fs-tools 1.40 released in September. (Does it work? Who knows; AFAIK the filesystem is still in active development.) Why would you claim support for F2FS, and not include any utilities to check and fix it? Have ROM builders just not gotten the memo that fsck.f2fs got that update in September?
There's almost no information out there about F2FS on Android in general, so I'm going to throw this out there: can anyone build f2fs-tools 1.40 as universal, statically-linked binaries which can be dropped into any KK ROM via flash scripting or an installer app? Y'know, something like Stericson's Busybox installer, but just for f2fs-tools? Is that even possible? (Would it be better to use the fork in the current Lollipop master? I have no idea; all I know is that said fork is in active development. I don't know if CM is doing their own work on this, or just pulling from master.) It just seems like the sort of thing that should be part and parcel of an F2FS implementation, as opposed to the bare minimum hacks which are still being used.
If I already knew how to build a ROM, I would've already done this. I don't, and I'm about to travel, so I don't have time to attempt it right now. (Also: do you really want someone who hasn't done this before throwing out builds?)
-XCN-
Aucun commentaire:
Enregistrer un commentaire