Let me get this out of the way first, I like this phone a lot.  It’s a great device, it’s fast, it’s sexy, it’s big..but it’s not perfect…far from it, and most of the reason is due to the crap software that is on it…let me explain.

The UI and Software

My OG ran stock vanilla Android (what devs call AOSP: Android Open Source Project). This basically means it’s the bare Android OS with no added UI tweaks and no added bloatware crap (with exception to some Verizon apps).  This is the best way to run Android for the most part because it’s not using the CPU or RAM to run some fancy/ugly user interface over top of it, it’s not going to have built-in apps syncing crap in the background, it’s just plain ol’ vanilla ice cream (and I like vanilla ice cream).  And it works!  It doesn’t waste CPU (meaning it’s faster) and it doesn’t background sync unnecessary apps constantly (meaning battery savings) unless you install them.  But of course, HTC and other companies want to change it to suit their own phones and needs.

This is a Screenshot from a Nexus 1 running AOSP 2.2

Now, the Thunderbolt (as with many HTC phones) doesn’t do AOSP Android, they use Sense UI, it’s their own user interface which they designed to put on mobile devices for a “sleek” and “unified” look.

This is Sense UI

While some people like the look (which I don’t think is terrible mind you) and the feel, I don’t like it, I hate it.  There are several reasons I hate it actually the first and most important being that it’s clunky and slow to respond VERY often; it feels like my OG before I rooted it…this shouldn’t happen on a 1Ghz phone with 700+MB or RAM.  So what I did to “fix” this was install ADW.Launcher and use that as my home app.  It’s faster, and it looks and feels more like a stock phone now.  Second, they package a whole mess of crap in with it; they have a “friendsteam” which gathers your Twitter and Facebook and whatnot into a widget on your screen and displays it and updates it for you; a weather widget (which is actually nice, but i should have a choice to remove it);  and their own Facebook and Twitter syncing built in.  This is stuff I’d like to install on my own and not have running in the background constantly asking me to log in and sync; if I want Twitter and FB, let me install them myself.  They also use their own MMS app which is very slow compared to the AOSP app.

You might be thinking, “man, this is cool that it’s all built-in, why are you hating on this?”  Because I like to be able to choose what to have installed on my device.  Because of these built in apps (which mind you, aren’t really apps, they’re more like utilities) I have two Facebook apps, and two Twitter apps and it’s kinda dumb to waste space on stuff like that.  I also find it annoying that they START UP WITH THE DEVICE…even when I DON’T USE THEM.  What a waste of CPU and battery.  Once CM7 is released for the phone (not Alpha-builds) that will be my savior.  Verizon is also guilty of bundling tons of bloatware with this device.  When I received the phone it was PACKED with tons and tons of useless crap..and you can’t remove this stuff!  I’ve written about carriers loading bloatware onto phones before, this shit needs to stop with Android.

The Battery

Smartphones are notorious for having crummy batteries.  My OG was actually pretty great before the last few months of using it.  I used to get over a day with it and I was happy.  When deciding on a new phone every review I read had the same complaint with regard to the Thunderbolt: The battery is terrible.  Now, I’m never far from a power source, and I have around 4 or 5 micro-USB chargers from my older devices and ones that I found around the lab, so this wasn’t too much of an issue for me.  My first day on the phone I got through the entire day of heavy use and texting without it dying, it got to about 5% by midnight (from 8am or so).  The second day, same thing.  On the third day that’s when it ended.  Without using it too much I made it to about 2pm before it started dying on me, I charged it and it was low again by 9pm.  Now I see what the complaints were about.  I tried using task killers to kill unwanted tasks, I synced data less, I lowered brightness, nothing helped.  I read around online and found the best way to get more mileage was to turn off 4G.  I figured, I don’t need 4G all the time, so it’s fine, if I get more battery time out of it this is what needs to be done.  After turning off 4G, I get through the day again.  A few weeks ago an update was released that helped the 4G radio consume less power, so since then I’ve actually been able to leave 4G on and get through most of my day with it…so good on them for fixing that.

The Hardware Itself

