For just over a week, I’ve been using two phones interchangeably. The first is the Lava Xolo X900 with Medfield inside, the second is the flagship of HTC’s new One series, the HTC One X on AT&T. It’s a device with lofty goals, as it’s the flagship of HTC’s new branding and strategic positioning behind a single line of devices, industrial design, and focus. The strategy mirrors that of Samsung’s with their Galaxy series, and if successful will rekindle the excitement behind HTC’s brand.
The One X on AT&T is really a One XL (L for LTE), however in the USA the device carries full One X branding. We’ve got the International One X and One S variants which will be reviewed in short order, but for today we’re talking specifically about the One X on AT&T. Read on for the full review.
HTC and Sprint teamed up today to announce the latest in the EVO line: the EVO 4G LTE. So, not the most novel name, but it gets to the point. The 4.7" device is carved out of an aluminum space frame, anodized to an all black finish with red accents ...
Yesterday we presented the first results of Qualcomm's Krait based MSM8960 SoC. While we still await the first Krait based phones (widely expected to begin shipping sometime in Q2), courtesy of Qualcomm's MSM8960 Mobile Development Platform we were able to get a good idea of the upper bound for Krait and MSM8960 performance. I mention it's the upper bound because, at least in the past, MDP performance hasn't corresponded directly to shipping device performance. There was a pretty big delta between MSM8660 MDP performance and phones that used the MSM8660. Qualcomm tells us that this time around things are going to be different. Qualcomm is expecting a much narrower (nonexistent?) gap between the MSM8960 development platform and phones that use MSM8960 silicon. One major difference between the MSM8960 MDP and our earlier MSM8660 MDP was the state of the CPU governor. In the earlier MDP the governer was set to max performance, always delivering the CPU's maximum clock frequency. With the MSM8960 platform the governor was set to ondemand, allowing for variable CPU speeds depending on what the OS requests of the device. The ondemand setting is in-line with what we can expect device manufacturers to use when they ship phones. All of this goes to say that while we have a good handle of what Krait and the MSM8960 are capable of, there are still a lot of unknowns.
While it's true that shipping performance remains to be seen, some of the deltas we saw between MSM8960 and the current competition were so great that even a much slower implementation in a shipping phone would still be significantly faster than anything else out today.
We left our MSM8960 investigation with two major unknowns. The first was power consumption. We still haven't been able to get Qualcomm's Trepn tool running on the MSM8660 MDP, which has always been a bit finicky. To get a true feel for MSM8960 battery life we will have to wait for shipping devices. The other major unknown was really how MSM8960 stacks up against NVIDIA's Tegra 3.
Tegra 3 was everything Tegra 2 should have been. We got higher clocks, NEON support and a much faster GPU. The only thing missing from Tegra 3 was a dual channel memory interface. We were happy with Tegra 3 on ASUS' Eee Pad Transformer Prime, but in less than a week we'll get to meet some of the first smartphones based on T3 silicon.
Armed with the Eee Pad Transformer Prime (updated to Ice Cream Sandwich) we're able to get a rough idea of how these two heavyweights will compare. The same caveats that applied to the MDP apply to our Tegra 3 platform as well. Since we are using a tablet we're obviously dealing with a higher TDP than what you'll find in a phone. The comparison today is largely academic and naturally shipping devices may be better or worse that these two representatives. With the disclaimers out of the way, let's get to the comparison.
If you've been following our SoC and smartphone related coverage over the past couple of years, you'll probably remember how Qualcomm let us take home an MDP8660 from MWC 2011 and thoroughly benchmark it. Qualcomm has done essentially the same thing this year, this time sending their latest and greatest MSM8960 SoC inside the aptly named MSM8960 Mobile Development Platform (MDP) just before MWC 2012.
The timing is impeccable as we're fully expecting to start seeing MSM8960 based phones next week at MWC, and we've been telling you to hold off on any smartphone purchases until the 8960's arrival. Today we're finally able to give you an indication of just how fast Qualcomm's next-generation Snapdragon S4 will be. Read on!
Let's recap the current smartphone/tablet SoC landscape. Everything shipping today is built on a 4x-nm process, built either at Global Foundries, Samsung, TSMC or UMC. Next year we'll see a move to 28nm (bringing better performance and power characteristics) but between now and the end of 2012 there will be a myriad of designs available on the market.
The table below encapsulates much of what you can expect over the next 12+ months:
| 2011/2012 SoC Comparison | |||||||
| SoC | Process Node | CPU | GPU | Memory Bus | Release | ||
| Apple A5 | 45nm | 2 x ARM Cortex A9 w/ MPE @ 1GHz | PowerVR SGX 543MP2 | 2 x 32-bit LPDDR2 | Now | ||
| NVIDIA Tegra 2 | 40nm | 2 x ARM Cortex A9 @ 1GHz | GeForce | 1 x 32-bit LPDDR2 | Now | ||
| NVIDIA Tegra 3/Kal-El | 40nm | 4 x ARM Cortex A9 w/ MPE @ ~1.3GHz | GeForce++ | 1 x 32-bit LPDDR2 | Q4 2011 | ||
| Samsung Exynos 4210 | 45nm | 2 x ARM Cortex A9 w/ MPE @ 1.2GHz | ARM Mali-400 MP4 | 2 x 32-bit LPDDR2 | Now | ||
| Samsung Exynos 4212 | 32nm | 2 x ARM Cortex A9 w/ MPE @ 1.5GHz | ARM Mali-400 MP4 | 2 x 32-bit LPDDR2 | 2012 | ||
| ST-Ericsson NovaThor LP9600 (Nova A9600) | 28nm | 2 x ARM Cortex-A15 @ 2.5GHz | IMG PowerVR Series 6 (Rogue) | Dual Memory | 2013 | ||
| ST-Ericsson Novathor L9540 (Nova A9540) | 32nm | 2 x ARM Cortex A9 @ 1.85GHz | IMG PowerVR Series 5 | 2 x 32-bit LPDDR2 | 2H 2012 | ||
| ST-Ericsson NovaThor U9500 (Nova A9500) | 45nm | 2 x ARM Cortex A9 @ 1.2GHz | ARM Mali-400 MP1 | 1 x 32-bit LPDDR2 | Now | ||
| ST-Ericsson NovaThor U8500 | 45nm | 2 x ARM Cortex A9 @ 1.0GHz | ARM Mali-400 MP1 | 1 x 32-bit LPDDR2 | Now | ||
| TI OMAP 4430 | 45nm | 2 x ARM Cortex A9 w/ MPE @ 1.2GHz | PowerVR SGX 540 | 2 x 32-bit LPDDR2 | Now | ||
| TI OMAP 4460 | 45nm | 2 x ARM Cortex A9 w/ MPE @ 1.5GHz | PowerVR SGX 540 | 2 x 32-bit LPDDR2 | Q4 11 - 1H 12 | ||
| TI OMAP 4470 | 45nm | 2 x ARM Cortex A9 w/ MPE @ 1.8GHz | PowerVR SGX 544 | 2 x 32-bit LPDDR2 | 1H 2012 | ||
| TI OMAP 5 | 28nm | 2 x ARM Cortex A15 @ 2GHz | PowerVR SGX 544MPx | 2 x 32-bit LPDDR2 | 2H 2012 | ||
| Qualcomm MSM8x60 | 45nm | 2 x Scorpion @ 1.5GHz | Adreno 220 | 1 x 32-bit LPDDR2* | Now | ||
| Qualcomm MSM8960 | 28nm | 2 x Krait @ 1.5GHz | Adreno 225 | 2 x 32-bit LPDDR2 | 1H 2012 | ||
The key is this: other than TI's OMAP 5 in the second half of 2012 and Qualcomm's Krait, no one else has announced plans to release a new microarchitecture in the near term. Furthermore, if we only look at the first half of next year, Qualcomm is the only company that's focused on significantly improving per-core performance through a new architecture. Everyone else is either scaling up in core count (NVIDIA) or clock speeds. As we've seen in the PC industry however, generational performance gaps are hard to overcome - even with more cores or frequency.
Read on for our analysis of Qualcomm's Krait architecture and the MSM8960.
There's a whole lot of misinformation on the web right now about reasons why HP had troubles with the TouchPad and eventually had to abandon the entire webOS hardware division. We'd moved on internally after yesterday's news but a bunch of stuff that popped up online today prompted a quick discussion about the realities of webOS hardware.
Read on for our analysis.
When T-Mobile launched the G2, I was super psyched. It was an HTC-designed slider, ran the stock Android UI, and happened to be one of the first phones running Qualcomm’s 2nd-generation Snapdragon (S2) chips. I was so psyched that I ended up buying one, three days before launch (thank you Radio Shack!) I must say, I loved that phone. The hinge mechanism was an initial concern for me, but the rest of that phone was absolutely brilliant. I still regret selling it to buy an HD7, but I had some major durability issues with the hinge. It started loosening up majorly after the four month mark, and it was out of my life by month five. If HTC had seen fit to equip it with a normal spring-loaded slider, I would almost definitely still have it.
T-Mobile EOL’d the G2 last month, and I was sad to see it go. But it set the stage for the MyTouch 4G Slide, which released last week and on paper looks like the ultimate slider phone. There’s one dual-core Snapdragon S3 processor, one real slider with one brilliant HTC keyboard, and one very highly touted 8.0MP camera. It joins the HTC Sensation and the T-Mobile G2x atop the T-Mobile smartphone list. How does it stack up versus the rest of the elite smartphone class? Read on to find out.
All microprocessor companies struggle with the same basic marketing problem: how do you explain to the average consumer why one part is faster than another without saying cache, GHz or cores. Intel and AMD have been using model numbers to abstract hardware differences for years. Today Qualcomm is announcing its ...
Yesterday evening I met up with HTC, who let me take a quick look at a number of upcoming unreleased phones, including the HTC Sensation 4G and HTC EVO 3D. Naturally, the first thing I did was sit down and run some benchmarks during our limited time with the phones, and get an overall feel for the two. These two phones are both based on Qualcomm's MSM8x60 SoC which consists of two 1.2 GHz scorpion cores, and Adreno 220 graphics. We also spent a little bit of time with the HTC ChaCha and HTC Salsa.
Read on for some benchmark goodness and our thoughts about these four devices.
Today is the second and last day of Qualcomm's Uplinq conference in San Diego California, but we've still got a bunch in store. This morning, we sat down at the keynote and listened to HTC CEO Peter Chou talk about where HTC has been, its plans for the future, and make an announcement about HTC Sense development. After that was Nokia CEO Stephen Elop, who outlined five principles which will help Nokia foster its own new mobile ecosystem in a joint partnership with Microsoft.
Read on for more from these two keynotes.
Today marks the first day of our coverage of Qualcomm's annual Uplinq conference in San Diego, California. It's our first time coming to Uplinq, a conference whose roots trace back to the haydays of the Brew MP platform, when featurephones were king. Since then it's become a mobile conference hosted by Qualcomm for developers, operators, and software developers alike.
Read on for our coverage of today's keynote by Dr. Paul Jacobs, CEO of Qualcomm.