[Motorola Droid RAZR] Ohmster:
I don't think snapshot 6 is but I never use snapshots anymore. We got 4.4.3 in early June so it is likely not in the snapshot. Snapshot builds are NOT the newest, most updated, or "better" than the current nightly builds. They are simply a build in the nightly releases that is "frozen" as a Snapshot Build and only on snapshot builds can you file an official bug report to CyanogenMod. Which really does not do any good, since our developers had in most cases, have already addressed. ANY snapshot you install will be older and lack development found in the new nightlies.

If you want good stuff, shiny and new, stick with the nightlies. If you want to be sure you get a "good" nightly and not something with new problems in it, pay attention to anyone who does a "build report", a post where a member installs a new nightly and reports on any issues or benefits he found in it. Build Reports are valuable for this very reason, anyone can do a build report, the groups is heavily encouraged to do build reports, and you get the information you need in them. So if you want a good Android cm11, look for install or build reports, find one on a recent build, then flash that build. Good luck! :good:

---------- Post added at 12:40 PM ---------- Previous post was at 12:35 PM ----------

Well 06/13 is an abomination, I quickly took 06/14 to get out of it. 06/13 gave me so many signal issues, Google cannot update, voice typing not working, Google search page says no internet, low signal bars, constant orange icons. I figured it would be a handful as there were so many things put into one build that a simple bug report to fix something is not even a possibility anymore. 06/14 better, and you are right, there IS an 06/16. I am on it, like NOW. This will help clean up many of the little annoying issues brought to the table in 06/13.

Thank you for the heads up! :highfive:

---------- Post added at 12:50 PM ---------- Previous post was at 12:40 PM ----------

Is my cumupdater broken?

Hey!

I update with OTA all the time and really like it. But for 06/13, I did a manual install with pa-gapps, thinking it might help. Every since, when I tap an OTA update, the download progress bar stop and it looks dead. So I tap to download again. Same thing, it stops and no more downloading. But I can see in notification bar 2 downloads now, of the same thing. CM11 06/16, which I want, which are never going to come, and cmupdater will run forever and even survive a flash update! Only App Info, Clear Data makes it stop.

But now my OTA update is broken. :crying:

The only thing I can think to do is to restore my very good backup of 06/07 and then update to 06/16. Something has to be really broke because I did an update to 06/14, new system, and yet these nit-picky bugs just are not going away. :(

* The restore to 06/07 did not work. The Download Manager/cmupdater is really broken!

Is anybody else having this problem or only me? :confused:

This really bites, my Advance Power Menu Xposed module is not making the rainbow colors anymore, so any answer is a good answer. How about you guys, any issues with 06/13 AND/OR cmupdater? Thnx.

UPDATE:

Found it! Not enough room on SDCard. This is exactly what Hughes was saying. Of course that is a perfectly good reason for the OTA download to fail and queue it for download until space clears up. BUT, there is NO clear indication of this when it happens. I get excited easily and this one set off triggers on me. I grabbed the file on PC and used AirDroid to copy it over. Normally I copy to EXTSDCard and would have never found it. But this time I wanted to pop it right in the /sdcard/cmupdater/ directly so it would show up as OTA downloaded and ready to install. THAT is where I got the out of space notice and transfer failure. There needs to be published into the build an "Out of card space" message when OTA fails like that. Regular folks might never figure that out on their own. I know this and Hughes reminded me of it, but in the excitement of the moment, I forgot about space. Really bad notification on that failure. :D