OverClocking 101

[ecsnead69]

so what is the best "advanced settings"? I have seen 50000, 70, 00 & 65000, 80, 0, 0..... Do you have a recommendation for a 2.1 ROM? Thanks!!

 

[Skull One]

Skull One, for me this is the most interesting thread on this board. I just updated setcpu to the 1.6.0 version, was using 1.5.1a. On the older version System Panel showed the cpu bouncing from 250 to 800, no stops in between. (mine is set 250 to 800). This new setcpu on System Panel looks more like a tach, it bounces all over, rarely hitting the 800 mark. It looks like the newer setcpu is doing a much better job of managing the cpu than the old one. And it also looks like I really don't need to clock any higher as it's not going to hit that higher mark. All my settings are the same as the older version. Is this what you see as 'normal' behaviour in system panel? Thanks for all your research too ...

SetCPU only sets files on disk that the Android OS reads. Once it sets those files SetCPU does nothing until a profile condition is hit. SetCPU is just finally showing the true frequency as the OS throttles it. Which it didn't always do well in the past versions.

 

[Phxphenom]

I agree that this is one of the most interesting threads going.....So much to learn.....

 

[rcfx]

Ok! That makes sense, I had it backwards, I always thought that setcpu controlled the throttle all the time.

 

[rcfx]

I agree that this is one of the most interesting threads going.....So much to learn.....

I'd bet money that the developer is reading this thread everyday!

 

[Skull One]

I agree that this is one of the most interesting threads going.....So much to learn.....

I'd bet money that the developer is reading this thread everyday!

I wish. If he did, he would put both a CPU and Battery temp profile in instead of only letting you pick one or the other.

 

[Skull One]

so what is the best "advanced settings"? I have seen 50000, 70, 00 & 65000, 80, 0, 0..... Do you have a recommendation for a 2.1 ROM? Thanks!!

Under 2.1 I was running 62500, 75 or 80 (depending on what I was testing), 0, 0 with a 7 slot Low Voltage 1Ghz kernel.

Never seemed slow. Battery life isn't as good as 2.2 but that is to be expected since they learned a lot since 2.1 came out.

 

[Skull One]

I want to take a moment to thank everyone for their kind words and encouragement.

When I started this life sucking hobby (*big grin*) called the Motorola Droid I had no idea what I was getting into. As a professional programmer, I am always asking why code works the way it does and why did the coder choose that method to get the job done. The Android OS, while *NIX based, presents some interesting tweaks to get it to work on a small foot print with software based event triggers. When I went to find out how to use SetCPU, I couldn't find enough info to write 100 words on the subject. And what info I did find was contradicting. Some people said SetCPU did everything. Some said it was the OS doing it. So I spent hours pulling everything apart to find out. That is when I did the first version of the articles back in April. When that thread met its untimely death due to a "scandal" I was asked to redo it. I re-evaluated everything I had done and noticed two things. I was a little wordy and I sometimes dumbed things down when in reality you all wanted the nitty gritty. Hopefully I corrected both.

There have been a lot of great questioned asked over the last 2 months I have been doing this. I hope that trend doesn't end.

 

[czerdrill]

I for one want to thank you for this thread. always something to learn and its good to know that I wasn't crazy (reference to the whole setCPU, bugless beast fiasco) lol. This thread is bookmarked on all my computers and I;ve read every page haa...thanks for a great thread!

 

[Phxphenom]

So here is my "takeaway". I have SetCPU set with a max of 1100 even though the kernel goes to 1250mhz. If you look at my SetCPU icon, it shows 1250MHz at the top with 1100 max and 250 min below it.

So how do I know it is holding to 1100?

Go to System Panel, click on "Menu" and then click on "Monitor" and you will see your CPU activity and for me at least, it does not go above 1100 MHz. The Monitor also has a battery temperatture as well as AK8973 temp sensor which I bet is the CPU itself.

Great thread!

 

[Skull One]

So here is my "takeaway". I have SetCPU set with a max of 1100 even though the kernel goes to 1250mhz. If you look at my SetCPU icon, it shows 1250MHz at the top with 1100 max and 250 min below it.

So how do I know it is holding to 1100?

Go to System Panel, click on "Menu" and then click on "Monitor" and you will see your CPU activity and for me at least, it does not go above 1100 MHz. The Monitor also has a battery temperatture as well as AK8973 temp sensor which I bet is the CPU itself.

Great thread!

Yeah, the widget is still not working right. He should take it back to saying SetCPU and give up on refreshing it or at least allow us the ability to turn it back off again.

AK8973 is the battery sensor. Since System Panel has two display sections he just fills it with the same info. OMAP3430 is how you get the CPU temp. Roll back to a 2.1 ROM with a kernel that has the CPU temp mod built in to see it.

 

[marcogiudice]

skull please just get it over with and please put out your own version of setcpu so the thing will be done right. i kno your busy and dont have time. but i would really appreciate it and so the rest of the community and i would pay top dollar for your hard work

 

[gospursgo2002]

Question about CPU governor on setcpu

I just started rooting again and have been playing around with kernels and themes and have come across a setcpu question for my droid. I understand what the governors do as far as how the cpu scales, but I'm curious how they are supposed to function. For instance earlier today I set it on powersaver and I noticed that the maximum dropped down to 800 from 1100 automatically. Now this made perfect sense to me, less speed less power. Through out the day if I needed to check email or do some browsing I would change it back to ondemand, and the max would change to 1100. Now if I go to powersaver though it stays at 1100 instead of switching. Question is this was it doing the right thing earlier switching to 800 or is it not working right now?

 

[Skull One]

skull please just get it over with and please put out your own version of setcpu so the thing will be done right. i kno your busy and dont have time. but i would really appreciate it and so the rest of the community and i would pay top dollar for your hard work

I have considered it. Even laid out the design criteria needed to cover all the bases. But my testing is easy to do. Learning how to code Java for the Android OS is a tad bit harder. Plus I only have a Motorola Droid to test with. Which means I could only guarantee it would work for one out of what, 50 different Android based phones? That concerns me a little.

 

[Skull One]

I just started rooting again and have been playing around with kernels and themes and have come across a setcpu question for my droid. I understand what the governors do as far as how the cpu scales, but I'm curious how they are supposed to function. For instance earlier today I set it on powersaver and I noticed that the maximum dropped down to 800 from 1100 automatically. Now this made perfect sense to me, less speed less power. Through out the day if I needed to check email or do some browsing I would change it back to ondemand, and the max would change to 1100. Now if I go to powersaver though it stays at 1100 instead of switching. Question is this was it doing the right thing earlier switching to 800 or is it not working right now?

You probably had a profile in use at the time. Either the charging one or your first battery level one as a rough guess. Powersaver doesn't change the max frequency. It simply limits how fast it gets to it and how long it stays there.