Slashdot Mirror


Android Ice Cream Sandwich Source Released

grcumb writes "Looks like the folks at Google have made good on their promise to release the Android 4.0 source code. Android software engineer Jean-Baptiste Queru writes: 'Hi! We just released a bit of code we thought this group might be interested in. Over at our Android Open-Source Project git servers, the source code for Android version 4.0 (Ice Cream Sandwich) is now available. ... This is actually the source code for version 4.0.1 of Android, which is the specific version that will ship on the Galaxy Nexus, the first Android 4.0 device. In the source tree, you will find a device build target named "full_maguro" that you can use to build a system image for Galaxy Nexus. Build configurations for other devices will come later.' " Once nice side-effect of this is that the revision history for the non-free Honeycomb series is also available, albeit without any release tags.

38 of 285 comments (clear)

  1. Good to see... by Algae_94 · · Score: 4, Interesting

    that Google has followed through on releasing the source code. This is awesome news after Honeycomb went MIA as far as source release.

    1. Re:Good to see... by Baloroth · · Score: 5, Insightful

      Huh? Google was supposed to release source code for Android? Pretty sure that counts as extra.

      Of course, by /. standards everyone is supposed to release their source code, so by that standard, yeah Google did what they were supposed to do. On the other hand, anyone who is truly a proponent of freedom should acknowledge that, being Google's project, they are free to do with it as they like. Including not releasing source, if they see fit.

      --
      "None can love freedom heartily, but good men; the rest love not freedom, but license." --John Milton
    2. Re:Good to see... by icebraining · · Score: 5, Informative

      When you build off of GPL software you're legally obligated to release the modifications, so yeah, Google releasing a significant portion of Android is not "extra" it is the minimum required by law.

      Only if you distribute binaries, which Google never did. Of course, the manufacturers did release binaries, so they did distribute the GPL'ed code from their websites. For example, you could always find Honeycomb's kernel code on the ASUS website.

      That's not to say they did not also release some code they did not strictly have to, but since they had promised to do so, changing their mind at this stage would have been willfully misleading consumers and partners.

      But they weren't obligated to promise it in the first place.

    3. Re:Good to see... by icebraining · · Score: 5, Informative

      Samsung was still legally the distributor, and they did in fact release the GPLv2 licensed code on their website (search for "D710" on https://opensource.samsung.com/index.jsp, for example).

    4. Re:Good to see... by Anonymous Coward · · Score: 3, Interesting

      That would be why none of Ice Cream Sandwich other than the kernel is under the GPL. They didn't 'build off GPL software', in fact they went to the extreme of writing their own libc in order to avoid that. The 'some code they did not strictly have to' is basically all of Android's userland.

    5. Re:Good to see... by Grave · · Score: 4, Informative

      ICS is designed to work nicely on both phones and tablets. Google knew that 2.x was not really ideal for tablets, hence Honeycomb. But forking their own OS was not ideal, either, so ICS now combines the best of both and should provide a great experience on either format.

    6. Re:Good to see... by errandum · · Score: 5, Informative

      Actually, it isn't missing in action. The ICS source tree includes the honeycomb code, even though it isn't tagged... So, technically, it's there.

    7. Re:Good to see... by iluvcapra · · Score: 5, Insightful

      But they weren't obligated to promise it in the first place.

      If there's some sort of hierarchy it works like:

      1) Release nothing, offer service (Google search, Salesforce.com)

      2) Distribute dongle-encrypted binaries (Pro Tools, AutoCad)

      3) Distribute binaries (Mango, Google Android apps, iOS)

      4) Distribute binaries, distribute open source to the open components (Mac OS X)

      5) Distribute binaries, distribute source on binary delivery (Android)

      6) Maintain public source tree, no one gets the bleeding-edge source before anyone else (Linux kernel)

      7) Distribute source with a permissive license (Apache)

      And thene there's the various support levels:

      1) Fuck you (a lot of software)

      2) Check out the forum (Apple level 1)

      3) Give us a call and we'll charge you by the hour (Microsoft, enterprise Linux)

      4) Submit a ticket but we won't tell you anything after that (Android)

      5) Bring the software into the shop and we'll see what we can do with it in 10 minutes, if you live in a city (Apple Genius Bar)

      6) Submit a ticket, recruit people to vote on it, post bounties for it, and follow it to resolution (Firefox)

      --
      Don't blame me, I voted for Baltar.
    8. Re:Good to see... by whoop · · Score: 4, Insightful

      No. There is no forgiveness for past deemed transgressions against the Open Source here! KDE is still kursed for using the unfree Qt! Loki porting games to Linux was shit because we don't need that binary-only crap! Wine is stupid because then developers won't need to make Linux-only ports.

      Welcome to Slashdot.

    9. Re:Good to see... by PopeRatzo · · Score: 5, Insightful

      When you build off of GPL software you're legally obligated to release the modifications, so yeah, Google releasing a significant portion of Android is not "extra" it is the minimum required by law. That's not to say they did not also release some code they did not strictly have to, but since they had promised to do so, changing their mind at this stage would have been willfully misleading consumers and partners.

      As a parent, I have learned that while you should not always reward simply "doing what you should", it's very important not to bitch about it when someone does what they should, or what they said they would do.

      So, for future reference, the correct response to this announcement of Google releasing the source code to Android 4 is "Good". Saying "Those fuckers, they didn't do it last time" is really not productive in terms of behavior programming.

      --
      You are welcome on my lawn.
    10. Re:Good to see... by bemymonkey · · Score: 4, Informative

      Were you really worried that Google wouldn't release Ice Cream Sandwich's source code because they didn't release Honeycomb's? The reasons for holding back HC were openly stated and quite equitable... Could you have imagined the chaos resulting from people trying to hack a tablet-only OS into their smartphone with half the phone functionality, and everything that makes the form factor work, missing completely?

      Also: Ice Cream Sandwich practically *is* Honeycomb, but ready for public release due to being suitable for phone AND tablet form factors...

  2. Here come the ports by exomondo · · Score: 3, Insightful

    Hopefully that means we will see ICS ported to other devices in the near future, it should be interesting to see how it performs on older devices.
    Good to see that ICS is an open source version of Android after the closed-source Honeycomb created that possibility (however unlikely) of other Android versions following suit.

  3. Show me the source. by mjwx · · Score: 4, Insightful

    Well here it is,

    Just like Google promised, they were quite open about why they didnt release the Honeycomb source (not that it stopped ROM cookers) and that the changes in 3.x would be released in 4.0.

    It's nice that a large company actually adheres to its word.

    Now how long before CyanogenMod 9 is released.

    --
    Calling someone a "hater" only means you can not rationally rebut their argument.
    1. Re:Show me the source. by Lumpy · · Score: 4, Interesting

      Screw that. When does the AndroidX86 version get released? I need to upgrade my home made Car stereo that runs Android.

      I can finally get rid of the crud hack of adding on screen buttons for volume, back and home.

      --
      Do not look at laser with remaining good eye.
    2. Re:Show me the source. by Elgonn · · Score: 4, Insightful

      Now how long before CyanogenMod 9 is released.

      This is really what most of us care about at this point. Maybe 1% of us will actively use the code personally.

    3. Re:Show me the source. by Anonymous Coward · · Score: 5, Informative

      Talk to these guys:
      http://www.android-x86.org/

    4. Re:Show me the source. by mjwx · · Score: 3, Insightful

      Now how long before CyanogenMod 9 is released.

      This is really what most of us care about at this point. Maybe 1% of us will actively use the code personally.

      But that 1% matters as they are the device manufacturers.

      Cheap Elocity or Archos tablets running ICS on display at your local Tesco's or Best Buy. Hell, I might buy one just for my car, the fact that the $200 tablets were all running 2.2 was the only thing stopping me (lets be honest, on a 7" screen 2.x was crap).

      --
      Calling someone a "hater" only means you can not rationally rebut their argument.
    5. Re:Show me the source. by icebraining · · Score: 5, Informative

      "To make our schedule to ship the tablet, we made some design tradeoffs," says Andy Rubin, vice-president for engineering at Google and head of its Android group. "We didn't want to think about what it would take for the same software to run on phones. It would have required a lot of additional resources and extended our schedule beyond what we thought was reasonable. So we took a shortcut."

      Rubin says that if Google were to open-source the Honeycomb code now, as it has with other versions of Android at similar periods in their development, it couldn't prevent developers from putting the software on phones "and creating a really bad user experience. We have no idea if it will even work on phones."

    6. Re:Show me the source. by Miamicanes · · Score: 4, Insightful

      > What was that reason, that they didn't release Honeycomb?

      That, and to temporarily give higher-end tablets with better hardware a fighting chance against the onslaught of underpowered K-mart-bound tablets from China with 10" 480x800 displays and 200MHz CPUs. Google wasn't terribly picky about whom they allowed to have access to Honeycomb, as long as your hardware met their minimum spec. It wasn't ideal, but it was the only way to give tablets like the Xoom, Transformer, and Galaxy Tab a fighting chance to break out of the 480x800 ghetto and give us hardware that wouldn't have iPad owners laughing at us.

    7. Re:Show me the source. by evilviper · · Score: 3, Interesting

      I guess you didn't see the Archos range.

      Yes I did. In fact my rant about low-res screens and crappy unresponsive touchscreens is directed SQUARELY AT ARCHOS.

      "Capacitive" isn't a magic keyword that makes it not-suck. The cheap ones are still a nightmare to use, and since that's the sole form of input, the whole device becomes worthless.

      That wasn't the only issue, btw. Other big issues were the lack of a compas, lack of GPS, inability to charge, AT ALL from USB, a power socket DIRECTLY next to the headphone jack, a power plug exactly the same size as a headphone jack (see where we're going, here?) super-slick case and absolutely no ergonomics making it impossible to hold, being much heavier than comparable devices.

      I consider Archos tablets the canonical example of crap that I wouldn't use if they were giving it away, and here you're trumpeting them as first-class devices.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    8. Re:Show me the source. by Lumpy · · Score: 4, Informative

      7" LCD with a resistive touchscreen. 800X480 resolution is more than enough for a car display.

      --
      Do not look at laser with remaining good eye.
  4. GitHub by ttong · · Score: 5, Informative

    GitHub provides a friendly interface to view the source without having to use the repo tool and downloading the whole thing, so I'm eagerly waiting for this to get pushed there as well. Shouldn't take long.

    https://github.com/android/

  5. Ice Cream+Graham Crackers+Crashing by orphiuchus · · Score: 4, Funny

    Come on, we all already know goes into an ice Cream Sandwich. You get two graham crackers, put ice cream between them, and serve with a side of randomly lock up my phone for no reason. Easy.

  6. Re:Stupid projects names by Daetrin · · Score: 4, Funny

    Yeah! "Cupcake", "Eclair", "Ice Cream", what the hell kind of names are those? Sounds more like something from a dinner menu than a release list!

    The OSS movement really needs to take a page from the book of professional companies like Microsoft. They know how to give their product versions classy names, like "Mango". See how much better that is?

    --
    This Space Intentionally Left Blank
  7. Re:Don't be kissing Googles ass by icebraining · · Score: 4, Informative

    They had no other choice legally, or else this wouldn't have happened.

    Uh, no. First, they never distributed binaries, so they weren't required to release anything.

    Second, the parts that *were* required to be released (by the manufacturers, not Google) were in fact released, and you could always get them. They're in the ASUS site, for example.

    Thirdly, most of the code that actually makes up Android is Apache2 licensed, which means they are never required to release it - you can use it on proprietary code.

    Can I type make install? Or are we still in tivo land?

    That's up to the manufacturers, not Google.

  8. Re:Not until the "incompleteness" is stated by Anonymous Coward · · Score: 5, Informative

    Well, for starters, Apple used to release all their intrusive changes to KHTML as a single patch, which made it impossible to discern what had changed and therefore "impossible" to integrate back upstream. Google has released the repository itself, with proper change history, of all the code they have been working on. That's quite a big difference, so stop spreading FUD.

  9. Re:Some, not all of Honeycomb up for tagging (mayb by LordLimecat · · Score: 4, Insightful

    IMHO, not good enough to not release the entire platform

    How about this for rationale: Its their code and they dont owe you a darn thing.

    Seriously, someone comes out with a new semi-revolutionary embedded device OS (revolutionary in that it took the market by storm and is reasonably open / easy to root), and then they release the source for the first several releases. But when they miss one, people act like theyre OWED something. You know what? Go use one of the OTHER open-source phone OSes if you feel so strongly about it.

    Seriously, this sense of entitlement bugs the heck out of me. The world doesnt owe you a thing.

  10. Only kernel is GPL by OeLeWaPpErKe · · Score: 5, Informative

    The point usually made is that this applies to the android kernel source, which has indeed been promptly released directly to the kernel developers (and for download for anyone who cares). Much more promptly, by the way, than required by the licence.

    It does *NOT* apply to the full android system, nor will it ever. Android itself (the various subprojects have separate licences, which I think you'll find, are all proprietary).

    Just distributing a linux kernel running distribution does *not* make it GPL.

    http://www.zdnet.com/blog/open-source/linus-torvalds-on-android-the-linux-fork/9426

  11. Re:Not until the "incompleteness" is stated by ninetyninebottles · · Score: 5, Insightful

    Funny, when Apple released source code in this manner (big chunks all at once) the open source community was up in arms, claiming they weren't being good open-source citizens.

    I actually don't remember anyone significant in the OSS community being up in arms. There were a lot of people on Slashdot, but I'm not really convinced that's the same thing.

    Remember when KHTML folks were ranting about Apple's handling of WebKit?

    No. I remember when one of the KHTML developers made a comment saying they wished Apple would make things easier to backport into KHTML. I further remember them politely e-mailing the Apple devs about it and then the KHTML team making numerous comments about how nice it was that Apple went out of their way to help even though a lot of the changes were in a direction the KHTML team was not really interested in emulating. I further remember people who weren't KHTML developers ranting loudly and at length in numerous forums and here on Slashdot about how "evil" Apple was and repeatedly making uninformed comments that bordered on libel. Apparently the impression that left still lingers.

    Unless Android development opens up, this is more of a "shared source" model than a real "open source" one.

    Not really. Until Google distributes the software they are not obligated to share any code and if they feel that the time to market advantage of keeping the code secret until they ship is important, well that's a perfectly reasonable strategy that has been quite common in OSS for a long time. It is a trade off because it discourages some players from contributing to the same project and can limit adoption by some vendors.

  12. They already released the GPL'd stuff by pavon · · Score: 5, Informative

    Google did release all of Android Honycomb that was GPL'd. In particular the Kernel, and a few other userland tools. However, everything that makes Andrioid Android, and not just another linux distro is licensed under the Apache license which allows for proprietary modifications. This includes the Dalvik VM, the Harmony Java libraries, and the Android APIs. Google was perfectly with the law to not release this code, not to mention the fact that they wrote half of it themselves.

    This has already been discussed ad'nausem on Slashdot, so there is no excuse for this misinformation to be moderated up. I swear only idiots that hardly read the site get moderation points anymore.

  13. Haters Thread by bill_mcgonigle · · Score: 4, Funny

    OK, here's a thread to post the links to all the haters' comments where they guaranteed that Google had gone Evil and would never release ICS source.

    Granted, I full well expect six people will rebuff, stating that since 4.0.1 was released but not 4.0.0 that they were precisely correct and that this is proof of Google's evil intentions.

    --
    My God, it's Full of Source!
    OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    1. Re:Haters Thread by msevior · · Score: 3, Insightful

      Yeah I commented on an earlier article about how much better off we are with Google and Android. I got weirdest set of hate comments. People hate getting their prejudices refuted. It causes massive cognitive dissonance and is physically painful. I have my own and have observed the effect on me.

  14. Some credit to Google by dell623 · · Score: 5, Insightful

    Google are:
    - releasing source code to their operating system for free, under no obligation. The Nook Tablet and Color and Kindle Fire are great examples of how this can work against Google - Android devices that make no payment to Google and do not come with access to Google's Android Marketplace, or Google's proprietary apps.

    - virtually the only major silicon valley company left (compared to Apple, Amazon, IBM, Microsoft, Oracle, Amazon etc) who haven't patent trolled anyone (except in retaliation of course), although they could have, Google still has thousands of patents even though companies like Microsoft have far more, some of them are a lot more important than Apple GUI animation patents. e.g. http://arstechnica.com/open-source/news/2010/01/googles-mapreduce-patent-what-does-it-mean-for-hadoop.ars

    - been far better at sticking to privacy promises and openness compared to the likes of Facebook

    - have entire divisions of their company and features that make no revenue for them (and are not R&D projects in hope of future earnings) but are retained. e.g. Free offline and IMAP/SMTP/POP access to gmail from day one, google docs for personal use (I can open and edit files with no ads anywhere), AOSP, Google chrome/ chromium, google.org

    - principled stand on net neutrality

    - taking a principled stand and pulling out of China

    Somehow Google are still constantly attacked, way more than companies like Apple and Microsoft these days, they deserve some credit. Sure, they are far from the do no evil motto, but these days, doing a lot less evil than other megacorps is still remarkable.

  15. You have warped sense of priorities by pem · · Score: 4, Interesting

    If you put a free website as more evil than a dongle-encryped piece of crap that you pay thousands of dollars for.

  16. Not GPL, Apache2 license by ZombieBraintrust · · Score: 5, Informative

    Android isn't GPL. Its an Apache2 license. Only the Linux kernel is GPL and they have been releasing the source for the kernel mods on time.

  17. Re:Not until the "incompleteness" is stated by Daniel+Phillips · · Score: 3

    The difference being that Android is Google's project and KHTML is KDE's...

    Bad comparison. The majority of Android was not developed by Google or Android before being acquired. Dalvik is the main from-scratch component, then there is the (fairly mundane) window manager, and most of the rest was assembling components.

    --
    Have you got your LWN subscription yet?
  18. Re:Not until the "incompleteness" is stated by serviscope_minor · · Score: 3, Insightful

    If you're trying to claim that Apple is as good an open-source citizen as Redhat, then you are drinking some particularly strong kool aid. It sounds good, and I'd be interested in trying some for myself. Wherecan I get it?

    Just in case you're merely mistaken, RedHat send an awful lot of stuff upstream, and they always have done. In fact, they don't just send stuff upstream, they employ quite a number of the kernel developers/maintainers full time who do nothing but hack publicly on the entirely open-source kernel.

    --
    SJW n. One who posts facts.
  19. anons: never failing to troll firstposts by poetmatt · · Score: 5, Insightful

    They were never evil. They're not MS/Apple. Do you have a short term memory loss? Honeycomb was withheld, and they told people why.

    They said basically honeycomb was a bad implementation, they didn't want people to move forward with it, they do want people to move forward on ICS. It's not like a "honeycomb is a goddamn secret!" This has been announced like 500x. It's like a design for a car that they say "this design causes engines to explode" so they don't release the design. Is this a surprise that they then release ICS source? Did you hear them say "ICS is a bad implementation"? No.

    That's not a lack of transparency either, they announced this repeatedly.

    [Andy] Rubin says that if Google were to open-source the Honeycomb code now, as it has with other versions of Android at similar periods in their development, it couldn't prevent developers from putting the software on phones "and creating a really bad user experience. We have no idea if it will even work on phones." "Android is an open-source project," he adds. "We have not changed our strategy."