More BLUR additions

We’ve already discussed the majority of Motorola’s BLUR-lite skin for Android in the context of the Droid X review. I thought that I wouldn’t see any more from BLUR, but I was wrong. Cleary not contented with how things turned out with the Droid X, Motorola has added a few extraneous things that for me push the Droid 2 a bit over the scale in my opinion.

First off, the default widget layout remains the same. 

Home Screens—Default Configuration and Layout

There’s stuff on every page, but thankfully you can remove them pretty easily. I still like that the Motorola widgets can be resized dynamically, however there’s just too many of them strewn about by default. It’s a matter of personal taste I guess, but don’t people like things to be clean and empty when they get them instead of already full of stuff?

Anyhow, what really gets me is what’s been added. Tapping on the up arrow to launch the applications list no longer results in an instantaneous presentation of applications. Instead, there’s a sporadically low FPS, choppy 1 second fade animation. Hit home to go back to the home screen, and there’s another 1 second fade animation. Go to settings -> display and set animations to “no window animations are shown,” and the second long blur animation will still happen every single time.

Left—Lock Screen, Right—Applications Menu

It sounds stupid, but it’s really these little extra things that are frustrating. Further, because they’re part of the BLUR UI, they don’t hook into the standard Android settings menus, which is why disabling all animations doesn’t do anything. It’s stuff like this that makes rooting not just a matter of choice, but rather a necessity for getting all this extra stuff out of the way. 

Virtually everything else about the BLUR skin that I saw on the Droid X I see on the Droid 2. Probably the only notable change is that random extra animation, and landscape support for when you have the keyboard out.

Landscape Homescreen

Thankfully, you really can use the device with the keyboard out basically everywhere in Android, as everything first party has portrait and landscape support. Applications have to build their own landscape support in, but that’s how it is on all the major platforms.

Browser

The Droid 2 is the first Motorola Droid shipping with Flash preinstalled. It comes with 10.1.72.10 installed by default, which is the last beta build out on the market before 10.1 officially was finalized. Interestingly enough, there’s Adobe Flash branding right on the Droid 2 box. 

You can update the device to the latest version of Adobe Flash, 10.1.92.10, by grabbing it from the market directly. Be warned though it doesn’t show up in the normal list of applications waiting to be updated from the downloads window, you have to seek it out yourself. Sam and I have been doing lots of flash testing and have an interesting story coming up—there’s no major difference between the Beta 3 build and this final version that we’ve encountered yet.

What’s different about the browser on the Droid 2 is in bookmarks. I noticed that you can’t delete either the Verizon or Google bookmark, which occupy the first and second spot in the bookmark menu. Try to delete them by long pressing, and you’ll get a dialog where deletion is suspiciously absent. You can't scroll up or down, it's just not there. 

Left—Bookmarks, Right—No delete link for VZW

This isn’t just slightly annoying so much as it is unnerving. Do we really need a permanent bookmark to Verizon’s portal page, or Google? Moreover, what's open about forcing you to live with a useless Verizon bookmark you can't delete—without rooting? I’ll let you be the judge.

The rest of the browser is thankfully unchanged and just as great as it is on stock Froyo. 

Virtual Keyboards - Multitouch, Swype, Swiftkey Cellular and WiFi Performance - Part 1
Comments Locked

39 Comments

