SetCPU Time in State 0 below 500MHz

[sonnydroid]

Not sure what happen but although I have my MIN at 125MHz, SetCPU won't underclock it pass 500MHz.

Is anyone else having this problem? And most importantly, is there a way to fix it?

P.s. yes I have it to auto detect.. Its the stock kernel BBv0.6.2.1 came with.



Sent from my Droid using DroidForums App

[x25064]

This may be a stupid suggestion, but have you shut off the governor in the toolkit?

My setcpu is reading 0 for everything which clearly isn't the case otherwise my phone wouldn't be running. I just disabled the governor in the toolkit so I'll see if that does anything. I thought setcpu overrode the rom's governor but maybe not, that's yet to be determined.

[sonnydroid]

Yes, since I use SetCPU with 1 (screen off) profile, cpu scaling in rom kit is disable.

Sent from my Droid using DroidForums App

[x25064]

Yeah disabling didn't do anything for me, but currently I have 0's for every frequency so I'm not sure what the issue is.

[HarvesterX™]

x25064, what kernel are you using? Some kernels don't support this. The stock BB kernel should as it is a modified 800MHz v1.6 Slayher kernel and those support it. I'm using a slayher 800MHz clocked at 1.1GHz (milestone overclock app) and the time on state works. For.some reason I'm thinking the v32 p3 ones don't, but I don't remember with enough certainty to say that as a fact. I know one of the kernels I have saved on the sdcard doesn't support this lol.

[sonnydroid]

I'm using the stock kernel that came with BB. I even restored to a previous backup when Time in State was working for all, but that still didn't fix the problem.

Sent from my Droid using DroidForums App

[HarvesterX™]

It doesn't make any sense why it's not working of you restored a backup where you knew that it was. The only advice I can think of is to download and flash a v1.6 slayher kernel (which ia what stock is, but slightly modified) and see if the time in state comes back. Other than that I'm at a loss of words and probably won't be too helpful. I'm still a little confounded why a restore of a backup didn't fix the issue if you were positive that it was working (unless maybe you did an advanced restore and only restored the boot partition as there might be a module or something in the /system partition that is needed but missing.

Wish I could be more helpful here...

[x25064]

I'm using a slayher 1.7 1ghz kernel, so kernels def aren't the problem.

Bb6.1.2 is littered with strange errors like this. I'd be surprised if we didn't see a new version soon.

[sonnydroid]

I do my backups thru Rom manager and yes I'm positive it was working before. I restored thru Rom Manager as well. Will it make a difference if I restored thru clockworkmod, by wiping and restoring?

Also, I just tried the Milestone Overclock app, ran the script (didn't make changes to rate and vsel yet) and still the same thing.

No Time in State for the first 2 slots, but this time its at 450MHz since the third slot is set at that.



Sent from my Droid using DroidForums App

[TMYINC]

@sonnydroid Is your phone charging? What is your screen off profile set to? Is it enabled? I didn't see setcpu's profile icon in your notification bar so that is why I ask if it is enabled are not. I know it can be enabled with out notifications on, just curious.