This is where the phone really does come out.  This phone has some weight to it (it’s heavier than my OG which was a brick) and it’s got that big bright screen.  The screen makes it so easy to read things on and to watch videos, the rubberized back makes it easy to hold, the weight makes it feel like you’re not going to crush it in your hands.  It is a nice, solid phone.  It’s also fast when you need it to be.  Playing games, running apps, downloading, it just runs fast (especially with ADW.Launcher).  Of course Verizon’s network helps too, I get 4G everywhere in NYC, and the 4G speeds are really good (EVEN INDOORS! Take that WiMax!).  I have plenty of space on the 32GB MicroSD card they give you and on the internal storage (8GB but only about 2.5 are available).  The only complaints I have about the hardware and design: no dedicated camera button, I really miss this, but it’s fairly minor; the bluetooth volume is super low, I’ve read that it only does it with some headsets but my Jabra is so low I cannot use it; and the GPS takes forever to lock on, sometimes 5-10 minutes.  Now, some of this is probably software-based so a fix may be in line (apparently there might be an update in the next month or so to address some of these issues as well as the random reboots caused by the last update) but until that fix is out these problems will remain.

Overall

So to sum this up in a few lines (TL;DR); I really like this phone a lot, it is a great phone by design.  The 1Ghz Snapdragon processor and the large amount of RAM really make this phone fly with apps and games and with Verizon’s 4G it really is a speedy phone in all faces.  However, the phone has many kinks due to some bad software that comes bundled with it and a broken update from HTC.  Most of it’s issues are solely based on the software so hopefully we will see fixes for them in the future.

Some first impressions: This thing is super fast, it’s got a nice feeling to it (not as solid as my DROID but still pretty well built), and the screen is really really nice.  The battery life isn’t as bad as everyone says it it…I got a full day out of it with fairly heavy use…we’ll see if that continues though.  I hate SenseUI…so I replaced it with ADW Launcher right away and I’m waiting for CyanogenMod to come out for it (it’s currently being worked on).  So expect some sort of review in the coming days/weeks…

I installed CM7 when it was at RC1 for the DROID (still buggy, but still good for everyday use) and I originally flashed my phone by doing a factory reset of the device (removes everything) and then installing the ROM. This gave me an endless boot screen.  What I had to do to fix this was not only do a factory reset, but wipe the cache partition AND the Dalvik cache partition.  This was easy with the ClockworkMod and it was also nearly 100% risk free since I had a complete Nandroid backup.  After wiping the two it booted successfully!

I noticed that in Android 2.3 Google will restore all of your previously purchased and downloaded apps if you want it to automatically on a new device (only the app itself, not the data..like game save data).  This is great, but I already decided to use MyBackup Root for this, mainly because I wanted to have my stuff there with all of the data.  So i just told the phone not to download everything and I’ll just restore everything from my backup.  What this left me with was broken installed apps with no way to update them because the Market links were all hosed.  This sucked, now what was I supposed to do?  I decided to flash again and allow Google to push the apps to my phone.  This process took some time but everything was downloaded for the most part; unfortunately, I didn’t have my app data, so all of my game data and all of my settings were gone…I check MyBackup and sure enough I was able to restore data only!  I did that and bingo, everything worked again with all of my old data!  A few apps needed to be reinstalled or needed their data wiped (Google maps and Facebook I think) but for the most part everything worked just as it was supposed to.

Choose which to restore? Yay!

So now that I had my apps on my phone, I was nearing happiness with my hacked DROID.  I say nearing because I was still having many issues with other things.  I won’t go into every little one but I will talk about the two that almost made me decide to go back to stock.

LED Notifications

The one thing I love about Android phones is the LED notifications.  A simple little LED in the corner of my phone blinks different colors for certain things (texts, emails, etc) so I don’t need to turn the screen on, or unlock my phone to see what I missed or see what that beep was from…I can just look at the color of the LED.  Funny thing happened after installing, it stopped working.  I would look down and nothing would be blinking but when I unlocked my phone I’d notice an e-mail that I missed!  What was going on here?  I looked in the settings and found that CM has basically rewritten the notification system and you can customize colors and blink rate from it if you so desired, but instead it broke the damn thing.  This wouldn’t fly with me, I was about to go back to stock because one of my favorite features was broken…then I found the forums.  I searched the issue on the forums and found a lot of people with the same issue, on different phones even!  Reading through many of the posts they all usually came around to the same solution, un-check everything in the LED settings then check them again then hit “Reset all LED notifications” and reboot. And it worked!  I had my LED back and working and now it was even better because I can change the settings for every program and even change the colors and blink rate for them, pretty neat.

Change color and rate for LED notifications

Missing Messages

Now that my LED notifications worked I was happy that I could look down and see if I missed any emails or (more importantly) text messages…but strangely I felt that I was receiving less messages.  I went an entire day without a text message, which is very odd for me actually.  I looked at my phone, no blinking LED, I unlocked the phone, no notification in the menu, I opened the messaging app and boom, new texts, some as old as a day!  What the hell was going on with this?  I’m missing text messages now?  This used to happen with my EnV Touch, never my DROID!  I tried resetting my notifications for the app, and it would work for a while after I opened the app.  I figured, okay, it’s fixed, but then it would stop later on in the day.  I was getting very frustrated with this now and was again thinking about going back to stock.  I hit the forums again and found one post about the issue with one simple solution:

The solution! Check that box!

Once I checked that, never missed another message.  It locks the message app in the memory so it’s always running.  Sure it uses up memory, but my messages are more important to me than the amount of apps I can run at one time.

Side note: But why does the DROID do this with CM7?  The DROID has 256MB RAM, this was a lot when the phone came out and with 2.1 it was fine.  Once 2.2 was released memory was becoming a problem for the phone.  The phone had trouble even keeping the Home app in memory; if you ran a program that was memory hungry and went back to the home screen you’d have to wait for it to redraw because Android’s memory management would kill it.  So in CM7 you can see the two check boxes for home and messaging, this stoped the redrawing(relaunching) and the missing messages…but it took some memory away of course which means you can only do so much multitasking before apps start getting killed.  Android 2.3.3 uses more memory, and the DROID just doesn’t have that much…so CM7 also allows asset purging to free up RAM as well as compucache (memory compression).  These use a little CPU but allow you to multitask fairly well;  it’s nowhere near as good as other newer phones, but it works.

There were some other small odds and ends that I had fixed by tweaking settings and installing updates but I thought that these two were really the most damming for me.  I managed to fix them with help from other nerds at the CyanogenMod Forums who were running into similar issues and there are some I managed to fix by trial and error.  Now, he ROM still has it’s occasional reboots and hiccups (not very often) and they usually happen with two programs; Google Maps and the Camera app, but these crashes happen less and less with each update.

CM7 is now out of RC and was released as Gold…but not for the DROID yet.  It still is very much a work in progress, but the progress is going very quickly, and I really like the direction it’s heading.  They’ve managed to give DROID users Android 2.3 even after Motorola decided it “wouldn’t work” on the phone.  Well, it is working (for the most part) and I’m fairly happy with it.  It has really allowed me to use my phone a bit longer than I was expecting.  I’m probably going to wait until August to upgrade my phone instead of going for the Thunderbolt, but time may change that.  What I do know is that my phone still works well and I will get more time out of it because of the ROMS.

So when Froyo (Android 2.2) came out the DROID got it down the line and that’s when the DROID started to show it’s age; extremely slow…a big drop in performance.  So I decided to root it to get a little more millage out of it before my upgrade.  Mind you, I was waiting for the Thunderbolt to come out to replace it…but decided against upgrading for the time…another story I suppose.  I decided to use SuperOneClick to root my phone, and damn it was simple.  Literally one click and it was done…but what can I do with this root?  Well, first thing was overclocking to see if I can get some more speed.  I overclocked it to 800MHz and really didn’t notice much of a difference besides the fact that I could now have a wireless hot-spot…oh and I could take screen shots now (why doesn’t Android have this functionality built in? Seriously!).

Hey look, I need to ROOT to take a screen shot!

So I decided to take it a step further.  My buddy was telling me about CyanogenMod and how he loved it on his MyTouch and basically brought life back into it.  So I said “Why the hell not?”  Not only does it add a lot of functionality, it will give me Android 2.3.3 (Gingerbread)…something the original DROIDs won’t ever see normally.  I backed-up my apps and text messages phone using MyBackup Root then flashed my recovery ROM to ClockworkMod which allows me to install firmware from the SD card and allows me to backup my entire phone to an image just in case anything goes wrong.  After the backup with MyBackup Root I rebooted into recovery mode and backed-up the entire phone using the Nandroid backup (in the recovery) then started to flash CyanogenMod 7 on my phone..this meant I had to do a complete wipe of the phone which is always scary but with the backup I should be cool!

