[Motorola Droid RAZR] Ohmster:
Oh I saw this earlier and wanted to answer then dinner and I lost your post. Self rebooting I have seen sometimes. And confusion on calculations of disk or apps space. For me, plugging in a USB cable to PC gave me problems. When you have to tap the pull down to release the cards for Explorer mounting, the circle would spin forever, but never release to Windows. Reboots. Happens sometimes. How did I get rid of that problem? OTA to a new build. ;) These are nightlies. Roll the dice but do not always come up with a winner, unless, you study the odds.

For 06/13, I did just what you did. Manual update, wipe the permissible caches, overwritten pa-gapps with new ones. ...didn't help. I would love to say it made things worse but I don't think so. 13 was just "a bad build". The cmupdater failing to notify lack of card space, then downloading not one, but two of the same updates in notification, "forever". Spooked me to perform an update to 14 and error still there, 2 cm11-06/14s downloading "forver". Hughes brought me out of my panic cycle by reminding me could be cards space, wipe updater data. (I already tried stopping the service, didn't help.) and he's right. Delete data stopped the "forever downloads". I didn't check card space and got stuck in the same loop. Others admit they got bit too on this updater error. So, cleaned space and updater works again. But I had enough of 06/13 and all the manual stuff I did. I reverted to 06/07 (A good build.) and then took 14. Better but signal issues and orange. OTA to 16, better but worse orange and signal, OTA to 17 and now, so far, nice. I reported cmupdater failing to notify card space deficiency and then going into a "forever loop" so this issue will be addressed. Imagine a user with a limited data plan, seeing these download arrows all day, they are going to freak and shut down the phone before they get killed "by passing their data limit", or so it appears.

OTA is NOT a dirty flash. It is how cm11 is meant to be updated. Not at first of course, we needed patches, camera apk files, duct tape and bailing wire to get it up and running in those days. But once we got a solid core, I did have to go clean to rid the system of patches and JBX. Ever since, OTA. There are good builds and there are bad builds. If you want to keep ahead of bad builds, then request and wait for build reports. People install and report all the time. I always bug reporters for more details, and praise them when they oblige. Reward good reports with one of your "Thanks Cookies", else they go unused and to encourage more, accurate reports. That's how I know what builds to install and what builds to avoid. When 13 came I was sure it would be a crap shoot, but we have waited a long time for a build, I have good backups, so I would "be brave", install, and report. It was "not so good", the phone chugged so bad it was like blowing a piston in a V8 engine and having to limp home on it. Had 06/14 not came along so quickly, I would have bailed on it but improvements came with 14, 16, and 17. All getting better, all OTA. Nightlies are cyclic, they get good, no black screens for over a month. Then we cut loose on the Theme Engine Activity and "they're back". Other dramatic improvements often bring back a symptom, same symptom, different cause for it. Same thing for signal, APN, and orange icons. They go away and then come back.

We have only so many ways for the phone to display problems and we have been through most all of them and they cycle around and around as the builds change.

Black Screen

Freeze or lock ups

Orange icons (Google services and updates fail)

Little or no signal

APN issues

Rebooting

GPS Fail (Been a while)

WiFi Fail or toggle (Been a while)

WiFi AP Fail (Been a while)

Camera Issues, still cannot safely Pause and Un-Pause video

UI FCs in all sorts of places

Battery Drain

MMS or Picture MMS failure, often APN related

Build that just will not work, period (Very rare)

Updater or server download problems or corrupt files (Not a phone issue)

That's off the top of my head. Anything I missed? Seen them all come and go, and come back again. And they do NOT hit the population evenly. 2¢ and chinkster get APN issues. I get orange bars and black screen lockups. Jake "never has a problem". (He does, but he has the time to virtually "sterilize the phone" and rebuild it from scratch, often. God do we need him.) It is never consistent, maybe the provider plays a role in how the phone reacts. I don't know. Same make and model phone, different providers and locations, same builds. What to think of that?

You want to keep this simple? Just remember these are nightlies. There will be good ones, bad ones, and intermediate ones. Pay attention to build reports and stay ahead of the game. :D

That is what I think is "causing this" and I have been here a long time. Sometimes I panic and someone kind here will pull me out of it. This is a good place. We got good people here and some nice treats for our phones. :highfive: