Just one person who want to know something

Angry Birds Rio for Mac os

The success of the Angry Birds game was remarkable, and has launched many versions of this game, be it a PC version, Portable PC version, Angry Birds Rio PC version, or Chrome Web browser version, this time has been also available Angry Birds Rio for Mac OS version.

Is Microsoft Cooking Something to Go Against the Google Glass ?

Everyone has heard about Google Glass, the wearable computer that can be slipped on like a pair of glasses, though it is much more than mere glasses. Undoubtedly the first of its kind, it comes with builtin navigation software that helps you with directions while driving, biking or even walking

Minebea Cool Leaf - Touch Screen Keyboard

Minebea, a Japanese multinational corporationand producer of machinery components and electronics devices, has recently launched its new flat keyboard called as Cool Leaf

Simple shortcuts Windows 7

Might have yet know, on a windows 7 a lot of shortcuts that will help us while working using windows..

Bad Piggies successful as Angry Birds

Bad Piggies, latest games Rovio, are likely to follow the success of Angry Birds and the Amazing Alex. The naughty green pigs is apparently managed to attract the gamers, at least on the iOS device users in the United States (U.S.).

Unordered List

Nokia N900 Review

Today, Nokia stands at a fascinating fork in the road. Let's consider the facts: first, and most unavoidably, the company is the largest manufacturer of cellphones in the world by a truly sobering margin. At every end of the spectrum, in every market segment, Nokia is successfully pushing phones -- from the highest of the high-end (see Vertu) to the lowest of the low (the ubiquitous 1100 series, which as far as we can tell, remains the best selling phone in history). The kind of stark dominance Nokia has built over its competition certainly isn't toppled overnight, but what might be the company's biggest asset has turned out to be its biggest problem, too: S60. In the past eight years, Nokia's bread-and-butter smartphone platform has gone from a pioneer, to a staple, to an industry senior citizen while upstarts like Google and Apple (along with a born-again Palm) have come from practically zero to hijack much of the vast mindshare Espoo once enjoyed.

Of course, mindshare doesn't pay the bills, but in a business dominated by fickle consumerism perhaps more than any other, mindshare foreshadows market share -- it's a leading indicator. Put simply, there are too many bright minds with brilliant ideas trying to get a piece of the wireless pie for even a goliath like Nokia to rest on its laurels for years on end. Yet, until just very recently, it seemed content to do just that, slipping out incremental tweaks to S60 on refined hardware while half-heartedly throwing a bone to the "the future is touch!" crowd by introducing S60 5th Edition alongside forgettable devices like the 5800 XpressMusic and N97. A victim of its own success, the company that had helped define the modern smartphone seemed either unwilling or unable to redefine it.

Not all is lost, though. As S60 has continued to pay the bills and produce modern, lustworthy devices like the E71 and E72, the open, Linux-based Maemo project has quietly been incubating in the company's labs for over four years. What began as a geeky science experiment (a "hobby" in Steve Jobs parlance) on the Nokia 770 tablet back in 2005 matured through several iterations -- even producing the first broadly-available WiMAX MID -- until it finally made the inevitable leap into smartphone territory late last year with the announcement of the N900. On the surface, a migration to Maemo seems to make sense for Nokia's long-term smartphone strategy; after all, it's years younger than S60 and its ancestry, it's visually attractive in all the ways S60 is not, and it was built with an open philosophy from the ground up, fostering a geeky, close-knit community of hackers and devs from day one. Thing is, Nokia's been absolutely emphatic with us -- Maemo's intended for handheld computers (read: MIDs) with voice capability, while S60 continues to be the choice for purebred smartphones.

So, back to that fork in the road we'd mentioned. In one direction lies that current strategy Nokia is trumpeting -- continue to refine S60 through future Symbian revisions (with the help of the Symbian Foundation) and keep pumping out pure-profit smartphones in the low to midrange while sprinkling the upper end of the market with a Maemo device here and there. In the long term, though, running two platforms threatens to dilute Nokia's resources, cloud its focus, and confuse consumers, which leads us to the other direction in the fork: break clean from Symbian, develop Maemo into a refined, powerhouse smartphone platform, and push it throughout the range.

Our goal here is to test the N900, of course, but fundamentally, that's the question we tried to keep in the backs of our minds for this review: could Maemo ultimately become the platform of Nokia's future? Let's dig in.



Hardware

Your personal take on the N900's look and feel depends almost entirely on how you approach it. As a phone, it can only be described as beastly -- but as a dedicated internet device, it's one of the smaller, sexier, and more practical devices in this tweener category to come to market. Physically, anyone coming from an N810 will immediately notice what Nokia has done here -- they've essentially traded height and width for thickness, probably a fair swap now that the latest model has made the leap from a pure MID to a smartphone with MID tendencies. After all, as a phone, it has to fit in your pocket without much drama, and shaving over 17mm off the width and 12mm off the height certainly helps Nokia meet that goal.

That said, it really can't be overstated: the N900 is thick -- thick enough to put a bulge in even the loosest pocket. Carrying it around reminded us of toting our trusty N95 back in the day, and a quick lookup confirmed that they're nearly the same thickness -- the N95's actually a couple millimeters beefier, believe it or not -- so if you're used to carrying something of that girth, it could actually be a pretty smooth transition. On the other hand, owners of most modern WinMo devices, iPhones, and even Nokia's own 5800 and N97 will have more of an adjustment period.

For better or worse, the N900 carries over some very uniquely Nokia-esque elements, notably the spring-loaded slider for toggling standby mode and the power button mounted dead center along the top edge. They're complemented by a volume rocker, 3.5mm headphone jack (doubling as a TV-out), two-stage camera button, and micro-USB port along the sides. Oh, and of course, there's a stylus tucked in the corner for actuating the resistive display. It's decent -- you won't find any metal bits or mind-blowing design here (HTC typically does a better job with that), but more importantly, it's long and comfortable enough to nearly resemble a standard writing utensil.

You'll notice in the last paragraph that we refer to the right edge of the N900 as the "top" edge. That's because the device is very much landscape-oriented -- a throwback to its Internet Tablet roots and the evolution of Maemo, which predates today's trend toward full-touch handsets that are fully functional and equally usable in any orientation. We'll talk about this a bit more in the software section, but for now, bear in mind that the controls are generally placed in a way that favors landscape use.

Tearing off the back gets at another Nokia quirk -- you really do have to tear it off, like so many Nokias before this. It doesn't slide at all, you just dig your fingernail in there, pull, and hope for the best. That's fine, we suppose -- generally speaking we're uncomfortable about doing anything to our gadgets that involves tearing at a fastened cover, but as long as it's designed to do that and it doesn't break, we're cool. Underneath you've got direct access to the microSD slot, meaning that you can technically access it without pulling the battery. Speaking of the battery, it's a BL-5J, the same 1320mAh unit employed on the 5230, 5800, and X6. Underneath you'll find the SIM tray, and those three nooks and crannies are about the only reasons you've got to be in this area of the device.

Going back to the resistive display: all things considered, it's not bad at all. It's certainly not the brightest we've seen, but we found it bright enough to use in every situation we threw at it. Interestingly, we never really noticed the phone's ambient light sensor working, but maybe that's the best-case scenario for an automatic brightness adjustment mechanism -- you should never have to think about it or let it disrupt you as you use the device, as long as the screen's bright enough to read without getting blown out in dark environments. In our earlier preview of a pre-production N900, we had issues with sensitivity that we didn't seem to have here -- in all likelihood, we owe that more to the fact that we've simply re-learned how to properly use a resistive display than any material change in the final retail unit's screen. Put simply, you'll be fine here as long as you remember to stick to your fingernail and the stylus; Maemo 5's UI elements are more or less exclusively large enough to be finger-friendly, and we found the experience a good deal more satisfying than what you get with S60 5th Edition. Unless we're using a drawing app, we'd almost always prefer being able to reliably use our fingertip to a fingernail -- capacitive still wins for ease of use -- but Nokia seems to have done the best it could here.