Wiped the phone, flashed the ROM, and booted the phone. It worked! I had the Release Candidate (at the time it was RC1) of CyanogenMod 7 on my phone!

I had some issues with CM7 at first and some issues with getting my apps back (which I’ll talk about in Part 2) but after some initial bumps I was up running as smooth as I could be on a release candidate.  I had some reboots and some programs would crash but reinstalling them from scratch helped for the most part.

After a few updates it became more and more stable.  I am now running RC4 with a new ultra-low voltage kernel (which allows me to overclock to 1GHz and uses less battery power than the stock kernel). which gives me good battery life, pretty good performance, and all around a pretty good experience.

Android 2.3.3 and 1.1GHz!

So if you’re looking to get some more time from your old DROID this seems like a great way to do it.  It’s not up there with the new phones, but it does give your device a nice little jolt until you decide to retire it.

In Part 2 I’ll talk about installing all of the apps from backup and troubleshooting the many issues I had with memory issues and how they were resolved.

Today Motorola responded to all of the eFuse nonsense with something that makes the situation a bit better.

Motorola’s primary focus is the security of our end users and protection of their data, while also meeting carrier, partner and legal requirements. The Droid X and a majority of Android consumer devices on the market today have a secured bootloader. In reference specifically to eFuse, the technology is not loaded with the purpose of preventing a consumer device from functioning, but rather ensuring for the user that the device only runs on updated and tested versions of software. If a device attempts to boot with unapproved software, it will go into recovery mode, and can re-boot once approved software is re-installed. Checking for a valid software configuration is a common practice within the industry to protect the user against potential malicious software threats. Motorola has been a long time advocate of open platforms and provides a number of resources to developers to foster the ecosystem including tools and access to devices via MOTODEV at http://developer.motorola.com.

This is very good compared to bricking the phone.  At least the phone can be recovered by the user instead of having to ship it to Motorola for a repair(not sure of the complete details and how warranty would work).  I’m also happy to see that Moto responded so quickly to the public.  However, this still does not sit well with me as Android was developed with developers and tinkering in mind.  If I want to mess around with my device, why can’t I?

(Thanks to Tom for pointing this out for me)

Well…

Yesterday’s post has already shown us that Motorola should really rework some of their business practices, but it also puts them in a precarious position in the OHA by going against what the OHA is exactly trying to stop, carrier and corporate lockdown of mobile devices. Some even think that because of the eFuse Moto should be asked to leave the OHA, and I’m not entirely sure that they’re wrong in asking this. If they are supposed to abide by the OHA terms, they should. No deviations.

Now for another punch in the OHA/Android face, T-Mobile and Verizon are now installing “junkware” in their new Android phones that cannot be removed in most circumstances. The LA Times blog is reporting that, “the Droid X comes loaded with several nonstandard applications for Google’s Android, most of which cannot be removed” and that T-Mobile’s new Samsung Vibrant is also loaded with some extra apps that cannot be removed. What kind of apps are installed? Here’s a few snips:

