We’ve already seen 1.5 GHz dual core Krait (MSM8960/MSM8260A/MSM8660A) performance before and talked about it in the HTC One X (AT&T) review, and the USA SGS3 review. For the most part, what we see with the HTC One S variants is largely the same as what we saw with a number of other dual core Krait based devices. Recall that MSM8960, MSM8660A, and MSM8260A differ only in baseband and thus what air interfaces are supported. The only big difference between the devices we've seen based on that SoC so far is RAM, and again the HTC One S includes 1 GB of LPDDR2. 

If you’re looking for a detailed comparison to the International SGS3 with Exynos 4412, I've finally had a chance to play with one and we will be doing a more direct comparison with Tegra 3, Exynos 4412, and dual core Krait shortly. I've tossed in the numbers from the International SGS3 for comparison already. 

For now, however, let's talk about the HTC One S. 

JavaScript Performance

Measuring JavaScript performance is just one component of overall web browsing performance, but it’s the most mature in terms of something we can benchmark. Sunspider 0.9.1 is quite possibly the most well known of these JavaScript tests, and a regular staple of our testing suite:

SunSpider Javascript Benchmark 0.9.1 - Stock Browser

There's an obvious grouping of 1.5 GHz dual core Krait devices around 1500 ms. What spread there is between devices is primarily a function of whatever tweaks OEMs have made to the stock browser's V8 JavaScript engine. 

Next up is Browsermark, which is another primarily JavaScript benchmark, with a few other measures. I'm told there are future versions planned which target HTML5 canvas performance. 


Again there's an obvious clump of dual core Krait devices. The International SGS3 pulls way ahead here for some reason. 

Next up is Vellamo, which is a Qualcomm benchmark developed originally for OEMs to use and optimize their browser performance with, and later released for general use. It’s a regular member of our test suite and includes both JavaScript tests and scrolling tests that stress the display composition and hardware acceleration in an Android WebView.

Vellamo Overall Score

Unsurprisingly the Qualcomm based devices do well in their own benchmark. All of the devices that score above 2000 feel very smooth browsing around in the stock browser and WebView. For the most part, choppy translation and zoom is a thing of the past on Android 4.x. 

Low Level FP Performance

Linpack isn’t a great indication of overall smartphone performance, but it is a good test of the floating point capabilities of the CPUs in these SoCs. ARM has steadily been improving FP performance for the past few generations but we’re going to see a big jump to Krait/A15. As most client smartphone workloads are integer based and those that are FP heavy end up relying on the GPU, an advantage here doesn’t tell us much today (particularly because Linpack isn’t running native code but rather atop Dalvik) other than how speedy the FPUs are. There’s a new port of Linpack which runs using native code which we’ll be trying out in the big performance comparison piece.

Linpack - Single-threaded

Linpack - Multi-threaded

I'm becoming more and more dissatisfied with this GreeneComputing build of Linpack, and given the availability of some alternatives which are implemented natively as opposed to atop Dalvik, will probably move away from it very soon. 


BaseMark OS

Rightware’s BaseMark OS is a general purpose benchmark designed to better simulate overall Android performance. It includes a heavily threaded benchmark, file IO tests, and compression/decompression tasks that all contribute to its overall score. This benchmark is pretty much the closest thing we have to a system benchmark for Android at this point, and is very close to achieving the same level of adoption that a few other big industry benchmarks have. 


BaseMark OS Performance


GPU Performance - GLBenchmark 2.1

As we wait for actual 3D gaming benchmarks to make their way into Android (and hopefully cross platform) games, we must rely on synthetic tests designed to simulate 3D game performance as best as possible. We start with GLBenchmark, one of the better Android GPU tests on the market today. There are two benchmarks, Egypt and Pro, and each is run in two modes: native screen resolution and offscreen (vsync disabled) at 720p. The latter is more useful for apples to apples comparisons as everything is rendering the same number of pixels, whereas performance in the onscreen tests is determined by the screen resolution of the device along with the performance of its GPU.


GLBenchmark 2.1 - Egypt

GLBenchmark 2.1 - Egypt - Offscreen (720p)

GLBenchmark 2.1 - Pro

GLBenchmark 2.1 - Pro - Offscreen (720p)


As a reminder, only the offscreen tests take place with vsync turned off, which is why you see devices with 720p displays posting different results on versus off screen where vsync is off. Part of the deal in getting Krait to market as quickly as possible required that Qualcomm pair the CPU with an older GPU, in this case the Adreno 225 instead of the newer Adreno 3xx offerings due out later this year in SoCs like MSM8960 Pro or the quad core Krait APQ8064. As a result, you can see the SGS2 with Exynos 4210 and the SGX543MP2 in the iPhone 4S pull ahead in some tests. Obviously the on-screen test isn’t a totally fair comparison because of the inherent difference in resolution - the One S is qHD. 


Basemark ES 2.0 V1

Rightware’s Basemark ES 2.0 V1 is an aging GPU test that tends to favor Qualcomm’s Adreno GPUs above almost all others:

RightWare Basemark ES 2.0 V1 - Taiji

RightWare Basemark ES 2.0 V1 - Hoverjet

These two tests we run at WVGA on the device. Basemark ES 2.0 is definitely starting to show its age, as Hoverjet is at vsync essentially the whole time, and Taiji is nearly there as well. Qualcomm appears to be using ES 2.0 as an optimization target, so I wouldn’t put too much faith in the ES 2.0 results.

Battery Life and Charging Software - ICS and HTC Sense 4


View All Comments

  • ltcommanderdata - Tuesday, July 17, 2012 - link

    To go with the smallest screen size for a modern smartphone, the iPhone 4S also has the smallest battery as shown on the first chart on page 2. It'd be interesting o find out how display power consumption scales with screen size to see if they are scaling battery size fast enough to fully compensate, but big phones with big screens do tend to have big batteries so big screens shouldn't automatically mean bad battery life. Reply
  • Penti - Tuesday, July 17, 2012 - link

    4S doesn't have HSPA+ baseband only 14.0 Cat 10 HSDPA. I.e. 14Mbit "4G-branding". In short small batteries, large screens, fast processors and gpus and power hungry baseband is what drains these devices. You need a significant larger battery to have a better battery life here. For most devices that isn't a priority. For example the iPad 3 gen has a larger battery then MBAir 11. Reply
  • amdwilliam1985 - Tuesday, July 17, 2012 - link

    Please explain the 4G part to a friend of mine.
    She claims her 4G iPhone 4s with iOS 5.1.1 on AT&T network can't go through a day with moderate usage.
  • Penti - Tuesday, July 17, 2012 - link

    What, it's just a 3G WCDMA baseband, no other radio or tech it shouldn't draw more power just because the icon says 4G in this 3.75G device. No smartphone survives more then a day with moderate usage, calls and what not. An 4s is spec'd at 8 hours talk time and 6 hours of internet use over 3G respectively. Play a game and the device is pretty much dead half day. Using apps that pull data over the wireless cellular network, talk for a few hours and play a game for 15 minutes and it should be pretty drained. If there is nothing wrong with the device then it is the usage that has to change to accommodate more battery life. If you need to talk for hours a day and be connected to chat, surf the web, use apps that leverage the internet and all that over the network you would need some solution to charge the phone over the day not matter what device you run.

    Why some people whine about early LTE phones is because they had bad dual baseband chips and about half the talk time. Pretty bad battery life surfing on LTE etc.
  • Spoelie - Tuesday, July 17, 2012 - link

    I'm wondering if the battery tests have ever been redone following iOS updates. In my experience, the battery life gets progressively worse with every new update. In this case, doing the tests once on release day and reusing the numbers for months on end may not be the best approach. Reply
  • Anand Lal Shimpi - Tuesday, July 17, 2012 - link

    I'll take the blame for this one. Notice the revamp of our tablet and OS X battery life tests? The smartphone web browsing test is in need of an update there as well. iOS has gotten a little too "good" at what we're doing there, at least in the web browsing test. The call and tethering tests are still great cross-platform indications of battery life. Reply
  • rd_nest - Tuesday, July 17, 2012 - link

    I think we should also look at multimedia playback times. Run high profile video files to check battery rundown time. It's an important parameter as far mobile usage is concerned.

    The SGS3 (International) is getting pretty good numbers compared to US SGS3 models.
  • yvizel - Tuesday, July 17, 2012 - link

    Saying 3.5'' vs. 4.3'' is not an accurate argument.

    If you come to think of it, the iphone is a smaller device, therefore packs a smaller battery (as you can see in the Battery Capacity chart).
    Also, I would rather have a "slower" processor and more battery juice than have an octa-core @ 4GHz on a smartphone with 1 hour of usage!

    Not all of us use smartphone for gaming or whatever. I guess that the more common usage is web, email, GPS and other basic stuff. So again, no need for zillion cores on a smartphone.

    Oh, and great review! looks like a great device!
  • Connoisseur - Tuesday, July 17, 2012 - link

    My point is that it's extremely difficult to compare phones of different size, resolution, screen type, OS and capacity. Even if you remove the OS out of the mix (so you can compare OS "efficiency"), the only comparison you can really make between two different devices is hours/battery capacity efficiency.

    At least when comparing laptops, you have some basis for comparison (comparable hardware or form factor for example).
  • amdwilliam1985 - Tuesday, July 17, 2012 - link

    We can do the following 2 tests.

    1) Hack and put iOS on an Android device and run the same test against iPhone 4s.
    2) Hack both device and put a custom OS on both and run the test.

    This way we can see if it's software or hardware that's affecting the battery life.

Log in

Don't have an account? Sign up now