Cubot CUBOT S600 vs Xiaomi Poco M3 Comparison and Differences
Smartphone 1
Cubot CUBOT S600
Smartphone 2
Xiaomi Poco M3
Smartphone 3
Cubot CUBOT S600 or Xiaomi Poco M3 Specs Comparison
or
Common specs
| Brand and model | Cubot CUBOT S600 | Xiaomi Poco M3 | |
| Rating | (+0) | (+0) | |
| Release date | November, 2015 | 2020, November 24 | |
| Dimensions (HxWxD) | 146.5 x 71.3 x 7.5 mm | 5.77 x 5.77 x 2.81 in | 162.3 x 77.3 x 9.6 mm | 6.39 x 6.39 x 3.04 in | |
| Weight | 170 g | 6 oz | 198 g | 6.98 oz | |
| Body Build | Glass, Metal | Glass front (Gorilla Glass 3), plastic back, plastic frame | |
| Case | buy from Amazon | buy from Amazon | |
| Colors | Black, White, Gold | Cool Blue, Poco Yellow, Power Black | |
| Battery | 2700 mAh, Li-Ion, non-removable | 6000 mAh, Li-Po, non-removable | |
| Approximate price | |||
| Check price | from Amazon | from Amazon |
Screen
| Technology | LCD IPS | IPS LCD | |
| Touchscreen | capacitive touchscreen | capacitive touchscreen | |
| Display colors | 16M | 16M | |
| Screen size | 5" in | 6.53" in | |
| Screen area | 104.7 cm2 | ||
| Screen format | 16:9 (height:width) | 19.5:9 (height:width) | |
| Screen to body ratio | 66% | 83.4% | |
| Screen resolution | 720 x 1280 px | 1080 x 2340 px | |
| Screen PPI /points per inch/ | 294 PPI | 395 PPI | |
| Screen protection | Corning Gorilla Glass 3 | ||
| Other specs | - 400 nits (typ) | ||
| Screen protector | buy from Amazon | buy from Amazon |
Camera and Video
| Rear camera, main | 13 MP, Single | 48 MP, Triple | |
| Camera specs | -13 MP, ƒ/ 2.0, (wide), 1.13 µm | -48 MP, f/1.8, (wide), 1/2.0'', 0.8µm, PDAF -2 MP, f/2.4, (macro) -2 MP, f/2.4, (depth) |
|
| Functions | Dual LED flash | LED flash, HDR, panorama | |
| Video | 1080p video | 1080p@30fps | |
| Front camera, selfie | 5 MP, Single | 8 MP, Single | |
| Specifications | 5 MP, ƒ/ | 8 MP, f/2.1, (wide), 1/4.0'', 1.12µm | |
| Functions | Panorama | ||
| Video | 1080p@30fps |
Performance
| Operating system - OS | Android 5.0 Lollipop | Android 10, MIUI 12 | |
| Chipset | - MediaTek MT6735A (28 nm) | - Qualcomm SM6115 Snapdragon 662 (11 nm) | |
| CPU | - Quad-Core (4x Cortex A53 1.3 GHz) | - Octa-core (4x2.0 GHz Kryo 260 Gold & 4x1.8 GHz Kryo 260 Silver) | |
| GPU | ARM Mali-T720 MP2 | Adreno 610 | |
| External memory | microSDXC (dedicated slot) | ||
| Internal memory | 2GB 16GB, 2GB · 16GB | 64GB 4GB RAM, 128GB 4GB RAM |
Benchmark
| Antutu 8 Total | 185320 | ||
| GeekBench 6 Single Core | 330 | ||
| GeekBench 6 Multi Core | 1032 | ||
| GeekBench 6 OpenCL | 290 | ||
| GeekBench 6 Vulkan | 481 | ||
| GeekBench 5 Single Core | 309 | ||
| GeekBench 5 Multi-Core | 1285 |
Communication and Connectivity
| SIM card | Dual SIM, dual stand-by (Micro SIM + Nano SIM) | Dual SIM (Nano-SIM, dual stand-by) | |
| Network | 2G / 3G / 4G / | GSM / HSPA / LTE | |
| Bands | -2G - B2 (1900), B3 (1800), B5 (850), B8 (900) -3G - B1 (2100), B2 (1900), B5 (850), B8 (900) -4G - B1 (2100), B3 (1800), B7 (2600), B20 (800) |
-2G - GSM 850 / 900 / 1800 / 1900 - SIM 1 & SIM 2 -3G - HSDPA 850 / 900 / 1700(AWS) / 1900 / 2100 -4G - 1, 2, 3, 4, 5, 7, 8, 20, 28, 38, 40, 41 |
|
| Speed | HSPA 42.2/5.76 Mbps, LTE-A | ||
| GPRS | Yes | Yes | |
| Edge | Yes | Yes | |
| Wi-Fi | 802.11b, 802.11g, 802.11n,Wi-Fi Hotspot | Wi-Fi 802.11 a/b/g/n/ac, dual-band, Wi-Fi Direct, hotspot | |
| GPS | GPS, A-GPS | Yes, with A-GPS, GLONASS, BDS | |
| NFC | No | No | |
| USB | Yes, USB On-The-Go (OTG) | USB Type-C 2.0, USB On-The-Go | |
| Bluetooth | Bluetooth 4.0, A2DP | 5.0, A2DP, LE | |
| Harmful irradiation |
SAR EU - 0.352 W/Kg (head), 0.400 W/Kg (body) |
Music and Audio
| Radio | Yes | FM radio | |
| Headphone jack | Yes | Yes | |
| Others | - 24-bit/192kHz audio |
Other features
| Sensors | - Fingerprint (rear-mounted), Proximity, Accelerometer, compass , Infrared port | - Fingerprint (side-mounted), accelerometer, proximity, compass , Infrared port | |
| Other extras |
- Fast charging 18W -Reverse charging |
Reviews and Opinions on Cubot CUBOT S600 and Xiaomi Poco M3
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!