BLU R2 vs ZTE nubia Z17 mini Comparison and Differences
Smartphone 1
BLU R2
Smartphone 2
ZTE nubia Z17 mini
Smartphone 3
BLU R2 or ZTE nubia Z17 mini Specs Comparison
or
Common specs
| Brand and model | BLU R2 | ZTE nubia Z17 mini | |
| Rating | (+0) | (+0) | |
| Release date | 2017, July | 2017, April | |
| Dimensions (HxWxD) | 150.3 x 74.3 x 9.6 mm | 5.92 x 5.92 x 2.93 in | 146.7 x 72.5 x 7.5 mm | 5.78 x 5.78 x 2.85 in | |
| Weight | 156 g | 5.5 oz | 155 g | 5.47 oz | |
| Case | buy from Amazon | buy from Amazon | |
| Colors | Black, Gold, Rose Gold, Silver | Elegant Black, Gold Black, Champagne Gold, Red | |
| Battery | 3000 mAh, Non-removable Li-Po | 2950 mAh, Non-removable Li-Po | |
| Battery life |
Stand by time - Up to 725 h (2G) / Up to 625 h (3G) Talking time - Up to 26 h (2G) / Up to 16 h (3G) |
||
| Approximate price | 170 EUR | ||
| Check price | from Amazon | from Amazon |
Screen
| Technology | IPS LCD | LTPS IPS LCD | |
| Touchscreen | capacitive touchscreen | capacitive touchscreen | |
| Display colors | 16M | 16M | |
| Screen size | 5.2" in | 5.2" in | |
| Screen area | 74.5 cm2 | 74.5 cm2 | |
| Screen format | 16:9 (height:width) | 16:9 (height:width) | |
| Screen to body ratio | 66.8% | 70.1% | |
| Screen resolution | 720 x 1280 px | 1080 x 1920 px | |
| Screen PPI /points per inch/ | 282 PPI | 424 PPI | |
| Screen protection | Corning Gorilla Glass (unspecified version) | ||
| Screen protector | buy from Amazon | buy from Amazon |
Camera and Video
| Rear camera, main | 8 MP, Single | 13 MP, Single | |
| Camera specs | -8 MP | -13 MP, f/2.2, 1/3'', 1.12µm, PDAF -2 MP, depth sensor |
|
| Functions | Dual-LED dual-tone flash | Dual-LED flash, HDR | |
| Video | 1080p@30fps | 2160p@30fps, 1080p@30fps | |
| Front camera, selfie | 8 MP, Single | 16 MP, Single | |
| Specifications | 8 MP | 16 MP, f/2.0 | |
| Functions | dual-LED dual-tone flash | ||
| Video | 1080p@30fps |
Performance
| Operating system - OS | Android 7.0 (Nougat) | Android 6.1 (Marshmallow); nubia UI 4 | |
| Chipset | - Mediatek MT6580 (28 nm) | - Qualcomm MSM8976 Snapdragon 652 (28 nm) - Qualcomm MSM8976 Pro Snapdragon 653 (28 nm) - High edition |
|
| CPU | - Quad-core 1.3 GHz Cortex-A7 | - Octa-core (4x1.95 GHz Cortex-A72 & 4x1.4 GHz Cortex-A53) | |
| GPU | Mali-400MP2 | Adreno 510 | |
| External memory | microSD, up to 64 GB | microSD, up to 256 GB (uses SIM 2 slot) | |
| Internal memory | 8 GB, 1 GB RAM | 64 GB, 4 GB RAM - Standard edition 64 GB, 6 GB RAM - High edition |
Benchmark
| GeekBench 6 Single Core | 270 | ||
| GeekBench 6 Multi Core | 613 | ||
| GeekBench 5 Single Core | 274 | ||
| GeekBench 5 Multi-Core | 654 | ||
| GeekBench 4 Single Core | 1372 | ||
| GeekBench 4 Multi-Core | 4259 | ||
| GeekBench 4 RenderScript | 4265 |
Communication and Connectivity
| SIM card | Dual SIM (Micro-SIM) | Hybrid Dual SIM (Nano-SIM, dual stand-by) | |
| Network | GSM / HSPA | GSM / HSPA / LTE | |
| Bands | -2G - GSM 850 / 900 / 1800 / 1900 - SIM 1 & SIM 2 |
-2G - GSM 850 / 900 / 1800 / 1900 - SIM 1 & SIM 2 -3G - HSDPA 850 / 900 / 1900 / 2100 -4G - LTE band 1(2100), 3(1800), 5(850), 7(2600), 38(2600), 39(1900), 40(2300), 41(2500) |
|
| Speed | HSPA 21.1/5.76 Mbps | HSPA, LTE | |
| GPRS | Yes | Yes | |
| Edge | Yes | Yes | |
| Wi-Fi | Wi-Fi 802.11 b/g/n, hotspot | Wi-Fi 802.11 a/b/g/n/ac, dual-band, Wi-Fi Direct, DLNA, hotspot | |
| GPS | Yes, with A-GPS | Yes, with A-GPS, GLONASS, BDS | |
| NFC | Yes | ||
| USB | microUSB 2.0 | Type-C 1.0 reversible connector, USB On-The-Go | |
| Bluetooth | 4.0, A2DP | 4.1, A2DP, LE |
Music and Audio
| Radio | FM radio | FM radio | |
| Headphone jack | Yes | Yes | |
| Others | - DTS sound -Active noise cancellation with dedicated mic |
Other features
| Sensors | - Fingerprint (rear-mounted), accelerometer, proximity, compass | - Fingerprint (rear-mounted), accelerometer, gyro, proximity, compass | |
| Other extras |
- Fast battery charging |
||
| Versions |
- Also known as ZTE nubia Z12 mini |
Reviews and Opinions on BLU R2 and ZTE nubia Z17 mini
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!