[Motorola Droid RAZR] Ohmster:
I can help with that, Vanwho. I was reluctant to install ANY May NIGHTLIES of cm11 because ALL of them were crashing more than a demolition derby. When I get the issue, it will manifest itself with a wake to black screen, hard buttons lit, but screen remains dark. Very bad when a call comes in and you cannot see the phone screen to either accept the call or hang up when goes black again using headset or speaker. Only thing I could do was Force a Hard Power Down and reboot to get my desktop back.

I always implore, request beg, do anything I have to in order to get members to report on new builds, how done, any issues, list build date, and give details. MOST IMPORTANT, give followup report a day later with what is broken and how it is holding up. I think the members are now seeing just how important these build install detailed reports are and are now cooperating, especially the newbies.

Based on the glowing reports for 05/17, I installed it. Could not crash it for anything. But orange bars came and would never leave. Signal drops were frequent as I traveled. I updated every day to improve this "orange bar here to stay" issue and had no luck. Nothing but orange bars no matter how many times I updated.

NOTE:

I always update OTA from the Settings menu, About Phone screen. I like the one touch updates and they do work well. I got the orange bars somewhere, maybe an early May build or from the crash free April builds that I reverted to. The OTA updates do wipe dalvik and cache every time you perform this update.

But since the orange bars never got better, seemed worse or at least never lightened up, I suspected it may be some "crud" in my current build that would NOT be wiped with an OTA update. I rebooted to recovery, deleted android secure, and just to clean it up, cache and dalvik. android.secure it NOT wiped in an update, only when one goes clean. Rebooting showed orange signal bars again. Toggling airplane on and off cleared them up. No more orange bars! I took a ten mile drive, saw my signal strength rise and fall, but no orange. I am now on build 05/21 and every one up to now, 05/21 has been good. Once I found that wiping android.secure helps rid the system of previous APN, signal, and orange bar issues, I am happy. We still have some signal issues in the current build but they are not severe and crashes are a thing of the past. I do read the change log every time before I update to see if it contains bug features or a slew of new additions. Bug fixes are good, meaning a good build. Many new additional features is something to be wary of. If you must have a working phone 24/7, it is best to wait for someone to test and report before trying it.

MAKE IT SIMPLE:

If you like and use OTA updates as I do, clean the crud out of your phone by booting to recovery. Wipe dalvik, cache, and android.secure. Reboot to System. Toggle airplane mode on then off again. This will take out any leftover crud causing extreme orange bars from the system. May also help with APN and signal.

The current builds are stellar, Vanho. Go for it! If you OTA update and find issues with it, wipe cache, dalvik, and now android.secure to clear out old issues. Best of luck to you. Please report on your install, build date, method of update, how it went, and how it is working in a day or so if you can. Thanks Vanwho! :highfive:

Hint:

Updating your cm11 phone when on NIGHTLIES can be really risky business. When to update, how frequent, what if I get a bad build, can it make things worse or introduce new problems? To answer these questions, one can and should view the Change Log for the build. Yeah I see it Ohmster, but what does all that "stuff" mean?

I cannot go over item, one by one and explain it, heck, I dot not understand ½ of them myself, in detail. What to look for are bug fixes, these are good things. Things like this:

Bluetooth: Adds check to verify Bluetooth adapter state (android_frameworks_base)

Fix socket descriptor leak from Zygote to child app (android_frameworks_base)

AppOps: fix framework reboot issue when AppOps enabled (android_frameworks_base)

Fix descriptor leak after accepting connections (android_frameworks_base)

These items are for the most part, fixes and are considered safe. Things that add more, new, or many new features are new, sometimes experimental, and dicey to install on an important phone that must always work. Things that add new and untested or unproven features are not so safe the first time around. The Theme Engine activation feature caused so many bugs it took weeks to work them out.

CM11 Themes: Allow defining a custom default theme [1/3] (android_frameworks_base)

CM11 Themes: Allow defining a custom default theme [3/3] android_packages_apps_ThemeChooser)

CM11 Themes: Allow defining a custom default theme [2/3] (android_packages_providers_ThemesProvider)

Add CPU boosting hooks (android_frameworks_base)

Allow untrusted apps to execute binaries from their sandbox directories. (android_external_sepolicy)

Things like introduction of new features in the build, especially many of them at a time, can introduce issues into your build. Not all of them, but many. This is a good strategy for those that need a 24/7 working phone to avoid bad builds. Learn to use it, it will become clear as you do it, and you should have a good, working phone all the time. Learning how to read a changelog and understanding how it applies to you is a skill which you will develop each time you try it. And you will get better at it each time you try.

If you do install a new build, report on it in detail and do a followup post next day reporting how it is holding up, issues now apparent, and how you like it. *details please*!

This is how I do it and it should work for you and others. Now it becomes much clearer to all members why reporting is SO important to the group, members, and especially the devs that come to peek in and see just what irks us.

Glad to be of service, Vanwho. It is always a pleasure to help and old friend and I did miss you being gone like you were. Nice to have you back. :highfive: :D