HTC One A9s vs Wiko Pulp Fab 4G Comparison and Differences
Smartphone 1
HTC One A9s
Smartphone 2
Wiko Pulp Fab 4G
Smartphone 3
HTC One A9s or Wiko Pulp Fab 4G Specs Comparison
or
Common specs
| Brand and model | HTC One A9s | Wiko Pulp Fab 4G | |
| Rating | (+) | (+) | |
| Release date | 2016, September | 2015, November | |
| Dimensions (HxWxD) | 146.5 x 71.5 x 8 mm | 5.77 x 5.77 x 2.81 in | 155.4 x 79.3 x 8.5 mm | 6.12 x 6.12 x 3.12 in | |
| Weight | 149.8 g | 5.28 oz | 168 g | 5.93 oz | |
| Case | buy from Amazon | buy from Amazon | |
| Colors | Black, Silver, Gold | Black, White, Chocolate, Electric Blue, Flashy Red | |
| Battery | 2300 mAh, Non-removable Li-Ion | 2820 mAh, Removable Li-Po | |
| Battery life |
Stand by time - Up to 432 h (3G) Talking time - Up to 13 h (3G) |
Stand by time - Up to 259 h (2G) / Up to 259 h (3G) Talking time - Up to 27 h 30 min (2G) / Up to 20 h 40 min (3G) |
|
| Approximate price | 150 EUR | ||
| Check price | from Amazon | from Amazon |
Screen
| Technology | Super LCD | IPS LCD | |
| Touchscreen | capacitive touchscreen | capacitive touchscreen | |
| Display colors | 16M | 16M | |
| Screen size | 5" in | 5.5" in | |
| Screen area | 68.9 cm2 | 83.4 cm2 | |
| Screen format | 16:9 (height:width) | 16:9 (height:width) | |
| Screen to body ratio | 65.8% | 67.7% | |
| Screen resolution | 720 x 1280 px | 720 x 1280 px | |
| Screen PPI /points per inch/ | 294 PPI | 267 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, 28mm (wide), 1.12µm, AF | -13 MP, AF | |
| Functions | LED flash, panorama, HDR | LED flash, panorama, HDR | |
| Video | 1080p@30fps | 1080p@30fps | |
| Front camera, selfie | 5 MP, Single | 5 MP, Single | |
| Specifications | 5 MP, f/2.8, 34mm (standard), 1/5'', 1.12µm | 5 MP | |
| Functions | LED flash |
Performance
| Operating system - OS | Android 6.0 (Marshmallow); Sense UI | Android 5.1 (Lollipop) | |
| Chipset | - Mediatek MT6755 Helio P10 (28 nm) | - Qualcomm MSM8916 Snapdragon 410 (28 nm) | |
| CPU | - Octa-core (4x1.8 GHz Cortex-A53 & 4x1.0 GHz Cortex-A53) | - Quad-core 1.2 GHz Cortex-A53 | |
| GPU | Mali-T860MP2 | Adreno 306 | |
| External memory | microSD, up to 256 GB (dedicated slot) | microSD, up to 64 GB | |
| Internal memory | 32 GB, 3 GB RAM 16 GB, 2 GB RAM | 16 GB, 2 GB RAM |
Benchmark
| Antutu 7 Total | |||
| GeekBench 4 Single Core | 727 | 510 | |
| GeekBench 4 Multi-Core | 2655 | 1338 | |
| GeekBench 4 RenderScript | 1924 |
Communication and Connectivity
| SIM card | Nano-SIM | Dual SIM (Micro-SIM, dual stand-by) | |
| Network | GSM / HSPA / LTE | GSM / HSPA / LTE | |
| Bands | -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) |
-2G - GSM 850 / 900 / 1800 / 1900 - SIM 1 & SIM 2 -3G - HSDPA 900 / 1900 / 2100 -4G - LTE band 1(2100), 3(1800), 7(2600), 20(800) |
|
| Speed | HSPA 42.2/5.76 Mbps, LTE-A (2CA) Cat6 300/50 Mbps | HSPA 42.2/11.5 Mbps, LTE Cat4 150/50 Mbps | |
| GPRS | Yes | Up to 107 kbps | |
| Edge | Yes | Up to 296 kbps | |
| Wi-Fi | Wi-Fi 802.11 a/b/g/n, hotspot | Wi-Fi 802.11 b/g/n, Wi-Fi Direct, hotspot | |
| GPS | Yes, with A-GPS, GLONASS | Yes, with A-GPS | |
| NFC | Yes (payments only) | ||
| USB | microUSB 2.0 | microUSB 2.0, USB Host | |
| Bluetooth | 4.2, A2DP | 4.0, A2DP | |
| Harmful irradiation |
SAR EU - 0.38 W/kg (head) 0.97 W/kg (body) |
Music and Audio
| Radio | FM radio | FM radio | |
| Headphone jack | Yes | Yes | |
| Others | - Active noise cancellation with dedicated mic |
Other features
| Sensors | - Fingerprint (front-mounted), accelerometer, proximity, compass | - Accelerometer, proximity, compass | |
| Other extras |
- Fast battery charging |
||
| Versions |
- For Europe |
Reviews and Opinions on HTC One A9s and Wiko Pulp Fab 4G
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!