Ulefone Armor X7 vs HTC One A9s Comparison and Differences
Smartphone 1
Ulefone Armor X7
Smartphone 2
HTC One A9s
Smartphone 3
Ulefone Armor X7 or HTC One A9s Specs Comparison
or
Common specs
| Brand and model | Ulefone Armor X7 | HTC One A9s | |
| Rating | (+0) | (+0) | |
| Release date | 2020, March 19 | 2016, September | |
| Dimensions (HxWxD) | 150 x 78.9 x 14.6 mm | 5.91 x 5.91 x 3.11 in | 146.5 x 71.5 x 8 mm | 5.77 x 5.77 x 2.81 in | |
| Weight | 234 g | 8.25 oz | 149.8 g | 5.28 oz | |
| Case | buy from Amazon | buy from Amazon | |
| Colors | Black, Orange | Black, Silver, Gold | |
| Battery | 4000 mAh, Non-removable Li-Po | 2300 mAh, Non-removable Li-Ion | |
| Battery life |
Stand by time - Up to 432 h (3G) Talking time - Up to 13 h (3G) |
||
| Approximate price | 80 EUR | 150 EUR | |
| Check price | from Amazon | from Amazon |
Screen
| Technology | IPS LCD | Super LCD | |
| Touchscreen | capacitive touchscreen | capacitive touchscreen | |
| Display colors | 16M | 16M | |
| Screen size | 5" in | 5" in | |
| Screen area | 68.9 cm2 | 68.9 cm2 | |
| Screen format | 16:9 (height:width) | 16:9 (height:width) | |
| Screen to body ratio | 58.2% | 65.8% | |
| Screen resolution | 720 x 1280 px | 720 x 1280 px | |
| Screen PPI /points per inch/ | 294 PPI | 294 PPI | |
| Screen protection | Corning Gorilla Glass (unspecified version) | ||
| Screen protector | buy from Amazon | buy from Amazon |
Camera and Video
| Rear camera, main | 13 MP, Single | 13 MP, Single | |
| Camera specs | -13 MP, f/2.2, (wide), AF | -13 MP, f/2.2, 28mm (wide), 1.12µm, AF | |
| Functions | Dual-LED flash | LED flash, panorama, HDR | |
| Video | 1080p@30fps | 1080p@30fps | |
| Front camera, selfie | 5 MP, Single | 5 MP, Single | |
| Specifications | 5 MP, f/2.2 | 5 MP, f/2.8, 34mm (standard), 1/5'', 1.12µm | |
| Video | 720p@30fps |
Performance
| Operating system - OS | Android 10.0 | Android 6.0 (Marshmallow); Sense UI | |
| Chipset | - Mediatek MT6761 Helio A20 (12 nm) | - Mediatek MT6755 Helio P10 (28 nm) | |
| CPU | - Quad-core 1.8 GHz Cortex-A53 | - Octa-core (4x1.8 GHz Cortex-A53 & 4x1.0 GHz Cortex-A53) | |
| GPU | PowerVR GE8320 | Mali-T860MP2 | |
| External memory | microSDXC (uses shared SIM slot) | microSD, up to 256 GB (dedicated slot) | |
| Internal memory | 16GB 2GB RAM | 32 GB, 3 GB RAM 16 GB, 2 GB RAM |
Benchmark
| Antutu 7 Total | |||
| GeekBench 4 Single Core | 727 | ||
| GeekBench 4 Multi-Core | 2655 | ||
| GeekBench 4 RenderScript | 1924 |
Communication and Connectivity
| SIM card | Hybrid Dual SIM (Nano-SIM, dual stand-by) | Nano-SIM | |
| 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 - LTE band 1(2100), 2(1900), 3(1800), 4(1700/2100), 5(850), 7(2600), 8(900), 12(700), 17(700), 19(800), 20(800) |
-2G - GSM 850 / 900 / 1800 / 1900 -3G - HSDPA 850 / 900 / 1900 / 2100 -4G - LTE band 1(2100), 2(1900), 3(1800), 4(1700/2100), 5(850), 7(2600), 8(900), 12(700), 17(700), 28(700), 38(2600), 40(2300) |
|
| Speed | HSPA 42.2/11.5 Mbps, LTE Cat6 300/150 Mbps | HSPA 42.2/5.76 Mbps, LTE-A (2CA) Cat6 300/50 Mbps | |
| GPRS | Yes | Yes | |
| Edge | Yes | Yes | |
| Wi-Fi | Wi-Fi 802.11 a/b/g/n/ac, Wi-Fi Direct, hotspot | Wi-Fi 802.11 a/b/g/n, hotspot | |
| GPS | Yes, with A-GPS, GLONASS, GALILEO | Yes, with A-GPS, GLONASS | |
| NFC | Yes | Yes (payments only) | |
| USB | microUSB 2.0 | microUSB 2.0 | |
| Bluetooth | 5.0, A2DP, LE | 4.2, A2DP |
Music and Audio
| Radio | FM radio | FM radio | |
| Headphone jack | Yes | Yes | |
| Others | - Active noise cancellation with dedicated mic |
Other features
| Sensors | - Fingerprint (rear-mounted), accelerometer, proximity, compass | - Fingerprint (front-mounted), accelerometer, proximity, compass | |
| Other extras |
- IP68/IP69K dust/water resistant (up to 1.5m for 30 mins) -Drop-to-concrete resistance from up to 1.2 m -MIL-STD-810G compliant |
- Fast battery charging |
Reviews and Opinions on Ulefone Armor X7 and HTC One A9s
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!