HiSense H20 vs Samsung Galaxy A32 5G Comparison and Differences
Smartphone 1

HiSense H20
Smartphone 2

Samsung Galaxy A32 5G
Smartphone 3
HiSense H20 or Samsung Galaxy A32 5G Specs Comparison
or
Common specs
Brand and model | HiSense H20 | Samsung Galaxy A32 5G | |
Rating | 0) | (+0) | (+|
Release date | June, 2018 | 2021, January 13 | |
Dimensions (HxWxD) | 148.6 x 71.2 x 8.0 mm | 5.85 x 5.85 x 2.8 in | 164.2 x 76.1 x 9.1 mm | 6.46 x 6.46 x 3 in | |
Weight | 164 g | 5.78 oz | 205 g | 7.23 oz | |
Body Build | Metal | ||
Case | buy from Amazon | buy from Amazon | |
Colors | Black, Blue, Gold | Awesome Black, Awesome White, Awesome Blue, Awesome Violet | |
Battery | 3020 mAh, Li-Polymer, non-removable | 5000 mAh, Li-Ion, non-removable | |
Approximate price | $ 723 | 250 EUR | |
Check price | from Amazon | from Amazon |
Screen
Technology | LCD IPS | TFT | |
Touchscreen | capacitive touchscreen | capacitive touchscreen | |
Display colors | 16M | 16M | |
Screen size | 5.84" in | 6.5" in | |
Screen area | 102.0 cm2 | ||
Screen format | 18:9 (height:width) | 20:9 (height:width) | |
Screen to body ratio | 81% | 81.6% | |
Screen resolution | 1080 x 2220 px | 720 x 1600 px | |
Screen PPI /points per inch/ | 423 PPI | 270 PPI | |
Screen protector | buy from Amazon | buy from Amazon |
Camera and Video
Rear camera, main | 12 MP, Dual | 48 MP, Quad | |
Camera specs | -12,2 MP, Unknow, (wide), -5 MP, ƒ/ , (Secondary) |
-48 MP, f/1.0, 26mm (wide), 1/2.0'', 0.8µm, PDAF -8 MP, f/2.2, 123˚, (ultrawide), 1/4.0'', 1.12µm -5 MP, f/2.4, (macro) -2 MP, f/2.4, (depth) |
|
Functions | Dual LED flash | LED flash, panorama, HDR | |
Video | 1080p video | 4K@30fps, 1080p@30/120fps | |
Front camera, selfie | 20 MP, Single | 13 MP, Single | |
Specifications | 20 MP, ƒ/ 2.4, 2.00 µm | 13 MP, f/2.2, (wide) | |
Video | 1080p@30fps |
Performance
Operating system - OS | Android 8.0 Oreo | Android 11, One UI 3.0 | |
Chipset | - Qualcomm Snapdragon 636 (14 nm) | - MediaTek MT6853 Dimensity 720 5G (7 nm) | |
CPU | - Octa-Core (8x Kryo 260 1.8 GHz) | - Octa-core (2x2.0 GHz Cortex-A76 & 6x2.0 GHz Cortex-A55) | |
GPU | Qualcomm Adreno 509 | Mali-G57 MC3 | |
External memory | microSDXC (dedicated slot) | microSDXC (uses shared SIM slot) | |
Internal memory | 6GB 128GB | 64GB 4GB RAM, 128GB 4GB RAM, 128GB 6GB RAM, 128GB 8GB RAM |
Benchmark
Antutu 8 Total | 249521 | ||
GeekBench 5 Single Core | 555 | ||
GeekBench 5 Multi-Core | 1666 |
Communication and Connectivity
SIM card | Dual SIM, dual stand-by (Nano SIM + Nano SIM) | Single SIM (Nano-SIM) or Hybrid Dual SIM (Nano-SIM, dual stand-by) | |
Network | 2G / 3G / 4G / | GSM / HSPA / LTE / 5G | |
Bands | -2G - CDMA BC0 (800), B2 (1900), B3 (1800), B5 (850), B8 (900) -3G - B1 (2100), B5 (850), B8 (900), B10 (1700) -4G - B1 (2100), B3 (1800), B4 (1700/2100 AWS 1), B5 (850), B7 (2600), B8 (900), B38 (TDD 2600), B39 (TDD 1900), B40 (TDD 2300), B41 (TDD 2500) |
-2G - GSM 850 / 900 / 1800 / 1900 - SIM 1 & SIM 2 (dual-SIM model only) -3G - HSDPA 850 / 900 / 1900 / 2100 HSDPA 850 / 900 / 1700(AWS) / 1900 / 2100 -4G - LTE () -5G - SA/NSA () |
|
Speed | HSPA 42.2/5.76 Mbps, LTE-A, 5G | ||
GPRS | Yes | Yes | |
Edge | Yes | Yes | |
Wi-Fi | 802.11a, 802.11b, 802.11g, 802.11n, 802.11n 5GHz,Dual band ,Wi-Fi Hotspot ,Wi-Fi Direct ,Wi-Fi Display | Wi-Fi 802.11 a/b/g/n/ac, dual-band, Wi-Fi Direct, hotspot | |
GPS | GPS, A-GPS, GLONASS, Beidou | Yes, with A-GPS, GLONASS, GALILEO, BDS | |
NFC | No | Yes (market/region dependent) | |
USB | Yes, USB Type C, USB On-The-Go (OTG) | USB Type-C 2.0, USB On-The-Go | |
Bluetooth | Bluetooth 5.0, A2DP, EDR, LE | 5.0, A2DP, LE | |
Harmful irradiation |
SAR EU - 0.33 W/kg (head) 1.08 W/kg (body) |
Music and Audio
Radio | Yes | ||
Headphone jack | No | Yes |
Other features
Sensors | - Fingerprint (rear-mounted), Proximity, Accelerometer, compass , Infrared port | - Fingerprint (side-mounted), accelerometer, gyro, proximity, compass | |
Other extras |
- Fast charging 15W |
Reviews and Opinions on HiSense H20 and Samsung Galaxy A32 5G
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!