[Motorola Droid RAZR] Ohmster:
Yep. Solid.

Hey rgerrans, what did you find out with your governor settings experiment? I use ondemand and like it, but man, this phone is slowing down worse than Jellybean did when the apps got very aggressive. Example, almost any task from making a phone call to using contact address for navigation, to finding and playing music on Play Music seems to take ...minutes. "Minutes"? To make a call or use navigation? That sounds *way* too long. Most of the time, I arrive at my destination before the navigation screen even comes up. You have any issues like that? ...or maybe I am just carrying too much baggage from constant OTA updates. :confused:

The Trickster module was pretty good with the JBX kernel, but mostly useless without it. With JBX and Trickster, you had mega governor and system tweaks. I really do not want to go through all that at every update so I am staying away from JBX. It is just this constant "phone app lag" that is irritating the doo doo out of me. Anyone else notice this? :rolleyes:

But overall, YES, the build is quite stable and good. For whatever reason, my phone is super sensitive to black screen issues and I have do put up with a bit of it, even in this build. Most likely others do not have this issue. I am in camp with chinkster and my2cents, we seem to have recurrent issues no matter what we do. :(

Feedback appreciated. :o

Furhter Research:

I went back to read the CPU Governors and I/O Schedulers tutorial again.

Just experimenting with the four governor types given in cm11's Performance menu, the only two that seem reasonable are ONDEMAND and INTERACTIVE. The other two just slam the phone at maximum CPU frequency which might be really good for performance, but would chew the battery a new butt hole. So what did I find out?

1. OnDemand Governor:

This governor has a hair trigger for boosting clockspeed to the maximum speed set by the user. If the CPU load placed by the user abates, the OnDemand governor will slowly step back down through the kernel's frequency steppings until it settles at the lowest possible frequency, or the user executes another task to demand a ramp.

OnDemand has excellent interface fluidity because of its high-frequency bias, but it can also have a relatively negative effect on battery life versus other governors. OnDemand is commonly chosen by smartphone manufacturers because it is well-tested, reliable, and virtually guarantees the smoothest possible performance for the phone. This is so because users are vastly more likely to ***** about performance than they are the few hours of extra battery life another governor could have granted them.

This final fact is important to know before you read about the Interactive governor: OnDemand scales its clockspeed in a work queue context. In other words, once the task that triggered the clockspeed ramp is finished, OnDemand will attempt to move the clockspeed back to minimum. If the user executes another task that triggers OnDemand's ramp, the clockspeed will bounce from minimum to maximum. This can happen especially frequently if the user is multi-tasking. This, too, has negative implications for battery life.

7. Interactive Governor:

Much like the OnDemand governor, the Interactive governor dynamically scales CPU clockspeed in response to the workload placed on the CPU by the user. This is where the similarities end. Interactive is significantly more responsive than OnDemand, because it's faster at scaling to maximum frequency.

I likw OnDemand, it does seem to give the best performance for the penny, but Interactive seems almost the same in the Performance menu as you can see in real time what the CPU speed is. Since Interactive is said to be more conservative with ramping up CPU speed, I will give it a try and see if it negatively impacts performance and if it improves my battery life. I think it will. These are simple experiments anyone can do so why not try it?

I did update to 08/13 and so far, it is better than 08/11. I thought 08/11 was the cat's pajamas, but it did give me overall very laggy performance and a few very annoying black screen incidents. Perhaps 08/13 will be better. So far, so good. No crashes or signs of instability or crashes. But, I have said this before. Safe to install and try out, only time will tell if it is a keeper. :D