[AT&T Samsung Galaxy Note I717] pj_rage:
I'm seeing an interesting problem that I think might be related to the kernel, but I'm not certain. I'm using the 0.2 OC version, and I'm on the stock ROM.

I ran the 0.1 OC version for a few weeks without any problems at all. I was set at 1.836GHz max and 192MHz min, with the on demand governor. Again, no issues. Loved it.

I updated to the 0.2 version specifically to try to the smartassv2 governor as I had read about it and it sounded interesting. Same max/min settings, only changed the governor to smartassv2. Everything worked great for a week.

After using the smartassv2 for a while, I noticed with CPU spy that it was basically only either full max CPU 1.836GHz or deep sleep, and I thought this might affect battery, so I changed back to the on demand gov with the same settings that worked great with 0.1 (192 min, 1836 max). Note that I had not previously spent any time with the on demand governor on 0.2 -- when I first booted 0.2, I immediately had changed to smartassv2.

However, with those settings, the phone was continually having trouble waking up. Most times it was fine, but every so often, it would refuse to come back on. When the problem happens, it seems as if the phone is on and operating normally (calling it would ring it, holding power button gives the slight haptic buzz), but just would not power the screen on (or respond to touch on the blank screen) -- the screen would not turn on and the only way to recover was to hold the power button and reboot it.

Changing the min to 384MHz seemed to fix this issue, but it hasn't been long enough to say. Based on how often the phone was not waking up with 192MHz, it seems that the 384 has done the trick, but I'm very curious as to why it was fine for so long (on the 0.1 kernel) but now is having the trouble?

Another related/unrelated issue is that I also tried the lagfree governor that 0.2 brought, and even with a min set at 384MHz (I use system tuner to set these things per Da G's recommendation), cpu spy will show that it is spending time at 192MHz. And again, with the lagfree governor, even with a 384MHz min, the not waking up problem is occuring. I assume it is because of the time spent at 192MHz. Is this the way lagfree is supposed to behave (ignore the min setting), or is this a bug?

The short story is that it seems that with the 0.2 kernel, my phone is no longer able to operate reliably with a min of 192MHz, because it cannot reliably turn on the screen and properly wake up. I'm continuing to monitor it at 384MHz min to make sure it the problem does not also occur with this frequency, but so far it does seem to be OK at 384. I'm just curious why it was OK for so long on 0.1 at 192 min, or maybe it is completely unrelated to the kernel version and is something else (though I'm not sure what). I'm not sure what I might have done to cause this? It did start when I changed from the smartassv2 gov though, I'm sure it's correlated with that change, going from smartassv2 with a max/min of 1.836MHz/192MHz back to on demand with the same max/min.

I'm hoping that someone can confirm 2 things -- that the lagfree governor of 0.2 allows the cpu to go below the min setting, and whether or not this is normal behavior, and also if anyone is able to operate reliably with a min of 192MHz on the on demand governor, on 0.2 version, without having trouble waking the phone (you would need to try it over a period of time as it seems to happen randomly -- most times it will wake fine, but eventually it just won't wake).