Google's Nexus One

FINALLY! Sitting here in my hands, I happen to have one shiny new Nexus One. Does it live up to all the hype? Is it everything I’d hope it would be?! In a word, yes. And in another word, no. Haha, this is one seriously sweet piece of hardware but the experience as a whole has been a bit of a disappointment. Now, I had originally intended to write a lengthy three-part article to discuss the hardware, software, and carrier performance I’ve experienced since my Nexus One was delivered. I even had a good chunk of it written last night before bed  but today I came across this article which does an excellent job of saying everything I’d wanted to say and it even has benchmark info to boot!

For those not wanting to read through all of that though, let me summarize my first impressions of the Nexus One:

- Wow!

- Excellent build quality. The outer casing has a wonderful textured finish which helps keep the device from slipping out of your sweaty, greasy, Dorito-stained hand. It’s a little heavy but not obnoxious. Overall it feels like an expensive, well designed piece of gear. It’s also thinner than a bulimic super model addicted to meth.

- The trackball is nicer than the one on the Hero and it’s more “crisp” and responsive in those rare times when you actually need to use it.

- The screen – holy crap it’s nice. This is my first AMOLED device and I can see what all the fuss has been about. There’s no comparing it to the LCD on my Hero or other recent phones. Touch input works great on the Nexus One and two handed typing is a cinch. Speaking of typing, the onscreen keyboard works like a charm. Text prediction is surprising accurate and they virtual keys are very responsive.

- Speech-to-text does a great job of transcription. It’s not always spot on but being able to dictate text messages is such a cool feature!

- Google Navigation RULES! It’s far better than the Hero’s Sprint Navigation app. Don’t get me wrong though; I love Sprint Navigation but Google Nav is just sooooo much more refined. Thankfully Google Nav will be coming to the Hero soon once the Android 2.1 update is pushed out.

- The live wallpapers are a neat feature. True, they serve no purpose and probably do wonders for draining your battery, but they look sweet! My favorite is the black and white cloud.

- The beefy Qualcomm Snapdragon processor and 512 MB of RAM (to my knowledge, this is more than any other phone on the market) enable Android 2.1 to cruise on the Nexus One. You can have several programs open simultaneously with literally no decrease in performance. Menus and transitions are as silky smooth as the iPhone 3GS, or possibly even smoother.

- Great camera! The speed reminds me of the Palm Pre (one of that phone’s few strong points) and photos come out pretty darn clear. Likewise, video is nice and smooth even at the highest resolution. Playback is flawless via the Android album app.

- Did I mention how fricken smooth everything runs?!

So, by now it should be fairly easy to see that I’m very impressed with both the Nexus One and Android 2.1. Neither are perfect but the phone is definitely a wonderful device. Android 2.1 has lots of potential too – I can’t wait to get it on my Hero along with an updated Sense UI. The phone and its OS are only part of the equation though. The other part of the experience is the carrier the phone is paired to and unfortunately, T-Mobile’s service around here turned out to be a major letdown. I knew going into this that their coverage is laughable (especially their 3G) but I’m experiencing call distortion even when I have three or four bars of 3G signal. That’s not the worst of it though; for some odd reason, right out of the box I was able to receive calls, send and receive text messages, and browse via EDGE but I wasn’t able to make outbound calls! No matter what I tried, I constantly got “Network busy” on the phone’s display and an earful of fast busy signal. I knew it had to be a network or provisioning problem so first I spoke with T-Mobile. The tech was friendly and tried to be helpful but in the end she didn’t know what she was talking about and referred me to HTC for further troubleshooting. I decided to play along though and called them via the number the T-Mo tech gave me. The gentleman who answered wasn’t at all shocked to hear that T-Mo sent me his way but said exactly what I’d been saying all along – that this was a network or provisioning problem. He got me through to T-Mo again and I proceeded to work with a gentleman in their tech support department. Let me just say, it’s highly frustrating when you know more about the device and network than the person that’s supposed to be helping you does, but again, I played along. He went through his checklist of things to try and after roughly 20 minutes he gave up and got me through to T-Mo’s Tier III troubleshooting department. The Tier III tech was noticeably more knowledgeable but it still took him half an hour of investigation before he resolved the problem (a provisioning issue in their system – go figure). The stories I’ve read about T-Mo, HTC, and Google all referring customers to one another during troubleshooting seem to be true. I honestly don’t know how the average person is going to put up with it if they should ever need assistance. The most annoying thing is that each of the three companies should have a very clearly defined role in the customer service process; Google should provide all assistance with Android OS related issues, HTC should provide help for hardware problems, and T-Mo should be responsible for network troubleshooting. The three companies really need to get this worked out or they’re going to be in big trouble. Someone who just spent $500+ on a phone is not going to want to be told repeatedly that they need to call another company for help.

