Binary patched kernels for Pipo models

[sebastianabate]

Are the voltages for those 2 figures too low?

I haven't seen others with mV lower than 800 for any figures.

Maybe, and thats exactly what I'm trying to test, but the problem is that the first two freqs just dissapear when I apply the patch.

[krucifix85]

Maybe, and thats exactly what I'm trying to test, but the problem is that the first two freqs just dissapear when I apply the patch.

I'm suggesting they might be dissapearing because they are below an 800mV threshold. Try lifting the mV for those 2 figures up to 800mV and see if they re-appear in your table.

[herrjemineh]

How do you know, which freqs are used for cpu/gpu/ram and which not?

[sebastianabate]

I'm suggesting they might be dissapearing because they are below an 800mV threshold. Try lifting the mV for those 2 figures up to 800mV and see if they re-appear in your table.

You are right! whith 800mV as the lowest voltage the patch works OK.

MHz mV
100 800
150 825
200 850
240 875
300 900
400 950
600 1050

Anyone know if 800mV is the minimun voltage we can use? because I use my tablet to read PDFs and EPUBs a lot, and I think that I can extend the battery duration if I can set the first two steps lower than 800mV (assuming that, when the gpu manage static content, it uses the lowest step in the list)

[Slowry]

I reverted back to the stock frequencies as soon as I realized that these are not used.
Unfortunately the only used are the frequencies foreseen in the stock kernel: 300Mhz and 400Mhz (366 ad 466 are ignored by the system).

I don't think that these values are not used, but both tables are doing the same because the system recalculate the table with our approx values and only use this one :

128, 198, 256, 297 (for 300 or 366), 384 (for 400 or 466), 594

So, to be more realistic or less ambiguous we should use the real values !

You can see these values after a reboot. Just have a look at the log startup, for example type :

su
dmesg | grep mali

[giouncino]

I don't think that these values are not used, but both tables are doing the same because the system recalculate the table with our approx values and only use this one :

128, 198, 256, 297 (for 300 or 366), 384 (for 400 or 466), 594

So, to be more realistic or less ambiguous we should use the real values !

You can see these values after a reboot. Just have a look at the log startup, for example type :

su
dmesg | grep mali

Yes, you're right (I used wrong words to say the same thing...), but the result is the same: 300 = 366, 400 = 466. So it seems completely useless to change these frequency values.

[krucifix85]

You are right! whith 800mV as the lowest voltage the patch works OK.

MHz mV
100 800
150 825
200 850
240 875
300 900
400 950
600 1050

Anyone know if 800mV is the minimun voltage we can use? because I use my tablet to read PDFs and EPUBs a lot, and I think that I can extend the battery duration if I can set the first two steps lower than 800mV (assuming that, when the gpu manage static content, it uses the lowest step in the list)

I would say the bottom 2 CPU voltages would also net you large battery savings, if you were to get them as low as possible.

Also, is it necessary to actually increase the GPU voltages for the first 2 steps? What's stopping you from using a table like this:

MHz mV
100 800
150 800
200 850
240 875
300 900
400 950
600 1050

[giouncino]

I would say the bottom 2 CPU voltages would also net you large battery savings, if you were to get them as low as possible.

Also, is it necessary to actually increase the GPU voltages for the first 2 steps? What's stopping you from using a table like this:

MHz mV
100 800
150 800
200 850
240 875
300 900
400 950
600 1050

