Samsung Galaxy A12 vs Oppo A33 Comparison and Differences
Smartphone 1
Samsung Galaxy A12
Smartphone 2
Oppo A33
Smartphone 3
Samsung Galaxy A12 or Oppo A33 Specs Comparison
or
Common specs
| Brand and model | Samsung Galaxy A12 | Oppo A33 | |
| Rating | (+0) | (+0) | |
| Release date | 2020, November 24 | 2015, November | |
| Dimensions (HxWxD) | 164 x 75.8 x 8.9 mm | 6.46 x 6.46 x 2.98 in | 142.7 x 71.7 x 7.6 mm | 5.62 x 5.62 x 2.82 in | |
| Weight | 205 g | 7.23 oz | 146 g | 5.15 oz | |
| Body Build | Glass front, plastic back, plastic frame | ||
| Case | buy from Amazon | buy from Amazon | |
| Colors | Black, White, Blue, Red | White | |
| Battery | 5000 mAh, Li-Po, non-removable | 2400 mAh, Non-removable Li-Po | |
| Battery life |
Stand by time - Up to 250 h (3G) Talking time - Up to 8 h (3G) |
||
| Approximate price | $ 170 | 240 EUR | |
| Check price | from Amazon | from Amazon |
Screen
| Technology | PLS IPS | IPS LCD | |
| Touchscreen | capacitive touchscreen | capacitive touchscreen | |
| Display colors | 16M | 16M | |
| Screen size | 6.5" in | 5" in | |
| Screen area | 102.0 cm2 | 68.9 cm2 | |
| Screen format | 20:9 (height:width) | 16:9 (height:width) | |
| Screen to body ratio | 82.1% | 67.4% | |
| Screen resolution | 720 x 1600 px | 540 x 960 px | |
| Screen PPI /points per inch/ | 270 PPI | 220 PPI | |
| Screen protector | buy from Amazon | buy from Amazon |
Camera and Video
| Rear camera, main | 48 MP, Quad | 8 MP, Single | |
| Camera specs | -48 MP, f/2.0, 26mm (wide), AF -5 MP, f/2.2, 123˚ (ultrawide) -2 MP, f/2.4, (macro) -2 MP, f/2.4, (depth) |
-8 MP, 1/3.2'', 1.4µm, AF | |
| Functions | LED flash, panorama, HDR | LED flash, HDR, panorama | |
| Video | 1080p@30fps | 1080p@30fps | |
| DxOMark Main Score | 90 | ||
| DxOMark Photo | 96 | ||
| DxOMark Video | 80 | ||
| Front camera, selfie | 8 MP, Single | 5 MP, Single | |
| Specifications | 8 MP, f/2.2 | 5 MP | |
| Video | 1080p@30fps |
Performance
| Operating system - OS | Android 10 | Android 5.1 (Lollipop); ColorOS 2.1 | |
| Chipset | - Mediatek MT6765 Helio P35 (12nm) | - Qualcomm MSM8916 Snapdragon 410 (28 nm) | |
| CPU | - Octa-core (4x2.35 GHz Cortex-A53 & 4x1.8 GHz Cortex-A53) | - Quad-core 1.2 GHz Cortex-A53 | |
| GPU | PowerVR GE8320 | Adreno 306 | |
| External memory | microSDXC (dedicated slot) | microSD, up to 256 GB (dedicated slot) | |
| Internal memory | 32GB 3GB RAM, 64GB 4GB RAM, 128GB 4GB RAM, 128GB 6GB RAM | 16 GB, 2 GB RAM |
Benchmark
| Antutu 8 Total | 103760 | ||
| Antutu 7 Total | |||
| GeekBench 6 Single Core | 158 | ||
| GeekBench 6 Multi Core | 691 | ||
| GeekBench 5 Single Core | 158 | ||
| GeekBench 5 Multi-Core | 930 | ||
| GeekBench 4 Single Core | 483 | ||
| GeekBench 4 Multi-Core | 1235 | ||
| GeekBench 4 RenderScript | 920 |
Communication and Connectivity
| SIM card | Single SIM (Nano-SIM)Dual SIM (Nano-SIM, dual stand-by) | Dual SIM (Nano-SIM/ Micro-SIM) | |
| Network | GSM / HSPA / LTE | GSM / HSPA / LTE | |
| Bands | -2G - GSM 850 / 900 / 1800 / 1900 - SIM 1 & SIM 2 (dual-SIM only) -3G - HSDPA 850 / 900 / 1900 / 2100 -4G - LTE |
-2G - GSM 850 / 900 / 1800 / 1900 - SIM 1 & SIM 2 -3G - HSDPA 850 / 900 / 1900 / 2100 TD-SCDMA -4G - LTE band 1(2100), 3(1800), 38(2600), 39(1900), 40(2300), 41(2500) |
|
| Speed | HSPA 42.2/5.76 Mbps, LTE Cat4 150/50 Mbps | HSPA, LTE | |
| GPRS | Yes | Yes | |
| Edge | Yes | Yes | |
| Wi-Fi | Wi-Fi 802.11 b/g/n, Wi-Fi Direct, hotspot | Wi-Fi 802.11 b/g/n | |
| GPS | Yes, with A-GPS, GLONASS, GALILEO, BDS | Yes, with A-GPS | |
| NFC | Yes (market/region dependent) | ||
| USB | USB Type-C 2.0 | microUSB 2.0, USB Host | |
| Bluetooth | 5.0, A2DP, LE | 4.0, A2DP | |
| Harmful irradiation |
SAR EU - 0.67 W/kg (head) 1.38 W/kg (body) |
Music and Audio
| Radio | FM radio, RDS, recording | FM radio | |
| Headphone jack | Yes | Yes |
Other features
| Sensors | - Fingerprint (side-mounted), accelerometer | - Accelerometer, proximity, compass | |
| Other extras |
- Fast charging 15W |
Reviews and Opinions on Samsung Galaxy A12 and Oppo A33
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!