Holy hell. Didn't think of that. It didn't increase the counter!
$weet
Sent from my GT-N7100 using Tapatalk 2
Good Morning!
Anyone knows if the Kernel works with Omega or other Custom Roms?
I'm trying this kernel, but the score in quadrant is lower than the stock kernel. why?
try running it on performance governor where all "quad"rant cores are turned on.
Andrei patched the performance governor to turn all the cores on and that should give you better score than the stock's performance governor.
similarly, pegasusq is tweaked and tends to give less score in some benchmark apps which only measure how fast your battery is depleted instead of the performance of the device. quadrant is one of them.
but unfortunately people do not believe in our words and they choose to believe in quadrant developers and keep asking or mentioning about quadrant scores
if you want to measure the performance at least choose something that doesn't give you 20% fluctuation in the score in two consecutive runs.
Actually three score difference seems to come from some weird I/O numbers in quadrant for stock Samsung kernels, any way, is a useless benchmark.try running it on performance governor where all "quad"rant cores are turned on.
Andrei patched the performance governor to turn all the cores on and that should give you better score than the stock's performance governor.
similarly, pegasusq is tweaked and tends to give less score in some benchmark apps which only measure how fast your battery is depleted instead of the performance of the device. quadrant is one of them.
but unfortunately people do not believe in our words and they choose to believe in quadrant developers and keep asking or mentioning about quadrant scores
if you want to measure the performance at least choose something that doesn't give you 20% fluctuation in the score in two consecutive runs.
Max GPU clock and voltage?
Sent from my Galaxy Nexus using Tapatalk 2
It's a Samsung feature, it's called Touch Boost and it serves to gain fluidity. It is also not battery friendly. I have removed this on the S3 and replaced it with another mechanism, but I still need to port it to the Note as it's bound by the touchscreen driver, and they slightly differ. Give me a few hours.CPU frequency seems to lock at 800 MHz whenever screen is touched. Feature or bug?
Sent from my GT-N7100
Get your head out of your ass, it's not about disagreeing or not, it's about the facts/content you disagree on. You're don't have immunity to criticism and neither do I so don't get upset when you are being called out on something.I'll do that. And I'll be sure you get a pm when I do. Also, you won't have to worry about your device rebooting anymore.
Have a nice day folks. Sorry for disagreeing with the almighty god
The point of undervolting is that it is a disadvantage free method of gaining power efficiency, and it can bring down the dynamic power usage on the SoC down, from, let's pull it out of my ass, 20% by the best estimates from what I have measured over the last year. If you have instabilities then it is your fault in your methodology because you are undervolting too much. We are merely eliminating a manufacturers safety margin by undervolting.Some of these frequencies are set almost -100mv. Processors nowadays are becoming very efficient on power and are absolutely DWARFED by the amount of power your display, radios, and other hw uses. My own personal opinion is to look at other power consumers such as the aforementioned before playing with hw that in the grand scheme of things is not your biggest power consumer culprit, yet is vital to system stability.
No the sampling rate is not when the CPU is polled for load, it's the periods between which the governor does DVFS decisions, load is merely a statistic of the reverse of how much time the CPU is in idle.SAMPLING RATE: 28000 - just to be clear, the sampling rate is the interval of spacing between CPU being polled for load. Use this as you see fit, the small the interval, the more it checks for pending tasks to be executed. I have found great success and performance (and accuracy and decreased latency) with 20000-15000. Battery will not suffer anything noticeable to the end user.
Same thing, again, absolute nonsense as with the CPU voltages above. Internal voltage especially can bring power gains, albeit it is much less than the CPU, but it is a free gain.honestly, I really don't see the need to mess with this either. More potential instability for a minimal gain in battery when analyzed against your main thieves of your voltage - display, radios.
Deadline is alright, but noop just means that you are turning scheduling off. It doesn't bring you any performance gains at all, you are better off using an IOPS and latency designed scheduler like ROW or FIOPS (I'll bring that back when I have time), again, Deadline is ok, and SIO is a compromise of everything.dealine and noop will give you the best performance on these devices in real time, data speeds are also increased significantly with these two IO schedulers.
Maintenance, logging???!!! These are tasks that do not even remotely task the CPU even at 200MHz with any significant load, any single process out there running in the background can be done at 200MHz, it is more power efficient and you are not even aware of it.Also, if i may add this... I would recommend bumping the min frequency to something like 500MHz for the CPU. Reason being is simple - smaller tasks (maintenance, logging, etc) can be handled with ease without causing unnecessary CPU ramping.
So you see how that whole last paragraph of yours is just nonsense and that last phrase is really something one might take out of a PR article. Your settings you suggested were not given more thought.THIS is performance without battery life taking a hit - making your system AGGRESSIVE YET EFFICIENT, not hindering and crippling it to not do what it is programmed to do. Efficiency. "Less is more" as you see thrown around in the Linux world can also be thought of as more is less if you think in terms of more thought, tuning, and logic is less power consumed by your device.
Yes please do deliver your kernel, because I want to see more nonsense delivered with an attitude. We already have a large amount of clueless developers on this site. The problem isn't that they're unskilled or do not know the technical details, everybody was like that including me; It's that they think they are doing some sort of meaningful change without giving the effort of thinking or dwelling into the topic more than 2 minutes. People are suffering from a severe case of the Dunning-Kruger effect (I was so happy when I found out there's a name to that attitude).I'll do that. And I'll be sure you get a pm when I do. Also, you won't have to worry about your device rebooting anymore.