Yep and they run like a charm

Originally Posted by robt772000

Yep and they run like a charm

the clock trick is enough, actually even better then the kernel and cm9 tip

I only suggested Franco's kernel and cm9 for those who can't b bothered settings pre gameplay

Originally Posted by hamdir

the clock trick is enough, actually even better then the kernel and cm9 tip

I only suggested Franco's kernel and cm9 for those who can't b bothered settings pre gameplay

Mass effect: Infiltrator runs in Quad mode with Franco's kernel, it's ultra smooth

Originally Posted by Nubzori

Mass effect: Infiltrator runs in Quad mode with Franco's kernel, it's ultra smooth

I can't get mass effect. Must be my location.

how did you get infiltrator? I tried to buy it but it says that its incompatible with my device.

Originally Posted by hamdir

T

- to kill the last possibility of a random OS caused stutter, use supercharger script and set the mem frees to 512HP Super UL values

I found 1000HP more responsive. Also Nitro Lag Nullifier script, and few Build.prop I found from TP Forum.

ro.kernel.checkjni=0
ro.kernel.android.checkjni=0
com.qc.hardware=true
windowsmgr.max_events_per_sec=300
debug.performance.tuning=1
persist.sys.composition.type=gpu
dalvik.vm.execution-mode=int:jit

Originally Posted by ShyamSasi

I found 1000HP more responsive. Also Nitro Lag Nullifier script, and few Build.prop I found from TP Forum.

ro.kernel.checkjni=0
ro.kernel.android.checkjni=0
com.qc.hardware=true
windowsmgr.max_events_per_sec=300
debug.performance.tuning=1
persist.sys.composition.type=gpu
dalvik.vm.execution-mode=int:jit

I wouldn't go with nitro, I tried kernelizer n disabled 2 cores lol n nitro I would expect it to cause issues

of course 1000hp is better that's very aggressive and no multi tasking, ill try ur build.prop values but some of them r needless like jit

Originally Posted by Drefsab

how did you get infiltrator? I tried to buy it but it says that its incompatible with my device.

Weird, works fine for me, although crashes on certain cutscenes

Alright i have an update for you guys

first of all my method in the OP of the minimum clock locking will heat up the device

i found better ways

i've been testing my device non stop for the past days and i can confirm the following

multitasking and background apps are a definite contributor to heat, battery consumption and lag in games

I just ran S4e2 for one hour of gaming, stock kernel, on just the interactive governor without touching the clocks, it ran the smoothest yet without any stutter, and the temperature never crossed 43c battery and 72c CPU

updated the OP with my new tips