[Samsung Galaxy Nexus] sert00:
read here guys if you miss it

i don't know if it help,but here the logic of intellidemand

cpufreq/cpufreq_intellidemand: intellidemand cpufreq governor (version 3.1)

Intellidemand is inspired by ondemand governor. Its main features are:

- auto cpu hotplugging based on runnable thread average calculations

- detection of browsing mode (long screen on activities with moderate run

queue depth =< 38 )

- limit max frequencies when in browsing mode to conserve battery for long

duration tasks

Browsing State Determination:

1- Browsing state is enabled as power-on default. Browsing state is disabled

when run queue depth is > 38 for 2 consecutive samples

(very high instantaneous spikes)

Browsing State Limit Max Freq Logic (sliding window algorithm):

1- While Screen is ON > 3 min, and average load of the CPU is < 35%, then

CPU Max frequencies will remain power-on default

2- While Screen is On, if average CPU load > 35%, both CPUs max frequencies

will be limited to a lower user configurable max value

3- While Screen is On, After both CPUs' Max is limited to lowered max, when

the average CPU load has dropped down to less than < 25%, then both CPUs

Max freq will be restored to back to power-on default

Runnable Thread Auto-hotplug (fast hotplug / slow unplug algorithm):

1- When average number of running thread is < threshold, 2nd cpu will be

unplugged.

2- When > threshold, 2nd cpu will be hotplugged.

3- The logic applies a fast hotplug and slow unplug algorithm so 2nd core

will stay enabled longer to help deal with performance spikes

changes from Ver 3.0 -> Ver 3.1:

- add run queue persistence to better determine browsing state

changes from Ver 2.0 -> Ver 3.0:

- remove GPU Busy dependency for browsing state detection (this will make

the governor more portable to other platforms without specific GPU

architecture knowledge)

dependencies:

-- Qualcomm's run queue average logic (SOC independent logic)

-- TI's runnable thread average logic (SOC independent logic)

adapted for OMAP2 platform from faux

can you give OP a dmesg?strange fact is i tried tiny 2 days ago,and how i wrote in some 3ad i don't remeber i haven't got so good response,but it's only my experience

good debat..me too i now leave color multiplier quite down,because my prevoius gnex had strange problems at display certainly because of multipliers way too high..i don't speak of this kernel settings,but what i used for at least 11 months from novermber (always used to be a trinity\glados fun!)

not completely right..at kernel level a dev can change\tweak in which mode the system free up\release the ram,with the LMK(low memory killer).Here the dev can change also the aggressiveness of it.below (post under this)OP says which are the levels settings for AK,and at first look,they seems ok to not have major lags

Tip..if you experience similar problems with yours usage,you can try patching the service.jar and try supercharger script from zeppelinrox,you can choose many levels of LMK depending on yours choice(for example usefull if you have lags,often launcher redraws etc..)

holy sh!t Stefano...what governors you tweaked to create nightmare?i think you create it due to the fact there isn't any documentation related...waiting!:angel: