The Android 4.4 update, aka KitKat, still has yet to roll out to a large number of Nexus device owners out there. And, in desperation, some users are resorting to methods they probably don't fully understand in order to get the OTA, one of which is clearing the Google Service Framework data. This method isn't new, but it's one whose side effects are not generally considered by those who use it, at least according to Google engineer Dan Morrill.

In a reddit thread on the subject, Morrill states, essentially, that clearing the framework data is going to break stuff. Specifically, any apps relying on GCM functionality (Google Cloud Messenger) for things like push updates may freak out, stop sending notifications, or engage in other odd / less than useful behavior. Specifically, he says the following about clearing the Google Service Framework:

Doing this changes the primary ID by which Google knows your device. As far as the servers are concerned, the device was basically factory reset. There are many downstream effects of this, but a big one is that this invalidates the tokens used by any app that uses GCM (which is nearly all the Google apps, and a ton of third-party apps.)

How apps react to GCM IDs changing varies by app. With Play Store you have to log out and log back in, I think Gmail usually handles it transparently eventually but won't get new mail notifications for a while, etc. Some apps you may have to clear data on to recover. All apps will simply stop getting GCM push-messages, until they get a new GCM ID; some do this frequently, others rarely, and some apps use the GCM ID as an ID on their own servers (as it is opaque and basically random), so other things besides push messages may not work.

Nothing bursts into flames, but it makes a ton of nuisances on the device, including some that can look pretty mysterious. Your mileage will vary depending on what apps you use.

All of this can be avoided by just doing an 'adb sideload' if you are impatient.

No, it's not the end of the world, but it's the kind of thing that you'd probably end up factory resetting just to solve, and that sort of defeats the purpose of a no-wipe update, doesn't it? Instead, Morrill asks that eager power users utilize the adb sideload command to flash the update manually and avoid all this potential messiness.

In a separate thread, Morrill discusses the Nexus OTA rollout process, and why during the first day or two of the update's release only a very small portion of phones are selected to receive it.

Rollouts are conducted in phases. Typically they start at 1% of devices for around 24 - 48 hours; we watch the return rates and resulting device checkins and error reports (if any), and make sure nothing looks wrong before sending it to more. Then typically it goes to 25%, 50%, 100% over the course of a week or two.

What the percentages mean is that when your device checks in, it has a 1% chance (for example) of being offered the OTA. If it doesn't (randomly) get an offer, it will never get an offer until the next batch.

IOW, once your device checks in and gets turned down, that's it until the next batch. Mashing on the "check for updates" button just causes your device to check in again, and get automatically turned down again. Think about how that makes your device feel! WON'T SOMEONE PLEASE THINK OF THE PHONES?!

That said, once the new batch does start, hitting that button does give you a new roll of the dice -- but once. Since devices usually only check in for system updates every 24 hours (I think? Certainly on a many-hours basis) this can get you your shot sooner than it would happen on its own.

So, mash away. :) Just be patient, and mashing on it more often than once or twice a day isn't going to gain you anything.

Edit: also, keep in mind that this isn't first-come/first-served. You're not racing other devices to get your slot in the current batch, or something.

So, tapping furiously at your check update button actually does absolutely nothing in any practical sense, though I suspect most of us were already intuitively aware of that fact. The batch system for rollouts is basically what you'd imagine, too - as the days go on, the group receiving the update grows, until eventually it is available to all devices.

This isn't exactly earth-shattering information, but it's good knowledge to have, I suppose.

Reddit [1], [2]

