The SoC

Given our transistor filled nature, one of our major concerns was discovering what System on Chip (SoC) lies at the heart of WP7S. This is especially the case given the strict, uniform hardware requirements stipulated for virtually all hardware manufacturers (it's like an iPhone made by 4 different companies?).

The basic hardware requirements are (as we mentioned earlier) the following:

  • Capacitive Touch
    • 4 or more contact points
  • Sensors
    • A-GPS, Accelerometer, Compass, Light, Proximity
  • Camera
    • 5 megapixels or more, flash required, camera button required
  • Multimedia
    • Common detailed specs, Codec Acceleration
  • Memory
    • 256 MB RAM or more, 8 GB Flash or more
    • No external storage support (no SD cards)
  • GPU
    • DirectX 9 acceleration
  • CPU
    • ARMv7 Cortex/Scorpion or better
  • Screen
    • Two Supported Displays
      • 480 x 800 WVGA : Aspect Ratio 3:5
      • 320 x 480 HVGA : Aspect Ratio 2:3

However, we've dug up some more hardware details that are entirely new. Microsoft told me personally they've definitely already chosen a particular SoC, but aren't ready to state what it is. There's a dialog that takes place between OEMs, Microsoft, and carriers to decide on both the clocks and optimal performance/battery target for the device. My understanding is that this dialog is ongoing, and that the software giant will make a final announcement when it's settled. Although Microsoft has not announced whether it's the case, Qualcomm has already made an announcement of its own that Snapdragon lies at the core. We should know soon, but Tegra or any other choices are looking highly unlikely at this point. Speculate all you want, no amount of pressing would get Microsoft to disclose what they've chosen. We'll just have to be patient.

Hopefully Microsoft has chosen its WP7S SoC with the future in mind - the landscape will likely have changed significantly by Q4 2010, and Snapdragon as we know it today will be old news. Both the single core 8X50A Snapdragon at 1.3 GHz, as well as the 8X72 dual core Snapdragon at 1.5 GHz will likely have made their debut and start arriving in products by Q4 2010. It's entirely possible that one of these is the choices, but we just don't know yet.

The GPU

There's some interesting stuff going on with the GPU on WP7S. Although we don't know anything about the specific silicon, we know a lot about the software implementation that needs to be rounded up thoroughly.

Let's start from the beginning. Remember from the earlier article how WP7S runs code across two separate frameworks - Silverlight, and XNA? Each of these have their own set of hardware accelerated functions that directly leverage the GPU. Furthermore, you cannot mix and match Silverlight and XNA frameworks at present, something Microsoft hopes to eventually reconcile, but not, you guessed it, in this release.

Zune Integration GPU Acceleration
Comments Locked

55 Comments

View All Comments

  • pcfxer - Sunday, March 21, 2010 - link

    Android is far easier to develop for than WM and iPhone. For my engineering project my team is developing a device for non-verbal users.
  • pro5 - Monday, March 22, 2010 - link

    Is android Java only? (I don't know) but if so that would reason enough for me not to develop for it. C# and objective C are 'bad enough' but java has always left me cold (I'm a C++ coder mainly).

    If it can use native C++ then great, still doesn't make up for it's other short comings. The only real advantage I see to Android is how 'open' it is, but really that's more of killer than a helper in the dev community (if money is your goal). How does the GPU compare to Winphone for example? Where is the 'standard' development target (screen size, hardware features). Stuff like iPhone and WP7 are 'easier' to develop for because you never need to 2nd guess the user's hardware config or screen size (ok 2 sizes in the case of WP7 in future)
  • Penti - Monday, March 22, 2010 - link

    Android has the NDK so you can run native code, you don't need to run your code in dalvik. That means C and C++. Just as any other Linux based Phone OS. Such as WebOS. Of course Maemo too. Bada too of course, and of course none Linux based Symbian.

    The shit runs at the same hardware so what's your problem? Nobody is forcing you to develop for free. That you can release your apps without review is not a bad thing. Apps such as Firefox (Fennec) are ported to Maemo and being ported to Android. There's an Alpha for WinMo too. Something that can't be done on iPhone OS or Blackberry. Or WP7. If you only want to develop for a specific phone thats fine, but then you miss millions of other users. Even if you do android apps you don't need to support every single phone there is. Old phones won't be upgraded to newer versions of Android OS any way. And it's really the software platform that should have the focus any way.
  • jms102285 - Saturday, April 3, 2010 - link

    Hey Anand, I sent you an E-mail regarding what the implications of Microsoft Communications Server just before the release of the WP7 is.... I haven't heard anything back yet in over a week from anyone I mailed about it.

    Are you guys tight-lipped about it because of NDAs or something???
  • CSMR - Sunday, March 21, 2010 - link

    Not really (http://jkontherun.com/2009/11/23/windows-mobile-vs...">http://jkontherun.com/2009/11/23/window...droid-wi... but hopefully it will be within a year.
    I'm hoping that it will get full, reliable exchange support (e-mail+calendar+tasks+scheduling meetings+search server etc.).

Log in

Don't have an account? Sign up now