Intel Medfield reference phone

One of the more exciting pieces of mobile news for 2012 -- Intel's introduction into the Android ecosystem -- is also one of the more difficult ones to show you. Well, that's not entirely true; we got a nice look at Intel's CES booth with the new Medfield reference phone. And we got ourselves a pretty cool look at some of the early graphics capabilities.

Android Central @ CES But that's just it. We've seen great graphics before. We've seen smooth graphics before. We've seen mobile graphics that have made our heads spin. That graphics are going to become smoother and faster and more realistic every year is a given.

So when you watch our early hands-on with the Intel platform, keep in mind that we're still a little ways away from actual phones hitting actual hands. Don't worry a whole lot about the look of the device. You're not going to see the Intel Droid RAZR III XL in stores anytime soon. But the bottom line is that Intel's ready to power smartphones and tablets, apps are ready to work out of the box, and we've now got a whole new world of horsepower to explore. Will Intel be the battery life saviour we're all desperately wanting? Dunno yet. But one way or another, with Intel now in the mobile game, it's going to be an exciting year.  See the video after the break

Youtube link for mobile viewing


Reader comments

Hands-on with the Intel Android reference phone


Well.... a long time in relative terms, sure. I mean, in the Phone industry, 3 months is forever... (Not saying they'll be here in 3 months, just trying to put it all in perspective)

All games and apps that use the NDK would need their binaries and libraries recompiled for x86. ie...tons of stuff wont work immediately.

On the other hand, tons of stuff might be actually easier to port that are already working well in x86.

The processor that Intel is offering here doesn't have the power consumption issues that prior atom's had. (Actually it was never the atom itself that was the power hog it was the supporting chipset that gobbled the power.)

I'm not sure this goes into phones anytime soon unless there is a big power advantage or a big price advantage or a big performance boost.

Why would anyone want to re-engineer their entire phone line for similar performance? Upgrading from one ARM implementation to another ARM implementation is largely transparent, a couple compiler switches at most, but when the underlying instruction set needs a total rewrite, its a big task.

This is pure blatent rumor at this point, but I've heard a future version of the SDK, NDK, and Eclipse plug-in will automatically cross compile for arm/mips/x86 if the proper toolchains are installed.  As long as Google can implement a way to properly check the device type in the Market, developers can simply upload all 3 apk files for seamless integration.

yes this is already possible. But my point was, many devs have only compiled for ARM (I'm one of them) or compiled before this was possible and have not had the need to recompile since. None of these binaries or libraries compiled for ARM will work on x86. They will have to be recompiled, like I said. Hopefully Google does make it easy on us though, I haven't looked into or even thought about x86, like almost every other dev.

Developers should just need to add the argument "APP_ABI=all" and the NDK will compile for all supported CPU (x86, ARM v6, and ARM v7 right now). The changes in the market should allow them to distribute the code all at once or limit it to only let you download the version that matches your processor.

that's ok, Phil tried several times to swipe sideways in the app drawer instead of scroll vertically for gingerbread AOSP. He's too used to his Galaxy Nexus and ICS, and he must be exhausted. Poor guy is working so hard! 18 phones announced in 1 day... gotta be rough.