Galaxy Nexus Owner Beats Microsoft at Windows Phone Challenge

appsplit: "Sahas Katta is a true Android believer and enthusiast living in Santa Clara. He went down to the nearest Microsoft Store to participate in a competition called “Windows Phone Challenge”.
Long story short, He won the challenge fair and square but Microsoft reps denied him the prize. When asked for an explanation Microsoft employee replied with these two historic words “Just Because”"

Read Full Story >>
The story is too old to be commented.
KingPin2393d ago

the Windows Phone had no chance at its own challenge.

Dont mess with the droids, you will get owned!!!

dilawer2393d ago

yup, you're right. I mean as far as I know there is no Dual core WP yet, so how can a single core phone compete with Dual Core Galaxy Nexus, Lol.

givemeshelter2393d ago (Edited 2393d ago )

It can compete very easily.
The challenges that Microsoft are doing are not CPU or GPU intensive and more related to how optimized the software is for daily tasks such as opening applications, booting up the phone and swiping between screens etc.
This is where the Windows Phone in most cases is faster and smoother because the software is better optimized than Android for its handsets.
This has always been a issue with Android phones. However I find my Galaxy Nexus running Ice Cream sandwich is better optimized than the previous OS's before it.

However you notice that Microsoft will NOT offer a challenge in regards to running the same software that requires GPU/CPU processing cycles on Android vs Windows Phones.
In that case the Windows phone would get 'smoked' every time and smoked quite badly.

I want to see how Window Phones run with the Apollo update and when they release their Quad and dual core phones in late 2012.

dilawer2393d ago

I understand but still Galaxy Nexus is way better optimized than any Windows Phone out there.

givemeshelter2392d ago (Edited 2392d ago )

Actually Windows Phones Are a lot better optimized.
I had a windows phone and now I have the Nexus.

When running day to day simple operations, Windows Phone 7 operating system runs smoother than Ice Cream sandwich. Pinch and zoom is smoother. Flipping through apps is smoother. Opening folders are smoother on Windows phone.
This is common knowledge. They have done side by side tests and it runs smoother. Same with IOS.
Where Windows Phones get destroyed totally by Android phones are applications that are GPU/CPU intensive.
It's no contest there. Reason? Dual core chipsets.


"That’s exactly what Munn argues. Citing several online sources plus ex-colleagues at Android, the 3rd-year engineering student explains that Android’s lagginess is fundamental to its architecture. Basically, Android was originally designed to be used on regular laptops with a keyboard and a mouse. It doesn’t prioritize real-time tasks like screen rendering with a separate, protected thread. As a result, the UI can’t handle constant input and screen redraws, as fingers on a touchscreen tend to create.

This is the main reason why Android isn’t and can never be as smooth as iOS or Windows Phone 7, which do prioritize real-time rendering, says Munn. Only a fundamental rewrite, the kind that would break hundreds of thousand of existing Android apps, will fix this nagging issue, he warns. Otherwise, “Android UI will never be completely smooth.”

Ice Cream is smooth as silk but it still stutters in areas that IOS and Windows does not. I know. I have the phone.
Now gaming and video? Nexus hands the Windows phones its ass...
Here is my Galaxy Nexus. My baby :-)

givemeshelter2392d ago

"To stir the pot more, Google’s Android expert Dianne Hackborn responded late Thursday nite:
The reader who pointed this out to me wrote “In short, the intern got it wrong.” I don’t think it’s so cut and dried. I’ll try to summarize what Hackborn wrote: 1) It’s true that Android lacks a real-time thread just for screen rendering like iOS, says Hackborn. 2) Instead, Android lets apps be prioritized as default or background. UI threads normally run at default. Application processes running in the background are forced to run in the background. 3) Background threads collectively are only allowed to take up 10% CPU utilization maximum. 4) There was a ‘foreground’ priority in the original Android but it was abandoned b/c it turned out not to give enough priority to things like the UI. 5) Android uses the two sets of priority threads as part of its goal of creating a ‘sandbox’ architecture that separates all apps, incl. 3rd-party ones, for security reasons. This, says Hackborn, differs from iOS’s design which didn’t originally accommodate 3rd-party apps. 6) Setting up a separate thread just for drawing the UI in real-time would not have been worth it, due to a bunch of complex reasons Hackborn lists that I don’t quite understand. 7) Android only “recently” began to use hardware acceleration for drawing inside the UI. 8) That’s because hardware acceleration isn’t as simple as making your graphics chip handle the UI. It takes a lot of memory and multiple processes to manage the graphics chips as “most mobile GPUs still have fairly expensive GL context switching.” 9) Hackborn acknowledges that “there are of course many things that can be improved in Android today, just as there are many things that have been improved since 1.0. As other more pressing issues are addressed, and hardware capabilities improve and change, we continue to push the platform forward and make it better.” 10) But…it’s no technical piece of cake to enable your iOS app to support touch scrolling at a smooth 60 frames per second, either, says Hackborn, quoting a comment to that effect from an outside developer. “Based on this statement I don’t see any indication that there is something intrinsically flawed about Android in making lists scroll at 60fps, any more than there is in iOS.”

Good read...