Root SetCPU and Das BAMF 1.6.3

[schmaltzy]

I just rooted my T-BOLT!!!

Came from a D1 about a month ago and I love my T-Bolt so much I decided to root!

Just threw Das BAMF on there and so far so good. But I go to use SetCPU and I get FC's like crazy when I try to change the MAX clock speed. Suggestions?

 

[schmaltzy]

Nevermind......I must have had something mess up with the APK when installing it though Titanium. I uninstalled it, reinstalled it, and it worked fine!

 

[ahoogst]

What setting are you using for the governor? The "ondemand" profile is pretty self explanatory but I haven't been able to find much info on smartass other than it's similar to interactive, but better...

 

[schmaltzy]

What setting are you using for the governor? The "ondemand" profile is pretty self explanatory but I haven't been able to find much info on smartass other than it's similar to interactive, but better...

All I can tell ya is that I leave it on "ondemand."

 

[Dex]

What setting are you using for the governor? The "ondemand" profile is pretty self explanatory but I haven't been able to find much info on smartass other than it's similar to interactive, but better...

I never figured it out either. I actually gave up on SetCPU by 1.6.3 because I had some issues with it in previous NTE versions of BAMF. The toolkit does a decent job of handling everything.

 

[ahoogst]

I never figured it out either. I actually gave up on SetCPU by 1.6.3 because I had some issues with it in previous NTE versions of BAMF. The toolkit does a decent job of handling everything.

Yeah I'm using the toolkit as well. Do I need to leave "Apply on boot" checked for the governor to be applied? Last time I did that I think I got an error after rebooting.

 

[ridobe]

Yeah I'm using the toolkit as well. Do I need to leave "Apply on boot" checked for the governor to be applied? Last time I did that I think I got an error after rebooting.

I'm assuming you mean "unclean shutdown". If so, it's because you ran speedtweak.sh. That runs the show as far as booting up. Applying on boot (toolkit only, not TiB) will cause this.