YouTube on the HTC Hero – what gives?

Sprint Hero

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!

Goodbye Palm, Hello Android!

Palm Pre

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…

Review – Official Sprint Palm Pre Cover

Yes, I purchased another Palm Pre. No, I’m not going to write about that decision other than to say that it replaced an HTC Touch Pro2 that I got rid of within two days of receiving it from Sprint. Since my first encounter with the Pre, things have been greatly improved; within just a few short months the webOS platform has really matured nicely and the Pre’s selection of apps (both official and homebrew) has started to take off.

Sprint's ZCP1098R cover

Sprint's ZCP1098R cover

I’m not here to talk about the Pre though. I’ll probably do a writeup about my latest adventures with Palm’s uber device after webOS 1.2.1 comes out (hopefully soon). Instead, I want to talk about the hard cover that I picked up from Sprint’s store here in town. I first learned about this particular cover from the PreCentral forums. There, a user mentioned that this case fixed the so called “Oreo Effect” that many Pre users are complaining about online. Prior to reading his posting I hadn’t heard of the Oreo Effect because my own Pre is pretty solid. I guess I’m one of the lucky ones. Anyway, he mentioned that this case uses a rail design wherein the top plate and bottom plate actually connect together as opposed to the cheap crappy covers you get off eBay which simply click onto one section of the phone and don’t provide any kind of structural support at all. Intrigued, I did some research but aside from some (not so great) photos and discussion, there wasn’t much in the way of details about the case. Yesterday I decided to purchase one and share my thoughts for the good of all mankind. I know, I rule – no need to point that out but thanks for noticing.

First things first, here’s a little video of the cover in action:

YouTube Preview Image

As you can see, it’s not a bad looking cover. The kit from Sprint includes two faceplates and one back cover. The back cover has all the cutouts for speaker, camera + flash, volume, power, and USB (though the USB is a lost cause with this thing). The front plate, red or chrome, also has cutouts for USB, power, and volume. Installation is straightforward and easy; two clicks and you’re done. As I said above, it’s not a bad looking case. It does add a little bit of thickness / width to the phone but after installing it I found that it hasn’t affected my Pre’s “pocketability” at all. Likewise, my ability to type wasn’t hindered with the cover installed. Where this baby really shines though is the unique rails that the makers have wisely incorporated into the design of the product. The top and bottom halves click together and slide through one another, which provides excellent stability to the Pre’s admittedly weak slider mechanism. I’ve been fortunate in that my Pre doesn’t suffer from the Oreo Effect, but if it did, I can say with complete certainty that this cleverly designed cover would remedy that. Overall, I’d have to say this case is a godsend for Pre users irked by axial wobble, but for the rest of us it’s just a so-so purchase (especially at $33 with tax – ouch). If you can find this particular model on eBay for less than what Sprint wants online or in their stores, then all the better.

Some quick observations:

- This case will fix the Oreo Effect, no doubt about it

- Sprint should price this sucker at $15, not $30 (it’s $.25 worth of plastic after all)

- Touchstone owners may be annoyed because even though this cover has a Touchstone-sized groove cut out of the back, the thickness of the back cover loosens the Touchstone’s magnetic grip on the phone causing it to slip off at the slightest bump (take heed those of you that have installed a Touchstone in your car!)

- This cover will not work with the extended batteries which come with their own custom back cover, such as Seidio’s and Amzer’s mega huge multi-amp hour units

- If you use a USB charger in your car, make sure you bring a pen or paper clip or something else to open the USB trap door on the side because the cover’s faceplate makes it super difficult to access the USB port by hand

- Only available in red or chrome… why?! I’d personally prefer matte black, but I guess that’s nothing a can of Krylon can’t fix

- The kit is built by A.G. Findings & Manufacturing, and it’s listed as item #ZCP1098R on Sprint’s website

If any other Pre owners have purchased this cover and want to chime in, please feel free to post your thoughts in the comments!