Sigh.

You know, I hate to keep harping on T-Mobile because I think they’re generally a good company, but several things about the cell service irritate me. First, my voice calls just don’t sound very good. Other reviews extol the Nexus One’s great audio quality which makes me reluctant to blame the phone for the distortion I get while on a call. It seems purely network related to me. Aside from that, T-Mo’s visual voicemail kinda sucks compared to Sprint’s. It’s definitely a nice feature but it just doesn’t seem to measure up (a minor annoyance but one I felt worth mentioning nonetheless). Then there’s T-Mobile’s pricing. The cheapest you can get away with on the Nexus One is $60 a month plus tax (500 anytime minutes, nights and weekends starting at 9pm, unlimited everything else). That’s not terrible next to the outrageous amount you have to pay for an iPhone plan but you have to realize that right now I’m paying $65 a month including tax through Sprint. For that $65 I’m getting 500 anytime minutes to landlines, unlimited minutes to and from any mobile number in the US, nights and weekends that start at 7pm, unlimited everything else – AND – vastly superior coverage and performance. It’s not really a tough decision folks, even if it means I have to live without the Nexus One.

Yes I sound like a broken record, but I’d like to say one last time just how impressed I am with the hardware and software on the Nexus One. It’s a shame that your only real option for a carrier is T-Mobile because their service is just woefully inadequate around here. The unacceptable alternative would be AT&T and they’ve consistently proven that they’re crooked and inept, so I don’t really consider them much of an alternative at all.

I anxiously await the arrival of the Nexus One (or something comparable) on Sprint’s excellent network but in the meantime, my T-Mo Nexus One is getting boxed up and shipped back to Google.

Say, is it just me or is my Sprint Hero doing a happy dance?

Pandora

Pandora - This was the very first app I installed when my Hero arrived. I had it on my Palm Pre and for whatever reason it bogged that phone down horribly (it was bad but still usable). Luckily Pandora performs far better on the Hero! So, for the three of you out there who aren’t familiar with it, Pandora is a free music streaming service that will automatically queue up songs it thinks you might like to hear based on some initial information you give it. As each song plays, you have the option to rate it with a thumbs up, a thumbs down, or skip it and come back later. Giving it a thumbs up tells the service that you like what you’re hearing and that you’d like to sample other music that they deem similar. For example, I started mine out with O.A.R. and after serving up some O.A.R. songs, they shifted to Dave Matthews and other artists they thought I’d like. Giving a song a thumbs down stops and removes it from your playlist forever, causing the next suggested song to queue up and start playing. If you’re not sure whether you like or hate a song and think you’d like to listen to it again sometime, just skip it and move on to the next. Overall, Pandora has done a great job of exposing me to bands that I probably would have never discovered otherwise. I do hit thumbs down now and then, but overall the service is a good judge of what I like (or maybe I’m just a sadly predictable person).

Price: Free

Pros: It’s a great way to discover new music or listen to stuff you already like without having to load your phone up with MP3’s. No commercial interruptions!

