T-Mobile G2 (Google Ion) Review: Most Improved Award

Not only does the T-Mobile G2/HTC Magic/Google Ion phone improve on original T-Mobile G1 in just about every way, it manages to do it while cutting down significantly on the size. The only thing it doesn’t have going for it is a hardware keyboard.

Note: This isn’t technically the G2 since it hasn’t been officially released here yet, but the T-Mobile G2 will have the same hardware and the same software—the same, essentially, as the HTC Magic in Europe—so this is as close to the G2 as you’re going to get until T-Mo ships their own.

Hardware:
Let me repeat that nationally-televised ad and get this out of the way first: The screen is still fantastic. If you place the G1 and the G2 side by side, the G2 has a more blue-ish tint while the G1 is more purple. The G2 produces whiter whites than the G1. It doesn’t seem any brighter—it’s just nicer.

The generously curved shell is thicker than the iPhone, but less wide, which actually makes it feel better in the hand. It weighs 4.09 ounces compared to the G1’s 5.60 ounces, but somehow manages to feel even lighter, like half as heavy. That curved chin that caused such a nuisance when typing on the G1 is no longer a problem, due to the fact that there’s no actual slide-out hardware keyboard. Face buttons are now smaller and shiny and raised, which makes them easier to locate and press. There’s also one extra button: Search. This pops up a context-related search menu for apps like contacts, email and the browser.

It’s also improved internally. A2DP Bluetooth stereo support comes standard (it was enabled for the G1 in the 1.5 Cupcake update), and the slimmer body houses a 1340mAh battery (the G1 had a meager 1150mAh pack). A battery test is coming later, but HTC’s specs rate this as 400 minutes talk time compared to 350 for the G1.

The camera is the same 3.2-megapixel, and as of the 1.5 update, both the G1 and the G2 can both record video adequately. Not great, just adequate. Still pictures are as passable as the G1’s in sunlight, and still not great in low light.

What you’ll feel most often is the increased ROM and RAM: 512MB and 288MB, respectively. The beefed up hardware makes a noticeable difference in speed when launching and using apps.

Unfortunately, there’s still no 3.5mm headphone jack, and you still need to use an adapter if you want to use your own headphones. The microSD memory slot is also hidden underneath the back battery cover, but thankfully not underneath the battery itself.

The hardware has been improved in just about every respect, minus the fact that you no longer have a physical keyboard to bang out emails and texts quickly. But fortunately the software keyboard actually makes the loss bearable.

Software
The G2 comes with the same Android 1.5 OS that just rolled out to G1s—the same update we’ve been tracking over and over through its long development cycle—so none of this will be a huge surprise. The key difference is that you have to use the software keyboard now.

Also, instead of switching to and from landscape view when the keyboard is extended, the G2 uses the accelerometer to detect transitions. It works well, and uses a fade-out fade-in effect. It’s not a speedy transition, but it’s not too slow either. And the landscape keyboard works in all the apps and all the fields we tested.

But the keyboard itself? It falls just slightly short of the iPhone’s. Like the iPhone (and the G1), it’s got a capacitive screen. Pressing a key makes the key pop up above, so you can see what you’re typing. Google thankfully decided against the goofy other-side-of-the-keyboard solution they had before.

Although the letter recognition is accurate, and is intuitive if you’ve ever typed on an iPhone, it just needs its sensitivity cranked up another 20%. Occasionally you’ll press a key and the phone will sit there staring back at you blankly. More often than not it’s the space key that refuses to detect, makingyourwordsruntogether. This mostly happens when you type really fast, so it seems like the hardware isn’t quite fast enough to keep up with your taps.

What’s nice is that the phone displays multiple word guesses (like so many other phones) for autocomplete, which may save you key presses on longer words. And as far as we can tell from blasting out a bunch of emails and texts from it, the dictionary is quite accurate at detecting what you’re typing.

It’s still no hardware keyboard, but it’s at least as good as typing on the iPhone, with the slightly worse sensitivity (and thus slower typing speeds) being made up for by the better auto-complete.