Sliding the N900 open reveals a full QWERTY keyboard comprising three rows of well-domed keys. Unfortunately, we've seen countless better mobile keyboard designs -- we really don't have a good explanation for why Nokia did it this way. The first problem is that the N900 only slides about 40 percent of the way open, a far cry from something like the Touch Pro2 which ends up closer to 75 or 80 percent exposed in the fully locked, tilted position. That explains, in part, why they've only gone with three rows here when four gives you considerably more layout flexibility. The next issue is that the space bar is pushed all the way over to the right side, making the learning curve unnecessarily steep; the N97 and N97 Mini are both configured the same way, so we suppose Espoo has no intention of addressing this in the short term for whatever reason. For most of our time with the phone, we found ourselves typing "M" when we meant to type a space; don't get us wrong, we're certain you can get used to it, but the question is why should you have to? We weren't terribly happy with the slider mechanism itself, either; it felt beefy enough and it'll probably survive through a typical user's abuse, but it didn't have the smooth, gliding, beautifully spring-loaded response -- nor the satisfying "click" -- that you feel on many higher-end portrait QWERTY sliders these days, including Nokia's own N97.

How about battery life? 1320mAh isn't too shabby for a device of the N900's specs, but we came away with mixed results. Moderate data and light voice use while connected to both WiFi and T-Mobile 3G consistently yielded a solid day (as in a full 24 hours) for us in the States, and we were thinking that a heavy user wouldn't have much issue making it through a day -- but a second review unit connected to T-Mobile Netherlands was consistently managing about 13 hours with middling use. Of course, the N900 charges off a standard micro USB port and BL-5Js are relatively easy to find, so you've got options if you need extra juice midway through the day.

Software

Hardware aside, it's really the N900's platform -- Maemo 5 -- that has people buzzing. There are plenty of reasons to believe that what we're looking at here is a very early incarnation of what will some day be Nokia's premier smartphone operating system (regardless of whether Symbian soldiers on in emerging markets and the lower end of the mainstream), so it behooves us all to pay close attention as this thing evolves both in Nokia's labs and in the open source community where Maemo was born and raised.

The first thing, and perhaps the most prominent thing, that a user sees regardless of device or operating system is the home screen. Coming from S60 5th Edition's restrictive grid-based widget placement, you might expect some limitations on the N900 -- but you'd be wrong. In fact, the N900 has one of the most extensible, customizable home screens of any mobile device we've ever used; you can drop widgets, bookmarks, and contacts exactly where you want them right down to the pixel, and you've got a total of four panels that loop around as you swipe (unlike Android, which stops in either direction). The system works well and does a great job of maximizing the handset's available screen real estate.

Tapping the icon in the upper left takes you to the main menu (more on that in a moment) or, if you've got any apps minimized, a display that Nokia calls the "dashboard." Basically, it's yet another interpretation of the so-called "card interface" popularized by webOS, and it works well here -- you see miniaturized views of all your open applications in one place. Minimized applications smoothly glide into the grid of cards, and tapped cards smoothly glide open to full screen again -- a testament to the power of the N900's hardware, we suspect.

Beyond the home screen, system notifications are a pretty hot topic, too, considering how well Android and webOS handle them and how poorly the iPhone does by comparison. Fortunately, Maemo 5 does a pretty great job here. New text messages, emails, and the like are briefly displayed as a yellow bubble in the upper left of the display; tapping it will take you right to the source of the notification (the new SMS, for example). If you let it go, though, the notification will persist as a "card" within the N900's multitasking dashboard, taking up the same space that a normal application would. You might think this would be confusing, but it's not for a very simple reason -- notifications appear as bright yellow squares, the same color as when they first appeared. So unless you've got an app minimized here with an entirely yellow background, you won't have any confusion.

If nothing else, Maemo 5 is pretty -- Nokia's prettiest platform ever, in fact, by a wide margin. We're sure that's due in no small part to the fact that the N900 is the first in the company's Internet Tablet line to employ a modern ARM Cortex A8-based core, making screen transitions and effects fast enough to accomplish their intended function: beautify the UI without sapping away precious seconds of the user's time. Out-of-focus screen elements are actually visually out of focus, which looks great (photographers, think "nice bokeh" here) and applications zoom and fade as you open, close, and minimize them.

"Pretty" doesn't cut it, though -- at least, not without a healthy dose of usability and functionality to go along with it, and in this regard, the N900 is much, much more raw. Indeed, Nokia has been surprisingly (and wisely) forthcoming about the fact that this is not a smartphone for the masses; it's for tweakers, hackers, geeks, nerds, and people who want as much control on their handheld device as possible -- and aren't afraid to get their hands dirty in the process. In fact, we'd go so far as to say that the N900 is a proof of concept -- a reference platform for Maemo that just happens to be sold in stores. Evidence of the N900's geeky aspirations are strewn about the platform from the X Terminal icon preloaded in the main menu, to the lack of an app store at launch (more on this shortly), to the fact that you need to connect the handset to a PC and run shell commands just to perform a hard reset.

You've got UI quirkiness to contend with, too. Maemo 5 dispenses of the left-anchored taskbar present in every version of Maemo before it, and even the status bar in the upper left (where you see time, signal strength, and so on) has a tendency to disappear rather frequently, leaving you without any bearing or sense of how to navigate between apps or elements of the platform. This is most clearly evident in the main menu, where you're presented with nothing but a full page of icons -- and it's not like the N900 has a front-mounted home or back button, so to a novice user, it's anyone's guess how to back out to the home screen or move to another app that's already running. As it turns out, the answer generally is to find a blank out-of-focus area and tap on it to go back one screen, but depending on the screen you're in, that occasionally leaves you hunting for a free area on which to tap. [You can also tap along the edge of the screen -- even if the home screen icon isn't visible -- and get back. -Ed.] Worst case, you can hit the power button up top to call up the profile menu, which will bump you out to the home screen underneath -- but it's not elegant by any stretch.

Speaking of UI quirkiness, this gets back to something we touched on earlier -- the N900's almost exclusive reliance on landscape mode. We get the argument that the 770, N800, and N810 didn't have portrait mode at all, but times have changed -- people walk and surf at the same time these days (particularly with devices like the N900 that have WWAN radios on board) and it's a lot more convenient if you can do that one-handed. Portrait mode, of course, lends itself to one-handed use. If you lump this in with Maemo 5's general usability roughness, you get the sense that the platform was rushed just a bit -- Nokia took it to 90 percent and said, "hey, this is open source, let's let the community fill in the blanks." We're guessing there are plenty of buyers that are delighted with that policy, but again, these are the kinds of things that keep Nokia from having a platinum best seller on its hands. Long term, it'll be interesting to see how close Maemo 6 comes to closing that gap and making the platform accessible to consumers at large.

About the only places the N900 officially supports portrait mode at this point are the Phone and Photos apps; you can hack it into the browser right now and we suspect the rest of the platform will get there soon enough, but we digress. In fact, you have to use the Phone app in portrait -- there aren't any apps in the device's standard load that support automatic orientation. [Turns out you can, you just need the keyboard open! -Ed.] It's a little weird, but we're thankful in at least one regard: the phone is the one piece of software here that absolutely, positively must be ready to use in portrait, particularly considering that the earpiece is at one end. As a phone, the N900's pretty basic -- again, Nokia considers this a MID with a phone bolted on, not the other way around -- but you get a finger-friendly keypad and full contact integration, which works swimmingly when paired with something like Google Sync (it totally works in the latest N900 firmware, by the way).

