[KERNEL][AP6210] Overclocked kernels for Neomode ROMs (2.1/2.0/1.9a/1.7)

[valzja]

Re: [KERNEL][AP6210] Overclocked kernels for Neomode ROMs (2.1/2.0/1.9a/1.7)

Yes, it looks like 1.9a doesn't like much overclocked kernels... even stock kernels did that... i can't even do dmesg on my stick with 1.9a because it goes nuts, and gives me a lot of errors i think that as of now, the best rom is the 2.1 beta, i'm using it as my daily driver, i left it with a stress test of running movies along the whole day and it never crashed

my screen is flickering on that ROM... i don't even need to overclock to get that...

Sent from my Nexus 7 using Tapatalk

[Pet2001]

And thats the problem we got. Even us with the RK3188 without the T. We cant oc GPU and Ram!

As far as I have observed with my tests, kernels from neo1.9a were compiled from a source tree which contained just the cpu freq. limitation directive for T-models. Here you can find a trace of such a limitation in the kernel source: if you follow the kernel source flow, you will find both a specific limitation to 1412 MHz for T-flagged rk3188 cpus, and the "cpufreq: delete arm freq..." kernel log message as a result of the T-flag being on.
As a fact, there is scarce hope to get cpu overclock to work on RK3188-T devices by starting from the kernels delivered with Neo1.9a rom. The only chance would be to compile a kernel from scratch with the same config of kernel3 and without the limit for T-flagged machines.

However, not evertything is lost for T-cpu users, like me, who wants to use Neo1.9a, since we can still get both GPU and DDR overclocking! Regarding GPU and RAM, I haven't found any limitation: neither at hardware nor at software level.
With the kernel I attach in the following, which I obtained by patching kernel3 of Neo1.9a rom, I have got such rom to work at 1080px, GPU 768 and DDR 800 (but cpu at 1.4GHz max), as you can see in my dvfs tree:
...
<4>[ 860.946700] | | |- clock: ddr current: rate 792000, volt = 1250000, enable_dvfs = ENABLE
<4>[ 860.946811] | | |- clk limit:[400000000, 800000000]; last set rate = 0
<4>[ 860.946885] | | | |- clock parents: pd_cpu, vd_parent = vd_core
<4>[ 860.946961] | | | |- freq = 396000, volt = 1100000
<4>[ 860.947020] | | | |- freq = 792000, volt = 1250000
<4>[ 860.947087] | |
<4>[ 860.947710] | |- power domaind_gpu, status = OFF, current volt = 1250000
<4>[ 860.947801] | | |
<4>[ 860.947811] | | |- clock: gpu current: rate 594000, volt = 1250000, enable_dvfs = ENABLE
<4>[ 860.947921] | | |- clk limit:[133000000, 800000000]; last set rate = 594000000
<4>[ 860.948007] | | | |- clock parents: pd_gpu, vd_parent = vd_core
<4>[ 860.948082] | | | |- freq = 384000, volt = 1100000
<4>[ 860.948140] | | | |- freq = 594000, volt = 1250000
<4>[ 860.948204] | | | |- freq = 768000, volt = 1350000
...
With this patched kernel3, my system gets an antutu score higher that 18000, whereas with 'stock' kernel3 of neo1.9a it was scoring just above 16000.

Enjoy this kernel!

[valzja]

As far as I have observed with my tests, kernels from neo1.9a were compiled from a source tree which contained just the cpu freq. limitation directive for T-models. Here you can find a trace of such a limitation in the kernel source: if you follow the kernel source flow, you will find both a specific limitation to 1412 MHz for T-flagged rk3188 cpus, and the "cpufreq: delete arm freq..." kernel log message as a result of the T-flag being on.
As a fact, there is scarce hope to get cpu overclock to work on RK3188-T devices by starting from the kernels delivered with Neo1.9a rom. The only chance would be to compile a kernel from scratch with the same config of kernel3 and without the limit for T-flagged machines.

