[Kernel] (ver 041) Mako KK 4.4 (UV/OTG/CPU/GPU OC/Hybrid Linux 3.4+) [08-02-14]

simms22

Recognized Contributor - R.I.P
Jun 4, 2009
34,056
25,931
0
BROOKLYN!
www.androidcommunity.com
yeah.. the benchmark should only be used under controlled environment.

Posting benchmark scores is really almost pointless.

Unlike desktop CPUs, our phones are PASSIVELY cooled, so we are at the mercy of the CPU and Ambient temperature (ie, if the CPU heats up, we have NO OTHER WAYS to cool it except force it to run at lower frequencies where as on desktop, with active cooling, the fans/coolant can go faster to carry away more heat keeping the CPUs at a constant operating temperature).

To make benchmark really meaning full, you will need to operate under the following conditions:

1. Run in airplane mode
2. disable all background operations
3. Note the ambient temperature of the ROOM or environment
4. Cool the phone to a known operating temperature
5. Run the benchmark and observe if thermal throttling kicked in or not and for how long

posting benchmark scores is pointless, unless your just doing it for the fun of it, comparing with friends. just doing them to do them is pointless. also, they are a good way to see if changes that you made in your kernel affect the device in a good or bad way.

1. do not put it in airplane mode, do have a mobile data connection/wifi on. as many benchmarks need you to have a data connection.
2. right, kill whatever is working in your background.
3. i do benchmarks in warm and cool environments. some benchmarks prefer cooler temps, some prefer warmer temps. most benchmarks that stress the cpu will want cooler temps(except quadrant likes warmer temps), while the benchmarks that put more stress on the gpu then the cpu it wont matter.
4. generally, 20C-30C cpu temps are a good starting point. a little lower if you are benching the higher cpu speeds(above 1.7ghz).
5. i prefer to disable thermal throttling while benchmarking. with thermal throttle on, you just dont know what your device can actually do.
6. have a consistant setup for your benchmarking, keep it the same for every time you benchmark.
7. also, when benchmarking, lock in your cpu speed, dont let it scale. for example, i like to benchmark at 1836mhz, i set my high and low cpu speed to 1836. many of the benchmarks dont stress the device enough and the cpu will scale up and down. when it scales, you dont actually know what cpu speed its testing.

and this is absolutely right, be consistent and thorough..

repeat the same benchmark several times UNDER THE SAME EXACT conditions from steps 1~5
then take the average scores in order to really use the benchmark to judge performance...

Unless you work for Toms Hardware or Anantech, it's really time consuming and lot of preparation required to do a "simple" benchmark and make their results MEANINGFUL :angel:
 
Last edited:

simms22

Recognized Contributor - R.I.P
Jun 4, 2009
34,056
25,931
0
BROOKLYN!
www.androidcommunity.com
Are people really still using that? It's buggy :(

My scores with latest Ultimate kernel.

Connor Baker
they fixed that bug in yesterdays update. btw.. ;)




---------- Post added at 05:14 PM ---------- Previous post was at 05:13 PM ----------

Yeah, I agree :/.

Heh, heh. I see what you did ;).

You used the "Simms Glitch" (I don't have a better name) to get over 30,000.

Sent from my Nexus 4 using Tapatalk 2
that would be more accurately called Connors Glitch, since he brought it to my attention :angel:
 

faux123

Senior Member
Dec 16, 2010
8,536
34,426
113
West Los Angeles
www.canonspike.com
posting benchmark scores is pointless, unless your just doing it for the fun of it, comparing with friends. just doing them to do them is pointless. also, they are a good way to see if changes that you made in your kernel affect the device in a good or bad way.

1. do not put it in airplane mode, do have a mobile data connection/wifi on. as many benchmarks need you to have a data connection.
2. right, kill whatever is working in your background.
3. i do benchmarks in warm and cool environments. some benchmarks prefer cooler temps, some prefer warmer temps. most benchmarks that stress the cpu will want cooler temps(except quadrant likes warmer temps), while the benchmarks that put more stress on the gpu then the cpu it wont matter.
4. generally, 20C-30C cpu temps are a good starting point. a little lower if you are benching the higher cpu speeds(above 1.7ghz).
5. i prefer to disable thermal throttling while benchmarking. with thermal throttle on, you just dont know what your device can actually do.
6. have a consistant setup for your benchmarking, keep it the same for every time you benchmark.
7. also, when benchmarking, lock in your cpu speed, dont let it scale. for example, i like to benchmark at 1836mhz, i set my high and low cpu speed to 1836. many of the benchmarks to stress the device enough and the cpu will scale up and down. when it scales, you dont actually know what cpu speed its testing.

and this is absolutely right, be consistent and thorough..
Ha, you, simms22, are the master of benchmarks here on xda. :)

Sent from my Nexus 4 using Tapatalk 2
 

VenomousSVT

Member
Apr 14, 2010
39
5
0
Charlotte NC
I've always run the mainline kernel and decided to try the 13tbu this time around.. I get boot loops with every attempt to reboot after flashing it. I flash back to 13tbm and it boots fine... Anyone have any suggestions?

Sent from my Nexus 4 using Tapatalk 2
 

faux123

Senior Member
Dec 16, 2010
8,536
34,426
113
West Los Angeles
www.canonspike.com
I've always run the mainline kernel and decided to try the 13tbu this time around.. I get boot loops with every attempt to reboot after flashing it. I flash back to 13tbm and it boots fine... Anyone have any suggestions?

Sent from my Nexus 4 using Tapatalk 2
Your phone just can't handle tbu. Tbm is fine :)

Sent from my Nexus 4 using Tapatalk 2
 

itshotinhere

Senior Member
Sep 13, 2009
420
68
0
I have .48 as well. As soon as CM M3 came out yesterday, I installed the newest faux kernel M from 4/11. Soon after, my phone began resetting for no apparent reason.

I've since uninstalled faux and gone with the CM kernel instead.
I'm also .48 and have had zero issues. -125 UV and working flawlessly here. Running TBU 13 on PA 3.1.


Sent from my Nexus 4 using xda premium
 
Last edited:

lowrider262

Senior Member
Jan 26, 2011
1,391
553
0
Racine, WI
13tbm running great, battery looking very promising too. Just wanted to drop in and say thanks to faux for all the work u put into this. Also just bought your faux clock app, figured it was about time since I been using your kernels for a couple years now lol. Quality stuff bro:thumbup:

Sent from my Nexus 4 using xda premium
 

aSquard

Senior Member
Jan 26, 2009
1,204
206
0
DF-Dub
Wow your battery really jumped up by that much? Amazing! :eek:
What was your screen on time if I may ask?
It was maybe 3 hrs screen on time - was at work mainly so I answered emailed and Goole Talk from the PC instead

Nexus⁴ Enlightened with ParanoidAndroid and XDA Premium
 

chlehqls

Senior Member
Jun 18, 2011
1,700
349
0
Toledo, OH
12m started to randomly reboot for me as well. I just wiped and reflashed images and haven't installed the latest release yet. Stock kernel is soooo good. Only downside is, I don't get gamma hax...