David Ruddock
David's phone is whatever is currently sitting on his desk. He is an avid writer, and enjoys playing devil's advocate in editorials, and reviewing the latest phones and gadgets. He also doesn't usually write such boring sentences.

  • Raloc

    I wouldn't clear my framework if your OTA process didn't suck ass, Google. gibe me the ota

    • Derek Traini

      Just sideload the ota and stop posting stuff like this.

      • Raloc

        If they made the OTA available for download so I, the supreme power user, could get at it, I would.

        • http://www.deathbycone.com Jared Kotoff

          "All of this can be avoided by just doing an 'adb sideload' if you are impatient."

          • http://www.Nave360.com Sebastian Gorgon

            Not if he is using a Google Play Edition phone, then he is just waiting for fuck knows what since Google is taking their sweet time.

          • shadowdude777

            Google is taking their sweet time making sure it works. I don't know why you think they would just literally send out the same shit to the Nexus 5 and the GPE One and S4, because that isn't how it works. The hardware is different, the drivers used have to be different, the testing process has to be done for each device, etc.

          • http://www.Nave360.com Sebastian Gorgon

            HTC made sure it works before sending it to Google to deploy to HTC One GPe devices...

          • http://petercast.net Peterson Silva

            Yeah, well, it's not like they had plenty of time _before_ publicly releasing Kitkat to test it on the devices, right? =)

          • Alan Shearer

            How do you know the exact date the new os version was considered final? ever done programming or bug fixing? sometimes even with ample time, unexpected things occur and cause delays. this is not like fabricating a pair of pants or a wooden stool, this is more like forging a sword, it is half art and half science.

          • Matthew Fry

            If you're like my company, you're literally committing fixes hours before the deadline.

          • Alan Shearer

            yes and yes, but at the same time, how often do unexpected bugs appear? (and I bet like me you sleep like a baby the day after :P )

          • Matthew Fry

            Um... all the time :-D

          • http://petercast.net Peterson Silva

            ... And this is Google, which means they have a lot of money and power to iron things out before releasing it to the public - what, so you believe they finished KitKat one or two days before the event? Even with ample time, ok, ok, got it, but come on. If it's an unexpected problem just release a statement or something.

          • Adrian Zugaj

            Sure they did, but when you rollout an update, you suddenly have a LOT more devices getting the update than what you were testing with. Errors are then more likely to crop up.

          • http://riteshtripathy.wordpress.com/ Ritesh

            So, they should have waited till it was fully ready for ALL devices before announcing it? Cool. Except, in that case, the same people would be moaning about "where is the KitKat?".

          • Gator352

            Prolly has no clue as to what adb is...or even sideloading for that matter.

          • Mick Collingwood

            Well he is a 'Supreme Power User' maybe Google should update his device before anyone else and us mere mortals can wait! 😂

          • JensAstrup

            The factory images weren't up until days after the OTA began

          • b9876

            If there was an OTA package. For example, for my N7 LTE, there isn't.

            I would gladly adb sideload, if I could. I cannot flash the full images either, because flashing the system requires new bootloader and radio and I cannot flash either without unlocked bootloader.

        • Alberto

          well as power user so just use factory image like i did. or just custom rom, if you got nexus the mean your phone is unlock and rooted for sure

        • http://aidan.info.tm/ Zack Casey

          If? It's been available for a week or two now.

          • Ian Santopietro

            I believe you can "fastboot flash" the factory images even on a locked device. And, it's possible to flash it without losing any data. Just be sure to fastboot update without the -w, or extract the update image and flash the contents manually (avoiding the userdata image)

          • b9876

            Your belief is wrong then. At least on N7 2013, you need unlocked bootloader to fastboot flash the images.

          • http://www.techmantis.net/ Minja Miketa

            You don't fastboot. Use adb sideload....or unlock your bootloader. It's very simple, fastboot oem unlock.

      • CasperTFG

        The issue becomes no one wants to deal with the dreaded exclamation point inside the yellow triangle in Device Manager. USB drivers aren't always reliable. For my Nexus 10, I updated SDK Manager, searched Samsung's website and perused them internets - all failed attempts to find the driver. I even added N10 code in platform-tools for it to be recognized. No luck. You can't extract the driver from Wug's toolkit. For a subset of us, it's hunker down and wait for the OTA.

        • Ian Santopietro

          You should switch to Ubuntu. No drivers necessary.

          • http://petercast.net Peterson Silva

            Exactly. It's comments like this that reminds me how hard life is there on the other side...

          • EowynCarter

            And some other other device works way better on windows ;)

            But yeah, as far as android device are concerned, ununtu works better.

    • http://halljake.com Jake Hall

      As a software developer, staged rollouts like this are pretty much the BEST 'OTA' (or whatever your deployment avenue may be) process...

      • Alan Shearer

        wish I could upvote this a couple thousand times.

      • Mick Collingwood

        Totally agree 100%

      • Wyatt Neal

        Ditto. We manager a few hundred nodes and we do ythe same style of roll outs; the impact has to go through the roof when you think about "how critical" people feel their cell phones are and even if you only broke 0.1% of the first 1% roll out, that's a few thousand pissed off android users.

    • Luis Augusto Fretes Cuevas

      You're gonna get downvoted for stating a fact. Apple manages to do it in a single day to every iOS user (iPhone 5, iPhone 4S, iPhone 4, iPad 4, iPad 3, iPad 2, iPad Mini) and Google can't even manage to deploy it to all Nexus 4 (which are not even 1/50 of any iPhone's user base)... and this is Google we're talking about, their server power is far beyond Apple's.

      Android is great, but Google sucks at updates, is that simple.

      • http://www.Nave360.com Sebastian Gorgon


      • Derek Traini

        Have you thought that Google and Apple just might do it differently?

        • Luis Augusto Fretes Cuevas

          Of course. They do it differently, Apple does it better than Google.

          • Derek Traini


          • Alberto

            apple os07 bug got lockscreen bypass every devices was effective

      • Alexei Watson

        Apple runs beta firmwares. which is what google should do

        • Luis Augusto Fretes Cuevas

          I'm aware of that. But that's still Google's decision and doesn't constitute a counter argument to their crappiness at updates.

          It's unrelated to deploying updates, Google isn't testing different variations of the update, they're just updating them, whether they do their testing completely at close doors or by using public betas is indifferent to this issue.

          • pfmiller

            It sounded to me like he was agreeing with you, not trying to make a counter argument.

          • Your Name Is Too Long

            When was iOS 7 announced? Released?
            When was 4.4 announced? Released?

      • Raed Ibrahim Albloushy

        Yes it may be true but have you tried it in practice? I did, when apples releases the other on one day the severs are really slow and I think I spent 4 hours or so trying to download it and then it won get verified because of a server problem so Rolling update in a day.... Bad idea

        • Alberto

          some devices had to get restore to get back 100% functional. If we get all the update at the same time server will be slow like he said people will complain speed are horrible for billion dollars company

        • Luis Augusto Fretes Cuevas

          Are you really even attempting to argue that Google is better at deploying updates?

          Unless you had to wait for a month before getting your update I don't think you can even attempt to do it without looking ridiculous.

          • Lex

            when the iOS7 rollout their update huge amount of user also get's the lock screen bug so it's much better to release first the update in small amount of device to minimise backlash

      • Alawn

        This isn't really true. The new version of iOS is released as a beta to developers for months before it goes to everyone else. All bugs should be fixed before the real release.

        • Alberto

          but they are not.

        • Luis Augusto Fretes Cuevas

          Again, this doesn't constitute a counter argument. Whether Google does testing behind doors or using a pubic beta program is irrelevant to this issue.

          And even if it mattered (which it doesn't), it's still a decision taken by Google that results in a crappier experience.

          • EowynCarter

            Just because you have to wait a few days ? Seriously.? Get a life, really.

      • esper256

        If Apple's updates all roll out on the same day, that just means ONE thing:
        Apple had the update available for various devices, but withheld them from the public until the last device's update to be ready was ready. So it's a strategy of withholding updates, not getting them to users super quickly.

        Google is releasing the updates as they become ready. In other words getting them to users as soon as possible without holding them back. Although yes they do a staged rollout. Necessary on Android since they don't do a developer beta like Apple does. Think of Apple's update as a staged rollout too, done through the developer beta and ending in broad customer release.

        • http://aidan.info.tm/ Zack Casey

          I never thought of that...

        • samshit

          You forgot to mention beta release from Apple too

      • Matthew Fry

        Did you even read what the dev said? It's not a matter of server capacity. It's a matter of Google's established staged rollout process. You can argue that their process is not to your liking but their reasoning is sound. This very staged rollout caught a bug that destroyed all of your encrypted data if you typed in the password incorrectly before it reached everyone.

        • Luis Augusto Fretes Cuevas

          It seems some of you are incapable of understanding that saying "they chose to do it that way" isn't an argument, it's irrelevant. Their update process sucks regardless of whether is on purpose or not.

          Catching bugs is another issue entirely and no update and no software will never be bug-free. Google chose to do testing behind doors, Apple does it using public betas, that's other issue entirely.

          • http://aidan.info.tm/ Zack Casey

            Your argument is essentially "they choose to do that way" too, only it's Apple instead of Google.

          • Luis Augusto Fretes Cuevas

            I don't think you understand my argument (in fact, I'm not making an argument, I'm just stating facts, that Apple manages to update its devices faster and more consistently than Google is absolutely non-controversial)... Apple chose to do it some way, that way is better, whether Google's update process is on purpose or an accident is moot to whether Google's update system sucks or not.

          • http://aidan.info.tm/ Zack Casey

            So, because Apple chooses to do something, regardless of what it is, automatically makes their method better?!

          • Luis Augusto Fretes Cuevas

            A mental synapse is getting lost somewhere, I'm not saying the system is better because Apple chose it, I'm saying the system is better, period. Whether Google chose another one or does it by accident is irrelevant to whether Google's system is inferior or not.

          • http://aidan.info.tm/ Zack Casey

            You're not making any sense, if that means I have a "mental synapse", then so be it, but that doesn't mean any what your saying is "fact" to any degree.

          • Luis Augusto Fretes Cuevas

            I'm glad I'm making sense.

          • http://aidan.info.tm/ Zack Casey

            I'm glad you missed my edit.

          • squiddy20

            "Apple chose to do it some way, that way is better," And that is your opinion. Not an empirical fact.

          • Luis Augusto Fretes Cuevas

            Oh really? Tell me, what system actually updates devices faster, more consistently, across all models?

            Because that's the fucking point of an update, that users get it. It's a non-controversial fact that Apple is better at it. It's an empirical fact (measurable), not an opinion.

          • squiddy20

            And when Apple sends out an update that has a bug in it, ALL devices get that bug, instead of just a few.

            Also, in the end, Android users get the update too. It just takes a bit longer. But besides the Android "power users", most people don't even care about system updates. On the other hand, when a new version of iOS comes out, everyone's screaming their fanatical little heads off about if they all got the update. And when iOS 7 came out, I heard of people updating days, even weeks, after it was first made available.

          • Zack Whitfield

            You're just completely incorrect. Google announced 4.4 and had it on devices within two weeks. Apple had like 3 months of beta before iOS 7.

          • http://halljake.com Jake Hall

            I think you mean to say: "it sucks for a small minority of users, but has big advantages for the majority which ultimately makes it a compelling choice to make"

      • Mick Collingwood

        Hmm iOS 7 devices, Google 1000's. IOS is released to developers months before it's release date and even then it's still bug ridden if you can manage to get the update on release day. Took me 3 days and more attempts than I can count for the version 7 update. In fact everyone I know with iOS devices had trouble getting the update and trouble once they had it. The same happened with the previous update. In comparison my galaxy nexus updated to 4.3 on the stated release day with no problems. Nexus 7 updated to 4.3, took a couple of days but again no problems, took till today to get the 4.4 update. Downloaded and installed no problem. I had to wait a week. Big deal because when I got the update I know other people already were reporting any bugs back to Google and I never heard of major problems.

        So basically Google might take longer but it's done right where Apple pushes an update and it all goes wrong. I know what I prefer as an owner of both android and iOS devices.

        • Luis Augusto Fretes Cuevas

          What are you even talking about? Google has only four devices to update: Nexus 7 (2012), Nexus 7 (2013), Nexus 10, Nexus 4. That's it.

          Google doesn't update the GPe editions, Samsung and HTC do it, and HTC has publicly stated it already sent the update to Google, Google is just slow at everything related to updating its devices.

          Now, whether Google hunts for bugs behind close doors or publicly is a different issue entirely, and your personal experience is an irrelevant data point.

          • http://aidan.info.tm/ Zack Casey

            Expect those devices are made by different manufacturers: two by Asus, one by Samsung, and another by LG. Oh, drivers, *whistles* come here, boy!

          • Mick Collingwood

            Are you really naive enough to think that Google only has four different devices to update?

            Plus my experience is totally relevant as it's what we're talking about. There's a simple solution though if you don't like Google's update procedure don't use Google product. See if you fare any better with Apple or any other manufacturer.

      • Zack Whitfield

        Apple's servers go down and it takes hours to get the download when it's released. They leave bugs which are forced to be hotfixed (see iOS 7.0.x and the timeframe they were released in). Google releases to 1%, spots those types of issues and fixes them and updates as necessary.

        Yes, Google occasionally has to hotfix something serious, but it's a lot rarer Google do it than Apple, and this is exactly why.

  • Richard Borkovec

    All I know about OTA for system updates, my phones gets it after my tablet. And even that, It's always (ALWAYS) about a week and a half to two weeks after the update rolls out. I'm always in that last group to get it. This really is making me think of sideloading the OTA, because I'm tired of waiting that long.

  • http://www.googlepants.com/ Wizard of Odyssey

    Surely they have enough beta testing to push this out to people who really want it?

    Must we point to Apple, who puts out point releases to everyone all at the same time?

    • Jordan

      I think Google over looks how big of a deal pushing it out to as many people as possible all at the same time is. Apple gets a lot of publicity by word of mouth & social media for it.

      It's my understanding that Apple rolls out the update similar to the way Google does(staged). The major difference is when you manually check for the update on iOS, you get the update.

      • Imparus

        No the major difference is the amount of devices they can push the update out to, and apple products is loved by the media. However I do think that when we manually check for update we should be able to receive it.

    • Thomas’

      Apple's advantage: They can claim how quick their updates arrive.
      Apple's disadvantage: They already had to patch iOS 7 twice, because lock screen security was broken. Plus, people are still getting blue screens.

    • Imparus

      Expect that there still are huge bugs that aren't resolved that get pushed out to normal people. I had to fix a problem where facebook wouldn't open unless it recived the latest update, but it wouldn't allow me to update facebook, I couldn't even delete/uninstall to fix it that way, I had to wait on the current iOS bug fix update, before facebook could open again. Worst part was it was my parrent iPad, and they was just mad that it didn't work.
      TL;DR staged roll out is a good thing, we power user can always just sideload.

  • http://www.Nave360.com Sebastian Gorgon

    I was hoping to get a clear answer to where the hell is my OTA for HTC One GPe? HTC finished it last week gave it to you to push it and it's up to you to click the button and roll it out, if that's not the case then please explain.

    • http://www.nerdshowandtell.com/ nerdshowandtell.com

      HTC probably used the same version that had the bugs google just patched, so now back to HTC to fix, and then back to Google again.

  • Kenny O

    Lies. Mashing the check for updates button totally works. I know it does.

  • DJ SPY

    Crap, I cleared mine the day they said they were starting to push the OTA update.

    • Onel Benjamin

      I cleared mine about a thousand times.

      • remister

        I've cleared mine on many nexus devices. I am okay!

      • Gav456

        Twice a day since rollout began =/ worked 1st time with 4.3.1 so I figured it'd work now, oops

      • RBI411

        I've been clearing mine every two hours trying to get this damn OTA. Might explain why I'm not getting a ton of notifications for my Google apps and maybe why the play store keeps installing things to my home screen even though I have it set not to.

  • Onel Benjamin

    I think OTA updates should get rolled out to devices differently, If Google, really wants to do staged roll-outs, they should at least do it priority wise. Meaning, who ever uses their devices most and logs into Google services should get it first. My coworker doesn't touch his tablet its left at work all the time and he has the update -.-

    • Alberto

      good point but what happen if the update brick those devices?

      • http://www.Nave360.com Sebastian Gorgon

        Gives google an incentive to hurry up and fix it.

    • Imparus

      Wouldn't it be the other way around, since they would loose the most if the OTA had big bugs or bricked the device.

      • http://www.Nave360.com Sebastian Gorgon

        Someone who actually uses the phone has more chances of finding bugs and reporting them to google than a person who doesn't.

        • Imparus

          Just because they are using their devices a lot doesn't mean they are power user, they could just be normal user who would get pissed that their device suddenly stopped working.

      • Onel Benjamin

        What @Sebianoti:disqus said, and also, heavy users like us, pretty sure have everything backed up if something goes wrong. Unlike someone who has no clue about the device, just got it to go on YouTube!

    • Adrian Zugaj

      It's fine the way it is. Sounds like someone's got update envy ;)

  • chris125

    Yet it's been over 2 weeks...

  • remister

    Where the registry entry that I need to edit to be first in line?

  • marycontrary

    So what's the problem?
    Google is doing it the best way possible in order to minimise backlash. If you can't wait, gee-wizz, guess what? With Android there's a way to sideload! Now, stop complaining and be grateful we aren't having the iOS 7 experience.

    • http://aidan.info.tm/ Zack Casey

      Part of me wants to blame iOS devices for the lack of patience people have over OS updates. Even then, Nexus users are lucky enough to even GET an update within any period of time.

    • Gabernasher


      • Marc R.

        Can you please tell me WHERE you were promised that you'll get the update as soon as the new version of Android is announced?

        • KaiserJay

          He's joking :)

          • Marc R.

            doh... I really need to go to bed (it's already 2:22am here). My sarcasm detector is not working anymore...

        • Matthew Fleisher

          Can you please tell me where you left your sense of sarcasm...

          • Kmastermaster

            At yo' mamma's house.

        • NinoBr0wn

          Cmon man, he said promised in blood.

    • Securus GPS

      Amen to that! iOS7 was nothing short of a total nightmare...and Apple is STILL having issues!

      • Dennis Ulijn

        Just wondering, what was this 'nightmare' you speak of? Not optimal speeds on older devices?

        • http://riteshtripathy.wordpress.com/ Ritesh

          Hint: This topic is about the update process.. not the OS itself.

          • Dennis Ulijn

            Then what was the nightmare? From what I know my apple devices updated the day or the day after the update was announced. Nexus 4 ota update is 3 weeks after kitkat was announced and counting

          • http://riteshtripathy.wordpress.com/ Ritesh

            You don't get it. iOS7 was announced and released to devs MONTHS before it was released to regular users. KitKat was announced less than 3 weeks ago and has already been rolled out or is rolling out to all but one device. Major difference.
            And the ioS7 nightmare was the sheer number of stuck, failed, taking-forever-download, downloaded-without-consent-and-hijacked-storage-space reports. And those still haven't stopped coming in..

          • Dennis Ulijn

            Then say THAT instead of "it's a nightmare!" (no direct quote). Still, if that is your argument, I'd love to see Google take the same route Apple takes: multiple channels. OR better yet, like Chrome, where they have the normal, beta, dev and canary channels.

          • http://riteshtripathy.wordpress.com/ Ritesh

            The nightmare was referring to something else, at least in my understanding. Read my previous comment again.

          • Michael Pahl

            The nightmare in my opinion is the 4 second transition effects... lol

          • Mozaik

            which can be turned off as you wish.

          • Michael Pahl

            How about the ability to place an icon in the bottom right of your screen?


          • Mozaik

            what !!

          • Michael Pahl

            On iOS. you can not drag an icon to the bottom right of your screen without it jumping back up to the top left most available spot.

          • Mozaik

            ohh ok , so what ,i will tell you one thing , i love android , but you to accept that ios device from start was not about customization but about how its easy to use and still it is.

          • Dario

            Sorry but what I see is a lot of excuse making in order to make Android still sound like the better choice. As an owner of several iOS and Android devices the Apple upgrade process is light years better.

            And what you described sounds like Android updates on the carrier side. Which adds more fuel to the fire the Apple OS updating is better. I hate to say it but it is.

          • Dennis Ulijn

            This. There is something to be said for Apple still having bugs in an OS that has been out for developers for months, but shit happens, at least developer have had months to update their apps. I updated to 4.4 last week and had a few days where i couldn't use my online banking app. While I knew this had to do with KitKat, I don't know what would happen if some not-so-tech-savvy person (say my mom or even my friends) updated because 'hey cool, i have an update'.
            The reason Apple releases these buggy dev versions is so that devs can update their apps so they still work or make use of the new options of the updated OS. Because Google handles this "Spray-and-pray" mentality, there are not a lot of developers that use the Notification syncing, play games achievement/progress syncing. Where you see that Chrome has a roadmap for the coming versions (through beta, dev, canary), it SEEMS like Android is a quickly gobbled up Service Pack of fixes and small changes. What does Google want with Android? HOLO light or black? Settings surely isn't sure. Even Google app icons don't fit well together, no wonder 75% of all app icons in the Play Store are a straight rip from their iOS counterparts. I wish Android would feel a bit more focused, and a good start is showing developers what the bulletpoints of interest are for the next release, and why not by releasing a dev version of Android; they have the hardware for it - Nexus. I would without a doubt run the dev channel, but i also understand that that means everything can get f'ed up.

          • http://riteshtripathy.wordpress.com/ Ritesh

            Erm... sure!

    • ravyal

      "Stop complaining and be grateful we aren't having the iOS 7 experience"

      Say what you want about Apple, but they do a great job of rolling out the updates to the whole world the same day much better than Google does, which takes about 2-3 weeks or more for the OTA to reach everyone. You just have to admire that about Apple and yet, I am not even a Apple fanboi.

      The point I am trying to make is, Google can definitely do better than what it is doing now in terms of pushing out the OTA to all devices AND they can definitely do a little better with the communication part. If they would have simply release a statement saying there are a few serious bugs that are being worked on and the OTA will be pushed out once they're resolved, a lot of people wouldn't have complained. And why even release the factory image for KRT160 at all if these bugs were such a big issue and the OTA couldn't be pushed out?

      • Sir_Brizz

        Apple doesn't roll out updates to the whole world the same day, though. And certainly not as close to the announcement of a new OS. Their "1%" (which could be a larger percent, who knows) are the "developers" that get the update before it is released.

        • Dennis Ulijn

          Then I would like to see a beta Android build, for the 'developers', just like chrome (normal, beta, dev, canary)

          • Mike

            but there is, it's called factory image.

          • Joshua Thong

            The whole point of the staged rollout is to have a representative sample of testers, not a skewed demographic of developers and tech enthusiasts who know about a beta build. Chrome develops at a different pace, which is not quite suitable for Android.

          • Sir_Brizz

            I don't disagree with that. At the very least they should do better about making sure developers get the update fast so they can fix their apps for the new version.

  • Willie D

    What I found interesting is that my friend got the last Nexus 7 update a week before I got mine. His Nexus was one of the first bought, mine, one of the last 2012 models. His black Nexus 4 got updates sooner than my Nexus 4 in white, the same one he sold me. My Nexus 5 I bought the first 10 seconds it went on sale, got updated for Sprint activation with the ESN a WEEK before some people who bought their Nexus 5 the next day. I believe updates are done on a first built first activated system. The first devices get it first, the last get it last.

    • Richard Borkovec

      My roommate, who bought his Nexus 7 (2012) about 6 months after, me gets every update before I do.

    • http://blog.tonysarju.com/ Tony Sarju

      It's completely random guys. It does not matter who bought it first, etc.

  • http://blog.tonysarju.com/ Tony Sarju

    Very good information. Thanks again AP.

  • http://www.marketnology.com/ Talib Morgan

    On another site someone asked recently why Google doesn't just make the OTAs generally available the Apple does for new versions of iOS. I love my Nexus devices and hate wondering when I'll be lucky enough to get the update. Going the Apple way and letting everyone download it once QA'd and ready would make people very happy - or at least it would make me happy.

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

      Yeah, flashing stock images without having to unlock the bootloader and lose data first would be cool.

      • Mkvarner

        I think there are some tools on XDA for unlocking bootloaders without losing data. Pretty sure I saw one on the portal.

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

          Yeah, but you have to be already rooted for that, which, if you're running the latest Android OS, is unlikely because I'm not aware of any outstanding root escalation vulnerabilities.

          • Jay N

            Or you could just rewrite the sh file (bat file for windows) to not flash "image-occam-krt16s.zip" and pull the system boot and recovery out and manually flash them...

            I don't have a rooted device, just an unlocked bootloader, saw update on dev site on Tuesday, downloaded, adjusted script and ran in terminal :-) did 2 of my colleagues nexus 4's after mine booted and they were happy that it was working fine.

            Colleagues waiting on the OTA are still waiting :-)

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

            That's not the point though - we're talking about a situation where you don't have an unlocked bootloader. There is a trick on some Nexus devices to unlock it without wiping, but it requires root.

          • DonPorazzo

            For me it works like this: If I want to be the first with the updated Android OS, I have to be unlocked, so I can flash images (with or without wipe) therefore I know what am I doing. If I don't know how to unlock it then probably it's better to wait for OTA and I am not that impatient (or I just don't care). Most people dosn't bother with update and they just install it to take away the notification. Of course, here, on Android Police we are all impatient..
            PS. fastboot oem unlock is the first thing I do when new device arrive (maybe 2nd after seeing if it's ok).

      • MeMyselfI

        Which is why the first thing I do is unlock the bootloader when I get a new Nexus.

  • A Black UI is the best UI

    Of course they will say it will "breaks" stuff but without seeing that everything still bloody works without that stupid app in the first place.

  • http://petercast.net Peterson Silva

    1 - Clearing data on Google Service Framework and other apps is the only way (the only I'm aware of after researching for hours) to stop a Google Maps bug that, when triggered, will consume the battery at a rate of 25% per hour. So if they would just fix that I'd be able to stop doing it =/
    2 - I thought, by the title of the article, that they would explain mysteries of nature such as why the vrz moto x is getting kitkat before the nexus 4 =]

  • Mazz

    Yeah I had a feeling. I cleared it like 2 or 3 times and today I got a message that said I had too many devices on GPMAA and had to deactivate them. I assumed it was because of the framework thing and I guess I was right. To be fair aside from signing back in a few times for some apps I'm now sure I see the problem with this. I guess it's annoying for Google but I couldn't care less.

  • Nightfall

    The level of entitlement in the comments is amazing. If you don't understand the benefits of a staged roll out, then you haven't been paying attention. If you want an Apple like experience, get an iPhone.

    • Milind

      Why get an iPhone? Why shouldn't Google learn from the one thing that Apple has done really really well for 6 years? And figure out how to get OS updates to ALL phones (not just Nexus) on the DAY of the release. Not weeks and months later. This is not the carrier's or the manufacturer's fault. It's Google's fault. Force manufacturers using the Play Store to provide the binaries for the phones in at least the last 2 (preferably 3 years) to Google for the new OS update. If they don't do that, withhold Play Store access for all future devices. The problem is not that it can't be solved. The problem is that Google doesn't think that this is a big enough problem. i shouldn't have to buy a Nexus device just to get OS updates. Mind you, I'm talking about a Google experience update. If the manufacturers want to provide their custom OS updates, they can do it on their own for people who want those skins and apps. All though, I'd like to see them follow Google's example here and put their apps on the Play Store for people to download and update. It frees them from carrier stranglehold as well. I'm not suggesting that this is simple, but it's not rocket science either.

      Apple does have it relatively simple with a few devices. But no fewer than Nexus models and Google regularly manages to botch that. It's good that the factory images are available. Why not upgrade images so I don't have to wipe my phone? Microsoft has done it for decades with Desktop Windows.

      • Nightfall

        You really don't understand how things work, or why things work the way they do.

        First of all, you are assuming that manufacturers want Google handling updates to their devices. The fact is that they don't. Those launchers like Touchwhiz and Sense are not just surface level software, they are embedded deep within the OS (that manufacturers have tweaked to suit their needs).

        Secondly, Google can't account for all the different hardware variations out there. There are devices that have IR blasters, stylus input, FM radio, different cellular radios, and so on. These different hardware might seem trivial to you, but Google cannot possibly provide one update for all these different types of hardware.

        Lastly, you are forgetting the level of control carriers have on the devices they support. As much as everyone would love for updates to come out without carrier intervention, its not going to happen. Carriers want to control the user experience through the bloatware they place on these phones. Carriers also require that software updates undergo their own tests before they are released. People assume that Apple can tell the carrier whatever they want, but the most likely scenario is that Apple waits for all the carriers to finish their test before releasing the next update.

        I'm going to take a stab in the dark and assume you are not a software developer/engineer (I'm sorry if I'm wrong). People need to realize that none of this is easy. There is so much that goes into releasing an update. It is not as easy as just flipping a switch.

        Google has handled updates the same way since forever now. Even outside of Android (for example Chrome) Google rolls out updates in a staggered fashion. I'm surprised people are not used to it by now.

        All I'm trying to say is that if the way Google handles updates bothers you to such an extreme, you may want to consider another OS because things aren't going to change anytime soon.

        • Milind

          I actually do understand how things work. And they don't need to work that way. Google, if it wants can fix it. The problem is that it doesn't want to. The biggest problem (especially from Don Morill's various comments over the years) is that they don't think it's a problem.

          I really couldn't care less that manufacturers and carriers don't want to provide updates. Carriers have the exact opposite desire. Manufacturers are looking at short term profit in terms of planned obsolescence to force you to upgrade your phone. What they don't realize is that the lack of support (and OS updates is a HUGE one) leads to lack of loyalty. Apple knows that. Nobody else seems to have figured it out.

          From a technical perspective, force manufacturers to provide drivers for all the proprietary radios and hardware for a new OS release to Google *before* the OS is released. Google needs to create a hardware abstraction layer and create a package for the new OS for *all* phones released at least in the last 2 years with hardware that can support the new OS and make it available for deployment on their servers. Yes, it will provide a Google Experience OS not a customized manufacturer OS. Let the manufacturer provide their own update down he road. The folks who can't live without the Stylus or Infra-red support can wait for it. Ideally, if the manufacturers are smart, they would do what Google has been doing - Provide their apps on the Play Store for folks to download. This decoupled approach will benefit consumers - and the manufacturers if they take the long view. Locking bootloaders, not providing updates in time, turning slightly hostile to the open source community didn't do HTC a favor. Samsung after a disastrous update history with the Galaxy S, improved things withe the S2 and practically outdid themselves with the S3. They went from last to first. Motorola with the new found chops on the X and the recent quick update to 4.4 may well find that to be a winning strategy if they continue to display this agility with the rest of the line up. I was ready to give up on Samsung after the Vibrant. But bought the S3. Today, I bought the LG G2 mostly in the hope that given how close it is to to the N5, the dev community will not let me down if LG does. It's not the only criteria, but a solid phone like the G2 backed by OS updates will win me (and many others) every day.

          And yes, I'm a software engineer and I do this for a living. It's not easy, but it's not rocket science either. I can do this. Google certainly can - if they have the will. Android is now well entrenched and they can learn a thing or two from Apple. And Microsoft for that matter. I have no idea what MS is doing with their phone updates. But their desktop updates are great.

          Eclipse can do it. Mozilla can do it. Apple can do it. Google can as well.

  • PhineasJW

    Interestingly, he didn't say why clearing the framework sometimes works. I've had it work on the second try, one after another. So, it's not behaving as he describes, once/day regardless.

    I suspect changing the primary device ID, as he described, get's you another crack at the lottery.

    Of course, it does have side-effects. I told a friend to do it, and he stopped getting Hangouts messages. Oops. :)

    I'll second the call that there should be an OTA way to force the update. Hide it in Developer Options, if they have to. OTA still feels more "official" than sideloading.

    • Paul Taylor

      Maybe it was just your turn anyway, and that's why it worked. I'm sure there are people out there who had trouble getting pregnant until the day they pressed the Check For Update button, and now include it as part of their fertility rites. (Joke :-)

  • PickSix

    How do the update servers keep count of how many times your device has checked in/been denied the update if you keep resetting your unique ID by clearing framework data? Surely, devices with cleared framework data get more chances during an ongoing batch rollout? An unlimited amount of chances I should say for the duration of the batch rollout.

  • DW Duck

    I don't know one person that has gotten the ota on a nexus 7 2012 or 2013. Not one!

    • Justin Swanson

      And how many people do you know vs the number of devices activated?

      • DW Duck

        Gee, an exact number? Give me a break. Enough that at least one should of gotten it. I own both and haven't seen it. Haven't heard of anyone on G+ saying they got it ota, only side loading.

        • http://halljake.com Jake Hall

          And this, kids, is an example of anecdotal evidence vs. empirical evidence.

        • Justin Swanson

          Well, only 1% of the devices got it. So I guess you don't know any 1%ers. Try the Nexus Community on G+ quite a few have gotten it there.

        • Simon Belmont

          Did you mean to say "give me a break?" Or was that just a total unintentional pun?

          You know. KitKat and so forth.

  • Colin Kealty

    I think they should take a different approach to staged rollouts if bugs/errors is their concern. They should have an almost "beta" opt-in, where people can say "yes, I'd like to be one of the first to get it at the risk of it being broken". Even if it isn't anywhere near 1% of the market that signs up for this they can just push it to those people and have them report what's going on

  • Luis Augusto Fretes Cuevas

    Google fanboys are even worse than Microsoft's, my god. They get emotionally attached to a corporation (that doesn't give a flying fuck about them, just like Apple or Microsoft don't), and can't stand the idea of the company they want to marry and have children with being bad at something, or some other company being better at something.

    Good thing for Google is mostly only its fanboys who buy Nexii or GPe devices, it allows them to prove them a shitty user experience and still get defended when some users with a working brain and critical capacity points it out the glaring inferiority of it in some regards.

    Android is great, I think is better than iOS (for the most part, there's things iOS does better), but Google is the absolute worst at updating devices, even Microsoft is better at this, even goddamn tricking Palm was better at deploying its WebOS updates.

    • http://aidan.info.tm/ Zack Casey

      Look, I'm not implying everyone here is fanboy but have you checked the site that you're on?

      • Luis Augusto Fretes Cuevas

        I'm here. I'm not a fanboy, I like Android (more than any other mobile OS), I like being up to date with its news, does that imply I have to be free astroturfer for it? No.

        • http://aidan.info.tm/ Zack Casey

          Sigh. Look, complaining about Android fans on an Android site is like complaining about Apple fans on an Apple site. If this was CNET or ZDNet, I'd full heartily agree but that's not the case. So, do us all a favour and quit crying over spilled milk.

    • http://halljake.com Jake Hall

      No, there's just a lot of us who understand and appreciate the advantages of Google's rollout strategy.

    • PiLoT .

      How is the update service bad?

    • Ray

      Really? Google are the worst at updating? That's a new one!

      They rollout their updates in stages, to catch any bugs/issues before deploying to everyone. It's better to have 1% of users affected, fix the issue and redeploy, rather then deploy to everyone and have 100% of users affected.

      Yes, you have to wait for a few days before you might get the updates but I'd rather wait and know it's safe to install without issue.

      A recent update to the Google+ app is a prime example of where staged rollouts are actually quite effective. The update was bad, they fixed the issue and reployed and for the most part, had it not been for Android Police and other media sites, I would never have known something was wrong.

    • Paul Taylor

      There are still Microsoft fanboys?

  • Kogure

    I wish Google said this earlier. I've wiped Google Services Framework many times in fear that my device is somehow not seeing the update.

  • whispy_snippet

    Great to read this.

  • Simon Belmont

    Wow. Such entitlement.

    Much anger. So stupid. See: http://i0.kym-cdn.com/photos/images/newsfeed/000/581/296/c09.jpg .

  • http://nexttopevent.com/ Keodangdnd

    growing technology, I love it

  • Terrence Godchaux

    While Dan Morrill's post was very well written and informative, perhaps it should have been provided by Google before the official release. As a 2012 Nexus 7 user, I also have not yet received the OTA. It's not about being overanxious, rather not being informed. This is a new experience, as I am an Apple convert also. A positive experience always begins with good communication.

  • John

    Update isn't a major step up anyway...even the N5 for that matter..skip a generation or 2 when buying tek...then you'll get the experience an update. (Just tapped my N7 fifty times too)

  • moelsen8

    eh, google should keep the current system but allow anyone who manually checks for an update a slot, if a slot in the current x% is still available.

    • Paul Taylor

      This. I suspect 99% of Android users don't even know that manual check button is even there, so it wouldn't get overloaded.

      • http://riteshtripathy.wordpress.com/ Ritesh

        That does make sense.

    • wolfkabal

      But then it does become a 'race' scenario, and not sure that's much better either.

      • moelsen8

        i would bet the vast majority of people have no idea about any updates happening until something pops up on their screen telling them. so the power users race to fill up the slots.. it's no different than the random picks filling up the slots. at some point in the early waves those people who are diehard about getting the update will have it and then random people will start getting it, having never known it was happening in the first place.

        actually, this is probably a better system as the people mashing the update button would probably be people who could better recognize bugs etc. it's probably a better sample pool for the rollout, in terms of making sure nothing breaks.

        • wolfkabal

          You're probably right, my initial thoughts were for managing the load on the distribution servers, but now realizing that's probably not an issue.

          Also, as for the 'recognize bugs etc.', sadly I don't think the number of qualified people for that is as high as you'd think/expect. I know a lot of android users who are enthusiasts, who must have the latest/greatest, yet don't have the knowledge, knowing, or capacity to properly recognize, diagnose, or report bugs. Sad but true. So in the end, the true dia-hard technical wizards of android would be the minority, of even the 'power-users'. And really those are the ones who are side-loading or using other means to obtain the updates anyways.

  • scuttlefield

    You know what I think would be neat to see...a program where you can voluntarily sign up to get updates earlier in the update process. I'm guessing that more of those folks would be power users so it would not only benefit users but alos Android because they'd get feedback from users with better knowledge of the OS.

    You might say that so many people would sign up for this that it would make it pointless, but I'd bet you'd get no more than 25%, which I still think would be a good way to identify knowledgeable users.

    • Roger Siegenthaler

      Or only ever let registered devs signup, because a lot of idiots would sign up otherwise and then complain

      • Andy Stetson

        Registered and ACTIVE devs, otherwise, anyone can sign up for a dev account... for $25 (or at least, that's what it was when I got mine).

        • Roger Siegenthaler

          You don't have to pay to get a dev account... you can be partner or whatever on a company one, that should also count imo. And not many people will spend $25 just to get updates earlier...

          • Andy Stetson

            Right, that would fall under Active devs, so long as the business is publishing apps/updates.

  • Sir_Brizz

    I hate the way Google does staged rollouts, but I do understand why they do them. It's impossible to compare to Apple because they announce the updates months in advance, and then it's available to ~1% (the developers) and they have months to work out the bugs before they do a general release.

    Google announced KitKat a couple weeks before the staged rollout started. And within 2 weeks of that it will be available for 100% of devices. In reality, that is MUCH faster than Apple.

    I do wish they would figure out how to get the most anxious people served first. adb sideload is only a barely passable solution. Worst case scenario, they could send the update to 1% before they announce the rollout, then announce the rollout for the next 25% or something.

    • Dr. Dave

      How on Earth is adb sideload a "barely passable" solution? Anybody who cares enough about getting an update OMG RIGHT NOW GUYZ is going to know how to use it (or spend 5 minutes Googling), and it makes you phone do the exact same thing an OTA would do. No unlockling or anything.

      • Sir_Brizz

        If Google were good about releasing the binaries at the time they announced the OTA, instead of days later relying on the community to find the download link instead, then maybe I would say that is true. Right now, you have to troll XDA to use adb sideload method unless you want to wait almost as long as everyone else anyway.

        • ????

          I'm not following, factory images were released, just about every tech site had step by step instructions on how to update and where to get the files needed...

          • Sir_Brizz

            Sideloading the factory images is far from easy. You need the OTA zip file to make it easy and even then it's way harder than it should be. And, even then, the factory images didn't come out until a day or two after they announced the availability.

  • Jsilvermist

    Meh I'm way way too impatient to ever wait for an OTA to sideload.

    I have the Google Nexus images page (https://developers.google.com/android/nexus/images) tracked in Page Monitor (https://chrome.google.com/webstore/detail/page-monitor/pemhgklkefakciniebenbfclihhmmfcd), and the second an update comes out, I just extract the system, boot (kernel), bootloader, and radio images, and fastboot flash them.
    Then boot TWRP, hit restart, install su binary, boot system and done.

  • http://nexttopevent.com/ Keodangdnd

    Can you please tell me WHERE you were promised that you'll get the update as soon as the new version of Android is announced?

  • James Jamison

    False! Here is the thing about this one. Once you receive the OTA update and the system installs the update it will wipe your dalvik cache. Thus the entire warning about not wiping the Google service framework or it will cause possible harm is total BS. Google just doesn't want there server overloaded.

    - XDA Recognized Developer Jamison904

    • Zack Whitfield

      Eh? The point is if you clear it and you don't get the download there are issues.

      • James Jamison

        There are people who have their phones set to wipe cache and/or dalvik on every boot. It will not hurt anything. Also the funny thing is when your phone starts acting up, wiping the cache/dalvik will fix the problem 90% of the time.

        • Zack Whitfield

          There are also a lot (probably majority) who don't do that, so his warning is valid.

          • James Jamison

            Again, no it is not. When you call tech support when your phone is acting up, this is like the 4th or 5th step in their script they read to help callers fix their phones. Are you just arguing to argue or do you know what any of this means?

          • Unrecognized Developer

            The stupid. It burns.

        • Paul Taylor

          This article has nothing to do with wiping cache or the dalvik cache. Return to GO, don't collect 200 dollars.

          • James Jamison

            Ah the trolls...smh. The point was wiping the Google service framework would not hurt the device and that wiping the cache and dalvik did exactly the same thing and even during the upgrade process it does exactly this. And yes the stupidity does burn...

          • Paul Taylor

            Still wrong. The article is about "clearing the framework data", and the problems this can cause. Nothing to do with wiping cache/dalvik, which will not cause problems. Why don't you just admit your "BS" remark was false?

          • James Jamison

            Re-read. You just agreed with my statement. You are also just arguing to argue.

          • Paul Taylor

            So you agree that calling "False!" was incorrect? It was you that brought dalvik etc. into the discussion in the first place, and erroneously. If we agree now then it must be that you've changed your position.

          • James Jamison

            No you troll. Your last statement agreed with my entire argument. Do you even know what davlick is? I am done with you. You probably have a bone stock nexus and afraid to root it because you think this could cause it to brick. Wiping the "framework" would be the exact same thing as wiping the cache and dalvik. This is obviously over your head so you keep double talking thinking you will catch me up.

          • Paul Taylor

            LOL you were done from the moment you first posted. The article says "clearing the framework data". If you think that's "the exact same thing as wiping the cache and dalvik" then they're obviously letting anyone become an XDA Recognized Developer these days lol.

          • Paul Taylor

            To summarize the article for you - as you seem to need it explained - Dan Morrill is stating that clearing the data for the Google Service Framework will cause a new ID to be allocated next time, causing potential issues. This is correct and true. You then piped up saying "False! ... BS" with the irrelevant remark that people clear dalvik and cache all the time without problems. In the process you made yourself look ignorant, as you appeared to equate dalvik/cache wiping with data wiping when in fact each can be performed entirely independently of the other.

          • James Jamison

            Sweetheart. You are still confused. I didn't not state the it was BS that it would not do this. I stated BS that it would possibly hurt something, it will not. Before jumping on people please read their entire comment. Now as for wiping the framework vs cache and dalvik. This will do the exact same thing. Last, nice personal attack. You still have no idea what you are talking about. I am done with you. I can tell by your post count here that you have nothing better to do than troll the comments.

          • Paul Taylor

            Sigh. :-) You said it was BS because people wipe dalvik/cache all the time. So you thought he was talking about that. They don't do the exact same thing - that's Android 101. Still, it was nice of you to try.

          • Paul Taylor

            "Google Engineer Dan Morrill ... Urges You To Never Clear Google Service Framework Data". You: "Now as for wiping the framework vs cache and dalvik. This will do the exact same thing." That's rubbish, basically. I can't state it any more plainly than that.

    • Tassadar

      This is just plain wrong. Dalvik-cache has nothing to do with app data.

      • Paul Taylor

        It can't be wrong. He's an XDA Recognized Developer. o_O

    • Fabi

      You are just making a fool of yourself, the article talks about clearing app data, not about cached odex files or the /cache partition. And proudly presenting your RD here doesn't help your case either...

  • greg

    so if i keep clearing my clearing my Google Service Framework i get another roll of the dice... :)

    • http://twitter.com/anishbhalerao Anish Bhalerao

      Yeah. Because new GCM, essentially a separate phone "for the servers".

      • greg

        w00t, 10x and i am now getting the update +1 good article!

      • mec

        i wonder if this jacks up the numbers that google sees as unique visitors to the play store...

    • Smithers_Jones

      No, it's your device ID (which is fixed), which determines this. Clearing the services framework only generates a new GCM ID, which isn't used in the batching selection process.

  • Matt

    I wonder if the GCM ID is related to why some apps restored from Titanium Backups, even after restoring previous Device ID, will not get new push notifications until you clear data for the app and sign-in from scratch...

  • Booyabobby

    So if the check button does nothing, why put it in?

    • Mkvarner

      They can't take away our most used button!

    • http://riteshtripathy.wordpress.com/ Ritesh

      It does something, but once a batch. Whoever said it does nothing?

  • Clear

    Yeah, fuck that. I'm going to keep clearing the Framework. It definitely works, and the only problem it causes me is that I have log in/out of my Play Store account to get that app to work properly.

  • Clear

    Why dont you just let people who want the early update, get it?

  • Funem

    I have had issues with clearing the framework data. I would advise you as well not to clear it. In one instance the device was not recognised by the Google servers as a valid device. I could purchase apps via the phone but it would not allow me to purchase though my web browser as the phone became invalid. This was definitely after clearing the framework data. This required a ticket being raised and Google engineers helping to fix the issue,

  • Logan Shaw

    It doesn't matter now, I've already done it. I'm gonna keep clearing it until i got the fucking update!

    • http://riteshtripathy.wordpress.com/ Ritesh

      Get the factory image and flash it except the userdata.img. Takes 5 mins! Jeeez....

  • http://mobipedia.in Hardeep Singh

    What about the times when your device mysteriously goes missing from the play store website? This happened to me recently and crippled my ability to comfortably push new apps to my tablet directly from the Play store website. The only solution I found was to clear data for Google Services Framework and Play Store and it worked.

  • Dissidence

    I've bookmarked this solely for the sake of linking it each and every time that some overly-entitled *expletive redacted* complains about not getting an update immediately after it's announced.

  • http://riteshtripathy.wordpress.com/ Ritesh

    Two things Google absolutely needs to add to Android:

    1 - A secure app+data backup solution that doesn't need root.
    2 - A password-protected option to flash factory images without wiping the slate clean or needing an unlocked bootloader to prevent a full wipe.

    • mjku

      1. This.
      2. That's what ADB sideloading is for. It's not the factory image, but it's the OTA image (which is usually available around the same time as the factory image, often sooner).

  • anti Google fan

    BS, do it every time you don't want to wait.
    Maybe it creates issues on Google side, but that's their problem. Let Google fix their own mess by themselves. There is no problem on the phone. Stop intimidating users.
    I'm not clearing the Google services this time because kitkat is a pile of .... that's not worth upgrading.
    Waited almost a year for changing the color of an icon from blue to white.... Gee... How much work and thought did you had to put on that Google???

    • Woody

      Google are a bunch of moronic puke geek-tards. It's no wonder their ecosystem is a fragmented disaster.

  • grimoald

    Did anybody receive the OTA for N4 yet?

    • Rom (us)

      Not yet!!!

    • http://www.markallen-online.co.uk/ Mark Allen

      I'm still waiting as well. :-(

  • bremberdee

    It's all about communication. If Google had announced during KitKat launch that updates would begin the last week of November, there wouldn't be such a fuss.

    • mjku

      Bull. People will whine either way.

    • mec

      well, they started earlier than that and stopped... there were security issues that needed to be corrected.

    • Guest

      So this staged roll out that has begun doesn't start until next week?

      • bremberdee

        It's Saturday and still no OTA...

  • Petr Minařík

    so, if clearing google framework data resets the id of device, you practically get new roll of dice, right? :))

    • natabbotts

      Nope, because they have already allocated randomly the devices that get it, so you have exactly the same chance as if you'd done nothing, in the next wave.

  • https://steamcommunity.com/id/m-p-3 m-p{3}

    Thanks for the PSA!

  • http://youtube.com/spelrutan Jens Törnblad

    I don't get it. Why don't they just put a checkbox under developer options witj something like "Ignore staged rollouts" or similar. So when the device checks in and looks for a new version it would skip the queue. And it should work for Play StoreStore as well. It would be such a small percentage that would use it, only power users. Normal users barely knows about new releases, and often they don't even care. This would make all the frustration stop and everyone would be happy.

    • mec

      or... permit users to sign up for GAPPS betas, in the same way we can sign up for nova launcher's beta. (for applications anyway. I'm sure they can also register device IDs for OS rollouts, too)

  • http://www.nexus5.com.es/ www.nexus5.com.es

    cool thanks!

  • Francois-Xavier Launois

    And this is how you end up having 10 devices linked to GPMAA subscription. Happened to me once, I guess factory resets on custom ROMs triggered the more-than-10-devices error. Had to go into the web interface to remove each cloned device one after the other. For Google, I owned half a dozen of S3s and Gtab 2s :)

  • Woody

    Google can go fuck themselves. Their update method blows.

  • johnforamerica

    You know what would be helpful to know? How do you FIX the issues he describes if you *were* stupid enough to clear the framework?

    • mec

      looks to be self correcting when the device pings the server, it just may be a couple of hours.

      • johnforamerica

        It wasn't for me. My device WOULDN'T show up on the web version of the play store and I also had issues with Android Device Manager via the web. Can't remember *what* I did to fix it, but I know it entailed more than "just wait" (which I did for a day or two before deciding to do more).

        Appreciate the reply!

  • jessnewcomb

    AT&T has you down to 1 check every 24hrs. on the HTC One anyway. If you check at 7 am it is 24 hrs to the second that you have to wait and it goes from the last check in. So if the following day you wait till 10pm and so forth. Not sure why. The only thing I am puzzled about is that a carrier branded Moto X is receiving the update before my Nexus 10. Not sure why and what the delay is.

  • yossarian

    OTA update installing right now :)

  • Nathan Fernandes

    Still waiting to get the update on the n7 WiFi model

  • sunny

    My nexus 7 did show up the OTA update, but it was stuck on "waiting for downloading". I did the google framework thing and now the OTA update is gone. Any solution this?

  • Syahrul

    So, if we have do "clear service framework data".. what is the solution and what is your suggestion to make things rite? help~

  • Venkatesh

    I have not received the update for nexus 4

  • Eams

    Like a douche I deleted the Google Framework Services - DON'T DO IT!!

    Sideloaded 4.4 onto my N4 and the Google Framework Servies problem is solved :)

    All apps now update without error :)

  • NoBigGovDuh

    Why not let advanced users volunteer as the update testers?

  • jloa

    If the check in is random, then there is chance u won't ever get the update :)

  • kimble89


    En effet je ne savais pas. Je suis tombé sur l'info ce matin et j'ai fait la manip vite fait.

    Non seulement je n'ai pas reçu la MAJ Lopllipop mais en plus depuis je n'ai plus aucune notification d'arrivé de mail , etc ...

    Donc surtout ne faite pas cette manip !!!

    Et comment peut on arranger ça ?

    J'ai lu qu'il fallait supprimer son compte et le réinstaller. Comment faire ?

    Merci de votre aide