[Motorola Droid RAZR] Ohmster:
You are very welcome. :o

You know, it is kind of a funny story for me. I use a small CPU Frequency Xposed Module, CPUFreq in Statusbar, that shows the current speed of the Razr's CPU. Our phones step through 5 different frequencies when it runs. From 1,200MHz full blast, to 300MHz when it is idling, sleeping, and essentially "doing nothing", just waiting for you to give it a command. I love to see that little Green "300M" in the status bar, it shows my phone is resting, saving battery, and is ready to jump for me and do anything I want. Nice.

But I was playing around with "OK Google Detection", trying to use the phone "hands free" in the car. It did not work very well at all and I forgot about it. Then I noticed I never got the nice green 300M in the statusbar anymore, the lowest my CPU would go was 600MHz. I tried to "fix it" with Trickser and other apps and modules and complained about it in this thread. Stargo saw my comment and replied to "Please do not try and fix this" and explained that when "OK Google Detection" is enabled, the CPU is forced to not go any lower than 600MHz in order to "listen for and hear" "the OK Google" words being spoken near the phone. Stargo intentionally grayed out the option in "/Settings/Performance/Processor/Minimum CPU Frequency" to prevent anyone with a Razr phone from making the CPU go lower than what is required by the system for that reason. I went and disabled my "OK Google Detection" and right away, my CPU dropped back to the happy 300MHz purr when it was "doing nothing" again, saving battery and ready to perform. BTW, if you disable OK Google Detection and tap the little microphone in the Google Search Bar, it will still listen to you talk and find what you want by voice only.

I was actually trying very hard to "fix something that was not broken" and it is a good thing that Stargo stepped in to stop me from doing that or else I could make my phone unstable and crash it. And, I learned why minimum CPU frequency is not available in the Settings menu. Stargo is a very dedicated developer and a very decent human being. He really does stop in to help us in here when he can. He is the OMAP4 (Droid Razr group) developer and he is the one who does the cm code work for our devices.

Oh, the actual REASON why turning on OK Google Detection stops system sounds randomly is because not all of the Motorola Droid Razr source code is available to the CyanogenMod developers or to anyone. Motorola keeps it's hardware audio drivers and other code proprietary so no one else can use it, so the CM developers have to work around this issue by using some of the old, binary files in the CM rom build when making a rom for us. This causes problems like Google Detection tying up the audio drivers so that they will and do fail when OK Google is turned on and system sounds stop. To get the sound back, you can try calling the phone and forcing it to ring, or just reboot it. Turn of Google Detection and this issue goes away. If Motorola released all the source code for the Droid phones, we would not have this issue and the rom code could be efficiently written to avoid issues like this.

I think it is really cool when I not only get to "Fix something" like this, but learn neat stuff while I am at it. Hope you like to learn stuff too. That is the fun part about working on your own phone! :D