HTCDream(plusGoogleAndroid)review|HTC,Android


7th April 2009 Author: Kinny Cheng - - Views:

 


HTC Dream
Our review set:
- HTC Dream
- Colour variant: ‘Black’ and ‘White’
- Software version: 1.1
- Baseband version: 62.33.20.08U_1.22.14.11
- Kernel version: 2.6.25-01845-g85d4f0d android-build@apa27 #27
- Build number: dream_stg-user 1.1 STG-RC8 128394
- RAM/Flash size: 192MB / 256MB
- Processor: Qualcomm MSM7201A-528MHz
- SAR when used at the ear (ICNIRP): 1.34 W/kg


Overview
Ever since OEM device maker HTC decided to go retail with the same branding, the landscape for Windows Mobile (WM) hardware took a turn for the good - specifically, with the more-interesting designs that we are now seeing. Some may not agree completely with this - but I believe the Touch Diamond was the model that truly made the mark, and turned over a new page in WM history.

Ever since search giant Google announced their intention on entering the mobile market with their own open platform, named ‘Android’, people like us have been patiently waiting for the arrival of the very first commercial device to host it - not only to see how it stands up amongst the competition, but (more importantly) to experience what the platform has on offer in terms of usability and functionality.

Renowned Windows Mobile based device maker, HTC, was the company to come up with this very device, designated as the ‘Dream’. But in most markets, it is known as the G1 - or, more specifically, the T-Mobile G1 (due to its exclusive availability in selected countries where the mobile network operator has a footing).

Not only is the Dream the world’s first “Google phone”, but it’s also HTC’s first product to break away from their Windows-only smartphone portfolio. This is obviously a great thing for HTC, where this will offer them an alternate market of products AND users. Although expectations are high for Android as a platform (hint: Google), trying to create and offer a good product shouldn’t be all that difficult - especially when you’re going head-to-head with Windows Mobile based products.

In a broader scope, the HTC Dream won’t be the typical smartphone product to review. Instead, it’s a product that will have wider ramifications not only to HTC, but the entirety of the smartphone market. Again, because it’s the first commercial product to land, it won’t just simply bring a new level of smartphone usability for its users - but also set a precedent for future Android-based device designs to come.

The Android platform will probably be similarly as disruptive as the Apple iPhone - that is, once it starts to makes its numbers throughout the different world markets. However, this will solely depend on how Google continues to develop its smartphone platform - something that I truly have high hopes for, especially after my somewhat-short stint with the Dream.

For this particular review, I will be looking closely into both the actual device and the platform, as both of these aspects will probably raise similar levels of interest - depending on the aspect that interests you, the reader, most. Think of this as a review for the HTC Dream and Android 1.0/1.1... how’s that?

(Throughout this review, I will be referring to the device as the ‘HTC Dream’).


Design

[ device category: smartphone ]
[ form factor: PDA monoblock, with slide-out thumb QWERTY keyboard ]
[ keypad: virtual touchscreen (capacitive) | QWERTY keyboard ]


HTC Dream - designIt is only human nature, when it comes to appreciating art (or, in this case, a product design) that be can become overly subjective with our feelings. Quantification of this, when asked to a random audience, usually leads to either a majority result or one that’s clearly bipolar.

When asked about the “looks” of the HTC Dream, most individuals (being their first time seeing it in the flesh) responded with a tone of negativity. On justifying such feelings, some found it hard to put a finger on the reason for their distaste - while others just didn’t buy its looks one bit, saying that it’s just “ugly”.

Agreed that the Dream is not a typical-looking smartphone design. Being rectangular in shape, but curved-up on one end of it - and the rather-odd display slider mechanism, which reveals the thumb-based keyboard when fully opened. Just these two physical design elements may have been too much for the average phone user to handle all at once.

And to be honest, my first encounter with the Dream wasn’t the most pleasant one either. Time wasn’t on my side on this occasion, where I had only so many minutes of playing time with the device. But at that very moment, my very first reactions were similar to those of many others: weird design; weird (but solid) slider mechanism; a barely-passable UI experience.

