[KERNEL] Kernel (deprimed_test) - Break It If You Can

[prime]

I actually do not recommend anyone keep running your device @1200mhz, this is my daily driver script:

Bump up the vsel values a little if your droid doesn't like LV/ULV kernels.

echo "58" > /proc/overclock/max_vsel
echo "900000" > /proc/overclock/max_rate

echo "6 200000" > /proc/overclock/freq_table
echo "1 200000000 22" > /proc/overclock/mpu_opps

echo "5 400000" > /proc/overclock/freq_table
echo "2 400000000 30" > /proc/overclock/mpu_opps

echo "4 500000" > /proc/overclock/freq_table
echo "3 500000000 34" > /proc/overclock/mpu_opps

echo "3 600000" > /proc/overclock/freq_table
echo "4 600000000 40" > /proc/overclock/mpu_opps

echo "2 700000" > /proc/overclock/freq_table
echo "5 700000000 48" > /proc/overclock/mpu_opps

echo "1 800000" > /proc/overclock/freq_table
echo "6 800000000 55" > /proc/overclock/mpu_opps

★edited values were wrong★

 

[jerroedr]

I actually do not recommend anyone keep running your device @1200mhz, this is my daily driver script:

Bump up the vsel values a little if your droid doesn't like LV/ULV kernels.

echo "58" > /proc/overclock/max_vsel
echo "900000" > /proc/overclock/max_rate

echo "6 200000" > /proc/overclock/freq_table
echo "1 200000000 22" > /proc/overclock/mpu_opps

echo "5 400000" > /proc/overclock/freq_table
echo "2 400000000 30" > /proc/overclock/mpu_opps

echo "4 500000" > /proc/overclock/freq_table
echo "3 500000000 34" > /proc/overclock/mpu_opps

echo "3 600000" > /proc/overclock/freq_table
echo "4 600000000 40" > /proc/overclock/mpu_opps

echo "2 700000" > /proc/overclock/freq_table
echo "5 700000000 48" > /proc/overclock/mpu_opps

echo "1 800000" > /proc/overclock/freq_table
echo "6 800000000 55" > /proc/overclock/mpu_opps

★edited values were wrong★

the reprimed values?

 

[mightybrick]

I actually do not recommend anyone keep running your device @1200mhz, this is my daily driver script:

Bump up the vsel values a little if your droid doesn't like LV/ULV kernels.

echo "58" > /proc/overclock/max_vsel
echo "900000" > /proc/overclock/max_rate

echo "6 200000" > /proc/overclock/freq_table
echo "1 200000000 22" > /proc/overclock/mpu_opps

echo "5 400000" > /proc/overclock/freq_table
echo "2 400000000 30" > /proc/overclock/mpu_opps

echo "4 500000" > /proc/overclock/freq_table
echo "3 500000000 34" > /proc/overclock/mpu_opps

echo "3 600000" > /proc/overclock/freq_table
echo "4 600000000 40" > /proc/overclock/mpu_opps

echo "2 700000" > /proc/overclock/freq_table
echo "5 700000000 48" > /proc/overclock/mpu_opps

echo "1 800000" > /proc/overclock/freq_table
echo "6 800000000 55" > /proc/overclock/mpu_opps

★edited values were wrong★

Is the test 5 kernel able to use any kind of 20overclock script like reprimed? It would be nice to have these values automatically loaded after a reboot.

 

[DanDroidX]

I'm loving that you brought back the MSOC app. This is a great kernel. So... the secret sauce is next?

 

[prime]

I actually do not recommend anyone keep running your device @1200mhz, this is my daily driver script:

Bump up the vsel values a little if your droid doesn't like LV/ULV kernels.

echo "58" > /proc/overclock/max_vsel
echo "900000" > /proc/overclock/max_rate

echo "6 200000" > /proc/overclock/freq_table
echo "1 200000000 22" > /proc/overclock/mpu_opps

echo "5 400000" > /proc/overclock/freq_table
echo "2 400000000 30" > /proc/overclock/mpu_opps

echo "4 500000" > /proc/overclock/freq_table
echo "3 500000000 34" > /proc/overclock/mpu_opps

echo "3 600000" > /proc/overclock/freq_table
echo "4 600000000 40" > /proc/overclock/mpu_opps

echo "2 700000" > /proc/overclock/freq_table
echo "5 700000000 48" > /proc/overclock/mpu_opps

echo "1 800000" > /proc/overclock/freq_table
echo "6 800000000 55" > /proc/overclock/mpu_opps

★edited values were wrong★

Is the test 5 kernel able to use any kind of 20overclock script like reprimed? It would be nice to have these values automatically loaded after a reboot.

Were not that far along just yet, it is possible but I'm not posting how just yet as it can cause a bootloop situation if the vsel values aren't thoroughly tested first...then there's all the changes I will be making still that may break thongs.

If your going to stick with this particular kernel build I will tell you how but I'm going offline for the night, pm me and ill get back will you.

 

[prime]

I'm loving that you brought back the MSOC app. This is a great kernel. So... the secret sauce is next?

Not yet, closer each test.

 

[afallucco]

Prime, I took your values and just changed the top slot of the kernel to 1 ghz and 60vsel.

Sent from my Droid using Tapatalk

 

[droidwire]

Prime how can I check if I have successfully flashed test 5?

Sent from my Droid using DroidForums App

 

[prime]

Prime how can I check if I have successfully flashed test 5?

Sent from my Droid using DroidForums App

If you flashed the kernel your running it?

My build number reset because my source isn't git controlled and I had to restart from scratch...next build should have different number.

 

[DanDroidX]

It would be cool if you could make/ have some one else make a unique icon for you MSOC app.

 

[droidwire]

That explains the build number 1. So looks like I am running test5. Compcache stats though give me errors. I cannot load MOC various versions I tried.

Sent from my Droid using DroidForums App

 

[droidwire]

Prime how can I check if I have successfully flashed test 5?

Sent from my Droid using DroidForums App

If you flashed the kernel your running it?

My build number reset because my source isn't git controlled and I had to restart from scratch...next build should have different number.

That explains the build number 1. So looks like I am running test5. Compcache stats though give me errors. I cannot load MOC various versions I tried.

Sent from my Droid using DroidForums App

BTW prime I m running test5 with winner 7-2. I am trying winner 8 today.

 

[chipmunk]

ok just wondering how do i change the kernel so that i can run for example at 900 mhz? and is it necessary to use the milestone app? or can i use setcpu? and lastly do i need to delete the previous overclock file before putting 99overclock in system/etc/int.d?

 

[mightybrick]

It appears something in build 8 breaks compcache (zram) with deprimed test 5. When entering "free" in terminal it returns 0 in swap. When I flashed back to build 7 and reflashed deprimed test 5, "free" returns numbers indicating swap is in use. So, build 7 has a functional compcache, and build 8 breaks it. I haven't tested build 8 with the reprimed kernel to see if its only broken with the deprimed test 5 kernel.

 

[emflow]

@mightybrick

I'm currently running winner's build 8 w/deprimed #5 and compcache + oc are working. Try this:

1. Redownload deprimed #5 (dunno if prime made any changes).

2. Before installing the kernel, set compcache to disabled in cyanogenmod settings (I think this was the key step).

Sent from my Droid using DroidForums App