This thread is to answer any and every one of your questions and i'll start with the most commonly used questions.
1. What is your addition to iodak's kernel.
At this point in time i have removed all of the Demetris additions that iodak added and regretted adding, i did so for two reasons, most of them are from Code Aurora and made for a different chipset than the one we use and the rest are just half additions of longer code chains that he could fit in there but didn't want to spend the time to complete. I've added about 2000 commits in one commit for one reason, i didn't expect i would share this kernel so i just made it for myself, it wasn't until Guiseppe asked me to that i shared it so i didn't structure my commits.
2. Why won't you use F2FS.
I've been involved in programming for the Linux kernel for a good 20 years, i've programmed for Unix and Xenix (don't worry if you don't know what that is, it was Microsofts failed attempt at Unix) and i've been involved in writing drivers for mobile devices for several years. This is a hobby, i produce free code and i'm not paid for it. So, there is my background which i add only to explain that i know a thing or two about drive management both for servers, desktops and mobile devices.
When it comes to F2FS i did what any sensible person would do, i didn't belive the hype that surrounded the new additions so i looked into what it actually does and i tested it in a real world situation (as i always do for everything before i release it).
If you had a hard drive in your phone then random reads would be a big deal, see in ye olden timey hard drives there were heads moving across magnetic discs and things like file system fragmentation mattered because the heads needed time to move across those discs, now we have solid state memory in our phones so this is irrelevant. What is relevant is reads, writes and application performance.
F2FS isn't great at reads and that is pretty much all you do with your phone (unless it's cached in which case it doesn't matter) you don't really need high write speeds on it (much better to do what i have done in my kernel, cache the writes) and you don't need excellent database performance unless you are using it to run databases on which you are not.
So in real world usage, Ext4 is faster and it's a tried and true file system, the only one i know that would actually be faster is XFS.
Now it's up to you to ask questions and me to decide if i want to answer them.
3. "Why don't you release a new ROM, there have been many nightlies since your last release"
Because there is no good reason to. You're running what i and the testers are running, if you want to update your ROM nightly for no reason what so ever this is NOT the ROM for you.
You can check the thread title, when there is a good reason to install a newer version of the ROM you'll find that it's been updated.
Sometimes there are loads of changes that do not affect our device, i won't update the ROM then because there is no reason to, sometimes code gets broken, i won't update the ROM then either. When there is a major change that i make to the dev tree or in a commit or when there are code changes that would benefit our device or when there are fixes or additions of features then i'll update the code.
The last interesting thing was the removal of DSP and addition of ViperFX, there is nothing new for us since then and right now art is borked so i'll wait until there is a good reason (notice the red thread there, good reason) to release a new version.
4. "What governors for CPU and CPUQuiet should i use and what scheduler and congestion control?"
I don't know but this is what i use and recommend:
1. CPU Governor: AbyssplugV2
2. CPUQuiet Governor: Balanced
3. Scheduler: ROW
4. Congestion control: Westwood (this is westwood+, there is no separate option for the old westwood)
Edited by Mourta, 16 August 2014 - 08:49 PM.