Hi, my name is Davis Woody. I'm a mechanical engineering student at UTC in Chattanooga, TN. I will be putting together this guide over the next few weeks. I am trying to be as scientific as possible with these scores so I will adhere to several rules for the tests. I would also love to test network strength, battery life, file transfer speed, and network speed but there are simply too many confounding variables. Can't wait to populate this thread.
My testing standards
1. I will allow each ROM to settle over the period of 12-24 hours before testing.
2. Identical applications will be installed on the different ROMs.
3. Identical phone settings (GPS, network, wifi, ect.) will be used during the tests
4. I will test 10 times at 1180mhz and 10 times at highest stable OC. I will note this maximum frequency in the data.
5. I will use a sample size of 10 tests to compute the sample average and standard deviation.
EDIT
If you would like for me to test a specific ROM and kernel combination, please feel free to ask. No request will be ignored.
It has been brought to my attention that Quadrant is not completely accurate for dual core. I am testing with CF Bench as well, the numbers seem to have a strong correlation.
ROM: VirusROM RC1 AOSP 1.13.651.7 2.3.3
Note: This ROM is so tight. It's about as close to CM as I've seen for the 3d. CF Bench is low for this ROM. My lowest quadrant was 3148. :O
Kernel: RCMix 2.6.35.10
Clock Freq.: 1836
CF Bench (mean score, std. dev)
Native: 7610.6, 123.80
Java: 2558.0, 66.50
Total: 4588.4, 82.80
Quadrant Standard (mean score, std. dev)
3650.3, 193.40
Underclock 1188mhz quad. score
2318, 62.64
ROM: Synergy ROM rev 318 w/ Sense 2.3.3
Note: Please note that I had disabled the EXT4 partitioning which can increase quad. scores. This is the fastest Sense ROM I've tested so far. Very stable w/ revision 318.
Kernel: RCMix 2.6.35.10
Clock Freq.: 1836
CF Bench (mean score, std. dev)
Native: 44202, 38.64
Java: 1791.6, 122.90
Total: 5555.4, 66.11
Quadrant Standard (mean score, std. dev)
3417.5, 245.55
Underclock 1188mhz quad. score
2215.2, 91.95
Underclock 1188mhz CF score
Native: 8569.0, 335.85
Java: 2150.3, 576.10
Total: 4660.5, 479.10
ROM: Showdown ROM 1 w/ Sense 2.3.3
Kernel: 2.6.35.14 Helicopter
Clock Freq.: 1836
CF Bench (mean score, std. dev)
Native: 11783, 650
Java: 2825.0, 675.72
Total: 6398.5, 592.3
Quadrant Standard (mean score, std. dev)
2920.3, 210.58
Underclock 1188mhz quad. score
2026.6, 128.68
ROM: Supra 1.5 AOSP 2.3.3
Note: Great ROM but it has its share of issues.
Kernel: SilverNeedles no lights 1.1.3
Clock Freq.: 1728
CF Bench (mean score, std. dev)
Native: 11341, 174.15
Java: 3270.2, 66.92
Total: 6498.2, 106.00
Quadrant Standard (mean score, std. dev)
2902.1, 205.72
Underclock 1188mhz quad. score
2125, 51.64
ROM: viperROM RC1.3 w/ Sense 2.3.3
Note: Great ROM for a daily driver.
Kernel: SilverNeedles no lights 1.1.3
Clock Freq.: 1728
CF Bench (mean score, std. dev)
Native: 11299.0, 117.80
Java: 3279.0, 40.0
Total: 6487.0, 65.71
Quadrant Standard (mean score, std. dev)
2798.2, 159.93
Underclock 1188mhz quad. score
2168.2, 84.35
ROM: Supra ROM 1.5 w/ Sense 2.3.3
Note: Great ROM for a daily driver.
Kernel: SilverNeedles no lights 1.1.3
Clock Freq.: 1728
CF Bench (mean score, std. dev)
Native: 11042, 239.4
Java: 3251, 152.2
Total: 6475, 125.4
Quadrant Standard (mean score, std. dev)
2773.33, 186.17
Underclock 1188mhz quad. score
2061.5,213.34
ROM: Douchless ROM w/ Sense 2.3.3
Note: Tether issues
Kernel: SilverNeedles 1.0
Clock Freq.: 1728
CF Bench (mean score, std. dev)
Native: 10787,192.2
Java: 1816,87.87
Total: 5404.8,120.86
Quadrant Standard (mean score, std. dev)
2647.8, 363.76
Underclock 1188mhz quad. score
2058.8,57.85
Underclock 1188mhz CF score
Native: 8748.4,118.7
Java: 1360.8,79.0
Total: 4321,95.2
ROM: SuperShooter3D(Bl00dy3dition)v.2 w/ Sense 2.3.3
Note:I'm not sure if this was a "clean" install. Got some FCs
Kernel: SilverNeedles no lights 1.1.3
Clock Freq.: 1728
Quadrant Standard (mean score, std. dev)
2239.8, 170.51
Underclock 1188mhz quad. score
1397.1, 269.10
chillfancy said:
Hi, my name is Davis Woody. I'm a mechanical engineering student at UTC in Chattanooga, TN. I will be putting together this guide over the next few weeks. I am trying to be as scientific as possible with these scores so I will adhere to several rules for the tests. I would also love to test network strength, battery life, file transfer speed, and network speed but there are simply too many confounding variables. Can't wait to populate this thread.
My testing standards
1. I will allow each ROM to settle over the period of 12-24 hours before testing.
2. Identical applications will be installed on the different ROMs.
3. Identical phone settings (GPS, network, wifi, ect.) will be used during the tests
4. Overclock speed will be at what I deem to be the highest stable level for each ROM. I will note this frequency in the data.
5. I will use a sample size of 10 tests to compute the sample average and standard deviation.
EDIT
If you would like for me to test a specific ROM and kernel combination, please feel free to ask. No request will be ignored.
It has been brought to my attention that Quadrant is not completely accurate for dual core. I am considering testing with CF bench as well.
Click to expand...
Click to collapse
you may as well leave off quadrant. its easily altered and not really accurate.
Seriously though, quardrant scores don't mean a much. The rom that claims to have the highest quads was not the fastest, but it was the most buggy (in my experience). And the rom I found to be the smoothest/fastest and lag-free had a quadscore 100 below stock lol.
chillfancy said:
...I am trying to be as scientific as possible with these scores so I will adhere to several rules for the tests. I would also love to test network strength, battery life, file transfer speed, and network speed but there are simply too many confounding variables...
My testing standards
1.
2.
3.
4. Overclock speed will be at what I deem to be the highest stable level for each ROM. I will note this frequency in the data.
Click to expand...
Click to collapse
Davis, If you're going to be scientific you've got to compare apples to apples, so ANY variables are unacceptable, including clock speed. To be completely objective, you need to compare all roms at 1.2Ghz (1188mhz) ... otherwise, any comparison is trash. The fact that a given kernel/rom combination can run at 2Ghz is nice, but it must be tested at 1.2Ghz for any comparison of battery life, data transfer rates, benchmarks, etc., to be meaningful.
Your goal is noble, but your method needs to be correct.
Good luck!
Success100 said:
you may as well leave off quadrant. its easily altered and not really accurate.
Click to expand...
Click to collapse
I don't think quadrant is completely useless. It does run full 2d and 3d to test the rendering performance.
oldjackbob said:
Davis, If you're going to be scientific you've got to compare apples to apples, so ANY variables are unacceptable, including clock speed. To be completely objective, you need to compare all roms at 1.2Ghz (1188mhz) ... otherwise, any comparison is trash. The fact that a given kernel/rom combination can run at 2Ghz is nice, but it must be tested at 1.2Ghz for any comparison of battery life, data transfer rates, benchmarks, etc., to be meaningful.
Your goal is noble, but your method needs to be correct.
Good luck!
Click to expand...
Click to collapse
I realized that testing at stock is important to really compare ROMs ,but with that said, a ROM that can run 1.8 stable is going to be a faster daily driver than one that crashes at 1.5. We'll see how the testing goes. And I'm not testing signal, battery life, or data rates.
chillfancy said:
I realized that testing at stock is important to really compare ROMs ,but with that said, a ROM that can run 1.8 stable is going to be a faster daily driver than one that crashes at 1.5. We'll see how the testing goes. And I'm not testing signal, battery life, or data rates.
Click to expand...
Click to collapse
Um, then I'm confused ... what exactly is it that you're testing? Are you just wanting to see which rom/kernel can survive the highest clock speed, regardless of battery life, or temperature (I guess?), or efficiency (however you want to define that)? If that's all you're doing, then why even bother with any "settling in" period at all? Heck, just keep cranking up the clock speed until the machine freezes or reboots, and report back to us, lol!
Carry on...
Quadrant is flawed to begin with. And you are testing with a flawed testing software for accurate results? Try this, run quadrant 5 times...you will see one of those scores will win, the others will vary widly. And this is on your phone!... Give me a break.
life64x said:
Quadrant is flawed to begin with. And you are testing with a flawed testing software for accurate results? Try this, run quadrant 5 times...you will see one of those scores will win, the others will vary widly. And this is on your phone!... Give me a break.
Click to expand...
Click to collapse
The sample size is 10. I'm running 2 different softwares. It's not just picking the highest outlier.
More power, but all your doing is spreading the myth of quadrant being the end all for performance. Not counting what apps are running, any tweaks each rom has..even stock and memory trash cleaning mechanisms, what natural speed of the phone is depending on the bus...yea it sure will be accurate....
So much venom in the forums... Geez.
So quadrants sucks. Oh well, as long as this guy isn't using the I/O tweak that shoots quadrants sky high, does several passes and than takes the average etc.
It sounds like he has a good foundation.
Except the whole overclocking thing. That kindof destroys your whole foundation and everything should be run at stock speed. Your taking all these steps to remove variants and then throwing a giant one in?
"Gentleman. We are going to study the effect of gravity on these rabbits. They will be weighted down at the base of there paws to keep them upright and from floating around.... Except this one. He will be stabbed, gutted and have the weight implanted into his abodmen. For funsies"
Just drop the overclocking part :-D
chillfancy said:
Hi, my name is Davis Woody. I'm a mechanical engineering student at UTC in Chattanooga, TN. I will be putting together this guide over the next few weeks. I am trying to be as scientific as possible with these scores so I will adhere to several rules for the tests. I would also love to test network strength, battery life, file transfer speed, and network speed but there are simply too many confounding variables. Can't wait to populate this thread.
My testing standards
1. I will allow each ROM to settle over the period of 12-24 hours before testing.
2. Identical applications will be installed on the different ROMs.
3. Identical phone settings (GPS, network, wifi, ect.) will be used during the tests
4. Overclock speed will be at what I deem to be the highest stable level for each ROM. I will note this frequency in the data.
5. I will use a sample size of 10 tests to compute the sample average and standard deviation.
Click to expand...
Click to collapse
Fantastic Idea and thanks for this! I'll be looking forward to seeing where they stand.... may I make a suggestion and start the testing after a reboot? Some roms performance varies and that'd make them all equal say .. hit the power button... wait a minute then start the ten tests.
Either way this will be a great reference for test jockeys
Although quadrant is not 100% reliable in determining how fast roms are but it will be interesting to see the results of each rom.
I'm just impressed that you are taking on such a tedious and time consuming test. Best of luck!
felacio said:
Except the whole overclocking thing. That kindof destroys your whole foundation and everything should be run at stock speed. Your taking all these steps to remove variants and then throwing a giant one in?
Click to expand...
Click to collapse
I like the overclocking test. Not including it would be like reading a car review and bashing them for testing a top speed higher than 75 MPH, since that's pretty much the highest speed limit you'll see anywhere.
Sure, you can state the 0-60 time and compare those, but who's gonna be hurt by knowing the top speed?
I want to see how well my rom will work when I crank that stuff up!
Assuming however, he does provide data for both the 1188 speed and the OC speed. Otherwise, he is just being silly. Lol.
BlaydeX15 said:
I like the overclocking test. Not including it would be like reading a car review and bashing them for testing a top speed higher than 75 MPH, since that's pretty much the highest speed limit you'll see anywhere.
Sure, you can state the 0-60 time and compare those, but who's gonna be hurt by knowing the top speed?
I want to see how well my rom will work when I crank that stuff up!
Assuming however, he does provide data for both the 1188 speed and the OC speed. Otherwise, he is just being silly. Lol.
Click to expand...
Click to collapse
Yeah... I don't agree with your analogy. But yeah, the OC should stay. But at the beginning it was forefront and he later decided to add the stock speed.
Your analogy fails because 75mph is 75mph. You can't go faster than 75 without going 76. And so on..
On the phone though. 1.2ghz can swing widely with how efficient the phone runs in that speed. It can be faster or slower depending on how the is is running. Look at Sense vs AOSP.. omg the difference! So the analogy that would work in that case is more "at 75mph. This car guzzles 20mpg. But this one does the same and at 30mpg" but at the end of that. Append ".. but the first car can go 180mph without an issue!"
Use linpack
Sent from my HTC EVO 3d
Root: revolutionary
Recovery: Twrp cwm 4
ROM: Synergy rls318 (I want aosp)
oldjackbob said:
...what exactly is it that you're testing?
Click to expand...
Click to collapse
Still waiting for an answer to this question.
Sorry, but I'm just not seeing the point to this whole effort.
mikedavis120 said:
Use linpack
Sent from my HTC EVO 3d
Root: revolutionary
Recovery: Twrp cwm 4
ROM: Synergy rls318 (I want aosp)
Click to expand...
Click to collapse
I'll consider it but CF Bench measures MFlops too so it might be a bit redundant.. It is taking me about an hour to collect and process the data on a single ROM already.
oldjackbob said:
Still waiting for an answer to this question.
Sorry, but I'm just not seeing the point to this whole effort.
Click to expand...
Click to collapse
The goal is to use testing standards, benchmarking software, and statistics to describe how the different ROMs score. I understand it isn't going to prove that once ROM is "better" than another but it will be very useful for others.
Cool I like it! Stock and OC is key! Also I think the max overclock is good too, if you find a rom that's stable at 2ghz(some people have done it) it'll help point others to those high speed roms. If you do come across one that's stable at 2ghz I would like to still see a 1.8ghz test.
For a battery test could you play a 5 or 10 min vid clip after a fresh reboot and a charge, then just record the percent dropped and voltage. Or just record the amount of batter drained before and after your bench marks. Using a app like battery indicator would be easy too.
Related
I've been running some really basic tests on the new Roms and kernels that are starting to pop up and I want to know if any of you agree with me on this. While using Cherryblur v1.4d and the stock ATT kernel I can get around 3500 on Quadrant Standard (I know its not the best benchmarking tool out there). Thats on a fresh reboot 2nd run. Then I flashed Faux123 OC, pushed the clock speed to max 1.1 and min 1.1, set on boot, ran the same test. Fresh reboot, 2nd run and got the exact same score...weird. So if this is the case whats the point of the OC? Has anyone else seen similar results? Or is there perhaps something I'm missing?
Hi,
You are only overclocking by 10%, even if it was 50%, Quadrant is not a cpu benchmark, what will impact it most is the 3D bits and the database tests. Data2Ext on the htc legend will almost double the scores with a fast external sd card used for data.
For these kernels you should be asking yourself, where did the source come from and is it a later version than what is compiled stock, and was it even designed for the Atrix?
Cheers!
Ya...quadrant isn't really designed for CPU but I'm pretty sure it takes it into some type of performance boost. Like on my Nexus the same .1 overclock boosts the Q score a good bit.
Yeah, quadrant scores are sketchy at best.
My cm7 nook color OC'd to 1300 scored 3100+
So I overclocked my GSII to 1.6Ghz, and ran benchmarks and it was blazing fast. So what's the point of overclocking other than running benchmarks? I'd rather not have my processor running at 1.6Ghz all the time and draining battery power. I actually prefer underclocking to save power. So my question is - how else can I benefit from overclocking my device?
yo whyd you put this in the dev section? get flame suit on brotha.
miui+siyah = beast
Well its obviously to have your device performance better. Honestly it's not really practical to run higher than 1.2 ghz though.
You also put this in the wrong section. Prepare your anus.
NJGSII said:
Well its obviously to have your device performance better. Honestly it's not really practical to run higher than 1.2 ghz though.
Click to expand...
Click to collapse
But in what ways other than benchmarks? Am I really going to notice a difference if I kick it up to 1.4 or 1.6Ghz when browsing the web or playing Angry birds or something?
where is the download link and what does it do?
Some serious development going on here.. [\sarcasm\]
OP even if you crank it up to 1.6GHz, unless your isolating that step, your phones not using that clock speed unless your doing sh*t on your phone. It will increase how fast apps or menu's open navagating throughout the phone. Your making the CPU think faster so your phone ends up doing its tasks little and big ...faster
But dude.. Googling the benefits of OC could have giving you an answer ..and FASTER. Lol
Sent from my SAMSUNG-SGH-I777 using xda premium
The benefits of overclocking you ask? Let me tell you just a few.
1. For every overclocked phone, one dollar is anonymously donated to poor and starving children, families, and college students across the world [citation needed].
2. Overclocking your phone emits a low frequency gamma wave inhibitor which in some cases, tested by prestigious scientists, has proven to protect you from harmful UV rays from the sun, nuclear fallout, increases neural synapse action in the brain, lowers bad cholesterol AND blood pressure, increases lifespan up to a minimum of three years, and is a natural antimicrobial agent that also interacts with your white blood cells to not only increase output and strength, but also breaks down the DNA rebuilding process by inhibiting protein synthesis in a wide variety of foreign microbes in your body.
3. Overclocking has been used to successfully treat sever depression, obesity, dementia, and AIDS.
4. With an overclocked phone, it's been observed waiting times for and inside elevators is severely decreased.
5. Bad driver? Accident prone? Overclocking has been shown to heighten driver awareness and overall skill.
6. It speeds up your phone on a day to day basis, with some, but not terribly noticeable battery drain [citation needed].
Sent from my SAMSUNG-SGH-I777 using xda premium
Overclocking is entertaining. But I'm running the Unnamed rom on my device and have it UNDER clocked to 800mhz. Crazy good battery life and zero lag.
Overclocking is pointless as it runs everything great already. I'm waiting to overclock until my phone is outdated and my contracts about to expire.
While its rather easy to do there really isn't any benefit to overclocking the SGSII. Yes, it'll run a little faster and your Angry Birds might run smoother (really? ), but it'll also mean a little more heat and more battery drain all to accomplish something you really won't be able to get any real advantage from.
another reason to overclock would be bragging rights
DJSLINKARD said:
another reason to overclock would be bragging rights
Click to expand...
Click to collapse
Only reason in my opinion lol...
Sent from my Galaxy S II (I777) - 1.4Ghz
For this phone, it's pretty much useless. The phone runs great without the faster clock speeds.
On the other hand, if it was a snapdragon processor, you'd need 1.5 GHz just to be marketable next to this phone (and 1.8GHz to perform as well in day to day usage.)
One reason could be... Because we can!
Sent from my SAMSUNG-SGH-I777 using xda premium
highaltitude said:
One reason could be... Because we can!
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
haha ... love it!
Sent from my SAMSUNG-SGH-I777 using xda premium
MattMJB0188 said:
So I overclocked my GSII to 1.6Ghz, and ran benchmarks and it was blazing fast. So what's the point of overclocking other than running benchmarks? I'd rather not have my processor running at 1.6Ghz all the time and draining battery power. I actually prefer underclocking to save power. So my question is - how else can I benefit from overclocking my device?
Click to expand...
Click to collapse
Most people overclock for a smoother/snappier experience. I notice that roughly 20% increase in scrolling/tabbing around. Also you can think of it like this:
1.4ghz will finish tasks faster then 1.2, that way taking less battery. You could also undervolt that 1.4 to 1.2 (1275mV), so your finishing tasks quicker while draining no more then stock.
I switch between 1.4 and 1.0 every other day it seems. 2 months later, still looking for the right one for me. 1.6 should only be for benchmarking imo, epeen.
cwc3 said:
1.4ghz will finish tasks faster then 1.2, that way taking less battery. You could also undervolt that 1.4 to 1.2 (1275mV), so your finishing tasks quicker while draining no more then stock..
Click to expand...
Click to collapse
It's not that simple.
There are dozens of bottlenecks in these devices (and any other computer), and 9 times out of 10, it's NOT the processor. Persistant storage, RAM, bus speeds, etc - all those things will ensure that a 10% bump in processor speed will NOT give you a 10% decrease in run time for a given typical application. In many cases, you'll see no speed increase at all, as it takes the same amount of time to flush to persistant storage no matter how fast the write cache fills.
I'm not suggesting that a person shouldn't O/C, but don't be surprised when going from 1200MHz to 1400MHz makes no visible difference other than the battery draining slightly quicker.
I know someone is going to respond that the processor will bump back down to a slower speed and therefore it runs at the higher speed for less time, etc. However, unless you have the governor set to poll for usage so often that the governer is driving your clocks up to max, it's not going to poll often enough to make much (if any) difference.
Think of it this way: We both own a mustang, but mine is a V6 at 220HP and yours is a V8 at 300HP. In theory, yours can accel faster and maintain a higher top speed. In reality, neither one of us can go faster than the car in front of us (but you'll burn more gas doing it.) (Of course, you'll have more fun in yours.)
I hope this helps with a very common misconception.
Take care
Gary
garyd9 said:
It's not that simple.
There are dozens of bottlenecks in these devices (and any other computer), and 9 times out of 10, it's NOT the processor. Persistant storage, RAM, bus speeds, etc - all those things will ensure that a 10% bump in processor speed will NOT give you a 10% decrease in run time for a given typical application.
Click to expand...
Click to collapse
Very true. Also I am guessing in gaming, that OC will drain your battery quite well.
Consider I mostly do Web browsing on my phone (I need a tablet), 1.4 is a much better browser experience imo. Worth the 100mV.
garyd9 said:
Think of it this way: We both own a mustang, but mine is a V6 at 220HP and yours is a V8 at 300HP. In theory, yours can accel faster and maintain a higher top speed. In reality, neither one of us can go faster than the car in front of us (but you'll burn more gas doing it.) (Of course, you'll have more fun in yours.)
I hope this helps with a very common misconception.
Click to expand...
Click to collapse
Excellent analogy.
Sent from my Galaxy SII
While for now Overclocking is mainly just done for fun im hoping that closer to my upgrade time that i will be overclocking for more actical reasons. That is the way it was for my Captivate. I enjoy trying to push my hardware to its limits. Ive gotten my GSII so far to a stable 1700mhz but i think i can squeak out a little more speed especially with the gpu down clocked a little. I run it at 1400MHZ Though with the gpu forced at 267mhz.
ANTUTU BENCHMARKING :- The "OPEN" Discussion (11/12/12) 10125 BEST SCORE SO FAR
First things First
I HAVE THE EXTENDED BATTERY
Secondly
TO ME
Benchmarks DO gauge the ACTUAL Performance of MY phone (when pushed)
right your still reading
HELLO
BENCHMARKING
I've had my phone since day one of the uk release, and have flashed many many many roms, and kernels, and hboot's , experimenting with different oc programs, governors, frequencies and voltages, and ui in comparison to smoothness is greatly improved the higher the antutu score
REGARDLESS OF BATTERYLIFE.
that said.
the best concoction I cooked up, with the best ingredients from many experienced chefs (so far) is
Rom:- HTC Stock ICS LATEST
Kernel:-Yoda 10.1
Tweaks:- Pedja kernel tweak app v3.3.3/ Chainfire 3D/ Pimp My Rom
oc'd @ max and min 1.836 ghz
Uv @ 1312 mv
performance CPU Governor
I/0 Scheduler SIO @ 2048kb sd cache
No vsync
my score was]
10125
Please leave detailed Descriptions of
ROM
KERNEL
PATCHES
CPU GOVERNOR
I/O SCHEDULER
SD CLASS/SIZE
OV/UV CHANGES
THANKS IN ADVANCE
mOAr voltz
argument invalid, benchmark numbers does not equal performance. research how to trick benchmarking apps.
gav-collins1983 said:
first things first, I HAVE THE EXTENDED BATTERY. secondly, TO ME, benchmarks DO gauge the performance of MY phone, ......
right your still reading, hello,
benchmarking, I've had my phone since day one of the uk release, and have flashed many many many roms, and kernels, experimenting with different oc programs, governors, frequencies and voltages, and ui in comparison to smoothness is greatly improved the higher the antutu score, regardless of battery life.
that said.
the best concoction I cooked up, with the best ingredients from many experienced chefs (so far) is
leedroids rom v 5.3.0
leedroids kernel v4.1.0
system tuner pro 1.863 Max 192 min (added 0.25mv to 1.863 frequencie because it seemed to struggle)
and leedroids ondemand forced dual core patch
my score was 7004
rant over , lol
Click to expand...
Click to collapse
Jesus Christ is this what this site has came to?
bloodrain954 said:
argument invalid, benchmark numbers does not equal performance. research how to trick benchmarking apps.
Click to expand...
Click to collapse
it's not an argument, I clearly state, that this is to "ME" on "MY" phone,
also, I'm not trying to trick my benchmarking app, what I've seen over 28 weeks is a clear indication, to "ME" on "MY" phone , that ui is smoother and faster on higher benchmark scores, simple as that
Well duh, having an overclocked CPU results in higher benchmarks because the phone can complete things faster. This translates to a smoother UI.
The problem is that benchmarks are affected by so many things that might not reflect accurately the performance of the phone. And comparing different phones is useless because of skins and different hardware performing better in tests but worse in real life.
Faster CPU = higher benchmarks and smoother UI. That doesn't mean that higher benchmarks = smoother UI.
Sent from my HTC Evo 3D using XDA Premium App
SoraX64 said:
Well duh, having an overclocked CPU results in higher benchmarks because the phone can complete things faster. This translates to a smoother UI.
The problem is that benchmarks are affected by so many things that might not reflect accurately the performance of the phone. And comparing different phones is useless because of skins and different hardware performing better in tests but worse in real life.
Faster CPU = higher benchmarks and smoother UI. That doesn't mean that higher benchmarks = smoother UI.
Sent from my HTC Evo 3D using XDA Premium App
Click to expand...
Click to collapse
it does to me from what I've seen, I've made that white clear,
what's with all the hating on evo 3d , we never had this in the desire hd forums.
gav-collins1983 said:
it does to me from what I've seen, I've made that white clear,
what's with all the hating on evo 3d , we never had this in the desire hd forums.
Click to expand...
Click to collapse
Lololol your not in Kansas anymore
Sent from my SPH-D710 using XDA App
one time, at band camp...
sent from Evo
SoraX64 said:
Well duh, having an overclocked CPU results in higher benchmarks because the phone can complete things faster. This translates to a smoother UI.
The problem is that benchmarks are affected by so many things that might not reflect accurately the performance of the phone. And comparing different phones is useless because of skins and different hardware performing better in tests but worse in real life.
Faster CPU = higher benchmarks and smoother UI. That doesn't mean that higher benchmarks = smoother UI.
Sent from my HTC Evo 3D using XDA Premium App
Click to expand...
Click to collapse
No, not, duhhhhh, overclocking also causes instability in some cases, more so if incorrect/not optimized voltages per frequency and governor in kernel, and smooth ness is affected
gav-collins1983 said:
first things first, I HAVE THE EXTENDED BATTERY. secondly, TO ME, benchmarks DO gauge the performance of MY phone, ......
right your still reading, hello,
benchmarking, I've had my phone since day one of the uk release, and have flashed many many many roms, and kernels, experimenting with different oc programs, governors, frequencies and voltages, and ui in comparison to smoothness is greatly improved the higher the antutu score, regardless of battery life.
that said.
the best concoction I cooked up, with the best ingredients from many experienced chefs (so far) is
leedroids rom v 5.3.0
leedroids kernel v4.1.0
system tuner pro 1.863 Max 192 min (added 0.25mv to 1.863 frequencie because it seemed to struggle)
and leedroids ondemand forced dual core patch
my score was 7004
rant over , lol
Click to expand...
Click to collapse
People will hate me for this, and I waited a long time to post this on this thread, but I just have to do it.
Cool Story Bro.
tgruendler said:
People will hate me for this, and I waited a long time to post this on this thread, but I just have to do it.
Cool Story Bro.
Click to expand...
Click to collapse
:thumbup:
From the Beast : Galaxy Note
gav-collins1983 said:
first things first, I HAVE THE EXTENDED BATTERY. secondly, TO ME, benchmarks DO gauge the performance of MY phone, ......
right your still reading, hello,
benchmarking, I've had my phone since day one of the uk release, and have flashed many many many roms, and kernels, experimenting with different oc programs, governors, frequencies and voltages, and ui in comparison to smoothness is greatly improved the higher the antutu score, regardless of battery life.
that said.
the best concoction I cooked up, with the best ingredients from many experienced chefs (so far) is
leedroids rom v 5.3.0
leedroids kernel v4.1.0
system tuner pro 1.863 Max 192 min (added 0.25mv to 1.863 frequencie because it seemed to struggle)
and leedroids ondemand forced dual core patch
my score was 7004
rant over , lol
Click to expand...
Click to collapse
7000 score in Antutu @ 1.86 GHz? That seems low... I right around the same score at 1.65GHz
gav-collins1983 said:
first things first, I HAVE THE EXTENDED BATTERY. secondly, TO ME, benchmarks DO gauge the performance of MY phone, ......
right your still reading, hello,
benchmarking, I've had my phone since day one of the uk release, and have flashed many many many roms, and kernels, experimenting with different oc programs, governors, frequencies and voltages, and ui in comparison to smoothness is greatly improved the higher the antutu score, regardless of battery life.
that said.
the best concoction I cooked up, with the best ingredients from many experienced chefs (so far) is
leedroids rom v 5.3.0
leedroids kernel v4.1.0
system tuner pro 1.863 Max 192 min (added 0.25mv to 1.863 frequencie because it seemed to struggle)
and leedroids ondemand forced dual core patch
my score was 7004
rant over , lol
Click to expand...
Click to collapse
*Sips his Earl Grey* You like high numbers? You clearly did not like high numbers when you tipped me for my "bedroom" services!
gav-collins1983 said:
No, not, duhhhhh, overclocking also causes instability in some cases, more so if incorrect/not optimized voltages per frequency and governor in kernel, and smooth ness is affected
Click to expand...
Click to collapse
Anybody who knows anything about overclocking knows to make sure it's stable..
Seriously, if you think your high quadrants means your phone outperforms the leaked scores of a quad core Tegra 3 phone by almost double, then you're in denial.
Let me put this in words you can understand.
Faster clock speed = faster graphics and calculations.
Faster clock speed = higher benches.
Higher benches != better performance. They're just linked.
Sure, if you're pulling over 4000 in quadrant, your device is performing quite well. But that doesn't make your Evo 3D a super phone twice as good as the rest of ours.
There are so many factors involved that simply saying "my quads are high, and that indicates performance" is ignorant and naive. Once you can explain to me how your phone "performs" better than a quad core device, then maybe I'll spare your thoughts my time.
Sent from my HTC Evo 3D using XDA Premium App
I can't wait to see where this thread goes from here. Also, my phone is completely usable, fast, smooth, and has amazing battery life and I just scored an 1100 on Antutu. Benchmarks are worthless except to raise your eEsteem. See my thread about GeekBench from a few nights ago for proof.
Sent from my PG86100 using Tapatalk
Yes, as I stated in the other thread, quadrant is simply the equivalent of measuring mobile phone penis size and nothing more.
From the Beast : Galaxy Note
7000? Pics or get out.
Twitter: @knowledge561
Blog: knowledgexswag.tumblr.com
my score was OVER 9000!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
What! Over 9000! THERE'S NO WAY THAT CAN BE RIGHT!
First off, let me say that this is more a question out of curiosity so I can learn more about the android system then real concern.
That having been said, I have noticed that AOSP roms consistently score lower on benchmark software (Antutu to be exact) then Sense based roms, even though its immediately obvious that the AOSP roms are faster in the "real world". I have read on another phone's forum that it was OpenGL based for that phone, is it the same thing for our Rezounds, or are there other factors at work?
I do realize that benchmark scores are not the end all for performance representation, however the fact remains that there has to be something that is bringing down the AOSP score, hence why this is a question of curiosity .
That is an observation I have not made. The scores are pretty much the same for me. Just ran a 6336 on Antutu. Without overclocking, I run about the same on Sense.
I just had to rerun to make sure I wasn't making an a** of myself....
Both runs were using Neo's roms (adrenaline and rage)
on adrenaline with dsb's kernel and no OC I got a 7125
on rage running the bundled kernel i got a 6577
I've never seen over 7k on this phone without some heavy overclocking. What version of dsb's kernel are you using? A lot of them don't hold stable clocks. Try a benchmark with the stock kernel. It's a much more fair test since the AOSP is basically stock.
Sent from my ADR6425LVW using Tapatalk 2
I was running his 2.01 kernel with 192 min and 1.5 max using smartassv2 gov for the posted score.
Will have to get back to you on the stock kernel numbers as I am currently back on AOSP since I am playing around with themeing it, however for what it's worth this phone consistently (10-12 different benchmark runs) scored between 7000 and 7200 on the dsb kernel.
Yup I got over 8200 with my friends class 10 card in... With the standard one I get just under 7800 with OC and around 7200 without on DSBs kernel on 2 different roms...
Does anyone even use geekbench?
Yourfate said:
First off, let me say that this is more a question out of curiosity so I can learn more about the android system then real concern.
That having been said, I have noticed that AOSP roms consistently score lower on benchmark software (Antutu to be exact) then Sense based roms, even though its immediately obvious that the AOSP roms are faster in the "real world". I have read on another phone's forum that it was OpenGL based for that phone, is it the same thing for our Rezounds, or are there other factors at work?
I do realize that benchmark scores are not the end all for performance representation, however the fact remains that there has to be something that is bringing down the AOSP score, hence why this is a question of curiosity .
Click to expand...
Click to collapse
Well Rezound is built for sense so you can expect it to be, but once we get a working OC kernel you will see asop jump up in benchmarks
In Antutu, I get around 6500 with "stock" based Sense 3.6 roms. Then Sense 4 came out and the Antutu scores are 1000 higher, my top was 7700. I don't know why Sense 4 runs so much faster, especially since it was ported to our phone. AOSP I think scores were in between, 7000 range? But I'm not certain. Anyway Sense 4 is blisteringly fast, Sense 3.6 is garbage, and AOSP roms are the fastest going between apps/launcher. Once AOSP gets more solid, I will probably switch full time, but ViperREZ Sense 4 has sooooooo many features (and speed) it is hard to put down.
when i run a benchmark the result shows some kind of information about Mflop/s,Time,Norm Res and Precision, what are those?? and i ran benchmark on two different roms 1 rom shows 22 mflops in 1024Mhz and next rom shows 18Mflops also in 1024Mhz. so what is the best rom from these two.
CHoosing a ROM ...Benchmark style
This should satisfy your doubts ...
http://www.netlib.org/benchmark/linpackjava/
Higher the better ....but you need to do a set of operations in same environment (read as performance governor .)Run the benchmark at very least 50 times ..200-500 is preferred .Take an average of those iterations and choose the ROM with higher average ...
Long way of saying that benchmarks is not indicative of IRL performance ....Plus that benchmark is used to check floating point operations which is not much used IRL situations related to androids unless you use your phone for scientific computing ...