Ulefone Armor X12 Pro vs Blackview BV7200 Comparison and Differences
Smartphone 1
Ulefone Armor X12 Pro
Smartphone 2
Blackview BV7200
Smartphone 3
Ulefone Armor X12 Pro or Blackview BV7200 Specs Comparison
or
Common specs
| Brand and model | Ulefone Armor X12 Pro | Blackview BV7200 | |
| Rating | (+0) | (+0) | |
| Release date | 2023, August | 2022, October 26 | |
| Dimensions (HxWxD) | 157.2 x 76.8 x 14.3 mm | 6.19 x 6.19 x 3.02 in | 165.3 x 81.6 x 16 mm | 6.51 x 6.51 x 3.21 in | |
| Weight | 257 g | 9.07 oz | 288 g | 10.16 oz | |
| Body Build | Rugged Smartphone, Polycarbonate | Rugged Smartphone, Polycarbonate | |
| Case | buy from Amazon | buy from Amazon | |
| Colors | Black, Black/Orange, Black/Green | Black, Orange, Green | |
| Battery | 4860 mAh, Li-Po, non-removable | 5180 mAh, Li-Po, non-removable | |
| Approximate price | 160 EUR | 250 EUR | |
| Check price | from Amazon | from Amazon |
Screen
| Technology | LCD IPS | LCD IPS | |
| Touchscreen | capacitive touchscreen | capacitive touchscreen | |
| Display colors | 16M | 16M | |
| Screen size | 5.45" in | 6.1" in | |
| Screen area | 76.7 cm2 | 91.3 cm2 | |
| Screen format | 18:9 (height:width) | 19.5:9 (height:width) | |
| Screen to body ratio | 63.5% | 67.7% | |
| Screen resolution | 720 x 1440 px | 720 x 1560 px | |
| Screen PPI /points per inch/ | 295 PPI | 282 PPI | |
| Screen protection | Corning Gorilla Glass 3 | ||
| Other specs | - 380 nits (typ) | ||
| Screen protector | buy from Amazon | buy from Amazon |
Camera and Video
| Rear camera, main | 13 MP, Single | 50 MP, Dual | |
| Camera specs | -13 MP, f/2.2, (wide), 1.12µm, PDAF | -50 MP, f/1.8, (wide), 1/2.76'', 0.64µm, PDAF -8 MP, 117˚ (ultrawide) |
|
| Functions | LED flash | Dual-LED flash, HDR, panorama | |
| Video | 1080p@30fps | 1080p@30fps | |
| Front camera, selfie | 8 MP, Single | 8 MP, Single | |
| Specifications | 8 MP, f/2.0, (wide), 1.4µm | 8 MP, f/2.2, (wide), 1/4'', 1.12µm | |
| Video | 1080p@30fps |
Performance
| Operating system - OS | Android 13 | Android 12, Doke-OS 3.0 | |
| Chipset | - Mediatek Helio G36 (12 nm) | - MediaTek MT6769Z Helio G85 (12nm) | |
| CPU | - Octa-core (4x2.2 GHz Cortex-A53 & 4x1.7 GHz Cortex-A53) | - Octa-core (2x2.0 GHz Cortex-A75 & 6x1.8 GHz Cortex-A55) | |
| GPU | PowerVR GE8320 | Mali-G52 MC2 | |
| External memory | microSDXC (dedicated slot) | microSDXC (uses shared SIM slot) | |
| Internal memory | 64GB 4GB RAM | 128GB 6GB RAM |
Benchmark
| Antutu 9 Total | 127002 | 200005 | |
| GeekBench 5 Single Core | 188 | 346 | |
| GeekBench 5 Multi-Core | 1022 | 1268 |
Communication and Connectivity
| SIM card | Dual SIM (Nano-SIM, dual stand-by) | Hybrid Dual SIM (Nano-SIM, dual stand-by) | |
| Network | GSM / HSPA / LTE | GSM / HSPA / LTE | |
| Bands | -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, 12, 17, 19, 20, 28 |
-2G - GSM 850 / 900 / 1800 / 1900 - SIM 1 & SIM 2 -3G - HSDPA 900 / 2100 -4G - 1, 3, 7, 8, 20, 40 |
|
| Speed | HSPA, LTE | HSPA, LTE | |
| GPRS | Yes | Yes | |
| Edge | Yes | Yes | |
| Wi-Fi | Wi-Fi 802.11 a/b/g/n/ac, dual-band | Wi-Fi 802.11 a/b/g/n/ac, dual-band, hotspot | |
| GPS | GPS, GLONASS, GALILEO, BDS | GPS, GLONASS, GALILEO, BDS | |
| NFC | Yes | Yes | |
| USB | USB Type-C 2.0 | USB Type-C, USB On-The-Go | |
| Bluetooth | 5.0, A2DP, LE | 5.0, A2DP, LE |
Music and Audio
| Radio | Wireless FM radio, RDS, recording | FM radio | |
| Headphone jack | Yes | No |
Other features
| Sensors | - Accelerometer, proximity , Infrared port | - Fingerprint (side-mounted), gyro, accelerometer, compass, barometer | |
| Other extras |
- 10W Fast charging - IP68/IP69K dust/water resistant (up to 1.5m for 30 min) -Drop-to-concrete resistance from up to 1.5m -MIL-STD-810H compliant |
- Fast charging 18W -Reverse charging - IP68/IP69K dust/water resistant (up to 1.5m for 30 mins) -Drop-to-concrete resistance from up to 1.8 m -MIL-STD-810H compliant |
Reviews and Opinions on Ulefone Armor X12 Pro and Blackview BV7200
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!