Slashdot Mirror


Google Delays General Release of Honeycomb Source

iluvcapra writes "BusinessWeek reports that Google will not be releasing the source code for Android Honeycomb 'for the foreseeable future.' Android lead Andy Rubin is quoted, stating that if Google were to release the source for Honeycomb, Google would be unable to prevent it from being installed on mobile phones and 'creating a really bad user experience.'"

6 of 262 comments (clear)

  1. From TFA by Anonymous Coward · · Score: 5, Insightful

    Over the past few weeks, Google has notified device makers of its change in plans with Honeycomb. Android executives have also been telling companies that Google will likely wait to make another open-source distribution of Android software until it completes the next version, called Ice Cream.

    So unlike what the summary suggests, and more in line with the title, it really is a delay, not an indefinite cutoff.

    1. Re:From TFA by tlhIngan · · Score: 5, Informative

      Yeah, the OSS platform will always be one version behind the version they give to their top-tier partners, thus Motorola and Samsung get a head start selling the best devices, and then vendors who Google doesn't license Ice Cream to are stuck selling last year's commodity, in a market that is by then saturated.

      Pretty cool, huh? Almost as if Google has created a perpetual motion machine that allows them to release their platform as open software, while simultaneously maintaining the power to decide which handset vendors will thrive.

      There are two projects called Android. One is Android, which is distributed to all OHA partners. And since you have to be an OHA partner anyhow to get the "with Google" stuff (e.g,, Market, YouTube, Gmail, etc.), all the OHA members can get access to Honeycomb right now.

      The other Android project is AOSP, which is the open-source version fo Android and distributed to the world. If you're not a member of the OHA (requirements include being sponsored by an OHA member, and some annual fee), you can only use AOSP. This is the rise of the cheap handsets and tablets that don't ship with the Google stuff (lots of handsets in China are built using AOSP and officially don't have "with Google", plus a lot of the cheap tablets you can find).

      I think this policy came about because the OHA members were complaining they had to compete with the cheap tablets out there.

      The other downside of this, that will bite the OHA's members in the ass is that silicon venders like Broadcom, TI, Marvell, Freescale, etc., rely on AOSP to provide Android packages so they can test their chips with Android. If they can't access the latest and greatest, then the chips that OHA members use may not have the Android support they need. Note that I excluded Samsung, and Qualcomm because they are OHA members.

  2. But, but... by Jugalator · · Score: 5, Informative

    http://twitter.com/Arubin/status/27808662429

    What is the definition of "open" today, Google...?

    --
    Beware: In C++, your friends can see your privates!
  3. Re:GPL violation? by Rastor · · Score: 5, Informative

    Because Android isn't GPL licensed, only the kernel is.

    For the record, the kernel is available at android.git.kernel.org

  4. Re:I don't understand their justification by naasking · · Score: 5, Insightful

    Who are they trying to protect from this bad user experience?

    The Android brand.

  5. Re:iOS their reason? by shaitand · · Score: 5, Insightful

    They are doing this to give the xoom a sales boost. There are tons of tablets sold with 2.2 code using hardware that can run Honeycomb (which isn't for your phone and has nothing to do with iPhone). This is about burning everyone who bought one of those to boost the sales of tablets with 3.0. In many cases, for the same company that sold the tablet with 2.2 and wants to now sell the exact same hardware with 3.0 and a new model number.