The LG Nexus 4 and the HTC DROID DNA are arguably the hottest two phones on the planet, right now. Our coverage of each has certainly been in overdrive, and rightfully so. With quad-core Snapdragon S4 Pro processors, tons of RAM, and big beautiful screens, these phones are fun to talk about. Beyond being fun to talk about, they are a pleasure to use throughout a day.
And speaking of using – performance on both is about as good as it gets. The 2GB of RAM in each coupled with the latest and greatest processor from Qualcomm leaves little doubt that these are the most powerful phones on the planet. You won’t find stuttering or slow loading times at all with either phone. But how do they stack up against each other? Well, that’s a tricky question because both seem to have few flaws when it comes to performance. (more…)
Qualcomm released a major update to their Vellamo benchmark Android app last night and it looks stunning. Aside from the UI changing to a 2012-esque styling, they updated the browser benchmarks and added tests for WebGL, network testing, and also for HTML video. If you haven’t benchmarked your phone in a while, now would be a good time to.
First, if you haven’t checked out our full review of the AT&T HTC One X, then you will want to do that. After doing that, let’s go ahead and start the conversation about benchmarks between the AT&T, Snapdragon S4 version and the Tegra 3, unlocked version of the phone.
With NVIDIA not having LTE modems for their quad-core processors just yet, carriers that want this phone with LTE capabilities are having to swap out the Tegra 3 in favor of the dual-core Snapdragon S4. Both processors are beasts in their own right, so we thought, “What better way to see if we can find a difference than through a handful of tests?” For those that hate benchmarks and think they mean nothing, we would agree with you to a point. We would have to disagree in that these at least give us something to compare against. We can flip through home screens all day long, open and close apps, look for stutters, etc., but in the end, you need to have numbers. Benchmarks give us numbers. (more…)
Let’s be honest here – benchmarks for the most part, are not something we care all that much about in 2012. Back in 2010 when we were overclocking everything that walked and phones still ran single-core processors, it was a big deal. Now, not so much. With the amount of power in phones today, a benchmark doesn’t tell the full story. With different cameras, screen sizes and techs, and build materials becoming increasingly more important, benchmarks are really just a piece of the puzzle and mostly for bragging rights now. And in the case of the HTC One X with the world’s first quad-core mobile processor inside (aka Tegra 3), bragging is exactly what we aim to do here.
We unfairly compared it to the Galaxy Nexus with its OMAP4460 dual-core chipset since it is the hottest Android device on the block, just to give you an idea as to how the T3 compares to last year’s dual-core chips. So what the G-Nex has to fight with is a “4-PLUS-1″ quad-core processor powering a 12-core GPU. “Oh joy!” (more…)
With the dual-core chipsets from Texas Instruments (OMAP), NVIDIA (Tegra) and Samsung (Exynos) all making their way into devices and our hands in the last couple of months, we wanted to see how each compared to each other in a series of Android benchmarks. We pulled the results for the Galaxy S II and DROIDX2 from this post that we ran a few weeks back and have now included results from the DROID3 to round out the comparison. The DROIDX2 is running NVIDIA’s Tegra 2 clocked at 1GHz, the Galaxy S II has their Exynos at 1.2GHz, and the DROID3 is running an OMAP clocked at 1GHz.
Here are the results… (more…)
Update: Just like we assumed, that benchmark was a first run. We’ve received another batch that were done after the device warmed up a bit and the results are much more favorable.
I’m not going to start making excuses for the DROID3 yet, but I’m certainly hoping that this was a first run after its first boot up because this is embarrassing. In the days of phones with dual-core processors (this phone being one), we’ve got to at least break 2000 on a Quadrant benchmark. After all, single core devices that have been overclocked can certainly eclipse the 1700 mark. To see what real benchmarks look like, you’ll want to check out this post we ran for the Galaxy S II and the DROIDX2.
To be fair though, we know that most benchmarks mean nothing and we also haven’t handled the device yet to run it through the DL set of tests. So I’ll try to hold back too many opinions, but what I will do though, is ask that all of our readers who received D3s early, post up their top benchmarks. This is not exactly what we were hoping to see from an OMAP4 – especially with the DROID Bionic likely running one.
Linpack score after the break. (more…)
As many of you know by now, we picked up a Samsung Galaxy S II to try to understand the massive amounts of hype that this device has seen even though it has yet to land in the U.S. We walked through a quick hands-on yesterday, but wanted to come back today and fulfill some reader requests which called for a string of benchmarks to be done. And since we happen to have a DROIDX2 handy, we thought it would be a great dual-core competitor to match it up against.
Here are the results we came up with after running SmartBench, CF-Bench, Linpack, Quadrant Standard, Neocore, and Nenmark1 a number of times on both devices. (more…)
I know, I know, benchmarks (especially) Quadrant are inconsistent, can be faked or bloated and aren’t a great tool to compare phones, right? I’ve heard the arguments, but at least these give us something. So we took both the DROIDX and DROID2, slapped the leaked Gingerbread on both and then compared them to the HTC Thunderbolt running Android 2.2 with Sense. The results are about what we figured since the Thunderbolt has slightly different and newer hardware, but Android 2.3 really seems to have given the DX and D2 a nice boost. (more…)