We've seen leaked pictures of the Motorola Opus One, and now we know it as the Motorola i1. Wish we could give you more about the specs, other then it's an iDEN device (get the name now?) running on Android 1.5 (is this a bad joke?) and a 3-megapixal camera, and will most likely have Motoblur.
For those not familiar with Motoblur, it's Motorola bringing all your social Web sites like Facebook, Twitter, Myspace and the like straight to your home screen, so you don't have to go through each one individually to update your every move. [via Engadget]
We've had discussion of the ESE53 build of the Android 2.1 update for the Motorola Droid (yeah, say all that 10 times fast) for a number of days, but now there's video to go along with all that talk. And the buzz is that live wallpapers are included and run just fine. There are only three homescreens, though that's easily fixed, isn't it. Peep the whole video after the break. [Droid-Life via AndroidCentral Forums]
Twitter clients are nearly as ubiquitous as Android phones these days. There's Seesmic, Twidroid, Tweetcaster, HTC's Peep, HootSuite, Touiteur, Twicca and Swift, to name but a scant few. And then there's always the mobile Web site. And it seems that new clients are being introduced every day.
And so, we want to hear from you. Head on into the forums and tell us what you use for your daily Twitter client. We'll pick one lucky winner at random to win a free 16-gigabyte MicroSD card from the AndroidCentral Store. We'll take entries through Wednesday, and announce your two Twitter client pics later this week. Good luck!
Update: Good news, everyone. Because of the overwhelming response, we're upping the prizes. We're now giving away a 16GB microSD card and two 8GB cards. Posts count through Wednesday.
The Backflip -- which sports the Motoblur social networking interface -- has a unique fold-over keyboard and 5-megapixel camera, along with a 3.1-inch touchscreen (at 320x480 pixels), comes with 512MB of storage memory and 256MB of RAM, and its microSD card can handle up to 32GB.
The Backflip is available starting today for $99 along with the usual 2-year contract and $100 "promotion card" rebate, or you can buy it outright for $349.99 (which isn't a bad price, actually). [AT&T]
Hey everybody! Jerry here again for our weekly get-together. I hope everyone survived another crazy week of things like data outages and Eris leaks. And Droid users, don't fret – your time is coming soon, I'll bet.
This week let's talk about apps! Everyone loves apps, and they're one of the biggest draws of the Android platform. The Android Market is growing by leaps and bounds, and I for one am loving it. But there's a whole internet full of stuff beyond the Market, and we're gonna explore it.
The HTC Legend -- you'll remember it from our hands-on at Mobile World Congress last month -- at this point remains a European-only phone, and as such it's starting to get into European journalists' hands for review. Don't worry, we fully expect to see a version of it in the States sooner rather than later, and you can already get a taste of the new Sense UI, if you want. In the meantime, here are a few unboxings, if you're into that sort of thing:
So CNET UK had a Nexus One whose screen mysteriously cracked and turned purple while merely charging on a desk. At Google's urging, they handed it over to HTC for further study. The results:
"Putting a phone in a tight pair of jeans and sitting down would usually cause the kind of damage," suggested our support guy. He agreed that it's possible that a small crack could spread over time, like a ding in a car window.
Words to live by, we suppose. But the question remains: What happened to Crave's Nexus One screen? Maybe it cracked under the weight of not knowing what's wrong with its multitouch? (Self-flagellation zinger there, folks.) [Crave.CNet.co.uk]
Did you hear that Apple is suing the pants off of HTC?Of course you did. And though the lawsuit will likely all be settled with millions of dollars exchanging hands and business will go on as usual...what if it doesn't? What if Apple has its way with HTC Android phones? Wired examines this potential horror story. The phone and Android UI above is what we'd likely be getting. To quote:
Picture an HTC Google phone whose desktop shows a grid of icons with gaps. Arrows on the screen help you navigate your windows. A physical unlock button on the phone gets you past the lock screen. Battery life could potentially be poor in sleep mode, which could be addressed with a free battery extender — or even better, a hand-crank charger — as shown in the illustration above.
Eek. Obviously, some of the items have been dramatized for effect but boy, that would be a clunker of a phone to use. Let's hope we never go down that path. Hit the link for full descriptions of what features would have to be replaced and with what.
The Swype keyboard has been incredibly popular, despite not being openly (or legally, for that matter) available for download for Android. But Swype just opened up a beta program for our beloved platform. Here's what you need to know:
Been holding your breath waiting for the "I am T-Pain" auto-tune app to come to Android? Ain't gonna hAAAaaa-pen. At least right now. In an interview with All Things D's Peter Kafka, Smule co-founder and CEO Jeff Smith lays out his reasons for avoiding Android, including having to contend with multiple versions of the operating system.
"Android is not in the plans for Smule," he said. "We just don't see an opportunity for us to make money short-term on Android."
"We love what Google's doing, we're really excited about it ... and people are using their products. The challenges with Android are -- the retail distrubution is not clear for us, and we don't see how we could monetize through their current distribution. It's not one platform. ... So, from the developer standpoint, it's expensive to get into Android."
Hard to blame the man for wanting to make a living. So, no official T-Pain auto-tune on Android. And you know what, we're OK with that.) Video of the interview after the break. [All Things D]
Update: OK, OK. I get it. I've been learned a thing or three over this one. So have at me in the comments, call me a bad person, throw things at my dog, whatever. I only hope one day we'll wake up an our long national multitouch nightmare will be over. :P
Let the debate continue! Earlier this week we saw a pretty damning video that illustrated how multitouch on the Motorola Droid was "better" than on the Nexus One, or that the Nexus One's multitouch is "broken." That was shown with and app called Multitouch Visible Test.
Here's our own unscientific test using a different app, called MultiTouch Visualizer. While it actually runs a little more smoothly on the Droid, it doesn't have nearly the same problem tracking multiple points on the Nexus One that Multitouch Visible Test had.
So what do we take away from this, aside from finding a bug in an app? So long as multitouch works well in the app in which you need it, we wouldn't worry too much. But you don't have to take our word for it. You can download Multitouch Visable Test and MultiTouch Visualizer from the Android Market and try it yourself.
Our pals at JK on the Run put up an excellent piece today breaking down Google's supposed (or blatant, depending on who you ask) favoritism regarding the latest OS versions, features, etc. Basically it boils down to this: Has Google put some of the latest features (i.e. Buzz, Google Maps Navigation) on the most current hardware with the newest builds? Absolutely. And why wouldn't you show off your best software on the best hardware? Writes Kevin C. Tofel:
I ask myself: if I were Google and I wanted to rock out a new app and build the biggest buzz, I’d get it on the heartiest hardware first so it really shines from a performance perspective. I’d also pair it with hardware designed to show it off — the Droid car dock morphs what’s essentially a software product into a look-alike, standalone GPS device.
And as for your older Android phone not yet rocking Version 2.0 or 2.1, remember that unless it's the Nexus One (or the G1, we suppose), updating devices such as the Motorola Cliq -- or the Cliq XT ... or the Devour -- is going to some doing, as Motoroblur is only on Android 1.6 at current. And that's not Google's fault.
Who chose to put Android 1.6 on this new Android device? It certainly wasn’t Google. If you have to “blame” someone, choose either Motorola who made the phone or Verizon who decided to sell the phone. All Google does for this phone is provide versions of it’s mobile platform to the phone maker.
Those are all points we've argued before, and we bet we'll be arguing them for some time to come. Is the platform fractured? Yep. But that's not Google's fault, just as it wasn't Microsoft's fault when Windows Mobile (RIP) saw itself running in various versions on a number of devices. [JK on the Run]
Portions of this page are modifications based on work created and shared by the Android Open Source Project
and used according to terms described in the Creative Commons 2.5 Attribution License. AndroidCentral is an independent site
that is not affiliated with or endorsed by Google.