Hello. A few months ago, I started working on a custom kernel based on erorcun's 3.10 kernel. I've worked in many different directions, i.e. updating the code to the latest upstream 3.10.x version, adding new features and optimizations, etc. Then I kind of paused the project, but I decided to pick it up again today, and release it within a couple of days on XDA. Having said this, I can't promise you I'll be able to fix the bug you wrote about, but I promise I'll at least give a look at it soon. I'll let you know when the kernel will be released.Could the f2fs + encryption issue at least be addressed? From my own experience the encryption process is fairly simple and straightforward. Whatever is broken could be just an f2fs driver issue or the compiled luks not working correctly. I don't believe you would necessarily need a physical OnePlus One to do this either, you could emulate the hardware on a PC within Linux.
I used to run my OPO on f2fs /data and /cache until encryption became a necessity. The file system performance was to say the least, astounding. I've been forced to switch back to ext4 though unfortunately due to the lack of f2fs encryption on kernel 3.4 and the broken f2fs encryption on this 3.10 kernel. The file system performance is notably slower and I have to constantly trim my partitions. The only reason I'm still bringing this up is because if we're going through the effort to make a 3.10 kernel, f2fs with encryption isn't much further to achieve. I'm running an encrypted LVM f2fs fedora install on my main PC's 1TB Mushkin SATA SSD for productivity and the recent things the linux kernel has been doing with f2fs have really made it a no-brainer for flash devices. Future android smartphones will most definitely be running f2fs on all partitions (and some already are) simply because it's better and preserves the performance of your flash device.