[Nexus 4 Original Android Development] Hanny:
Omg he returns!! The ultra-patient re-posting gamer! This time with abusing the mentioning function!! People I know you and I have tried to ignore but no, he will repeat! :eek:

First of all hoangtungst my friend, please read the forum rules http://xdaforums.com/announcement.php?a=81

And 3 notes for you:

1. Franco doesn't write all the detailed changes in the changelog if he thinks it isn't worth the time. If you don't see it, its because the changes are UNDER THE HOOD and the difference doesn't worth you to take effort on noticing. But! That doesn't mean that you cannot see what has been changed. The link to source is posted clearly in the OP https://github.com/franciscofranco/mako/tree/nightlies and the latest changes regarding interactive dynamic tunables in r138 and r139 are here https://github.com/franciscofranco/mako/commit/75f0a2540ba6dd2419845e94cf0e69bd93b920ff & https://github.com/franciscofranco/mako/commit/57131edd5361a32ee37b5583a00168af5bc9e900 You can enjoy reading them as I did.

2. Please state your question clearly. "Have you edited the interactive governor" is not a proper / necessary question. By looking at the sources, you can easily tell that the answer is YES. Therefore you don't need to ask the same question, twice. Don't ask for facts but ask for reasons, because you can discover the facts and you might not know the reason; and finally, state your concern, why is that question being asked at the first place, because the developer is not going to explain the reason for every of his commits.

For example, "Why did you remove scale_interactive_tunables(0, 80, 10, 80) under static void second_level_work_check(unsigned long now)? The FPS of GTAVC has significantly decreased." I asked the question and that helped finding out bugs or something. For you, I can't make a proper suggestion because I still don't know what your concern is.

Well not really every question has to be that seriously revised or I am saying most of the people here are incorrect. But why I'm just talking about your question is that you used the mention function for 2 times, directly towards a developer, and therefore the question has to be made proper, or else, don't direct that kind of useless questions to franco so that you dont spam his email / xda notifications while other members here might be able to help you out.

3. If you would not like to read the source, read the posts on the forum. The forum is meant to be separated with github because the language here is easier to be understood.

Are you concerning about gaming? The report is out http://xdaforums.com/showthread.php?p=41574593#post41574593

Are you concerning about UI interactions? No one here has been complaining yet, or if you would like to appreciate, you should have typed it in your post.

But I can spend a minute to type what's been changed so to save the man some time:

Before r138:

Interactive tunables for 4 cores [activated by first_level]: (0, 80, 10, 80)

Interactive tunables for 4 cores [activated by incremental second_level]: (0, 80, 10, 80)

Interactive tunables for 2-3 cores: (50, 99, 30, 20)

Interactive tunables for 1 core + load is not below fourth_level (default 10): (50, 99, 30, 20)

Interactive tunables for 1 core + load is below fourth_level (default 10): (15, 99, 25, 40)

r138:

Interactive tunables for 4 cores [activated by first_level]: (0, 80, 10, 80)

Interactive tunables for 4 cores [activated by incremental second_level]: (50, 99, 30, 20) <mistake>

Interactive tunables for 2-3 cores: (50, 99, 30, 20)

Interactive tunables for 1 core + load is not below fourth_level (default 10): (50, 99, 30, 20)

Interactive tunables for 1 core + load is below fourth_level (default 10): (50, 99, 30, 20) <battery improvement>

r139:

Interactive tunables for 4 cores [activated by first_level]: (0, 80, 10, 80)

Interactive tunables for 4 cores [activated by incremental second_level]: (0, 80, 10, 80) <fixed>

Interactive tunables for 2-3 cores: (50, 99, 30, 20)

Interactive tunables for 1 core + load is not below fourth_level (default 10): (50, 99, 30, 20)

Interactive tunables for 1 core + load is below fourth_level (default 10): Not setting, its same as above

Thats all, tried my best to answer your one-line question. :) Hope to see you next time with a non-spam, useful post.