HTC has had a hard time recently. It's gotten bad enough that they even needed to pull out of the Indian market. Now things are going from bad to worse, as a device codenamed "Imagine Life" has been leaked by Android Authority. Because of its codename and specifications, it's only fair to assume that this is the upcoming HTC U12 Life.
HTC U12 Life Specifications
Specs | HTC U12 Life |
---|---|
Software | Unknown, possibly Android P |
SoC | Octa-core Qualcomm Snapdragon 636 (4x 1.8GHz Arm Cortex-A73 derived cores + 4x 1.6GHz Arm Cortex-A53 derived cores); Adreno 509 GPU |
RAM and storage | 4GB of RAM with 64GB of storage, microSD card support. There may be more storage options at launch. |
Battery | 3,600mAh battery |
Display | 6-inch FHD+ (2160×1080) with 18:9 aspect ratio |
Connectivity | Bluetooth 5.0, NFC, Dual SIM |
Ports | Unknown |
Rear camera | 16MP + 5MP, PDAF, 4K video support |
Front-facing camera | 13MP with flash and beauty mode |
As we can judge from the specifications, this particular device is solid so far. While the status of a headphone jack will make or break it for many, the specifications themselves are decent. The Qualcomm Snapdragon 636 is no slouch, and anything above 4GB of RAM is usually plenty. It's also certainly an upgrade over the HTC U11 Life, which featured a 5.2-inch display and a 2,600mAh battery. The chip upgrade isn't so pronounced, however, as last year featured a Qualcomm Snapdragon 630.
In terms of availability and pricing, it's hard to say right now. Such a huge amount of information leaked from promotional imagery, which usually suggests a somewhat imminent release. If HTC wants to release it with Android P, then we likely won't be waiting long. As for pricing, the HTC U11 Life cost $349 at launch. It's a steep price to pay, given that competitors like Xiaomi offer similar specs for nearly half the price. We can hope HTC doesn't go too crazy on their pricing, but there's a reason the company is having difficulties as of late.
Source: Android Authority
from xda-developers https://ift.tt/2JSozKi
via IFTTT
No comments:
Post a Comment