[Kernel]netarchy-toastmod, Version 4.1.9.1 Beta: 4.2

[netarchy]

Originally Posted by parousia15

I'm running this over SprintLover's ROM. No issues.

I'm just curious, the FPS is different for different tests
I know 2D is simpler. I get about 53 fps on that
On Gears I get about 44-45.
But on Quandrant and Neocore I still get under 30 FPS.

I guess 3D is harder to hack/fix or is that due to the limited GPU? (as compared to hummingbird processor)

Anyway, I absolutely love this. My phone runs so smoothly now.

Neocore you should expect around 27 on any snapdragon (even the nexus one benches about 27 in neocore). The neocore score is very much due to limitations of the gpu. In this particular case, the bottleneck for the gpu in neocore is fill rate.

Both quadrant and neocore are made to stress hardware to its limits. They are not necessarily indicative of performance in everything. As an example, neocore may bench at about 27, but I guarantee you if you were to fire up raging thunder 2, you'd find it runs smooth as butter.

As for gears, you should be able to get in the 50's, but it depends largely on the scaling parameters for your cpu.
Benchmarks are highly sensitive to the speed of the cpu, how quickly the cpu governor scales the cpu speed from idle to full in response to load.
For instance, if you were to install setcpu, and set the governor to performance (essentially forcing the cpu to run at full speed all the time) you would find that your benchmarks are consistently higher.

The defaults in the kernel aim for good performance out of the box, but it is worth noting that any default settings can be overridden.

Some custom roms override the defaults by setting the cpu threshold (aka the % of load the cpu experiences before the governor starts increasing the speed of the cpu to deal with the load). It's also worth pointing out that apps like setcpu and overclock widget can also override the defaults, for better or worse (depending on your settings).

The default threshold in my kernel builds is 70%, meaning that once something is throwing a 70% load to the cpu at its current speed, it starts speeding up to deal with the load.

Setting a higher threshold results in better battery life, but progressively lower performance in trade.

[parousia15]

Originally Posted by netarchy

As for gears, you should be able to get in the 50's, but it depends largely on the scaling parameters for your cpu.

Thanks for the explanation. Is "scaling parameters" something I can alter with setcpu? I have it install, but I have it set to just 998 and 245 ondemnod. I fear overclocking will break my cpu.

I've noticed that on gears, it's a little erratic, it fluctuates between 43-49, which makes it look a little choppy. I think it looked a little more smooth when it was consistently at 31fps.

Originally Posted by netarchy

The default threshold in my kernel builds is 70%, meaning that once something is throwing a 70% load to the cpu at its current speed, it starts speeding up to deal with the load.

Is that why, the first time around when I run fps2d it works its way up to aboue 54-55 and the sd is larger, while immediately running it a second time, performance is more consistent?

[netarchy]

Originally Posted by parousia15

Thanks for the explanation. Is "scaling parameters" something I can alter with setcpu? I have it install, but I have it set to just 998 and 245 ondemnod. I fear overclocking will break my cpu.

I've noticed that on gears, it's a little erratic, it fluctuates between 43-49, which makes it look a little choppy. I think it looked a little more smooth when it was consistently at 31fps.

Yes you can, if you go to the advanced tab in setcpu you can change the governor parameters. The 2 you're mainly interested in are sampling rate and threshold.
Sampling rate is how often the governor checks the cpu load to decide if it needs to increase the cpu speed, I personally use 50,000 (about .05 seconds).
Threshold is what % of cpu needs to be hitting before the governor starts increasing the cpu speed, I prefer around 70 to preserve that snappy feeling. Setting it lower can improve performance, but can increase battery drain.

Gears can be a touch misleading to the governor since it doesn't hit the cpu as hard as fps2d might. Generally I tend to advise people to fire up setcpu (or whatever clock control util they prefer) and set the governor to performance for the benchmark to see what your peak is. (Just remember to change it back to ondemand when you're done ofc!)

Originally Posted by parousia15

Is that why, the first time around when I run fps2d it works its way up to aboue 54-55 and the sd is larger, while immediately running it a second time, performance is more consistent?

That's exactly why.

When you first fire up fps2d, you're probably still running at min, and on that first run the governor will be ramping up the cpu speed to meet the load it's seeing from fps2d.

On the second pass, the speed is already scaled up a bit(unless you let fps2d idle long enough for the governor to scale the speed back down) so there isn't as much fluctuation.

[Sievers]

I have a feeling I already know the answer to this, but will this work on the 002 hardware with nova screen? If not, is anyone working on one that will?

[netarchy]

Originally Posted by Sievers

I have a feeling I already know the answer to this, but will this work on the 002 hardware with nova screen? If not, is anyone working on one that will?

The HW revision has no bearing on the fps fix working or not. This kernel is for both nova and epson screens so yes, it should work.