[Motorola Droid RAZR] Ohmster:
Dwillian, your answer and update

[MENTION=5362796]Dwillian[/MENTION] [MENTION=1472623]d.casper.b[/MENTION] [MENTION=3668995]Meneldur[/MENTION] read this, it is good stuff to know and help you get your phones on track. Things to look out for.

[MENTION=5362796]Dwillian[/MENTION] I did not see the first part of your question. Yes, I have all 5 of the frequencies listed in your screenshot, including 300 MHz. Thank you and good looking out. That is not so much the issue though, I could not scale all the way back down to 300 MHz at idle like before. But I answered this already. It was turning on OK Google Detection that forced the CPU/Min frequency to rise to 600, although it does not show anywhere. Stargo not only knows this, he writes our code and is "the one responsible" for graying out the Minimum CPU button. Because of our binary audio blobs, in order to use the audio drivers, it requires a minimum CPU Frequency of 600 MHZ to run them. For OK Google Detection, the audio drivers not only have to run all the time, they must be sensitive enough to hear the "OK Google" at any time of day, even through lockscreen if enabled, through all the background noise. It makes sense and once I turned of OK Google Detection, my idle dropped back down to 300 MHz.

Oh, those 5 listed frequencies you showed me are the steps the CPU takes on the way up and on the way down. You never see the Razr at 539 MHz because it does rise and fall through those 5 steps. These steps are set in the following files and you can read them in any file manager as text:

/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies

/sys/devices/system/cpu/cpu1/cpufreq/scaling_available_frequencies

Oh, you are the one I was looking for with the latest update and my two last updates tanked. When I was in the middle of this CPU Freq thing, I used Trickster to set CPU min to 300 MHz and it "worked". But [MENTION=3457922]stargo[/MENTION] warned me later not to do that, "please"! He said that by forcing the idle frequency down when the audio drivers are pushing them up would result in return of black screens, reboots, whatever issues I had would/could return because now the phone would be unstable. Of course he was right again. 'member I was saying I tried to update twice during that time? To 11/05 and again to 11/06. The 05 update did not even get off the ground and I immediately restored a backup to get out of it. 06 seemed to install well, but 7 hours later it was crashing, black screening, and all the things that Michael predicted. And I noticed one more unusual thing during the updates... (Check this out.)

You know after an update or anytime the Dalvik cache is wiped, you get that "Updating 52/197 Apps" that keeps counting until it reaches the total number? My number of apps really is 197, but these two quirky updates got my app count total, Dead Wrong! I remember seeing that my app count total was under 100 like 58 at one time, and the other was also below 100, but the apps were really there. Android

never

gets an app count wrong, it is a freaking computer for gosh sakes! But for the two bad updates and it was not bad roms, the app count was off by a mile. And the updates failed.

Now, I have the CPU Freq straightened out and am not using Trickster to force the CPU min frequency down, or are using it for anything at all but the information page (I disabled all tweak turn on and set on boot options.), and my CPU frequency is right, the 11/07 update installed like a charm. I did shut off OK Google but could have left it on and left my idle CPU frequency alone. CM11 Nightly Build 11/07 is running sweet, smooth, fast, idles quickly, and so far, so very good. After a full day and night, I will post a build report on it.

I "broke my own rule" by using system tweaks to "fix a broken system" but was aware of it and did it for testing. I would not have left it that way. That is also what [MENTION=3668995]Meneldur[/MENTION] was doing too and I asked him to please not use system tweaks to fix a broken system and he did get rid of all his tools for that.

I thought you should know because you say you have some lags and battery issues. I finally have just about every "little" issue with the phone clear now and it really does run like new. Now you know something else to watch for, the app count after a Dalvik wipe or update install. You still have something "a little bit wrong" with your system because you have the lag and battery issue. I sent you the BetterBatteryStats to help narrow it down. But let me know how it is going, it sounds like you are getting close and I think we can get you 3 guys up to finally having "Good CM11 Phones". Take care, bra. :)