setscaling.sh takes no parameters
setclock.sh mhz vsel
So just "setscaling.sh" and "setclock.sh 1150000 34" for example. One note, both assume overclock.ko has been loaded. So after a reboot, you must do it as follows:
insmod /system/lib/modules/overclock.ko (loads kernel module here)
setscaling.sh (or your setclock.sh)
Thanks, I've done the commands in the 1st post to allow over-clocking already and have had good results. With me being new to the command line stuff could you please give me all of the commands for getting your script up and running? I tried the setclock.sh command and got an error so I'm missing something even with that.
Again, I apologize but this is new to me and I don't want to mess something up.
I have gotten some high 1300s in Quadrant and 9.5s in Linpack on 1.15ghz @ 34 vsel. The stock settings are 1.0ghz @ 66 vsel. So we're using substantially less voltage. The setscaling.sh script I posted above lowers the voltages across the board. I haven't been running overclocked long enough to know how good/bad it impacts battery, but supposedly lower voltages = less battery use.
I think I'm seeing better battery. Since I have less than 1 day using these speeds/voltages I don't want to rule out placebo just yet. I'm at 60% after my normal everyday use. Usually I've put it on the charger by now (meaning <30%).
Maybe others can chime in on their battery results after using the low voltages for some time.
I also have been running it fine at 1.15ghz @ 34
This could porbably give me a few more hours of phone use.
Does anyone know how to make this automatically start at boot?
I was having issues with the 1150000 34 max setting (lots of lag) and since I was having real good results earlier with 1125000 45 I edited the values of the setscaling.sh in RE and everything is now really stable. I'm getting Qaudrant scores in the 1380-1410 range consistently now.
I'll keep track of my battery usage tomorrow and see how it goes.
Basically pull /init.rc to your desktop, edit it to add the 2 lines to the bottom, and push it back. I think you're going to have to copy it to /sdcard first since it is owned by root. You're also going to have to remount the root file system to read/write since it is read only.
insmod /system/lib/modules/overclock.ko
setscaling.sh
Okay, got it copied to /sdcard/init.rc. Opened up and ready to add in those two lines. One more assurance. Can I recover if this bricks? And if so, can I recover to where i was prior, or just back to factory settings?
Also, would the mount remount commands used in the op work to remount the root file system as you stated above? If so, I am assuming I would sandwich the insmod lines between them just as in the op. That correct?
Can I just do this with RE? Adding it into /init.rc with that?
I would also like to adjust the setscaling.sh befoe i attempt any of this. Would i just dl the setscale zip file and do it all from the beginning again?
Okay, be a few minutes. Putting the kids down and preparing for some work time in case this bombs.Never used RootExplorer. I'm more of a cmd line guy.
I used RE for this. That being said, i will get ur opinion droider13, think i can just edit the init.rc with RE and ha e the same outcome?You can just edit the file on your computer with Notepad++. Thats what Fab and I did
I used RE for this. That being said, i will get ur opinion droid13, think i can just edit the init.rc with RE and ha e the same outcome?
So, just add these two lines:
/system/bin/insmod /system/lib/modules/overclock.ko
/system/bin/setscaling.sh
at the end of init.rc? just like they are? Sorry to annoy anyone. Just trying to make sure.
We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.