10
Jan
LpNQg
Last Updated: January 11th, 2012

Intel and Lenovo just announced the world's first Intel-powered Android smartphone: the K800. It utilizes Intel's Medfield mobile platform, with what we assume is the Atom Z2460 1.6GHz processor. Intel and Lenovo claim that the new Medfield platform is a "no compromise" mobile processor in terms of performance and battery life, though no exact figures were quoted. It actually looks pretty similar to Intel's reference device, and will be available in China (no US availability announced) some time in Q2.

XECth

Intel also demoed said reference device on stage, but didn't tell us anything we don't already know. Intel was keen on showing off the battery life of its reference device, which while it only has a 1440mAh battery, manages an impressive 8 hours of 3G talk time, and a full 5 hours of 3G web browsing. Quite good for such a small battery. Intel is also claiming that the reference device has a 14-day standby time, but didn't disclose whether it was airplane mode or some hibernate function which made this possible.

Sadly, Intel didn't indicate that it was actively working on getting Intel-powered phones optimized for Ice Cream Sandwich, though an upcoming Lenovo Medfield tablet was spotted on the CES floor running Android 4.0, albeit without any hardware acceleration of the OS.

David Ruddock
David's phone is whatever is currently sitting on his desk. He is an avid writer, and enjoys playing devil's advocate in editorials, and reviewing the latest phones and gadgets. He also doesn't usually write such boring sentences.

  • Deltaechoe

    I have a feeling that those battery life claims are just a "bit" exaggerated. I doubt you will ever see battery life like that in real situations with a chip using intel's architecture.

    • p3ngwin

      i'm suspicious too.

      looking at the chip's power efficiency, we can see that something doesn't add up if we apply what we have learned recently.

      http://www.dailytech.com/Intel+Medfield+Details+Leak++Powerful+But+a+Battery+Guzzler/article23611.htm

      "The platform reportedly has a 2.6W TDP at idle and a maximum power consumption of 3.6W when playing 720P Flash video. By launch the maximum power is intended to drop to 2.6W, while the idle is also likely to drop a fair bit."

      Some quick "napkin math":

      * An average smartphone battery is around 1600 mAh
      * The output voltage is typically 3.7 V
      * The total battery power is thus 5.92 Wh
      * Thus the platform would last a bit over two hours at idle in a smartphone before dying.

      something isn't right with either the previously thought numbers, or Intel's announcement numbers.

  • http://social-catalog.com/apple-iphone-4s-vs-samsung-galaxy-s3 aatif

    When we will get this ? china is getting in QT and what about US

  • Steve

    I can't wait until all these Intel-powered x86-based Android phones come out and watch the shit hit the fan when people try to use ARM-compiled NDK apps.

    I hope Google has a plan to handle this.

    • p3ngwin

      "The Android NDK is a companion tool to the Android SDK that lets you build performance-critical portions of your apps in native code. It provides headers and libraries that allow you to build activities, handle user input, use hardware sensors, access application resources, and more, when programming in C or C++. If you write native code, your applications are still packaged into an .apk file and they still run inside of a virtual machine on the device. The fundamental Android application model does not change."

      http://developer.android.com/sdk/ndk/index.html

      the way android runs in a virtual machine is similar i think to the way Native Client works with Chrome browser running NC apps on PC's, it doesn't matter what hardware you're running as it's abstracted.

      • Steve

        The virtual machine is only for SDK-based Java code. The NDK apps are compiled and run right on the processor.

        I have tried Android-x86 on my EeePC and also tried a MIPS-based Cruz Tablet... NDK apps do not work on those because they are not ARM.

        You can compile x86 NDK apps, but there will be an apk for each version out there and it will be confusing to people.

        Since Android on x86 is not mainstream yet, its not a big deal to developers, but this new Intel-Android partnership is going to change all that and they need to make sure they address it.

        • p3ngwin

          ah, so NDK is compiled to run on an Instruction Set Architecture like ARM or x86, etc ?

          that will be interesting then.

  • Leon Zap

    The Market is smart enough to figure out if an app will un on your machine. All developers have to do is get the NDK for google and recompile it for x86 and do not even have to test it. I have done this blindly on NDK apps I have written for ARM. There is also an x86 emulator that one can run in Qemu. Also regarding battery usage, the link is old. Intel will not be stupid to release a processor that only last for 2 hrs. They might as well license and make ARM again, which they can do very easily.

    • p3ngwin

      " ....watch the shit hit the fan when people try to use ARM-compiled NDK apps."

      ..

      "The Market is smart enough to figure out if an app will un on your machine. All developers have to do is get the NDK for google and recompile it for x86 and do not even have to test it."

      so there is already a plan in effect, as if people configure their devices with the android market properly, they won't be trying incompatible apps simply because they won't even be presented them.
      as for the "old link" for the Intel Atom specs", the link is to a 2 week "old" article. unless you have some better sources negating the information i linked, then it stands.

  • http://ppcmanagementtools.com/ Pay Per Click Help

    The Android Smartphone is a great device that helps people, like me, multi task with the latest Google Apps.

Quantcast