One of the hopeful rumors today is focusing around the LG E900 (seen last week), that sleek keyboardless Windows Phone 7 device probably headed for European markets.
The word is that it is running a 1.3GHz QSD8650A Snapdragon CPU, which of course would be a first and not too unexpected as Qualcomm is gearing up to launch a few new CPUs this Fall/Winter. It also features the obvious 3.7" screen,
The bad news is, at least according to WMPU, that due to an goof in Google Translation, it may actually be just a 1GHz CPU, not the coveted 1.3GHz version.
[It all hinges on the 'A' in QSD8650A--with an 'A' it is the 1.3Ghz revision; without it is the regular 1Ghz. In the original Polish text, it is just QSD8650, so 1GHz.]
Either way, we're sure we'll like it, but alas it doesn't have the same headline making umph. We can actually see this going either way, so we'll just wait for LG to tell us but we're leaning with 1GHz.
Finally, some new, almost higher quality videos are out which can be found below for your viewing pleasure. And check out the source, Android.com.pl for more close up shots.
Windows Central Newsletter
Get the best of Windows Central in in your inbox, every day!
Daniel Rubino is the Editor-in-chief of Windows Central, head reviewer, podcast co-host, and analyst. He has been covering Microsoft since 2007 when this site was called WMExperts (and later Windows Phone Central). His interests include Windows, laptops, next-gen computing, and for some reason, watches. Before all this tech stuff, he worked on a Ph.D. in linguistics, watched people sleep (for medical purposes!), and ran the projectors at movie theaters because it was fun.
To release new devices with a new OS runniing 1.3 speeds would be a really good move. All of a sudden, everyone elses devices are behind a cycle. and while the advance may be short lived, it would help steer people to new devices running wp. Fingers crossed on this one.
Thank you for signing up to Windows Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.