Galaxy is surreally desirable

Having tasted my first real Android experience in the mold of HTC Desire, I had another opportunity to lay my hands on Samsung’s new Android flagship product, Galaxy S. I am not sure what does the “S” means, but one cannot be faulted for assuming it is  Galaxy “Supreme”, based on its technical specification, and my initial impression of the phone.

In my short 20 minutes hands on, I was deeply impressed by its form factor and its captivating Super Active-Matrix Organic Light Emitting Diode (Super AMOLED) screen. First of all, it’s thin with a 4″ wide screen, a size that I feel more comfortable after having used to HTC HD and HTC HD2, which have screen size of 3.8″ and 4.3″ respectively. I just find the 3.7″ screen in the HTC Desire, a tad too small for me.  The Galaxy S has  just the right size, and to top it all, it is only 9.9mm slim and weighs only 118g. My only gripe is its piano-finishing battery cover, which is going to be a fingerprint magnet. The fact that the battery cover is made of polyurethanes material, doesn’t make it any more “cheap plasticky”, as I thought the overall build quality is solid.

Now the screen; it looks  stunning to the naked eyes, but once I put it side by side against HTC Desire, with the brightness level maximised for both devices, I find the difference is marginal, if any. I suspect the main reason behind this nano difference, is Samsung’s decision to maintain similiar brightness level, so as to maximize the power consumption efficiency. Afterall, a Super AMOLED screen is statistically capable of achieving 20% better brightness at 20% lesser power consumption level, in comparison to a AMOLED screen.  So if Galaxy S is designed and manufactured at the same brightness specification  as the AMOLED screen, then mathematically one can achieve 33% reduction in the power consumption. Not bad!  (Note: I did observed that the power consumption in Galaxy S much better than that in Desire. It’s not scientifically proven though that it is due to the above mentioned theory, but if anybody can confirm that, please let me know)

In the end, the brief experience was enough to lure me into the Samsung Galaxy S camp. So I got a set a few days later, and begin my Android journey, ehm,  officially. Afterall, the HTC Desire is technically a “T-loan” unit from yeez, and my other Android experience was really Android Cupcake half baked into my old HTC HD.

Having used the phone for the last few days, my conclusion of Galaxy S and Desire comparison is basically  hardware versus software. It is without a shadow of doubt that Galaxy S just shines in almost every aspect of hardware departments, except maybe the flash-less camera (and if I want to be nitpick, lack of LED notification light). I can however forgive the lack of flash, for its superb video taking capability. On paper, it can take 720p video at 30 frame per seconds,  but what counts at the end of the day is the actual quality of the video captured in reality. And I have to say it is almighty impressive, as it  could take a good video without any ghosting effect. Probably the best video capture capability I have come across for a smart phone.

Now, when it comes to software arena, HTC Desire is the clear winner by a mile. HTC sense  and its  home screen widgets,  spice up the otherwise default boring android home screen. One can draw the similarity from the  Windows Mobile devices; that without the Windows Mobile version of HTC sense, it is ladened by a functional but very dated Today screen. HTC has established itself as a smartphone leader, not because of its superior hardware specification, but its ability to mate the hardware and software (regardless of Android or Windows Mobile platform) to address the different needs of various mobile market segments. Samsung, on the other hand, has tried too hard to emulate iPhone, loosing it s own DNA. Its  TouchWiz user interface and the bubble style conversation for text messagin, are just some examples of that. Thankfully, there are applications like  LauncherPro, which can reinstate the iPhone wannabe back to the real android Galaxy S where it should be.

Desire over HD2

I have always have the desire to learn about (mobile) life beyond Windows Mobile,  after having owned numerous Windows Mobile devices for the past 5 years. Then came iPhone, in 2008. But despite its edge cutting user experience and its hundreds of thousands of (useless) applications, it didn’t wow me over. I admit I’m not a big fan of Apple, but that has nothing to do with me not joining the fruity camp. I think it’s a great mobile product to start with, and had redefined the usability of mobile devices. It forces telco to sell data plan as a mainstream service. There’s many good things about the consumer focused phone, but just not enough to replace the likes of my trusty Xperia, Touch HD and subsequently HD2 as a productivity phone.


Then few months ago, I had a taste of Android on my Touch HD, albeit booted from Windows Mobile using haret (just think of it as a PC that can dual boot between Windows and Linux). I thought Android was an unpolished product then, with a great potential to woo over die hard Windows Mobile users.

In the past 6 months, many Android based phones had launched, but they were either too small for my fat fingers, or did not look appealing to me. Most importantly, until Android 2.1 (or Eclair) was released, there was no good way to integrate Android with Exchange Server backend.

Last month, a couple of new Android Eclair phones were launched, and one of them caught my attention. The phone “Desire” is so aptly named. Sporting a screen of 3.7″ size, running HTC sense and most importantly has support for Exchange Server integration,  it looks like a good phone to replace my HD2, which had been on steriod for the past few months.

So when Yeez decides to renew her telco contract, I shamelessly offer her my professional service to set up her HTC Desire, and in the process, for her to experience the steroid boosted HD2 and for me to test-play her HTC Desire for the next few weeks. 

But it took me 2 weeks before I could lay my hands on the desirable phone, as the phone was out of stock island-wide since day 1 due to its overwhelming demand and conservative supplies from HTC (as I understood HTC allocated only 100 units to each telco on day one of its release). Fast forward to yesterday, upon first powered up,  I was first greeted by the familiar shell interface, HTC Sense, which has been around in other HTC Android and Windows Mobile phones. The Android version of the HTC Sense supports a wide variety of widgets, and I believed it is based on Android App Widgets framework. This is a big contrast to the Windows Mobile version of HTC Sense, which has been developed from ground up, based on Lua scripting language. Ok, it sounds little too techie here, but bottomline, you should be able to customise the Android version of HTC sense with other non HTC-sense widgets easily. In the Windows Mobile camp, you would need skilled developers to custom build additional “home tabs” which will only run on HTC-sense powered Windows Mobile devices. That said, I am alittle annoyed with the fact that I can only have 7 “widget screens”, even though I could work around that “limitation” by choosing different “Scene” (each scene has its own set of home widget screens configured).

Installation of third party applications into HTC Desire, like any other Android phones (and iPhone if I’ve to be politically correct), is seamless through Android Market.  I installed a few applications, including big installation packages such as NDrive.  There are some installed applications such as SMS widget counter, File explorer,  Bluetooth transfer app, etc which I deemed basic and should be part of the Android base system. Or maybe I have been spoilt by Windows Mobile for the last few years. On the otherhand,  there are good applications such as Tapatalk which I had been hoping for during  the Windows Mobile  days, and I reckon the lack of “easy to use” UI SDK as the main reason why developers are slow in porting their applications to Windows Mobile.

Applications aside, setting up HTC Desire was a breeze, in particular setting up Exchange Server account for my push mail needs. In a few minutes, all my company mails, calendars and contacts were downloaded to the phone. While the PIM features in Desire (or Android phones for that matter) is not as extensive as that in Windows Mobile, it’s  more than adequate for one to connect to workplace, e.g. scheduling a meeting with a list of  invitees,  setting out of office,looking up company’s global address book, etc. And because I had setup my HD2 favorite people previously, the Desire’s favorite widget screen shows the same list of favorite contacts after synchronising with the exchange server. Neat!

Now here comes my biggest gripe(s),  to date. I always pin-secured my phones, and its no different for HTC desire. The problem with HTC Desire, and possibly for any other Android phones, is that if I choose to have numeric pin, I would still face a full qwerty keyboard to enter the pin when I try to slide unlock the phone. It may sounds like nitpicking, but just imagine you have to tap 8 key codes quickly every time you turn on the phone to make a call or do a quick read of new messages. It didn’t help that Android phones (or at least for HTC Desire) seem to have only one single power management mode; regardless of whether the phone is on external power source or battery, or whether the phone is idle or running some active services.

Apart from these gripes, there are other small nags such as occasional screen lags, inability to have full access to application configurations (probably require rooting). Still, I think it has been a refreshing experience, and is the smart phone that is capable of replacing my HD2. This is even more so with the next version of Android, Froyo,  rumoured to be available for HTC Desire in a couple of weeks time, and reportedly to be 5 times as fast as Eclair. Of course, since its made by HTC, one can easily head over to xda-developers to satisfy ones desire for the dark side.