Quote:
Originally Posted by gTen
First of all..I don't lie to win debates, you can ask anyone..hence whenever I found information one way or the other I put up the information. It is irrelevant what SDK has set to a resolution! I can have a blank white screen and a million processes running in the background..unless the benchmark/app makes use of the display elements its irrelevant what resolution it runs in..
|
Until you get past this totally INCORRECT position, I can't continue this discussion with you. The FACT here, is whatever is running in the background affects the processing power of the device. So if you are testing the processing power of a device, then the stuff running in the background ABSOLUTELY influences that test. If one device is emulating a resolution, then whatever is making it emulate that resolution is absolutely affecting the processing power. So if only one device is doing that extra processing, then the test is flawed. It's like comparing internet speeds while one device is streaming a video and the other isn't. Even though the speed test isn't testing the video stream, that video stream still affects the speed test.
Quote:
Originally Posted by gTen
If I have a monitor thats 1920x1200 resolution and a monitor at 1600x1080 resolution..if I lower the 1920x1200 monitor to 1600x1080 and benchmark a game..it will benchmark THE SAME!
|
This is a false analagy. The test is NOT lowering the resolution of the monitor. It emulating a lower resolution.
Quote:
Originally Posted by gTen
So your saying because student A finished a test faster and got a score of 30 he is smarter then a student who finished a bit later and got a score of 60? its a speed/quality thing...unless the sensation finished the test 2x faster, it has no reason to quantify having 2x less FPS...
|
No, I'm not saying that at all. That is a horrible analogy. I am saying that if this test is supposedly rating the performance of the 2 devices, then the device that finished first, even though it was running at a higher resolution, is obviously faster.
Quote:
Originally Posted by gTen
Yes, lower FPS is expected at higher resolution yes..but that just means the GPU is not powerful enough to support a phone with such resolution..simple as that...
|
No, that is not what it means. It means the Galaxy S2 is not powerful enough to run at the higher resolution. Simple as that.
Quote:
Originally Posted by gTen
none of the benchmarks showed higher scores for sensation except linpack which showed a higher score by like 1%..if not less...which falls within margin of error of manufacturing quality..and this is on a benchmark that tests only 1 thing being floating point math...
|
There were 2 benchmark tests performed. First, quadrant- the Sensation finished significantly faster, yet somehow scored lower. Then, linpack, the Sensation actually scored higher. Then smartbench- the Sensation was obviously running at an emulated resolution and scored lower.
Quote:
Originally Posted by gTen
Smartbench and GL Benchmark are better then the others because they are the only ones actually still being developed and improved upon. In smartbench case it is developed by a community effort...hence why it adapted to multiple cores and higher resolutions while the others didn't..
|
So? That doesn't mean anything. Maybe someday it will run at native resolution if it is still being improved. But right now, today, it does not.
Quote:
Originally Posted by gTen
Actually samsung issued a statement on that, its mostly because they were not able to achieve qHD on AMOLED technology yet..but you can make an SGS2 render at qHD if you want using kernel hacks..
|
Good, so show me these tests with the devices running at the same resolution before you start talking about fps.
Quote:
Originally Posted by gTen
Well let me ask you this..whats better 720p at 24fps or 1080p at 12fps? (I am not using 480i to 1080p because thats not the difference here)
|
Nobody runs either of those resolutions at those fps you listed. However, 480i IS 30 fps standard, and 1080p IS 24 fps standard. So that is a perfect example of higher resolution still being better than lower resolution even though the fps is lower. Like you kept saying, this is not rocket science.
Quote:
Originally Posted by gTen
Why do you think people were complaining on EVO when things were locked to 30fps? it makes a difference for many...
|
Nobody was saying the Evo was worse than any lower resolution device. They were comparing the Evo to other wvga devices. Yes, fps makes a difference, but most people understand that a higher resolution will mean a lower fps.
Quote:
Originally Posted by gTen
Just because I don't say things you want to hear does not mean I am lying...
|
No, not at all. But when you say things that are blatantly false, it means either you don't know what you are talking about or you are lying.
Quote:
Originally Posted by gTen
Every benchmark has flaws yes, but there are good benchmarks and bad benchmarks..good benchmark= one that adapts, bad benchmark= one that doesnt adapt..
|
Just because it adapts doesn't mean it is the end all be all. I don't care if a particular benchmark is supported by the community. That doesn't mean the test is 100% accurate. If the device is emulating a resolution while it runs the test, then the results are flawed.
Quote:
Originally Posted by gTen
Quadrant for example you can still cheat on using I/O..and its been 1-2 years since that has been known and they still haven't fixed it!!!! hence why I have been asking you to ignore Quadrant since the beginning of the convo!
|
And I have been saying I ignore ALL of those benchmarks, not just quadrant. But if you are going to say the Galaxy S 2 is clearly the better hardware, and cite benchmarks as your clear and undeniable proof, then I will point out that some other benchmarks, that I consider just as flawed as the ones you are using, indicate the Sensation is the faster device.
Quote:
Originally Posted by gTen
Smartbench updates on a daily bases hence is a more trust worthy benchmark...
|
I don't care how often it updates. If it emulates a resolution one device, and runs at native resolution on the other device, then the test is flawed. Period.