Cons: Ads! You can close them manually but they pop up again down at the bottom of the screen after every new song begins. The program is somewhat data intensive (I believe the “high quality” setting has your audio streaming at 96 Kbps, which comes out to around 40 MB per hour of music). As you probably already know, any time you’re downloading data, you’re using your phone’s radio – that means that it’s a battery killer. Best to use this app when you have AC or USB power nearby or when you’re in your car with a mobile charger. Still, even on battery power you should get several hours of streaming.

Dolphin

Dolphin Browser – The stock web browser that ships with the Hero is not bad at all but Dolphin has more features and (in my opinion) runs faster than the stock app. Some of Dolphin’s perks include pinch zoom, the ability to save photos and YouTube videos, and tabbed browsing. Definitely worth checking out.

Price: Free

Pros: Tabbed browsing, better download / file save features, seemingly faster operation than the stock browser, pinch zoom, skinnable interface, optional hand gesture interface, RSS capabilities, cool URL sharing features.

Cons: Ads! To be fair, you only see ads if you use the default homepage, when you do a search, and when you’re in the menu system. No biggie. A paid version which does away with the ads may already be in the works.

NetSentry

NetSentry - This program lets you keep track of how much data you burn through on your phone every month. If you somehow don’t have “unlimited” data from your carrier (which would be awfully foolish with a phone like the Hero), this app would be extra useful since you can set your limits in NetSentry and have it alert you when you’re getting close to them. Even with an “unlimited” data plan though, I still love being able to compare NetSentry’s numbers to what Sprint claims I’ve consumed. So far both have been within about 5 MB of each other. In addition to allowing you to keep track of your 3G usage, NetSentry can keep track of your WiFi too. I don’t really know why you’d want to do that but hey, it’s there if you need it.

Price: Free

Pros: With this app you no longer have to rely on your carrier’s potentially inflated consumption numbers. User definable alert thresholds for both 3G and WiFi, very accurate!

Cons: None to speak of; if you want to get really nitpicky, it’s always running in the background and consumes a minor amount of CPU and battery.

Facebook

Facebook - It’s Facebook on your phone. What more can I say? When I first got my Hero and tried out this app, it was pretty lame. Not quite as bad as the one for the Palm Pre (which is a TOTAL joke), but still lacking a lot of basic functionality. Since then, the app has improved by leaps and bounds. The latest version has 90% of the features that the full blown website has but presents it all in a much more streamlined way. In my opinion, the Android Facebook app is on par or possibly even better than its admittedly awesome iPhone counterpart.

Price: Free

Pros: Shake to update (on the main page), almost the same level of functionality you get directly from the Facebook website.

Cons: None, other than being a little slow sometimes. It remains to be seen if that’s due to the app,  the network I’m accessing it over, or slowdowns on Facebook’s end (or a combo of all three).

Speed Test

Speed Test – You’ve been to Speedtest.net before, right? Well, this app from Ookla gives you the ability to determine how well your cell connection is performing. Lots of factors will affect how fast you’re able to download or upload to the Internet; there’s radio interference issues, tower congestion (lots of other users competing for limited bandwidth), and cheapskate backhaul links (carriers love to use lame 1.5 Mbps T1 circuits to connect their towers back to the the rest of their network rather than put in more efficient ethernet connections whenever they can). This is one of the apps that I always envied on the iPhone. It’s simple, but works beautifully.

Price: Free

Pros: Works like a charm! Tons of options too. Just like Speedtest.net, you can choose which city and ISP you want to test with, you’re given a little screenshot of the results that you can share with other people online, and the app even keeps a record of all the tests you’ve ran over WiFi or 3G.

Cons: None; I have yet to experience anything negative about this app. Ookla really outdid themselves with this one.

PdaNet

