SetCPU 1.50 bug?

[ViciousCircle]

This didn't happen prior to the latest SetCPU update (1.50) that came out last night. If I have my charging profile turned on, it seems to always use that one now, ignoring my normal SetCPU settings. If I turn off that particular profile, all works well.

Running BB1.1 with AdamZ's kernel.

[dfuser10332]

This didn't happen prior to the latest SetCPU update (1.50) that came out last night. If I have my charging profile turned on, it seems to always use that one now, ignoring my normal SetCPU settings. If I turn off that particular profile, all works well.

Running BB1.1 with AdamZ's kernel.

I just downloaded it and I'm not seeing this bug you're talking about. If I see any changes I'll get back to you.

[dadevers]

This didn't happen prior to the latest SetCPU update (1.50) that came out last night. If I have my charging profile turned on, it seems to always use that one now, ignoring my normal SetCPU settings. If I turn off that particular profile, all works well.

Running BB1.1 with AdamZ's kernel.

Mine did the same thing. I reinstalled the last version until it gets fixed.

[BayouFlyFisher]

Yep mine did it too. I had to disable charging. It then went to 250. I had to move the slider from 1250 down to 250 and back up to 1250.

[bastosero]

I restarted after changing my profiles and it works fine for me. Did you guys try to reboot after changing the profiles also?

[jasonb]

This didn't happen prior to the latest SetCPU update (1.50) that came out last night. If I have my charging profile turned on, it seems to always use that one now, ignoring my normal SetCPU settings. If I turn off that particular profile, all works well.

Running BB1.1 with AdamZ's kernel.

Mine did the same thing. I reinstalled the last version until it gets fixed.

Can you share the file for the last version?

I am also having this problem.

[dadevers]

This didn't happen prior to the latest SetCPU update (1.50) that came out last night. If I have my charging profile turned on, it seems to always use that one now, ignoring my normal SetCPU settings. If I turn off that particular profile, all works well.

Running BB1.1 with AdamZ's kernel.

Mine did the same thing. I reinstalled the last version until it gets fixed.

Can you share the file for the last version?

I am also having this problem.

I had it backed up in astro.

[ViciousCircle]

If you want the previous version, there are links in the first post here:

SetCPU for Root Users [1.5.0 UPDATE notifications] 02/28/2010 [Over9000] - xda-developers

Last version looks like it wazs 1.46. That's the one that was working well for me.

[ViciousCircle]

Okay, looks like it may be working now. I went into the charging profile and just moved the slider back and forth to 'change' the profile, but set it back to what I wanted before hitting apply. Seems to be working now.

[bastosero]

Like I said on my earlier post, for those that changed your profile settings, try a reboot also. The current SetCPU works fine for me.