When you go around flashing ROMs, you have to expect that things might occasionally go wrong. The previous milestone build of CyanogenMod 11 seemed fine at first, but then Google released the 4.4.3 update. Devices that were eligible (Nexus phones, for example) started producing update notifications, which shouldn't happen on a custom ROM. This was more troublesome than a notification that wouldn't go away, though.

Screenshot_2014_06_04_21_56_13 Screenshot_2014_06_04_22_07_16

Google apparently made a tweak to the packages in Google Mobile Services (GMS) that pull down updates from Mountain View's servers. Because the M6 build of CM11 didn't have those new packages disabled, the devices which would have been updated if they were on a stock build were asking to update. Of course, the update would fail, but that's not the main issue.

When users dismissed the update, the device still thought it was supposed to be updated. So, of course, it kept trying over and over... and over. Users on the CM forums report as much as 1GB of mobile data being eaten up by Play Services each day since the update started popping up. As of the M7 build, the new GMS components have been nuked and the problem should be gone (fixed in nightlies too). You just need to grab the update (the right update) to fix the issue. It's also worth noting that CM doesn't ship with Gapps installed – users are flashing them on top of the ROM, but at least the CM team recognizes pretty much everyone does.

[CyanogenMod Code Review, CM Forums (screens via maikl91)]

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.

  • MrJigolo

    -Google updates GMS so you can now pull the update
    -nexus 10 still on 4.4.2
    -fuck me

    • Paul_Werner

      Same here with the N7 2012 Wifi

    • sweenish

      "Google apparently made a tweak to the packages in Google Mobile Services
      (GMS) that pull down updates from Mountain View's servers."

      Reading comprehension helps.

    • David Cesarino

      Since you're reading this site, you probably know. But for others, it's always nice to remember that you can easily install the factory image.

  • Chris

    For once I feel lucky the android update isn't available for me yet.

    • Jonathan Czitkovics

      Haha nice!

  • http://dabuxian.com/ Dabu

    Another reason to stay with stock.

    • AOSPrevails

      After I converted to Stock+GravityBox, I haven't had a single reason to consider custom rom.

      • Chris

        I bought a Nexus to flash ROM's... then discovered Gravity Box.

        Mind. Blown.

        • Calipsort

          Same here! Stock+Xposed +GravitBox.

      • grumpyfuzz

        Maybe for security? An xposed module has access to EVERY permission on your device. Download a bad one, you're probably screwed.

        • Mike Reid

          Same w/ root apps, anything with a root exploit, and anything flashed from recovery.

          Don't think I've ever heard of an evil root app or recovery ZIP in the wild.

    • shonangreg

      As long as we're trying to avoid all risks, two cans and a string is even safer. No monthly payments and all you can eat ;-) Hell, even then you might cut your finger. Better you just stay in your cave, Dabu, and not come out into the dangerous sunshine. Who knows what might happen?

      • jump

        A bit touchy, aren't we, shonan? Is senpai's attention that desirable?

      • http://dabuxian.com/ Dabu

        I already went out of the cave by getting an Android device, 98% of mobile malware here I come!

  • http://petercast.net Peterson Silva

    M6 was reeeeally fucked up. M7 is good this far =)

  • http://ignaciozippy.com/ Ignacio Zippy

    All the weird things will happen to me when messing around with ROMS... but not this one. Good :D

  • blahblahblah

    "Buy a Nexus they said."

  • Ruben Moreno Jr

    Stupid crap ate up almost 3GB, never gonna use this mod again

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

      Pretty sure this bug would have affected most ROMs because of the way blocking of update checking is done. If another ROM isn't based on CM, and it's actually done things differently as far as blocking goes, hats off to them.

      • Vitaly Streltsov

        Once I had this on previous CM and have been charged for almost 4x monthly payments. Since then I'm on AOSP. BIG shame on CM this time.

        • moelsen8

          yeah this has happened before.. it got me at some point last year on my N4 - I was up by about 2 gigs before I noticed it. i don't know if you can blame CM here, but it sucks.

          • Vitaly Streltsov

            Btw my costs were much higher: my gf had N4 with the same CM ROM. And because that custom-flash was initiated by me, I had to pay bills. =)
            Sorry for my Eng.

        • samoanbiscuit

          Maybe, just maybe, you shouldn't be downloading unstable software if you aren't prepared to deal with major bugs?

          • Vitaly Streltsov

            thank you, but major bugs for me are: FC of important apps, exposed private data and crazy battery drain.
            Before that i thought this list includes 3 items only. =)
            P.S. my CM experience: CM6-CM11 . I used to be very loyal and dedicated, even on samsung-blobs trouble for my SGS2

    • matt

      For real though it used 3gb OVER my 3gb and I'm on purity

  • Brian Menius

    I LOL'd.

  • Jk Jeeks

    No wonder I didn't receive the OTA. All the slots are taken up by custom roms!

  • supremekizzle

    Xposed on AOSP FTW!!!!

  • Adam

    This is why you only deal with stable releases. Not nightlies, snapshots, milestones, or even experimental. Only if you are a dev really. d2vzw aka d2lte.

    • Carl

      Actually I read that M build is replacing the stable build so this was suppose to be the stable release. This issues has nothing at all to do the the rom and everything to do with Google making a change. If anything, the cm team did great to make needed changes so quickly

      • Adam

        Then why not put them under stable release section?

        • bozzykid

          CM no longer labels builds "stable". Only "M" builds going forward. Although IMHO, the builds have went down in quality lately.

        • Jurk

          Because CM's philosophy is one of continuous progress meaning there will never be a "stable" CM. Then again, given any software anywhere from any developer, is there ever really a "stable" version of anything?

    • noahstewart

      My wife and I were both running the stable mako release. Now, in order to "fix" this, I have to install a snapshot.

  • http://mekakiwi.blogspot.com.br/ ED-Z が あらわれた!

    Someone really update via data connection?

  • Joel Sacco

    Pretty sure this happened to me with the 4.4.2 update as well on CM.

    • Vitaly Streltsov

      Yep. Since then i'm on AOSP..

  • Pdiddy187

    CM has been dead for awhile now.

  • Richard

    It isn't really the fault of cm devs. You'd face the exact same problem even if you compiled aosp and added Google apps to them.

  • Lalu

    That... Didn't happen to me :-??. And I flash nightlies on a daily basis.

    • http://petercast.net Peterson Silva

      "I flash nightlies on a daily basis."

      This was such a poetic sentence :)

  • http://www.geordienorman.com/ George Byers

    Queue comments of people bitching about something which is free...

  • Cuvis

    I haven't had this behavior on my N4, but I'm glad for my T-Mobile unlimited data regardless.

  • Nifs

    Oh I can feel people's pain in this situation. I had the same problem back with some custom rom back on 4.2 when the stock 4.3 was rolling out. Luckily I usually disable my data when not in use, but it managed to drain about 400MB until my carrier warned me.

    Didn't bother trying to get it removed from my bill. I screwed up by using a nightly build, thus it's in reality my fault as well. Not the carrier by any means.

    Sad to see CyanogenMod of all the devs out there have such a fatal bug. That highly unusual, especially in a milestone build.

  • DaveNull

    This article is misleading and plain wrong. It's clearly an issue with Google apps that are not part of CyanogenMod.

  • Fellwalker

    It happened to me on a nexus 4 in a previous stable version of cyanogenmod. You'd think they'd have learned.

  • matt

    Wooooooow FML 3gb over....

  • wtf

    Any clue, when the needed CM-Update will ship via OTA update?

  • noahstewart

    What the eff? A terrible oversight.

  • Heldring

    This shit has cost me over €100,- on the phone bill...

  • Greg

    I used 2 gb of data because of this..eeks.