Originally Posted by Zittoro
Everything has its upside and downside. I'm not being a smarta$$ or something but just warning you guys...
I think f2fs has a more than 50 or so times slower average mounting time than that of ext4, so most of the flashaholics out there will simply come back to ext4. It requires partition formats and an f2fs kernel. If one flashes an f2fs kernel to a phone with ext4 partitions, the phone will simply hardbrick, and vice versa. Of course it is possible to be unbricked, but it will be difficult for anyone who hasn't dealt with partitions, especially NAND, before.
I'm just afraid this will brick thousands of gnex's. It will cause a serious confusion and eventually succeed or will just be ignored by everyone.
I have seen two people successfully ported f2fs, one to Galaxy Nexus and the other to Nexus 5, but both of them said their phone literally mounted forever. Of course the benchmark provided by one of them with gnex showed a really good improvement, but even he forgot that he shouldn't flash an ext4 kernel, which he did and got bricked.
I agree with you about this may or may not be worth it to the general public. But I was interested in this for the op as well as my curiosity .
That's also a great reason for this to stay in the dev support thread
The kernel supports both filesystem's , so flashing the f2fs kernel on a ext partition is OK , hell I'm running that combo now lol , I'm only using ( trying to ) f2fs for the userdata partition like the motoX .
I'm not doing this for recognition , weather its of value to anyone other than my curiosity or self is secondary , not saying I'm thinking only about me. But I would never put a ROM out that I didn't test on my phone first .
I'm compiling AOKP 4.4 now with hopefully everything I'm looking for . I'll post the eventual results .
Sent from my Galaxy Nexus using Tapatalk