View Single Post
Posts: 11 | Thanked: 7 times | Joined on Jun 2010
#14
Originally Posted by Dragoss91 View Post
Ok , now I'm using this .

FREQS="0:20,90 250:30 500:38,360 1000:60,500"
UP_THRESHOLD=75
SAMPLING_RATE=150000

Voltages are good ?
yup, voltages are normal now.

each device has a processor with different yields, you might be able to go lower, but you have to experiment.

if the voltage too low, it will just restart and you have to change the voltage again and try.

mine is 0:25, 250:25, 500:35, 1000:60

some people go much much lower.

you can create copies of the included profiles and modify them further. those are lv, ulv, xlv and ideal

but do remember what you modify so that you know what caused the device to freeze and adjust that value. so always keep a reference copy once you reach a stable voltage.

most importantly, change one value at a time and test it, or else you wont know which value caused the freezing/rebooting.

ideal methods to test would be to play a media file while online using wifi and loading some video from youtube for e.g. - use your imagination.

install conky as well to see what is the processor doing when running tasks in the background

htop also is a good application to monitor running daemons and apps but conky is more graphical and shows more information at a glance

try this first,

0:20, 250:30, 500:38, 1000:56

if it is stable at that for a day, running multiple tasks, try this

0:20, 250:30, 500:38, 1000:52

if it crashes at 52 try 54

you get the idea

and then once you find a stable voltage for 1000 for e.g. 56, then adjust the voltage for 500, for e.g. 34

0:20, 250:30, 500:34, 1000:56

its a very logical method to find all the lowest voltages for each frequency.

and remember, stability is more important than lowest possible voltage, because if its unstable and reboots - you know how much battery rebooting process eats ???

Last edited by jananan; 2011-05-12 at 22:07.
 

The Following User Says Thank You to jananan For This Useful Post: