This is a thread I will be updating tonight and tomorrow, I will be comparing benchmark performance for stock, the new paranoid android build and an unofficial cyanogenmod build compiled for the new nexus 7 (It uses the exact cyanogenmod code, nothing custom. Just to tide us over before nightlies. I will test all of these roms with and without jassy's kernel (Yes I will be rooting stock for that.)
Stock Benchmarks:
Antutu Benchmark:
19318
Quadrant Benchmark:
5229
3d Mark Ice Storm Benchmark:
11866
3d Mark Ice Storm Extreme Benchmark:
7210
Stock with Root and Jassy's Kernel (Using Jassy's settings w/ 1890 mhz clock) Benchmarks:
Antutu Benchmark:
21803 (Large improvement)
Quadrant Benchmark:
6757 (Very large improvement)
3d Mark Ice Storm Benchmark:
13048 (Large improvement)
3d Mark Ice Storm Extreme Benchmark:
8120 (Large Improvement)
Don't even think about it
Reserved.
Related
Hello i am new and looking to learn a little bit.My next question for you all is what kernal/rom combinations do you use? what are your quadrant/linpack scores and what is your battery life like??
I am using
Epic experiance rom
With xtreme kernal
setcpu overclocked to 1.2 conservative
Quadrant 1030
Linpak 9.591
PyRo
Heroic Epic w/ Extreme Kernel
SetCPU 1.2 GHz Interactive
Quadrant = 988 (1200 when oc'd to 1.6GHz)
What do you mea by linpack/quadrant scores? I'm a bit new to rooting and haven't seen anyone talk about that yet
quadrant and linpack are available in the market
quadrant benchmarks cpu,I/O and 3d graphics
linpack behcmarks the cpu and looks at floating point operations per second.
PyRo
So Qualcomm just released an awesome new benchmarking tool, its quite comprehensive, go check it out:
https://market.android.com/details?id=com.quicinc.vellamo&feature=search_result
Curious what kind of scores everyone is getting.
On the bonsai 0.1.6 ROM, OC @ 1.4ghz I am getting 1201
Share yours, along with ROM and OC (if any)!
949 on purely stock GT.
Sent from my badass Galaxy Tab 10.1.
951 Stock
949 TouchWiz (Wifi)
I wonder why there are such drastic differences between stock and TW Quadrant scores (17xx vs 22xx).
hoodoomagic said:
951 Stock
949 TouchWiz (Wifi)
I wonder why there are such drastic differences between stock and TW Quadrant scores (17xx vs 22xx).
Click to expand...
Click to collapse
This benchmark focuses more on user experience. Quadrant has very low level tests that are surely effected more by slight hardware optimizations. Also I have never seen consistent scores on quadrant (they fluctuate +/- 200) With this I am consistently getting the same score within 5-10, which is nice.
952 - stock, unrooted
1170, bonzai ROM 0.1.3 overclocked to 1.4Ghz.
I installed this rom the other day and so far everything works except the screen rotation lock button but no rom has that working.
Frst its HC 3.2 ported over from the xoom has the new feature of being able to upscall the smaller apps to the larger screen.
Over clocking is built in just get set cpu and off you go.
My acer is over clocked to 1.5 and here are my benchmark scores.
Useing Quadrant I got 3421 (best of three runs) and frame rates around 45
Useing Linpack I got 45.438 mflpos on single thread in 1.85 seconds and
71.53 mflops on multi-thread in 2.36 seconds again best of three runs
Useing AnTuTu Benchmark I got a score of 6159 and frame rates right at around 60 fps
Useing Vellamo (its new and a benchmark tool for a tablets browser to see how ell the browser performs does things like java and flash stress tests and load speeds of web pages) I got a score of 1072
These are the top 4 bench mark tools for android and these scores while may not look impressive are awsome. in comparisons on benchmark tools grafs these score are much higher them most tablets.
bottom line this tablet rocks.
If your into benchmarking and tweaking as I am please post your results here list benchmark toos used,scores and with rom your running and cpu speed. so we can get and over all view of this remarkable tablet.
I got 1291 from Vellamo using Stock 3.1 with custom Kernel Taboonay CPU 1408Mhz
same rom, same oc, similar scores XD this tablet does rock!!!!!!
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.
Adam Kernel
Thanks, good job
Would you prefer the Adam Kernel ?
dianlb50 said:
Thanks, good job
Would you prefer the Adam Kernel ?
Click to expand...
Click to collapse
Stock has given me no problems so far, it seems it gives a perfect middle point for my usage, as for the optimizations done to specific kernels, the efforts of the dev is not well represented in the results of such simple bench tests bcs the results are within margins of error of such test, but again have to stress out that these are purely synthetic benchs therefore DO NOT apply to real life scenarios.
Here you go fully stock non-rooted xxDMB5.
hagba said:
Here you go fully stock non-rooted xxDMB5.
Click to expand...
Click to collapse
Added results for the Stock MB5 on the OP.
Added results for Stock MC3 , RedPill and Abyss kernels. plus some additional benchmark tools.
Stock DMB5, Perseus Kernel
@ 1.8 ghz.
Sent from my GT-N7100 using xda premium
The point of the tests is to compare the kernels performance side by side in the same environment/setup in MY device, using the DEFAULT settings (no tweaking or OC) with which they are delivered to end user, and if you are careful to notice, I have included MORE than just a simple Antutu result aiming to be as close as possible to real usage scenarios.
abauer said:
The point of the tests is to compare the kernels performance side by side in the same environment/setup in MY device, using the DEFAULT settings (no tweaking or OC) with which they are delivered to end user, and if you are careful to notice, I have included MORE than just a simple Antutu result aiming to be as close as possible to real usage scenarios.
Click to expand...
Click to collapse
My bad, but the OP is TL;DR.
Sent from my GT-N7100 using xda premium
ThankS for posting
Sent from my GT-N7100 using xda premium
Added Devil kernel results.
Perseus 35
Geekbench
Quadrant
Sql
Antutu
Sent from my GT-N7100 using Tapatalk 2
I just bought a used Note II GT-N7105 so before I sell my GT-N7000 I decided to take advantage of it not being needed and run a quick comparison between the Samsung Jelly Bean 4.1.2 firmware and the latest CM11 (20150419). In each case it is absolutely stock except for the installation of Quadrant apk. The stock firmware is really stock (no 3rd party recovery) and CM runs with the CWM version it ships with. No accounts set up, no SIM, nothing removed or added except a 16GB microSD containing no media except a signed recovery and a modern kernel (to enable installing cm) and a cm11 nightly zip. The only additional change from set up is to connect to my wifi.
I ran the test several times on each OS and below are the best results from each:
Samsung 4.1.2
Code:
Overall: 4505
CPU: 6730
Mem: 5003
I/O :8669
2D: 321
3D: 1803
CM11
Code:
Overall: 4030
CPU: 7581
Mem: 3265
I/O: 6865
2D: 243
3D: 2196
Although not every run of the benchmark produces identical numbers the same differences between each firmware are reliably apparent in every test - CM11 has much poorer 2D performance but slightly better 3D. CM has better CPU score but worse Mem and slightly worse I/O scores.
CM 10.1.3 benchmark
Same benchmark, same conditions but this time it's CM 10.1.3 which is the last official stable CM release for the GT-N7000. This time I installed Lanchon's FPBug fix kernel so as to avoid bricking the device right before I sell it... http://forum.xda-developers.com/gal...ernel-fpbug-stable-4-x-kernel-galaxy-t2978107
Code:
Overall: 3765
CPU: 7135
Mem: 2324
I/O : 6094
2D: 314
3D: 2147
These were the best results of 5 runs, all were similar.
The most striking thing is that in CM 10.1.3 2D and 3D performance are excellent, comparable to or even marginally better than stock. CPU score is great. I/O not great but not terrible. Memory score ...oh dear - really bad every time, even worse than CM11 and that was poor already.
Probably in real use the most visible difference to us users is that 2D performance is excellent - no lagging, no jerkiness, no stutters - a really snappy feel. KitKat was a giant leap backwards in this respect.
10.1.3 feels nice and usable so my next post will be one more set of benchmarks in 10.1.3 with JB gapps installed, my google account set up and all my usual apps installed, and everything up to date, as far as is possible.
CM 10.1.3 + Gapps benchmark
CM 10.1.3 with Gapps and Rekey patch. https://play.google.com/store/apps/details?id=io.rekey.rekey
Code:
Overall: 3599
CPU: 7161
Mem: 2368
I/O : 6004
2D: 317
3D: 2147
The undisputed best performer is Samsung Touch Wiz JB 4.1.2, and by a very long way.
Lollipop Benchmarks
I noticed Bauner's NightOwl LP 5.1 (unofficial CM 12.1) got an update this week so I installed it and benchmarked it. As above, totally default except Quadrant installed and my wifi connected. No Gapps:
Code:
Overall: 4577
CPU: 11438
Mem: 3206
I/O : 5853
2D: 235
3D: 2152
This is the only ROM, so far, whose overall benchmark score is better than stock Samsung Jelly Bean. The 2D performance and Mem scores are still poor and the CPU score seems remarkably high and I wonder if it is reliable or credible. I will try Antutu next to see if it produces similar remarkable differences.
julian67 said:
I noticed Bauner's NightOwl LP 5.1 (unofficial CM 12.1) got an update this week so I installed it and benchmarked it. As above, totally default except Quadrant installed and my wifi connected. No Gapps:
Code:
Overall: 4577
CPU: 11438
Mem: 3206
I/O : 5853
2D: 235
3D: 2152
This is the only ROM, so far, whose overall benchmark score is better than stock Samsung Jelly Bean. The 2D performance and Mem scores are still poor and the CPU score seems remarkably high and I wonder if it is reliable or credible. I will try Antutu next to see if it produces similar remarkable differences.
Click to expand...
Click to collapse
The cpu scores can be higher, because my higher thermal throttling values.
With the stock values the cpu is running very fast into thermal throttling.
The differences in I/O and memory scores can be come because lollipop is much more complex and there are running much more services in the background.
It would be very interesting to see the results with the raw kernel.
If there the scores for I/O and mem are higher I should check which changes in my kernel are causing the regression
OK the thermal throttling explains a lot.
Last night I ran antutu on JB and on NightOwl. My Note actually became so hot after these benchmarks on LP that I shut it down immedaitely afterwards. Not warm, but actually hot (this in a room at about 15 C). Running Samsung JB it is usally cool to the touch and occasionally gets slightly warm. Perhaps there is a happy medium range that doesn't lead to such experiences? I would hate to run this in a hot climate (I once killed a £1300 laptop by trying to save a few pennies on AC in Bangkok... ha ha lesson learned).
I will do some more tests this evening or tomorrow (family day out today) and will include raw kernel.
julian67 said:
OK the thermal throttling explains a lot.
Last night I ran antutu on JB and on NightOwl. My Note actually became so hot after these benchmarks on LP that I shut it down immedaitely afterwards. Not warm, but actually hot (this in a room at about 15 C). Running Samsung JB it is usally cool to the touch and occasionally gets slightly warm. Perhaps there is a happy medium range that doesn't lead to such experiences? I would hate to run this in a hot climate (I once killed a £1300 laptop by trying to save a few pennies on AC in Bangkok... ha ha lesson learned).
I will do some more tests this evening or tomorrow (family day out today) and will include raw kernel.
Click to expand...
Click to collapse
This values should not harm your device. I'm using it for a long time, and also with many hours of cpu stress testing. The overheat protection values are not changed.
see http://forum.xda-developers.com/galaxy-note/general/antutu-benchmarks-nightowl-lp-12-1-vs-t3093720 for antutu benchmarks (ongoing).