Verdict
Although the T-Mobile G2/Google Ion/HTC Magic has still has its flaws, it’s essentially better than the G1 in every way. It’s lighter, faster, better and supposedly lasts longer on a charge. Unless you absolutely need to have a hardware keyboard for massive text entry, there’s no real reason why Android seekers shouldn’t get the G2 when it debuts on T-Mobile soon.

It’s lighter, thinner and faster than the G1

Software keyboard actually works

No more physical keyboard

Exactly the same OS as the G1, so there’s not a lot of reason to upgrade if you already own the predecessor

Hands On with Android 1.5 and the (T-Mobile?) HTC Magic

Android 1.5 home.jpgThe big surprise at the Google I/O conference in San Francisco on Wednesday? Not Google’s push for HTML 5.0, but the fact that the company gave out over 4,000 HTC Magic phones (AKA the “G2”) to every conference attendee.

In doing so, Google also allowed us to clear up some questions concerning the 1.5 “Cupcake” release and the HTC Magic, as well. But some others remain unanswered, such as the carrier (if there is one) and the price of the phone. Google gave them out to seed the Android operating system, and not the hardware.

Sascha Segan was given some hands-on time with a Cupcake-enabled Magic at the Mobile World Conference in Barcelona, where he was assured that its 3G radio absolutely does not work in North America.

Given that the phone came with a one-month SIM card from T-Mobile good for one month of unlimited voice calls and data, I can assure you that the phone does indeed place calls, and it’s a good bet that T-Mobile will in fact be supporting the phone. It’s not a sure thing, but as Sascha notes, there’s now enough data points to suspect a conspiracy.

Incidentally, Eric Chu, Google’s mobile program manager, claimed that “we expect that by the end of the year many of the major carriers around the world will be deploying Android devices”.

If you’re interested, the official specs of the HTC Magic are here. A quick recap: the phone uses a a 3.2-inch, 320×480 touchscreen, and includes GPS, 3G, and Wi-Fi.  The box also includes stereo headphones (the phone supports stereo Bluetooth, as well) as well as an audio headset. Both the headset and headphones use a miniUSB connection, however.

Google Ion hands-on and unboxing

Looks like Chris’ hatred wasn’t totally unfounded. We just got our hands on a Google Ion — which as you can tell is a spitting image of the HTC Magic — complete with 30 days’ worth of T-Mobile service on an included SIM card. It’s not a public release model, but seems fully capable. Yes, it’s got Cupcake, and while the portrait keyboard seems more cramped than the iPhone’s, we found it very comfortable to type in landscape mode. Form factor wise, this thing is as sexy as hardware gets — light, sleek, and thin. The only thing that exceeds our love for it right now is its own love for fingerprints — seriously, the entire body and screen attract them like flies to honey. Colorful similes aside, hit up the gallery below for all the pics you could ask for.

Filed under: ,

Google Ion hands-on and unboxing originally appeared on Engadget on Wed, 27 May 2009 16:41:00 EST. Please see our terms for use of feeds.

Permalink | Email this | Comments

Google I/O attendees getting free unlocked HTC Magic with T-Mobile 3G

In case you needed yet another reason to nerd out with Android developers for a couple days in scenic San Francisco, here’s a doozy: every attendee is getting hooked up with an unlocked HTC Magic in black plus 30 days of voice and 3G data service. While the carrier isn’t specified, we certainly wouldn’t be surprised if it ended up being T-Mobile, which would make this an AWS version of the phone — and a probable precursor to the presumed myTouch 3G release (or whatever they end up calling it) later this year. In the meantime, I/O attendees — and yes, that includes you, Ross Miller — we hate you out of sheer, raging envy.

Update: Confirmed — it’s a T-Mobile SIM, hence AWS 3G!

Update 2: It seems Google is calling this phone the “Ion,” but make no mistake, it’s an HTC Magic.

Filed under: ,

Google I/O attendees getting free unlocked HTC Magic with T-Mobile 3G originally appeared on Engadget on Wed, 27 May 2009 15:48:00 EST. Please see our terms for use of feeds.

Permalink | Email this | Comments

Android 2.0 “Donut” features demoed at Google I/O