(Thinking back to that moment, it must have been the “black” colour of the device that put me off - a colour that, I personally think (to this very day), just doesn’t go well with the Dream at all!)

But upon further evaluation, with time not being as critical in comparison, the reasons behind the Dream’s physical design and aesthetics became clear with its progressive use. One needs to be in the driver’s seat to appreciate what’s truly being offered - and I’ll step through my experiences right here:



{ Form factor }
HTC chose to go minimalist with the Dream, where the use of a 3.2-inch capacitive touch screen (identical in technology to that of the iPhone’s) has helped greatly in making this a possibility. Four-plus-one navigational-based hard buttons on the front side, along with a very usable mini-trackball for panning and on-screen selection, was all that was needed. Any more cluttering would certainly have defeated the purpose of such a design, one that I have come to liking very much.

Opening up and revealing the keyboard doesn’t change a thing. A QWERTY keyboard there may be, but it’s how this is physically (or aesthetically) presented that matters - and HTC has done a fantastic job in creating an input panel that not only looks fitting, but also highly usable through almost any means (more on this later).

Currently (at the time of this review), the Dream is available in three different colours: Black, Bronze, and White. My preference is for the latter - being the colour that changed (or probably more like “inspired”) my feeling towards this device.

{ The “curvatured” design }
As “ugly” as it may have made the Dream look, it is only when you begin working the device that you realise the advantage of this physical design oddity.

When used in an upright orientation, the curved-up area makes the flush hard buttons and mini-trackball more easily accessible to the thumb, when used in conjunction with the Dream’s glass touch display. And remembering that capacitive technology only requires the slightest touch to register the user’s command or gesture, other elements belonging to the same interface design must also work in relatively the same manner - hence, such a design.

Turn it 90-degrees anti-clockwise, slide up the display, and you’ll find your middle finger (plus a small part of your palm below it) sitting very comfortably beneath the same curved-up area, and providing a very solid grip too! It also allows for the right thumb to have almost-perfect access to the entire right half of the QWERTY-based keyboard, which may not be possible if the Dream had a standard monoblock (or candy bar) form factor.

And even in landscape orientation, the mini-trackball and nav-based hard buttons are still very usable, accessible without any need of repositioning the device in the hand whatsoever - which is how it’s supposed to be, unlike some device designs.

{ Navigation }
Since the release of the Touch Diamond, HTC has scaled back on the use of hard buttons to help with improving overall device usability. And on the Dream, albeit a Android-based device, it utilises the same four keys - but their uses are by far more practical:

“Answer/call” key:
  • answers or picks up an incoming call;
  • brings up the “Call log” tab of the ‘Dialer’ application (at other times).

“End call” key:
  • ends an active call;
  • sleeps the display (at other times);
  • brings up the ‘phone options’ dialog to disable/enable slient mode or to turn off the device (when the device is on and button is held down for >2 seconds);
  • turns on the device (when the device is off and button is held down for >2 seconds).

“Home” key:
  • opens (or returns) to the middle (second) Home screen;
  • brings up a quick-access dialog with the last six opened applications (when button is held down for >2 seconds).

“Back” key:
  • returns to the main phone menu, parent menu (when a dialog is active), or previous screen (when pressed inside an application);
  • behaves as the “back” button in the ‘Browser’ application.

And then, there is the ‘menu’ button. No, it’s not used to go back to the main menu - but, instead, brings up an on-screen menu of respective commands for the currently-screened application, feature or function. To put it another way, it’s like an “options” context menu, but a far-more-intuitive one that’s more direct to use.

Finally, the mini-trackball offers a very good level of traction or resistance, is non-slip, and works extraordinarily well with either thumb or individual fingers. It can be slightly over-sensitive at times, depending on the job at hand. But it beats using a 5-way D-pad controller, which wouldn’t work on such a device design.

(More on the usability aspects of this in the following section).

{ The thumb keyboard }
By just looking at it, I would’ve never thought it would be very usable at all. The smaller-sized buttons for the individual keys, their minimal travel distance, and somewhat-flat design - all of which seem to defy the positive ergonomics of a typical thumb-based QWERTY keyboard design.

Or do they?

Again, much credit goes to the designers at HTC for coming up with a perfectly-formulated
input interface. Combining those three design variables I just mentioned with a fine-tuned tactility for the entire keyboard tile, along with the unique curvature design of the Dream, the resulting usage experience was one of the best for any QWERTY-enabled smartphone device I’ve ever used. Absolutely brilliant!

{ Physical reliability }
Surprisingly good, actually. Initially, I had concerns about the display slider mechanism. But after my extensive episode with the Dream, my worries can certainly be put to rest.

Overall, the Dream’s build quality seems extremely sound. So be rest assured that it’s as physically reliable as any other HTC product out there...


Usability

[ hardware: Qualcomm MSM7201A @ 528MHz | 256MB ROM + 192MB RAM ]
[ platform & user interface: Google Android 1.0/1.1 ]
[ navigation: Capacitive touchscreen, mini-trackball, pre-defined hard buttons ]
[ display: TFT LCD | 320 x 480 px (HVGA) @ 65,536 colours | 3.2-inch viewable diagonal ]


Sharing virtually the same “hardware” specs as those of the Touch Diamond, the Dream’s performance - as a smartphone of similar calibre - was, by far, more impressive and outstanding than any Windows Mobile (WM) enabled device currently on the market. And this includes HTC’s WM-based products too - quality, performance products that are being held back by the software platform which operates them.

Anyway, let’s move onto more topical commentary...

For those that may not be aware, Android is a brand new smartphone platform created by Google, and competes in the same space for patronage as Apple’s iPhone, Nokia’s Series 60 (aka ‘S60’), Microsoft’s Windows Mobile (of course), and _maybe_ RIM’s BlackBerry. Currently, S60- and WM-based devices dominate this space - but I can foresee a probable change in the status quo in the not-too-distant future.

The release of the iPhone platform by Apple has made a distinct change in the smartphone landscape - one that brings a deservingly new level of innovation to such mobile telephony devices, and something I’ve been looking forward to for quite some time. Unfortunately, in the world that we live in, it usually requires a new player or market entrant to kick-start a change in routine - and what Google has done with Android is the reinforcement of Apple’s position and direction in the evolvement of this product market.

In a way, both the Android and iPhone platforms share many similarities. But there is (and will be) an obvious difference when it comes to the type of device designs that Google would like to get into. The HTC Dream, albeit the very first Android-enabled device, shows what kind of potential the platform truly has for both end users and the makers of the actual hardware.



{ First-time use }
On booting up the Dream for the very first time, it will step through an introductory about the Android platform, and how it integrates with the many Google online-based services - such as Gmail’s email and contacts, and Google Calendar. In my case, being an existing user of these services, I simply needed to enter my user name and password details to get the ball rolling - while new users can sign up for an account straight away.

Unlike the iPhone, the Dream offers no virtual keyboard for alphanumeric input. So sliding aside the display and using the physical one is the only way - which, at this stage, introduces its user to the flexibility and very ergonomically-sound of its design.

If, by the off-chance, that the proper data settings aren’t available out-of-the-box, which can cause problems with setting up the Google services on the Dream, it is possible to input these manually by bringing up the hidden pop-up menu (by pressing the ‘Menu’ button), and tapping the “APN Settings” on-screen button. A list of the available data network settings will be listed, allowing for immediate selection. If the one needed isn’t there, then a manual entry can be created right away.

Upon verification of the Google account details, Android will automatically begin synchronising the respective Gmail account’s inbox and contacts information, and calendar entries from Google Calendar. Users can choose to disable certain sync services, or even the auto-sync option, from within the ‘Settings’ app under “Data synchronisation”. Note that a device can only be synchronised with one Google account login.

Android can also work with no Google-based services, making the Dream function simply as a smartphone by itself. An option is available to skip this part of the setup, taking the user directly to the ‘Home’ screen to begin his or her journey of discovery.

Interestingly, the type of (written) grammar used throughout the introductory was typical Google - conversation-like, with a tone that’s easy to digest for anyone spending their first minutes with the Android-enabled device. Such a style of “connecting” with its user, which brings a more-casual user experience for the UI, is virtually unfounded on other devices of such.

{ General browsing }
Getting around in Android is extremely straight-forward - that is, after you’ve become acquainted with a few of the basics...
  • Basic navigation: On-screen finger (or thumb) action by taps and directional swipes, or browsing and selection via the mini-trackball - take your pick! But under most usage scenarios, both methods will somehow complement each other, which is the beauty of using the Dream!
  • Screen sleep and lock: By default, the Dream’s display will time out after a pre-defined period, and will concurrently activate the keyguard. To bring the device out of standby, simply press any of the four hard buttons and followed by the ‘Menu’ button (or press the ‘Menu’ button twice - but not too fast!)
  • The ‘MENU’ button: Shows a pop-up of prominent functions for the current application or phone feature, with these being presented as on-screen virtual buttons. Irrespective of orientation, this pop-up will appear in the bottom area of a given display, making these commands extremely accessible.
  • Feature-specific functions - by just “holding down”: Sometimes (or maybe at most times), either keeping your finger/thumb held down on a selection on the display, or even the mini-trackball, this will bring up a contextual menu with access to various functions. This works in tandem with the pop-up menu, which displays those more “primary” functions of the current application or phone feature.
  • Status bar: Prominently occupying the display’s uppermost rows of pixels, this white strip displays the device’s vitals (e.g. current time, signal level, battery charge remaining, data indicator/s) at all times. It is also used to: indicate missed calls and received messages; missed calls; and provide notification messages for other on-board applications.
  • Home screen: In most cases, this is where everything begins. Customisable in a variety of ways, it can host a range of one-touch shortcuts to favourite apps, contacts, Internet web pages, pre-defined music playlists, and even show emails categorised via an individual Gmail “label”.
  • Applications drawer: Represented as a virtual tab in home screen view, this is where Android houses all native and installed applications. Opens or closes by simply tapping or dragging the tab, whichever action works best and feels most natural.

{ The home screen, in detail }
Anyway, I think I’ve made my case very clear for this particular aspect - one that I believe to be a real deal-breaker if its existence is considered vitally important.

The ‘Home’ screen is the starting point, and can be returned to by simply pressing the respective hard button. But what the user sees as the home screen is, in fact, only one of two other adjoining “screens” or panes. On the Dream, the entire Android ‘Home’ screen spans three panes, and three panes only (this means that panes cannot be added or removed).

Each of these can house up to 16 different application “quick access” icons or ‘shortcuts’, or different ‘widgets’ (dependent on the available space on-screen at the time). To set-up and customise these, either hold down onto an empty space on the screen or select the ‘Add’ option from the pop-up menu. And deleting these is just a matter of holding down on the item until the device makes a short vibration, and dragging that to the drawer tab below (which turns into a “bin” in this mode of operation).


Application “quick access” icons:
These are actually shortcuts to on-board applications, which can also be created by dragging the icon out from the apps drawer - indicated by a virtual grey-coloured tab located just above the ‘MENU’ hard key.

‘Shortcuts’:
These are specific “shortcuts” that you can place anywhere on the three different ‘home’ screen panes, and are designed to provide the maximum (but customisable) level of convenience for users of the device.

Application-specific shortcuts include: “bookmarks” for launching a URL via the built-in web browser; “contacts” for showing an individual address book (name) entry allowing for almost-instant calling or messaging; “Gmail labels” for the showing of all emails marked with a specific categorisation; and the immediate launching of a predefined list of songs through “music playlists”. A “folders” shortcut is also available, and can be used to group those other home screen icons together (useful when you want to make a speed dial entry, or group commonly-used Gmail labels or music playlists together, for example).

The possibilities in home screen customisation is endless! But what’s most important is the broad flexibility available in doing so.

Widgets:
These mini-apps can run on any of the home screens on the condition there is sufficient screen real estate for them to be allocated to. Out-of-the-box, the Dream has the “Clock” widget running on the primary (or second) pane, and the Google “search” widget running in the third (right) pane.

An additional “pictures” widget is also available, displaying a crop of a selected picture on the home screen (the end result is something like a virtual picture frame).


Similar to the iPhone, swiping across the touch-sensitive display will show the adjacent pane on the opposite side. For example, swiping from left to right will move the current focus to the left screen. To go back to the middle pane from any of the other two, a simple press of the ‘Home’ button will achieve this.

For accessing those other applications that don’t deserve a place on the front line, these can be located in the Apps drawer.



{ Interface behaviour }
Being instinctive to the human touch should always be a predefining condition of any outstanding interface design - something that Google has (obviously) managed to reinforce and ultimately offer in the Android platform shown off on the HTC Dream.

The use of a capacitive-based touch screen display allows for effortless touch-based control by its user. Gestures such as tap, swipe and hold have been made commonplace by Apple on their iPhone product - and for Android to use these similarly for its own
platform implementation is only logical.

(One slight difference that I found between the Dream and the iPhone was in the system-wide transitional effects by the latter, which were somewhat more fluid and smoother than those animations shown off by the Android UI. In terms of user experience, this may simply be seen as “icing on the cake”. Yet, something like this can and will affect how well the platform truly “feels” in an overall sense.)

But by also combining the use of function-specific hard buttons and a QWERTY thumb-based keyboard, the Dream makes the Android platform a truly unique one. I personally loved the convenience of being able to perform certain actions without having to solely rely on the touch screen interface to do these. One very good example is the mini-trackball, where I would use this as an alternate menu navigational device should finger-pointing become too much of a task (especially true when selecting on-screen items becomes difficult due to a small (visible) target area).

Another good example of their tight integration is the availability of keyboard-based shortcuts. Not those pre-defined commands that get printed on the actual buttons - but keystroke combinations that users can personally customise for his/her own use. For example, pressing the “search” button (the one with a magnifying glass silhouette, on the left of the “@” button) together with “B” launches the on-board browser app - while Search + “i” and Search + “m” opens the ‘Chat’ and ‘Messaging’ functions respectively.

On top of possible personalisation of these defaults, additional shortcuts can also be created for those newly-installed third-party applications. Not only can this save some time in launching apps, but it can certainly provide for an improved workflow for many users who

Again, these presets can be personalised by its user - plus, additional shortcuts can be created for newly-installed third-party applications too.

And you may have noticed that the Dream does not come with the typical pair of soft keys for accessing menu- or feature-based options and functions. Instead, this has been replaced by the use of the ‘Menu’ button and the use of an on-screen contextual menu - both of which contribute greatly in enriching Android’s overall platform usability (again, some “icing on the cake” that really matters!)

{ PORTRAIT versus LANDSCAPE }
Android can be used in either standard portrait or widescreen landscape mode at any given time - and it makes sure that the user experience doesn’t differ greatly in a visual sense.

Combined with the intelligent physical design of the Dream, I must emphasise once again that the overall usability of this particular device is just outstanding. On some devices, I have a clear preference as to how (physically) I would use it. But in the case here, using it either way is as comfortable and doesn’t cause a stir

Over time, I found myself spending more time in landscape mode because of my frequent need for QWERTY - since I do a lot of text-based messaging. And because Android includes those Google-based communication services, like Gmail and Google Talk, I find myself less likely to operate the Dream in traditional portrait mode, unless for making and receiving calls or browsing the Web.

{ Configurations and settings }
I’m sure this is the part of a device that most people try to stay away from, usually due to the complexities of finding something and/or correctly applying a specific setting.

But on the Dream, the Android UI avoids all efforts of being overwhelming with the underlying technology, and attempts to present the smartphone’s configuration and settings in “plain English”.

On opening the ‘Settings’ app, various different (settings) categories are shown, and have been ordered in terms of their importance to the general user. For example, each category has a clear title shown in a title-sized white typeface, followed by a brief explanation in slightly-smaller text. I find this way of presenting the different (major) settings groups to be very clear and concise.

Going back to the ordering of the ‘settings’ list, I also quite favour the method in which it has been ordered - that is, by the “frequency” that the settings would most likely be accessed by its user. For example, the very first category on the list is “wireless controls”, which consists of all settings relating to communications (phone radio, network data, WiFi) - and it made perfect sense for it to be where it is. Next was “call settings”, then “sound & display”, “data synchronisation”... and the list goes on!

Unlike most other smartphone devices, where categorisation is supposedly “logical”, trying to find the setting and making the change usually takes longer than expected. Here, though, the experience of finding what I wanted was indeed far easier and less stressful.


Communiqués

[ calling: voice calls ]
[ messaging: SMS / MMS / email / IM (Google Talk) ]


HTC Dream - designUnquestionably, the Dream is one of the better devices out there where broader communication needs is a prime concern. Its thumb-based keyboard is the main attraction for people who live on mobile email and text messaging, and is complemented also by the positive ergonomics of this device.

While all operations requiring text input needs to be done via the keyboard, telephony-based functions are exempted from this thanks to the virtual (3-by-4) numpad displayed from within the ‘Dialer’ app. Once a call is established, the display will enter sleep mode after a pre-defined period. This is to prevent any accidental “touches” registered by the capacitive touchscreen when it’s right next to the user’s face - a scenario that products like the Apple iPhone and Nokia 5800 XpressMusic need not deal with, because a proximity sensor was used.

During a call, the display can be re-activated by simply pressing the “menu” button. If this was immediately after making the call, then the current call status is displayed, plus access to the slide-out (virtual) number pad drawer that’s shown as a drawer tab. Pressing “menu” again will offer additional in-call options, such as call waiting and conference, plus the option of switching on speakerphone or transferring audio to a connected Bluetooth audio accessory.

For text-based communications, the Dream offers:
  • the typical SMS and MMS messaging capabilities (via the ‘Messaging’ application);
  • native access to your Google-based Gmail account (that is, the one used when setting up the Dream for the very first time), along with push capabilities;
  • access to other POP3, IMAP4 and various webmail based email accounts; and
  • a native Google Talk instant messaging client.

Obviously, these features are only usable in landscape (keyboard-opened) mode.

The alternate email client (item 3 in the above list) is certainly handy to have around, especially for us who may have more than just the one email account - or even if you’ve yet to sign up for Gmail (which I would very much doubt, after having spent quality time with the Dream!) On the other hand, if you have more than one Gmail account, it is certainly possible to access those via this method.

In most cases, set-up is extremely straight-forward. Simply enter your email address and password, and Android will try and work out the nitty-gritty (or configuration) for you in the background. For mail accounts that require special logins or usernames, it is possible to manually edit these.


Connectivity

[ cellular: GSM 850/900/1800/1900 (quad-band 2G) | UMTS 2100 (3G) ]
[ data: GPRS, EDGE, WCDMA, HSPA (7.2 Mbps down | 2.0 Mbps up), WLAN 802.11 b/g ]
[ device-to-device: Bluetooth 2.0 + EDR (data, handsfree/headset), USB (HTC ExtUSB - compatible with mini-USB cables) ]
[ Internet sharing: No ]
[ web browsing: native (WebKit-based) web browser ]


The Dream comes with the average set of connectivity options founded on most smartphone offerings of today. Hardware-wise, the overall package is pretty sufficient - yet, it lacks support for the broader UMTS (3G-based) frequencies used across the globe, with its 2100MHz-only support.

Data capabilities is undoubtedly important to many of the Dream’s core competencies, as a device offering direct access to Google-based online services. The 7.2Mbps HSDPA support offers good downlink speeds not just for those push-based services, but also the built-in WebKit-based browser that I found to be quite the usable front-end to the World Wide Web.

Alternative to network-based data, there is the wireless LAN (Wi-Fi) option on the Dream for choosing wherever such a network may be available for use.

On other fronts, the Dream supports wireless device connectivity via Bluetooth with compatible audio- and data-based devices (but no A2DP), and can be hooked up to a mini-USB cable allowing access to data plus charging.


Featuresque

