Motorola Moto E5 Play vs Samsung Galaxy J3 (2018) Comparison and Differences
Smartphone 1
Motorola Moto E5 Play
Smartphone 2
-104.jpg)
Samsung Galaxy J3 (2018)
Smartphone 3
Motorola Moto E5 Play or Samsung Galaxy J3 (2018) Specs Comparison
or
Common specs
| Brand and model | Motorola Moto E5 Play | Samsung Galaxy J3 (2018) | |
| Rating | (+) | (+) | |
| Release date | 2018, April | 2018, June | |
| Dimensions (HxWxD) | 151 x 74 x 9 mm | 5.94 x 5.94 x 2.91 in | 142.7 x 70.1 x 8.9 mm | 5.62 x 5.62 x 2.76 in | |
| Weight | 150 g | 5.29 oz | 152 g | 5.36 oz | |
| Case | buy from Amazon | buy from Amazon | |
| Colors | Black, Dark lake, Flash gray | Black, Blue, Gold | |
| Battery | 2800 mAh, Removable Li-Ion | 2600 mAh, Removable Li-Ion | |
| Approximate price | 80 EUR | 150 EUR | |
| Check price | from Amazon | from Amazon |
Screen
| Technology | IPS LCD | IPS LCD | |
| Touchscreen | capacitive touchscreen | capacitive touchscreen | |
| Display colors | 16M | 16M | |
| Screen size | 5.2" in | 5" in | |
| Screen area | 74.5 cm2 | 68.9 cm2 | |
| Screen format | 16:9 (height:width) | 16:9 (height:width) | |
| Screen to body ratio | 66.7% | 68.9% | |
| Screen resolution | 720 x 1280 px | 720 x 1280 px | |
| Screen PPI /points per inch/ | 282 PPI | 294 PPI | |
| Screen protector | buy from Amazon | buy from Amazon |
Camera and Video
| Rear camera, main | 8 MP, Single | 8 MP, Single | |
| Camera specs | -8 MP, f/2.0, 1.12 µm, AF | -8 MP, AF, f/1.9 | |
| 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 | 5 MP, f/2.2 | |
| Functions | LED flash |
Performance
| Operating system - OS | Android 8.0 (Oreo) | Android 8.0 (Oreo) | |
| Chipset | - Qualcomm MSM8917 Snapdragon 425 (28 nm) - Qualcomm MSM8920 Snapdragon 427 (28 nm) |
- Exynos 7570 Quad (14 nm) | |
| CPU | - Quad-core 1.4 GHz Cortex-A53 | - Quad-core 1.4 GHz Cortex-A53 | |
| GPU | Adreno 308 | Mali-T720 | |
| External memory | microSD, up to 256 GB | microSD, up to 256 GB | |
| Internal memory | 16 GB, 2 GB RAM | 16 GB, 2 GB RAM |
Benchmark
| Antutu 7 Total | |||
| GeekBench 5 Single Core | 146 | ||
| GeekBench 5 Multi-Core | 358 | ||
| GeekBench 4 Single Core | 648 | ||
| GeekBench 4 Multi-Core | 1821 |
Communication and Connectivity
| SIM card | Nano-SIM | Single SIM (Nano-SIM)Dual SIM (Nano-SIM, dual stand-by) | |
| Network | GSM / CDMA / HSPA / EVDO / LTE | GSM / HSPA / LTE | |
| Bands | -2G - GSM 850 / 900 / 1800 / 1900 CDMA 800 / 1900 -3G - HSDPA 850 / 900 / 1700(AWS) / 1900 / 2100 CDMA2000 1xEV-DO -4G - LTE band 1(2100), 2(1900), 3(1800), 4(1700/2100), 5(850), 7(2600), 8(900), 12(700), 13(700), 14(700), 17(700), 25(1900), 26(850), 29(700), 30(2300), 38(2600), 41(2500), 66(1700/2100), 71(600) |
-2G - GSM 850 / 900 / 1800 / 1900 - SIM 1 & SIM 2 (dual-SIM model only) -3G - HSDPA 850 / 900 / 1900 / 2100 HSDPA 850 / 1900 / 2100 - AT&T -4G - LTE LTE band 2(1900), 3(1800), 4(1700/2100), 5(850), 7(2600), 12(700), 14(700) - AT&T |
|
| Speed | HSPA 42.2/5.76 Mbps, LTE-A (2CA) Cat6 300/50 Mbps | HSPA, LTE | |
| GPRS | Yes | Yes | |
| Edge | Yes | Yes | |
| Wi-Fi | Wi-Fi 802.11 a/b/g/n, dual-band, WiFi Direct, hotspot | Wi-Fi 802.11 b/g/n, WiFi Direct, hotspot | |
| GPS | Yes, with A-GPS, GLONASS | Yes, with A-GPS | |
| NFC | |||
| USB | microUSB 2.0 | microUSB 2.0 | |
| Bluetooth | 4.2, A2DP, LE | 4.2, A2DP, LE |
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 | - Accelerometer, gyro, proximity, compass | |
| Other extras |
- Charging 5V/2A 10W - Splash resistant |
||
| Versions |
- Also known as Motorola Moto E Play (5th Gen.) For USA |
- Also known as Samsung Galaxy J3 Star for T-Mobile; Galaxy Amp Prime 3 for Cricket |
Reviews and Opinions on Motorola Moto E5 Play and Samsung Galaxy J3 (2018)
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!