We’re still trying to get used to the overwhelming joy of having Cupcake installed on our G1s, but it’s full steam ahead over at Google where engineers are already slaving away on the Donut branch that’ll eventually come to be known as Android 2.0. Demoed today at the first I/O keynote were Donut’s universal search (known simply as “Android Search”), which will let you search both online and locally on the phone through contacts, calendars, music, and any app with the proper code, and a text-to-speech API, which should allow developers to integrate Google Voice Search-style awesomeness into the apps of their choice. We also got a brief glimpse of handwriting gestures used for searching through list — the live example was drawing the letter ‘e’ and going to that specific point in a list of songs. Nothing wildly different interface-wise — yet — but we know from the initial 1.0 release that the UI’s very much subject to change, not to mention the fact that HTC and others look poised to do some serious customization of their own. Check out the gallery for shots live from the I/O keynote!

Filed under: ,

Android 2.0 “Donut” features demoed at Google I/O originally appeared on Engadget on Wed, 27 May 2009 14:41:00 EST. Please see our terms for use of feeds.

Permalink | Email this | Comments

Every Mobile Browser Should Give Up and Just Go WebKit

The ZuneHD looks like a lovely catchup to the original iPod touch—you know, before apps allowed it to be so much more—except for one thing. That damn browser. It’s not just they’re basing it off hellacious and reviled IE—it’s that it’s not WebKit-based.

There simply isn’t a better mobile browser than WebKit right now. It powers the internet in the iPhone, Android, Symbian S60 and Palm Pre, and destroyed all comers in our Battlemodo. It’s fast, it’s competent and most importantly from a development perspective, it’s open source. Meaning Microsoft could adopt it for its mobile devices with (relatively) little shame (okay, maybe a lot of shame) and it’s ready to go right now, meaning there’s no wasting time building a new engine just to attempt to play catchup to a browser that handily delivers the best mobile internet experience right now across multiple platforms.

Mozilla’s Fennec could become a contender to the throne, true, but it’s still far from final. Opera and Skyfire are interesting and good, but they’re both proprietary, meaning there’s no chance in hell they’d ever be adopted by Microsoft or RIM, much less the entire industry, as the basis for their mobile browsers. Update: BTW, Ballmer himself mentioned they might look at WebKit.

You could rail against the idea of WebKit becoming a “monopoly,” but you’d be foolish to do so: Web standards are important, and WebKit, which is again, open source, is dedicated to standards compliance and performance. A performance and compliance standard that web developers could count on in every single mobile device wouldn’t be a bad thing—far from it. It would mean even more amazing web apps, since developers would know they’d run on any mobile device, no matter what “OS” they were running underneath—the web would be the real OS.

That day is coming. I just hoped I’d see it a little sooner.

Canonical giving Ubuntu the gift of Android apps

Well, here’s a wild new spin on the Android for netbooks debate: Canonical, commercial sponsor of Ubuntu, is creating an Android execution environment that would allow Android apps to run on Ubuntu and other desktop-style Linux distros, which seems like the best of both worlds for netbooks in most cases. Canonical already has a working prototype of the execution environment, and plans on making the necessary changes to the kernel in its next version of Ubuntu to give Android all the juice it needs at the core level and will open source the project soon. Things are still early, and there’s a lot of work to do before this is going to really make the highly specialized Java-based Android apps actually usable on regular Linux — they’re currently working on granting Android access to the Ubuntu file system, for instance — but we love where this is headed.

[Thanks, Michael Y.; Image courtesy of Scott James Remnant]

Filed under: , ,

Canonical giving Ubuntu the gift of Android apps originally appeared on Engadget on Tue, 26 May 2009 15:27:00 EST. Please see our terms for use of feeds.

Read | Permalink | Email this | Comments

Nokia Ovi App Store Faces Turbulent Start

nokia-oviNokia’s Ovi store got off to a rocky start Tuesday as users faced problems accessing the store and downloading the programs.

“Shortly after launching the Ovi Store at 2 a.m. ET, we began experiencing extraordinarily high spikes of traffic that resulted in some performance issues for users accessing store.ovi.com and store.ovi.mobi,” said Eric John, head of product marketing for Nokia Ovi in a blog post. “We immediately began to address this issue by adding servers, which resulted in intermittent performance improvements.”