There is one key area where the N900's phone excels, though: Skype support. In fact, this is about the best Skype experience we've ever had on a mobile phone -- you add your account through the N900's control panel, which then keeps you connected and ready to take and place VoIP calls just as you would a GSM call. It's truly seamless and worked extraordinarily well. In fact, there was a point when we were on a GSM call and a Skype call came through on call waiting, which we could switch to and place the original caller on hold -- had we not known the caller was on Skype ahead of time, we wouldn't have been able to tell. Likewise, you can natively add contacts' Skype IDs in the address book. Ironically, the whole integration makes the N900 the closest the Internet Tablet series has ever been to not needing a GSM radio -- and yet it's the first to have one.

The N900 includes a Maemo build of Ovi Maps, a staple for most Nokia handsets sold today. Coming from Google Maps on Android and iPhone, Ovi Maps leaves a lot to be desired here. First up -- and this isn't Ovi Maps' fault, specifically -- we had an awful time with AGPS, which was totally unable to get even a rough lock without GPS line of sight. At this point, we're used to living in the world of instant location mapping that Google has brought to every platform that Google Maps has touched, and we really miss it here -- waiting for a satellite constellation is so 2005. As for the app itself, it's on par with something you might expect a couple years ago; it can map routes (and the latest firmware is supposed to speed that process substantially), but you don't have turn-by-turn navigation or cool add-ons like street view out of the box. Finally, map scrolling is one activity that's made measurably easier on a capacitive screen -- preferably with multitouch -- so no amount of user hacking or third-party development is going to fix that particular issue. On the plus side, the map renders quite quickly as you scroll (everything we tested on the N900 moved with hustle, really) and we appreciated the app's shortcuts for bouncing between common zoom levels (country, city, and so on).

Speaking of Ovi, how about the Ovi Store? We just had a little bit of time to play with the live beta of Nokia's Maemo port of the Store which went live shortly before this review, and at this point, it's a little undercooked (hence the "beta" label, we suppose). The most glaring deficiency is in the usability of the UI; rather than make an actual Ovi Store app, Nokia has elected to simply point users to a mobile-optimized portal in the browser, which ultimately leads to more scrolling and tapping than you'd like. That's not the end of the world, though; the bigger problem in the short term is the availability of actual... you know, apps. We searched for a few common phrases ("IRC," for example) and were met with zero results; in all, the store has fewer than 100 assets as of press time, and many of those are images, videos, and themes rather than actual applications. Over the years, Internet Tablet users have grown accustomed to getting their free, open wares over both official and unofficial repositories, and injecting the Ovi Store's layer of commercialism in there is a new step that might not gel at first with folks upgrading from N800s and N810s -- that said, it's an absolutely vital step to taking Maemo mainstream, so we hope Nokia finds some creative ways to attract more high-profile devs to the platform.

