The Android L release is the first time Google has offered a developer preview of an upcoming version of the platform, so no one knew how it would handle things. Would there be updates? Could we watch L evolve over time? It was unclear before, but now Google has posted new versions of the images for the Nexus 7 and Nexus 5.


The new versions have build number LPV81C, whereas the last one was LPV79. Basically, it's two days newer than the last preview (check out our version number calculator). This version includes support for Google Fit, according to the download page. We're not expecting huge changes otherwise, but we are digging through it anyway. If anything pops up, we'll update.

Maybe we will get more versions before the release, and maybe this is it—no way to know. You can grab the new images at the Android Developers site and flash them to your device, but a full wipe will probably be needed (if you get the missing button/busted notification issue from not wiping, try this fix). Here are the specifics.

430 MB (451,424,729 bytes)
MD5 f3d795fc41fbd993121998caa597477b

421 MB (441,760,643 bytes)
MD5 101c6e1673f54048ba2eee0c9f9be041

[Android Developers – Thanks, Sebastiano Poggi]

Ryan Whitwam
Ryan is a tech/science writer, skeptic, lover of all things electronic, and Android fan. In his spare time he reads golden-age sci-fi and sleeps, but rarely at the same time. His wife tolerates him as few would.

He's the author of a sci-fi novel called The Crooked City, which is available on Amazon and Google Play.

  • Christopher Bement

    Deb :(

    • nhizzat

      Fuck you Google. I too own the bastard child Nexus device.

  • Illford

    is media controls with android wear fixed? thats the only thing keeping me off of L. I ran L as my daily driver till I got my Gwatch with no issues.

    • NothingUnknown

      That's what I'm waiting to find out.

      The other bug is WiFi tethering but there's a workaround for that.

      • Kyle Bailey

        What's the work around?

      • usaff22

        Tethering is fixed in this build, at least for me

        • NothingUnknown

          Excellent news. Thanks.

          Do you have a wear device to test out music controls?

          • usaff22

            Sorry, doesn't seem like it's fixed. Apparently I had a different tethering issue where Settings would FC so I thought it was fixed. It doesn't FC anymore but none of my devices are able to connect to the internet, despite connecting to the AP.

            I think the only change here is new Google Play Services with Google Fit, unfortunately.

  • Tom Harman

    downloading now, just waiting to hear if anything exciting enough to flash it or just wait till real ota, or a more exciting preview, lol, be nice if we could just update like an ota from the current preview build.

    • NothingUnknown

      Probably can via a flashable zip just like any old ROM. But over kit Kat it doesn't work well without a factory reset. Over an l install it will probably work.

      Once one is made which will probably be minutes from now.

      • Tom Harman

        Yeah that is true

  • samuelmaskell

    I expected them to do an ota update. Maybe they still will.

    • Pal

      OTA is acceptable for end-users, but not a very considerate thing to do for developers working on a specific version.

      • samuelmaskell

        1. You could just not accept the OTA and
        2. There is absolutely no reason why anyone should be staying on an old version of L. It's never going to be publicly released so you're supporting a version that doesn't really even exist.

        • mgamerz

          The OTA popup shows up every few minutes and automatically downloads. It's not hard to accidentally accept it if it bugs you every few minutes.

      • Crispin Swickard

        I was curious if they would approach it OTA style. Apple does it with the preview iOS builds, and for the reasons samuelmaskell pointed out it would not benefit anyone to have an old preview build.

  • Mobile_Dom

    I give it a matter of days before some intrepid dev has made a Nexus 4 version of this, just as they did with the last

    • http://adonisk.com Adonis K.

      It's only useful for Google Fit devs...

      • http://mwinter.in/ Yan Gabriel Minário

        Sure, what kind of dev you're if you don't have DA LATEST NEXA?

  • manish

    flashing =D

  • siddude11

    I think Android L official kernel will be 3.10.

    • username_already_exists_error

      i highly doubt it. base kernel in CAF is still 3.4 for nexus 5.

      • siddude11

        I am talking about the Official, October release.

        • username_already_exists_error

          even on official release. it will still be 3.4 on nexus 5. in case there's a new nexus, it's possible.

    • angel_spain

      It won't. So far, the only device that seems to be running 3.10 kernel is the next nexus phone ("Shamu"). It wouldn't make sense then to have developer preview builds with 3.4 kernel when L release is expected for Q4 2014.

      • Yowan

        Not exactly, a lot of devices have already been using kernel 3.10 for quite some time. This includes the international Exynos Galaxy S5 (SM-G900H), the newer S5 LTE-A or even some of those new low end Galaxy devices running Spreadtrum/BCM SoCs.

  • Guest
    • Deeco


      • Chris

        I am with you on this. I can't stop laughing.

  • Guest
  • Ben F

    I dont want these roms on my phone as stability is important.

    if I install this on my N7 tablet will it make me want it on my Nexus 5?

    • Thomas’

      The N5 version surprisingly didn't crash my phone a single time.

      • Craig M

        Then you weren't using it that much.

        • usaff22

          It crashed a lot in the beginning, but now it never crashes. It hasn't crashed for weeks now.

    • siddude11

      Stability is better than Kitkat and yes you will be drooling all over.

      • Chris

        What about MMS on AT&T? That wasn't working on my N5 when I flashed LPV79...

        • markgbe

          not fixed

        • Nigel Antonio

          mms isnt fixed on SPRINT nor ATT. i think for ATT its a simple APN fix, just like with tmob,
          on sprint i was able to send and receive MMS the first 2 days of L then after none... I was able to install 4.4.2 modem and it worked for a day to send but cannot receive MMS. from what i've been gathering from every one on here and xda. its broken till official release.
          if your on Tmob, consider yourself lucky.. lol

    • Zach Gamble

      Yeah, I ran it on my 7 for a long time and it never crashed.

  • Guillaume

    will you compare the differences ?

  • Cody Fyler

    I don't see the updated image? Still see:

    Download and uncompress the Android Developer Preview package.DeviceDownloadChecksumNexus 5 (GSM/LTE)
    "hammerhead"hammerhead-lpv79-preview-ac1d8a8e.tgzMD5: 5a6ae77217978cb7b958a240c2e80b57
    SHA-1: ac1d8a8e4f4a1dca5864dc733caa940bffc28616Nexus 7 (Wifi)
    "razor"razor-lpv79-preview-d0ddf8ce.tgzMD5: b293a5d3a4e07beabebcc0be85ad68a2
    SHA-1: d0ddf8ce733ba2a34279cdff8827fd604762c2342d

  • Tomáš Petrík

    Is it finally possible to pull down the notification bar in the emulator?

  • Michell Bak

    There's probably a small chance of this happening, but can anyone test if it fixes the issue with OkHttp 2?

  • http://www.ronakg.com/ Ronak Gandhi

    Quote from the source - "To start developing with the Google Fit Developer Preview, you need:
    A special version of the Android L Developer Preview system image with Google Fit support. The system image is available for the Nexus 5 and the Nexus 7 Wi-Fi version 2."
    So that's what this is. Just a special version of Android L preview image with Fit support for N5 and N7.

    • http://www.androidpolice.com/ Artem Russakovskii

      Might as well flash it and gain Google Fit support.

      • http://www.westagemusic.com/ Marc

        Can't wait to see the article roll in. :)

    • Felix

      Seems like Android Police didn't read what's on that site^^
      It clearly includes Google Fit support. I think that will be the only difference.

      • Will Tisdale

        Yeah, I don't think it's worth flashing to be honest, unless you want the Google Fit support of course.

        • Devon Warren

          I'm sure there are a bunch of bug fixes as well

  • kindrudekid

    update zip anyone?

  • Андрей Прохоров
    • http://www.androidpolice.com/ Artem Russakovskii

      What about it? That's already linked in the post.

  • http://twitter.com/_vinr vinothr

    Release it for Nexus 7 (2012)! Come on, Google. Ugh...

    • MJ

      I won't hold your breath... It's a developer preview and they already have one version for a phone and another for a tablet. I don't think they want to waste a lot of resources creating builds for a bunch of devices.

  • WORPspeed

    Multi-user support? net build right?

  • godutch

    And the n7 lte is still stuck on 4.4.3 !!!! Why are the ones paying the premium price for the premium device being left out?

    • Brad


    • frhow

      Why they only need a phone and a tablet to send out to developers. Why would they make multiple builds for a preview image. Its not mainstream yet. Be patient young grasshopper.

  • Abhishek

    They might have fixed the miscellaneous battery draining bug too.. In this new build..

  • TheBlueF0x

    I wonder if MMS will start working properly on this build? I couldn't get it to work (with AT&T) when I flashed the older DP.

    • markgbe

      MMS does not appear to be fixed.

    • Chronus719

      I got MMS to work with Hello MMS in the Play Store. You do, however, need to be on mobile data in order to send or receive properly.

  • Charles

    Anyone with a N5 on AT&T who can report if MMS works in Hangouts? That's the only killer bug preventing me from running this preview full time.

    • markgbe

      Flashed. and looking like it's not fixed yet.

      • Matthew Ross

        I had it work fine on mine but I know I had to make changes to the APN in the hangouts app to fix it. However I have since flashed a PA preview so I cant check what I did :(

        • markgbe

          yeah i dont use much MMS, when i need to do it i just use chompsms and turn off wifi. seems to work fine that way.

          • Matthew Ross

            That is by far the easiest approach but I understand why people want it to work like normal. As an example like many android users I use a mix of hangouts and text during the day and work with a lot of iphone users. It is annoying to have to turn off WiFi every time I want to see a group iphone message only to forget to turn it on again when I want to use anything like netflix or even hangouts if my mobile data connection is bad (which it often is in the building where I work).

          • markgbe

            chompsms has a sweet option to automatically turn off wifi while downloading an MMS, then turns it back on after it's done.

            Works well as far as i can tell.

            However, i'll be excited for sure once October or November rolls around and all these bugs are fixed in final(hopefully).

          • Matthew Ross

            Yeah I have noticed that option on several texting apps. I have my own that I enjoy using but I always fall back to hangouts and its merged text/hangouts option. I enjoy only using one app hence the off and back on again nature but I admit it is a problem of my own making and there are other alternative.

  • Ano Niem

    Is there a solution yet to change the worse than awfull eyeblinding headache causing white in L? If not Android with L will break my heart.

    • deano


  • burdo

    any solution to this bug ? An app from the recent app menu will show up when closing another app by tapping the back button quickly.

  • ßTester

    Is it stable (at least more than the first image) ?

    • fahadayaz

      What issues are you having? I'm yet to come across any on my Nexus 7.

    • monkeybutts

      No mainly just gets the Google Fit SDK in not much else. It's pretty much the same L.

  • Giampi

    Can I use Android Wear with "L"? If I recall correctly previous version didn't.

  • https://google.com/+LateefAlabiOki Lateef Alabi-Oki

    Google has a build process problem.

    Apple's preview release of both their desktop and mobile OS is available for the last 3 generations of all their hardware.

    Cyanogen, a company with infinitely smaller resources than Google, churns out stable, beta and nightly builds of Android on more devices than Google ever has.

    Somehow, Google can't manage to make a preview available even on the latest versions of all their Nexus devices, not to mention the last two generations.

    I'm embarrassed for Google's Android build team. You guys are slacking big time.

    Developers/testers with the latest Nexus 7 LTE are screwed again.

    • Will Tisdale

      Lol, you people need a reality check. This is the FIRST developer preview Google has ever released for an upcoming Android version. Why on earth do you think they should do it for *all* Nexus devices? They're testing the water with this too.

      Do you want them to release previews for *all* Android devices whilst they are at it? Come on...the 2 devices they have chosen are the easiest to support - why would they want to make it harder for themselves by having to involve carriers?

      I wouldn't be embarrassed for them - I doubt they are embarrassed.

      CyanogenMod has churned out buggy junk for a lot of devices for years. Once in a while something will actually work fully, without issues. It doesn't make it a good development model, it just dilutes the little skill there is.

      Apple is very unique in its vertical integration, and it's attitude towards carriers - so it's much easier for them to support all their devices.

      • https://google.com/+LateefAlabiOki Lateef Alabi-Oki

        Sounds like a bunch of baseless excuses.

        The reality is that Apple, Microsoft, Cyanogen, 99% of open source projects push development builds of their OS on way more hardware. For some reason Google is incapable of doing it.

        A robust build process will push builds on multiple devices regardless of the branch is preview, experimental, daily, alpha, beta or stable. Is there not a team running daily automated build tests on Nexus devices other than the Nexus 5 and one version of the Nexus 7? If you want to call that testing, then that's laughable.

        And don't give me that nonsense about the FIRST developer preview argument. Both Apple and Microsoft also had their FIRST developer preview and they managed to push their previews to devices, some of them made almost 3 years ago.

        There will be carnivals in hell, when Google or any Android vendor pulls that off.

        This preview should have been available on all Nexus devices made within the last 2-3 years from day one. What Google is going to learn the hard way are the bugs that are exposed from not running L on more than 2 cherry picked devices early enough.

        The earlier they get feedback from developers and testers using different Nexus devices, the better L is going to be on release date. If they wait till the last minute, they'll definitely be overwhelmed with complaints and bugs. L is not a minor update, like Jellybean or Kit Kat.

        L is a major update and it befits Google to make it available on as many devices as early as possible. Cherry picking the latest hardware and fastest SOCs is not going to cut it.

        Heck, they did that with Kit Kat and they got burned. Early versions of Kit Kat had performance issues and bugs on older Nexus devices, even though they claimed performance had improved. Apparently not much testing was done on older devices.

        Oh and I still don't have the latest version of Kit Kat on my Nexus 7 LTE (2013). What excuse do you have for that on behalf of Google?

        Again, the Nexus Android build team should take notes from Cyanogen, Apple, Microsoft and 99% of open source projects to see how pushing software is done seamlessly on multiple branches and multiple hardware, both old and new.

        • Will Tisdale

          This idea of the L preview was never meant to get rid of bugs. It was to get devs to change their design.

          I don't disagree with you about the fact their testing model is crap - there is no testing done until the public release. But nothing has changed in that respect. In one version, Froyo I think, they broke HE-AAC playback completely. In the next they completely broke rtsp streaming. They'd made a bunch of changes and not tested them and broken some critical things. The proper 'testing' is done once a public release is made - mainly by Nexus users, because the OEMs do tend to try to fix bugs.

          I don't think the Android team are particularly interested in bugs and they never have been. My criticism of their lack of testing has been very vocal on their bugtracker in the past - particularly when I was doing Android development, but it's a waste of time.

          Once you get your head around the fact the the preview is for design, and nothing to do with bugfixing, it makes sense that they have only released it for 2 devices.

        • http://mwinter.in/ Yan Gabriel Minário

          I wish I cloud double thumb up you so there is a comment talking about how right you are.

  • Kingu Prima

    so no nexus 4 version expected :(

  • Diego De Barbieri

    Still the old version on the web :(

  • http://victorhaggqvist.com/ Victor Häggqvist

    FYI, system settings seems to be reset to defaults.. That touch sound was reenabled!! (A flash with on -w that said)

  • Shining Wing

    A Google employee on G+ has said that this build only updates the GMS APK so that it works with Google Fit. https://plus.google.com/114243379843599336175/posts/4YZmHtR33cw

  • Suli

    When is the release date?

  • Xiang

    A quick question.
    Does camera in hdr+ still very lag in this released?
    This is the only bug make me away from L...

  • YouNex

    I want the 3.16 kernel !

  • Ashmedai ♔

    will there be an OTA if I have only flashed version of L preview? :p