[ONE Original Android Development] jgcaap:
You guys quickly forget but let me remind something .

1) I'm not a normal user.

I've helped and created different profiles, and study as also understand how linux works (which reflects on android). I study the core of the issues, not the soft side of them. I lost many hours of studying linux features, and to test, where i put my device at risk in order of doing research.

I've managed to get some accomplishments from them, cause i read, and after ir properly test it.

i suggested different profiles:

http://xdaforums.com/oneplus-one/development/rom-kernel-sabermod-cm-11-0-t2880407/post55889255

Results came from it:

https://www.dropbox.com/s/y4d20xjnilbwjte/Screenshot_2014-09-30-15-47-27.png?dl=0

Where i reported here:

http://xdaforums.com/showpost.php?p=55855975&postcount=4284

After this i done another battery test, which i am not finding the post where it lasted 3 days of use + 6 hour screen on.

All that was with this configuration:

300Mhz - 2.5Ghz

Interactive

intelliplug (balanced4 my choice as is more efficient)

Cpu sync 1.2ghz

Cpu touch 729mhz

Read ahead at 1056

Ratio at 5

Background ratio at 15

Swap at 10

Vfs pressure at 40

I'm saying this not to say i'm a genius, but to remember, i'm not a normal user which will content with a kernel that i have already seen in better shape, as also, know that because of that we are not using our phones potential as we should.

2) If you are happy that's fine... But that doesn't mean that inside, your phone is in healthy state the way the kernel is now.

When gaming improve graphics or apps needs a more demanding job, and you notice lags... Perhaps, by then you will remember that perhaps have been best to have studied this better. But you want to know the real problems? Devs copy each others commits here, and when that happens, no one will remember about this changes, and keep on advancing.

Then some users will switch back to CM kernel, others to kernels near Lords Boeffla development style (which is near stock with overclock features, and some extra governors and schedulers). Others will perhaps say "i can live with the lag". Other say "I'll just sell my phone, is already outdated" or even perhaps "dam.. my phone doesn't switch on! need to send my phone to RMA something broke..." and after that comes report saying it was your fault.

3) Between all of these situations you know what i prefer?

AK reviewing the code faux123 gave him, and the kernel itself for real, do real tests. Stop chaging 4 times a day from diferent roms, and only change/flash 1 rom per week to test stability and consistency. And perhaps then, it'll found the problems, and how to fix them so that it can be achieved stability.

4) Stability experience

My record on GS2 without needing reboots was for 1 entire month. It shutdown because it run out of battery. That's stability, and if i done tests with quadrant or Antutu, would be consistent always and that's more than proof of stability. With AK already got 160 hours with consistent antutu results.

Conclusion, all i am asking here, is proper testing, proper reading of the code as proper fixing. There is a problem in the kernel,

hurting performance which can one day give a bigger problem

. I'm the only one reporting it, because i know that is something on the kernel side doing that diference. My bet, bad implementation of code on the thermal and there is necessity of review. Development takes time, and cannot be done in hours of testing, but days.

Thank you for reading.