Xolo Black 3GB vs Xiaomi Redmi Note 3 (MediaTek) Comparison and Differences
Smartphone 1

Xolo Black 3GB
Smartphone 2
-794.jpg)
Xiaomi Redmi Note 3 (MediaTek)
Smartphone 3
Xolo Black 3GB or Xiaomi Redmi Note 3 (MediaTek) Specs Comparison
or
Common specs
Brand and model | Xolo Black 3GB | Xiaomi Redmi Note 3 (MediaTek) | |
Rating | 0) | (+0) | (+|
Release date | 2015, December | 2015, November | |
Dimensions (HxWxD) | 155.5 x 76.6 x 7.3 mm | 6.12 x 6.12 x 3.02 in | 150 x 76 x 8.7 mm | 5.91 x 5.91 x 2.99 in | |
Weight | 0 g | 0 oz | 164 g | 5.78 oz | |
Body Build | Front/back glass (Gorilla Glass 3), aluminum frame | ||
Case | buy from Amazon | buy from Amazon | |
Colors | Black | Silver, Gray, Gold | |
Battery | 3200 mAh, Non-removable Li-Po | 4000 mAh, Non-removable Li-Po | |
Battery life |
Stand by time - Up to 798 h (2G) / Up to 634 h (3G) Talking time - Up to 36 h (2G) / Up to 27 h (3G) |
Stand by time - Up to 264 h (3G) Music play - Up to 60 h |
|
Approximate price | 180 EUR | ||
Check price | from Amazon | from Amazon |
Screen
Technology | IPS LCD | IPS LCD | |
Touchscreen | capacitive touchscreen | capacitive touchscreen | |
Display colors | 16M | 16M | |
Screen size | 5.5" in | 5.5" in | |
Screen area | 83.4 cm2 | 82.6 cm2 | |
Screen format | 16:9 (height:width) | 16:9 (height:width) | |
Screen to body ratio | 70.0% | 72.4% | |
Screen resolution | 1080 x 1920 px | 1080 x 1920 px | |
Screen PPI /points per inch/ | 401 PPI | 403 PPI | |
Screen protection | Corning Gorilla Glass 3 | ||
Screen protector | buy from Amazon | buy from Amazon |
Camera and Video
Rear camera, main | 13 MP, Dual | 13 MP, Single | |
Camera specs | -13 MP, f/2.0, AF -2 MP, f/2.4, depth sensor |
-13 MP, PDAF, f/2.2 | |
Functions | LED flash, panorama, HDR | Dual-LED dual-tone flash, HDR, panorama | |
Video | 1080p@30fps | 1080p@30fps | |
Front camera, selfie | 5 MP, Single | 5 MP, Single | |
Specifications | 5 MP | 5 MP, f/2.0 | |
Functions | LED flash | ||
Video | 1080p@30fps |
Performance
Operating system - OS | Android 5.0 (Lollipop) ; HIVE Atlas UI | Android 5.0.2 (Lollipop); MIUI 7 | |
Chipset | - Qualcomm MSM8939 Snapdragon 615 (28 nm) | - Mediatek MT6795 Helio X10 (28 nm) | |
CPU | - Octa-core (4x1.5 GHz Cortex-A53 & 4x1.0 GHz Cortex-A53) | - Octa-core 2.0 GHz Cortex-A53 | |
GPU | Adreno 405 | PowerVR G6200 | |
External memory | microSD, up to 32 GB | No | |
Internal memory | 16 GB, 3 GB RAM | 16 GB, 2 GB RAM 32 GB, 3 GB RAM |
Benchmark
GeekBench 6 Single Core | 259 | ||
GeekBench 6 Multi Core | 609 | ||
GeekBench 5 Single Core | 260 | ||
GeekBench 5 Multi-Core | 698 | ||
GeekBench 4 Single Core | 1399 |
Communication and Connectivity
SIM card | Dual SIM | Dual SIM (Micro-SIM, dual stand-by) | |
Network | GSM / HSPA / LTE | GSM / HSPA / LTE | |
Bands | -2G - GSM 850 / 900 / 1800 / 1900 - SIM 1 & SIM 2 -3G - HSDPA 900 / 2100 -4G - LTE band 3(1800), 40(2300) |
-2G - GSM 900 / 1800 / 1900 - SIM 1 & SIM 2 -3G - HSDPA 850 / 900 / 1900 / 2100 TD-SCDMA -4G - LTE band 1(2100), 3(1800), 7(2600), 38(2600), 39(1900), 40(2300), 41(2500) |
|
Speed | HSPA 42.2/7.2 Mbps, LTE Cat4 150/50 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, WiFi Direct, hotspot | |
GPS | Yes, with A-GPS, GLONASS | Yes, with A-GPS, GLONASS, BDS | |
NFC | |||
USB | microUSB 2.0, USB Host | microUSB 2.0, USB On-The-Go | |
Bluetooth | 4.0, A2DP | 4.1, A2DP, LE | |
Harmful irradiation |
SAR EU - 0.13 W/kg (head) 0.27 W/kg (body) |
SAR EU - 0.33 W/kg (head) |
Music and Audio
Radio | FM radio | Stereo FM radio, recording | |
Headphone jack | Yes | Yes | |
Others | - 24-bit/192kHz audio -Active noise cancellation with dedicated mic |
Other features
Sensors | - Accelerometer, gyro, proximity, compass | - Fingerprint (rear-mounted), accelerometer, gyro, proximity, compass , Infrared port | |
Other extras |
- Fast battery charging |
||
Versions |
- For India |
Reviews and Opinions on Xolo Black 3GB and Xiaomi Redmi Note 3 (MediaTek)
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!