[ memory: 256MB internal ROM + hot-swappable microSD ]
[ multimedia: Audio output via ExtUSB, Music Player, native YouTube app ]
[ imaging: 3.2 Mpx CMOS + AF ]
[ video: not supported ]
[ others: A-GPS, native apps supporting Google-based services (Gmail + contacts, Google Calendar) with push support, Google Maps with Street View & Digital Compass support, third-party application downloads via ‘Android Market’ ]


Google, and not HTC, has offered a very different product proposition here. With its Android platform, the search giant is trying to bring those same online services, taken for granted when used via a desktop browser, to the handheld, while trying not to alter the user experience too much. In my opinion, the timing for a product like this is “just right” for Google, where 3G-based technology has reached a stage of maturity that’s both practically usable and (most importantly) affordable.

As you may have learnt thus far, one of the highlights of the Dream is the Google-based services supported by its smartphone platform. But it is the “pushing” of the data for these services that make the device so much more worthwhile to use. Yes, you could probably say that Android mirrors some of the features of RIM’s BlackBerry devices, but with its crosshairs set on typical consumers rather than business users.



The Dream comes pre-loaded with native Gmail and Google Calendar applications, which can be used in either portrait (for viewing only) or landscape mode. Any changes made via the Dream are pushed almost immediately back to the Google servers, on the condition that an Internet connection is available, and vice-versa. This also applies to changes made to the on-board ‘Contacts’ app, where additions and editions are also treated in the same manner and syncs with the associated Gmail account’s contacts.

If you prefer to have greater control over “when” you want to send and/or receive updates, there is a option under the Dream’s settings that controls the auto-syncing. Turning this “off” will mean that the on-board data, for the respective apps, will not get updated unless its user manually initiates a sync from within the app itself. This is useful for people who don’t need updates to be pushed, and can also extend the battery’s standby time (because of the lesser need to initiate a data connection).

It’s also handy for people who are roaming. Since turning off roaming data will restrict network data access completely, the ability to manually perform a sync - where required - can allow its usage to be controlled, somewhat.

Maps is the other Google-based service that the Dream supports. On top of the standard functionality offered through its app made available on other mobile platforms, this one for its own Android offering comes with the ‘Street View’ feature that’s also tied in with the Dream’s digital compass. When functioning in tandem with the accelerometer, the Street View feature can be navigated simply by shifting the device in a left/right and even up/down orientation. The actions of the user is almost immediately reflected by a shift of the Street View “view” shown on the Dream’s HVGA display, with the direction shown on-screen being relative to that of the device’s current heading (or facing).

The Dream also supports third-party based apps, which can be downloaded and installed via the ‘Market’ (Android Market) native app. As of the time of writing, all applications listed were free-of-charge, meaning that they could be freely downloaded by any Android-based user onto their device. But I do believe that in some other, more-mature markets where Android has been in, chargeable apps have already begun to appear.

I downloaded a few apps to “have a play” and to test out. However, the quantity of apps listed on the Android Market is huge, and the task of trying to find a good-quality piece of software that does what it describes can prove difficult. On the contrary, this is not to say that there aren’t any good apps being written and offered for the platform.

{ +ve’s } .. Integration of app features between apps
One of the hidden gems of the Dream, and the Android platform, is how Google manages to get their applications to talk to one another on a transparent level.

One example of this is the ‘Maps’ application, and its accessibility to the information stored inside the ‘Contacts’ app. With a properly-loaded address book database, Maps can easily retrieve search results on-the-fly by doing wildcard matching as you type in the “search” field.

Another interesting one is how the ‘Calendar’ app can help you automatically switch your current presence (or Google Talk) status to “busy” for specific appointments (requires the “show extra options” option to be selected). And after the time for the calendar entry has lapsed, it will revert back to the previously-selected status - very neat!

{ -ve’s } .. Poor camera performance
Attempting to take proper pictures with the Dream can be quite a frustrating act, more so when all the other faculties of the device are working out so well for its user.

