[ONE Original Android Development] RenderBroken:
I have been really enjoying the non-CAF version of Euphoria.

[MENTION=787541]schaggo[/MENTION]

That was a very nice and informative post. I had made some adjustments based on it. I will say a couple things though:

1. CPU-Boost does not really clash with governors and such. It works really well in that it is pretty seamless by adjusting min_freq on the fly like it does. The governor does not trip over itself looking for a freq that is below the input_boost_freq of CPU-Boost. It just uses the lowest value it can which is the boosted freq. So SmartMAX having a different boost value doesn't change anything. Also there are other functions in SmartMAX that are looking for the values of boost_freq and such. With that, I ended up just machine the boost freq to that of CPU-Boost's boost freq. Just to kinda sync things up for good measure.

2. The max and min load values are set that way to make SmartMAX more interactive. But I don't mind trying different values so right now they are set to min=30 max=70. Lets see how that goes.

3. The ideal_freq is also set so that when the workload is finished it ramps down to a VERY low idle. But again, lets try something a little different. So right now awake and sleep are set to what you had recommended. You had sound evidence in proving why those values were sufficient.

So with all of that, the main goal is to have the workload completed ASAP and return to the lowest freq available. With CPU-Boost in place and tuned, that makes it so there is not any lag when you engage the screen. (Should not be but you know how that goes. . .) Also I do disagree with you about the multi core, low freq setup being more efficient than the 2 core, 1 low freq, the other set way higher. There are a couple reason, I believe, that this is why msm_hotplug is more efficient.

Lets just add up voltage. Lets say msm_hotplug has one core max and the other fairly low. you are looking at about a total of ~1700mv

Then lets do Bricked with 3 cores at even the lowest freq, you are looking at about ~2100mv.

Both with an undervolt of 55mv. So at stock you would have about ~1800mv and ~2250mv

Then if you are using CPU-Boost its much more, I would have about ~1500 and you would have about ~2200 again.

So in just pure voltage msm_hotplug wins out. And with less hotplugging/unplugging than Bricked.

Lastly, the second reason I believe the msm_hotplug setup is better is for the same reason SmartMAX has been working well as is. I want to take care of the workload and get back to a low freq ASAP. With msm_hotplug, I can do so with the higher freq on one core and can raise the second one if needed. Also its tuned so that when idle, you will go down to a single core but as soon as you touch the screen, it onlines the second core. This way we can have a smooth UX and take care of workload properly without having to hotplug/unplug numerous cores all the time. That was my biggest issue with Bricked. BUT we all have are own preferences and I appreciate you sharing yours.

I would LOVE to have a true quad core CPU and just use C-States like the N6 but we have a 3.4 kernel while they have a 3.10 based one. Our scheduler and thread migrations are done completely differently. Before workload can be handed over to another core, that second core HAS to be AT or ABOVE the freq of the core you are receiving the workload from. This is why in my opinion, CPU-Boost becomes very helpful in that it makes it so the freqs are already pretty close to each other.

I say these things as a hobbyist and not as the definitive law on such. I do enjoy discussing these things and I invite more people to throw out some discussion topics. If you think I am doing something wrong, tell me. If you want a feature, tell me why. If you want to know something, Just ask. We were all noobs at one point, as long as you search the thread first and at least take a look at the newest 3-4 pages, I will never call you out for being a noob or for not searching first.

Also, I wanted to say that I flashed my newest version of Render-UKM and it works flawlessly. Not sure what everyone else's problem is but I will do more testing to see if I can reproduce.