[Nexus 4 Original Android Development] Hanny:
r115 Gaming Test :)

ROM used in all my tests: AOKP-PUB

Throttle threshold: 85​

Why I don't depend on Real Racing 3 for gaming tests although its cool: http://xdaforums.com/showthread.php?p=39559547#post39559547

First, GTA VC Max Graphics

Huge base of statistics for comparison

thalamus hotplugging google interactive 29-31

mpdecison google interactive 31-33

mpdecision conservative 35-37

mpdecision lazy 29-32

mpdecision codeaurora interactive (original) 32-34

mpdecision codeaurora interactive (tweaked) 30-32

m1 interactive (timer_rate=20000) 30-32

r110 interactive (default timer_rate=50000) 28-31

r110 interactive (manual timer_rate=20000) 32-34

r115 (default timer_rate=50000)

Average FPS = 30-31

Let's pause here for a short conclusion:

Yes, if you are careful, you will notice the 4 cores were stably and constantly on based on the graphs. Many users wanted this before but no - they do not really empower the phone with doubled FPS as what you may have expected. It's still the same principle - keeping your phone cool. Simply with the feelings of my hand, the current constant 4 cores are not generating any noticeable extra heat comparing to heavy gaming with mpdecision's [2 + unstably on and off 3rd 4th] cores before, thanks to the frequency management.

Well, but I understand 30-31fps on GTA is not satisfying. By simple logic at least a bit should be improved by doubling the cores right? The hotplug driver will have a lot of potential in customization (and optimizations from franco as well), and I will investigate more on it when its in later stage where we can have loads of tunables in it, as in current stage we still don't know what is causing the fps not boosting, before we do some experiments. If timer_rate can temporarily relieve you, just make it your way.

An extra thing we can observe is that, the average FPS is 200% stabler, simply because the 3rd and 4th core does not go on and off like dancing, making every momentary fps closer to the average.​

The next few games, I don't take them as serious as GTAVC, just for your reference.

Next, the long-gone NFS MW

Race: Most Wanted #1 one on one. Your fps will be lower on races with more cars.

Average fps recorded at the end of two races - 43 and 40

Stat for comparison: NFS thalamus (old) hotplugging (only 2 cores used) - 45-50 fps

Yup, this is 4 cores having lower fps than 2 cores. I have left NFSMW in mpdecision tests so maybe you test it for me. I will come back when tunables are available.

The light game Temple Run 2

The stat for this is easy to remember - thalamus (old) hotplug driver interactive having 56-58 fps

Before, in this game the online cores stay on 2 constantly. Now it becomes the 3rd and 4th cores coming on and off, but is much slower than what i call dancing when playing heavy games on mpdecision.

These extra cores have made the FPS to 59-60 on interactive.

Finally you guys' favorite RR3

As seen in my post before it has a huge range - in mpdecision the

range of average fps

was 25-35 on a 22-cars race on my phone. (imagine how big the range of momentary fps are)

And now with the new franco-hotplugging, the range did not change - it is also 25-35 and the most time the average fps spend on is 30.

Again, 2 cores raised to 4 cores, but not much fps improvement can be seen.

Lag? No I didn't have it with RR3. If pinpointing I do witness some minimal slowdowns at the beginning of the race where you rush between 21 cars. Then, its smooth without any disturbance.​

User Interface?

I would not disagree with UBER, lol don't shoot him. I have been using the new hotplug driver (disregard switching between test versions) for 3 days and I am of course a power user (300 apps installed, half ram used up) while franco apparently isn't. Comparing with mpdecision, I do notice a non-smooth animation when opening apps directly from home or from the notifications (for example, gtalk) at 30% of the time. But stuttering at any other parts of the system? I don't see them.

And lets talk about the hotplug driver. It is completely new, written from scratch by franco. It is unrelated to the old hotplug driver that we have been using in the post 90's time, which is by thalamus. This one, by franco, includes a smart algorithm other than simply on/off cores based on the load. (That's why you are seeing stable 4 cores in heavy games) However as said in his post, some threshold changes might help getting rid of the little slowdowns.

Something bad happening after screen on? Yes, at the very beginning of the driver development, there was a lot of 1-core-at-384 locks for many seconds after screen on. But on r115 we do not see it anymore (for me, its 1 day with nothing. in older testing builds, it was once per hour to 2/3 times per day).

If you get anything seriously lagging after screen-on, do this: put perfmon/system monitor shortcut on your main homescreen without any folders. After unlocking if you feel THE TIME HAS COME, IT LAGS AND IS RELATED TO SCREENON - press on the either cpu monitor and focus on the frequency/online cores, and start counting seconds. Report exactly what you observe, and how long the screen-on lag lasts.

Enjoy and be constructive :cool::good: