Nokia C6 vs. HTC Wildfire – Review

by Jerry D on August 4, 2010

Another battle of the budget phones commences… Can the feisty little Wildfire grab the Nokia C6 in a headlock and choke it until it submits? Or will the C6 come in quickly and strike a low blow to knock out the HTC handset? I’m Jerry D and I’ll be your commentator for this big phone fight…


This first round is a gentle loosener as the two phones square up to each other. As far as connectivity is concerned, the guts of the C6 come packed with 3G/HSDPA (3.6 Mbps), 802.11b/g Wi-Fi and Bluetooth 2.0 with A2DP connectivity. The Wildfire has 3G/HSDPA (7.2 Mbps), Bluetooth 2.1 with A2DP and 802.11b/g Wi-Fi in its own connectivity package. No real punches exchanged. It remains a draw for now. (1-1)

Size & Weight:

Browse the specs and the Nokia C6 has dimensions of 113.0 x 53.0 x 16.8mm; the HTC Wildfire is 106.8 x 60.4 x 12.0mm. The C6 is the bulkier handset of the two. Measure the weight of the duo and the C6 weighs 150g, while the HTC Wildfire tips the scales at only 118g. I know which one I’d rather have in my back pocket… (1-2)



Nokia has opted for a 5.0 Megapixel camera in its phone, which boasts an LED flash, geo-tagging and VGA video capture. It also features a second, front-facing camera. The two phones match each other for megapixels – the Wildfire also packs a 5.0 MP camera with autofocus, LED flash, smile detection, geo-tagging and video recording. (2-2)


Nokia has built the C6 with a 3.2-inch touch-sensitive display that has a good resolution of 360 x 640 pixels. As for the keyboard, it’s a compact QWERTY layout, designed to speed up data entry. In terms of size, the Wildfire’s touch-sensitive LCD screen is identical. Unfortunately, it boasts a lower resolution (only 240 x 320 pixels) than the C6 and there’s no keyboard. Typing can be tricky on the virtual keypad. (3-2)


In terms of performance, the C6′s chip is a 434MHz ARM 11, while the Wildfire uses a Qualcomm MSM 7225 processor, clocked at 528MHz. The C6 runs the trusty Symbian OS (Series 60). But it’s really no match for the Android 2.1 OS (with HTC’s Sense UI), which gives the Wildfire much more flexibility. As for downloadable apps… check the stats of the Android Market and Ovi Store below. (3-4)

Downloadable apps:


The C6 wins the internal storage battle with 2GB, compared to 384MB of internal memory that comes as standard on the Wildfire. The C6 also has a microSD interface, which can extend the overall capacity to a much more respectable 16GB. However, the Wildfire’s overall capacity can be increased to 32GB via its own microSD memory card slot. (4-4)

Battery life:

How long will the battery last? Nokia says that its C6 can deliver 11.0 hours of GSM talktime, while the Wildfire is rated at 8.0 hours. Meanwhile, standby time is quoted as 400 hours and 480 hours respectively. The C6 just snatches it. (5-4)



The C6 also includes GPS/A-GPS and a stereo FM radio (with RDS). The Wildfire features a stereo FM radio too, GPS/A-GPS and a built-in digital compass. (5-5)

It’s a tie!

It’s tough to call this fight as both phones have their good and bad points. For starters, the Android OS gives the Wildfire a greater degree of customisation than the Symbian OS, which once strode across the cell phone landscape like a colossus. Add to the fact that the Wildfire features the best all-round camera features and that it’s lighter and thinner than the C6. But then Nokia’s phone has a good keyboard, a superior display and a better all-round battery life. A 5-5 scoreline is a fair result.

Buy the Nokia C6 Unlocked GSM Phone with Easy Email Setup, Side-Sliding Touchscreen, QWERTY, 5 MP Camera and Free Ovi Maps Navigation (Black) Nokia C6 vs. HTC Wildfire   Review

Do you agree with the outcome of this fight? Leave us a comment below now…

    Other Posts You Might Like...

  1. HTC Legend vs. HTC Wildfire – Review
  2. HTC Wildfire vs. Palm Pre Plus – Review
  3. HTC Aria vs. HTC Wildfire – Review
  4. Samsung Galaxy S vs. HTC Wildfire – Review
  5. iPhone 4 vs HTC Wildfire – Review

Previous post:

Next post: