03
Jul
thumb

A couple of days ago, AOSP was graced with a series of freshly created "l-preview" branches and a massive push of brand new code. As we know now, quite a bit of that code push wasn't truly representative of the L developer preview. (Very sneaky, Google.) Most of the truly new updates belonged to GPL-licensed projects, which Google is obligated to release in a timely fashion. The remaining projects with "l-preview" branches were filled with a recent snapshot from the Master branch.

While we didn't get enough code to build our own versions of L, there is still an obscene amount to look at. Since it's not a sign of good mental health to obsessively crawl around each project looking for changes, we usually wait for Al Sutton of Funky Android to generate a full list of commits with developer comments.

Screen Shot 2014-07-03 at 3.34.45 AM

This time, the full changelog comes in at a whopping 60,305 commits. Even if we drop everything from the Chromium project, that number only drops to 36,637. Unfortunately, this list might contain some changes that never made it into the L factory images, and it's obviously missing a substantial number of the most important updates.

Fun fact: Despite being a partial code dump which lacks most of the major platform changes, L already has 3,500 more code commits than the update from Jelly Bean 4.3 to KitKat (JSS15J 4.3_r2.1 to KRT16M 4.4_r1).

If you're up to the challenge of looking through all of these developer comments, head over to Funky Android and check out this monster of a changelog. The full changelog, with Chrome commits included, weighs in at a hefty 10 MB. Some people have even complained that this page can cause Firefox (and possibly other browsers) to crash or freeze up. You've been warned.

Changelog: including Chromium changes (10MB) or without Chromium changes (5MB)

Thanks, Al!

Cody Toombs
Cody is a Software Engineer and Writer with a mildly overwhelming obsession with smartphones and the mobile world. If he’s been pulled away from the computer for any length of time, you might find him talking about cocktails and movies, sometimes resulting in the consumption of both.

  • 16Bitz0r

    C'mon, Google... Release the Preview to N4 owners. My N4 bugs me.

    • Wyatt Neal

      I mean, sure releasing the preview to the other systems would be great ... but I don't think putting a less-than-stable preview on your N4 that's bugging you is going to make your day much better ... then again, Android "L" ... oh yea ... they maybe already did that:

      https://android.googlesource.com/device/lge/mako/+/l-preview

      Tada!

      • h4rr4r

        The minute it is not 100% stable and bug free that chucklehead would be flying off the hinge.

    • Ayysir_PA

      its a developer preview not a user preview.. doubt they'll do that for ya

  • Finger

    Poor dalvik :(

  • http://www.torikomix.pl/ Adam Szopa

    Both changelog links point to the same place!

    • http://www.androidpolice.com/author/cody-toombs/ Cody Toombs

      Damn, the link must not have copied correctly the first time. #fixed

  • cae

    I'm afraid that the changelog ist wrong. For example take a look at platform/packages/apps/Calendar. In the changelog it has 24 changes. If you take a look here there are only 2 commits since kitkat https://android.googlesource.com/platform/packages/apps/Calendar/
    This also true for most other packages.

    • http://profiles.google.com/geoffreyzub Geoffrey S. Zub

      If you look preview-l is a branch off of android 4.4.2 (kot49h) and so this changelog is from the point at which they branched the code. There should be a duplicate of all of the commits in this changelog that were also done from 4.4.2 to 4.4.4

      • Jerome de Bretagne

        Yes, the post is not very clear about this important point, so it is quite misleading if one doesn't understand this subtle difference.

        It would be much more interesting to have the list of commits between 4.4.4 and L Preview.

    • Jeffrey Smith

      Agreed. While the page states that l-preview appears to have been forked from 4.4 shortly after 4.4.2_r1, that doesn't appear to be the case with Calendar. That is probably true of many other projects.

  • mlj11

    L is shaping up to be a real whopper.

    When it's released I'm gonna totally wipe my N5 before installing the full image... I want to see and feel the new OS unburdened by all the bloat I've accumulated over the past year.

    • overtook

      That's a good idea i think I'll do that too

    • http://thedangerbrain.com/ Alfonso Surroca

      Same. I didn't wipe when I flashed the developer preview because I was too antsy to flash it as soon as it was posted, but I'll actually probably wipe and reflash at some point.

  • Luca

    Hey Google! There's also a nexus 7 2013 LTE! Do you remember?

    • Wyatt Neal

      Not according to VZW /zing

    • http://www.droid-life.com/ Steve B

      That's your fault for buying something that Verizon has a hand in. If they can f*ck it up, they will.

      • someone755

        I think you misinterpreted that.
        Whatever Verizon has a hand in, they will fuck up. But the point is that Verizon fucks up things that not only they have a hand in xD

  • jamaall

    So many changes in the changelog that chrome is unresponsive :/

  • mgamerz

    1 bug per kloc... We're in for quite a few bugs at launch.

    • someone755

      Launch is still months away.

  • Squiddles

    Could someone explain all the "DO NOT MERGE" lines in there? I understand what merging is in terms of Git and whatnot, but here not so much.

    • Joel Fåk

      Since this is a list of Git commits I guess it means just that. Probably this commit doesn't contain everything that is needed to build the software and therefore you should not have merged this into your own branch at the time of development. I guess the commits after fix the problem.

    • http://www.androidpolice.com/author/cody-toombs/ Cody Toombs

      To quote David Turner, who I believe is the same David Turner from the Android NDK team (posted this). Hey, the name may not be rare, but it's still probably not a coincidence.

      "They usually come from commits that happened originally in the internal tree used at Google. This is used by scripts used to process the commits, their meaning is usually lost once the corresponding commit has been open-sourced." -- Google Groups

      So, it's basically a code change that appears twice (or more), once in private and again in public.