SetCPU Charging Profile & New Taz Kernel Not Friendly For Some Users

[olletsocmit]

I'm not sure who else has noticed this yet, but when you set your profiles in SetCPU there is one for when the phone is plugged in for charging. Most ppl have it set at 550 max - 250 min. So if ur overclocked at say 1ghz when u plug the phone in to charge it should run at stock speed. This is important for when ur driving long distances and using it as a gps so it does not get super hott. Anyways the problem is that when u plug it in, nothing happens. Yes the widget changes down to 550 max, but its not sctually changing. If you open the app and plug it in you will see that the white number in the upper left does not change. The 2 numbers that are green on the top right do, there the same as the widget though. Here is how we know its really not changing click system info and plug it in. If you look at BogoMIPS the number is a few decimal points under ur current overclock speed. Its truely not changing when u plug it in. Now to the same exact thing, BUT plug it into ur computer this time as if u were charging it threw the computer. First start by just opening SetCPU and pluging it in. Look at the top left number in white. It changes like it should plugged into the wall. If it does not change, hit refresh and it will. Now hit system info again. The number that you were looking at before next to BogoMIPS is now way down. Its a few decimal points under 550, where it should be.

So in conclusion... the profiles do not work when its plugged into the wall to charge!! This gets u thinking... do the sleep/standby profiles really truely work either... we can't tell if they are going down or not b/c the screen is off. But for right now its confirmed that the plugged in profile does not work when plugged into the wall. Ok sorry for spelling. This was typed on my droid! Currently running BB 0.7.5 and overclocked at 950mhz.

[Corinacakes]

wow that's kinda scary

[HolyGrail]

I have mine set for 800mhz plugged in, 550mhz unplugged. When plugged in it shows the white and green 800mhz. I just unplugged it, and both the white and green dropped down to 550mhz. I tried this now with the usb, and got the same results, so my profile appears to be working for me.
I did notice the my profile settings wouldn't stick until I checked "set on boot". Every since then its worked.

[Backnblack]

I have mine at 1Ghz, I am assuming that the profiles do work as my Droid is cool to the touch when charging...

[theascended]

Wow... such an alarmist. Try you experiment again, as another noted above I can confim your confirmantion is wrong. However, I have noticed it can take up to 30 seconds for the cpu profiles to actually change and therefore adjust the limits.

[natediddy1120]

Wow... such an alarmist. Try you experiment again, as another noted above I can confim your confirmantion is wrong. However, I have noticed it can take up to 30 seconds for the cpu profiles to actually change and therefore adjust the limits.

Yes, I will confirm this also....

My SetCPU works fine on every ROM I've tried.....and believe me I've tried 'em all

And yes, you're also correct, and can take about 30 seconds to register the CPU speed in the app

[windmeup]

When I plug my phone in, my SetCPU numbers instantly change to the charging profile. I am not experiencing the same issues you are, or the delays that some others have experienced. Guess I'm just lucky!

[Pdigg]

Mine works fine on BB 0.7.4
It wasn't until I installed 0.7.5 that it stopped working.
When I plug the phone in to charge, the widget, and the min/max on the main screen (top right green numbers) change as they should. But, the speed stays locked at 800Mhz.

No idea what is going on. I know a few others have reported this happening to them also when they upgraded to 0.7.5

[pthance]

SetCPU works as designed on my droid. Sorry to hear you are having issues.

[JhankG]

The ROM you are using has Taz's newest kernel. I have read that it does not work properly with SetCPU's profiles. BB 0.7.4 does not use the same kernel and the Sholes ROMs do not use the same kernel either, so you have a couple of options. Wait for SetCPU to get an update, go back to BB 0.7.4, or switch over to Sholes ROM (or any other ROM of your choice). Either way, I think you need to change the title of this thread because it is a bit misleading. SetCPU works wonderfully and has a great dev.