Binary patched kernels for Pipo models

[levicius]

Re: Binary patched kernels for Pipo models

i have a not big experience in overclocking, so i want ask: what are minimum/recommeded step for freq and voltage (now I make all tests with 12 for freq and 25 for voltage)

thanks

Never mind all bout the request I di before , I managed to work a way around and my device is ok now.

Enviado de meu SM-N9005 usando Tapatalk

[levicius]

Everything ok now !

Everything you did is right.

It seems strange that the app crashes on 3D test...Because I didn't modify the GPU part of the kernel
you can try reinstalling Antutu.
Are you sure that with stock kernel everything works fine with antutu?

Its everything ok now , Giouncino helped me out and I am able to run the claro kernel with no issues . Thanks !!!!

[giouncino]

i have a not big experience in overclocking, so i want ask: what are minimum/recommeded step for freq and voltage (now I make all tests with 12 for freq and 25 for voltage)

thanks

the minimum step for voltages is 25mV

For frequency the step is 12Mhz (limitation by the local oscillator) BUT pay attention, because the frequecies that Android will use are written in a kernel compiled file called cpufreq.c .

In details are the following (they are written in many parts of this file):

{.frequency = 312 * 1000, .index = 10}
{.frequency = 504 * 1000, .index = 20},
{.frequency = 816 * 1000, .index = 30},
{.frequency = 1008 * 1000, .index = 40},
{.frequency = 1200 * 1000, .index = 50},
{.frequency = 1416 * 1000, .index = 60},
{.frequency = 1608 * 1000, .index = 70},
{.frequency = 1704 * 1000, .index = 80},
{.frequency = 1800 * 1000, .index = 90},
{.frequency = 1920 * 1000, .index = 100}

(don't care about the "index"),
Then if you set a freq of 1560 (130x12Mhz) this frequency is visible by Cpu Spy for example, BUT never used by android OS (it can be forced by CPU master only...).
So be careful "inventing" intermediate frequencies: they are totally useless!!!

[herrjemineh]

And if we change the value in that file?

[giouncino]

And if we change the value in that file?

you can't, because we don't have ALL the source code for making a working kernel for M6pro.
We have an already coded kernel in which we change some parameters without recoding again.

[fazerg]

kernel sources are available for RK3188 but not for Pipo tablets. Therefore it's a really hard work to compile new kernel as you have to go through loads of things and select proper. Not even sure we can get all the drivers required to implement them.

[giouncino]

kernel sources are available for RK3188 but not for Pipo tablets. Therefore it's a really hard work to compile new kernel as you have to go through loads of things and select proper. Not even sure we can get all the drivers required to implement them.

they are available for stick not so easy to make it working for a display of tablets

[fazerg]

that's exactly what I mean

[Billcnz]

Re: Binary patched kernels for Pipo models

Nice work giouncino, tested with Claro version, stable and antutu 21027

Sent from my m6pro running Riley ROM 1.7 KitKat

[giouncino]

Nice work giouncino, tested with Claro version, stable and antutu 21027[ATTACH]4789[/ATTACH]

Sent from my m6pro running Riley ROM 1.7 KitKat

This is the HIGHEST result for an M6pro I have ever seen!
Very good result!

[levicius]

Re: Binary patched kernels for Pipo models

Nice work giouncino, tested with Claro version, stable and antutu 21027[ATTACH]4789[/ATTACH]

Sent from my m6pro running Riley ROM 1.7 KitKat

Very nice !! The best i got was 20400 ,tried only 2 times.

Enviado de meu Nexus 7 usando Tapatalk

[dmr]

the minimum step for voltages is 25mV

For frequency the step is 12Mhz (limitation by the local oscillator) BUT pay attention, because the frequecies that Android will use are written in a kernel compiled file called cpufreq.c .

In details are the following (they are written in many parts of this file):

{.frequency = 312 * 1000, .index = 10}
{.frequency = 504 * 1000, .index = 20},
{.frequency = 816 * 1000, .index = 30},
{.frequency = 1008 * 1000, .index = 40},
{.frequency = 1200 * 1000, .index = 50},
{.frequency = 1416 * 1000, .index = 60},
{.frequency = 1608 * 1000, .index = 70},
{.frequency = 1704 * 1000, .index = 80},
{.frequency = 1800 * 1000, .index = 90},
{.frequency = 1920 * 1000, .index = 100}

(don't care about the "index"),
Then if you set a freq of 1560 (130x12Mhz) this frequency is visible by Cpu Spy for example, BUT never used by android OS (it can be forced by CPU master only...).
So be careful "inventing" intermediate frequencies: they are totally useless!!!

ok, can we say the same about ram and gpu ? any pre-declared freq points/steps?

[giouncino]

RAM steps are at 24Mhz.
There isn't predefined values because on that table can be set only ONE value, BUT rising RAM frequency over 720Mhz seems to increase memory latency.
720Mhz seems to be the best trade off between RAM bandwidth and latency.

[dmr]

RAM steps are at 24Mhz.
There isn't predefined values because on that table can be set only ONE value, BUT rising RAM frequency over 720Mhz seems to increase memory latency.
720Mhz seems to be the best trade off between RAM bandwidth and latency.

thanks
tested: stock / 720 / 768 / 792
best results was on 768 (and i use it now and cpu table i posted before, antutu - 19400+)

[giouncino]

1440Mhz for the CPU is not good for the reasons I told you before.
It is better that you set it back to 1416Mhz
For a JB rom 19400-19500 is easily reachable also with RAM to 720Mhz.