PdaNet - Wow, this app could end up being the most important app you download for your phone depending on what kind of user you are. In a nutshell, PdaNet lets you tether your PC to your phone via USB or bluetooth. You can then use the phone as a modem, which can be extremely useful if you travel a lot and don’t want to pay for WiFi, and it can also come in handy when your electricity or home Internet connection goes down. The free version lets you tether via USB with no restrictions for 30 days, then after that it stops letting you use port 443. For the less technically inclined, this means you cannot access pages that use the https protocol like banks or other secure websites. If you’re a cheapskate you should be able to get around this limitation by setting up a home VPN, or you could just pony up the one time fee and get the full featured app. Just be careful though because your cell carrier thinks you should pay them even more for the privilege of using the bandwidth you’re already paying them for on your laptop instead of on your phone. In other words, don’t get their attention by torrenting stuff. Note, you don’t need PdaNet if you root your phone and install the MoDaCo ROM, which has Wifi-to-EVDO tethering built in.

Cost: Free (with some limits) or $29 for the full version.

Pros: Lets you use your laptop anywhere you have a cell connection without having to pony up extra fees to your cell carrier just to use the bandwidth you’ve already paid them for. Extremely handy when WiFi isn’t available. I’ve gotten as much as 1.5 Mbps down and 950 Kbps up, which as far as the upstream goes, is actually on par with the highest tier that my ISP at home will give me via cable modem. As an added bonus, your phone recharges itself when you tether via USB.

Cons: Can suck up lots of battery if you’re tethering via bluetooth, has the potential to get your cell carrier upset with you if you use the connection constantly, especially if you do obvious stuff like run torrents.

Seesmic

Seesmic - Twitter clients are one thing that the Android platform has plenty of. I’ve tried out my fair share of them and in my opinion, it really comes down to two apps – Seesmic or Twidroid. Both have some really nice features and honestly I’d recommend Twidroid over Seesmic if its alert system weren’t all goofed up. I’ll probably switch back to Twidroid after that gets sorted out. Anyway, Seesmic is a great app with lots of nice features. It has support for lists, tweet searches, and just a really nicely polished interface. You can do just about anything in Seesmic that you can on the Twitter website. I haven’t used the desktop version but it looks really nice too.

Cost: Free

Pros: Excellent feature set, allows you to do all your Twitter stuff on your phone instead of having to use the website or Desktop apps.

Cons: Unlike Twidroid, lacks the option to automatically start the app when the phone boots up.

Of course, with over 20,000 apps in the Android Market, there is a mind boggling amount of other stuff out there that you should check out. Even the paid apps are typically only a dollar or two, so get out there and download away! If you find something you think is especially cool, please let me know in this article’s comments section.

So why all the talk about rooting today? Well, my friend William Ruckman is also a Hero owner / fanatic and he saw fit to send in the following steps to take if you’d like to gain root access to your Sprint Hero. It should be noted that rooting your phone can be potentially dangerous (worst case scenario, you screw up and brick your phone). Also, I’m not 100% clear on whether William wrote this procedure completely on his own, borrowed heavily from other resources on the web, or some combination thereof. Bill, if you’d care to clarify that for me, I’ll be happy to update this post.

Presumably this would work on a non-Sprint Hero but since we’re both Sprint users, we can’t really verify that with complete certainty.

In case you want root, do this:

Download the Android SDK to your desktop.

http://developer.android.com/sdk/index.html

Open CMD.exe (Windows) and change directory to the tools directory in the Android SDK.

Make sure your phone is set to development mode under applications, and make sure you have the Android SDK and drivers installed.

Download asroot2 to the tools directory from here:

http://code.google.com/p/flashrec/source/browse/trunk/assets/raw/asroot2

In CMD.exe type:
———————–
adb push asroot2 /data/local/

adb shell

cd /data/local

chmod 0755 asroot2

./asroot2 /system/bin/sh

mount -o remount,rw /dev/block/mtdblock3 /system

cd /system/bin

cat sh > su

chmod 0755 su

chown root.shell su

exit

exit
———————–

ROOTED!

Just copy a file and run the commands above! No installing, no flashing custom ROMs, no worries about bricking your phone!

Give it a restart and enjoy.

Seems pretty cut and dry to me, but again, proceed with caution. I know he says “no worries about bricking your phone” but don’t complain to me if you goof something up and your phone stops working, your boss fires you, your daughter becomes pregnant, the bank repossesses your farm, aliens invade, or the Mona Lisa disappears.

For those of you that would like to give Bill a shout to thank him or shoot him a question about this procedure, you can do so by stopping by his website.

Thanks again for the heads up, amigo!

Update: Bill wrote in to update me on the genesis of this procedure:

About 70% of the procedure I came up with. The rest I got from various forums. However, I found the exact same procedure after the fact in the XDA forum. The asroot2 binary is the key, the rest is just Linux basics.

So there you have it – proof that great minds think alike!

Sprint's HTC Hero

I’ve been enjoying my HTC Hero immensely since I got it earlier this month, but having said that, it hasn’t been a completely problem-free ride. One complaint that’s cropped up so far is that I’ve been experiencing problems watching videos via the kickass YouTube application that the Hero ships with. At first, the app worked perfectly; I could stream all the videos of newlyweds dancing to the altar or Geordi requesting apple juice clips to my heart’s content in either standard or high res, via EVDO or WiFi. Everything ran great! Then, as of about a week ago, I started getting intermittent error messages stating “Sorry, this video cannot be played”, even on videos that had worked before (like my own). Initially I dismissed it as a problem with YouTube not being able to serve up the video stream but when a few hours (and then a few days) passed with the message still popping up, I decided to research and experiment a little to see if I could pinpoint the exact cause of the problem.

To date, this is what I’ve learned:

EVDO

- It’s very rare not to get the “Sorry, video cannot be played” message now.

- When a video does play, opening the menu and then selecting “Watch in high quality” leads to the failure message 100% of the time.

- Selecting the same video over and over sometimes works. For example, I repeatedly selected a Christmas themed LEGO movie featured on the main page of the YouTube app, resulting in the fail message. On the 9th try, it played without any problems. I then paused it and selected the “Watch in high quality” option and immediately got the fail message.

WiFi

- Most videos fail to play the first time, but I can generally get them to work after a couple attempts. Occasionally a video will load right off the bat. All in all, WiFi seems to be much more consistent than EVDO.

All EVDO testing was done with two or more EVDO signal bars in different parts of the country (thereby eliminating the possibility of local tower / backhaul congestion). WiFi tests were conducted via five different ISP’s – three in Ohio, and two in Florida.

I've gotten pretty used to seeing this now.

In researching this issue online, I’ve found that I’m not the only one having trouble with the YouTube app. The frustrating thing about it though is that two other friends with Sprint HTC Hero’s can watch any YouTube videos they want without any trouble whatsoever. Given that this doesn’t affect everyone, it would be difficult to pin the blame on Google / YouTube; likewise, some folks online have theorized that this is Sprint’s way of trying to cut bandwidth usage but that also doesn’t seem like a very plausible explanation because again, the problem does not affect all Hero users. Another important point to take into consideration is that it doesn’t seem to matter if your phone is modded or completely stock. My own Hero has not been rooted, so it’s running the stock Android 1.5 ROM that all new handsets are shipping out with (version 1.56.651.2). Some Hero owners have reported that removing the SD card, rebooting, and then replacing the SD card seems to clear up the YouTube problem. I tried this but it had no effect for me. Another user pointed out that (s)he has better luck when accessing videos in landscape mode vs. portrait mode. As with the previous tip, trying this made no difference with my phone’s symptoms. Still, other users have reported that using YouTube Mobile works, but that also fails for me regardless of whether I’m on WiFi or EVDO, or whether I select the YouTube app or HTC’s Flash Player when prompted. Suspecting that one of the Android Market apps that I’ve downloaded may be partly to blame, I did a complete factory reset of my Hero and made another attempt to watch YouTube videos while everything was in 100% stock condition. Sadly, this still had no affect.

