Ulefone Armor 21 vs Ulefone Armor X11 Pro Comparison and Differences
Smartphone 1
Ulefone Armor 21
Smartphone 2
Ulefone Armor X11 Pro
Smartphone 3
Ulefone Armor 21 or Ulefone Armor X11 Pro Specs Comparison
or
Common specs
| Brand and model | Ulefone Armor 21 | Ulefone Armor X11 Pro | |
| Rating | (+0) | (+0) | |
| Release date | 2023, May 30 | September, 2022 | |
| Dimensions (HxWxD) | 176 x 81.6 x 18.1 mm | 6.93 x 6.93 x 3.21 in | 158.2 x 76.7 x 14.6 mm | 6.23 x 6.23 x 3.02 in | |
| Weight | 400 g | 14.11 oz | 330 g | 11.64 oz | |
| Body Build | Rugged Smartphone, Polycarbonate | Rugged Smartphone, Plastic | |
| Case | buy from Amazon | buy from Amazon | |
| Colors | Black | Black | |
| Battery | 9600 mAh, Li-Po, non-removable | 8150 mAh, Li-Polymer, non-removable | |
| Approximate price | 280 EUR | ||
| Check price | from Amazon | from Amazon |
Screen
| Technology | IPS LCD | LCD IPS | |
| Touchscreen | capacitive touchscreen | capacitive touchscreen | |
| Display colors | 16M | 16M | |
| Screen size | 6.58" in | 5.45" in | |
| Screen area | 104.3 cm2 | ||
| Screen format | 20:9 (height:width) | 18:9 (height:width) | |
| Screen to body ratio | 72.6% | 63% | |
| Screen resolution | 1080 x 2408 px | 720 x 1440 px | |
| Screen PPI /points per inch/ | 401 PPI | 295 PPI | |
| Screen protection | Scratch resistant | Scratch resistant | |
| Other specs | - 120Hz - |
||
| Screen protector | buy from Amazon | buy from Amazon |
Camera and Video
| Rear camera, main | 64 MP, Dual | 16 MP, Quad | |
| Camera specs | -64 MP, f/1.9, (wide), 0.8µm, PDAF -24 MP, f/1.8, (night vision), 2 infrared night vision lights |
-16 MP, ƒ/ 1.8, (wide), 1.12 µm -2 MP, ƒ/ 2.4, (depth), -0.3 MP, (wide) |
|
| Functions | LED flash, HDR, panorama | Quad LED flash | |
| Video | 4K@30fps, 1080p@30fps | 1080p video | |
| Front camera, selfie | 16 MP, Single | 5 MP, Single | |
| Specifications | 16 MP, f/2.2, (wide), 1.0µm | 5 MP, ƒ/ 2.0, 1.12 µm | |
| Video | 1080p@30fps |
Performance
| Operating system - OS | Android 13 | Android 12 Snow Cone | |
| Chipset | - Mediatek Helio G99 (6 nm) | - Mediatek Helio G25 (12 nm) | |
| CPU | - Octa-core (2x2.2 GHz Cortex-A76 & 6x2.0 GHz Cortex-A55) | - Octa-Core (8x Cortex A53 2.0 GHz) | |
| GPU | Mali-G57 MC2 | IMG PowerVR GE8320 600MHz | |
| External memory | microSDXC (dedicated slot) | ||
| Internal memory | 256GB 8GB RAM | 4GB 64GB |
Benchmark
| Antutu 9 Total | 370006 | 101405 |
Communication and Connectivity
| SIM card | Dual SIM (Nano-SIM, dual stand-by) | Dual SIM, dual stand-by (Nano SIM + Nano SIM) | |
| Network | GSM / HSPA / LTE | 2G / 3G / 4G / | |
| 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, 34, 38, 39, 40, 41, 66 |
-2G - B2 (1900), B3 (1800), B5 (850), B8 (900) -3G - B1 (2100), B8 (900) -4G - B1 (2100), B3 (1800), B7 (2600), B8 (900), B19 (800), B20 (800) |
|
| Speed | HSPA, LTE | ||
| GPRS | Yes | Yes | |
| Edge | Yes | Yes | |
| Wi-Fi | Wi-Fi 802.11 a/b/g/n/ac, dual-band | 802.11a, 802.11b, 802.11g, 802.11n, 802.11n 5GHz, 802.11ac,Dual band ,Wi-Fi Hotspot ,Wi-Fi Direct ,Wi-Fi Display | |
| GPS | GPS, GLONASS, GALILEO, BDS | GPS, A-GPS, GLONASS, Galileo | |
| NFC | Yes | Yes | |
| USB | USB Type-C 2.0 | Yes, USB Type C, USB On-The-Go (OTG) | |
| Bluetooth | 5.2, A2DP, LE | Bluetooth 5, A2DP, HID |
Music and Audio
| Radio | Stereo FM radio, RDS, recording | Yes | |
| Headphone jack | Yes | Yes | |
| Others |
Other features
| Sensors | - Fingerprint (side-mounted), accelerometer, proximity, compass, gyro, barometer , Infrared port | - Fingerprint (side-mounted), Proximity, Accelerometer, compass, gyro , Infrared port | |
| Other extras |
- 33W 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 -Accessory connector (ulefone endoscope, microscope) |
- IP68, MIL-STD-810G -IP69K |
Reviews and Opinions on Ulefone Armor 21 and Ulefone Armor X11 Pro
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!