Feeds

Intel preps x86 Android for summer release

There is no joy in Redmond

Boost IT visibility and business value

Microsoft got some more bad news today: Intel is porting Android 2.2, née Froyo, to the x86 architecture.

"Our expectation is that [native x86 Android] will be based on the Froyo release and will be available this summer to developers," no lesser light than Renee James, Intel's software and services head honchette, told APC on Thursday.

In the main, Microsoft has owned the Intel Atom–based netbook market (sorry, Linux-lovers), while Google's Android has found success in the ARM processor–based smartphone market. But with an x86 Froyo on tap, Android could make inroads into the established netbook market as well as the nascent tablet market.

Which is news that's unlikely to cheer up inhabitants of the increasingly irrelevant corner offices of Redmond, Washington.

Intel is ramping up its efforts in the lucrative low end. As early as May 2009, Intel CEO Paul Otellini put his cards on the table, telling investors that his company was embracing netbooks, handhelds, consumer electronics, and embedded products. "That's what we're aiming at," he told the moneymen. "This is where we think the growth opportunity is for us."

Even before Otellini spoke at the investors' confab, Intel had joined Nokia to create the Moblin-Maemo mobile mashup, MeeGo. And after stumbling on its Menlow low-end attempt, Intel appears to have found if not its stride at least a bit of a loping gait with its recently released and much more power-miserly Moorestown platform.

Although Intel insists that Moorestown is aimed at smartphones, its use in netbooks and tablets would seem to fit its power and performance profiles quite nicely, with smartphones being a better target for Moorestown's follow on, Medfield.

Netbooks, tablet, and smartphones — three areas where the open-source Android can play quite nicely. From this vantage point, an x86 Android would give Microsoft a run for its money on netbooks and be a significant challenger as both OSes aim at tablets.

Smartphones? Microsoft is sinking fast in this market already, and whether Windows Phone 7 can pull them out of their tailspin is the billion-dollar question.

And then there's MeeGo — or, perhaps, with Intel's Android efforts in ascendancy, it may be time to consider rewriting that sentence to read: "And then there was MeeGo." ®

The essential guide to IT transformation

More from The Register

next story
Intel's Raspberry Pi rival Galileo can now run Windows
Behold the Internet of Things. Wintel Things
The Return of BSOD: Does ANYONE trust Microsoft patches?
Sysadmins, you're either fighting fires or seen as incompetents now
Munich considers dumping Linux for ... GULP ... Windows!
Give a penguinista a hug, the Outlook's not good for open source's poster child
Microsoft cries UNINSTALL in the wake of Blue Screens of Death™
Cache crash causes contained choloric calamity
Eat up Martha! Microsoft slings handwriting recog into OneNote on Android
Freehand input on non-Windows kit for the first time
Linux kernel devs made to finger their dongles before contributing code
Two-factor auth enabled for Kernel.org repositories
prev story

Whitepapers

5 things you didn’t know about cloud backup
IT departments are embracing cloud backup, but there’s a lot you need to know before choosing a service provider. Learn all the critical things you need to know.
Implementing global e-invoicing with guaranteed legal certainty
Explaining the role local tax compliance plays in successful supply chain management and e-business and how leading global brands are addressing this.
Build a business case: developing custom apps
Learn how to maximize the value of custom applications by accelerating and simplifying their development.
Rethinking backup and recovery in the modern data center
Combining intelligence, operational analytics, and automation to enable efficient, data-driven IT organizations using the HP ABR approach.
Next gen security for virtualised datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.