Motorola Xoom Review: The First Honeycomb Tablet Arrives
by Anand Lal Shimpi on February 23, 2011 11:57 PM ESTOld & New Apps on Honeycomb
As we mentioned in our overview of Android 3.0, there are a number of features that Honeycomb specific apps are going to be able to take advantage of. For example the dual-pane view that we see in the Honeycomb email apps - we’ll see more of that in future Honeycomb apps similar to what we saw happen with iPad specific apps. We’ll also see developers use contextual action menus.
Existing Android apps should just work on Honeycomb (although some definitely have issues). Google runs these older apps by default full screen, just scaled up to fit the higher resolution of the Xoom.
The fourth button for backwards compatibility: menu
You’ll remember that Honeycomb does away with the menu button, however older Android apps are expecting it to be there. In these situations you’ll see a fourth button added to the lower left of the screen: a virtual menu button.
It’s Crashy
At MWC earlier this month I noted that the Galaxy Tab 10.1 running Honeycomb seemed to be unusually unstable. Given that the first tablet running the OS would be shipping in a matter of weeks I just assumed that it was due to Samsung not having access to the latest build of Honeycomb. After all, Motorola is Google’s device partner this time around.
After using the Xoom for the past couple of days I can say that while the experience isn’t horrible by any means, Honeycomb isn’t anywhere near as stable as Froyo on the Atrix 4G. I’ve had many application crashes in both older Android apps and native Honeycomb apps. For a while there I couldn’t get the Android Twitter app to work at all, even after a reboot.
As I mentioned, it’s not just third party apps. The Honeycomb Browser, camera app and even Marketplace have all crashed on me over the past two days.
There’s also no microSD support in Honeycomb yet, it’ll be added via a forthcoming OS update. And there are many bugs sprinkled throughout the OS (background data automatically enables itself after a reboot even if you disable it). Things like this combined with the instability I mentioned earlier makes me feel like Honeycomb was a bit rushed, perhaps to hit the streets before one other major tablet announcement coming this year?
Facebook
Twitter
RSS
112 Comments
View All Comments
punjabiplaya - Thursday, February 24, 2011 - link
Looks good, I'm really tempted to pick one up (wifi model) if it truly is $600. Any word from Google on any updates to fix the crashing? I assume with updates (including driver optimizations) it can only get faster and there's no way that Google/Motorola isn't aware of the crashing apps.LeftSide - Thursday, February 24, 2011 - link
Don't hold your breath. I have an Epic 4g and just now got the 2.2 update. Google needs to standardize their update system. Until they do, I will not buy another Android device. Waiting for months just for an outdated update, so that you can download and use the latest apps (skype) is unacceptable.Impulses - Thursday, February 24, 2011 - link
Blame Samsung, not Google. Most HTC & Motorola devices were running 2.2 as of last September. My EVO got Froyo (2.2) in August, a mere two months after it's release (and only like there months after Froyo itself launched). People need to start doing some research and stop rewarding manufacturers that are lousy with updates, like Samsung and Sony Ericson.daveloft - Thursday, February 24, 2011 - link
I say blame the carriers. All six carriers in Canada carrying the Galaxy S device released 2.2 before any of the American carriers. This seemed to be the situation around the world as well.Impulses - Thursday, February 24, 2011 - link
Yeah at this point it's their fault, it still took Samsung twice as long to release the updates as it took other manufacturers tho. Sprint and T-mobile recently updated their Galaxy S variants to 2.2 btw, so Verizon and AT&T are slacking off the most... Verizon has half a dozen other Android options tho, until today (Atrix) AT&T had no alternative to the Captivate, besides an iPhone.ph00ny - Monday, March 7, 2011 - link
At the same time, their devices came out later those other devices. Also all the international iteration of galaxy s had froyo long before any north america based galaxy S phones. Look at HTC Aria. AT&T is the worst carrier in terms of device update due to the fact that they want to restrict the device as much as they can. Look at the issues with hsupa with atrix.BTW i have a captivate running 2.2.1 and i had froyo running since last year which was based on the international version of galaxy s
kkwst2 - Thursday, February 24, 2011 - link
Blame Canada.Milleman - Sunday, February 27, 2011 - link
Blame Terrance and Phillip!punjabiplaya - Thursday, February 24, 2011 - link
The reason I was asking is because there is no manufacturer skin. Honeycomb is unmolested by Motorola, so Google should be able to get updates to the device without Motorola having to customize their skin, then the carrier customizing that.Enormously Hatworthy - Thursday, February 24, 2011 - link
Yep, since this is the reference hardware for the platform, you'll get OTA updates directly from Google. No carriers or OEMs to screw things up.No word from google though... I suppose they don't want to draw attention to the bugs on the first day of release. I'd bet there'll be a quiet update issued sometime in the next week or two.