T-Mobile Galaxy S II benchmarks redux

We recently saw some benchmark numbers for the T-mobile Galaxy S II, and like everything else ever put on the Internet many cried foul.  I hate benchmarks.  They tell me nothing about how a phone acts and feels in real world use; you need to actually use it to determine that.  But since there's a bit of controversy, allow me to interject a few new pictures.

Nothing shut off, still getting mail and everything like I should.  Now stop worrying.

Jerry Hildenbrand
Senior Editor — Google Ecosystem

Jerry is an amateur woodworker and struggling shade tree mechanic. There's nothing he can't take apart, but many things he can't reassemble. You'll find him writing and speaking his loud opinion on Android Central and occasionally on Twitter.

  • Neat.
  • I notice overscroll effect on this version vs the others. Anything else different you can point out? Is the AP mobile widget still there?
  • Overscroll -- yep, it's a slow blue flash. Yes AP mobile widget is still there. 
  • I see so quadrant was right, anyhow me neither i prefer to see a live test loading heavy graphic websites and try pinch to zoom and scrolling, but thanks for the info
  • Amazing. Why does this SoC perform so shitty on HTC phones then?
  • i guess is htc sense fault, sense usually slows down the system because it requires more power to run.
  • It actually makes sense too. According to Anand from Anandtech.com, a lot of Spandragon-based SoC's are bottlenecked by shitty software (although that wasn't his exact word used to describe it, lol). http://www.anandtech.com/show/4940/qualcomm-new-snapdragon-s4-msm8960-kr... So I guess Samsung's software team > HTC's software team.
  • Considering Cyanogen is on Samsung's software team I would say so!
  • Those numbers are on par with the exynos chip at 1.2 ghz. If you want to compare the same clock speeds, the exynos @ 1.5 ghz on the epic touch 4g does 4200 on quadrant and 122 on linpack. So basically 20-25 percent faster.
  • And the Nexus S can do 6ooo on quadrant clocked at 1.5. I hate benchmarks.
  • But Jerry, in order to get those numbers out of a nexus S you need to run some cheat in command prompt ( as you demonstrated in your video here ). Those numbers are real world numbers with nothing but a over clock kernel running a higher clock speed. They were also running different benchmarks as well to show that its not just one hack for that particular benchmark.
  • no.  you can hit 6K without cheating now that openGL on the NS has been fixed. But so what?  It doesn't make the phone faster, just higher numbers.
  • Yep Trinity kernel 6000+ on Quadrant. No hacks. It just takes advantage of the Nexus S native ext4 file system. The kernel also increases the bus speed of the gpu.
  • This is also running 2.3.5
  • It's also a lower resolution.
  • But better contrast and color via SAMOLED PLUS.
  • What is? The tmo variant is running at a lower resolution than the epic touch 4g (stupid name) Jack
  • My bionic went almost that high on the Neocore, but not on the others. It completely rocked downloading the benchmarks though.
  • It performs pretty well. The A9 (what the Exynos is based on) will always peform better than the Scorpion at the same clock speed, so that's probably why T-Mobile and Samsung had this version clocked at 1.5 GHz.