[Motorola Droid RAZR] Ohmster:
Okay, I did some testing with [MENTION=4414937]kennethso168[/MENTION] the author of Advanced Power Menu, APM and the new APM+. Although the built in "Reboot to Recovery" in CM11, build 01/26 does not work, I was able to get the APM+ Xposed Module to work quite well for rebooting. I have been using APM for over 6 months. It only modifies the Power Menu and does not actively run on the phone or slow it down.

In the APM+ apk & module:

The Reboot menu works great.

The Soft Reboot is immediate and terrific!

The Reboot to Recovery does not work at all, takes a long time and finally shuts the phone off.

The Reboot to Bootloader on a Razr takes you straight to Safe Strap and does it rather fast. So for me, that is my "Boot to Recovery" option. The entire thing is customizable and so you can add/remove/customize/theme the entire power menu!

Something recently broke in CM11 to make this "Reboot to Recovery" almost impossible. Mr. Chen says he got his working properly on his XT910 but he is using the 02/02 build and that build is not even on the servers anymore after 5 days. I personally do not like it because it "simply does not install easily and just plain work" without additional fuss. Now 01/26 installed w/out a hitch, did not need so much as a single reboot to keep it working, and that is what I call a good rom. Less than perfect but still "usable" roms are also "good roms", but why settle for less if you don't have to? :silly:

Advanced Power Menu+ (APM+)

This is a totally awesome Power Menu changer and you will get back your boot to recovery if you use the boot to bootloader instead. For those of you using APM like [MENTION=838017]sherri[/MENTION], uninstall it, install APM+, and you got your boot to recovery menu back! :D

EDIT:

Now I am saying that "I could not get the Reboot to Recovery" to work in CM11, 01/26. That does not mean "it can't be done". Maybe some of you managed to get it working. If I am developing or debugging something, I need all the patience in the world. But when I test a rom, I do it as a typical end use would (That is why I use OTA updates" and I taper down my patience to match that of a typical end user. Meaning, if I constantly have to hassle with this rom in order to run it, then to me, it is a bad build, bad rom. :(

What would I tell my friend if I were giving it a review? "Oh it's a great rom man. Sometimes you have to tap and wait, but eventually, most of the apps open and work. Sometimes you get horrible lag, but if you reboot it, then it works good again for a while. I cannot get so and so to work but hey, it's a great rom!" ...uh, I doubt anyone would be interested in any rom with a review like that. So I test it as if I were a new rommer and simply wanted a good, reliable, dependable rom, easy to use, easy to customize, and everything works. And that is how CyanogenMod wants and expects it to work when finished.

Experienced rommers and hobbyists are different creatures. The more time they spend tweaking, adding, modifying, and playing with the rom is fun to them. But for end users, the less hassle it is, the better.

True, I did write a Guide on how to improve performance and maintain the rom, but it is mostly a one shot deal. Get it done sort of thing and then, enjoy it. :)