[Galaxy Note II General] abauer:
These are the result of the benchmarks done to the kernels that are being developed (4 Apr 2013) for the Samsung Galaxy Note 2 .

The settings used are the default that come with N7100XXDMB6 on a GN2 baseband N7100XXDLK7. The changes from the stock areas follows , rooted, TWrecovery 2.3.3.2 , 240 dpi. Brightness used during test 100 %, WiFi on, Nova Launcher Pro, Force GPU rendering (enabled) under Developer options, Power saving option OFF, GPS off , Screen rotation on, sound on 100%, multiwindow active.

Kernels used Stock mb6, Perseus 34.2, Adam 2.2.1 , Neak 1.7

Applications used 3dMark 1.0.0-875 , RL Benchmark:SQLite 1.3 , Vellamo 2.0.2 , CF-Bench 1.2 , AnTuTu Benchmark 3.2.2 , PowerTutor 1.4

Addition applications Linpack for Android 1.2.8, Pi Benchmark 1.0, Quadrant Standart 2.1.1, Geekbench2 2.4.2, SD Tools 3.0.

Methodology used : The benchmarks were run in sequence 1 minutes after a clean reboot was done (cleaning cache and dalvik-cache).

Explanation about the results,

3dMark has 2 scores the first is the normal and the second the extreme suite (Higher is better).

RL Benchmark:SQLite measures the time in seconds needed to dullfill the tests incuded ( smaller is better).

Vellamo has two scores first is HTML5 and second is the metal suite score ( Higher is better).

CF-Bench has three scores first is native score, second is java score and third is overall score ( Higher is better).

AnTuTu just the overall result ( Higher is better).

PowerTutor measures the power usage in milliWatt for the last 5 minutes ( smaller is better).

Linpcack for Android measures floating point performance of the system , has two numbers first is single thread second is multi threaded score in Mflops (higher is better).

Pi benchmark measures the time in seconds to calculate pi, I settled for 200 000 numbers ( smaller is better).

Quadrant Standart 2.1.1 ( higher better).

Geekbench2 2.4.2 cross platform bench ( higher better).

SD Tools measures the read and write speed in Mb/s from the sdcard, first number is writting speed second is read speed (higher better).

Results :

Stock MB6

3dMark 3339x2502

Sql 14.837

Vellamo 1763x610

CFbench 26604x7402x15082

Antutu 16979

Powertutor 803 mW

Perseus 34.2

3dMark 3034x2305

Sql 14.482

Vellamo 1743x612

CFbench 26027x7407x14855

Antutu 17140

Powertutor 816

Adam2.2.1

3dMark 3203x2421

Sql 20.406

Vellamo 1776x619

CFbench 26253x7423x14955

Antutu 17311

Powertutor 805

Neak 1.7

3dMark 3199x2432

Sql 15.855

Vellamo 1710x624

CFbench 26934x7558x15308

Antutu 15911

Powertutor 810

Stock MB5

3dMark	3312x2476

Sql 14.54

Vellamo 1753x610

CFbench 25915x7355x14779

Antutu 17268

PowerTutor 807 mW

Stock MC3

3dMark 3282x2474

Sql 15.181

Vellamo 1768x599

CFBench 26544x7652x15208

Antutu 17024

PowerTutor 502 mW

Linpack	64 x 211

Pi 200 000 53.67

QuadrantS 6991

Geekbench 2059

SD Tools 6.0x12.5

Abyss 2.3.1

3dMark 3200x2387

Sql 14.334

Vellamo 1740x619

CFBench 25870x7077x14595

Antutu 16780

PowerTutor 500 mW

Linpack 62 x 68

Pi benchmark 53.29

QuadrantS 7149

Geekbench 2105

SdTools 6.2x14.9

RedPill 1.42

3dMark 3145x2379

Sql 16.854

Vellamo 1502x618

CFBench 25297x7373x14542

Antutu 16927

PowerTutor 501 mw

Linpack 62x129

Pi benchmark 53.12 s

QuadrantS 6635

Geekbench 2005

SdTools 6.4x12.8 Mb/s

Devil 0.12

3dMark 3177x2315

Sql 14.668

Vellamo 1744x604

CFBench 24850x7335x14341

Antutu 17227

PowerTutor 508

Linpack 64x124

Pi benchmark 53.79

Quadrant S 6661

Geekbench 1696

SdTools 5.8x12.6

The intention of these test is to show the devs their strength/weakness regarding the benchmarks area. These benchmarks are purely synthetic which means they DO NOT represent real life scenario usage.

I am opened to every suggestion possible for further monthly or bimonthly benchs.

Edit: For accuracy have to clarify that about the difference in results with PowerTutor due to removing of an application that used exactly 300 mw the results of the recent test show 300 mw less than the previous ones.