Among the [Droid X's] so-called junkware is a Blockbuster video app and a demo for an Electronic Arts game called Need for Speed: Shift….The EA racing game, which provides limited functionality and a large button on the introduction screen urging players to buy the full version, can be removed…

Skype, which is included with other Android handsets Verizon sells, is a permanent fixture, as is a utility called City ID. The latter program provides location information about phone numbers on the incoming call screen. But it works for only 15 days before asking users to pay $1.99 per month…

The T-Mobile Vibrant phone from Samsung, meanwhile, has four of these extra apps staring you in the face.

One is the movie “Avatar,” permanently loaded onto the device…Another is a live video channel called MobiTV — good for only 30 days. The third is a link to install an EA game called The Sims 3: Collector’s Edition. The last is an outdated version of Amazon’s Kindle app.

There’s also Slacker Radio, which cannot be used before providing an e-mail address, and a button leading to Gogo Inflight Internet’s website, which includes a one-month trial for Web surfing (only on plans that provide the service).

Try as you might, none of these apps can be uninstalled.

That is an awful lot of software to load onto a phone that runs an operating system that is supposed to be “free” and “open” for it’s users. The fact that most of them cannot be uninstalled is the most enraging part. I’m also sure that these apps take up a good deal of storage space.

Samsung, Motorola, Verizon, and T-Mobile are completely going against the principles of the OHA which they are all (with the exception of Verizon) a part of. But I’d probably blame the carries more because in the end, they are the one’s with final say on what is loaded on their devices.

So, should all of them be asked to leave the OHA? I’d say that if they continue this trend then yes. The OHA should give them an ultimatum to stop and they should take it or leave. If the OHA fails to even deliver on that then what is the point of the OHA? If you’re not going to stand by one of your most basic principles then you have failed.

While I don’t think this is worse than the eFuse in the Droid X, it certainly is something that needs to be resolved just as rapidly. Putting a few small applications on a phone specific to your company is not really a problem, not allowing your customers to remove them is.

According to a source at My Droid World (and Motorola themselves), the Droid X has an eFuse chip installed in the device. The long and short of it is that Motorola has installed this eFuse in the new Droid X which checks the phone for the proper kernel, boot-loader, and ROM and if the proper software is not found it will automatically “trip a fuse” to corrupt the phone’s boot-loader forcing you to get it repaired and will most likely void your warranty. Oh and did I mention that the phone can ONLY be repaired by Motorola, so the Verizon Store won’t help you (well, they’ll ship it to them for you) and you’ll most likely end up pay for a new phone.

Why is Motorola doing this to their phones? According to the Motorola blog:

We understand there is a community of developers interested in going beyond Android application development and experimenting with Android system development and re-flashing phones. For these developers, we highly recommend obtaining either a Google ADP1 developer phone or a Nexus One, both of which are intended for these purposes. At this time, Motorola Android-based handsets are intended for use by consumers and Android application developers, and we have currently chosen not to go into the business of providing fully unlocked developer phones.

Now if I read that correctly, Motorola just told people to buy an HTC device (the Nexus One or a Google ADP1 dev phone) and not their product because their “Android-based handsets are intended for use by consumers and Android application developers.” So, the DROID was a fluke? Well…

When we do deviate from our normal practice, such as we did with the DROID, there is a specific business reason for doing so. We understand this can result in some confusion, and apologize for any frustration.

You’re joking, right? You deviated on the DROID for a “business reason” and now that everyone loves your Android-based phones, you’re going to change it? How stupid does that sound?

First, if you’re going to say you have a reason you could at least tell the people what that reason was even if it’s most likely about money. Secondly, why would you want to change something that has worked already? You know the whole “no fix if no broke” thing? The DROID was probably the best smartphone released last year because of it’s features and it’s openness. Taking one of those key selling points away is really going to piss people off. Also, not only is it frustrating, it’s just a punch right in the face of all the people who praised your phone for it’s openness.

What happens when (like the MyTouch 3g and G1, etc) the developers stop caring about a phone so much that they don’t release a new version of Android for it, when their phones are still capable of running them? Or if Motorola decides not to update the SenseUI on the phone and you’re stuck with whatever they stop with? Well, of course you’re supposed to buy another phone from them, but it probably won’t be a Moto phone if the eFuse is still there. But there are a lot of people want to get all they can from their device (I mean, you did pay $200+ for it!). So they’ll end up going the route of rooting a phone and installing a modded Android install and continue to be happy with your device. Does it change that fact that it’s still a Motorola brand phone? No, it just shows that your hardware still kicks ass 2 years after it was released instead of going to the bottom of the old electronics drawer or whatever.

I realize not everyone cares about modding their phones, hell it’s most likely a larger portion than the people who do care, but the issue is that Motorola is making it okay for a company to brick YOUR phone if they don’t like what you do to it. You know, the phone YOU paid for with YOUR money (which Motorola took of course!). A lot of people buy devices based on how much the company lets you tinker with the device after you buy it.

I’m almost positive that the phone will still be hacked, but this is going to cause a big backlash in the Android community against Motorola (and probably Verizon even though they most likely have nothing to do with it). A lot of Android folk are very pro-open-source and while the software is still “open” the hardware will strike you down if you try to change it.

While I won’t tell people not to buy a Moto phone again I will say that the Droid X will probably be a bad choice if you’re going to alter the base software or if you want the phone to last a long time.