However, not evertything is lost for T-cpu users, like me, who wants to use Neo1.9a, since we can still get both GPU and DDR overclocking! Regarding GPU and RAM, I haven't found any limitation: neither at hardware nor at software level.
With the kernel I attach in the following, which I obtained by patching kernel3 of Neo1.9a rom, I have got such rom to work at 1080px, GPU 768 and DDR 800 (but cpu at 1.4GHz max), as you can see in my dvfs tree:
...
<4>[ 860.946700] | | |- clock: ddr current: rate 792000, volt = 1250000, enable_dvfs = ENABLE
<4>[ 860.946811] | | |- clk limit:[400000000, 800000000]; last set rate = 0
<4>[ 860.946885] | | | |- clock parents: pd_cpu, vd_parent = vd_core
<4>[ 860.946961] | | | |- freq = 396000, volt = 1100000
<4>[ 860.947020] | | | |- freq = 792000, volt = 1250000
<4>[ 860.947087] | |
<4>[ 860.947710] | |- power domaind_gpu, status = OFF, current volt = 1250000
<4>[ 860.947801] | | |
<4>[ 860.947811] | | |- clock: gpu current: rate 594000, volt = 1250000, enable_dvfs = ENABLE
<4>[ 860.947921] | | |- clk limit:[133000000, 800000000]; last set rate = 594000000
<4>[ 860.948007] | | | |- clock parents: pd_gpu, vd_parent = vd_core
<4>[ 860.948082] | | | |- freq = 384000, volt = 1100000
<4>[ 860.948140] | | | |- freq = 594000, volt = 1250000
<4>[ 860.948204] | | | |- freq = 768000, volt = 1350000
...
With this patched kernel3, my system gets an antutu score higher that 18000, whereas with 'stock' kernel3 of neo1.9a it was scoring just above 16000.

Enjoy this kernel!

nice to hear that... i will try this... but is it possible to make 720p kernel like this ? i tested a lot, i found that i like 720p resolution better because of performance...

[valzja]

it seem's that it's not working for me, because i have cx919 device, maybe there are more importatnt roll for some caind of drivers in 1.9a rom, because i have only errors in dmesg compairing to neo 2.0

[FrankieDedo]

With this patched kernel3, my system gets an antutu score higher that 18000, whereas with 'stock' kernel3 of neo1.9a it was scoring just above 16000.

Enjoy this kernel!

Wow, what have you did to patch kernel like that? i've tried something like 10-15 combinations and i've always got the same results!

Sincerely, i didn't have actually verified with the 1080p kernel (it's the kernel3, right?) do you managed to overclock the 720p too?

[Pet2001]

it seem's that it's not working for me, because i have cx919 device, maybe there are more importatnt roll for some caind of drivers in 1.9a rom, because i have only errors in dmesg compairing to neo 2.0

what errors do you get? can you post your dvfs tree and your dmesg (just the kernel startup part)?

[Pet2001]

Wow, what have you did to patch kernel like that? i've tried something like 10-15 combinations and i've always got the same results!

Sincerely, i didn't have actually verified with the 1080p kernel (it's the kernel3, right?) do you managed to overclock the 720p too?

Yes, it is kernel3.
I haven't tried with kernel1 and kernel2 since I use the one at 1080p.
I obtained the patched kernel by means of overclockomatic with simply using the following profiles for cpu, gpu and ram (tables 6, 7 and 8, respectively, in the kernel):

# CPU profiles
my %cpu_profiles = (
"cpustock" => 0,
# "cpu1608h" =>
# [
# [1150000, 1200000],
# [1250000, 1416000],
# [1350000, 1608000],
# ],
# "cpu1704h" =>
# [
# [1150000, 1200000],
# [1350000, 1608000],
# [1375000, 1704000],
# ],
# "cpu1800h" =>
# [
# [900000, 312000],
# [925000, 504000],
# [1000000, 816000],
# [1075000, 1008000],
# [1150000, 1200000],
# [1250000, 1416000],
# [1350000, 1608000],
# [1375000, 1800000],
# ],
# "cpu1920h" =>
# [
# [1150000, 1200000],
# [1350000, 1608000],
# [1450000, 1920000],
# ],
);


# GPU profiles
my %gpu_profiles = (
"gpustock" => 0,
# "gpu600" =>
# [
# [975000, 133000],
# [1000000, 200000],
# [1025000, 266000],
# [1050000, 300000],
# [1100000, 400000],
# [1250000, 600000],
# ],
# "gpu600h" =>
# [
# [1100000, 400000],
# [1250000, 600000],
# ],
"gpu798h" =>
[
[1100000, 400000],
[1250000, 600000],
[1375000, 798000],
],
);


# DDR profiles
# the final digit of the frequency signifies the following:
# 1 DDR_FREQ_NORMAL
# 2 DDR_FREQ_VIDEO
# 3 DDR_FREQ_IDLE
# 4 DDR_FREQ_SUSPEND
# only 1 and 2 seem to be used in the source code for Android sticks and even though 2 is set it doesn't seem to be used

my %ddr_profiles = (
"ddrstock" => 0,
"ddr800" =>
[
[1100000, 400002],
[1250000, 800001],
],
);

[FrankieDedo]

Yes, it is kernel3.
I haven't tried with kernel1 and kernel2 since I use the one at 1080p.
I obtained the patched kernel by means of overclockomatic with simply using the following profiles for cpu, gpu and ram (tables 6, 7 and 8, respectively, in the kernel):

