Tuesday, September 28, 2010

Friday, September 24, 2010

Thursday, September 9, 2010

Samsung's Epic Fail, Part II

Lots of comments, calls, e-mail, and questions the past couple of days on my review of the Epic 4G. A number of reviews I've seen make me believe that most reviewers aren't using the phone as their sole mobile device; that, or I simply have a piece of totally crap hardware.

Before going to the virtual mailbag, let's take a look at the last couple of days' use...

Yesterday, the Epic made it five hours before dying. Usage was pretty basic--a solid half-hour of e-mail and web surfing on the train, a bit of note-taking during an hour-long meeting, another solid half-hour of e-mail and web surfing on the train, about 10 minutes of phone calls, then more random e-mail and web surfing until the unit died five hours from unplugging. Note that none of the bonus radios were on--4G, Wi-Fi, Bluetooth, and GPS were all off. Five hours of relatively light use like that on my BlackBerry Curve would've probably cost me about 20% of my battery.

Of course, yesterday was a dream compared to today. Yesterday was like living in a corridor. Today was more like living in a paper bag in a septic tank.

I undocked the Epic at 6:45 a.m.; after an 80-minute bus/L commute where I did nothing but e-mail and web surfing, I was down to 55% of battery. Seriously. An hour-twenty, and I'd gone through nearly half my battery. As was the case yesterday, this was as battery-saving a commute as one could possibly hope for--4G, Wi-Fi, Bluetooth, and GPS all turned off. I can say good things about Sprint's 3G coverage and speeds here in Chicago; as I noted in my initial review, there's a ton of other stuff I'd like to test, but the range anxiety makes doing so a tenuous proposition.

From 8:05 till about 8:25, I used the phone for a couple of e-mails, but it was in my pocket the rest of the time. At 8:25, I sat down with a couple of buddies, and we started talking about the phone. I showed them all the stuff I like about it (screen, OS responsiveness, apps, keyboard), while kvetching about the battery life, and all the wackiness about apps firing off in the background. At 8:35, I was down to 45% battery. Remember that number.

In an attempt to show my friends how apps initiated themselves with no rhyme, reason, or intervention whatsoever, I offered to turn off the phone, then power it back on. I've done this a number of times in hopes of getting some kind of handle on what's going on with the OS and the apps, so I expected to lose another percentage point or two of battery life in the power down/power up process.

At which point I moved into the paper bag in the septic tank.

15%. Fifteen percent. Fifteen freakin' percent of battery left after that reboot.

Seriously.

At this point, I was somewhere between incredulous and pissed.

Incredulous because, well, stuff like this just doesn't happen; while I'm not an engineer by degree, I do play one on TV, so my logical mind just can't process something like this. Pissed because, I can't understand how any reasonable kind of QA process from two top-notch companies like Samsung and Sprint could've let something like this out into the wild.

I wasn't near a power outlet, so I plugged into my Mac via the USB port to grab some juice at about 8:45. The MacBook isn't exactly its own utility substation, but I did manage to get enough juice to get back to 65% by 11:30 when my MacBook battery gave up. Thank God for my iPad.

Yesterday, five hours. Today, I might've made it two-and-a-half if I'd continued to use the phone. Brutal.

One comment from the mailbag mentioned that turning on the 4G radio for even two minutes can make for a 10% hit on the battery. Yep. Brutal. The same commenter mentioned that the mobile hotspot functionality is a two-hour feature on just about any phone. Agreed. Equally brutal.

Listen up Samsung, HTC, and whoever else is building 4G phones for Sprint, as well as Verizon, AT&T, and whoever will be building y'all's LTE phones...

Don't cram in features that people want just because the marketing research says it's a good idea. The Epic 4G has a killer feature set--but the only thing being killed right now is Samsung's reputation, either for initial build quality and QA, or for overall design (i.e., if they can't fix this with a hardware exchange or a new firmware/software download). The software has definite usability issues, some of which I mentioned in the initial review, some of which I'll get to shortly. But, shipping a phone that can only last a few hours when users merely use the features for which they've chosen to purchase this phone--the most expensive phone in the Sprint stable? Unacceptable, both from a customer satisfaction standpoint and from a corporate branding and reputation standpoint.

