Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?
Android Cellphones Google Intel

Intel, Google Team To Optimize Android For Smartphones 187

angry tapir writes "Intel and Google announced on Tuesday that they would partner to optimize future versions of the Android OS for smartphones and other mobile devices using Intel chips. Intel CEO Paul Otellini demonstrated a smartphone with the upcoming Medfield chip running on Android during a keynote at the Intel Developer Conference being held in San Francisco. However, Otellini didn't mention the version of Android running on the smartphone. Intel wants to make x86 the architecture of choice for smartphones, and porting Android will provide a larger opportunity to the chip maker in the smartphone market, Otellini said."
This discussion has been archived. No new comments can be posted.

Intel, Google Team To Optimize Android For Smartphones

Comments Filter:
  • Re:x86? (Score:4, Interesting)

    by fuzzyfuzzyfungus ( 1223518 ) on Wednesday September 14, 2011 @07:16AM (#37396922) Journal
    Why would Google possibly object to Intel adding their pet OS to the list of operating systems that intel pushes along with their embedded CPUs?

    I'd be a bit shocked if the next Nexus whatever phone happens to have Intel inside, Intel just hasn't cracked the low power problem very well; but they move Atoms like crazy for slightly higher powered applications. It isn't make-or-break; but I doubt that Google would mind displacing WinCE in a few of the ubiquitous-but-wastefully-overpowered Kiosk/Signage/etc. applications that are typically intel/WinCE or intel/XP-embedded powered today.

    Plus, while it isn't officially blessed and released at present, Android already runs on x86. The "GoogleTV" products are all Android running on an Atom-based STB SoC(the CE1400 if memory serves.)
  • by Funk_dat69 ( 215898 ) on Wednesday September 14, 2011 @10:03AM (#37398314)

    There are Android-specific patches to the kernel, including an extensive security model, custom locking mechanism, and different frame buffer support among others. A lot of this code may have some ARM-only trickery. Add to that the library of redundant device drivers that phone companies write and discard (that may or may not work) and you have yourself a chunk of work there.
    It doesn't help that Google has no interest whatsoever in getting their code merged into the Linux kernel properly. In fact, that's the main problem with Android. If their patches were merged and properly supported, device drivers would be better and it would be easier to do an x86 (or ppc or what have you) port. It's too bad since userspace is basically all java- the apps should just work on a new arch, but that benefit is torpedoed by Google's lack of follow-through in working with the community to get stuff merged.

    In other news, Meego certainly seems doomed to hacker-land.

We all like praise, but a hike in our pay is the best kind of ways.