The store features games, applications, podcasts and videos for smartphones running Nokia’s Symbian operating system.

The problems with Ovi’s launch do not bode well for Nokia, which has been struggling to better Apple’s App Store, whose more than 46,000 titles have been downloaded more than 1 billion times since the store’s July 2008 launch. Nokia has lagged other mobile platforms such as Research In Motion’s BlackBerry and Google’s Android OS, both of which launched their own app stores months ago.

The Ovi store can be accessed by about 50 million Nokia device owners worldwide, including the soon-to-be launched N97. The store will have more than 20,000 titles at launch, said Nokia, including both free and paid apps. Customers can visit Ovi through their phone’s browser to personalize and downloads services and programs.

“Ovi is open for business and we’ve stocked the shelves with both local and global content for a broad range of Nokia devices,” said Tero Ojanperä, Executive Vice President, Nokia Services in a statement. “Ovi Store makes shopping for content and applications easy for feature phone and smartphone owners alike.”

But some Nokia fans aren’t pleased. Inability to access the Ovi store on launch isn’t the only trouble that users say they faced. Allaboutsymbian.com, a web site that follows Nokia closely, pointed out that the Ovi store does not offer a clear distinction between Java and native Symbian apps.  The performance of the store client was also slow and the store did not have much content, said the site.

Ovi store users in the U.S. will face additional challenges buying from the Ovi store. U.S. consumers can access and purchase content from the Store via unlocked devices using AT&T or T-Mobile. But those purchases will require a separate credit card transaction. Later this year. AT&T has said it will offer carrier billing, so purchases from the store become a part of the monthly service bills.

Photo: Ovi store rendering on Nokia N97 (dekuwa/Flickr)


Sunday scoops: Android on AT&T, Palm Eos details, BlackBerry Magnum, and more

Usually, Sundays don’t get too crazy at Engadget — after all, even super-nerds need to rest. That wasn’t the case yesterday, however, as we found ourselves knee-deep in a handful of seriously sweet smartphone leaks. Most of the news centered around AT&T’s upcoming devices (you know, like its first Android phones, brand new BlackBerry offerings, and… the Palm Eos), but we also saw a few new angles on the Pre. Do yourself a favor and hit all the links below — you won’t be sorry.

AT&T leaks

HTC Lancaster is a QWERTY slider with Android for AT&T
Palm Eos on track for AT&T release second half of 2009
HP triumphantly returns to AT&T with iPAQ K3 “Obsidian”
Blackberry Magnum, Onyx, Pearl 3G, and Gemini to harmonize on AT&T
HTC’s Warhawk and Fortress are AT&T’s Touch Diamond2 and Pro2
Nokia Grouper, Mako, Snapper, and Thresher rolling deep on AT&T

Pre leaks

Sprint’s Pre business launch guide leaked in its entirety
Plethora of Palm Pre interface videos emerge from leaked emulator

Filed under:

Sunday scoops: Android on AT&T, Palm Eos details, BlackBerry Magnum, and more originally appeared on Engadget on Mon, 25 May 2009 11:27:00 EST. Please see our terms for use of feeds.

Permalink | Email this | Comments

ATTs Android Phone Might Not Be a Google Phone

Engadget Mobile today published excerpts of an unusually action-packed AT&T slide deck today, showing a dozen potential new devices for the Big Blue network.

One thing to understand as you pace through the deck is that these devices may never show up on store shelves; as Engadget Mobile editor-in-chief Chris Ziegler pointed out on Twitter, “only sure things are death and taxes.” Many phones enter carrier approval processes; fewer make it out the other end.

One thing to keep an eye on is the “LE Date” field on Engadget’s slides. That’s the Lab Entry date – the date the device enters AT&T’s labrinthine carrier approval process, a black hole from which some phones never return. Some of the devices Engadget shows – most notably the “Palm Eos,” the rumored next Palm WebOS phone – haven’t even entered the lab yet.

By far the most intriguing story, though, is told on the slide for the HTC Lancaster, which might be AT&T’s first Android phone. I say “might,” because of the note on the slide: “Initial Lab Entry dates were based on Google Mobile Services (GMS) UI. AT&T Standard UI has been requested, which puts schedule in question.”