The HTC One has done pretty well for HTC since its debut last year, selling several million units and hitting all four major U.S. carriers. Because of its success, it seems like a fairly safe bet that HTC is planning to release a follow-up to the One sometime soon. The big question surrounding the device concerns its specs and exactly which features HTC will select for its next flagship device. Today a new leak claims to have the "preliminary" details on HTC's plans, and if it's accurate, the spec hounds out there will need to clear some room at the top of their wish lists for the new One.
A tweet from @evleaks claims that the HTC M8 (the One was codenamed "HTC M7") will feature a 5-inch 1080p display on its face, which is slightly larger than the 4.7 incher found on the HTC One. The front of the M8 will also play host to a 2.1-megapixel camera, while the phone's backside will house an UltraPixel shooter.
The M8's innards are expected to include a quad-core Snapdragon 800 processor, which is an improvement from the One's Snapdragon 600 chip, as well as 2GB RAM and 802.11a/b/g/n/ac Wi-Fi. On the software front, it's said that the M8 will come preloaded with Android KitKat running beneath HTC's Sense 6.0 user interface.
While still very much unconfirmed for now, this list of purported HTC M8 specs looks like one that could very easily belong to a flagship smartphone in early 2014. Large smartphones are pretty popular in the Android world right now, so a slight screen size bump up to 5 inches isn't a shock, and the bump up to a Snapdragon 800 processor also makes sense now that every other high-end Android device is packing the same chip.
What will be interesting is seeing how HTC tweaks the design of the One for the new model. Because the One's aluminum unibody frame is one feature that's received quite a bit of praise, I wouldn't be surprised if the M8's design doesn't stray too far from the OG One.
What do you think of this list of leaked HTC M8 specs? Would you be happy if HTC released this device as the follow-up to the One or are there some changes that you think should be made?
Via @evleaks
- Log in to post comments