[Captivate Android Development] Jsmokey:
Mine is actually at 75 the factory setting was somewhere around 80-95 I can't remember and as far as yours I know it was 65 in an older version cause I mentioned for you to up it a little around 70-75 to save on battery cause your settings for sampling rate scan often enough to catch the cpu usage right away so you don't get a delay really when the cpu needs to scale up.

If you are still using my kernel ddoubt just add the following to lmk_vm tweaks or one of the others I just say that one since it contains most cpu/kernel scheduler settings. Just replace 50 with whatever you want but I'm not too sure this is really the problem you're having seems more like a sleep state issue. I personally use go locker and have no unlock lag although I would occasionally get a little here and there when ram usage was high with the original lock screen.

echo "50" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold

Ok I went back through adrenaline shot just to see if I was remembering correctly the settings and I really believe if you are still using it with mine or kyuta's kernel this is most likely the issue. It would overwrite a lot of settings and the ones it wouldn't would definitely not agree well with his values when tweaking settings my kernel, kyuta's, adrenaline shot, supercharger, basically anything that will mess with kernel scheduler or cpu scheduler they really need tweaked as a whole and not added over other ones. Its the same way in the linux kernel on a pc if you tweak one or two things you're going to see certain things improve but others will suffer because of it. There really are a lot of guidelines to follow when changing these things.

A few things like shm(shared memory) and small things like that can be tweaked separately without any real side effects along with vfs_cache_pressure and swappiness because they have no major impact on the kernel settings they have more to do with mem management than anything, but major kernel tweaks need to be done as a whole reason being as in the case of sched_granularity and wakeup_granularity there are formulas to find correct values that work well together which while his would be optimal on a higher powered device on our lower power captivates its too high and would cause some lags here and there.

Also the latency is set too high even for some older pc's in adrenaline shot and we're talking something with around a 2.7ghz single core this would be a little high for. Just about any guide or man page you're going to find is going to say try lowering this value only high powered desktops can really benefit from upping it and if I remember the stock setting correctly he went way up. Not knocking his work, its really good with some kernels but when you are trying to add it to a highly modified one things don't usually come out so well. Also adrenaline shot uses NO_GENTLE_FAIR_SLEEPERS which I found was terrible with the new kernel leaks I tried it with mine and lost over 400 points in cf bench and scores went down pretty much across the board along with efficiency.

I'm not saying by any means I am the end all be all of the kernel tweaking world but a lot of his values just don't seem right for our cappy's when applying the formulas for finding optimal settings. Really I don't know if you are even still using these tweaks but I know you mentioned it to me and I meant to say something then but never got around to it.

Sorry for taking up so much page space in your thread kyuta I'll stop playing teacher now I just thought now would be as good a time as any to really explain the effects mixing and matching settings can have and explain a little about what each really is/does.