Motorola Droid X: Thoroughly Reviewed
by Brian Klug on July 20, 2010 4:27 PM EST- Posted in
- Smartphones
- Motorola Droid X
- OMAP
- Mobile
Years ago, before we hit the power wall, CPU innovation happened at a slow but steady pace. Every five years or so we’d get a new microprocessor architecture and every couple of years we’d get smaller transistors.
The smaller transistors made chips run cooler and at higher clock speeds. The shrink in die area also paved the way for new features, but between major architectural shifts those features normally came in the form of larger caches.
Texas Instruments’ move from the OMAP 3430, used in phones like the Palm Pre, to the OMAP 3630 used in the Droid X is reminiscent of this sort of steady progress I mentioned above.
The OMAP 3430 was built on a 65nm process (like Qualcomm's Snapdragon), while the 3630 is a 45nm shrink (like Apple's A4). Architecturally the two SoCs are very similar. They both use a standard ARM Cortex A8 CPU paired with an Imagination Technologies PowerVR SGX 530 GPU. The two SoCs fit in the same size package (12mm x 12mm BGA) and are ball compatible. If a customer wanted to, it could simply drop in a 3630 into an existing 3430 design with minimal engineering efforts.
Note that the most direct competitor to the 3630 is Qualcomm’s Snapdragon. While TI uses a standard Cortex A8 core from ARM, Qualcomm designed its own low power ARMv7 based core that is similar, but not identical to the Cortex A8. Both are dual-issue, in-order architectures - they’re like the original Pentium, but in your phone. Qualcomm also integrated the cellular modem into the Snapdragon SoC while TI’s OMAP 3 is a strict application processor - the modem is housed in a separate chip.
On the CPU side TI doubled the L1 cache of the 3430 to 64KB (32KB instruction, 32KB data). The L2 cache remains unchanged at 256KB. We won’t get a larger L2 until the OMAP 4, which will ship with a 1MB L2 shared among its two cores. There are the usual tweaks and bug fixes which may improve performance per clock a little bit over the 3430, but overall the 3630 just gets a larger L1 as a result of the die shrink - oh and a much higher clock speed.
The Cortex A8 now runs at up to 1GHz. The OMAP 3430 topped out at 800MHz in shipping configurations but most vendors ran it at sub-600MHz speeds to save power. The 3630 in the Droid X runs at a full 1GHz. It's worth pointing out that Qualcomm was able to hit 1GHz on a similar architecture at 65nm by designing its core from the ground up. There's clearly value in these custom designs from a performance and time to market standpoint. These advantages will only become more critical as the SoC performance wars heat up.
Power Consumption
The OMAP 3 as well as Qualcomm’s Snapdragon SoC support dynamic voltage and frequency scaling. Based on application demand and cues from the OS the CPU clock speed and voltage can vary. The Cortex A8 in the OMAP 3630 will drop down to the low 300MHz range when idle at the Android home screen and ramp all the way up to 1GHz when needed.
TI's OMAP 3630 running at full tilt
...and automatically underclocked to 446MHz under lighter load
This is nothing unique to the OMAP 3630, but it shows that frequency and voltage scaling is alive and well in Android.
TI supports full power and clock gating. All major IP blocks are placed on their own power islands, so based on input from the OS the CPU, GPU, video decoder, etc... can ramp down depending on the application needs at the time. The power and clock gating is no more granular in the 3630 than it was in the 3430. What has changed however are operating voltages.
While the 3430 needed 1.35V to hit 720MHz, the 3630 can reach 1GHz at around 1.26V. That still sounds a bit high to me but at the same clock speed, thanks to voltage scaling, you can drop power by around 30% compared to the 3430.
Coupled with the dynamic voltage/frequency scaling of all OMAP 3 parts this means that overall power efficiency should be better on the 3630 vs. the 3430. The added CPU performance in the form of larger L1 caches and a higher clock speed should make tasks complete quicker and allow the 3630 to get to a lower voltage state than the 3430 was ever able to reach.
Samsung has already shown off 1.2GHz+ versions of its Cortex A8 based SoC at 45nm, so I would expect to see higher clocked versions of the 45nm OMAP 3 family to follow at some point in time.
Facebook
Twitter
RSS
89 Comments
View All Comments
homebredcorgi - Tuesday, July 20, 2010 - link
Who do we have to blame for the “Droid” moniker? Verizon or Motorola?I have a Nexus One and continually get asked, “Is that a Droid?” or “Does that run Droid?” to which I usually reply yes and let sleeping dogs lie…but seriously, why name it so similar to the operating system? And then why make “Droid” a series of phones if your first phone is just known simply as “Droid”?! At least call it the "Droid One" or something to differentiate from the series of phones....
So now we have the Droid, Droid Eris, Droid X, and will soon have the Droid 2 which are all phones in the Droid series, all running on various builds of Android. Yeesh. Could they have made that any more confusing?
All in all, the Droid X looks very nice. I personally think the original Droid had all the flair of a TI-82 calculator (ugly as sin in a blocky retro way), but the Droid X seems to have modernized its looks. Still not sure if I would want a phone that large though….
metafor - Tuesday, July 20, 2010 - link
Verizon owns the rights to the "Droid" trademark from Star Wars. So they decided to capitalize on that and name their whole line of Android phones "Droids".I think it's kinda cheezy but hey, it's selling and is something that people can focus on. With the army of phones coming out every week, it's difficult for the average person to keep up. It helps if they can just go to a store and ask for a Droid.
strikeback03 - Tuesday, July 27, 2010 - link
Actually they have only been using Droid on the high-end phones, the Devour and Ally were not Droids.There is also rumor of a special edition Droid 2 coming with R2-D2 on the battery cover...
lewchenko74 - Tuesday, July 20, 2010 - link
The best, most comprehensive review of the Droid X Ive read so far. Thank you.Just got to wait until it arrives in the UK unlocked now, but personally I think Im going to get the Droid 2 instead with the keyboard.
I am amazed at the pace the smartphone market is moving at. Im 1yr into a 2yr contract with a HTC Hero. It feels like an antique! These 2yr contracts really are a ball and chain.
It also seems like HTC is starting to lag behind Samsung and Moto now in terms of processor and features. Sense also seems a little 'old' compared to other UI layers (or maybe thats just me).
Disappointed that it only runs Android 2.1 when 2.2 is now out though.... That would be like Apple releasing iPhone4 running OS3.2 whilst saying OS4 is out there too but not quite available yet! (I guess Apple actually did that though with the iPad ;-) )
mvmorr01 - Tuesday, July 20, 2010 - link
What app are you using for those CPU utilization graphs? I did a quick search and couldn't find it in the market.Brian Klug - Tuesday, July 20, 2010 - link
It's an application called "SystemPanel" which I found a while back. If you turn logging on, it'll give you some very cool graphs of battery use over time and CPU utilization over days even. Produces some very cool results when I do battery life testing.-Brian
529th - Tuesday, July 20, 2010 - link
First of all I want to say I love mine! :) Bought it the day it came out.Wow what a great review!!!
I didn't know you could run benchmarks on a phone! Linpack!?? WOW awesome!
I can't wait till Froyo! :)
Thanks again chief!
<3 Anandtech reviews!
WaltFrench - Saturday, July 24, 2010 - link
Linpack is a 90s-era benchmark that performs a specific matrix solution. As much as possible, all floating point adds and muls.I've tried in other forums to find an app, prior to 6/1/2010, that actually uses Gaussian elimination with partial pivoting. The particular method works best to find complex patterns within large data sets; that's great for my statistical investment models and for a lot of other stuff. It's strongly suggestive of performance on weather simulations, quantum chemistry, etc., stuff that no sane person would attempt (today) on a smartphone.
Others claim Linpack scores around 40 on overclocked ARM chips with Froyo (the JITting being fabulously helpful for highly repetitive benchmark code). I got ~35 on my iPhone. These scores are ~ 13X–16X what the Linpack author quoted long ago for his 486 (/487, I presume).
I don't know a lot about graphics but presume 3D work that calls for lots of floating point Add/Mul work would get routed to the GPU, so I think these scores are of extremely limited relevance to any smartphone app I can envision.
vshin - Tuesday, July 20, 2010 - link
Where are the antenna attenuation tests? No weak spots?Brian Klug - Tuesday, July 20, 2010 - link
There's definitely attenuation tests in there, and weak spots. The bottom of the phone as expected causes a 15 dB drop. It's on page 14: http://www.anandtech.com/show/3826/motorola-droid-...-Brian