Nokia to use ST-Ericsson U8500 SoC for its Windows Phone 8 devices ?

Ready for some totally weird news? ST-Ericsson’s CEO is now claiming that Nokia will use the company’s U8500 SoC in some of its upcoming Windows Phone devices. But contrary to what you may think he is not talking about Windows Phone 7 but about Windows Phone 8 which is probably still 1 year away. As you already know Qualcomm is the only certified SoC manufacturer for Windows Phone 7 and this was confirmed again with the updated chassis specification unveiled last month. The fact that ST-Ericsson’s CEO is now claiming that Windows Phone 8, which has yet to be announced and probably isn’t finalized in terms of required hardware specifications, will run on this particular SoC is rather strange.

The rest of the claims are for the most part factually wrong:

Even after the Microsoft deal ST-Ericsson continues to have “very close relations” with Nokia, said Bozotti, and will be “an important supplier” for Nokia’s Windows Phone 8 phones. (The first/current wave of Windows Phone devices is called Windows Phone 7 but the next generation of Windows Phones will be known as Windows Phone 8.)

The first “wave” of Windows Phone devices as the say is Windows Phone 7 and the second wave is still Windows Phone 7 (Mango aka Windows Phone 7.5) not Windows Phone 8.

The first ST-Ericsson chipset that will appear in a Nokia Windows Phone is the U8500, a sophisticated dual-core system-on-a-chip that can also be found in the new Samsung Infuse 4G smartphone on AT&T and the T-Mobile Sidekick 4G. Later Nokia Windows Phones – the company is planning to release 12 Windows Phone devices over the course of 2012 – will run on future versions of the U8500, said Bozotti.

This is totally wrong: The Samsung Infuse 4G sports a single core Samsung Hummingbird Cortex A8 clocked @ 1.2Ghz and the T-Mobile Sidekick 4G a Samsung Hummingbird clocked @ 1Ghz. I just hope that this is Forbes’ editor mistake and not ST-Ericsson’s CEO…

Anyway, let’s take all these claims with a grain of salt. So far only Qualcomm is officially known as the Windows Phone SoC provider and even the latest Nokia Windows Phone devices rumors are claiming that Nokia will only use Qualcomm’s SoC. Also remember that Nokia’s Setphen Elop will keynote at Qualcomm’s Uplinq event next month.

UPDATE: Here’s what Nokia official statement on the matter issued a few hours after Forbes story was posted:

“The first Nokias based on Windows Phone will have the Qualcomm chipset,” said a Nokia spokesman.

“Our aim is to build a vibrant ecosystem around Nokia and the Windows Phone OS and with that intent we are naturally continuing discussions with a number of chipset suppliers for our future product portfolio,” he said.

He said one of the companies involved in the talks was ST-Ericsson.

Keywords here: “involved in the talks“. Not much has changed since ST-E’s first statement in February and as I said back then nothing is set in stones yet for ST-Ericsson who has no choice other than release this kind of PR talk to save face in front of investors because loosing Nokia as a costumer would be a big blow to the company (Nokia is their biggest partner/costumer). Also note that no matter what Nokia says it’s still Microsoft who decides which Chipset is going to be certified for the platform.

UPDATE2: The Forbes writer seems to be confused about the whole thing and even assumed that Windows Phone 8 was going to be launched this fall (!?) and will try to clarify the whole thing later.

source: Forbes, Reuters thanks to everybody for the heads-up on the Reuters story

  • Nataku

    i feel like getting a bucket of salt now… 

  • Davidh

    Samsung Infuse 4G smartphone on AT&T and the T-Mobile Sidekick 4G are using ST-Ericsson’s modem(Thor). Prosessor itself is from another company.

  • Ahmed Salem

     I hope that Windows Phone 8 would be soon, or both Nokia and Microsoft would be screwed-up!!!

  • MobileTechWorld

    Yes only the radio modem is a ST-E the main SoC is Samsung’s Hummingbird. So the Forbes/ST-E statement is totally false.