As I mentioned in the first review, my hope is that I just have a piece of bad hardware, a bad battery, and/or a bad software load. I haven't been able to get back to Sprint to pick up a new device, but am planning to do so over the weekend. But, if after going to a replacement device, the experience is no different, I'll only be able to conclude that Samsung and Sprint are going to end up with a whole lot of phones in landfills. Samsung's made an unbelievable move into the mobile device market over the last decade; they'd survive a black eye like this, but it sure wouldn't feel good.

Speaking of not feeling good, over the past couple of days three Evo owners shared their experiences with me, none of which I'd classify as being high quality experiences. My former colleague Keith Mahoney left an in-depth comment on the original post, concurring with my experience, and also believing that Android has some kind of weirdness going on with unwanted phantom app firing destroying battery life. As Keith noted, the HTC HD2 has the same screen as the Evo, so Sprint's blaming the size of the screen being a power-hungry beast doesn't fly--the HD2 runs Windows Mobile, and doesn't have battery life issues according to Keith.

Wait a sec...did I just throw a compliment to Windows Mobile? Where's my thermometer?

Keith also mentioned that Sprint suggested putting the Evo into standby mode when not in use; Matt Burns also mentioned that he's taken to putting the Evo into airplane mode to extend battery life. Realistically, all any of us want as customers is for our devices to offer some semblance of the value proposition upon which we based our purchasing decision.

If I wanted to own a phone where I had to turn off the radios to use it, I'd buy an iPod Touch, for God's sake.

One final point that Keith makes bears investigation--not all devices running Android are having this issue, so some combination of Sprint and Android is turning devices into power-hungry beasts. I'm not hearing battery life complaints about either Droid, so Android and CDMA seem to be getting along just fine on Verizon's network. And, the Epic's battery life is abysmal even with no radios on save for the regular 3G radio, so something funky is going on that can't be blamed on the 4G radio.

Ray Trygstad weighed in with his answer to the Evo's battery life problems--he pulled a spare battery out of his pocket. I'm willing to go that route, but a single spare battery isn't going to cut it for the Epic--I'd need a pocket full of kryptonite to reach what seems like the 4500-6000 milliamp hours I'd need to get through a day of regular-to-heavy use on the Epic.

I can't say this enough--I hope I just have a lemon. I hope I just have a lemon. I hope I just have a lemon.

Before wrapping things up for tonight, here's two more "features" for you to consider. In the initial review, I mentioned that the voice-activated Google Search doesn't work with Bluetooth--pretty stupid, since when I'm driving, I'd prefer to not have to deactivate Bluetooth (or pick up the phone and hold it next to my mouth) just to use voice-activate search. Well, I've identified at least one other case where the guys working on the Bluetooth stack missed the team meetings with the OS guys--voice mail. The Epic has a very cool voice mail app where you can see and act accordingly on each individual voice message--but God forbid you want to check voice mail while using Bluetooth.

You see, the voice mail app doesn't seem to understand that Bluetooth exists.

Seriously.

Want to check voice mail while your Bluetooth earpiece is in your ear? Hold the phone to your other ear.

One other UI issue that's continually bugging me is when I want to go to a contact in portrait mode. In landscape mode with the hard keyboard slid open, I can simply start typing the contact's name, and the contact manager quickly narrows down who I'm looking for. But, in portrait mode, there's no option to pop up the soft keyboard, meaning you have to touch the alphabet letter of your contact, then scroll down (or up, if you choose to go +1 on the letter and work backwards) to find your contact. If I'm on a train or a bus, or sitting in a meeting, it's no biggie to pop the hard keyboard. But, if I'm driving and need to look something up (and spare me the lecture on distracted driving...assume I'm at a red light), having to kick the device open is a total pain--not nearly as bad as the inability to dial from the calendar, but you get my gist.

So, a week in, and I still haven't come close to approximating a typical day's use on my old school BlackBerry Curve. Agreed, I'm cranking through a lot more web content, since the browser on BB OS 4.5 was all but unusable, but the range anxiety associated with the Epic makes me shy away from doing all the stuff one might want to do on a mobile device.

Like phone calls and e-mails, for instance.

