What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

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

It's said that there are tiny differences in the cpu chips when they're manufactured. This combined with length of use and maybe stress or heat or something like that can make one chip be unable to run a set of values that another could run perfectly fine. You should really read this one thread on overclocking/undervolting... I'm on my phone right now so ill find it later and post it.

For now, here's a link I made to some research pete of bugless beast did on voltages. Pretty helpful to get a general idea of what might work for you....
bit.ly/vchart

Sent from my Droid using Tapatalk
 
It would awesome to see what prime could do with this now that so many changes have been made.
His work STILL stands up.
This rom has to be getting close and his finishing touches would really make my day.
Sure do miss the guy and hope he's doing well.
 
thank you soooo much for this. the deprimed kernel brought me back to the way my og droid should be running...super fast and super cool...
 
Can anyone confirm whether the standard "deprimed" script is LV or SV? I'm trying it with "overclock" right now but I've had issues in the past everytime I use an ULV kernel so I'm not expecting it to last. I saw in one of the changes early on LV was used as the standard "deprimed" kernel setting but I can't figure out if it's still like that. I'd rather not use SV as I already seem to get warm enough on an LV when playing with the various Angry Birds games.
 
I believe the original point of this kernel was to allow individual users the ability to edit voltages as per the tolerances of each device.

Each individual device has a maximum clockspeed that it is able to run at. This will vary from Droid to Droid.

For every clockspeed there is a minimum voltage/vsel each individual device will function reliably at.

Higher voltage/vsel = higher battery drain. As well as higher temperature. Higher temp = higher CPU stress and lower reliability.

The biggest benefit we see when these come together is battery life.

An example is as follows:

The original kernel was clocked to 550mhz with a vsel of 56...

My phone is capable of running 900mhz at a vsel of 56. This translates to (for me) a 50% increase in speed while keeping the battery drain and CPU temp the same as it was designed for.

At 550mhz my phone works with a vsel of 38 or so. The battery lasts a hell of a lot longer.

I usually keep my phone at 800mhz/ 48vsel which is overclocked adequately and still operates as a battery saver from the stock kernal.

Play around with milestone OC find the values that work for you. It is worth it as you get a custom kernel taulored for your device.

Sent from my Droid using DroidForums
 
Does anyone want to help me bring deprimed back to life? or do you know anyone that would want to help me? I can pull stuff from his github but can't get it to build.
 
I wish I knew Linux to help ya on that winner, I can offer to be a tester though...my Droid is a champ when it comes to running super low voltages and crazy high speeds

Sent from my Droid using DroidForums
 
yea, i dont know anyone with his linux experience. cvcps could but has his hands full. what about chevyno1?
he has his own kernels, maybe he can get it crackin
 
Or Peter Alphonso of bugless beast, all he is currently working on is his stock gingerbread rom, Chevy is very busy lately with making new roms and new jobs he has now...what about corcor?

Sent from my Droid using DroidForums
 
THis is so overwhelming

I finally after 1.5 years am trying to get into this stuff to breathe new life into my phone.

I just got CM7.1 on my phone.

Why do I want this kernal? Is it strictly for overclocking? and how do I apply it?

Its hard to figure all this out because all the posts are by people "in the know", its not exactly noob friendly.

All help is appreciated, in the meantime, I'll keep on reading!

Thanks again.
 
# primed
Disclaimer: You have enabled overclock, your device will now run the /etc/init.d/20overclock script and overclock module upon boot.
To disable please run the command 'deprime' in a su shell.
executing 20overclock
insmod: init_module 'overclock.ko' failed (File exists)

I'm on UD2.5 and can't get custom kernel settings to survive reboot. I have the milestone oc, ran the overclock script and ran the primed command after I set the values I wanted. I think the fail line above has something to do with it.

Anyone lend a hand?
________________________
You had me at herro
 
Last edited:
This oc script is what I use...

Edit the values to what you KNOW works for YOUR droid name it 20overclock and put it in your etc/init.d directory.

If the values are incorrect you may bootloop. So be careful.

#!/system/bin/sh

# PRIMED KERNEL

MODDIR=/system/lib/modules/
MODULE=overclock.ko
VARIABLES=msocv

cd $MODDIR
insmod $MODULE

$VARIABLES

echo "6 300000" > /proc/overclock/freq_table
echo "1 300000000 26" > /proc/overclock/mpu_opps

echo "5 450000" > /proc/overclock/freq_table
echo "2 450000000 32" > /proc/overclock/mpu_opps

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

echo "3 700000" > /proc/overclock/freq_table
echo "4 700000000 42" > /proc/overclock/mpu_opps

echo "2 800000" > /proc/overclock/freq_table
echo "5 800000000 48" > /proc/overclock/mpu_opps

echo "1 900000" > /proc/overclock/freq_table
echo "6 900000000 56" > /proc/overclock/mpu_opps

echo "62" > /proc/overclock/max_vsel
echo "1000000" > /proc/overclock/max_rate

echo "Your system is now running the following slots and vsel values..."
cat /proc/overclock/mpu_opps

echo "Kernel has been primed for ULV"

Sent from my Droid using DroidForums
 
Last edited:
Back
Top