The Dream comes with a 3.2-megapixel imaging capability, assisted by an auto-focus lens to allow for shots taken at a range of distances. Although well-facilitated for the job, the one thing that had to spoil it all was the unexpected shutter lag, of around a second for every shot without fail (under standard lighting conditions). Plus, the time that it takes the Dream to come up with a resulting on-screen preview feels longer than it should.

Furthermore, the on-screen virtual viewfinder offered a lesser representation of how the final (captured) image would actually look, which seems to be caused by the ‘Camera’ app not displaying a full (100%) image during pre-shot/“viewfinding”.


Battery and power

[ cell: Li-ion cell @ 1150 mAh ]
[ charging method/s: AC adapter, USB power (via ExtUSB or mini-USB cable) ]
[ power management: screen timeout feature ]


My biggest disappointment with the Dream was its rather-poor battery performance, which - under standard usage conditions - could only provide for a standby duration (from a single full charge) of up to 24 hours.

At the end of the day, it all boils down to the amount of data usage going through the Dream, and the type of data connection that it chooses to use. In most usage scenarios, 3G/HSPA would probably be the primary connection method, and is also the most power-hungry one compared to the likes of Wi-Fi or even 2G-based data (GPRS/EDGE). During my review of the Dream, I rarely chose to use its Wi-Fi capabilities.

During the fortnight that I had the Dream as my primary phone, the device would always be hooked up to the AC charger during my slumber hours. From the moment that I’m out of bed, so would the Dream be relying on its own power source. And by the time another cycle is completed, the battery meter would usually be in the orange zone (~30% charge remaining), or even exhibiting a near-depleted charge (with the red LED continuously flashing). Either way, it’s absolutely necessary to charge the phone overnight, every night.

There are ways to conserve overall power usage, with one of these methods being the disabling of the “push” feature, which will most certainly guarantee a longer standby time per full charge. Alternatively, periodic charging via a mini-USB cable, connected to a computer’s USB port, can also provide the Dream with some relief whenever possible.

But ultimately, the fact remains that a 1150mAh lithium-ion battery is clearly insufficient for a device design like the Dream.


Pros...
  • Native, always-on push access to selected Google Services (calendar, contacts, mail)
  • Down-to-earth, and highly customisable, user interface
  • Unique, highly-usable keyboard, trackball navigation, and slide-out display
  • Good ergonomics overall - when used in either portrait or landscape orientation
  • HSPA and Wi-Fi enabled

Cons...
  • Poor battery life (maximum standby of up to 24 hours on average use)
  • Overall camera functionality is not up to scratch


Sales box contents...
- HTC Dream handset
- Li-ion battery @ 1150mAh
- ExtUSB to USB data cable
- AC charger adapter with detachable wall plug (required use of ExtUSB to USB data cable)
- Stereo headset with multifunction button | ExtUSB interface
- Ear cushions (fits over headset earbuds)



 


You may be interested in

HTC Unveils Second Android-based Smartphone | - latest

HTC Unveils Second Android-based Smartphone |  - latest

BARCELONA, Spain - Vodafone and HTC today unveiled the HTC Magic, the network's first Android-powered...

More

HTC Dream True Images revealed | - latest news, specs,

HTC Dream True Images revealed |  - latest news, specs,

Just in the day Neo Carlo Magno sends us some pictures of the camera, a Taiwanese forum leaks out tru...

More

HTC Shift purchased online at NT$ 45,900

HTC Shift purchased online at NT$ 45,900

HTC super-perfect as mobile office solutions HTC Shift to support HSDPA and GSM quad-band for mobile ...

More

HTC Cleopatra Shadow II gets release date | - latest news,

HTC Cleopatra Shadow II gets release date |  - latest news,

The upcoming leaked HTC Cleopatra phone will be known as the Shadow II on T-Mobile, which should be o...

More

HTCTouchDiamond&TouchProreview|HTC,WindowsMobile,TouchFLO

HTCTouchDiamond&TouchProreview|HTC,WindowsMobile,TouchFLO

Our review sets: HTC Touch Diamond - ROM version (and date): 1.96.710.3 WWE (25/09/2008) - UI version...

More