The HTC Windows Phone 8X

Brian already gave the HTC Windows Phone 8X a good once over here; today I'm fortunate to offer a slightly more detailed analysis beyond the existing performance metrics. The WP8X is essentially competing with the Nokia Lumia 920 as the flagship phone for Windows Phone 8, and while the Lumia 920 has benefited from a combination of Nokia's close relationship with Microsoft and Nokia's own remarkably useful app suite, it's tempting to give the slight edge to the HTC.

On paper the Lumia 920 is the more robust device, offering greater storage capacity (32GB instead of the WP8X's 16GB), better camera quality, and a slightly higher resolution IPS display. I've copied Brian's chart from his preview below to give you a better idea of specifications, adding information about the Lumia 920 in place of the Samsung Galaxy Note 2.

Physical Comparison
  Apple iPhone 5 Samsung Galaxy S 3 (USA) Nokia Lumia 920 HTC 8X (International)
Height 123.8 mm (4.87") 136.6 mm (5.38" ) 130.3 mm (5.13") 132.35 mm (5.21")
Width 58.6 mm (2.31") 70.6 mm (2.78") 70.8 mm (2.79") 66.2 mm (2.61")
Depth 7.6 mm (0.30") 8.6 mm (0.34") 10.7 mm (0.42") 10.12 mm (0.4")
Weight 112 g (3.95 oz) 133 g (4.7 oz) 185 g (6.53 oz) 130 g (4.59 oz)
CPU 1.3 GHz Apple A6 (Dual Core Apple Swift) 1.5 GHz MSM8960 (Dual Core Krait) 1.5 GHz Qualcomm MSM8960 (Dual Core Krait) 1.5 GHz Qualcomm MSM8260A (Dual Core Krait)
GPU PowerVR SGX 543MP3 Adreno 225 Adreno 225 Adreno 225
RAM 1 GB LPDDR2 2 GB LPDDR2 1 GB LPDDR2 1 GB LPDDR2
NAND 16, 32, or 64 GB integrated 16/32 GB NAND with up to 64 GB microSDXC 32 GB NAND 16 GB NAND
Camera 8 MP with LED Flash + 1.2MP front facing 8 MP with LED Flash + 1.9 MP front facing 8.7 MP with dual LED Flash + 1.3 MP front facing 8 MP with ImageChip, LED Flash + 2.1 MP front facing
Screen 4" 1136 x 960 LED backlit LCD 4.8" 1280x720 HD SAMOLED 4.5" 1280 x 768 IPS 4.3" 1280 x 720 SLCD2
Battery Internal 5.45 Whr Removable 7.98 Whr Removable 7.4 Whr Internal 6.8 Whr

The Lumia 920 has a lot going for it, but it's also a bigger, heavier phone with a slightly reduced pixel density compared to the 8X's. Internally these employ basically the same silicon; the MSM8960 and MSM8260A are the same chip with different basebands available. I will say I would have appreciated the additional storage space of the Lumia 920; 16GB is rough to live on when twenty bucks and a pair of tweezers could turn the Dell Venue Pro into a 32GB smartphone. It does bear mentioning that the 8X hasn't had the rocky launch that the Lumia 920 had.

As for the HTC Windows Phone 8X itself? The blue polycarbonate shell is beautiful without being ostentatious, and though the black levels of the display make me long for AMOLED again, the high pixel density results in incredibly sharp images. I feel like button placement could be slightly better, as I often accidentally squeeze the volume rocker while trying to press the power/lock button. I've also found the automatic brightness setting to often be a shade too dim, though ironically the phone's rear-facing camera is remarkably adept at handling low light.

Interestingly, though the 8X has a slightly lower resolution display than the Lumia 920, the change in aspect from 15:9 to 16:9 has ameliorated one of my minor complaints about the Dell Venue Pro and Windows Phone: the extra space at the top of the display stemming from the slightly taller aspect means you can still access the notification pane in applications designed for the 15:9 ratio.

Introduction The Windows Phone Interface
POST A COMMENT

118 Comments

View All Comments

  • jeffkibuule - Monday, January 28, 2013 - link

    I've been using a Nokia Lumia 920 for the past 2 months and pretty much loving it. Windows Phone 8 is no longer hampered by weak hardware, it just needs not "more" apps, but the "right" apps.

    I'd be interested to see whether Microsoft will more heavily leverage the Xbox brand into making both Windows Phone 8 and Windows 8 successful gaming platforms. It really needs more tier 1 studios to make both platforms worthwhile for developing. It should be that hard, especially considering Windows Phone 8 finally supports DirectX (very weird that WP7 didn't expose it to 3rd parties).
    Reply
  • BedfordTim - Monday, January 28, 2013 - link

    There are two major ommissions for me.
    Firstly does the speech recognition work, and secondly is there an equivalent to Google's excellent predictive text? For Europeans Google's recognition engine understands the words but fails to act.
    Reply
  • GrzegorzWidla - Monday, January 28, 2013 - link

    Speech recognition does work. It's worse than Google's but not a lot. It's definitely usable and the more you use it, the better results it yields. I haven't used voice dictation and various voice commands in non-English.

    As for predictive text, do you mean in keyboard or in search? Keyboard prediction is far better than on Android, especially in Polish which I write in mainly. Also it works perfectly with multiple languages. Google Search prediction is obviously better. Bing is lacking when it comes to text search. It's better though for searching for videos and images - especially due to proper, modern, mobile interface. Searching for images on my Android devices is a joke and I always pick a laptop instead of even trying.
    Reply
  • CaedenV - Monday, January 28, 2013 - link

    1) MS's speech recognition is a learning system. The more you use it, the better it gets. When I first turned it on it always had a rough time figuring out what I wanted, but now it is almost always accurate. There are still some issue, like it can never figure out things like desert and dessert (one yielding pictures of guns, and the other giving tasty treats), but for the most part it does an excellent job now that I have used it for a month.
    The really amazing thing is that it does a good job not matter the background noise. I am not sure how much of this is the lumia 920's sound canceling, and how much is the speech recognition engine being good at eliminating extraneous data, but it does work very well, and works faster than the Android phones I have seen/played with.

    2) Predictive text is there and works well. I do wish it was grammar-specific as I am often given an option for the proper root word, but the wrong tense. So I am often given a singular instead of a plural, or a plural when I am looking for a possessive, etc. But like the speech recognition it is a learning system, and it at least catches on to what you are trying to say pretty quickly. As a keyboard typer who can do 60+wpm I thought I would be annoyed at the text input, but while I am still getting use to the lack of tactile feedback, the predictive text does keep up with me pretty well.
    Reply
  • Thermalzeal - Sunday, February 17, 2013 - link

    The one thing that is better than Google's is the app level API's that can be accessed . For instance, there is a Hey DJ app which allows you to hit your windows phone button and say, "Hey DJ, Play artist...song...etc" It works with all music on your phone. The pass through capabilities of being able to integrate not only search but queries to content within the phone are quite powerful. Reply
  • lmcd - Monday, January 28, 2013 - link

    and regulate its handsets so that all users were Nexus users, no one would care about the 8X. Simply put, it's carriers and skin-happy manufacturers killing (slaughtering?) Android.

    Now, what's your issue with stock? I love stock 4.1, personally.
    Reply
  • thesavvymage - Monday, January 28, 2013 - link

    Google can't do that, that is precisely why it is so popular. It is open. The instant they make it impossible for carriers and manufacturers to customize, it will also be extremely difficult for groups like cyanogen to customize android as well. Anybody can go download the source code and customize android, thats what makes it a popular choice among manufactuers. It is both a blessing and a curse Reply
  • UpSpin - Monday, January 28, 2013 - link

    People complain about fragmentation, yet, it's a stupid term people have no clue about:
    1. If you want the bleeding edge Android version, get a Nexus device. No one forces you to buy a HTC or Samsung device, if you want Android, get a Nexus device. Unlike with iOS however, you can, with Android, buy other devices with different UI being 100% compatible to Android.
    2. The ability to do with Android whatever you want is the reason it's so succesful. Intel is able to port it to their hardware, and so is ARM and MIPS. Not possible with iOS, WP8, other locked down OS. RIM is able to run Android Apps, you are able to run them on Windows, ... not so possible with locked down iOS or WP8 apps. Some people don't like the Android UI, yes, such people exist. They prefer the HTC, Samsung, Sony, ... whatever interface. They are free to choose what they like. The abilty to customize the UI allows manufacturers to differentiate themself from each other. Again, if you don't like the Sense UI, get a Touchwiz, if you want stock Android, get a Nexus device.
    3 It would be pretty boring and totally uninspiring if everyone uses stock Android. Many ideas of Touchwiz/Sense/CM... got integrated in AOSP. Google can take a look at what people like about Touchwiz, Sense, ... and use the best of it. Microsoft on the other hand is the sole developer of WP8. If people don't like specific things, they're fu****. They can't buy a HTC WP8 with a, for their taste, better UI. So it's really boring, and harms progress and inventions. Everyone is forced to use the same.
    4. Fragmentation: There are currently two important Android versions: Version 2 and Version 4. The minor version changes are minor and for most customized Android versions negligible. What matters are the major numbers, because this is important for API and thus App compatibility. The customization added by HTC or Samsung makes the changes done by Google in minor versions mostly negligible. They offer their own keyboard, own launcher, own widgets, own extensions, tweaks, ... And honestly, most users don't even know what Android version they're running. Bugs get fixed by device manufacturers OTA, too, without the need of a minor or major version upgrade, too.
    Fragmentation is a dumb no-reason against Android. iOS is much more fragmented (older devices get a major version upgrade, yet with all the new features artificially disabled (not so on Android, you get what the version supports), so no upgrade at all, but people are dumb enough to think they are running the latest version, yet, nothing changed). WP is even worse. WP8 apps are totally incompatible to WP7.x devices. And if WP8 is two years old, older devices won't be able to run the latest demanding apps and features any longer, either, because older hardware doesn't support it. So either they make it like Apple and increment the major version number without changing anything and break what was working fine in the past, or are honest and stop upgrading the device.

    What's disgusting however, is that companies benefit from Android without supporting it.
    Example: RIM supports emulating Android Apps, yet, they also added their own programming language. That's redundant. It would have been much better if they just natively use Android apps/dalvik and ditch their own approach. So if you develop for RIM you automatically develop for Android. But they want their own Ecosystem. The same with Amazon. They benefit by using Android on their devices, yet, lock it down to only support their Ecosystem and block out everyone else.
    The huge advantage of Java and the Dalvik VM is that you can run the apps everywhere. That's not the case with Objective-C apps, nor with .NET apps.
    Reply
  • steven75 - Monday, January 28, 2013 - link

    It's sounds like you don't understand what people mean when they say fragmentation. They are talking (most importantly) about supporting all the newest APIs and second the display resolution where you are incorrectly talking about built-in features. A consistent set of APIs are MUCH MUCH MUCH more important than the bonus built-in OS user facing features. I can use a 2+ year old iPhone 4 and download pretty much every single app in the App Store, even those using the very latest iOS 6 APIs. Not so on Android!

    Android 4.x and Android 2.x have different sets of APIs and Android has obviously craploads of display size fragmentation. Multiply those two and you are indeed looking at mass fragmentation.

    Apple has essentially a single set of APIs work across all their devices that are 3 years old or newer and 4 total display sizes. FAR less fragmentation.
    Reply
  • Belard - Tuesday, January 29, 2013 - link

    How old is Android 2.x? Oh yeah 3 years old. Android 4.x has just surpassed 2.x. Apple still makes the iPhone 3 for the $1 market... the 4S for the $100~50 entry.

    Yeah, Android 2.x sucks... but again, 3 years ago... are we living in 2010?

    Fragmentation is not between the vendors, its *WHEN* low-end manufactures (usually Asian market or cheap $80 tablets in Walgreen's) make cheap devices using very old cheap hardware and sells them currently. ALL new devices from reputable sources are 4.0~4.2.

    Android as a whole, has sold 75% of the phones in 2012...
    Reply

Log in

Don't have an account? Sign up now