I’m continuing to keep an eye on forums and message boards but it still looks like this is a widespread problem without much in the way of a fix just yet. The more people that report the problem though, the more likely it is that Sprint, HTC, and YouTube will take steps to investigate. Not being able to watch YouTube on my phone certainly isn’t a huge deal and even if the problem persists for a while, it won’t do much to sour my opinion of the Hero or Android in general. Who knows, maybe the impending Hero software update (Android OS 2.1) will be the magic fix. Until then, I’ll continue enjoying the other aspects of this kickass phone… which still beats the pants off the Palm Pre.

Update, 12.27.2009 – I spoke with one of the friends I mentioned up top that has a Hero but was not experiencing problems streaming from YouTube. It turns out that now he is in fact unable to watch anything via EVDO too, so this issue seems to be spreading. I personally believe it to be a software bug with the app itself, but I’ve started hearing unconfirmed rumors that Palm Pre users are also having problems with YouTube. Is this a coincidence, or is something afoot?

Update, 1.6.2010 – Cellular South user “RV” wrote in to let me know that he is experiencing the same YouTube problems on his Hero too. Between that and reports of this affecting VZ’s Eris users, my theory that this is either a server-side problem with YouTube or a software problem with the app itself seems more and more likely. I’m still leaning towards the problem stemming from a glitch in the app though.

Update, 1.7.2010 – I was able to confirm that YouTube videos will not work via EVDO on the brand new VZ Eris that another friend purchased today. At this point I don’t know anyone with a Hero or Eris that isn’t having at least partial failure when trying to stream video from YouTube.

Update, 1.10.2010 – As of today, I am running the custom MoDaCo ROM on my Hero and the YouTube app still doesn’t work (not that I thought it would).

…

Do you have a Hero and want to share your experiences using the stock YouTube app with the rest of the Interwebs? Well, what are you waiting for?! Leave a comment, sucka!

Palm Pre

The last time I posted an article, I talked about my previous cell phone, the Palm Pre. At that point I hadn’t yet given up hope that Palm would get off their asses and transform the Pre from a so-so device to the truly ass kicking machine that it was meant to be; I knew the phone had its shortcomings but I was willing to overlook those because of the few things it’s actually good at (and it reeeeeally is good at them). Well, I’m here today to tell you fine folks that I finally got tired of waiting for Palm to make a move so I’ve just officially joined the hordes of other disgruntled ex-Pre owners that left Palm’s uber phone for greener (Android-ier) pastures. Even now, Palm still hasn’t done much to correct most of the glaring issues that have been obvious since webOS and the Pre were officially launched on Sprint about six months ago. To their credit, Palm has released several OS patches but each update so far has failed to take a corrective stab at what irks me about this platform.

Here are a few just of those issues off the top of my head:

- Inability to set custom ringtones / alert sounds for pretty much anything that isn’t a phone call (the latest software update, webOS 1.3.1, makes a very half assed attempt to address this but still fails miserably). A small but decidedly annoying deficiency.

- During an alert such as a freshly received text message, the phone will gently buzz one time and give off a chime. After that there’s no external indication whatsoever that you have a new message, unless you have installed the homebrew LED modification. You have to manually wake the phone up and check to see if any new alerts are present. This is very inconvenient if your phone is in your pocket at the time.

- The stock calendar app is a joke. Period.

- There is no onscreen keyboard unless you add one via homebrew modifcations, which means that any time you want to enter even a single letter or digit into a field on a webpage or app, you have to slide the fragile keyboard open. Not a huge deal, but it actually gets pretty tedious after a while.

- Battery life was pretty disappointing for me. I realize there are many factors such as signal quality and usage that have to be taken into account on this one, but I was lucky if I was able to get through a full 8.5 hour workday on a single charge with my Pre.  I purchased an extra Touchstone just for my desk at work so I wouldn’t have to worry about not being able to use my phone in the evenings.

- In six months, the Palm App Catalog has had less than 700 apps posted. I get it – a brand spanking new OS is going to take time to develop apps. The problem is that of those 700-ish apps, many are garbage that aren’t worth a second look ($20 translator apps that only do one language, etc.). There are a few good paid apps such as Tweed and PixelPipe, but the latter is priced more expensively than it is on Android and the webOS version doesn’t even have all the same features. An $8 app to track your FedEx or UPS packages… are these app developers really that dense?