View All Comments

  • bjacobson - Sunday, September 19, 2010 - link

    My Droid's keyboard now has very bubbled keys. Try running your fingernails down and across in the creases beteween keys. I did this a few times pressing hard, went back to typing texts, and it's made my keys bubbled like the Droid2's, even moreso in my opinion than the photograph there.

    Also, I believe the resistance in the sliding mechanism is the mechanical sliders; I'm pretty sure 2 teflon strips on the back of the phone won't fix that.
  • sotoa - Monday, September 20, 2010 - link

    I like having a dpad on my droid, I just wish it was on the left side like a gamepad, and wish it had diagonals.
  • KaRRiLLioN - Monday, September 20, 2010 - link

    I bought the Droid 2 the day it came out but had to return it for several reasons, most of which I hope have been fixed. Corporate email synch had a terrible bug where it wouldn't synch contacts from Exchange if they had categories. Facebook synch would synch EVERYONE instead of just existing contacts. There was no option to change that.

    Most of these issues were caused by BLUR. Any idea if these items now work as advertised?

    So I still have my original Droid with the original flat keyboard. I'm pretty used to it now and have no issues. I think I'll stick to this until another Android-based phone catches my eye. I wouldn't mind something like the Droid X, but I want Super AMOLED.
  • LoneWolf15 - Monday, September 20, 2010 - link

    To fix the Facebook issue, download the Facebook app instead of using the Droid 2's "Social Networking" app.

    I'm not using my D2 for Exchange (we have a Google Apps Domain) but after a week, I've been very happy with my switch from a Blackberry Tour (which I was reasonably satisfied with).
  • PubicTheHare - Monday, September 20, 2010 - link

    The best keyboard on any smart phone is found on the Epic 4G. I played with it yesterday and was amazed at the tactile feedback and overall usability.

    Also, I don't buy that the Droid 2 screen is brighter than the Epic/Fascinate/Captivate/Vibrant's.

    I have the Fascinate and placed it side by side with the Droid 2, both in a store and against a friend's Droid 2 outdoors, and the Fascinate's display was substantially brighter and had more contrast.

    Great review. It seems like Motorola is hitting it out of the ballpark with its latest phones, though I still think they have the most bland styling and their UI (Motoblur) is hideous.

    I bet the OMAP processors are about 80% responsible for the impressive battery life. 9.5 hrs is ridiculous!

    Thanks, Anand.
  • Myrandex - Monday, September 20, 2010 - link

    The Keyboard does look much better than the original Droid, however it still doesn't look like it comes close to the HTC Touch Pro 2 series phone's keyboard. That one is the thing to beat in my opinion. I love the spaced out offset keys and the dedicated row of numbers at the top. I sure hope my next phone has one at least that good.

    Jason
  • silverblue - Monday, September 20, 2010 - link

    ...that you barely mentioned the Epic 4G and its Galaxy S variants. Not trying to justify my purchase, however the lack of a mention on even the gaming and video capture fronts was a little disappointing.
  • MrPIppy - Monday, September 20, 2010 - link

    It's interesting that the Motorola Droids have always been a huge design win for TI, even though almost no other Android phones use TI's OMAP or wireless chips. The Droid, Droid X, and Droid 2 use TI OMAP and WiLink (for WiFi/BT), instead of the almost universal combination of Qualcomm MSM+Broadcom BCM4329. Even Motorola's other Android phones (Backflip, Cliq, etc.) use MSM+BCM4329. Any idea why the Droids get the TI parts?
  • bil3 - Tuesday, September 21, 2010 - link

    Surprised that Anandtech doesn't know, but the Droid JIT performance in linpack is normal.

    Only Snapdragon's scorpion and cortex A9 devices have a fast 128bit FPU which the JIT is optimized for and takes full advantage of.

    This is a very specific case for this operating system as it's very much Java based, JIT performance matters in many operations.

    The OMAP uses the standard A8 FPU which is anemic in comparison (just like the hummingbird & co.)

    The CPU itself is not bad, that's why it's fast enough in raw performance benchmarks or benchs that aren't limited by the JIT.

    In all cases, the JIT still bring a good bit of performance, just not as much as on devices with a fast FPU.
  • Brian Klug - Tuesday, September 21, 2010 - link

    Bil3,

    Very interesting, I wondered for a while about the performance delta being due to the A8 architecture versus Qualcomm's own Scorpion design, but couldn't find that remaining detail. Intriguing that the 128bit FPU makes such a big difference.

    Awesome tidbit!

    -Brian

Log in

Don't have an account? Sign up now