HTC One vs BLU Dash 4.5 Comparison and Differences
Smartphone 1
HTC One
Smartphone 2
BLU Dash 4.5
Smartphone 3
HTC One or BLU Dash 4.5 Specs Comparison
or
Common specs
| Brand and model | HTC One | BLU Dash 4.5 | |
| Rating | (+) | (+) | |
| Release date | 2013, February | 2013, July | |
| Dimensions (HxWxD) | 137.4 x 68.2 x 9.3 mm | 5.41 x 5.41 x 2.69 in | 133 x 65 x 12 mm | 5.24 x 5.24 x 2.56 in | |
| Weight | 143 g | 5.04 oz | 144 g | 5.08 oz | |
| Body Build | Aluminum body | ||
| Case | buy from Amazon | buy from Amazon | |
| Colors | Black, Silver, Red, Blue, Gold | Black | |
| Battery | 2300 mAh, Non-removable Li-Po | 2000 mAh, Removable Li-Ion | |
| Battery life |
Stand by time - Up to 500 h (2G) / Up to 480 h (3G) Talking time - Up to 27 h (2G) / Up to 18 h (3G) |
Stand by time - Up to 900 h (2G) / Up to 750 h (3G) Talking time - Up to 24 h (2G) / Up to 10 h (3G) |
|
| Approximate price | 270 EUR | 100 EUR | |
| Check price | from Amazon | from Amazon |
Screen
| Technology | Super LCD3 | TFT | |
| Touchscreen | capacitive touchscreen | capacitive touchscreen | |
| Display colors | 16M | 16M | |
| Screen size | 4.7" in | 4.5" in | |
| Screen area | 60.9 cm2 | 55.8 cm2 | |
| Screen format | 16:9 (height:width) | 16:9 (height:width) | |
| Screen to body ratio | 65.0% | 64.5% | |
| Screen resolution | 1080 x 1920 px | 480 x 854 px | |
| Screen PPI /points per inch/ | 469 PPI | 218 PPI | |
| Screen protection | Corning Gorilla Glass 2 | ||
| Screen protector | buy from Amazon | buy from Amazon |
Camera and Video
| Rear camera, main | 4 MP, Single | 5 MP, Single | |
| Camera specs | -4 MP, f/2.0, 28mm (wide), 1/3'', 2µm, OIS, AF | -5 MP | |
| Functions | LED flash | LED flash | |
| Video | 1080p@30fps, 720p@60fps, HDR, stereo sound rec. | 720p@30fps | |
| Front camera, selfie | 2.1 MP, Single | 0.3 MP, Single | |
| Specifications | 2.1 MP | VGA | |
| Functions | HDR | ||
| Video | 1080p@30fps |
Performance
| Operating system - OS | Android 4.1.2 (Jelly Bean), upgradable to 5 (Lollipop); Sense UI 5 | Android 4.2 (Jelly Bean) | |
| Chipset | - Qualcomm APQ8064T Snapdragon 600 | - Mediatek MT6589M (28 nm) | |
| CPU | - Quad-core 1.7 GHz Krait 300 | - Quad-core 1.2 GHz Cortex-A7 | |
| GPU | Adreno 320 | PowerVR SGX544 | |
| External memory | No | microSD, up to 32 GB (dedicated slot) | |
| Internal memory | 32/64 GB, 2 GB RAM | 4 GB, 512 MB RAM |
Benchmark
| Antutu 7 Total | |||
| GeekBench 5 Single Core | 109 | ||
| GeekBench 5 Multi-Core | 398 | ||
| GeekBench 4 Single Core | 705 | ||
| GeekBench 4 Multi-Core | 1652 | ||
| GeekBench 4 RenderScript | 791 |
Communication and Connectivity
| SIM card | Micro-SIM | Dual SIM (Mini-SIM, dual stand-by) | |
| Network | GSM / HSPA / LTE | GSM / HSPA | |
| Bands | -2G - GSM 850 / 900 / 1800 / 1900 -3G - HSDPA 850 / 900 / 1900 / 2100 -4G - LTE band 3(1800), 7(2600), 20(800) - EMEA LTE band 2(1900), 4(1700/2100), 5(850), 17(700) - AT&T LTE band 3(1800), 7(2600) - Asia LTE band 4(1700/2100), 17(700) - T-Mobile |
-2G - GSM 850 / 900 / 1800 / 1900 - SIM 1 & SIM 2 |
|
| Speed | HSPA, LTE Cat3 100/50 Mbps | HSPA 42.2/5.76 Mbps | |
| GPRS | Yes | Class 12 | |
| Edge | Yes | Class 12 | |
| Wi-Fi | Wi-Fi 802.11 a/b/g/n/ac, Wi-Fi Direct, DLNA, hotspot | Wi-Fi 802.11 a/b/g/n, dual-band, Wi-Fi Direct, hotspot | |
| GPS | Yes, with A-GPS, GLONASS | Yes, with A-GPS | |
| NFC | Yes (Market dependent) | ||
| USB | microUSB 2.0 (MHL TV-out), USB Host | microUSB 2.0 | |
| Bluetooth | 4.0, A2DP, aptX | 3.0 | |
| Harmful irradiation |
SAR - 0.66 W/kg (head) 0.40 W/kg (body) SAR EU - 0.86 W/kg (head) 0.36 W/kg (body) |
Music and Audio
| Radio | Stereo FM radio, RDS | Stereo FM radio | |
| Headphone jack | Yes | Yes | |
| Others | - Beats Audio -Active noise cancellation with dedicated mic |
Other features
| Sensors | - Accelerometer, gyro, proximity, compass , Infrared port | - Accelerometer, gyro, proximity, compass | |
| Other extras | |||
| Versions |
- D300 Single SIM D310 Dual SIM |
Reviews and Opinions on HTC One and BLU Dash 4.5
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!