For the last few days, there has been tons of leaks about this new Windows Phone from HTC, and I there are more to come, as an HTC new event in August the 19th is coming up, and with an invitation for WP Central, WinBeta, and all the Windows Phone essential websites, combine with overall smartphone covered web, it is quite clear that a Windows Phone will be coming out of this event. We see rumors from all over the place, and today, we see a render from Verizon itself leaked.
So, this leaked render tells us a few things. Now, aesthetically, this device looks exactly the same as the HTC One M8, even on features on screen navigation button instead of capacitive navigation buttons. We also see the appearance of BoomSound and the wide-angle front-facing camera. The navigation buttons indicate the handset will be pre-loaded with Update 1, with HD display support from on-screen buttons.
On the screen, we see the date 22nd, a Friday. We know that the company having an event on the 19, to possibly launch this phone, and maybe the 22nd is the date that the phone will be available? What’s also interesting appears in these renders is a certain “BlinkFeed” live tiles, could this be the Blink Feed from the Android variant?
Not only will this be the first non-Nokia for version 8.1 of Windows Phone. So, any buyer?
Via: WP Central
3 replies on “HTC One (M8) for Windows render leaked from Verizon”
[…] Microsoft is in should be directed by Nadella, and so far, it does not look so good. I mean, yes, HTC might release a high-end Windows Phone 8.1 handset soon, and more to come from other OEMs, but let’s think about it, how many actual high-end phone […]
[…] rumors and leaks of a One device that runs Windows Phone. It becomes more transparent as we saw the leak render from Verizon a few days ago. So, the question now for those who aren’t living in the States is that will be phone be […]
[…] the day gets closer, the more leaks we get from this new HTC Windows Phone. We’ve seen the render leaked, and information about it leaked as well from @evleaks, bandwidth documentation leaked, some […]