How can you say that?
Do you know when 100150Mhz are actually used?
It is also possible that 100/150/200 in reality are not used and the GPU is normally set directly to 256Mhz during browsing ad set to 594 for gaming (this is an example, i don't know ).
For me the GPU frequency scaling is a mistery...

And then, thinking a lot, now I'm having some doubt that the GPU change voltages as we set in the kernel.img.
Have you tried setting 600Mhz@850-900mV to see if the tablet freeze or shows artifacts?
If does not freeze we are loosing time: the GPU voltages are actually written elsewhere.
I'm saying this because a -200mV for 600Mhz (from 1250mV to 1050mV) in my opinion is not realistic...In the sense that as far as I know for IT technology a reduction of 20% in voltage from the stock... is HUGE and often impossible...or PIPO guys are stupid and they are risking to fry the GPU...

[X-Ray]

Hi at all..
Thx for the wonderful description to pach a kernel. Finally i create my own kernel

"cpu1608h" =>
[
[850000, 312000],
[875000, 504000],
[900000, 816000],
[1000000, 1008000],
[1075000, 1200000],
[1175000, 1416000],
[1275000, 1608000],
],

"gpu600" =>
[
[875000, 133000],
[900000, 200000],
[950000, 266000],
[975000, 300000],
[1025000, 400000],
[1175000, 600000],
],

"ddr720" =>
[
[1200000, 720001],

because all over1608 Mhz don t finish antutu and crach at 27 %
but i want to have a kernel with battery saving settings.
I hope it works now . Antuto is working with 18600 points and i hope its stabele with low power consumtion.
Ray

[heisenberg]

su
dmesg | grep mali

Do I have to use the terminal Emulator apk to run this command? Cause doing this gaves me no output.?

[giouncino]

Do I have to use the terminal Emulator apk to run this command? Cause doing this gaves me no output.?

yes, you need terminal emulator.
Write down:

su (enter)
busybox dmesg | grep freq (enter)

1-2 minutes after booting the tablet.

[Slowry]

How can you say that?
For me the GPU frequency scaling is a mistery...

And then, thinking a lot, now I'm having some doubt that the GPU change voltages as we set in the kernel.img.
Have you tried setting 600Mhz@850-900mV to see if the tablet freeze or shows artifacts?
If does not freeze we are loosing time: the GPU voltages are actually written elsewhere.
I'm saying this because a -200mV for 600Mhz (from 1250mV to 1050mV) in my opinion is not realistic...In the sense that as far as I know for IT technology a reduction of 20% in voltage from the stock... is HUGE and often impossible...or PIPO guys are stupid and they are risking to fry the GPU...

Yes !! I'm agree, I also doubt about real GPU voltage.

The voltage can also be set to never go below a critical value... with hardware regulator is a "normal" behaviour.

The freq table is the good one because we can put something like this 128, 128, 256, 256 ... and the system accept this.

So it's time to play with impossible mix !!!

[sebastianabate]

Yes !! I'm agree, I also doubt about real GPU voltage.

The voltage can also be set to never go below a critical value... with hardware regulator is a "normal" behaviour.

The freq table is the good one because we can put something like this 128, 128, 256, 256 ... and the system accept this.

So it's time to play with impossible mix !!!

OK, tonight I'm going to test with 800mV on all steps and then do some benchmarks (I'm going to use 3DMark, because it seems to be more "stressing" than Antutu).


Just one question before I brick my tablet... the bootloader mode needs the GPU? because if the GPU is powered on in bootloader mode and I use a very low voltage, there is the chance that the tablet get stuck into a bootloop, and I'm not going to be able to flash another kernel.

[mad86]

Hello there is a howto usePHJAnderson's Perl Script ? thanks

I dl the latest ROM for M7 and i want to try it

Edit : i try but i have "ERROR: DDR profile table ddr667 is larger than the DDR table in the kerneluser" error ? Do y ou have an idea ?

[heisenberg]

yes, you need terminal emulator.
Write down:

su (enter)
busybox dmesg | grep freq (enter)

1-2 minutes after booting the tablet.

The output is this (after deepsleep) :
u0_a94@android:/ $ su
root@android:/ # busybox dmesg | grep freq
[ 0.000000] DDR DEBUG: init success!!! freq=300MHz
[ 1.322331] rk3188 cpufreq version 2.0, suspend freq 1008 MHz
[ 6.303278] mmc_rescan_try_freq..1718.. ===== Initialize SD-card successfully. [mmc0]
[ 6.510813] ddrfreq: verion 2.4 20130427
[ 6.510831] ddrfreq: normal 720MHz video 0MHz dualview 0MHz idle 0MHz suspend 198MHz reboot 300MHz
[ 6.512749] ddrfreq: change freq to 720 MHz when normal
[ 7.974266] Mali: mali freq table num : 6
[ 7.974283] Mali: mali freq table :Mali: 128,Mali: 198,Mali: 256,Mali: 297,Mali: 384,Mali: 594,Mali:
[ 71.497602] mmc_rescan_try_freq..1675.. ===== Initialize SDIO successfully. [mmc1]
[ 91.679469] ddrfreq: change auto self refresh to 1 when suspend
[ 91.681089] ddrfreq: change freq to 198 MHz when suspend
[ 483.803932] ddrfreq: change auto self refresh to 0 when normal
[ 483.805568] ddrfreq: change freq to 720 MHz when normal
[ 1270.574305] ddrfreq: change auto self refresh to 1 when suspend
[ 1270.576039] ddrfreq: change freq to 198 MHz when suspend
[ 1284.282447] ddrfreq: change auto self refresh to 0 when normal
[ 1284.309588] ddrfreq: change freq to 720 MHz when normal
[ 1294.843499] ddrfreq: change auto self refresh to 1 when suspend
[ 1294.845024] ddrfreq: change freq to 198 MHz when suspend
[15112.000364] ddrfreq: change auto self refresh to 0 when normal
[15112.001994] ddrfreq: change freq to 720 MHz when normal
root@android:/ #