I am a big fan of Palm products. Those days it was cool to carry a Palm PDA, and if my memory did not fail me, my first Palm product was a Palm Pilot series. Palm gave me the impression of building nifty products but not a world shaker one. However when the webOS was first unveiled in 2009, I thought it is the mobile platform to go, with Windows and Linux both dominating the desktop market. The thoughts of web connected device, taking advantage of the Web 2.0 technologies, was just salivating.
Since then, a handful of Palm devices were launched sporting WebOS. I love the simple interface but the form factor never grew on me. With the products mostly focused in the US market, strangely if I may add, I never got to own one until now. Then HP acquired Palm, and it got me lighted up. A PC giant (or a ex PDA big player in Jornado and iPAQ), and an promising next generation mobile OS maker, perfect marriage or a disastrous divorce in making? Continue reading →
Whenever i hear such a claim, on any product for that matter, i always wonder what is the context of the “best”. You see unless the product excels in all departments, i.e. it is the purrrrr -fect product in comparison to its competitors (see there is still a context) it can’t be the best.
Take the category of smartphone as an example. I would rate HTC for its famed Sense experience, which help to ramp up a newbie experience with Android (and Windows Mobile previously). On the other hand I see SonyEricsson being in the leader in its camera functionality having used its Xperia Arc and compared it with all the Galaxy S series. That said, HTC Sense is getting too complicated as the company tries to be sophisticated for its products to be ‘smart’. But I have digressed.
So when I read reports that raved the new Samsung Galaxy S II as the best Android smartphone to date I thought it is a bold statement. Don’t get me wrong as I think it is yet another fine product by the Korean company but that statement needs to be contextualized. Continue reading →
A couple of years ago, when SonyEricsson decided to re-invent their new flagship mobile product in Xperia X1, I bought their vision, literally. The phone, despite running on Windows Mobile platform, wowed me with their sleek design and their UI panel concept. Hey, I even contributed to their vision by developing a navigation panel. The quality of the phone was far from perfect, and I promptly returned the phone back to the service centre when they offered a buy-back proposal to appease my dissatisfaction. That was my last impression of a Xperia product. Continue reading →
It has been more than 3 months since I have gotten myself a Desire HD. Usually I would be excited with the new phone, and would blog about it like I did with my Galaxy Tab and Galaxy S. Somehow, with Desire HD, I have been dragging my feet (or rather my fingers) to blog about my thoughts of the HTC latest flagship Android gadget. It was mostly disappointments that piled up one after another, and I tell you why.
HTC Desire HD
When I first had my hands on the Desire HD, I actually thought I fell in love with it. The overall quality is just what you would have expected from HTC; The use of good quality material (over some cheap plastic material assembly), the polished user interface including the initial set up process. The phone feels heavy but it makes you think of the good solid material instead of the negative aspect of the weight. The tactile feedback on the screen gives a “tight, controlled mechanical” response you would expect from a high quality haptic technology based components. The initial take of the phone then was this should be what HTC Desire was 6 months ago. But it turned out to be more than 6 months gap.
Like all romances, love at first sight is never definitive, and with Desire HD it is a good classic example of that. The quality one can expect from HTC is not just about the positive ones. There were still alignment issues with the housing and casing covers, and the stability of the HTC applications that were bundled with the phone remained questionable, just to name a few. Before this blog entry degenerates into rants, let me just highlight three key areas that had subdued my enthusiasm about this phone.
With all the fantastic technical specifications that Desire HD is carrying, the phone fails miserably in the screen display and camera department (of course in my humble opinion). If Samsung Galaxy S had changed my perception about what a mobile phone can do as far as video recording and playback are concerned, Desire HD proved why the former is the best selling Android phone in the marketplace today. That is despite all the great things you can find about the phone itself. At a first glance, Desire HD screen display looked fabulous. The Super LCD screen appeared to have match the bar set by Samsung’s Super AMOLED screen. But when I placed my Desire HD and Galaxy S side by side, my jaws dropped and I was almost screaming, “What is so super about the SLCD!?”.
From the video below, the display on Desire HD is simply washed out. The display colors looked faded and flat, whereas in the Samsung devices they looked vibrant. Looked at the contrast and brightness! The conclusion I got? I would never want to watch any movie on my Desire HD, if I happen to spot somebody around me carrying a Samsung Galaxy S.
Moving on to the video recording capability. Despite the specification of being able to take 720p video, Desire HD was never able to match the video recording capability I had experienced in Galaxy S. The ghostly motion effect is still there, especially if the video is taken in an indoor setup (flash is a moot point because I could record a smooth video indoor with Galaxy S). If that was not bad enough, there was a severe bug in Desire HD, that resulted in video recorded with random stuttering effect. So when you are trying to take a HD video, this bug becomes a big joke. Incidentally this bug occurred only when I set the video camera mode to 720p. Essentially, the phone had problem recording at 30 frames per second in high definition. There are “dirty” workarounds, but I was never happy with this video recording function since day one.
a sample of video recording using Desire HD. Notice the freeze in 0:16 frame.
Then comes the software aspect of the phone. I remembered when I first got HTC HD2 more than a year ago, I had to endure the buggy SMS application for more than 2 months. If text messaging is an essential mobile function for you, that bug effectively rendered the phone unusable. Despite the bad experience, I remained hopeful when Desire HD was first launched in the market. HTC development team must have learnt a big lesson out from that saga and delivered a better quality product this time round.
How wrong was I again! One of the selling point of Desire HD is that it is “smarter” than before with its Htcsense.com. The latter is essentially a service based feature which enables the phone owner to locate and control the phone remotely. Theoretically one can locate the phone with the help of GPS, or initiate a ringing on the phone so you can locate its presence acoustically. One can even initiate remotely, to redirect phone calls and text messages, or wipe out data in case of emergency. Sounds great isn’t it? And of course I said that is in theory, because until last month, I could do nothing of these, even though these were advertised features. The HTC support acknowledged that the performance stricken services (or applications) in htcsense.com were buggy and the development team was working on it. Being an IT-trained professional, I can understand how software can never be perfectly free of bug. However, the line should be clear between a software in alpha stage versus one that is go-to-market ready. HTCsense.com was clearly at a former stage, so it baffled me why the product was being launched in the first place. Perhaps it should not come as a surprise given the pressure to launch in the market, but it looked like somebody in HTC had done his maths. That the market share gain (through early product launch) will take care of the market share loss (due to the product quality problem).
A web-based service that looks good but not functional at all
On the otherhand, the HTCsense.com could also be more smarter than it is. As of now the services become useless when the phone battery get depleted. Imagine you discover that you have left your phone at home when you reach the office. You want to remotely redirect your phone calls and/or text messages, only to find out that your phone is “uncontactable” because it runs out of battery. But I digress.
In all my correspondences with HTC support, it was clear to me that they could not commit a time to fix the problems. I gave up, and was looking to sell away the phone, or to do something about the phone myself. With xda-developers.com, I could save a hell lot of my time from building my own ROM or optimizing my kernel which I did for my previous phones. I found Leedroid custom ROM and kernel, flashed it, and the phone finally became what it should really be in the first place. However, there are things that do not change, such as the hardware limiting issues (i.e. screen display). In other cases, such as the overall product and customer experience with HTC, it is almost like a carbon copy of the previous one when I had HD2.
Year end holiday season is here finally, and I am already imagining a Christmas tree in my house with all the interesting gadgets nicely packed as presents surrounding it. More on that in subsequent blog posts. In the spirit of sharing joy of holiday season, I would begin by sharing my peep on Creative ZiiO 7″ — Creative first attempt in the Android tablet space.
ZiiO 7" Tablet
Earlier this week, I was privileged to have my hands on Creative ZiiO 7″ tablet, even though it was just a development unit. Given that (that it was just a development unit), the exterior finishing was not expected to be polished. The tablet was however loaded with the latest firmware that would supposedly shipped for production, so the hands on experience will still be close to that of a retail unit.
For a tablet, what draws to one’s attention is usually its form factor and its screen display. Admittedly, the first impression was a mixed feeling. The size of the tablet, defined by a 7″ wide screen, coupled with its all-white outfit, would definitely catch an enthusiast’s attention. This is especially so for somone like me who had already experienced a 6″ Kindle and a 10″ iPad, the two extreme end of a tablet-type devices. Of course, Kindle belongs to a different league altogether, given that it is a dedicated e-reading device. However, the size and weight of these devices should give a tablet-shopping buyer a good reference of what he needs to look out for, for there is no one perfect tablet in the market that fits all the needs.
Holding ZiiO 7" with one hand is convenient
Once ZiiO 7″ catches your attention, the screen display might possibly drops yours. I was definitely disappointed by the screen display, especially after having used to colour vibrancy that Super AMOLED display offers, in my Galaxy S and recently Galaxy Tab. The colour is a little flat, and further impacted by the viewing angle. If there is anyway to describe the visual impact, it feels like a 3M privacy screen filter fitted on it, albeit a little exaggerated. Ziio sports a resistive screen. While it is probably one of the most sensitive resistive screen in the market today, Creative’s decision to stick with it sets me scratching my head given that capacitive screen has becoming a norm these days. But I was quickly reminded that Ziio 7″ is Creative’s entry model for their Android tablet product line, and costs just 1/3 of Samsung Galaxy Tab’s price tag. Fair enough, but unless you are a budget-conscious shopper, or one who is about to buy the China-made i-Pad lookalikes, wow will be the last thing you would say when you power on the Creative’s ZiiO.
Usability wise, Creative ZiiO is very capable, despite having to navigate over the resistive screen. The screen was responsive, so were the applications. I was told that ZiiO uses its own processor, ZiiLABS ZMS-08 HD Media-Rich Applications Processor. While I have not benchmarked its processor in the 7″, I tried on ZiiO 10″ which uses the same processor, and the result was astonishingly good, scoring a 3000 over points in CPU. To give some context, my over-clocked Galaxy S could only manage half of what ZiiO has achieved. ZiiO has a stereo speaker, but I could not make out its quality given that I was in a cafeteria at the point of testing ; Just not a conducive environment to test sound quality.
Creative Zii applications
ZiiO is still running the older Android Eclair (2.1) as we speak, even for the retail units. However, I was told that Froyo (2.2) should be released for upgrade very soon. As I unlocked ZiiO 7″ tablet, I was greeted by Creative’s own simplified lock screen and home launcher. Neat, I told myself. At least the company is going to the right direction in developing its own DNA. On the application front, Creative have a few customised applications, ZiiMusic, ZiiVideo and ZiiPhoto. Given Creative’s specialty, I have no complaints with their multimedia playback software, although ZiiMusic did hang on me once before I had to reboot the tablet to solve it.
ZiiO's Kindle
Having used Kindle for a while, I naturally tend to compare ZiiO with the former, as an e-reader. ZiiO, with its weight almost twice that of the Kindle 3 (400g vs 241g), definitely feels heavy if one were to read over a prolong period of time. For a quick read, I would think it is definitely capable. What I was impressed is ZiiO’s night mode feature, which not only dim the backlit display, but also also toggle the display foreground and background color, so that the screen would not be too glaring. Although it can’t beat e-ink technology, the night mode feature is the most welcome feature, if you always like to read at night.
In a nut shell, for $359 SGD, I think it gives the China-made A-Pad a run for their money (go support Singapore products!). Looking from another perspective, if you are planning to spend $200-300 for a digital photo frame, grab this Creative ZiiO for its value for money, since it could do what a digital photo frame does, and more. But when pitted side by side with the bigger brothers, I could sense that Creative ZiiO 7″ is shouting out for his super-brother (not ZiiO 10″! fwiw) for reinforcement. I heard it will be coming …
Snap shot video of the hands-on (in a noisy cafeteria)
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.
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 thesmart 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.
You may like to call it an iPhone app clone. I got to acknowledged, that iPhone apps, less those mind-less ones, have been churned to serve a purpose in one’s daily life. Traffic CAM SG is one of them, which displays the road traffic in Singapore highways.
However, other than a more intuitive interface as a result of the iPhone UI, there isn’t really a breakthrough functionality that can’t be offered outside of iPhone. The live traffic, is afterall taken from the local authority website (OneMotoring), and I decided to bring this capability to Windows Mobile world.
That said, the Windows Mobile SDK doesn’t really offer gesture-based interface, unless you work in the native C++ environment. Since this application is meant to be a “quicky” one (as I cannot afford to burn my weekend just for this) so I have to design and build based on what compact .NET framework could allow me. This is built in less than half a day, including creating the graphics and the testing of the links, so please pardon this appy for its very basic interface.
Note: Traffic images and contents are sourced from Intelligent Transport System Centre of LTA (Land Transport Authority). You may go to this OneMotoring link for the online version.
Home screen showing all the highways that has live cam positioned by LTA
Listing of all live cameras in the selected highway
Snapshot of the road traffic, courtesy of LTA OneMotoring Site
You can download the beta from here (only WVGA/VGA supported at the moment)
One of them is performance. After flashing my HD with Dutty’s V3.9 XT Turbo ROM, I felt as if I have gotten a new toy. But the moment I hold up the phone, the squeak on the battery cover put a big dent on the otherwise wonderful HD experience. As I depress on either side of the battery cover, the squeaks just remind me on the squeak and rattles I experienced in my old Volkswagen Bora.
I decided that I have to do something about it (and give me one less excuse to change my phone!)
Upon inspecting the area where the squeak happens, I identified spots where the plastic on the battery cover is pressing against the phone housing.
All it took for me is a pair of scissor, masking tape, and a small screw driver (or any tool such as tweezers that can be used to position and press the tape on the squeaking area, or just your fingers if you do not have fat thumbs like I do). Stick the tape at the offending area, and you are done literally within a minute!
DIY Tools to mask the squeak
The left hand side of the battery cover
Right hand side of the battery cover; NB: The area above the tape needs to be masked as well
Finally, my HD feels like a gadget with a solid built quality. Maybe it was, but the squeay cover certainly suggests otherwise.
So it looks like I have to wait longer (for an excuse) to ditch my HD. Maybe a HTC Hero might be the one.
It always amazed me whenever Apple releases its new products, the technologies it delivered is deemed refreshing, nevermind the industry is already on it for months, if not years.
I recalled reading Steve Job’s argument on why 3G is not bundled in its 2G iPhone product; He said that 3G consumes more battery juice than its predecessor. Yes it does and so does WIFI which can be found in its first generation of iPhone.
Fast forwarding to now, the new iPhone 3G S is touted as a turbo charged iphone 3G with its HSDPA technology. Again it’s a technology found in my Dopod c730 two years ago. Anybody who wants to argue that Apple always does thing better than its competitors should really question how better is it for this context? That we are able to have 3.5G broadband at fraction of power consumption? I don’t think so.
Then BGR has reported undesirable high pitch noise when iPhone 3G S plays some sound files. One site blamed it on the bluetooth headset, and claimed that he had no problem with another. Surely we can infer a more objective conclusion from all these can we?