I hope I just have a lemon, I hope I just have a lemon, I hope I just have a lemon...

Tuesday, September 7, 2010

Samsung's Epic Fail--the Samsung DOH!

(Let me preface this post by noting the possibility that I may have bad hardware, a bad battery, and/or a bad software load. I've checked for new software each day this week (to no avail), and continue to be hopeful that Samsung will have new software available in the coming days. That said, I'm extremely skeptical that the issues I'm having with battery life are solely software-related, so I'm also planning to return this hardware for a different unit, in hopes that a newer manufacturing run might address the issues I'm seeing. Everything I say in this review is predicated on the fact that the unit I currently have performs as Samsung designed it--and if that's the case, the entire design is a lemon. If I have bad hardware, an exchange for new hardware should resolve the battery life and 4G issues I'm seeing, hopefully; further, I'm hopeful that any software-related and lack of functionality issues will also be fixable in relatively short order.)

I tend to start reviews by focusing on the positive, then later mixing in whatever negative thoughts I may have. This is the rare review where I simply can't do so. The Samsung Epic 4G is awesome, in all respects--awesome screen, awesome capabilities, and awesomely bad battery life.

Here's the most succinct way for me to describe this...if you're in the target demographic for the Samsung Epic 4G, you simply won't be able to survive life with this phone. That's one hell of a paradox, but that's how bad battery life is. I'm not normally at a loss for words (and I know that some of you wish I was more often), but I had to turn to a thesaurus to grab a sufficiently broad range of adjectives to describe the Epic 4G's battery life...
  • abominable
  • appalling
  • atrocious
  • deplorable
  • ghastly
  • horrendous
  • shocking
Let's step back a week. Before picking up my Epic 4G, I thought back to the first phone I owned with a full keyboard--the T-Mobile Sidekick, which I purchased in mid-2002. Despite its shortcomings, the Sidekick had two radically compelling capabilities going for it--the landscape design made for a fantastic typing experience, while the cloud-based architecture meant that all your mail, contacts, and calendar could be stored (or lost, as Microsoft learned last year) on the network, independent of the device itself.

Since my Sidekick, I've owned a Palm Treo 650, a BlackBerry 8700 and 8320 (Curve), and now the Epic 4G. If you know me, you know that I tend to be a bleeding edge, first day guy on some technologies, like the new Apple TV (already on order) or the Jawbone II. However, over the years I've been a slow follower from a mobile device standpoint; with my mobile as my lifeline to the world, I've tended to be a bit conservative in making technology jumps. Plus, since I seem to write essays on my mobile, I've been unwilling to give up a hardware keyboard. For all the cool things that an iPhone 4 can do, there's two features it doesn't offer that I desired on my next phone--a hard keyboard and mobile hotspot capability. The Samsung Epic 4G offers both; combined with Android as an operating system, I've been eagerly awaiting the Epic's arrival.