– Poor handset build quality. It seems some units were built better than others; I was lucky in that my second Pre did not suffer from the same shoddy construction that many other Pre owners have been complaining about in the PreCentral forums and elsewhere.

- Absolutely AWFUL stock camera application. No zoom, no ability to crop? Just pitiful. Loads of people are also ticked at Palm simply because the Pre still doesn’t feature the video recording mode that it was supposed to come with. Recent software updates have at least laid the groundwork for that to be implemented.

- Overall disappointing performance. The Pre has the same very capable CPU as the iPhone 3GS along with an integrated GPU which could easily help rid the phone of the jerky menus and stuttering apps it currently suffers from, but Palm shipped it with the GPU deactivated because apparently they didn’t have time to devise a method of programming for it before they were forced to hand the phone over to Sprint. Rumor has it that an upcoming software update will finally unlock the GPU so some tasks can be offloaded onto the GPU from the CPU.

Like I said, that’s just a few complaints that I can think of off the top of my head. In all fairness, there are an assortment of things that Palm has managed to get right so far.

Of those, here is what readily comes to mind:

- Multitasking. Yes, other platforms like Android are capable of running several apps at once but no one can compete with the way webOS does it. Simply put, the “cards” system that webOS employs is as elegant as it is simplistic. Nothing else even comes close (yet?).

- Synergy. This is webOS’s fancy name for its integration with Facebook, Google, and other resources where you might have contacts. Synergy has its own set of flaws but it’s still a very nice first attempt at aggregating all your information into one easily accessible place.

- Browser. Easily as good as, if not better than, the iPhone’s browser. It’ll be interesting to see if it remains as robust after Flash support is finally added.

- On-screen notifications. I like how Android handles on-screen notifications, but the way webOS resizes your active card and displays your notification at the bottom is pretty nice too.

- You cannot brick the Pre. Okay, that’s not entirely true, but Palm has released software tools which make the likelihood of you killing your phone while trying to mod it very, very minimal. I guess this is their way of saying “Hey, we know the phone is missing many basic features that other phones have right out of the box, but if you want to try adding those features yourself by modding your phone, at least you won’t kill it.”

- Copy and Paste. I’ve played around with my friends’ and relatives’ iPhones before but I never tried cutting and pasting text with them. I may not be able to compare the iPhone and Pre in that category, but I can at least say that the Pre’s method of cut and paste puts Android’s to shame.

- Touchstone wireless chargers. They’re a total ripoff at $80 a pop for the kit, but that didn’t keep me from purchasing three.

I really wanted webOS and the Pre to succeed, which is why I was willing to give Palm another chance when I purchased my second Pre in September. Unfortunately, the Pre turned into a major letdown for me. Everyone knows the it was rushed out the door before development was complete because Palm was on the verge of going under, but since then, my perception has been that they aren’t terribly motivated to finish what they started. Also, from what I’ve read, the development kit they’re giving out only allows 3rd party app creators to build the most basic of apps. Programs that make use of the phone’s hardware like the mic and camera are not possible with the current SDK because it doesn’t grant developers access. Because of this the Pre is incapable of having rich graphical games like the ones rapidly becoming commonplace on the iPhone 3GS despite the fact that both have virtually the same hardware setup.

I could go on and on about why I feel the Pre is just a big ball of FAIL when compared to more feature-rich devices like HTC’s Hero but ultimately it’s a very subjective topic. What works for me may not work for you, and likewise. If you’ve stumbled across this rant because you’re considering jumping in bed with Palm though, keep reading what others are saying elsewhere on the Interwebs and try to stop in to a Sprint store to examine a Pre in person so you can make up your own mind.

Now if you’ll excuse me, I’m off to go lovingly stroke my Android-powered Hero…