More Reading

Post navigation

202 Comments

  • I honestly like lollipop…but itll be hard to make an andy lollipop figure to put at googleplex…so ima go with lemon head or lifesavers kinda jumping on the similar bandwagon as teaming up with kitkat….but i did see a delicious lava cake at the store this morning while getting my ice coffee…ohhh so many options

  • Hannah .
    I agree that Gary `s article is nice… on saturday I got a gorgeous Land
    Rover Range Rover from earning $5743 thiss month and in excess of $10,000
    this past-month . without a doubt its the best-work I have ever had . I began
    this six months/ago and almost immediately started to bring home more than
    $85, per-hr . view website

    …………………………………………….

    Ｗ­­Ｏ­R­Ｋ­Ｓ­­7­7­­.­Ｃ­Ｏ­­Ｍ­

  • I Feel Like a Kid On the Night before Christmas who can’t wait to open their gifts the Next Morning :):):)

  • Google releases next version of android at Google I/O…. bout an hour after announcement Motorola announces that it has begun pushing it out for the moto x, moto g, and moto e and cancels plan for the Droid line to be updated to 4.4.4 and will instead be updated for the next version of android 4.5 or 5.0 🙂 🙂 🙂

  • This is what they’ve been doing every year, with the exception of last year when they delayed the release of 4.3. So where’s the news? Don’t these people know Google releases two versions of android each year, not one like Apple? WTF?

  • LemonDrop
    Licorice
    Lobster Tail
    Lemonheads
    Laffy Taffy
    Lava Cake
    Lemon Bar
    Lollipop
    Life Savers
    Lychee
    Lemonade
    Latte
    Lady Fingers
    !?

  • Can anyone suggest an app like Zumocast but for a Droid Maxx. I want to be able to pull open, or play file on my phone from my PC

  • It will be 5.0 (I’m hoping Lollipop). Switching runtimes is a big change and definitely deserves a version increment for the milestone. Giving us ART a year early to test out was necessary for such a big change.

  • Quick! Name as many L candies and desserts as you can think of:

    Licorice
    Lemonheads
    Laffy Taffy
    Lemon Merengue
    Lollipop
    LifeSavers…

  • I wouldn’t be surprised if what AP has been leaking for months is Spot on. They have a shtton of information

    • No kidding.

      It’s going to hurt to have this previewed for us today, then not be able to get our hands on it for 4+ months.

  • google already does beta testing with Chrome, it makes sense for them to do something similar with Android

  • Here’s to hoping part of the focus is battery savings…since battery tech isn’t really moving would be nice to be able to have phones like the x with multiple day battery life.

  • Maybe they will go a different route with the name. Maybe it will be call Larry (Page)…

  • This will just make it easier for apple to “borrow” new elements and roll them into iOS 8.

    • well right now all the Nexus 10 tablets are out of stack as well as all the GPE devices a week before I/O so that must hint at something.

  • 1) Didn’t Google release Jelly Bean at I/O with the Nexus 7 in 2012?

    2) Linzer torte

  • You guys are going to be disappointed if you are expecting the release to have a name. For now (Tomorrow) it’s just going to be L.

    And it’s a huge update, I hope OEMs will have a chance to look at it ahead of time, some devices would possibly be left behind.

  • I like Lemonhead for the next version. In my head, I can already see the Lemon shaped android head (with antenna ears) and the statue on the Google campus.

  • They should make the L another 4.x variant, so they can make 5.0 called “Mustang”. Not a dessert, but it would be awesome! B-)

  • I’m thinking if they go with a dessert it could be Lemon meringue if they go with a candy I’m thinking Licorice or Lolipop.

  • Lets hope they give devs the preview so it can run free through XDA. My body and my phone are ready.

  • This is great actually. I’ve always wanted Google to take this approach from Apple and implement it. By allowing a preview (and hopefully this means a beta for developers) to access, this allows more apps to be ready for the update. Could possibly allow OEMs/Carriers to be ready sooner (although that one is a huge wish), and lets us know what we have to look forward to, effectively building hype.

    I’m so ready for Wed.

    • Yes on all of this. I’m really hoping for that OEM/Carrier thing working out with this. Would be great if I could buy any higher end Android phone/tablet and be able to expect updates.

      • Exactly. I’ve never understood why this wasn’t the way it was. I always felt that besides the “fragmentation” (which can be debated depending on who you ask), that this was one of the main reasons that apps have issues for so long. Because they don’t get access to the new build until we get it. So then we’re both sitting here, waiting for new build so our apps can function properly.

        Fingers are crossed for beta build for devs tomorrow.

        • Yeah, I’m kind of wondering if they’ll just offer “preview build” factory images for Nexus devices on this, but not push updates out over the air until the fall or whatever. Which would work perfectly fine. They could even block app reviews (and just allow bug reports) to developer when someone is using a “preview build” or whatever.

        • The issue is that OEMs don’t want to update. They make money by selling hardware, having to spend resources updating an OS on a phone they are no longer making money off of is counter to corporate culture.

    • Well… I do think that previews or early access to new Android version is not really the issue. Developers are not eager to update to new guidelines or new features and API’s that much because even though after months of release, not everybody has the software anyways. Less than 20% of the population of android devices have kitkat after months of release. There’s a sense of “complacency” for devs not to update to latest android standards because of the very slow rollout of the software and that what they currently have will still work for a long time.

      Imagine this (wishful) situation…. If one day Google solves fragmentation and update issues…. A new version is released, 100% adoption after a couple of days…. Dev’s will be compelled to update because their apps will not work anymore and is already outdated.

      • Do we really want 100% adoption of new versions of Android? That would mean that the next version would have to be available on every low end device that doesn’t have the sensors and technology that newer devices have? That seems like it would limit Android’s ability to grow.

        • it’s not about the hardware dependent features. Just the codebase, the compatibilities, the API’s. Can you point out Kitkat specific features that need very specific hardware??

          • Off hand I can think of Tap and Pay but you’re absolutely right and I agree with you. If the iPhone 4 (4years old) and iPad 2 (4 years old) can run iOS8, then we should be able to have over 80 percent of Android devices running At the very least Jelly Bean, preferably Kit Kat.

          • Well 60% of android devices run jb so we’re almost there.

            And while I don’t know about the ipad2, but apple has confirmed that the iPhone 4 is not getting the ios8 update.

          • No offense to people who have very tight budget but if you opt for a really really really affordable Android smartphone to the point that it does not have NFC then there is a very high chance that you won’t be using tap to pay in the first place.

            Having existing “older” versions of android is DEAD WEIGHT to the latest versions.

          • That’s a very good point lol. Having to support older versions will stifle progress. You’re right. i do hope Google tightens up their ship this year and pushes back against carriers instead of competing with them. This is why I’d like to see this year from Google and Android:

            * Remove applications from the Play store if they haven’t seen an update in 365 days.
            * Deprecate anything below OS 4.0.
            * Better Enterprise integration and MDM support.
            * AOSP Beta for developers.
            * More negotiating power and Android control against Mobile Carriers (Especially since the carriers are no longer subsidizing devices)

      • I don’t think it’s about making them update to new design guidelines or whatever, but at the minimum, making sure they still function as is on newer versions.

      • But with the early access, it could also benefit the OEM/Carrier update process. Of course, this is a big wish also. But it could do so. So that would be killing two birds with one stone.

        But again…this is a BIG wish on our part. The fragmentation is never really the issue anymore, this is seen by the speed at which international versions, and more recently the Moto X, are updated. It’s mainly down to the OEM additions and carrier testing that hold up updates.

      • Devs generally don’t want to overhaul their apps to begin with.

        Google almost switches design guidelines every 6 months. At the very least they get big tweaks. Sure, it’s nice for us techies to keep seeing new things, but it’s a pain in the arse for devs to keep reworking.

        Conversely Apple has put like 1 tweak on their guidelines out since starting – and it is a tweak because it’s the same layout but flat.

        Android got a layout change with 2.3, 3.0, 4.0, and 4.3. Now we’re likely to see another.

    • A preview makes sense since the rumor is they are going to ditch dalvik and go to ART. developers need the time to essentially remake their apps to be compatible.

      • I forgot about that. That would definitely be a major motivator to get a preview in the hands of devs to make sure it all works.

    • Considering the switch from DRT to ART, I think a preview is very necessary for developers. Many many older apps will probably be dead for Android 5.0+. We’ll see what the back compatibility will be like.

    • Google does everything internally and usually do a pretty good job the first time around but I agree having an iOS like approach with betas over the summer followed by the release in the fall is a good idea. I don’t expect android lollipop to be a huge release so maybe it won’t be necessary. I guess you’ll know very soon

      Androids fragmentation might limit what they can do though

    • Well, OEMs like Samsung and HTC get new versions sooner already, but it still seems they’re behind.

  • I KNEW IT!. . . MORE ANDROID. We need a UI update….maybe…. I don’t know what we need we just need newness

  • Apple approach – Show it off and debut it months down the road. I actually like the idea

      • “Losing Money Every Quarter” is Motorola’s official tagline since the Google’s acquisition.

        yet it wants to convince everybody that:
        4.7″ is great.
        thick yellow brick is design.
        10mp OIS-less is perfect.
        2,200 mAh is awesome!

        Active Display is differentiation.
        “Moto X” is branding.
        MotoMaker is marketing.

        • I’m not one of them, but a lot of people like the 4.7″ form factor of the MotoX. Choice is good. Also, as design is subjective, I’d say that personally I quite like the hardware design of the X.

        • so by your criteria the only thing anyone anywhere ever wants is either an iphone or a galaxy s device?

  • Taking votes:
    Laffy Taffy
    Lancaster
    Lemonheads
    Life Savers
    Lindor Truffles
    Lip Pops Lollipops
    Lolli Pops
    Long Boys
    Lonka
    Luv Pops

  • This is great news! I think a lot of people have been hoping they’d do this for a while to make sure “everyone” can get their phone updates out at the same time, to make sure app devs have time to get their apps ready… and to make sure there aren’t 20 bugs in it!

    • I always thought that was the point of the Nexus program and why they got the updates first.

      • Maybe the dev build of the “L” release will only be available for nexus devices?

      • Technically, that was true. However, this is more clearly a “hey, if you’re not a developer then you probably don’t want this to be on your device”, since a lot of consumers ended up with Nexus devices.

        It also gives the OEMs a 4-5 month head start on updates, so they have absolutely zero excuses for late updates, since the major features are going to be set now, and everyone can work toward bug fixing.

        • If this is how they do it, that would be simply amazing. Brilliant idea. Q3 comes around and all the latest phones will recieve an OTA at the same time to the latest version. Fragmentation could potentially be a thing of the past… This is exciting.

      • The “point” of the Nexus program was to show off the best from Google, having stock Android.

      • I think that was the point of the Nexus program at first… but google has been grappling with the expectation of everyone wants the exciting new thing for a while. GPE helped speed that up, but I suspect part of the point with this is to go much further in eliminating that.

  • I think this might be similar to how Apple does their updates. Manufacturers will get ahold of it so that they can have it released for their flagships soon after it’s released. This is great news.

  • Wonder if they will do betas like ios. They definitely could use the feedback with all the bugs before release

    • I’m fairly certain that it will. Kit Kat was developed on gimped Nexus 4s, and it looks like that may continue to be their target to ensure that they don’t let the base OS processes get out of hand. Only way to keep that up is to make sure they have a build for the Nexus 4.

      The only reason that the Galaxy Nexus was left behind was because of the OMAP processor. Otherwise, it would be on Kit Kat; it certainly has the specs for it, just not the vendor firmware support.

  • So it does sound like they are taking the “apple model” of updates. Preview it and send it out to the masses a couple of months later

    • And I love if this is what they’re going to do from now on. I never understood the whole “keep it locked up until its finished” model.

    • Please don’t attribute beta testing to Apple. We don’t need another thing for them to pretend they invented.

      • I never said Apple invented beta, but I do agree with what your saying. Just comparing it

      • It will likely be access to a pre-release branch of AOSP. Hence, once the code is uploaded, you can compile the new version for your device, provided the firmware blobs for your platform are available of course, just like any other version of AOSP.

      • Artem, from androidpolice stated that there are some rumors that Nexus device may get a preview build before the release build…. (Not saying that this will happen this week…. but its still good info to know)

    • Just a state of mind. I’d rather know what new features will be coming, and the fact of knowing that developers are getting ready early for the features so it’ll be ready in time for launch makes the wait easier.

      • Well to me, that’s teasing me with something awesome and saying I can’t have it yet. I don’t like that. lol

    • Be willing to bet my bottom dollar that one of the reasons they decided to preview it was because they’ve got Apple trying to act like they’ve caught up to Android. I imagine this will put Apple even further down the mobile OS totem pole.

    • I’m pretty sure it’s a release. He didn’t say preview, the numbnuts that wrote the article did.

    • Sarah
      . I see what you mean… Henry `s c0mment is inconceivable… on tuesday I
      bought Mazda MX-5 after making $8050 this last five weeks and-also, ten k
      this past-munth . with-out any question its the easiest-job Ive had . I
      actually started five months/ago and pretty much straight away began to bring
      in over $72 per/hr . check my source

      w­w­w．w­o­R­k­s­7­7．c­o­m

    • My
      Uncle Evan recently got a nearly new white Toyota Land Cruiser by parttime
      working online at home… browse around this website

      w­w­w．w­o­R­k­s­7­7．c­o­m

    • I think lemon meringue pie would be sweet too! Maybe they’ll go with it since they decided not to stick with key lime pie. I don’t think they are gonna do another name-brand thing again.

      • I think they should….at least 3 more times. KitKat is red, Lemonhead would be yellow, Mike & Ikes would be green, Nestle Crunch for blue. The company colors!

        • But a type of pie fits in with what Android is really named after, which is a dessert not a piece of candy.

          • eh….they already broke the cycle with kit kat and jelly bean. And would you really eat a honeycomb after dinner? 😉

          • yeah of course! that was the only one I didn’t think would be weird to eat after dinner haha 🙂

  • I’m surprised. Figured we’d see it next year. /s

    I do want a new Nexus 10, though. Please Google.

Comments are closed.

Related Posts

back to top