**** V3 was removed, it had problems.
V4 includes built-in thermal disable - don't complain if your device fries - but it shouldn't...
The CPU is overclocked to 1.8 ghz, and the GPU to 544 mhz.
I started a new thread, because this kernel deviates from the past in some significant ways, and I want to be able to track any problems separately.
This boot image disable the proprietary 'mpdecision' process - which is used to govern the clock speeds and which CPUs are online.
Instead it uses an 'in-kernel' mpdecision based on the work done here but with some significant changes. It relies on the governor to control all cpu frequencies, and only enables/disables CPUs. It also looks at the current governor to know if it should bias toward performance or power savings, so...
The 'ondemand' is slightly towards power savings, and 'interactive' sightly more towards performance. 'performance' is maximum performance. 'power save' is maximum power savings (although very slow...).
Also, setting the governor on CPU0 will automatically set it for CPU1. So, you can now do a 'tasker' to switch the governor based on battery left, etc. and have it work as expected.
Some things to note, often AnTuTu will not detect the second CPU due to aggressive power savings. If so, you will see a maximum score around 14k. This is a bug in AnTuTu - other benchmarkers will work fine. Often it will detect the second CPU and you should see scores above 18k.
The V4 loki-fied boot image is available here.
I would suggest using 1.8 ghz, with the ondemand governor for excellent balance between performance and power savings.
V4 includes built-in thermal disable - don't complain if your device fries - but it shouldn't...
The CPU is overclocked to 1.8 ghz, and the GPU to 544 mhz.
I started a new thread, because this kernel deviates from the past in some significant ways, and I want to be able to track any problems separately.
This boot image disable the proprietary 'mpdecision' process - which is used to govern the clock speeds and which CPUs are online.
Instead it uses an 'in-kernel' mpdecision based on the work done here but with some significant changes. It relies on the governor to control all cpu frequencies, and only enables/disables CPUs. It also looks at the current governor to know if it should bias toward performance or power savings, so...
The 'ondemand' is slightly towards power savings, and 'interactive' sightly more towards performance. 'performance' is maximum performance. 'power save' is maximum power savings (although very slow...).
Also, setting the governor on CPU0 will automatically set it for CPU1. So, you can now do a 'tasker' to switch the governor based on battery left, etc. and have it work as expected.
Some things to note, often AnTuTu will not detect the second CPU due to aggressive power savings. If so, you will see a maximum score around 14k. This is a bug in AnTuTu - other benchmarkers will work fine. Often it will detect the second CPU and you should see scores above 18k.
The V4 loki-fied boot image is available here.
I would suggest using 1.8 ghz, with the ondemand governor for excellent balance between performance and power savings.