So, aside from the battery (whose awesome brutalness I'll expound on more shortly), how is it?

First, a look at what's typically in my bag at any given time, at least as of last week...
  • T-Mobile BlackBerry Curve 8320
  • Jawbone II
  • 13" MacBook
  • 64 GB iPad 3G
  • Verizon MiFi
  • Clear 4G USB stick
  • A ridiculous array of cables to power and connect all of the above; look for me on wirelessmyass.com one of these days
In trying to simplify my world, I want to get down to just the Mac (and would buy a new MacBook Air the moment it came out if Apple were to ever introduce a new version, for crying out loud), the iPad, a Bluetooth earpiece which charges using micro-USB (rather than a proprietary connector), and a phone. Is the Epic 4G my answer?

As of now, no freakin' way, based solely on battery life. Sadly, there's a bunch of features that I can't even sufficiently test, as the battery's that bad--if I don't test at the beginning of the day, the phone's out of juice long before I get around to my typical late-night testing regimen; of course, the phone's already been plugged in for hours by that time, but hey. At least the Epic charges fairly quickly.

I'm less than a week in, but I'm already having the range anxiety typically associated with owning a plug-in electric vehicle. In fact, that'd be a recipe for an epic disaster--plugging an Epic into a Nissan Leaf would grind the car to a halt faster than driving it over a spike strip. At least now I know what it's like to own a plug-in electric vehicle without actually having to take the plunge.

What's to like about the Epic? A lot. What's to not like about the Epic? Not a ton, but of the stuff to dislike, the battery's such a dealbreaker that I've taken my eye off the ball on the other negatives.

The interwebs are full of out of box experience recaps of the Epic, so let's skip to what's important...

Keyboard: Really good, bordering on excellent. After more than six years on a portrait-shaped device, moving back to a landscape device is taking a little getting used to; and, while the device doesn't yet feel as comfortable as my Sidekick did, it feels good. On a scale of one to 10, I'll give it an eight, with possibility of a higher grade as I gain more comfort over time (assuming the Epic survives the 30-day money back guarantee, which it won't as of right now due to the battery issues). Love the cursor keys, too.

Screen: Awesome, except in outdoor light. Responsive, well-registered, and crisp. Unlike many reviewers, I don't find the Epic's AMOLED screen to be overly saturated to my eyes--but I'm also a guy that used to shoot Fuji Velvia 50, so yeah, I love contrast. Outdoors, the screen is challenging; in bright sunlight, it's worthless. I'm not sure how to state that more eloquently, but the best advice for trying to use the Epic in the sun is, don't. Go find some shade. I give it a nine for almost all uses, a three outdoors on a typical Beijing day, and a generous one on a San Diego summer day. Let's call it a seven, unless you live in a cave (with a 20 amp circuit, an Airvana femtocell, and a cable modem-attached Wi-Fi access point), in which case it's a nine.

Apps: While the Android Market is still well behind the iTunes app store in terms of number of applications, I'm pleasantly surprised at the depth and breadth of applications available on Android. In a side-by-side comparison with my iPad, I have quite a few apps which aren't available on Android. But, coming off of a BlackBerry, whose App World can most kindly be described as "crap", I'm not displeased with the currently available choices. Plus, in an open development environment and market like Android's, I expect that Android will continue to close the gap on Apple in terms of both quantity and quality of apps, particularly given the ability to sideload apps. I give it a six, with the expectation that over the next year, that grade will improve to an eight.

GPS: Solid, seemingly showing none of the flaws other Galaxy S GPS devices have shown at shipment. Both Sprint Navigation and Google Maps work extremely well. Turn-by-turn directions on Sprint Nav are a definite benefit. In 4G coverage areas, the GPS works great even when on a phone call; outside of 4G coverage areas, not so much. Seven.

Call quality: So far, so good, on handheld, speaker, and Bluetooth. Call completion is ridiculously quick; this is my first experience with Sprint as a carrier, and my first experience overall with CDMA for circuit-switched voice, so maybe this is a CDMA versus GSM benefit, but I'm pleasantly shocked at how quickly calls complete. Eight, maybe a nine.

4G: Sadly, not good at all. Over the last six months, my 4G stick has been pretty solid for me in much of the Chicago area. But, in places where I know I've had good Clear 4G reception with my USB stick, I'm getting zero 4G reception on the Epic--in many cases over the last week, when I've turned on the 4G radio, the status message has immediately informed me that 4G is disconnected. The Epic 4G without the 4G would be the Samsung Doh, as a 3G phone with lousy battery life would make me say little more than "DOH!" I intend to do some more testing over the next couple of weeks comparing the Epic 4G's reception with my USB stick's reception, as well as with my Verizon MiFi. While I understand design tradeoffs for packing antennas into mobile devices (something that Apple's learned a little bit about, too), my hunch is that the poor 4G reception is a firmware issue, not an antenna placement issue. Right now, I'll grade the 4G capability a two, until I'm able to do some more testing. Speaking of 4G and potential firmware/software issues...

Mobile Hotspot: Disappointing in two of the three cases where I've needed it; there've been other times when I've wanted it, but didn't want to take the battery hit (again, a range issue which is simply unacceptable). I still haven't been able to test the mobile hotspot with 4G coverage, owing to the coverage/reception issues I mention above. This demands much further testing. For now, I'll grade mobile hotspot as a three, based on the fact that the one time I've been able to successfully use the feature (albeit over 3G), the battery drained so quickly that the device was dead before I accomplished much.

Android OS: Wow, am I conflicted here. Seriously, there's a ton to like about the OS on this hardware. In particular, Google Apps users will LOVE the instant synchronization of contacts and calendars. The device is extremely responsive, the OS boots quickly, and all in all, I find the performance and usability of the OS to generally be quite good. But, note I said "generally". For now, I have to grade the OS as Incomplete, with a few items that are particularly mind-boggling...
  • On a calendar appointment, you can't click to dial a phone number. Seriously? Whiskey Tango Foxtrot? For a conference call I had earlier today, I had to dial in six times before I remembered the correct combination of phone number and passcode. This should be an A-1 priority fix for whoever's responsible for this calendar app, whether it's a Samsung app or an off-the-shelf Android app.
  • The built-in mail reader (not to be confused with the Gmail app, which is an external app with its own shortcomings, including the inability to view a combined inbox of multiple mail accounts) doesn't support push mail, at least that I've been able to determine. Worse, there doesn't seem to be a rhyme or reason to how the mail reader goes out and gets mail, if at all. In the combined view (which is great), you can see all your accounts in a single view. The key problem is, despite the fact that I have the reader set to pull e-mail in five minute intervals, I have to manually go out and refresh in order to receive new mail; worse, I can only do so from within each individual account, rather than from the combined inbox--meaning, if you have five mail accounts, you have to go to each inbox, then refresh within each. I can't possibly imagine that this would've been a design feature in a PRD--although I can't imagine that a ridiculously short battery life was a goal, either.
  • The Google Search box on the main screen takes a little getting used to, but is a reasonably beneficial way to access contacts, one which I could see myself getting used to with more use. However, there's a dealbreaker here--the fact that the voice-activated Google Search doesn't work with a Bluetooth headset attached. That's so entirely brain dead, it deserves its own bullet.
  • Voice-activated Google Search doesn't work with a Bluetooth headset attached. (See? I told you it deserved its own bullet). Let me paint a picture for you. You're driving and need to make a phone call. You tap the voice-activated Google Search icon, and say "Call Jimmy Carter". The device returns a "No speech heard" error, since for whatever cotton-pickin' (or peanut-pickin') reason, the inter-app communication between voice-activated Google Search and the Bluetooth stack doesn't seem to exist. I mean, I understand pressure to get products to market, but how the hell do you ship a device that almost requires a driver to cause an accident? Between the inability to dial from a calendar appointment and the requirement to either disable Bluetooth to search for a contact to call, or to spell out the contact's name on the virtual or physical keyboard, the Epic should come with both its own liability insurance policy and a stack of get-out-of-jail-free cards, which you'll need from continually messing around with the device while driving.
  • A number of other things are annoying--in addition to copy and paste functionality being limited, the main home screen doesn't rotate to landscape mode unless you slide open the physical keyboard, which is particularly annoying when you have the Epic in the battery dock--which you will, since you need to keep it plugged in every time you're near an outlet.
  • But, the single most annoying "feature" is apps firing off in the background with no rhyme nor reason whatsoever--which could be the single biggest battery-sucking issue on the entire device...
Since the introduction of the iPhone, we've all heard Steve Jobs loud and clear on the potential shortcomings of multitasking as a power drain on mobile devices. If the experience I've had over the last week is any indicator, he's 110% correct. But, let's not jump to conclusions. I can't possibly imagine that when Sprint and Samsung got together to write the MRD and PRD for the Epic, someone said "Hey, why don't we not only allow apps unlimited ability to initiate themselves in the background, but also allow them to trigger for no apparent reason? They don't even have to be apps that've ever been used."

Case in point--right now, after rebooting the phone, then killing all the running apps, the following apps have loaded themselves into memory within a couple of minutes...
  • Sprint Navigation
  • Sprint Hotspot
  • Messaging
  • Qik
  • Google Voice
  • Gmail
  • Voicemail
  • Voice Dialer
  • Gallery
  • Sprint Football Live
  • NASCAR
  • Sprint Zone
  • Email
  • Battery Monitor
  • Amazon MP3
Let's be crystal clear on something. This is not a case of the device launching my most frequently used applications. I've used Qik exactly once, to test it. Google Voice, I signed into the day I picked up my Epic. Sprint Zone is some kind of customer service dealio. The other Sprint apps also fired off on their own for no apparent reason. Yes, I've used each at various times, but haven't set them to auto-launch, ever. Amazon MP3 is an on-deck app that I can't get rid of, despite numerous attempts. If this damned thing loads on its own one more time, I swear I'm going to cancel my Amazon Prime membership. That, or start ordering anvils by the dozen, upgrading to overnight shipping for $3.99, then refusing delivery.