Now, finally, let's talk about this handset's real treat, its crown jewel: the glorious browser. The Internet Tablet line has used a fairly capable Mozilla-based browser for ages, but between the latest tweaked code and the N900's thoroughly freshened internals, it's gone to an entirely new level. Almost without fail, sites were rendered faithfully (just as you'd expect them to look in Firefox on your desktop) with fully-functional, usable Flash embeds -- and it's fast. Not only is the initial rendering fast, but scrolling around complex pages (Engadget's always a good example) was effortless; you see the typical grid pattern when you first scroll into a new area, of course, but it fills in with the correct content rapidly. To say we were blown away by the N900's raw browsing power would be an understatement -- in fact, we could realistically see carrying it in addition to another phone for browsing alone, because even in areas where it gives a little ground to the iPhone or Pre in usability, it smacks everyone down in raw power and compatibility. In our line of work where 24 / 7 access to the web is of paramount importance, having the N900 in our pocket when we were away from our laptop was a comforting insurance policy. As with Ovi Maps, the one complaint we'd lodge here is that capacitive multitouch would've been a huge win, but we adopted to the resistive setup without too much drama -- and the inclusion of a creative "swirl to zoom" gesture certainly mitigates the problem. Just don't lose the stylus!

Wrap-up

We came into this review wanting to know as much about Maemo as a platform as we did about the N900 itself; after all, the N900's just a single phone that'll be dead and forgotten from store shelves within a year. That's just reality, the hustle-and-bustle pace of the modern handset release cycle. Maemo, however, will live on -- but in what capacity? Where does it fit (or could it fit) in Nokia's grand plan?

After having dug in, we're seeing glimmers of brilliance here that give us hope. Maemo 5 isn't the polished, consumer-friendly, all-encompassing solution that Palm, Google, and Apple are all selling today, but it's fairly evident that Nokia has built itself a stable, extensible platform that can reach those levels with a little tender loving care. The company's commitment to open source and the Maemo development community is commendable -- it's something that should absolutely continue -- but going forward, we'd love to see what kinds of magical things could happen if it took development to 100 percent feature completion internally with a full round of usability testing before handing it off to the eager geeks in the field. The mere thought sends shivers down our spine.

That said, for now, Maemo officially remains an experiment; there's no greater evidence of that than the N900's half-bakedness. And hey, calling the N900 half-baked seriously isn't a knock in this case -- it's just a realistic admission of where Maemo stands today. As it has with its predecessors, Nokia seems totally comfortable with that assessment, throwing this loosely-assembled box of high-power hardware and software at anyone who dares live on the bleeding mobile edge. The company continues to insist that Symbian has a huge place in its line and will continue to do so, but long-term, we see nothing about Maemo that leads us to believe it couldn't be Nokia's single platform of the future. Even if it takes high-end hardware to run effectively, you can't deny that today's high-end is inevitably tomorrow's low-end. Everything gets cheaper, and Maemo itself -- by its very nature -- is free for Nokia to distribute.

Let's turn our attention back to the N900, though, since it's the only Maemo 5-powered device available today. Is it a keeper? As a daily workhorse smartphone for your average Jill or Joe, it's impossible to recommend the N900 at this point; it's just missing too much functionality that's waiting to be written by some enterprising CS grad students with spare time on their hands. As a second, dedicated browsing device or a geeky weekend hobby, though -- possibly an upgrade from an N810 -- the N900 is a very compelling device indeed, as long as you remember one simple rule: it's a computer with a phone, not a phone that can compute.

Additional reporting by Thomas Ricker
engadget.com
Share:

Motorola DROID review

It's hard to look at the DROID without looking at the company which brought the device to life. Motorola: for years the name has been synonymous with... well, disappointment. While the industry-stalwart made cellphones sexy with the RAZR, the days which followed have not been especially fruitful or compelling. Over the past year or so, we've seen Motorola beating its way back into the mainstream through a series of smart plays: first embracing Android as a platform, then shucking off the weight of Windows Mobile and finally bringing some desirable (and high profile) devices to market.

With the DROID, the company has perhaps created its most attractive and intriguing piece of technology yet. Forging an alliance with both Verizon and Google, Motorola has come up with a second compelling reason to count the phonemaker down, but certainly not out, while the other two giants have finally found a seemingly worthy device to position against the iPhone. So we must pose these questions: is this the phone which will catapult Android into the mainstream? Is it the device that will pull Motorola back from the brink? And -- most importantly -- is it the lynchpin Google and Verizon have needed to challenge the leader in mindshare in the smartphone market? After putting the device through its paces, we think we can give you the answers you seek -- so read on to find out!


Hardware


The DROID is an odd and beautiful device. Looking at the hardware from a purely philosophical standpoint, the ID of the phone seems staunchly defiant. Instead of taking its cues (and lines) from current contenders in the smartphone space, the DROID is all hard edges and angular slopes. The construction is a mix of plastic and metal, and the phone has a solid, expensive heft to it. Couple that weight with soft touch materials and gold highlights, and the effect is somewhere halfway between a Vertu device and the European version of the Hero -- and it's a good mix.

The basic structure of the phone is made up of two main pieces, the large, glass display up top, and the slightly longer keyboard / mainboard lower half. Above, the 3.7-inch screen dominates, almost filling the space edge-to-edge, though there are four capacitive buttons at the bottom of the display: back, menu, home, and search (which might be tricky for folks coming from other Android devices, since they've thrown the order of the buttons in the blender). The top section slides smoothly upwards to reveal the aforementioned QWERTY keyboard, though unlike other models of this ilk, it doesn't snap automatically into place; rather, it requires a bit of force to move up, then clicks firmly once settled. The keyboard is a wide (though mostly flush) affair, with minimal amount of spacing between the keys. To the right of the four row QWERTY is a 5-way rocker -- a bizarre deviation from the CLIQ's left-sided controls -- and the bottom piece has a strip which juts out from the device with a small mic hole (closed or open). It's almost like Motorola's version of the HTC chin... though tempered somewhat. Atop the phone is a 3.5mm headphone jack and a power / sleep button; along the right edge is a volume rocker, and camera button on opposite ends; the left side houses a MicroUSB port; around back the 5 megapixel camera (and flash) are revealed, along with a thin, gold, crosshatch strip that hides the DROID's speaker.


The thickness of the DROID is striking, coming in at just a hair (13.7mm vs 12.33mm) thicker than the iPhone 3GS. The body itself is actually narrower than the iPhone. While thinness is important (though typically not a deal breaker for us), the fact that the phone packs a larger, higher resolution screen and a physical keyboard in such a small frame is notable.

In all, Motorola has pulled off what seemed unimaginable for them just 12 months ago; they've made a device which is truly lustworthy, even next to the best efforts of Apple, HTC, and Palm.

Internals

Inside the DROID beats an Arm Cortex A8 CPU (a 600MHz, OMAP3430 chip downclocked to 550MHz), 256MB of RAM, and 512MB of ROM. If that CPU sounds familiar, it should -- it's similar to the chip inside the iPhone 3GS and Palm Pre. If you're wondering about performance, you can breathe a sigh of relief... kind of. Yes, there is a noticeable bump in speed when switching applications on the phone, scrolling through lists, and generally getting any basic tasks done. We did notice, however, that paging through homescreens on the DROID actually seemed somewhat stuttery; odd, considering this phone is certainly better equipped than most Android devices to handle pixel pushing. Pulling down the window shade notification area also seemed less than optimal. We don't know if this was due to the screen resolution being jacked up, or just a software quirk, but it was mildly disheartening -- especially considering that the rest of the phone's performance seemed extra snappy to us. As an aside, in a totally unscientific test of playing a 3D game (Mystique, in case you're wondering) the rendering seemed considerably smoother on the DROID than with other, older Android-based phones we've used.

Throughout our tests, we were consistently impressed with the tightness and speed of navigation on the phone. The DROID makes Android feel modern the way the iPhone 3GS and Palm Pre are -- like machines designed for a pace of life that's increasingly more Twitter and less USPS.

Display


As we mentioned, the screen on the DROID is a 3.7-inch capacitive touchscreen -- a full glass display with a WVGA resolution clocking in at a handsome 480 x 854. We found the responsiveness on the DROID to be on par (if not better) than most of its Android contemporaries; gestures and flicks registered with little to no lag. Whether that can be attributed to Moto's screen technology, Android 2.0 improvements, or just the speedy CPU inside the DROID is anyone's guess, but we certainly won't knock the phone for it. Another perk to having that big screen is seeing webpages how they're meant to be viewed (or at least closer), and browsing on the DROID is a solid experience. Those additional pixels definitely come in handy when you're looking at something graphically intensive or wordy... such as Engadget.

As you have probably heard (or guessed), there's no multitouch on this device. That's clearly an issue with Android 2.0 and choices that Google is making about user interface -- we're fairly certain there's nothing technically holding back the DROID from utilizing multitouch input, and we wouldn't be surprised to see some tweaked ROMs hit the information superhighway with the functionality onboard. Regardless, the resolution, materials, and clarity of the DROID display make it an absolute pleasure to keep your eyes on. Motorola gets a +1 for the bump in resolution, and we can only hope everyone else follows suit.

Note: Android 2.0 does support multitouch events, but the functionality isn't implemented here.

Keyboard


A physical keyboard can be a blessing or a curse, depending on just how well (or poorly) it performs. In the case of Android devices, QWERTYs have definitely been hit or miss. We think the closest case for comparison with the DROID's version would be the G1; both have shallow, clicky keys, and both force your right hand into a bit of an awkward position. On the G1, it's due to the placement of the "chin," and with the DROID, it's all down to the five-way rocker living next to the 'board itself. We're happy to report, however, that after a short adjustment period, typing on the DROID is a reasonable experience. It's not as slick or comfortable as a nice, portrait-oriented Tour or (better yet) Bold layout, though it bests the CLIQ, and holds its own against other landscape contenders like the Moment.

Visually, the keyboard is an easier read (and more aesthetically pleasing) than those other QWERTY phones too, though sometimes the keys can feel a bit cramped. Additionally, we had major issues with the auto-dimming on the DROID. If we left the screen in auto brightness mode, the constant on / off dimming of the keyboard was intolerable; eventually we had to just switch the auto dim off altogether. We also had issues with the keyboard not lighting up at all in some instances, requiring us to close and open the pad again. Not a huge deal, but annoying when you're trying to quickly tap out a message. Admittedly, we missed the CLIQ's two-stage keyboard backlighting that only enabled the second light when ALT was pressed, but it's a luxury we can do without.

As you would expect, Android 2.0 includes the onscreen keyboard as well, but there don't seem to be many improvements in this area. As a backup keyboard for quick SMSs and the like, it works, though we eventually had to replace it with the Better Keyboard application -- which we think is more usable and snappier. In comparison to the iPhone keyboard (really the high bar for virtual keys) Android continues to feel like a distant second. Still, you won't go to it that much -- the DROID's physical keyboard is solid, but it's going to take some getting used to for most people.

Camera


Google has made some pretty major changes to the camera application in Android 2.0 (including more control over white balance, focal length, flash settings, and effects), and Motorola has smartly outfitted the DROID with a 5 megapixel camera coupled with an LED flash. It sounds like a match made in heaven, right? Well, not quite.


No, no, no. Yes! Our attempts to photograph a watch in broad daylight.

While the camera certainly seems capable of taking great looking photos, getting everything to play nice isn't as easy as it should be. First off, the camera is painfully slow to focus and snap pictures -- and when it does, the results can be unpredictable. Strangely, the lens seems to be able to take pretty sharp macro photos (it's even a setting in the camera app), but it struggled with getting adjusted to close subjects, even in broad daylight. Sometimes we got lucky and cranked out a decent pic, but the process was frustrating. Furthermore, the new settings Google has added to 2.0 are contained in a hard to get to and counterintuitive menu which sits to the left of your viewing area. Trying to make changes on the fly was a hassle. If this is the best the engineers at Google can do, they need to outsource this work.


Video, on the other hand, was somewhat of a pleasant surprise. The DROID is capable of shooting at a 720 x 480 resolution, and in our tests, produced watchable -- if not totally shake-free -- video. The phone definitely fares better in this department than with stills, and we could easily see using the DROID as a stand-in for a flip cam. You can check out a little of the action in the video below (with a surprise cameo from !!!'s Nic Offer).


Speaker / earpiece


The sound on the DROID is second to none -- really. In fact, this is simply one of the best sounding devices we've ever used. Whether it's audio through the loud (but undistorted) earpiece, or a speakerphone call -- even music -- the sound which Motorola's device outputs is crystal clear. Now, obviously Verizon's reception has something to do with our in-call sound, but it's likely Moto put some thought into the aural aspect of the phone. There's not really much to say except that we were more than pleased with the audio fidelity of the DROID, and we can only hope that future phone makers (ahem, Apple) look to this device as a high water mark in this department.

Software


Besides the introduction of the phone itself, obviously 2.0 is a major update for Android. Based on the launch and hype surrounding Moto's device, we'd say it's fair to assume that Google wanted as many eyes on the achievement as possible. They definitely got it with the DROID -- but was it worth all the fuss?

The first thing you should know is that Android 2.0 isn't drastically different than 1.5 or 1.6, save for a few notable features and tweaks that have significant impact. True to form, Google hasn't gone for visual flair or wild embellishments for the sake of a few dropped jaws; most of these changes are about functionality and usability.

One of the first major changes Google has made is support for multiple Gmail or Exchange accounts, and a new universal inbox which allows you to get a look at your electronic correspondences in a single view. For BlackBerry users, this concept is old hat, but for most people with multiple accounts, it should feel like manna from heaven. We would have been slightly more stoked about the feature if it allowed you to look at both Gmail and POP / IMAP / Exchange accounts in one field. Instead, you can view your Gmail accounts separately (not in a single stream, but in one place), and your other accounts can be blended in the "Combined Inbox" view. Not exactly a perfect implementation for those of us with both Exchange and Google accounts, but certainly a solution light years beyond what previous versions of Android were offering. Another minor niggle: deleting an email now takes you to the next email in your inbox rather than bumping you back out to the list of emails, as it did in 1.5 and 1.6. We preferred the old functionality, though we imagine some will prefer the new as well.

We loved being able to keep a few of our accounts in the phone, but we ran into a weird and annoying issue when attempting to remove one of them. We were using the DROID with two Gmail accounts active, but when we tried to remove the second one we'd added (note: not the account we used for our contacts or calendars) the device informed us that we would need to factory reset the phone because that account was "required" for certain applications. Try as we might, we couldn't find a way around the problem, and we eventually did reset the device. The behavior was strange to say the least, especially since it was a barely-used, secondary account -- not a daily use address which tied into services.

As you may have heard, Facebook account integration is now built into 2.0, and there should be more of that coming, as Google has created "sync adapters" which allow third parties to plug into the contact and calendars of your phone. Mercifully, Google has figure out that you might not want your Facebook contacts in your address book, and gives you the option to turn off contact syncing (as it does with Exchange and Gmail accounts). You're also given the option to sync contacts, but keep certain sets from displaying in your contacts list; this variation is best demonstrated with Facebook integration, because it merges duplicate names and pulls the accompanying images, but doesn't clutter up your Gmail contacts with additional names. Beyond that, the pairing doesn't go tremendously deep, even though we're told Facebook had a hand in this version of the OS as well. Really, you get a widget for your homescreen which auto-updates, and that contact integration if you really want it. This is obviously just the tip of the iceberg for this kind of... er, synergy, and we expect to see lots of people taking advantage of the feature (hello, Twitter). Regardless, it's a forward thinking move that will clearly obviate the need for some of the functionality built into BLUR, and makes the DROID (and other 2.0 phones) competitive against the Pre and Pixi when it comes to social networking integration.

Speaking of contacts, Google has made some big and thoughtful changes to how contacts are handled (and used) in Android 2.0, most notably adding a "Quick Contact" menu to your contact list. The quick contact function allows you to tap on someone's name and get a context menu with jumps to the various ways you can reach out; if you're friends with someone on Facebook, you'll be given an option to message them there, along with SMS, phone, and email choices. It's a brilliant little touch that makes quickly pinging someone a cinch. Android 2.0 also improves the SMS and MMS experience by giving you the option to search your messages, and also allowing you to set a limit on how many SMSs to store before beginning to delete old threads. It's not groundbreaking stuff, but nice choices to have (finally).


You'll notice some major changes within the browser, most notably the fact that when you load up pages now, you're presented with a fully zoomed-out "overview" (much like the iPhone and Pre). If you've been griping about that weird, half-zoom that Android has relied on for so long (as we have), this is a breath of fresh air. Coupled with the DROID's massive display, it makes navigating pages roughly a million times more pleasant. The updated browser also now supports double-taps to zoom (as does Google Maps) -- making navigation a bit more natural -- though we noticed some weird column display issues on our site and others. As we mentioned before, there's still no multitouch, but this does stand in quite well for pinch zooming. While the overall browser speed still isn't as snappy as the iPhone 3GS (or even the Pre), it's a step up from previous efforts, and when you factor in little touches like auto-prediction on URL entry, it's eminently usable.

As we said, most of the alterations are under the hood -- not stuff that immediately jumps out at you, though there are some notable visual tweaks which bear mentioning. Google has added some new fades and cross-application animations into 2.0 which makes Android seem a bit more contemporary. Of course, older iterations of Android contained animations, but 2.0 seems far more polished to our eyes. Additionally, icons and elements have been updated across the board to give the OS a more modern look, sadly there is much of this UI and its applications that remain unchanged -- and not for the better.


A few of the obvious spots include the music player, which is quite frankly a mess; not only is the navigation poorly thought out, but the application is just straight-up ugly. It's not easy on the eyes, and not much fun to use either. The same goes for the phone app -- the remnants of a hastily thrown together interface are plain here, and the functionality of the phone itself gave us some issues. Often the screen was confused or unresponsive during calls, as if the hardware and software weren't communicating with each other properly. It seems obvious to us that some portions of Android need a serious, ground-up reworking... but they don't get them here. Another annoyance was the home screen -- unlike with HTC's tweaks (or even Motorola's BLUR), you only get three screens for icons and widgets. Furthermore, the DROID doesn't come equipped with even the most basic widgets you see in most new builds, like weather. The weird thing is that there is a weather app in the dock display, but no way to access the application in standard phone mode.

Additionally, some third-party (and even some first-party) software seems unable to deal with the DROID's new resolution. There are bitmaps that look upscaled and jagged, such as the attachment icon in Gmail. The game Robo Defense seemed to play slower than it did on the Hero, which was a bit of a surprise, though it has been updated to support the new resolution. None of these problems are show stoppers, but it points to a disconnect between where Google is at versus its developers. There is catch-up to be played.

Also notable (and perhaps a selling point for some) is that the DROID is a Google Experience device, which should theoretically mean that it's more likely to receive fast and frequent software updates than its skinned cousins like the CLIQ. The Google Experience is sort of the "gold standard" Android showcase for the company, so to speak, and it's in Google's best interest to keep it rock solid at all times -- and since there's no third-party skin to revalidate after every Android version is released, the update process should go a heck of a lot smoother.

One thing to keep in mind: when it comes to media syncing, you're in the same boat you were for previous versions of Android -- which means sideloading or additional desktop apps. doubleTwist has just introduced DROID compatibility, though the experience leaves much to be desired. In fact, after our tests, we'd say you're better off just mounting that SD card and dragging your content over.


Navigation


One of the biggest pieces of news (perhaps the biggest) to come out of the DROID launch was the introduction of dedicated, fully realized turn-by-turn navigation which integrates with Google Maps. The DROID makes further use of this functionality by switching into a nav mode when snapped into a dock (you can also enter the application normally, sans dock). Google has gone all out on this, providing a rich mixture of its satellite, map, traffic, and location info with text-to-speech directions. Of course, the big G takes it one step further and adds layers like parking info, ATM spots, restaurants, and gas station locations (amongst others) to the stew, making the navigation more robust than many dedicated PNDs -- which would explain that nasty drop in Garmin and TomTom stock we saw yesterday.

In our tests, the nav worked excellently for the most part, though as you can see in the video above, we did run into some minor issues on our hunt for cannoli. It's not uncommon for a GPS unit to send you the wrong way down a one way street, and maybe it was just unlucky coincidence that it happened on our first outing, but being told to turn left where you can't -- then being sent in a loop -- doesn't fill us with warm, fuzzy sensations. Still, the navigation is super intuitive and cleanly laid out, and even if there were major issues (which there really aren't), it's hard to knock a service that is completely free. We think a little more time and some longer trips will help put it in better perspective, but we like what we've seen so far.

Accessories


The DROID will get a few nifty extras when it launches, most notably a dock for setting your phone on a nightstand (or appropriate flat surface), and a car mount for using the device as a proper GPS unit. Both are notable because they use sensors to alter the DROID's functionality. The dock turns the DROID into something that looks not entirely dissimilar from Verizon's now defunct Hub, while the car mount just boots the phone into nav mode. Both are nice touches, and you'll want the car mount if you plan on taking Google up on that offer of free satnav.

Battery life


We haven't had a lot of time to put the DROID through its paces when it comes to battery life, but at a glance it seems to be holding its own against the current crop of 3G devices -- impressive considering it's only packing a 1400mAh battery behind that extremely sexy door. Paul Miller, who has been concurrently testing the phone, claims he had 24 hours of on and off usage before requiring a recharge (syncing, but no major phone calls or lots of screen time). In general, you won't be blown away by the DROID's staying power, but it doesn't deviate in any wild ways which should make you take pause. It's solid, not breathtaking, and it seems better than the CLIQ, which -- despite using the same battery -- typically manages to just barely eke through a day's worth of typical use.

Wrap-up


It will be difficult for casual observers not to see the DROID as a kind of anti-iPhone in Verizon's arsenal. Certainly the company has played up the comparison with its "DROID does" ad campaign, and it's no secret that Verizon and Apple have previously had some friction -- the V famously passed on the first-generation iPhone, after all. Of course, it's easy to draw parallels between the two devices; as with most current smartphones, they share a tremendous number of similarities, though there is plenty that set the two apart as well. And that's really kind of the point -- it's useless to look at devices like this in black and white, or to try and figure out if an Android device on Verizon is better than an Apple device on AT&T (or any other device on any other carrier, for that matter). What it ultimately comes down to when judging this kind of device is more complicated than a "yes" or "no" answer.

If you must compare the DROID to the iPhone, then know that the Android platform still has a ways to go before the experience of using the phone is as seamless as the one Apple has created -- but also know that Apple has a long way to go before its messaging, email, and customization can match what Google is offering. Both products have very distinct strengths and weaknesses.

So, is the DROID a good smartphone? Yes, the DROID is an excellent smartphone with many (if not all) of the features that a modern user would expect, and if you're a Verizon customer, there probably isn't a more action packed device on the network. That's not to say the device doesn't have its faults; the camera was unpleasant to use, the application selection feels thin in both quantity and quality (despite the claim of 10,000 options), and the phone has bits of basic, non-intuitive functionality that might chafe on some users after a while. But even still, it's hard not to recommend the DROID to potential buyers eager to do more with their devices. It's easily the best Android phone to date, and when you couple the revamped OS, Verizon's killer network, and an industrial design straight from a gadget enthusiast's fever-dream, it makes for a powerful concoction. Ultimately, the DROID won't usurp the iPhone from the public's collective mindshare or convince casual users that they must switch to Android, but it will make a lot of serious geeks seriously happy -- and that's good enough for us.

engadget.com
Share:

Onyx Review

Image Hosted by ImageShack.us

Have you read my personal review on Blackberry 9700 “Onyx”? You have? Ok then :) This time I just got a Blackberry 9700 Onyx review made by our friends at the Boy Genius Report. The difference between my 9700 Onyx review with their review is that I didn’t got the chance to try the device; but they do. Therefore, this review can complete my9700 review since they can tell the performance of the 9700 directly…

Anyway, please remember that the 9700 Onyx unit reviewed here is not the production unit. It is a pre-release unit. Therefore prepare for updates :) In this review I will shortened the BGR review and point some important parts, and if you would like to, you can pay them a visit at the link provided at end of this review

Ok so lets just start the 9700 Onyx Review, shall we?
Image Hosted by ImageShack.us

BB Bold 9700 Onyx Hardware, Design, Screen:

Yap. They have confirmed that this one is a the most beautiful Blackberry to date. At the back of the phone, there’s a faked leather textured battery cover; which has some fans (and haters). It is smaller than the tour, it has rounded corners, and has powder-coated keyboard… In addition, the Blackberry Bold 9700 Onyx has titanium chrome finish on the bezel and the high gloss black finish on the front of the device. To make it short, it is the sexiest Blackberry design to date.

As I said earlier, the default trackball was replaced with the optical one. While many recently Tour users complaint about the new optical trackball; but the performance of this new breed of optical trackball is definitely above the predecessor. The vibration of the phone is also amazingly loud and satisfactory.

About the screen, our folks at BGR found out that the Blackberry Bold 9700 Onyx has the best screen compared to other Blackberry phone to date. With resolution of 480×36; the screen is really awesome. It offers vibrant colors and appears as if they’re floating on top of the display.

BB Bold 9700 Onyx OS and Keyboard:

the pre-release Blackberry Bold 9700 Onyx came with OS 5.0.0.169… A bit different with the rumored OS 5.0 features. The one leaking over at the internet have a slight UI refresh with more blues, more gradients, updated icons and buttons and kinetic scrolling on some devices.After BGR updated the OS of the pre-release BB9700 Onyx; they finally got the updated features and sexified UI elements. We don’t know which OS will be used by the official BB 9700 Onyx yet…

The Blackberry Bold 9700 Onyx’s keyboard is a blend of the Bold and the Tour keyboards. Tour-shaped (little better) with the bounce and feel of the Bold keyboard. It’s really fantastic. Definitely not as large as the original Bold’s mammoth boat-sized chiclet pad, but it’s great. Once again, the BB Bold9700 Onyx has the best keyboard to date.

BB Bold 9700 Onyx Phone utilities

The actual ear speaker seems less recessed than previous BlackBerrys and we could hear callers loud and clear using the ear speaker. Speakerphone also worked well (as it should) with minimal distortion at maximum volume. Quite refreshingly, the device didn’t get too hot during long voice sessions and we really had no problems using the phone as a phone.

BB Bold 9700 Onyx Browser:

The BBBold 9700 Onyx’s browser has been improved with Javascript support; but still it is not as good as other mobile browser. I recommend you to try using third apps browser like Opera Mini etc. The optical trackpad makes the surfing the web experience a smooth ride…

BB Bold 9700 Onyx Battery:

Quite simply the 9700 Onyx has the longest and best battery life. It might be even better than the 8900 battery. WOW. For some rough statistics, the BlackBerry Bold with normal usage patterns lasted me around 7 hours of usage until the battery was dead. How long do you think the 9700 lasts using the exact same BlackBerry Bold battery? Try around 15 hours. We’re talking more than double with a faster CPU and using the same battery. Really remarkable and will help those on-the-go warriors.

Note: Battery life was based on OS 5.0.0.169. It’s dramatically worse in OS 5.0.0.215 which the unit is now running.
Image Hosted by ImageShack.us

Review Conclusion:

The BlackBerry 9700 combines the most-loved features that have been sprinkled about on BlackBerry phones over the last year (3G, 3.2 megapixel camera, Wi-Fi, GPS, trackpad, QWERTY keyboard, smaller size, faster CPU) and combines them into a single sexy and compact package. It is simply the best Blackberry available to date.

Every single thing about the BlackBerry 9700 screams high-end to us, and for a device that’s a part of the Bold-series (the Bold won’t go anywhere, we’ve been told), it should. It’s the best of the best to come out of Research In Motion to date and we can’t wait until everyone’s able to use one.

bestblackberry.com


Share:

Nexus One Review

The Nexus One. In the modern climate of hyped (and over-hyped) smartphone launches, Google's official entry into the phone-sales game has excelled in a department where many find difficulty: generating legitimate excitement. Of course, long before the name Nexus One or the recent bounty of pictures and details existed, the very concept of a "Google Phone" had been ingrained in the public conscience, predating even the Open Handset Alliance and Android itself; the company dabbled in the concept of direct sales through its offering of the Android Dev Phones 1 and 2 (alias Ion), but this time, it's a public retail ordeal, not a couple of one-off developer specials. The genuine-article Google Phone is finally here -- for better or worse.

The device, a Snapdragon-powered, HTC-built phone looks -- on paper, at least -- like the ultimate Android handset, combining a newly tweaked and tightened user interface with killer industrial design. A sleek, streamlined phone that can easily go toe-to-toe with the iPhone 3GSs, Pres, and Droids of the world, powered by the latest version of Android (2.1 "Flan," if you're counting), and hand-retooled by Google. But is it all it's cracked up to be? Can the Nexus One possibly live up to the hype ascribed to it? And more importantly, is the appearance of the phone the death knell for the OHA and a sign of the coming Android autocracy? In our exclusive review of the Nexus One, we'll answer all those pressing questions and more... so read on for the full scoop!

Note: The unit we have in hand is -- by all appearances -- a production model, save for the QR code imprint on the back, which is likely an employee-only Easter egg. However, Google is making its official announcement tomorrow, and there could always be differences. If anything changes with the device, or there are revelations about the marketing or sale of the phone, we'll be sure to update the review with new info.

Hardware


As we said in the intro -- and our previous hands-on write up -- the Nexus One is nothing if not handsome. From its ultra-thin body to sleek, curved edges, the phone is absolutely lustworthy. While it's unmistakably HTC, there are plenty of design cues that feel authentically Google as well -- and it's that balance which makes the phone such an intriguing piece of hardware.

Industrial design


When you first lay eyes on the Nexus One, you can almost hear someone at Google say something like, "Make us something as sexy as the iPhone, but let's not forget what got us here" -- "what got us here" being the G1, which Google worked tightly with HTC to create. Whether you love or hate the iPhone, it's hard to deny its obvious physical attractiveness, and it's clear that Google and HTC made strides to bring an Android handset into the same realm of base desirability that Apple's halo device occupies. For the most part, they've succeeded. The phone shape finds itself somewhere between the iPhone and Palm Pre -- taking the Pre's curved, stone-like shape and stretching it into something resembling a more standard touchscreen device (a la the Hero or Instinct). The body of the handset is comprised of what appears to the eye as two interlocking pieces, a main, dark gray housing (coated in a soft-touch treatment) which is intersected and wrapped by a lighter gray, smooth, almost metallic band. The overall effect is fluid, though we're not crazy about the choice of coloring -- we would have liked to see something a little more consistent as opposed to the two-tone, particularly when the choice of hues is this drab and familiar. Still, the shape and size of the phone is absolutely fantastic; even though the surface of the device houses a 3.7-inch display, the handset generally feels trimmer and more svelte than an iPhone, Hero, and certainly the Droid.

HTC has managed to get the thickness of the phone down to just 11.5mm, and it measures just 59.8mm and 119mm across and up and down -- kind of a feat when you consider the guts of this thing. In the hand it's a bit lighter than you expect -- though it's not straight-up light -- and the curved edges and slightly tapered top and bottom make for a truly comfortable phone to hold. On the glass-covered front of the device there are four "hardware" buttons (just touch-sensitive spots on the display) laid out exactly as the Droid's four hard keys: back, menu, home, and search. Clearly this is going to be something of a trend with Google-approved devices.


Unlike the Droid, the Nexus One has a trackball just below those buttons that should feel very familiar to Hero users -- the placement feels a bit awkward here, and there's literally nothing in the OS that requires it. Along the left side you've got a volume rocker, up top there's a sleep / wake / power button on one end, and a 3.5mm headphone jack on the other, and along the bottom there's a micro-USB port, a mic hole, and three gold dots that look destined for some kind of dock (which would jibe with what we've seen and heard). Around back you'll find the strangely pronounced 5 megapixel camera and accompanying LED flash, along with Google's Android mascot holding up a QR code -- a decidedly geeky Google touch that we expect won't make it to the final retail version. The layout of the phone is solid, though we would have liked a physical camera key (no biggie), and we actually had some real trouble with those four dedicated buttons. Hopefully it was just our review unit, but the target areas seemed to be too high on the row, and we found ourselves consistently accidentally tapping them while composing an email or text message, or missing them when we tapped a little too low. It wasn't a deal breaker, but it was definitely maddening -- especially considering that we don't have similar issues on the Droid.

Despite the minor niggles, HTC and Google have put together pretty damn good looking and feeling phone; it's not without faults, but they're pretty few and far between.

Internals


As you've heard, the Nexus One runs atop the much-hyped, rarely seen 1GHz Snapdragon CPU from Qualcomm (the same processor powering the HD2) -- really the highlight of this show. The phone also has 512MB of both RAM and ROM, but those hoping for new application storage options will find themselves out of luck yet again -- you're still limited to that small partition for app use. The display is an AMOLED, 480 x 800 capacitive touchscreen, and the handset also contains a light sensor, proximity sensor, and accelerometer, along with an HSPA-capable GSM radio (AWS and euro 2100MHz bands only for 3G -- sorry AT&T users), WiFi, the prerequisite AGPS chip, and a microSD slot (which comes loaded with a 4GB card, but is expandable to 32GB). By late-2009 / early-2010 standards, there's really nothing notable about the guts of this phone beyond the presence of a Snapdragon processor, and even that left something to be desired. The phone is fast, assuredly, but not so much of a leap up from the Droid that we felt it kept pace with the boost we were expecting. Scrolling lists and opening apps seemed speedy, but put simply, it's not a whole new Android experience (we'll talk more about this in the software section).

Display


The 3.7-inch display should be stunning -- and is for the most part -- but we did have some issues with it (at least on the unit we have). In terms of touch sensitivity, the display is as good or better than any Android phone we've used. While the resolution is high (480 x 800), it's missing 54 pixels that we expected given the size of the Droid's screen. It didn't bother us that much, but it's noticeable in certain apps -- Gmail for instance, where you have to scroll further in some menus than you do on the Droid. The big issue with the screen, though, is actually the color balance. We found colors on the Nexus One, particularly in the reds and oranges, to be severely blown-out and oversaturated -- a common effect with AMOLED displays like the Nexus One's. At first we thought Google had tweaked some of the Market settings because the highlight orange was so bright, but comparing images on the web across different displays, the Nexus One consistently looked brighter then it should have. Oh, and using this thing in daylight? Forget about it. Like most screens of this type, the Nexus One is a nightmare to see with any kind of bright light around, and snapping photos with it on a sunny day was like taking shots with your eyes closed.

Camera


One place where the Nexus One seems to be improving things is in the camera department. Not only has Google bumped up the speed of the camera app (which we're still not that stoked about in general), but the 5 megapixel lens and flash took sharp, detailed images with none of the HTC-related issues we've seen on other models. The focus of the lens was super speedy, and images came out looking more or less as we'd hoped. The flash felt a bit stark at times, but given its size, we didn't lose too much sleep over it. One place where Google has really made some smart decisions is within the Gallery application. Instead of the drab, flat iterations of Android past, the new version is extremely attractive and user friendly, giving you far more options than before (like a nice pan and scan slideshow) and making browsing photos a much more enjoyable experience.


Telephony / data / earpiece and speaker


As a phone, the Nexus One isn't dramatically different than most GSM devices you've probably used. In terms of earpiece quality and volume, it's certainly on par with its contemporaries, providing a loud, reasonably clean talking experience, though it doesn't touch the Droid in terms of call clarity and evenness. The loudspeaker, on the other hand, seemed extremely tinny to our ears, making for a pretty unpleasant companion for conference calls, with the midrange cutting through in a way that could be painful at times. We'd be inclined to blame that issue on the extremely thin housing here, but it's hard to say what the real culprit is. As far as connections and 3G pickup, the Nexus fared as well as our iPhone did when traveling, but -- surprise, surprise -- neither of these could touch Verizon. For instance, at JFK airport, we had no trouble placing calls on the Droid, but both the Nexus One and iPhone were completely incommunicado. When we hit the ground in Las Vegas however (you know, for a little event called CES 2010), 3G seemed to function as we might have hoped. In a few cases, T-Mobile did seem to be hanging onto a signal a bit better than AT&T was, and in a browser test between the two, even though the iPhone ended up with a slightly faster load time, the Nexus One pulled down initial content considerably quicker. In all, we averaged download speeds of around 559Kbps on the phone -- about where we expected things to be.

Software



Now, the big story with the Nexus One (besides how it's being sold -- we'll get to that in a minute) has been the rumored alterations or updates Google has made with Android 2.1. There's been talk that this is somehow the "real Android," a suggestion that other, earlier versions weren't true to Google's mold. There's been talk that the Nexus One is worth the hype, and will blow people away when they see what this version of Android can do. Mostly, there's been a lot of talk. So, what's really the story here?

Well the real story is that Android 2.1 is in no way dramatically different than the iteration of the OS which is currently running on the Motorola Droid (2.0.1). In fact, there is so little that's different in the software here, we were actually surprised. Of the notable changes, many are cosmetic -- if there are major underlying differences between this OS and the one on the Droid, we can't see what they are. Still, there ARE changes, so here's a peek at just what Google has cooked up for the new phone.

Firstly, the place where Google really seems to have put a lot of its energies has been in the look and feel of homescreen navigation. Obviously the feedback the company has gotten is shaping the next steps on Android's path, and as anyone who has used Android will tell you, the homescreen situation was kind of a mess. In 2.1, Google has jettisoned key chunks of the established Android paradigm for how to get around its device. Most noticeably, the company has killed the sliding drawer which used to house all of your application icons -- the tab is replaced with a handy "home" icon which zooms in your icons over top of whatever homescreen you're on. You can scroll up and down through those icons, which is now accompanied by a cute 3D animation where the items slide over the top and bottom edge, like wrapping a piece of paper around the side of a table. It's nice, but not necessarily functional in any way. Google has also added a little bounce to the menu, in keeping with its contemporaries' love of physics.


Additionally Google has expanded the number of homescreens accessible from three to five (following a precedent set by skins like Sense and BLUR), adding a combo of webOS and iPhone style dots to help you keep track of where you're situated. If you long press on those dots, you get a kind of "card" view of all your homescreens which you can use for quick jumps. All of the homescreen improvements are just that -- improvements -- and it's nice to see Google thinking about a user's first impression of this device. Not only do these additions bolster the look and feel of the UI, but they're actually sensible and helpful solutions to problems which Google had heretofore approached in an obtuse way.

Elsewhere, there are nips and tucks that are welcome, such as the improved Gallery application we mentioned previously, which seems to be one of the few areas actually tapping into the Snapdragon's horsepower. But Google stumbles as well; the dated and always-underwhelming music player has undergone almost zero change, and the soft keyboard -- while better than previous models -- can still be inaccurate. Of course, Google wants to provide another option for text input that we haven't seen before the Nexus One. Now included when the keyboard pops up is an option to use the company's speech-to-text engine, which will (attempt) to translate your words into onscreen text. Our experiments with the technology were marginally successful, but we don't see this being a big part of our communications game until the audio recognition gets a little more robust. It might work for an occasional SMS where use of the Queen's English isn't a priority.


One other thing. As we mentioned in our impressions post, there's no multitouch on the Nexus One. Now, we can live with a browser or Google Maps with no pinch-to-zoom, but not having a hardware keyboard hamstrings this device in other ways. For instance, gaming on the phone is pretty much abysmal save for a few accelerometer-based titles. And some of our favorite software, such as Nesoid (an NES emulator) is a total dead. For a phone which uses touch input as its main vehicle for navigation, relegating that experience to a single digit is really kind of bogus. There were plenty of times when using the Nexus One (and this does happen with other Android devices as well, but it's pronounced here) where we felt not just bummed that you could only use one point of contact, but actually a little angry. Why won't Google open this up? Why have they kept what has become a normal and quite useful manner of interaction away from their devices? Only Eric Schmidt knows for sure. What it made us realize, however, is that an Android phone is really better off with a keyboard, and we were longing to get back to the Droid a number of times while using this device.

Battery life

We haven't had a lot of time to spend with the phone just yet (you may have heard, it's been a bit hard to get ahold of), but from what we've seen, the battery performs admirably. Thus far we haven't had any major shockers when it came to power drain, and that AMOLED screen seems to go easy on things even when cranked up to a pretty stark setting. That said, we did see a dip when taking long calls, which indicates that this might not be a charge-free device day to day if you've got some serious gossip to dish. We're going to be running some more tests this week to see how the phone performs over a lengthier stretch of time, and we'll let you guys know how it fares.

Pricing and availability


As of this writing, all we have on the Nexus One in terms of pricing and sales plans comes to us in the form of leaked documents and tipster screenshots. That said, if everything falls into line the way we think it should, the sale of the phone won't be the kind of barnstorming industry shakeup that many predicted -- rather, it's business as usual, with one small difference. While the phone is manufactured by HTC and destined for use on T-Mobile's network, Google will be the one doing the selling of the device. By all appearances, the company will have a new phone portal where buyers can pick between an unsubsidized, unlocked Nexus One for $529.99, or sign up for a two-year agreement with T-Mobile and purchase the phone for $179.99. This shouldn't seem strange or exciting to anyone who's recently bought a smartphone -- it's pretty much the lay of the land right now. Previous to the documents we'd seen, the hope was that Google had found some ingenious ad-supported way to get this phone into consumer's hands for a low, seemingly subsidized price but without the shackles of a contract or specific carrier -- but those plans seem have been either invented, or somehow dashed.

Wrap-up


Never mind the Nexus One itself for a moment -- there's a bigger picture here, and it might spell a fundamental change for the direction of Android as a platform. Whereas Google had originally positioned itself as a sort of patron saint for Android -- sending it off into the cold world to be nourished and advanced in a totally transparent way by the widely-supported Open Handset Alliance -- it has instead taken a deeply active role and has elected to maintain some semblance of secrecy as it moves from pastry-themed version to version. In general, that approach isn't necessarily a bad thing for device variety, functionality, and availability, but the way Android's evolution in particular has gone down certainly seems like a bait-and-switch from an outsider's view. Take Motorola and Verizon, for example: what had seemed like a deep, tight partnership literally just weeks ago with the announcement of Eclair and the selection of the Droid / Milestone as 2.0's launch platform has taken a distant back seat just as quickly as it rose to the top. In a word, Google is plunging head-first into the dangerous game Microsoft has adamantly sought to avoid all these years on WinMo: competing head-to-head with its valued (well, supposedly valued) partners. Whether Android risks losing support over manufacturers and carriers being treated like pieces of meat remains to be seen, but realistically, Motorola (which has very publicly gone all-in with Mountain View over the past year) and others are likely to grin and bear it as long as the platform pays the bills -- no matter how awkward competing with the company that writes your kernel and huge swaths of your shell might be.

Industry politics aside, though, the Nexus One is at its core just another Android smartphone. It's a particularly good one, don't get us wrong -- certainly up there with the best of its breed -- but it's not in any way the Earth-shattering, paradigm-skewing device the media and community cheerleaders have built it up to be. It's a good Android phone, but not the last word -- in fact, if we had to choose between this phone or the Droid right now, we would lean towards the latter. Of course, if Google's goal is to spread Android more wide than deep, maybe this is precisely the right phone at the right time: class-leading processor, vibrant display, sexy shell, and just a sprinkling of geekiness that only Google could pull off this effortlessly.

Then again, we suspect Motorola, Samsung, Verizon, and countless other partners might disagree.

engadget.com
Share:

Support

Definition List