[Motorola Droid RAZR] Ohmster:
Thank you Dwillian. The Max CPU Freq screen has always been adjustable, but the Min CPU Freq has always been grayed out, SFAIK. Just wanted to double check. Michael explained why the Minimum CPU Frequency button is grayed out on Drod Razr phones: "The min-frequency gets set by Motorola-specific blobs, that's why you can't change it in the menu. It's handled by the system. If I would enable it, the audio-driver couldn't set its minimum required frequency to operate correctly."

This particular thread we are in is a "developer thread" so deeper discussion into the workings of cm11 are encouraged and I will participate with what I have learned so far. We now have a general Q&A thread for end user questions so in here, we can go further and deeper into cm11 issues. :)

Actually, I did get the idle CPU frequency doubled on my device issue solved. It was not so much a problem, as to me wanting to know "why" has the idle CPU Freq doubled. And I did not know. I spent 2 days thinking about it, looking through the phone for answers, and trying to think "What did I do or change recently that could explain this"? I even used Trickster to set the Min CPU Freq and that did work, but I was uncomfortable with it, that was a "workaround", not a true fix. The entire point of why this is so important to me is that to have a good running cm11 phone, you have to be very familiar and intimate with the phone. You will "

get a feel for it

" so that you know, anytime you pick it up, what it is doing, if it is idle, if the CPU is busy, are any WiFi, Bluetooth, or GPS services are running, is the phone syncing, and everything about that phone, you have to know, when you finally get your phone running well and intend to keep it that way. I am in no way an expert at this, but I do understand the gist of it, finally, and am getting better at accomplishing it and having a phone that is fast and always ready. That is part II of the Guide I want to write and it is hard to put "Get a feel for the phone" into words. But I am working on it.

The double idle frequency I had help with. I do email stargo and a few days ago, stargo mentioned the debugging he put into the OK Google Detection. Enabling it could/would knock out your system audio and finding the cause of it is difficult. So Michael put debugging code into it and had it merged with the cm11 tree for the current builds So now if OK Google causes you to lose audio, logs that you take and hand in will contain meaningful information to the developer to debug this elusive issue. Michael easily, matter of factly, hit the nail right on the head about the double idle frequency. Here is a direct quote from Michael:

Please do not try to "fix" this, this is caused by either some audio-action (ok google everywhere?) running or just the system- settings polling the cpu-frequency and causing enough load for the governor to decide that 600MHz should be used. If you force it back to 300MHz, you will most likely get your black screens and a sluggish system back. One of the things is the audio-driver. So if you for example play some music or enable ok google everywhere, then you are locked at 600MHz min, as the system will not cope with the task and a lesser frequency.

He stated quite correctly that something in the system was causing the idle frequency to run at 600 because the system must run at least that high to accomplish things like "OK Google Detection" or any other services that you run which require a higher minimum CPU frequency. I did re-enable OK Google Detection a few days ago, and when I turned off Trickster my idle speed went back to 600 MHz. When I turned off OK Google Detection, my idle frequency dropped down to 300 MHz. My phone is idling right now at 300 MHz and if I enable OK Google Detection or any other things to rum, I can expect the minimum CPU frequency to raise enough to run these services smoothly at all times. :)

Michael also stated:

"If you install BetterBatteryStats (or another tool which provides you with a CPU history), you will see that the phone will most likely use 300MHz."

That is a really good tip. BetterBatteryStats can give a CPU history that is useful for tracking down what is running on the phone, to get a better feel for it, and to trim down things running which you are not aware of or actually need so they can be turned off, frozen, or uninstalled.

Michael, [MENTION=3457922]stargo[/MENTION] is an "amazing man" and hit that right away. He said that the audio driver would need to run at least 600 MHz to run and if I forced it back down with Trickster, about the problems I could likely enable by doing that. I got my answer. And I need that answer to get that intimate "Feel for the Device" I need to run cm11 efficiently and know at all times what it is doing. Guys like [MENTION=4977351]DumbleCore[/MENTION] have this "feel for the phone" thing down pat and he does not need system monitors to know what is going on. He is

very skilled

and experienced. For the time being, I use the CPUFreq in Statusbar Xposed Module to know better what is going on with the phone at all times. This is a very lightweight module that does not load the system down and it is not just the numbers I see, but how and when these numbers come up and change that let's me know what is going on.

The Guide that I wrote and updated is pretty good and will/can/should get you a good running cm11 phone. Part II of the guide, "Getting the Feel for your Phone" is yet a WIP (Work In Progress) and will allow you to keep it running well because

you always know what the phone is doing.

When you get good at this, the phone will do *nothing* without you knowing about it because YOU set the parameters of what runs, when it runs, and what never runs at all.

* This entire post is going into my "CM11 Guide - Installation and Maintenance" folder to help me remember this stuff when I polish up the Guide and publish the long anticipated part II.

** Man, I want this BetterBatteryStats tool, it is not free, and I don't have 3 bucks at the moment to get it. This would really help with getting that feel for the phone and tweaking out things causing more and unnecessary CPU usage. I need to install it and learn to use it. If I tell members to use this tool, I see 8 screenshot on the play store page. Most guys will look at all this information, have no idea of what to make of it, say "that's pretty cool", and not look at it again. I have to find out how to to work it and teach people this skill. It is on the to do list. ;)