Motorola Droid X: Thoroughly Reviewed
by Brian Klug on July 20, 2010 4:27 PM EST- Posted in
- Smartphones
- Motorola Droid X
- OMAP
- Mobile
Of course, any discussion of the OMAP 3630 series would be incomplete without mention of the recent headlines involving Motorola’s potentially locked down bootloader.
The original controversy stemmed from speculation that Motorola would be blowing e-Fuses on the OMAP platform. If you’ve been following console modifications the last few years, you’ll likely recall that Microsoft has been using and blowing e-fuses for years now to prevent users from downgrading the Xbox 360 kernel. The reality is that TI has included mobile security and e-fuses through M-Shield on their SoCs for some time now, including the OMAP 3430 on the original Droid. We pinged TI just to clarify our suspicions:
“TI's M-Shield technology, which is integrated on the OMAP processors, does include OEM-specific, one-time-programmable keys (e-fuse) that are only accessible from inside the secure environment for authentication and encryption. It is up to our customers - Motorola in this case - to comment on how this component is utilized on our chips.”
So M-Shield and e-fuses have always been on the TI datasheet, Motorola has just decided to use them on the X. It’s highly likely that the X will have an encrypted and locked down bootloader just like the original Droid’s European cousin, the Motorola Milestone - a device which is still unbroken months later. If Motorola goes this route, it’s possible that it will be a long time before we see the same kind of custom ROMs on the X as we did the original Droid, and if a phone’s bootloader isn’t unlocked within a few months, the phone will likely be forgotten and replaced with the latest and greatest.
Motorola’s official statement on the matter is that while they won’t be bricking devices, they will be enforcing official firmware for the OS and baseband - and the mechanism for doing so is with e-fuses. The result is that if you aren’t running updated and approved software (assumedly OS and baseband), the X will go into recovery mode and won’t boot until approved software is re-installed.
Motorola is in an interesting bind here - there are carrier requirements and other legal requirements which force them to lock the bootloader. However, bootloaders from HTC devices are famously (in fact, possibly purposefully) easy to crack, making it easy for anyone to cook and flash their own ROMs and enable all kinds of customization. If the X truly is as locked down or more locked down than the Milestone, it might not even see that kind of development at all. As it stands now, if that kind of modification is important to you, you’re better off with an HTC device.
Android’s openness is an interesting subject. The platform is undeniably more open, but users are still forced to unlock bootloaders and flash custom ROMs, or root their devices to play around with things like overclocking or even loading different skins (Sense, Blur, stock, or others). Though it’s unquestionably less locked down than iOS, Google and its partners could do well to take a look at Nokia, which famously provides instructions for and even encourages users to gain root on devices like the N900.
Facebook
Twitter
RSS
89 Comments
View All Comments
TareX - Thursday, July 22, 2010 - link
Why are all the Samsung Galaxy S phones missing from your charts and comparisons? I wanted to see how Hummingbird compared and how the Super AMOLED fared against their Droid X counterparts...strikeback03 - Tuesday, July 27, 2010 - link
Maybe because the first US version launched a day before the review went up, and they weren't sent a review sample.enealDC - Thursday, July 22, 2010 - link
Great job!Juniper Research - Friday, July 23, 2010 - link
Very interesting article... we have this week published a new report on smartphones and a free whitepaper is available to download here... http://www.juniperresearch.com/reports/next_genera...John Levett
Marketing Executive at Juniper Research
Homefries - Saturday, July 24, 2010 - link
First off, great review Brian.However, while you did a very thorough comparison of the Droid X to other Android devices, you barely mentioned the real competitor the Droid X has to stand up against: the iPhone 4.
Readers want to know if the Droid X is the best phone on the market - the whole market - not just the market subset dedicated to Android devices.
Like the majority of the tech media, your review furthers the notion readers belong exclusively to either the iOS camp or the Andriod camp. This is simply not true. Informed readers, like the ones that peruse Anandtech, want to buy one smartphone, regardless of any marketing slants, that is the best.
Your review of the Droid X should have helped us answer the question, "Should I buy the Droid X or the iPhone 4?" But, it did not.
strikeback03 - Tuesday, July 27, 2010 - link
Well, I think the conclusion in the iPhone article and some earlier Android articles applies, there is no "best" for everyone. Some people love Apple and the Apple way of life, some people won't touch it. As the iPhone is currently limited to AT&T, that is going to deter a lot of people. How large a pocket/bag you plan on carrying the phone in might make size differences more important to some than others. So while I am not one of the readers calling for no subjective opinions (it is interesting that FroYo feels significantly faster/different) I think it is still up to each buyer to decide what is most important to them.Electrofreak - Saturday, July 24, 2010 - link
Brian and Anand, are you sure you're using the correct information regarding the SoC in the Droid X? I believe it is a OMAP 3640, not a 3630, as the maximum recommended clock speed of the 3630 is described in numerous places across the net as being 720 MHz, while the max clock speed of the 3640 is described as 1 GHz. In addition, the max recommended clock speed of the 3430 in the Droid was 600 MHz, not 800.The information I cite above is widely available across the web... if you've got inside information the rest of us don't have, by all means let us know. But as someone who has written articles of my own on ARM SoCs and follows ARM industry news closely, I suspect that your data may not be 100% correct.
Regardless, I do have to thank you for writing some of the most informative hardware articles on the net. I appreciate it!
Electrofreak - Saturday, July 24, 2010 - link
...and I just found this: http://e2e.ti.com/blogs_/b/mobile_momentum/archive...So, per TI's blog it is the 3630... now we just need an explanation of the other info on the web that describes the 3630 as maxing out at 720 MHz.
Brian Klug - Monday, July 26, 2010 - link
Yeah, TI's documentation is a bit outdated. Anand tackled the SoC part, but the 3630 is indeed a 1 GHz part, it isn't the 3640 guaranteed. There was a lot of confusion online about it, but Anand got the official word. ;)I agree, back when I did my other OMAP 3 piece it was 720 MHz.
-Brian
Electrofreak - Saturday, July 24, 2010 - link
Looking forward to that Hummingbird review Brian. I hope you're able to dig up some info that I wasn't able to when I wrote my article (http://alienbabeltech.com/main/?p=17125) back in April.