LOL that overclockomatic file is identical to mine, it means that maybe my kernel is overclocked too :P Anyway, since i've used the same method as you, probably the 720p can't be overclocked (probably, the 1080p kernel derivates from a sam321 kernel, instead the 720p ones are different) it makes sense because 1080p and 720p kernels have completely different cpu tables (and gpu too, if i'm not wrong)

[Pet2001]

I don't think kernel3 from neo1.9a is derived from a sam kernel, since when I tried to flash sam kernels over neo1.9a my device got stuck in bootlooping, while if I use sam kernel over neo1.7 it runs fine and supports cpu overclock up to 1800MHz.
Moreover, if I try to patch kernel3 with overclockomatic in order to get cpu overclock, I don't get frequencies above 1.4 GHz and in dmesg I find:
...
<4>[ 0.743050] cpufreq: delete arm freq(1608000)
<4>[ 0.743084] cpufreq: delete arm freq(1800000)
...
which means that kernel3 was built with the T-flag limit enabled

[basmand]

And thats the problem we got. Even us with the RK3188 without the T. We cant oc GPU and Ram!

Hi
I got the RK3188 running SAM kernel and ROM neomode 2.1Beta I have oc n CPU and RAM, but not GPU as you said
|- power domaind_cpu, status = OFF, current volt = 1200000
<4>[ 164.800060] | | |
<4>[ 164.800066] | | |- clock: ddr current: rate 744000, volt = 1200000, enable_dvfs = ENABLE
<4>[ 164.800103] | | | |- clock parents: pd_cpu, vd_parent = vd_core
<4>[ 164.800129] | | | |- freq = 744000, volt = 1200000
<4>[ 164.800152] | |
<4>[ 164.800157] | |- power domaind_peri, status = OFF, current volt = 0
<4>[ 164.800217] | | |
<4>[ 164.800223] | | |- clock: aclk_periph current: rate 0, volt = 0, enable_dvfs = DISABLE
<4>[ 164.800260] | | | |- clock parents: pd_peri, vd_parent = vd_core
<4>[ 164.800288] | | | |- freq = 100000, volt = 1000000
<4>[ 164.800308] | | | |- freq = 200000, volt = 1050000
<4>[ 164.800332] | | | |- freq = 300000, volt = 1070000
<4>[ 164.800354] | | | |- freq = 500000, volt = 1100000
<4>[ 164.800372] | |
<4>[ 164.800378] | |- power domaind_gpu, status = OFF, current volt = 975000
<4>[ 164.800405] | | |
<4>[ 164.800409] | | |- clock: gpu current: rate 127285, volt = 975000, enable_dvfs = ENABLE
<4>[ 164.800440] | | | |- clock parents: pd_gpu, vd_parent = vd_core
<4>[ 164.800461] | | | |- freq = 128000, volt = 975000
<4>[ 164.800480] | | | |- freq = 179000, volt = 1000000
<4>[ 164.800498] | | | |- freq = 223000, volt = 1025000
<4>[ 164.800518] | | | |- freq = 297000, volt = 1050000
<4>[ 164.800535] | | | |- freq = 297000, volt = 1100000
<4>[ 164.800554] | | | |- freq = 446000, volt = 1200000
<4>[ 164.800571] | |
<4>[ 164.800576] | |- power domaind_vio, status = OFF, current volt = 0
<4>[ 164.800601] | |
<4>[ 164.800605] | |- power domaind_video, status = OFF, current volt = 0
<4>[ 164.800629] |
<4>[ 164.800633] |- voltage domain:vd_cpu
<4>[ 164.800650] |- current voltage:1000000
<4>[ 164.800664] | |
<4>[ 164.800668] | |- power domaind_scu, status = OFF, current volt = 0
<4>[ 164.800692] | |
<4>[ 164.800697] | |- power domaind_debug, status = OFF, current volt = 0
<4>[ 164.800721] | |
<4>[ 164.800725] | |- power domaind_a9_3, status = OFF, current volt = 1000000
<4>[ 164.800753] | | |
<4>[ 164.800758] | | |- clock: cpu current: rate 816000, volt = 1000000, enable_dvfs = ENABLE
<4>[ 164.800791] | | | |- clock parents: pd_a9_0, vd_parent = vd_cpu
<4>[ 164.800813] | | | |- clock parents: pd_a9_1, vd_parent = vd_cpu
<4>[ 164.800834] | | | |- clock parents: pd_a9_2, vd_parent = vd_cpu
<4>[ 164.800855] | | | |- clock parents: pd_a9_3, vd_parent = vd_cpu
<4>[ 164.800876] | | | |- freq = 312000, volt = 900000
<4>[ 164.800893] | | | |- freq = 504000, volt = 925000
<4>[ 164.800910] | | | |- freq = 816000, volt = 1000000
<4>[ 164.800930] | | | |- freq = 1008000, volt = 1075000
<4>[ 164.800951] | | | |- freq = 1200000, volt = 1150000
<4>[ 164.800969] | | | |- freq = 1416000, volt = 1250000
<4>[ 164.800987] | | | |- freq = 1608000, volt = 1350000
<4>[ 164.801004] | | | |- freq = 1704000, volt = 1350000
<4>[ 164.801022] | | | |- freq = 1800000, volt = 1400000
<4>[ 164.801040] | |


Basmand

[FrankieDedo]

I don't think kernel3 from neo1.9a is derived from a sam kernel, since when I tried to flash sam kernels over neo1.9a my device got stuck in bootlooping, while if I use sam kernel over neo1.7 it runs fine and supports cpu overclock up to 1800MHz.
Moreover, if I try to patch kernel3 with overclockomatic in order to get cpu overclock, I don't get frequencies above 1.4 GHz and in dmesg I find:
...
<4>[ 0.743050] cpufreq: delete arm freq(1608000)
<4>[ 0.743084] cpufreq: delete arm freq(1800000)
...
which means that kernel3 was built with the T-flag limit enabled

Yep, i said that just because when i was messing around, i noticed that kernels were similar.

[Pet2001]

Hi
I got the RK3188 running SAM kernel and ROM neomode 2.1Beta I have oc n CPU and RAM, but not GPU as you said

Are you running sam kernel at 1080p with cpu 1800 and ddr 1500?
If yes, you can try this kernel (a patched version os sam's one) and let us know.

[locolars]

As far as I have observed with my tests, kernels from neo1.9a were compiled from a source tree which contained just the cpu freq. limitation directive for T-models. Here you can find a trace of such a limitation in the kernel source: if you follow the kernel source flow, you will find both a specific limitation to 1412 MHz for T-flagged rk3188 cpus, and the "cpufreq: delete arm freq..." kernel log message as a result of the T-flag being on.
As a fact, there is scarce hope to get cpu overclock to work on RK3188-T devices by starting from the kernels delivered with Neo1.9a rom. The only chance would be to compile a kernel from scratch with the same config of kernel3 and without the limit for T-flagged machines.

However, not evertything is lost for T-cpu users, like me, who wants to use Neo1.9a, since we can still get both GPU and DDR overclocking! Regarding GPU and RAM, I haven't found any limitation: neither at hardware nor at software level.
With the kernel I attach in the following, which I obtained by patching kernel3 of Neo1.9a rom, I have got such rom to work at 1080px, GPU 768 and DDR 800 (but cpu at 1.4GHz max), as you can see in my dvfs tree:
...
<4>[ 860.946700] | | |- clock: ddr current: rate 792000, volt = 1250000, enable_dvfs = ENABLE
<4>[ 860.946811] | | |- clk limit:[400000000, 800000000]; last set rate = 0
<4>[ 860.946885] | | | |- clock parents: pd_cpu, vd_parent = vd_core
<4>[ 860.946961] | | | |- freq = 396000, volt = 1100000
<4>[ 860.947020] | | | |- freq = 792000, volt = 1250000
<4>[ 860.947087] | |
<4>[ 860.947710] | |- power domaind_gpu, status = OFF, current volt = 1250000
<4>[ 860.947801] | | |
<4>[ 860.947811] | | |- clock: gpu current: rate 594000, volt = 1250000, enable_dvfs = ENABLE
<4>[ 860.947921] | | |- clk limit:[133000000, 800000000]; last set rate = 594000000
<4>[ 860.948007] | | | |- clock parents: pd_gpu, vd_parent = vd_core
<4>[ 860.948082] | | | |- freq = 384000, volt = 1100000
<4>[ 860.948140] | | | |- freq = 594000, volt = 1250000
<4>[ 860.948204] | | | |- freq = 768000, volt = 1350000
...
With this patched kernel3, my system gets an antutu score higher that 18000, whereas with 'stock' kernel3 of neo1.9a it was scoring just above 16000.

Enjoy this kernel!

What device do you have? I dont get it, even with that kernel i only get the 3 freqs for GPU. 276, 446, 446 .

[Pet2001]

What device do you have? I dont get it, even with that kernel i only get the 3 freqs for GPU. 276, 446, 446 .

I have a MK809III that mounts a RK3188T. Here you can find some pictures of it.

[locolars]

It sucks. When you got the OC problem of cpu on the rk3188T, we got a OC problem of GPU on mk802iv RK3188! .