Wednesday, March 12, 2014

New HTC One for Verizon photos show off dummy model, retail packaging

Are you sitting down? If not, you should probably take a seat, because I’ve got some pretty shocking news for you: the new HTC One has leaked out.

Yes, it seems that we can’t go more than a day without being confronted by more new HTC One leaks. Today I’ve got a mid-week twofer for you, as the Verizon version of the new One has leaked out in two different styles. First up is an eBay listing by seller “dummy_models” that offers a peek at, you guessed it, the dummy model of the new HTC One. The unit looks pretty similar to the dark gray Verizon model that appeared in a render last month, complete with the Duo Camera and Verizon 4G LTE branding on its backside as well as some BoomSound speakers and on-screen navigation buttons on its face.

Today’s second leak also comes to us from eBay. This time around we’re getting a look at the Verizon HTC One’s packaging, which is not dissimilar from the box that the original HTC One came in. The phone itself doesn’t appear in any of the photos included with the listing, but we do get a look at the back of the box, which includes a pretty complete spec list for the new One:

  • 5-inch 1080p display
  • 2.3GHz quad-core Snapdragon 801 processor
  • Rear Duo Camera with UltraPixel tech
  • 5-megapixel front-facing camera with wide-angle lens
  • 32GB built-in storage, microSD slot with support for cards up to 128GB in size
  • 2GB RAM
  • NFC
  • 4G LTE

The combination of today’s two leaks give us a pretty good idea of what the new HTC One is all about. That doesn’t mean that I’m not looking forward to the device’s event on March 25, though, because the official debut of a device is always nicer than a bunch of leaks. Plus, the event may include an announcement of the one piece of new HTC One information that we’re still missing: its release date.

htconevzwdummyfront htconevzwdummyrear htconevzwdummylay2 htconevzwbox htconevzwboxrear

Via: GSMArena (1), (2)
Sources: eBay (1), (2)



source: androidandme

0 comments :