HTC One ME vs Meizu MX5 Comparison and Differences
Smartphone 1
HTC One ME
Smartphone 2
Meizu MX5
Smartphone 3
HTC One ME or Meizu MX5 Specs Comparison
or
Common specs
| Brand and model | HTC One ME | Meizu MX5 | |
| Rating | (+0) | (+0) | |
| Release date | 2015, June | 2015, June | |
| Dimensions (HxWxD) | 151 x 72 x 9.8 mm | 5.94 x 5.94 x 2.83 in | 149.9 x 74.7 x 7.6 mm | 5.9 x 5.9 x 2.94 in | |
| Weight | 155 g | 5.47 oz | 149 g | 5.26 oz | |
| Case | buy from Amazon | buy from Amazon | |
| Colors | Meteor Grey, Rose Gold, Gold Sepia | Gray, Gold, Silver, Black/Silver | |
| Battery | 2840 mAh, Non-removable Li-Po | 3150 mAh, Non-removable Li-Ion | |
| Battery life |
Stand by time - Up to 598 h (2G) / Up to 626 h (3G) Talking time - Up to 23 h (2G) / Up to 13 h (3G) |
||
| Approximate price | 340 EUR | 210 EUR | |
| Check price | from Amazon | from Amazon |
Screen
| Technology | AMOLED | ||
| Touchscreen | capacitive touchscreen | capacitive touchscreen | |
| Display colors | 16M | 16M | |
| Screen size | 5.2" in | 5.5" in | |
| Screen area | 74.5 cm2 | 83.4 cm2 | |
| Screen format | 16:9 (height:width) | 16:9 (height:width) | |
| Screen to body ratio | 68.6% | 74.5% | |
| Screen resolution | 1440 x 2560 px | 1080 x 1920 px | |
| Screen PPI /points per inch/ | 565 PPI | 401 PPI | |
| Screen protection | Corning Gorilla Glass 3 | ||
| Screen protector | buy from Amazon | buy from Amazon |
Camera and Video
| Rear camera, main | 20 MP, Single | 20.7 MP, Single | |
| Camera specs | -20 MP, f/2.2, 28mm (wide), AF | -20.7 MP, f/2.2, 1/2.3'', 1.2µm, laser AF | |
| Functions | Dual-LED dual-tone flash, HDR, panorama | Dual-LED dual-tone flash, HDR, panorama | |
| Video | 2160p@30fps | 2160p@30fps, 1080p@30fps, 720p@100fps | |
| Front camera, selfie | 4 MP, Single | 5 MP, Single | |
| Specifications | 4 MP, f/2.0, 27mm (wide), 1/3'', 2µm | 5 MP, f/2.2 | |
| Functions | HDR | ||
| Video | 1080p@30fps | 1080p@30fps |
Performance
| Operating system - OS | Android 5.2 (Lollipop), upgradable to 6 (Marshmallow); Sense UI 7 | Android 5.0.1 (Lollipop); Flyme 4.5 | |
| Chipset | - Mediatek MT6795 Helio X10 (28 nm) | - Mediatek MT6795 Helio X10 (28 nm) | |
| CPU | - Octa-core 2.2 GHz Cortex-A53 | - Octa-core 2.2 GHz Cortex-A53 | |
| GPU | PowerVR G6200 | PowerVR G6200 | |
| External memory | microSD, up to 512 GB (dedicated slot) | No | |
| Internal memory | 32 GB, 3 GB RAM | 16/32/64 GB, 3 GB RAM |
Benchmark
| Antutu 7 Total | |||
| GeekBench 4 Single Core | 789 | 817 | |
| GeekBench 4 Multi-Core | 2041 | 3671 | |
| GeekBench 4 RenderScript | 663 | 2478 |
Communication and Connectivity
| SIM card | Dual SIM (Nano-SIM, dual stand-by) | 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 / 1900 / 2100 -4G - LTE band 1(2100), 3(1800), 5(850), 7(2600), 8(900), 28(700), 38(2600), 39(1900), 40(2300), 41(2500) |
-2G - GSM 850 / 900 / 1800 / 1900 - SIM 1 & SIM 2 -3G - HSDPA -4G - LTE |
|
| Speed | HSPA 42.2/5.76 Mbps, LTE Cat4 150/50 Mbps | HSPA, LTE Cat4 150/50 Mbps | |
| GPRS | Yes | Yes | |
| Edge | Yes | Yes | |
| Wi-Fi | Wi-Fi 802.11 a/b/g/n/ac, dual-band, Wi-Fi Direct, DLNA, hotspot | Wi-Fi 802.11 a/b/g/n/ac, dual-band, WiFi Direct, hotspot | |
| GPS | Yes, with A-GPS, GLONASS, BDS | Yes, with A-GPS, GLONASS, BDS | |
| NFC | Yes | ||
| USB | microUSB 2.0 | microUSB 2.0, USB On-The-Go | |
| Bluetooth | 4.1, A2DP, aptX | 4.1, A2DP, LE |
Music and Audio
| Radio | FM radio | No | |
| Headphone jack | Yes | Yes | |
| Others | - Dolby Surround audio enhancement -Active noise cancellation with dedicated mic |
- Active noise cancellation with dedicated mic |
Other features
| Sensors | - Fingerprint (front-mounted), accelerometer, gyro, proximity, compass , Infrared port | - Fingerprint (front-mounted), accelerometer, gyro, proximity, compass | |
| Other extras |
- Fast battery charging: 60% in 40 min (mCharge) |
Reviews and Opinions on HTC One ME and Meizu MX5
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!