A couple of days ago I flashed Fresh 3.5 and SBC 4.2.2 Non-HAVS with a Seidio 3500mA extended battery. Phone is very stable and smooth, mimimal lag, and battery life has definitely improved without that big dropoff after unplugging from the charger. Now I have a question about which SetCPU governor I should be using. With the latest version of SetCPU, there are now 6 (smartass, interactive, ondemand, powersave, conservative, and performance). I'm currently using the conservative setting based on my own tests and other posts, although I used to use ondemand. Performance and powersave are obvious, but I have no idea what interactive does...I tried looking at the latest SetCPU guide but I can't even find a definition for interactive. There aren't any recommendations for specific kernels anyway, and I'm really looking for the best setting for my current SBC 4.2.2 non-HAVS. Thanks as always for the help...
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Recommended SetCPU governer with SBC 4.2.2 non-HAVS?
- Thread starter Roymus
- Start date
-
- Tags
- htc evo 4g
frenchy714
Android Expert
I like my phone using the smartass governor 1152/245 (over/under). With a non-HAVS kernel I'd use a screen off profile set at 245/245 (priority 100%). You'll get speed, stability, performance, and you'll still get EXCELLENT battery life........Let me know how it goes!
Interactive - my understanding of it is that it is similar to ondemand in that it bases the cpu frequency scaling on load determined on a constant sampling rate. Supposedly, it's more responsive and efficient.
Smartass - it's meant to make decisions on how to scale the cpu based on several factors such as battery life, load, etc. In theory, it does everything that setcpu profiles are meant to do automatically. For example, with smartass, when you turn the screen off, it will automatically keep the max scaling value way down.
Conservative - It's like most other governors in that it determines the frequency based on load using a sampling rate, but it differers in that it steps the frequency up and down in an attempt to favor lower frequencies. It's meant to save battery more so than ondemand.
Smartass - it's meant to make decisions on how to scale the cpu based on several factors such as battery life, load, etc. In theory, it does everything that setcpu profiles are meant to do automatically. For example, with smartass, when you turn the screen off, it will automatically keep the max scaling value way down.
Conservative - It's like most other governors in that it determines the frequency based on load using a sampling rate, but it differers in that it steps the frequency up and down in an attempt to favor lower frequencies. It's meant to save battery more so than ondemand.
That's neat, but that really just shows the phone being used for a whole lot of nothing, while being on WiFi to boot. I don't say that to say you aren't using your phone like you should, that's up to you, I just say it because nearly every kernel with a screen-off profile will give you outstanding battery life while the phone is sleeping. The real difference comes from how much battery your phone uses while doing different tasks (calls, texts, internet, games, etc.).
Smartass does appear to give me better quadrant scores, although I'm not sure why based on the definitions. With smartass I regularly get quadrant scores in the high 1300s...with interactive and other governors, 1100 and below. Overall performance seems to be better with smartass too (I'm OC's at 1190). Plus it has the coolest name. So I'll stick with smartass for now...
Quadrant scores are pretty much meaningless in terms of real-world usage. If you want to really test a kernel on an objective scale, you should set the governor to performance, which will peg the frequency at the max. Naturally any amount of scaling will give you a lower quadrant score.
Oh, and to those who are using screen-off profiles with smartass, that's pretty much unnecessary. It does it for you, already, and you could potentially cause conflicts. It probably won't matter, but still...
v01rider
Android Expert
I have a question regarding this as well. My info is in my signature,
I was playing around with the different scaling options and I found that if I set max/min to 1152/245 with ondemand scaling, the phone was rediculously responsive, but I would assume that the on demand scaling will use more battery than the smartass scaling correct? unless you had some very consevative profiles in the ondemand scaling?
I like how the battery lasts on the conservative scaling, but sometimes I just want it to be snappy, so trying to find a happy medium, any problems with overclocking on the "conservative" scaling?
do most people find that they dont run into any problems overclocking to 1152? would smartass scaling have a built in "failsafe" profile that would prevent it from getting too hot? Thanks, I did some searching but having a hard time finding these specific answers
I was playing around with the different scaling options and I found that if I set max/min to 1152/245 with ondemand scaling, the phone was rediculously responsive, but I would assume that the on demand scaling will use more battery than the smartass scaling correct? unless you had some very consevative profiles in the ondemand scaling?
I like how the battery lasts on the conservative scaling, but sometimes I just want it to be snappy, so trying to find a happy medium, any problems with overclocking on the "conservative" scaling?
do most people find that they dont run into any problems overclocking to 1152? would smartass scaling have a built in "failsafe" profile that would prevent it from getting too hot? Thanks, I did some searching but having a hard time finding these specific answers
frenchy714
Android Expert
Here's some info on how the Smartass Governor works
With smartass governor set, no profiles, scaled to 1152/245, you'll get the performance you want while still realizing the battery life you've been seeking to achieve....1152/245 is known to be the most stable setup for most EVO's using kernels with smartass.
Havs: Hybrid Adaptive Voltage Scaling, basically tries to undervolt as much as possible to conserve power, but adapts to things like cpu load and temperature.
Cool thanks! I was reading on the XDA forum that people were saying the smartass govenor was great with the screen off but it would drain quickly with the screen on, more so than say the conservative governor, (they didnt mention how it drained with the screen on compared to "on demand")
So I was thinking I could keep it at 1152/245 and just swap between either smartass or conservative governors depending on how long I needed by battery to last... Do you see any potential problems with me doing that? I swapped a little yesterday with the min/max set at 998/245 and I definately felt like the smartass was snappier but he conserative made the battery last noticeably longer..
So I was thinking I could keep it at 1152/245 and just swap between either smartass or conservative governors depending on how long I needed by battery to last... Do you see any potential problems with me doing that? I swapped a little yesterday with the min/max set at 998/245 and I definately felt like the smartass was snappier but he conserative made the battery last noticeably longer..
frenchy714
Android Expert
There shouldn't be any problems with doing that. Keep in mind that every EVO reacts to kernels differently and what works for one may cause instability for another. Whatever you feel works best on your phone, go for it.