redux-framework domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131woocommerce domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131workreap domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131customized-task-offer domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131workreap-hourly-addon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131| Management number | 213273209 | Release Date | 2026/04/12 | List Price | $36.00 | Model Number | 213273209 | ||
|---|---|---|---|---|---|---|---|---|---|
| Category | |||||||||
The Blackview HERO 10 boasts a 6.9-inch flexible AMOLED screen with 2.5K resolution, delivering a PPI of 443 and a broad P3 color gamut. It sports a 108MP primary camera with 12MP and 108MP modes, an 8MP 120 ultra-wide lens, and a 32MP front-facing camera. Running on DokeOS 4.0 with Dynamic Live View, it features a sleek vegan leather back and robust aluminum-alloy frames for a sophisticated feel.
| Brand | Blackview |
|---|---|
| Color | Black |
| Frame Rate | 60 fps |
| Resolution | 2560 x 1440 |
| Unit Count | 1.0 Count |
| Form Factor | Capture every moment, No tripod needed, Pose in various positions |
| Screen Size | 6.9 Inches |
| Aspect Ratio | 16:9 |
| Camera Flash | 108MP |
| Display Type | AMOLED |
| Manufacturer | Blackview |
| Model Series | HERO |
| Refresh Rate | 60 |
| BuiltIn Media | Camera Body & Accessories |
| Sim Card Size | eSIM |
| Shooting Modes | Automatic, Custom, Manual |
| Battery Capacity | 4000 Milliamp Hours |
| Operating System | DokeOS 4.0 |
| Processor Series | Mediatek Helio G99 |
| Camera Description | Clear selfies, Portrait perfection |
| Compatible Devices | Computers, smartphones, tablets, external storage devices (via USB, Wi-Fi, Bluetooth) |
| SIM Card Slot Count | Single SIM |
| Display Pixel Density | 443 Pixels Per Inch (PPI) |
| Water Resistance Level | Not Water Resistant |
| Number of Front Cameras | 1 |
| Video Capture Resolution | 2160p |
| Specific Uses For Product | Photography |
| Display Resolution Maximum | 2560_x_1440 pixels |
| GPS Geotagging Functionality | False |
| Front Photo Sensor Resolution | 32 MP |
| Number of Rear Facing Cameras | 2 |
| Rear Facing Camera Photo Sensor Resolution | 108 MP |
If you notice any omissions or errors in the product information on this page, please use the correction request form below.
Correction Request Form