I'd heard that Advanced Task Killer was absolutely the most beneficial app I would download from the Android Market; to each of you (Ward, you were first) who told me that, thank you, thank you, thank you. Plus, ATK could almost serve as a pseudo-random number generator--every time I go into ATK, there's a different and unique combo of self-launched apps running in the background, spitting battery life onto the floor.

So, after a week, where are we?

With a bit of a crazy week heading into the Labor Day weekend, I didn't get a chance to use the device in anything approximating a normal day's use. Today, I did, and it ain't pretty.

4:15.

That's right--four hours and fifteen minutes from a full charge to flat-out flatlined. That's beyond brutal.

That sucks. And that's putting it kindly.

I mean, not only does that suck, but that makes me say there's no possible way that this could've been within the design envelope for this device, and that I absolutely must have some kind of a hardware problem.

Let's break this down a little. While I didn't have a pen and paper with me (which I regret, since that's the sole mechanism to successfully dial into a conference call from a calendar appointment), I have a pretty good idea of what my usage looked like.

(By the way, to those of you who might suggest that I need to be more diligent in turning off radios that aren't in active in use--I did. I read all the Evo reviews, so I know all about turning off radios to extend battery life. In this case, we're talking about trying to treat a punctured femoral artery with a piece of scotch tape and a slide rule.)

I pulled the Epic out of its desktop dock and immediately jumped onto a conference call--or tried to, as I had to dial in six times before I remembered/guessed the proper phone number and password combo; at this point, the Bluetooth and CDMA radios were the only two in use, with 4G, GPS, and Wi-Fi turned off. About five minutes in, I turned on the 4G radio and ran a speed test; 3.5 mb/s down and 500 kb/s up during a phone call is pretty awesome performance. A couple of minutes later, I turned on the GPS, and punched in the address of my destination, which was about 20 minutes from where I was at that point. Due to the spotty 4G reception, it took a while before I could actually get directions and maps, but once I had them, navigation was a cinch.

When my conference call ended after 67 minutes, I jumped on another call, but not before checking my battery life remaining. I was at 60% of battery left, after little more than an hour undocked from the cradle.

Epic!

I spent a little less than a half-hour on the second call, still with the GPS and 4G radios on so I could navigate to my next destination. Once I arrived there, I jumped on another call which took about 20-25 minutes; I turned off the GPS during that call, but left 4G on, as I wanted to be able to get e-mail while on the phone. I spent the next 45-50 minutes or so doing other stuff that allowed the Epic to drain battery on its own, rather than with my direct intervention. I then turned on the mobile hotspot, which connected over 3G (but not 4G). I had my iPad attached to the mobile hotspot for about 10 minutes--just long enough to do a couple of speed tests spaced out a few minutes apart. I then checked e-mail a few times, before the phone finally croaked at the four hour and fifteen minute mark.

Epic!

As I sit here shaking my head at the device's paucity of power, the only word that comes to mind is "incredulous". I just don't understand how a product, particularly one from a top-notch consumer electronics leader like Samsung, could come to market with such a woefully inadequate usage experience.

I mean, the Kin had a longer battery life than this.

Let's tie this up with a neat little bow. The Epic 4G is the first 4G phone with a slide-out keyboard, and has mobile hotspot capability, a gorgeous screen, a pretty darned good camera, and a whole bunch of other compellingly interesting features. Just don't try to use them all at once, for any period of time.

And that, my friends, may be the single biggest shortcoming of this entire experiment. Samsung has delivered a device that's world class in many aspects, but in the most important aspect--actual usage--the device is nearly worthless. Two hours of phone calls, a couple hours of the GPS and 4G radios turned on, and a bit of hotspot usage, and the Epic isn't.

Here's an analogy for you. Boeing is going to eventually ship the 787 one of these years. While the Dreamliner's testing hasn't quite gone according to plan, at least they're testing it. I have serious doubt that Samsung (or their contract manufacturer) did much real-world testing, at least to any level of depth. If the Epic was an airplane, its cruise height would be 7,000 feet, with a ceiling of 11,000 feet. Loading the airplane with actual passengers would lower cruise and ceiling by another couple thousand feet each; allowing those passengers to use any amenities (lavatories, air vents) would chop off another few hundred feet. Ultimately, the plane would only be allowed to fly mail stop routes, cruising at 4,000 feet, ensuring that when the engines flamed out the Epic could dead-stick its way to its next stop a few miles down the road.

I mentioned earlier the paradox that if you're in the crosshairs as a potential user of this phone, it's the wrong phone for you. As of right now, that's absolutely the case--Sprint's most expensive phone is laden with features, albeit ones you may not be able to use for any period of time if at all. If you can justify spending (after rebate) $250 on this phone, it's highly likely that you're a person who has a need for speed, for functionality, for business e-mail and calendar integration, and for ease of use. The Epic does some of those things well, some more than others. But, until I receive a unit with stable hardware (a category in which my current Epic doesn't qualify, as I gotta believe there's something wrong) and stable software (where my current Epic also doesn't qualify, as unattended app initiation is to me a showstopper bug), I can't recommend the phone to anyone, unless you have money to fritter away. If you do, buy a couple of spare batteries and a couple extra chargers, as you're going to need them.

In the meantime, I'm going to return my Epic to the Sprint store tomorrow and pick up a different one--one which I hope has come from a different manufacturing batch. I want to love this phone. I need to love this phone, purely from a capabilities standpoint. But the only way I'm gonna get some love from this phone is a decent user experience, which a ridiculously short battery life totally ruins. Right now, I feel a little like Charlie Brown in his relationship with the little red-haired girl.

Unrequited.

Thursday, September 2, 2010

Not Exactly The Onion: DLNA Responds to Apple TV

Moments after Steve Jobs announced the new Apple TV yesterday, I sent out a status update that said…

"Time to pre-order the new Apple TV. DLNA needs to worry, right freakin' now. And I'm a HUGE DLNA fan."

I made it nearly an entire minute before my phone rang; that call was shortly interrupted by another, followed by a slew of e-mails, tweets, and Facebook comments.

Pretty much everyone wanted to know, what the heck did I mean? The more I thought about it, the more I decided that the best response DLNA could make is in the form of a press release. So, here we go--the release *I* might write if I were in a position to do so…

DLNA Welcomes Apple to the Living Room


Congratulates Apple on Decision to Enable Content Enjoyment in a Social Setting


Portland, OR -- September 2, 2010 -- The Digital Living Network Alliance (DLNA) today welcomes the Apple ecosystem to the digital living room. By the end of September 2010, Apple users will be able to enjoy their photos, video, and music in a social setting, on the ideal display for social interaction--the television, rather than the small screen setting of iPhones, iPads, and iPods.


Steve, we know you've been busy, but what took you so long?


Since its founding in 2003, more than 7,500 products have been DLNA Certified®, giving consumers the interoperability they need within a full range of products including digital cameras, PCs and laptops, printers and televisions. Such a wide range of products means that by 2012, more than a billion DLNA devices will have shipped, according to ABI Research. Apple's recognition that consumers enjoy content in a twelve foot setting is an important milestone for our industry. The current two-foot user interface where Apple users typically consume content is ideal for touch screen devices, particularly when sharing photos of grandchildren with fellow airplane travelers, blaring music at inappropriate volume on trains, and nodding one's head at a visual voice mail message.

However, the explosion in social networking enabled by high-powered mobile platforms such as the iPhone has created the dichotomy that in a world of oversharing, the actual consumption of content has never been more solitary. When silver halide still played a part in preserving memories, doing so meant to capture, to share, and to enjoy--together. Unfortunately, as first-world economies have morphed into always-on, all-digital lifestyles, the actual act of enjoying shared memories in a social environment has gone the way of Jarts and the Oldsmobile.

Today, content is most often consumed by individuals on mobile devices; DLNA members Nokia, Samsung, LG, Motorola and Sony Ericsson shipped a combined 1.21 billion mobile phones worldwide in 2009, so we understand that mobile is a huge market for capture and consumption. But, one of the big challenges the entire consumer electronics industry continues to face is how to keep people truly connected in an ever-more-connected world, a world where a family of five can sit around a dinner table and avoid face-to-face conversation, courtesy of the very devices that our members ship in tremendous volumes.

We're certainly not against shared virtual enjoyment of content--Facebook has revolutionized the lives of technology users in a manner not seen since Google, and before that, well, Apple. But, there's more to life than photos that spend their lives locked up in a Facebook account, even if tens of millions of the cameras taking those photos are produced by our members. When we started DLNA in 2003, we believed that the right way to enable consumers to enjoy their content was in a connected environment; that's even more true today. Technologies like high-speed wireless, network-attached storage, and high-resolution HD video cameras one can shove in a pocket largely didn't exist seven years ago; if they did, they were the exclusive domain of the earliest of early adopters, at price points out of reach for all but the ultra-affluent, and at a technology integration cost only a geek could love.

We set out to change that, to get ahead of the technology curve, to standardize in a multi-vendor environment all the things that made this type of content sharing a five- or six-figure investment. In 2003, a number of us got together and chose to think different. What that's meant over the last seven years is a lot of heavy lifting, an enormous amount of time and investment, to ensure that consumers are able to connect and enjoy their content in a multi-vendor environment, one where content can be captured, stored, shipped, and consumed. Consumers buying DLNA Certified® devices can be confident they're purchasing solutions that work together and can be networked, regardless of manufacturer. That's why more than 200 companies have joined DLNA, and continue to collaborate to ensure that our products will work together to deliver content sharing which our users can enjoy.

That type of shared, truly shared, content enjoyment was challenging for Apple users until yesterday's announcement. As Apple mentioned, Apple TV has been little more than a hobby since its introduction in 2006. The new Apple TV offers a compelling value proposition, one which we're confident will motivate the entire industry to develop and deliver products which interoperate even better, at even lower cost, delivering even more value. Ultimately, in doing so, we all stand to benefit, particularly as we get people back in front of the big screen, together. Maybe, just maybe, the new Apple TV will promote a few more families to gather around the television to enjoy a shared content experience together, to set aside their iPhones, iPods, and iPads for a few minutes or a few hours. Whether viewing a high budget movie from a major studio delivered over a high-speed Internet link, or simply enjoying family photos served off of a personal computer in the home, we think there's real benefit for those families and friends gathering to connect and enjoy; that's the motivation for all of us to keep at it, to keep delivering products our customers want, at a range of price points, in a truly multi-vendor environment.

We've learned a lot about the art and science of content sharing over the last seven years. One of the most important things we've learned is that this race is a marathon, not a sprint. We'd like to take this opportunity to welcome Apple to the race.

See you on the couch.

I'll clarify a few more of my thoughts over the coming days, and try to answer a number of questions that've already come in from some of you. The point is, Apple's entry to the market is a huge challenge to DLNA, a challenge to move beyond the vernacular of DMPs, DMCs, and DMRs, to deliver a clearer message to the average consumer. DLNA's value proposition has always been solid; the challenge has been, how to get an alliance of more than 200 members to agree on a single message, one which resonates with the average consumer. Apple's entry into this market now gives them an end-to-end solution that looks suspiciously like a DLNA architecture--iTunes as the digital media server (DMS); the new Apple TV as the digital media player (DMP); and the iPhone, iPod, and iPad as digital media renderers (DMRs) or digital media controllers (DMCs).

DLNA's always had the architecture right; now it's time to get the message right. Ironically, Apple's announcement may've been the best possible kick in the pants for DLNA and its members. Personally, I have a foot in both camps; I ordered the new Apple TV today, which will be the DMP in an all-Mac content flow (Mac Mini as DMS, iPad as DMC/DMR, Apple TV as DMP). But, I also firmly believe in DLNA; today I picked up the Samsung Epic 4G, which serves as a DLNA DMC/DMR, to go with my Promise DLNA NAS (DMS). I think I have a DLNA DMP floating around here somewhere, but that'll have to wait...