HTC Desire 612 vs HTC Desire 820 Comparison and Differences
Smartphone 1
HTC Desire 612
Smartphone 2
HTC Desire 820
Smartphone 3
HTC Desire 612 or HTC Desire 820 Specs Comparison
or
Common specs
| Brand and model | HTC Desire 612 | HTC Desire 820 | |
| Rating | (+0) | (+0) | |
| Release date | 2014, October | 2014, September | |
| Dimensions (HxWxD) | 143.8 x 70.4 x 9.4 mm | 5.66 x 5.66 x 2.77 in | 157.7 x 78.7 x 7.7 mm | 6.21 x 6.21 x 3.1 in | |
| Weight | 146 g | 5.15 oz | 155 g | 5.47 oz | |
| Case | buy from Amazon | buy from Amazon | |
| Colors | Black | Marble White, Tuxedo Grey, Santorini White, Milky-way Grey, Tangerine White, Saffron Grey, Flamingo Grey, Blue Misty, Monarch Orange | |
| Battery | 2040 mAh, Non-removable Li-Po | 2600 mAh, Non-removable Li-Po | |
| Battery life |
Stand by time - Up to 484 h (3G) Talking time - Up to 16 h 10 min (3G) |
Stand by time - Up to 424 h (3G) Talking time - Up to 22 h 24 min (3G) |
|
| Approximate price | 240 EUR | 340 EUR | |
| Check price | from Amazon | from Amazon |
Screen
| Technology | Super LCD2 | LCD | |
| Touchscreen | capacitive touchscreen | capacitive touchscreen | |
| Display colors | 16M | 16M | |
| Screen size | 4.7" in | 5.5" in | |
| Screen area | 60.9 cm2 | 83.4 cm2 | |
| Screen format | 16:9 (height:width) | 16:9 (height:width) | |
| Screen to body ratio | 60.2% | 67.2% | |
| Screen resolution | 540 x 960 px | 720 x 1280 px | |
| Screen PPI /points per inch/ | 234 PPI | 267 PPI | |
| Screen protection | Corning Gorilla Glass 3 | ||
| Screen protector | buy from Amazon | buy from Amazon |
Camera and Video
| Rear camera, main | 8 MP, Single | 13 MP, Single | |
| Camera specs | -8 MP, AF | -13 MP, f/2.2, 28mm (wide), AF | |
| Functions | LED flash, HDR | LED flash, HDR | |
| Video | 1080p@30fps | 1080p@30fps, 720p@60fps | |
| Front camera, selfie | 1.3 MP, Single | 8 MP, Single | |
| Specifications | 1.3 MP | 8 MP, f/2.3 | |
| Video | 720p | 1080p@30fps |
Performance
| Operating system - OS | Android 4.4.2 (KitKat); Sense UI 5.5 | Android 4.4.2 (KitKat), upgradable to 6.1 (Marshmallow); Sense UI 7 | |
| Chipset | - Qualcomm Snapdragon 400 (28 nm) | - Qualcomm MSM8939 Snapdragon 615 (28 nm) | |
| CPU | - Quad-core 1.2 GHz Cortex-A7 | - Octa-core (4x1.5 GHz Cortex-A53 & 4x1.0 GHz Cortex-A53) | |
| GPU | Adreno 305 | Adreno 405 | |
| External memory | microSD, up to 256 GB (dedicated slot) | microSD, up to 256 GB (dedicated slot) | |
| Internal memory | 8 GB, 1 GB RAM | 16 GB, 2 GB RAM |
Benchmark
| Antutu 7 Total | |||
| GeekBench 4 Single Core | 573 | ||
| GeekBench 4 Multi-Core | 1447 | ||
| GeekBench 4 RenderScript | 1914 |
Communication and Connectivity
| SIM card | Nano-SIM | Nano-SIM | |
| Network | GSM / CDMA / EVDO / LTE | GSM / HSPA / LTE | |
| Bands | -2G - GSM 850 / 900 / 1800 / 1900 CDMA 800 / 1900 -3G - CDMA2000 1xEV-DO -4G - LTE band 4(1700/2100), 13(700) |
-2G - GSM 850 / 900 / 1800 / 1900 -3G - HSDPA 850 / 900 / 1900 / 2100 - EMEA, Asia HSDPA 850 / 900 / 2100 - Europe TD-SCDMA - Asia -4G - LTE band 3(1800), 7(2600), 8(900), 20(800) - Europe LTE band 1(2100), 3(1800), 7(2600), 8(900) - EMEA LTE band 1(2100), 3(1800), 7(2600), 8(900), 28(700), 38(2600), 39(1900), 40(2300), 41(2500) - Asia |
|
| Speed | HSPA, LTE | HSPA 42.2/5.76 Mbps, LTE Cat4 150/50 Mbps | |
| GPRS | Yes | Yes | |
| Edge | Yes | Yes | |
| Wi-Fi | Wi-Fi 802.11 b/g/n, DLNA, hotspot | Wi-Fi 802.11 a/b/g/n, dual-band, Wi-Fi Direct, DLNA, hotspot | |
| GPS | Yes, with A-GPS, GLONASS | Yes, with A-GPS, GLONASS | |
| NFC | TBC | Yes (optional) | |
| USB | microUSB 2.0 | microUSB 2.0, USB Host | |
| Bluetooth | 4.0, A2DP, aptX | 4.0, A2DP, aptX |
Music and Audio
| Radio | No | FM radio | |
| Headphone jack | Yes | Yes | |
| Others | - BoomSound dual front stereo speakers -Active noise cancellation with dedicated mic |
Other features
| Sensors | - Accelerometer, proximity | - Accelerometer, proximity, compass | |
| Other extras | |||
| Versions |
- For Verizon |
Reviews and Opinions on HTC Desire 612 and HTC Desire 820
If you had to recommend one of these phones to a friend, which one would it be and why? Share your arguments using the Add Opinion button!