Ulefone Armor 22 vs Cubot KingKong AX Comparison and Differences
Smartphone 1
Ulefone Armor 22
Smartphone 2
Cubot KingKong AX
Smartphone 3
Ulefone Armor 22 or Cubot KingKong AX Specs Comparison
or
Common specs
| Brand and model | Ulefone Armor 22 | Cubot KingKong AX | |
| Rating | (+) | (+) | |
| Release date | 2023, August 14 | 2024, March | |
| Dimensions (HxWxD) | 176.8 x 84.9 x 15 mm | 6.96 x 6.96 x 3.34 in | 172 x 80.9 x 12.7 mm | 6.77 x 6.77 x 3.19 in | |
| Weight | 324 g | 11.43 oz | 296 g | 10.44 oz | |
| Body Build | Rugged Smartphone, Polycarbonate | ||
| Case | buy from Amazon | buy from Amazon | |
| Colors | Black, Black/Green | Black | |
| Battery | 6600 mAh, Li-Polymer, non-removable | 5100 mAh, , non-removable | |
| Approximate price | € 264.9 | ||
| Check price | from Amazon | from Amazon |
Screen
| Technology | LCD IPS | IPS LCD | |
| Touchscreen | capacitive touchscreen | capacitive touchscreen | |
| Display colors | 16M | 16M | |
| Screen size | 6.58" in | 6.58" in | |
| Screen area | 104.3 cm2 | 104.3 cm2 | |
| Screen format | 20:9 (height:width) | 20:9 (height:width) | |
| Screen to body ratio | 69.5% | 75.0% | |
| Screen resolution | 1080 x 2408 px | 1080 x 2408 px | |
| Screen PPI /points per inch/ | 401 PPI | 401 PPI | |
| Screen protection | Scratch resistant | ||
| Other specs | - 120 Hz | - 120Hz -Secondary screen on the back |
|
| Screen protector | buy from Amazon | buy from Amazon |
Camera and Video
| Rear camera, main | 64 MP, Triple | 100 MP, Dual | |
| Camera specs | -64 MP, f/1.9, (wide), 1/1.7", 0.8µm, PDAF -64 MP, f/1.8, (night vision), 2 infrared night vision lights |
-100 MP, (wide), PDAF -5 MP, (macro) -Auxiliary lens |
|
| Functions | LED flash, HDR, panorama | LED flash | |
| Video | 1440p@30fps, 1080p@30fps | Yes | |
| Front camera, selfie | 8 MP, Single | 32 MP, Single | |
| Specifications | 8 MP, f/2.0, (wide), 1/4.0", 1.12µm | 32 MP | |
| Video | 1080p@30fps | Yes |
Performance
| Operating system - OS | Android 13 Tiramisu | Android 14 | |
| Chipset | - Mediatek Helio G96 (12 nm) | - Mediatek Helio G99 (6 nm) | |
| CPU | - Octa-core (2x2.05 GHz Cortex-A76 & 6x2.0 GHz Cortex-A55) | - Octa-core (2x2.2 GHz Cortex-A76 & 6x2.0 GHz Cortex-A55) | |
| GPU | Mali-G57 MC2 | Mali-G57 MC2 | |
| External memory | microSDXC (dedicated slot) | microSDXC (uses shared SIM slot) | |
| Internal memory | 128GB 8GB RAM, 256GB 8GB RAM | 256GB 12GB RAM |
Benchmark
| Antutu 9 Total | 302002 | ||
| GeekBench 5 Single Core | 564 | ||
| GeekBench 5 Multi-Core | 1852 |
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, 34, 38, 39, 40, 41, 66 |
-2G - GSM 850 / 900 / 1800 / 1900 - SIM 1 & SIM 2 -3G - HSDPA 800 / 850 / 900 / 1700(AWS) / 1900 / 2100 -4G - 1, 2, 3, 4, 5, 7, 8, 12, 13, 17, 18, 19, 20, 25, 26, 28, 38, 39, 40, 41, 66 |
|
| 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 | |
| GPS | GPS, GLONASS, GALILEO, BDS | GPS, GLONASS, GALILEO, BDS | |
| NFC | Yes | Yes | |
| USB | USB Type-C 2.0 | USB Type-C, OTG | |
| Bluetooth | 5.2, A2DP, LE | 5.2, A2DP, LE |
Music and Audio
| Radio | Wireless FM radio, RDS, recording | ||
| Headphone jack | Yes |
Other features
| Sensors | - Fingerprint (side-mounted), accelerometer, proximity, compass, gyro, barometer , Infrared port | - Fingerprint (side-mounted), accelerometer, gyro, proximity, compass | |
| 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 |
- 33W Fast charging - IP68/IP69K dust/water resistant (up to 1.5m for 30 min) |
Reviews and Opinions on Ulefone Armor 22 and Cubot KingKong AX
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!